Public report of hocha113/CalamityOverhaul, published 16 November 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 report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert 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, 16 November 2026, 21:45 UTC · Survey ID cd_b77d205e79ac4eba8f33b3af6f5acb1c

hocha113/CalamityOverhaul

Measured 16 November 2026, 21:42 UTC, at code version 8d2bd38

First survey, so nothing to compare with yet Code coverage: not measured

Code coverage is not measured: Suite not runnable in-image.

CAI score 36.6out of 100 Weak
CriticalWeakAdequateStrongExemplary

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: 950,924 lines of product code in 5 projects, tests not counted · Estimated rebuild effort: about 18.3 person-years · Weakest lens: Production Readiness, 24.3

Findings by how serious they are

3 critical 12184 serious 70 minor

12 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look 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

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
16 November 2026, 21:42 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 the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

The score is deterministic, which means the same code always gets the same score. We work 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 ▸

41of 41 dimensions measured by tools.
12245of 12257 findings point to an exact file and line, so you can open each one in the code. The other 12 concern the repository as a whole, such as missing documentation.
41dimensions across 5 lenses, read from 950,924 lines of product code in 5 projects.
Chapters

Executive summary

hocha113/CalamityOverhaul falls short of our standard for a preview release because we found no working pipeline that builds or tests changes to the code and no automated security scanning of the code, its secrets or its dependencies. It scores 36.6 out of 100 and is rated Weak, and none of its three critical findings concern security.

Production Readiness, at 24.3, is the weakest lens and counts most in the score. The best first step is adding an automated build and test pipeline, worth about 9.7 points. Recording design decisions comes next, worth about 4.3 points. Raising Production Readiness to 62 would lift the score to about 46.9.

One set of files in separate parts keeps changing together, which points to a hidden dependency. Making the hidden dependencies explicit would close this risk. The loop of parts of the code that depend on each other needs breaking by moving the shared parts into a project of their own.

The product code is 950,924 lines, about €2,700,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 for The 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.
Production Readiness 24.3 · counts for 47%Maturity 37.8 · counts for 26%Code Health 43.0 · counts for 14%Security and Compliance 60.0 · counts for 8%Performance 100.0 · counts for 4%

If Production Readiness rose from 24.3 to 62, the lowest score rated Strong, the score would rise from 36.6 to about 46.9.

Code composition: what the lines of code are
Business logic 65%Supporting code 35%Tests 0%
Rebuild cost: about €2,700,000 · Estimate
Cost to rebuild€860,000 to €4,500,000, for 14,352 to 47,081 hours of work, about 18.3 person-years for 10 to 35 engineers
Difficulty of the problemStandard, 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 37. 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.
SizeVery large: 950,924 lines of product code, of which 19% is declarations and boilerplate, 16% straight logic and 65% logic with branches
Comment linesThe estimate prices 842,152 lines. Comment lines count towards the size of 950,924 lines but aren't priced as work.
What it is notNot 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: We price 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.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Add a CI workflow that builds and runs the test suite on every push/PR.
Raises the score by about 9.7 points · Medium effort · CI/CD gates
2
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.
Raises the score by about 4.3 points · Medium effort · Architecture documentation
3
Enforce authorization at every handler — call the guard method (throw-on-violation) from each one, or adopt [Authorize] so protected-by-default is demonstrable.
Raises the score by about 3.2 points · Medium effort · Access Controls

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 €2,700,000 to build again, about 18.3 person-years of work. Its weakest lens is Production Readiness, at 24.3 (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
Add a CI workflow that builds and runs the test suite on every push/PR. Of all the actions in this report, it raises the score most for the work it takes: about 9.7 points for medium effort. 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 5.8 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 6% to 13% on every change. The history of the code shows how much it changes: about 1,457,100 lines over the last 90 days, which is about 5,909,350 lines a year. At that pace, the extra work comes to an estimated 828.1 to 4968.7 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our 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; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
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.

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.

arch (root) (root) API API (root)->API Common Common (root)->Common Content Content (root)->Content API->Content Content->Common OtherMods OtherMods Content->OtherMods OtherMods->(root)

At a glance — Code Health · 43.0 · Weak · gated by D4, X5 ·

At a glance — Architecture · — · — ·

At a glance — Maturity · 37.8 · Weak · gated by M2 ·

At a glance — Readiness · 24.3 · Weak · gated by P1, P3 ·

At a glance — Security · 60.0 · Adequate · gated by C2 ·

At a glance — Performance · 100.0 · Exemplary ·

Roadmap

Top priorities: Add a CI workflow that builds and runs the test suite on every push/PR; 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; Enforce authorization at every handler — call the guard method (throw-on-violation) from each one, or adopt [Authorize] so protected-by-default is demonstrable.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Add a CI workflow that builds and runs the test suite on every push/PR.+9.7 ptsMediumCI/CD gates
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.+4.3 ptsMediumArchitecture documentation
Enforce authorization at every handler — call the guard method (throw-on-violation) from each one, or adopt [Authorize] so protected-by-default is demonstrable.+3.2 ptsMediumAccess Controls
Resolve the 2 Off-boarding risk finding(s) in Bus Factor.+1.4 ptsLowBus Factor
Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`.+2.7 ptsMediumNullable reference types
Expand the README with getting-started, architecture overview and a project map.+2.5 ptsMediumDocumentation (README)
Resolve the 2 finding(s) in Folder & project structure.+1.7 ptsMediumFolder & project structure
Swallowed exception (empty catch)+1.4 ptsMediumException handling

File quality

Per-file score 0–10 — a quality signature. Of 2691 files carrying findings, judged against the Preview bar: 0% slop · 0% mixed · 100% near-clean.

FileScoreBandWorst signal
Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendCleave.cs4.8MixedCyclomatic Complexity: CrimsonRendCleave.AI (cyclomatic 23)
Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/HeadPrimeAI.cs4.8MixedCyclomatic Complexity: HeadPrimeAI.TryBeginViceExecution (cyclomatic 21)
Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs5.5MixedCyclomatic Complexity: CrimsonRendSlash.UpdateBladePose (cyclomatic 39)
Content/HackTimes/HackPanelRenderer.cs5.5MixedCyclomatic Complexity: HackPanelRenderer.DrawRowForeground (cyclomatic 28)
Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs5.5MixedCognitive Complexity: OniAnnihilate.ModifyHitNPC (cognitive 16)
Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleCut.cs5.6MixedCognitive Complexity: OniFinaleCut.DrawDetonateDressing (cognitive 19)
Common/EffectLoader.cs6.5MixedChange Coupling: Boundary-crossing change coupling: EffectLoader.cs ↔ OnikiriUITheme.cs
Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistPlanetProj.cs7.0Near-cleanCyclomatic Complexity: CultistPlanetProj.AI (cyclomatic 97)
Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPour.cs7.0Near-cleanCyclomatic Complexity: KikasaInkPour.AI (cyclomatic 77)
Content/LegendWeapon/OnikiriLegend/OniDismembers/OniSeverStrike.cs7.0Near-cleanCyclomatic Complexity: OniSeverStrike.AcceptAuthoritySnapshot (cyclomatic 73)
Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs7.0Near-cleanCyclomatic Complexity: KikasaGunServant.UpdateGuns (cyclomatic 62)
Content/LegendWeapon/OnikiriLegend/UI/OniMeiUI.cs7.0Near-cleanCyclomatic Complexity: OniMeiUI.UpdateInteraction (cyclomatic 61)
Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs7.0Near-cleanCyclomatic Complexity: OnikiriPlayer.PostUpdate (cyclomatic 60)
Content/LegendWeapon/KikasaLegend/UI/Panorama/KikasaPanoramaUI.cs7.0Near-cleanCyclomatic Complexity: KikasaPanoramaUI.DrawHoverTipPanel (cyclomatic 58)
Content/LegendWeapon/HalibutLegend/UI/Atlas/AtlasSkillSea.cs7.0Near-cleanCyclomatic Complexity: AtlasSkillSea.Update (cyclomatic 50)
Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs7.0Near-cleanCyclomatic Complexity: KikasaInkDrop.AI (cyclomatic 50)
Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs7.0Near-cleanCyclomatic Complexity: KikasaQueenBeeServant.UpdateRake (cyclomatic 49)
Content/NPCs/BrutalNPCs/BrutalMoonLord/Core/MLordLocomotion.cs7.0Near-cleanCyclomatic Complexity: MLordLocomotion.Update (cyclomatic 49)
Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs7.0Near-cleanCyclomatic Complexity: DeepGaolWraith.UpdateCuffs (cyclomatic 48)
Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs7.0Near-cleanCyclomatic Complexity: CrimsonSweepSlash.UpdateBladePose (cyclomatic 45)

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 — 3

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 — 12184

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 — 70

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 12

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

This survey 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. All 41 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.7, the weighted average across measured dimensions.

Every figure here is one of two 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. 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.

What we checked — 41 dimensions across the health lenses
D1D2D3D4D5D6D13D15D16D28D29D34D35AX10AX2AX3AX4AX6C2GD1IC1M1M2M3P1P3PF3X12X15X16X18X20X21X23X25X27X28X29X3X30X5

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
  1. 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, 12245 of 12257 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.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. 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.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic

Every finding is locatable in findings.md. Run 01a1e64f-d4ae-7eb9-99ce-4e0aa8e8ac0b.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

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.

  • D8 Code Coverage — not measured this run — We 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. Coverage NOT MEASURED: the test suite could not be built/run in-image (commonly external-service dependencies — a database, a broker — we won't provision). To have it measured, make the suite runnable without them. For context only, test code is ≈ 0% of production LoC (132 test / 950,924 production) — a rough proxy, NOT a coverage measurement, so it is excluded from the score. You can widen what we reach: optional: make the suite runnable without a database, broker or other service we do not provision, and real coverage is measured on the next scan.
  • D12 Dependency Hygiene — not measured this run — We 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: /usr/share/dotnet/sdk/10.0.400/NuGet.targets(521,5): error MSB3202: The project file "CalamityOverhaul.csproj" was not found. [CalamityOverhaul.sln].
  • D14 License Compliance — not measured this run — We 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.
  • D20 ADR Quality — not measured this run — We 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. The ADR expectation is gated on whether a repository ships a deployable product. Our repo-kind classifier reads .NET project files and the host and package markers of the other ecosystems it knows (a Go `package main`, a Cargo binary, a package.json `bin`, `start` script or application dev server such as Vite or Next, Python console scripts or a Django/WSGI entry point, a Spring Boot / WAR / Gradle application build, a Rack or Rails app, a Composer project, an OTP release or escript, a Dockerfile, a Procfile, a Platform.sh `.platform/routes.yaml`, and the corresponding published-package manifests, including an OTP `*.app.src`, a Drupal module's `*.info` and a Claude Code `.claude-plugin/plugin.json`), and found none here, so we could not tell what kind of repository this is and did not assess its ADR log. This is a gap in our analyzer, not a finding about this repository. Read, stating neither a host nor a published package: `CWRAsset.cs`, `CWRConstant.cs`, `CWRID.cs`, `CWRLoad.cs`, `CWRMod.cs`, ….
  • D22 Internal API Consistency — not measured this run — We 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. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository DOES commit C#/VB source and a project or solution file, so the conventions are there to read and the load still produced nothing. That is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and runs on C# constantly, and the remedy is to inspect the restore, the SDK band and the target resolution — not to build anything.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We 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. `CWRLoad.cs`, `Content/CWRCrafted.cs`, `Content/Cyberwares/Implementation/SCCA32CRPs/SCCA32CRPPlayer.cs`, `Content/Cyberwares/Implementation/Sandevistans/SandevistanPlayer.cs`, `Content/Cyberwares/Implementation/SelfHackCrystals/SelfHackCrystalPlayer.cs`, … (+322 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • D44 Platform End-of-Life — not measured this run — We 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.
  • AX2 Stateful singletons — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. 1054 further occurrence(s) are not listed individually; the score already reflects all 1094.
  • P5 DR & Backup — not measured this run — We 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 backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found. Whether there is anything here to recover could NOT be determined: persistence is detected from deployment/container manifests and from dependency manifests, and neither was readable by this pass, so a data store this code opens directly — a file, an embedded database — would not be visible to it. The blindness is this analyzer's, not a finding that the repository holds no data. You can widen what we reach: keep the deployment/container manifest or a dependency manifest in this repository — or a link to the ops repo that holds the DR evidence — so the persistence probe has something to read.
  • P8 Schema migrations — not measured this run — We 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 EF Core usage in C# and the schema tooling its file scan recognises only, and no .NET project was loaded, and this repository's language is not one the scan models, 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.
  • X10 Duplicated predicate — not measured this run — We 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 — We 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 repository's C# was parsed (it ships no .sln or .csproj, so it was read as syntax-only projects), but this check proves its findings from resolved symbols and a reference-free parse resolves none. It abstained rather than report a clean bill it could not earn. That is a gap in this analyzer's reach into build-less repositories — not a finding that the repository is free of what this check looks for.
  • X3 Exception handling — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. 21 further occurrence(s) are not listed individually; the score already reflects all 61.
  • Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for one or more projects, so those projects were analysed with framework references only: every check keyed on a third-party type saw an error type there and reported nothing. Findings on those projects are a lower bound; run `dotnet restore` on them and rescan.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

We assess the repository exactly as committed, and only the repository. By design we do 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.
  • 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.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • 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.

Dimensions

D1 · Cyclomatic Complexity6.0 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 6.0 / 10 · rule-coverage 100% · ceiling Prevented

1425 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was CultistPlanetProj.AI at 97. A further 34 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 OniMeiCombat.IsExplicitNonHeadSegment at 38 — they are counted neither in the figure above nor in this dimension's score. 13 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: Content/Cyberwares/Implementation/Sandevistans/SandevistanNet.cs (SandevistanStateSnapshot.IsValid.get at 31), Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraRangedSlashSequence.cs (SakuraRangedSlashSequence.SakuraRangedSlashSequence.ctor at 28), Content/RAMSystems/RamNet.cs (RamStateSnapshot.IsValid.get at 26), Content/LegendWeapon/OnikiriLegend/OniDismembers/OniSeverReplicationSystem.cs (OniSeverActivationSnapshot.IsValid.get at 21), Content/Scenarios/Shenyo/ShenyoFullBodyPortrait.cs (ShenyoFullBodyPortrait.OnDraw at 18), and 8 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

CultistPlanetProj.AI (cyclomatic 97)Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistPlanetProj.cs:126
KikasaInkPour.AI (cyclomatic 77)Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPour.cs:161
BssHubState.PickAttack (cyclomatic 75)Content/NPCs/BloomsandSerpents/States/BssHubState.cs:140
OniSeverStrike.AcceptAuthoritySnapshot (cyclomatic 73)Content/LegendWeapon/OnikiriLegend/OniDismembers/OniSeverStrike.cs:936
ValidatePass.ApplyPass (cyclomatic 73)Content/Scenarios/Dungeonworld/Gen/Passes/ValidatePass.cs:21

+ 1420 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 9 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with CultistPlanetProj.AI (cyclomatic 97), KikasaInkPour.AI (cyclomatic 77), BssHubState.PickAttack (cyclomatic 75). — 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 9 together lifts Cyclomatic Complexity from 6.0 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

D2 · Cognitive Complexity4.9 / 10Weak✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 4.9 / 10 · rule-coverage 100% · ceiling Prevented

2113 method(s) exceeded the cognitive complexity threshold of 15; the worst was KikasaGunServant.UpdateGuns at 145.

KikasaGunServant.UpdateGuns (cognitive 145)Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1040
CultistPlanetProj.AI (cognitive 133)Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistPlanetProj.cs:126
ValidatePass.ApplyPass (cognitive 126)Content/Scenarios/Dungeonworld/Gen/Passes/ValidatePass.cs:21
KikasaPanoramaUI.DrawHoverTipPanel (cognitive 117)Content/LegendWeapon/KikasaLegend/UI/Panorama/KikasaPanoramaUI.cs:2064
CultistConjunctionState.UpdateRelease (cognitive 109)Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistConjunctionState.cs:149

+ 2108 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 3 bodies over 120 down to 120 or less in Cognitive Complexity — start with KikasaGunServant.UpdateGuns (cognitive 145), CultistPlanetProj.AI (cognitive 133), ValidatePass.ApplyPass (cognitive 126). — 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 3 together lifts Cognitive Complexity from 4.9 to about 5.2/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

D3 · God Classes8.5 / 10Strong✓ 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.

Maturity: Documented → Verified → Prevented · effective 8.5 / 10 · rule-coverage 100% · ceiling Prevented

472 god class(es) detected.

FileTooLong: OnikiriLegend/OnikiriPlayer.cs · ×178Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs
TooManyMethods: OnikiriPlayer · ×132Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs
ClassTooLong: TwinsRenderHelper · ×94Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Rendering/TwinsRenderHelper.cs
MethodTooLong: KikasaGunServant.UpdateGuns · ×68Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1040

What to do

  1. Resolve the 178 FileTooLong finding(s) in God Classes — start with OnikiriPlayer.cs, DeepGaolWraith.cs, KikasaPanoramaUI.cs. — One of this dimension's main actionable groups (178 warning-level).
  2. Resolve the 132 TooManyMethods finding(s) in God Classes — start with TimeFreezeSystem.cs (2), WorldFreezeGlobals.cs (2), OnikiriPlayer.cs. — One of this dimension's main actionable groups (132 warning-level).
  3. Resolve the 94 ClassTooLong finding(s) in God Classes — start with TwinsRenderHelper.cs, OverhaulSettingsUI.cs, KikasaHud.cs. — One of this dimension's main actionable groups (94 warning-level).

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

D4 · Code Duplication2.1 / 10Critical✓ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

Maturity: Documented → Verified → Prevented · effective 2.1 / 10 · rule-coverage 100% · ceiling Verified

4651 duplicated block group(s) detected. 19.8 % of the production lines (188,489 of 950,924) are in a reported copy. A further 3141 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.

Duplicated block (5 lines × 2) · ×465Content/Scenarios/OldNet/Tiles/OldNetBulkheadTile.cs:48
Duplicated block (6 lines × 2) · ×387Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:250
Duplicated block (7 lines × 2) · ×284Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/PrimeCannonAI.cs:77
Duplicated block (8 lines × 2) · ×238Content/LegendWeapon/HalibutLegend/FishSkills/FishBat.cs:602
Duplicated block (9 lines × 2) · ×177Content/Scenarios/OldDuke/Campsites/CampsiteLocationFinder.cs:222

+ 874 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 465 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with DraedonQuestLogStyle.cs (4), KikasaEyeServant.cs (4), FishBunny.cs (3). — One of this dimension's main actionable groups (465 warning-level).
  2. Resolve the 387 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with KikasaDestroyerServant.cs (5), KikasaEyeServant.cs (4), Undrowned.cs (4). — One of this dimension's main actionable groups (387 warning-level).
  3. Resolve the 284 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with KikasaEyeServant.cs (6), DraedonQuestLogStyle.cs (4), QueenChandelierProj.cs (3). — One of this dimension's main actionable groups (284 warning-level).

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

D5 · Coupling0.0 / 10Critical✓ 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.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Prevented

5 production modules (source-import), 1 dependency cycle(s), 0 unstable depended-on module(s). No manifest declares this repository's modules, so the modules are its top-level source directories and the edges the imports between them; 0 module(s) off the main sequence.

Circular dependency

What to do

  1. Resolve the 1 Circular dependency finding(s) in Coupling. — One of this dimension's main actionable groups (1 issue-level).

Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 1075 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D15 · Churn × Complexity Hotspots9.9 / 10Stronggated by 272 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs (47×60=2820); Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs (53×39=2067); Content/LegendWeapon/OnikiriLegend/UI/OniMeiUI.cs (26×61=1586)

Hotspot: Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs · ×272Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs:531

What to do

  1. Resolve the 272 Hotspot finding(s) in Churn × Complexity Hotspots — start with OnikiriPlayer.cs, CrimsonRendSlash.cs, OniMeiUI.cs. — One of this dimension's main actionable groups (272 warning-level).

Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.

D16 · Bus Factor8.3 / 10Strong✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

Maturity: Documented → Verified → Prevented · effective 8.3 / 10 · rule-coverage 100% · ceiling Documented

521 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs. Counted over 3000 of the 4735 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Off-boarding risk: anonymized user #1 · ×2

What to do

  1. Resolve the 2 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (2 recommendation-level).

Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)10.0 / 10Exemplary○ Nothing flagged

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).

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

semgrep found no security issues. semgrep hit a parse error in 327 file(s) — `CWRLoad.cs`, `Content/CWRCrafted.cs` (lines 181–185, lines 188–192, lines 195–199, …), `Content/Cyberwares/Implementation/SCCA32CRPs/SCCA32CRPPlayer.cs` (line 43, line 47), `Content/Cyberwares/Implementation/Sandevistans/SandevistanPlayer.cs` (line 150), `Content/Cyberwares/Implementation/SelfHackCrystals/SelfHackCrystalPlayer.cs` (line 172, line 182, line 186), … (+322 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 63 of those file(s) — `Content/Cyberwares/UIs/CyberSlotRenderer.cs`, `Content/GameModes/BrutalMobs/DungeonDeep/DungeonDeepNPC.cs`, `Content/GameModes/BrutalMobs/Eclipse/EclEclipseSets.cs`, `Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserMarkLine.cs`, `Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomSporeMistTelegraph.cs`, … (+58 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. In 49 of those file(s) — `CWRLoad.cs`, `Content/CWRCrafted.cs`, `Content/DamageModify/ModifyNPCDamage.cs`, `Content/GameModes/UI/GameModeWorldMenu.cs`, `Content/Industrials/ElectricPowers/Crushers/CrusherRecipes.cs`, … (+44 more) — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything.

✓ On the Gold path — maintain.

Detailed fixes: d29_recommendation.md.

D34 · Knowledge Freshness10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

Every significant source file has living knowledge — recently and meaningfully worked. Counted over 3000 of the 4735 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

D35 · Change Coupling10.0 / 10Adequategated by 1 critical finding✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: HeadPrimeAI.cs↔PrimeCannonOnSpan.cs 85%; OniFlashMark.cs↔OniZanshinSlash.cs 80%; CrimsonRendCleave.cs↔CrimsonRendSlash.cs 70%

Boundary-crossing change coupling: EffectLoader.cs ↔ OnikiriUITheme.csCommon/EffectLoader.cs:1
Change coupling: HeadPrimeAI.cs ↔ PrimeCannonOnSpan.cs · ×7Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/HeadPrimeAI.cs:1
Change-coupling hub: CrimsonRendSlash.cs → CrimsonRendCleave.cs, OniAnnihilate.cs, OniFinaleCut.cs, OniFlashMark.cs · ×2Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs

What to do

  1. Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with EffectLoader.cs. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 7 Change coupling finding(s) in Change Coupling — start with HeadPrimeAI.cs (2), CrimsonRendCleave.cs (2), OniFlashMark.cs. — One of this dimension's main actionable groups (7 warning-level).
  3. Resolve the 2 Change-coupling hub finding(s) in Change Coupling — start with CrimsonRendSlash.cs, OniFinaleCut.cs. — One of this dimension's main actionable groups (2 warning-level).

Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX10 · Code composition10.0 / 10Exemplary✓ Tool-verified

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.

AX2 · Stateful singletons1.0 / 10Critical✓ Tool-verified

Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.

Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.

  • `ExternalQuestNode` is not registered, but `QuestLogsAPI` creates it and keeps it in the static `QuestNode._quests`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_title, _summary, _detail, _objective, _completeBool, _completeFloat; e.g. `_title` at line 56). — Content/QuestLogs/Core/ExternalQuestNode.cs:13
  • `HackUploadOverlay` is not registered, but `HackTimeRender` creates it and keeps it in the static `UploadOverlay`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (pulseTimer; e.g. `pulseTimer` at line 14). — Content/HackTimes/HackUploadOverlay.cs:8
  • `OreDropRule` is not registered, but `MiningMachineSystem` creates it and keeps it in the static `DropRules`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (Relevance, Progress, WorldState, NeedDedicatedDrill, IsRareByproduct, VeinWeightPerTile; e.g. `Relevance` at line 300). — Content/Industrials/ElectricPowers/MiningMachines/MiningMachineSystem.cs:270
  • `LegendUpgradeDecision` keeps one instance of itself in the static `Instance`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (cachedName, cachedLevel, cachedItemType; e.g. `cachedName` at line 27). — Content/LegendWeapon/LegendUpgradeDecision.cs:12
  • `RestartFishBoid` is not registered, but `HalibutReset` creates it and keeps it in the static `garnishFish`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (Life, LifeProgress, spiralAngle, Velocity, Position, Frame; e.g. `Life` at line 136). — Content/LegendWeapon/HalibutLegend/DomainSkills/RestartFish.cs:97
  • `Track` is not registered, but `KikasaResetHistory` creates it and keeps it in the static `npcTracks`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (Head, Count; e.g. `Head` at line 43). — Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetHistory.cs:36
  • `OniStancePreviewSource` is not registered, but `OniStance` creates it and keeps it in the static `preview`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (lastTick, fullHold, value, gainCountdown; e.g. `lastTick` at line 71). — Content/LegendWeapon/OnikiriLegend/UI/OniStanceData.cs:59
  • `OniVigorPreviewSource` is not registered, but `OniVigor` creates it and keeps it in the static `preview`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (lastTick, value, spendCountdown; e.g. `lastTick` at line 69). — Content/LegendWeapon/OnikiriLegend/UI/OniVigorData.cs:58
  • `SHPCModuleSection` is not registered, but `SHPCItemTooltipPanel` creates it and keeps it in the static `moduleSection`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (modules, bonus; e.g. `modules` at line 128). — Content/LegendWeapon/SHPCLegend/UI/SHPCItemTooltipPanel.cs:113
  • `BssPortraitActor` keeps one instance of itself in the static `instance`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (petalTimer, flowerTimer, dustTimer; e.g. `petalTimer` at line 60). — Content/NPCs/BloomsandSerpents/BssPortrait.cs:15
  • `FssPortraitActor` keeps one instance of itself in the static `instance`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (dripTimer, dustTimer; e.g. `dripTimer` at line 64). — Content/NPCs/FestersandSerpents/Rendering/FssPortrait.cs:17
  • `CrabulonLife` is not registered, but `CrabulonMountLifeBar` creates it and keeps it in the static `crabulonLives`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (waveShakeOffset, shakeTime, damageShakeOffset, dynamicRotation, lifeValue, dynamicScale; e.g. `waveShakeOffset` at line 151). — Content/NPCs/Modifys/Crabulons/CrabulonUIs/CrabulonMountLifeBar.cs:126
  • `SeaShrimpPortraitActor` keeps one instance of itself in the static `instance`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (ctx, headPos, heading; e.g. `ctx` at line 31). — Content/NPCs/SeaShrimp/Rendering/SeaShrimpPortrait.cs:15
  • `QuestWorldDecision` keeps one instance of itself in the static `current`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (answered; e.g. `answered` at line 55). — Content/QuestLogs/QuestWorldDecision.cs:11
  • `GlyphLayout` is not registered, but `RarityNameEffects` creates it and keeps it in the static `sharedLayout`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (Glyphs, Positions, Widths; e.g. `Glyphs` at line 82). — Content/Rarities/RarityNameEffects.cs:64
  • `TechParticle` is not registered, but `ExoMechdusaSumRender` creates it and keeps it in the static `techParticles`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (Life, Position, Velocity, Rotation; e.g. `Life` at line 593). — Content/Scenarios/Draedon/ExoMechdusaSums/ExoMechdusaSumRender.cs:570
  • `MatrixRain` is not registered, but `DeploySignaltowerRender` creates it and keeps it in the static `matrixRains`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (Y, UpdateTimer, Characters; e.g. `Y` at line 425). — Content/Scenarios/Draedon/Quest/DeploySignaltowers/DeploySignaltowerRender.cs:399
  • `HexDataBlock` is not registered, but `DeploySignaltowerRender` creates it and keeps it in the static `hexBlocks`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (Life; e.g. `Life` at line 514). — Content/Scenarios/Draedon/Quest/DeploySignaltowers/DeploySignaltowerRender.cs:490
  • `TechParticle` is not registered, but `DeploySignaltowerRender` creates it and keeps it in the static `techParticles`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (Life, Position, Velocity, Rotation; e.g. `Life` at line 773). — Content/Scenarios/Draedon/Quest/DeploySignaltowers/DeploySignaltowerRender.cs:750
  • `DataStream` is not registered, but `DeploySignaltowerRender` creates it and keeps it in the static `dataStreams`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (Life, Position; e.g. `Life` at line 868). — Content/Scenarios/Draedon/Quest/DeploySignaltowers/DeploySignaltowerRender.cs:847
  • `OldNetNodeBudget` is not registered, but `OldNetPlans` creates it and keeps it in the static `Budget`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (UnderPlainPlaced; e.g. `UnderPlainPlaced` at line 81). — Content/Scenarios/OldNet/Gen/OldNetBuildContext.cs:51
  • `EnchantmentHandler` is not registered, but `EnchantUI` creates it and keeps it in the static `EnchantmentHandler`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (EnchantProgress, SelectedEnchantment, SelectedEnchantmentIndex, IsEnchanting, CurrentItem; e.g. `EnchantProgress` at line 43). — Content/Scenarios/SupCal/End/EternalBlazingNow/Enchants/EnchantmentHandler.cs:11
  • `CyberBossHPUI` is not registered, but `CyberBossBarStyle` creates it and keeps it in the static `Bars`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (CloseTimer, OpenTimer, InitMaxLife, HitFlash, PrevLife, SmoothRatio; e.g. `CloseTimer` at line 134). — Content/UIs/BossBars/CyberBossBarStyle.cs:83
  • `PortraitMotes` is not registered, but the singleton `BssPortraitActor` creates it and keeps it in `motes`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (motes; e.g. `motes` at line 32). — OtherMods/BossChecklist/PortraitMotes.cs:11
  • `SerpentPortraitRig` is not registered, but the singleton `BssPortraitActor` creates it and keeps it in `rig`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (headPos, prevHeadPos, heading, displayHeading, snapHeading, gait; e.g. `headPos` at line 163). — OtherMods/BossChecklist/SerpentPortraitRig.cs:19
  • `FssClawRig` is not registered, but the singleton `FssPortraitActor` creates it and keeps it in `clawRig`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (lastCommand; e.g. `lastCommand` at line 190). — Content/NPCs/FestersandSerpents/FssClawRig.cs:20
  • `ShrimpSkeleton` is not registered, but the singleton `SeaShrimpPortraitActor` creates it and keeps it in `skeleton`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (seed, built, wavePhase, TailFlare, gripTick; e.g. `seed` at line 64). — Content/NPCs/SeaShrimp/Kinematics/ShrimpSkeleton.cs:12
  • `SeaShrimpStateContext` is not registered, but the singleton `SeaShrimpPortraitActor` creates it and keeps it in `ctx`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (SpineCurl, WaveGain, TailFlare, ClawDamageWindow, CrystalGlow, AfterimageStrength; e.g. `SpineCurl` at line 192). — Content/NPCs/SeaShrimp/Core/SeaShrimpStateContext.cs:41
  • `OldNetOccupancyGrid` is not registered, but the singleton `OldNetBuildContext` creates it and keeps it in `Grid`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (ReserveReject, ReserveOk; e.g. `ReserveReject` at line 45). — Content/Scenarios/OldNet/Gen/Rooms/OldNetOccupancyGrid.cs:8
  • `OldNetRoomGraph` is not registered, but the singleton `OldNetBuildContext` creates it and keeps it in `Graph`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (Edges; e.g. `Edges` at line 50). — Content/Scenarios/OldNet/Gen/Rooms/OldNetRoomLayout.cs:45
  • `BssLegRig` is not registered, but the singleton `SerpentPortraitRig` creates it and keeps it in `legRig`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (boundCtx, Scale, battleGroundAt, battlePlant, travel, travelDir; e.g. `boundCtx` at line 209). — Content/NPCs/BloomsandSerpents/BssLegRig.cs:33
  • `BssClawRig` is not registered, but the singleton `SerpentPortraitRig` creates it and keeps it in `clawRig`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (Scale, lastCommand; e.g. `Scale` at line 129). — Content/NPCs/BloomsandSerpents/BssClawRig.cs:25
  • `ShrimpLegGait` is not registered, but the singleton `ShrimpSkeleton` creates it and keeps it in `Gait`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (paddlePhase; e.g. `paddlePhase` at line 81). — Content/NPCs/SeaShrimp/Kinematics/ShrimpLegGait.cs:13
  • `CWRID` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_idCache; e.g. `_idCache` at line 522). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — CWRID.cs:10
  • `CWRLoad` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (SepulcherSegments, StormWeaverSegments, PrimordialWyrmSegments, PerforatorLargeSegments, PerforatorMediumSegments, ArmoredDiggerSegments; e.g. `SepulcherSegments` at line 142). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — CWRLoad.cs:13
  • `CWRMod` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (instance, ILoaders; e.g. `instance` at line 18). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — CWRMod.cs:11
  • `CWRNetWork` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (channels, channelByType; e.g. `channels` at line 27). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — CWRNetWork.cs:13
  • `CWRRef` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_has, loggedReflectionFailures, DownedBossSystemType, downedDesertScourgeProp, downedCLAMProp, downedCrabulonProp; e.g. `_has` at line 27). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — CWRRef.cs:22
  • `CheckedVersions` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (SaveVersion; e.g. `SaveVersion` at line 38). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — CheckedVersions.cs:9
  • `CWRClientConfig` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (Instance; e.g. `Instance` at line 57). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Common/CWRClientConfig.cs:9

What to do

  • Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
  • A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
AX3 · Project dependency cycles5.0 / 10Adequate✓ Tool-verified

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.

  • The projects (root) → API → (root) (one cycle inside a mutually-dependent group of 5 projects) form a reference cycle. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference.

What to do

  • Break project reference cycles by extracting shared abstractions into a separate project; keep the graph a DAG.
AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

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.

AX6 · Interface segregation9.7 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

  • `IQuestLogStyle` declares 24 members: `UpdateStyle`, `DrawBackground`, `DrawNode`, `DrawConnection`, `GetPadding`, `DrawQuestDetail`, `GetCloseButtonRect`, `GetRewardButtonRect`, `DrawProgressBar`, `GetClaimAllButtonRect`, `DrawClaimAllButton`, `GetResetViewButtonRect`, `DrawResetViewButton`, `GetStyleSwitchButtonRect`, `DrawStyleSwitchButton`, `GetNightModeButtonRect`, `DrawNightModeButton`, `DisplayName`, `SupportsNightMode`, `DrawsOwnChrome`, `DrawChrome`, `SyncLayout`, `DrawDetail`, `MeasureDetailHeight`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Content/QuestLogs/Core/IQuestLogStyle.cs:6

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
C2 · Access Controls3.0 / 10Weak✓ Tool-verified

Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.

Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.

  • Authorization machinery exists but no [Authorize] usage and no imperative guard calls were found at handlers.

What to do

  • Enforce authorization at every handler — call the guard method (throw-on-violation) from each one, or adopt [Authorize] so protected-by-default is demonstrable.
GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

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.

IC1 · Incompleteness & stubs7.5 / 10Strong✓ Tool-verified

Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

  • The first 2 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently. (×4) — Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainHoverState.cs:96, Content/NPCs/FestersandSerpents/States/FssMoltGrowthState.cs:90, Content/NPCs/Modifys/ModifyTruffle.cs:44, …
  • Both arms of `Context.IsAsuraMode ? … : …` are `2`, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerPrecisionSniperState.cs:22
  • The first 1 statement of the `if` and of the `else` are identical, so it runs on both paths regardless of the condition. Lift it above the `if` — leaving it duplicated inside makes the branches read as though they handled this differently. — Content/NPCs/BrutalNPCs/BrutalQueenBee/BrutalQueenBeeAI.cs:473
  • Both arms of `isEnhanced ? … : …` are `Color.Yellow`, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. — Content/PRTTypes/PRT_CampfireSteam.cs:39
  • Both arms of `plan.Forbidden ? … : …` are `12`, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. — Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3MazeBlock.cs:137
  • Control only reaches here when `qualityDrops.Count == 0` is false, because the guard on line 79 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test. — Content/Scenarios/OldDuke/Campsites/OldDuchestLootGenerator.cs:85
  • A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×27) — CWRUtils.cs:52, CWRUtils.cs:58, CWRUtils.cs:453, …
  • `StopOwnCutscene` has an empty body — confirm it's an intentional no-op and not an unfinished method. — Content/Scenarios/Kiame/Overlay/OniRainWorldTransition.cs:445

What to do

  • Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)4.0 / 10Weak✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

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 25 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, 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. — README.md:1

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.
M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

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.
M3 · Folder & project structure6.0 / 10Adequate✓ Tool-verified

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

  • Most of the production code is in directories of its own, but 12 application file(s) sit at the repository root beside the build and tooling files (`CWRAsset.cs`, `CWRConstant.cs`, `CWRID.cs`, `CWRLoad.cs`, `CWRMod.cs` and 7 more).
  • Tests aren't grouped in a dedicated test folder — the test surface isn't separable from production code at a glance.
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.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

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 `semgrep --config=auto` plus gitleaks for committed secrets — this tree has no MSBuild project file, so CodeQL's csharp pack (which traces a build) and NuGet security analyzers (which are referenced from a project) have nothing to attach to — 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: `semgrep --config=auto` plus gitleaks for committed secrets — this tree has no MSBuild project file, so CodeQL's csharp pack (which traces a build) and NuGet security analyzers (which are referenced from a project) have nothing to attach to — 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.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements (or a repository exception type deriving from it) controlled by an `if` — directly or through the `using`, `lock` or `try` that wraps the throw — whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`); in the `else` branch, for a conjunct of the admitting condition that is FALSE of a non-null `p`. Range guards are read for bounds that leave nothing and for a `p > C.Count` bound whose index then reaches `C[p]`, `C.RemoveAt(p)` or a method of the same type that indexes with it. Deterministic, provable per finding. Advisory.

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

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.

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

X3 · Exception handling4.8 / 10Adequate✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×34) — Content/Cyberwares/CyberwareNet.cs:233, Content/Cyberwares/CyberwareNet.cs:234, Content/Cyberwares/Implementation/SelfHackCrystals/SelfHackCrystalNet.cs:82, …
  • `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. (×6) — Content/Cyberwares/CyberwarePlayer.cs:369, Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterRecipeId.cs:145, Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:336, …

What to do

  • Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

X5 · Nullable reference types2.0 / 10Critical✓ Tool-verified

Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • This method contradicts itself about `entry`: line 261 writes `entry?.Provider`, which says `entry` can be null, but line 265 then dereferences it directly as `entry.Key` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `entry` truly cannot be null here, the `?.` is misleading. Settle it one way — test `entry` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — Content/EntrustManager/Styles/ChronicleManagerStyle.cs:265
  • This method contradicts itself about `hack`: line 585 writes `hack?.Name`, which says `hack` can be null, but line 603 then dereferences it directly as `hack.SlotIndex` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `hack` truly cannot be null here, the `?.` is misleading. Settle it one way — test `hack` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — Content/HackTimes/HackTimeNetSync.cs:603
  • This method contradicts itself about `cyberware`: line 63 writes `cyberware?.Player`, which says `cyberware` can be null, but line 65 then dereferences it directly as `cyberware.ProfileInitialized` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `cyberware` truly cannot be null here, the `?.` is misleading. Settle it one way — test `cyberware` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — Content/HackTimes/PvP/Protocols/CyberwareOfflineHook.cs:65
  • This method contradicts itself about `player`: line 224 tests it for null before doing anything with it — the author's own statement that null is an input this code expects — but that `if` scopes only the block beneath it, and line 241 then dereferences `player` as `player.GetModPlayer` AFTER the block has closed, where the guard no longer applies. A null `player` skips the guarded body and reaches that line anyway, throwing NullReferenceException on exactly the input the guard was written for. If the dereference belongs to the guarded work, move it inside the block; if `player` truly cannot be null by then, the guard above is misleading and should go. — Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs:241
  • This method contradicts itself about `player`: line 225 tests it for null before doing anything with it — the author's own statement that null is an input this code expects — but that `if` scopes only the block beneath it, and line 242 then dereferences `player` as `player.GetModPlayer` AFTER the block has closed, where the guard no longer applies. A null `player` skips the guarded body and reaches that line anyway, throwing NullReferenceException on exactly the input the guard was written for. If the dereference belongs to the guarded work, move it inside the block; if `player` truly cannot be null by then, the guard above is misleading and should go. — Content/Items/Melee/WeaverGrievanceses/WGManifestationNet.cs:242
  • This method contradicts itself about `unloadedItem`: line 66 assigns it with `as UnloadedItem`, which hands back null rather than throwing when the value is not a `UnloadedItem`, but line 67 then dereferences it directly as `unloadedItem.ModName` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `unloadedItem` once before the first use and handle the null case, or cast with `(UnloadedItem)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Content/Items/Modifys/RecoverUnloadedItem.cs:67
  • This method contradicts itself about `umbrella`: line 99 writes `umbrella?.FlipChargeFill`, which says `umbrella` can be null, but line 104 then dereferences it directly as `umbrella.Projectile` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `umbrella` truly cannot be null here, the `?.` is misleading. Settle it one way — test `umbrella` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuPei.cs:104
  • This method contradicts itself about `fx`: line 238 tests it for null before doing anything with it — the author's own statement that null is an input this code expects — but that `if` scopes only the block beneath it, and line 267 then dereferences `fx` as `fx.CurrentTechnique` AFTER the block has closed, where the guard no longer applies. A null `fx` skips the guarded body and reaches that line anyway, throwing NullReferenceException on exactly the input the guard was written for. If the dereference belongs to the guarded work, move it inside the block; if `fx` truly cannot be null by then, the guard above is misleading and should go. — Content/LegendWeapon/OnikiriLegend/OniOmokages/OniOmokageRender.cs:267
  • This method contradicts itself about `ui`: line 551 writes `ui?.FirstVisibleEntry`, which says `ui` can be null, but line 561 then dereferences it directly as `ui.SetEntryStatus` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `ui` truly cannot be null here, the `?.` is misleading. Settle it one way — test `ui` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — Content/QuestLogs/Guide/QuestBookGuidePlayer.cs:561
  • This method contradicts itself about `state`: line 588 writes `state?.LoadoutRevision`, which says `state` can be null, but line 577 then dereferences it directly as `state.TrySetSlotAuthority` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `state` truly cannot be null here, the `?.` is misleading. Settle it one way — test `state` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — Content/Wraiths/Runtime/WraithNet.cs:577
  • This method contradicts itself about `player`: line 805 writes `player?.selectedItem`, which says `player` can be null, but line 806 then dereferences it directly as `player.inventory` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `player` truly cannot be null here, the `?.` is misleading. Settle it one way — test `player` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — Content/Wraiths/Runtime/WraithNet.cs:806
  • 0/4735 C# file(s) are in a nullable-enabled context. This repository commits no project file, so nothing sets <Nullable>enable</Nullable> for it: a file is enabled only by its own `#nullable enable`, by a Unity `csc.rsp` with `-nullable:enable` for its assembly, or as a file-based app (`#:` directives) whose `#:property Nullable` does not turn it off. NRTs catch a whole class of null-deref bugs at compile time.

What to do

  • Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`.
  • Where a method null-tests a symbol and then uses it after the guarded block closes, move the trailing work inside the block — the guard skips its body on null, it does not stop the method.
  • Put every file in a nullable-enabled context — `#nullable enable` at its top, or commit a project file with <Nullable>enable</Nullable> — and resolve warnings rather than suppressing with `!`.

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.

LensScoreRatingImpact
Code Health43.0Weak — gated by D4, X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity37.8Weak — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness24.3Weak — gated by P1, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security60.0Adequate — gated by C2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100.0ExemplaryStrongest area.
Unscored — 1 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • X7 Silent fallback defaults — 31 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 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.

  • 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
  • P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 69 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.
  • AX1 Captive dependencies — no DI registrations detected
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) 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
  • 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 — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • D10 Test Quality — ~132 lines of test code exist on disk but weren't loaded from the analyzed solution (excluded from the .sln, or co-located/using a test attribute not loaded here), so test quality couldn't be assessed. Include the tests in the analyzed solution to enable this check.
  • 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
  • D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
  • D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution; this repository's .NET projects are all F# (.fsproj), which the C#/VB workspace does not load, so the dimension does not apply.
  • 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.
  • D20 ADR Quality — Repository kind not determined
  • D21 Naming Consistency — N/A — no production declarations to compare.
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D23 Boundary Type-Coupling — Production source is present (.cs) but bounded contexts are resolved over the C#/VB project set, which exposed none, so context scope could not be assessed. Not scored — this is a gap in the analyzer, not a verdict about this repository. Declaring the codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed — see the recommendation on this dimension for where. 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 — No hand-written C#, Visual Basic, TypeScript or JavaScript source; comment value is not applicable here.
  • D25 ADR Conformance — no ADRs to check
  • D26 Project Cohesion — Project cohesion is assessed over the .NET project set; this target exposed no projects, so project size and spread could not be assessed. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
  • D27 Navigability — No calls could be sampled, so navigability was not assessed — tracing effort is measured over resolved call sites and this target exposed none. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
  • D30 Dependency Vulnerabilities — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to 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) — 327 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • 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.
  • 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 project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured
  • 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 (this repository commits no MSBuild project, so its C# was read as syntax-only projects — a handler marked ONLY by an interface from a package is not visible without a build)
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • M4 Documentation accuracy — Not applicable: the 3 current-state document(s) make no claim of a kind M4 checks. 1 claim(s) of kinds M4 does not check were not checked (path 1); M4 checks only links and versions and artefact counts.
  • P12 CI test-gate honesty — no CI workflow found
  • P2 Observability — Observability was not assessed: this check reads a source model that does not carry this repository's product — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of a logging idiom this check recognises is NOT evidence that this repo lacks structured logging (it may log through its own ecosystem's logger). This is a gap in the analyzer, not a finding about this repository.
  • P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
  • P8 Schema migrations — 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
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found by the two searches this check runs — a BenchmarkDotNet package reference in any project file (loaded, or on disk), and a script whose name contains `benchmark` that this repository's CI runs. Neither can see a suite in another ecosystem's idiom, so this is not a verdict that the repository has none. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted, and nothing is asked of a repository that has none.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
  • X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X2 Cancellation propagation — no async method does work a token could cancel
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — This check needs a compiled C# program and this repository commits no project file to compile, so only its syntax could be read. That is a limit of the analyzer, not a finding about your code.
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's C# was read, and every log call in it goes through a logger that takes one finished message — its own wrapper, log4net, Console or Debug — so an interpolated message there loses nothing the API could have kept. Calls through Microsoft.Extensions.Logging, Serilog, NLog or ZLogger, or any logger with a message-template overload, would be judged.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

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.

Critical — 3 finding(s)
AX3 · Project dependency cycles · Project dependency cycle · ×1
  • Project dependency cycle — The projects (root) → API → (root) (one cycle inside a mutually-dependent group of 5 projects) form a reference cycle. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference.
D35 · Change Coupling · Boundary-crossing change coupling · ×1
  • Boundary-crossing change coupling: EffectLoader.cs ↔ OnikiriUITheme.cs Common/EffectLoader.cs:1 — `Common/EffectLoader.cs` (context Common) and `Content/LegendWeapon/OnikiriLegend/UI/OnikiriUITheme.cs` (context Content) sit in DIFFERENT parts of the tree yet change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `5228d822` update; `890ecf4d` update; `a375d021` update — run `git show` on any of them.
D5 · Coupling · Circular dependency · ×1
  • Circular dependency — (root) → API → (root) (one cycle inside a mutually-dependent group of 5 modules)
Serious — 12184 finding(s)
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×465
  • Duplicated block (5 lines × 2) Content/Scenarios/OldNet/Tiles/OldNetBulkheadTile.cs:48 — Content/Scenarios/OldNet/Tiles/OldNetBulkheadTile.cs:48-52 | Content/Scenarios/OldNet/Tiles/OldNetSealGateTile.cs:69-73 — 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 (5 lines × 2) Content/Scenarios/OldDuke/OldDukeShops/OldDukeShopRenderer.cs:117 — Content/Scenarios/OldDuke/OldDukeShops/OldDukeShopRenderer.cs:117-121 | Content/Scenarios/OldDuke/OldDukeShops/OldDukeShopRenderer.cs:321-325 — 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 × 2) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:642 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:642-646 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:808-812 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:642` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) Content/NPCs/SeaShrimp/Projectiles/SeaShrimpCavitationBubble.cs:113 — Content/NPCs/SeaShrimp/Projectiles/SeaShrimpCavitationBubble.cs:113-117 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpVoltBubble.cs:167-171 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpCavitationBubble.cs:113` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) Content/Items/Melee/WeaverGrievanceses/WGMaterializationRenderer.cs:203 — Content/Items/Melee/WeaverGrievanceses/WGMaterializationRenderer.cs:203-207 | Content/Items/Melee/WeaverGrievanceses/WGMaterializationRenderer.cs:263-267 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Melee/WeaverGrievanceses/WGMaterializationRenderer.cs:269` calls `SetValue` and `Content/Items/Melee/WeaverGrievanceses/WGMaterializationRenderer.cs:209` 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 (5 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainRender.cs:241 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainRender.cs:241-245 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainRender.cs:195-199 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainRender.cs:240` calls `FillUniforms` and `Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainRender.cs:194` does not — after which the two agree again for 4 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 (5 lines × 2) Content/GameModes/BrutalMobs/Ambience/DuneStorm/DuneStormRender.cs:238 — Content/GameModes/BrutalMobs/Ambience/DuneStorm/DuneStormRender.cs:238-242 | Content/GameModes/BrutalMobs/Ambience/Stratos/StratosAmbientRender.cs:134-138 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/DuneStorm/DuneStormRender.cs:238` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) Content/GameModes/BrutalMobs/Ambience/Prismglade/Projectiles/PrismgladeJudgmentProj.cs:182 — Content/GameModes/BrutalMobs/Ambience/Prismglade/Projectiles/PrismgladeJudgmentProj.cs:182-186 | Content/GameModes/BrutalMobs/Ambience/Prismglade/Projectiles/PrismgladeJudgmentProj.cs:554-558 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/Prismglade/Projectiles/PrismgladeJudgmentProj.cs:182` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) Content/GameModes/BrutalMobs/EvilBiome/Projectiles/MummyWrapProj.cs:99 — Content/GameModes/BrutalMobs/EvilBiome/Projectiles/MummyWrapProj.cs:99-103 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmStrafeBulletProj.cs:67-71 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/EvilBiome/Projectiles/MummyWrapProj.cs:99` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzShardProj.cs:124 — Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzShardProj.cs:124-128 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofBloodClot.cs:70-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzShardProj.cs:124` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzShardProj.cs:121` calls `PrismHue` and `Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofBloodClot.cs:67` does not — after which the two agree again for 3 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 (5 lines × 2) Content/Items/Melee/StormGoddessSpears/AncientStormGoddessSpear.cs:42 — Content/Items/Melee/StormGoddessSpears/AncientStormGoddessSpear.cs:42-46 | Content/Items/Melee/StormGoddessSpears/StormGoddessSpear.cs:45-49 — 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 (5 lines × 2) Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs:134 — Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs:134-138 | Content/Scenarios/OldDuke/Quest/SulfseaTrackerWidgetStyle.cs:150-154 — before extracting anything, compare `Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs` and `Content/Scenarios/OldDuke/Quest/SulfseaTrackerWidgetStyle.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 75 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs:134` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:702 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:702-706 | Content/Scenarios/Kiyume/NPCs/RidgeWalkerYokai.cs:208-212 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:702` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailHead.cs:221 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailHead.cs:221-225 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:247-251 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailHead.cs:221` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:1028 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:1028-1032 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:1042-1046 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs` as WHOLE FILES: this scan already matched 70 separate duplicated blocks between them, totalling at least 835 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:1028` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBladeEngrave.cs:463 — Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBladeEngrave.cs:463-467 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBladeEngrave.cs:528-532 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBladeEngrave.cs:463` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) Content/LegendWeapon/OnikiriLegend/OniSakuraFlights/OniSakuraFlight.cs:900 — Content/LegendWeapon/OnikiriLegend/OniSakuraFlights/OniSakuraFlight.cs:900-904 | Content/Scenarios/Himayo/ToriiShrines/ToriiShrineActor.cs:544-548 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (5 lines × 2) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowDevourOmen.cs:130 — Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowDevourOmen.cs:130-134 | Content/NPCs/FestersandSerpents/Projectiles/FssCascadeDrop.cs:100-104 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowDevourOmen.cs:130` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemSunCore.cs:272 — Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemSunCore.cs:272-276 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Rendering/SkeletronRenderHelper.cs:498-502 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemSunCore.cs:272` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (5 lines × 2) Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordOrbProj.cs:334 — Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordOrbProj.cs:334-338 | Content/Scenarios/Dungeonworld/NPCs/UndrownedTideWave.cs:171-175 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordOrbProj.cs:334` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (5 lines × 2) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/Arms/PrimeViceStates.cs:94 — Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/Arms/PrimeViceStates.cs:94-98 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/Arms/PrimeViceStates.cs:513-517 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/Arms/PrimeViceStates.cs:94` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/States/WofMawVortexState.cs:116 — Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/States/WofMawVortexState.cs:116-120 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/States/WofTongueGrabState.cs:208-212 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/States/WofMawVortexState.cs:116` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) Content/Scenarios/Kiyume/NPCs/FuneralCortegeYokai.cs:1225 — Content/Scenarios/Kiyume/NPCs/FuneralCortegeYokai.cs:1225-1229 | Content/Scenarios/Kiyume/NPCs/LanternGuideYokai.cs:610-614 — 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 (5 lines × 2) Content/Scenarios/OldNet/Tiles/OldNetCacheTile.cs:103 — Content/Scenarios/OldNet/Tiles/OldNetCacheTile.cs:103-107 | Content/Scenarios/OldNet/Tiles/OldNetLedgerDockTile.cs:90-94 — before extracting anything, compare `Content/Scenarios/OldNet/Tiles/OldNetCacheTile.cs` and `Content/Scenarios/OldNet/Tiles/OldNetLedgerDockTile.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 36 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 (5 lines × 2) Content/GameModes/BrutalMobs/Legion/Projectiles/LegionSurfOmen.cs:159 — Content/GameModes/BrutalMobs/Legion/Projectiles/LegionSurfOmen.cs:159-163 | Content/GameModes/BrutalMobs/Ocean/Projectiles/OceanSharkOmen.cs:205-209 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Legion/Projectiles/LegionSurfOmen.cs:159` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • + 440 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×387
  • Duplicated block (6 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:250 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:250-255 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:281-286 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 491 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:250` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) Content/Scenarios/Draedon/DraedonEffect.cs:496 — Content/Scenarios/Draedon/DraedonEffect.cs:496-501 | Content/Scenarios/OldDuke/OldDukeEffect.cs:280-285 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Draedon/DraedonEffect.cs:496` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdChargeOmen.cs:162 — Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdChargeOmen.cs:162-167 | Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdMarksmanOmen.cs:96-101 — 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 × 2) Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkEmberSeedProj.cs:96 — Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkEmberSeedProj.cs:96-101 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkMortarShellProj.cs:98-103 — before extracting anything, compare `Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkEmberSeedProj.cs` and `Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkMortarShellProj.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 61 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkEmberSeedProj.cs:96` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMoonFlare.cs:277 — Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMoonFlare.cs:277-282 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteStarSurge.cs:191-196 — 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 × 2) Content/Items/Magic/SandVortexOfTheDecayedSea.cs:301 — Content/Items/Magic/SandVortexOfTheDecayedSea.cs:301-306 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/SandstormBarrelModule.cs:161-166 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/SandVortexOfTheDecayedSea.cs:301` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) Content/Items/Summon/BloomCallers/BloomCallerSprout.cs:168 — Content/Items/Summon/BloomCallers/BloomCallerSprout.cs:168-173 | Content/Items/Summon/Deepclaws/DeepclawLobster.cs:186-191 — before extracting anything, compare `Content/Items/Summon/BloomCallers/BloomCallerSprout.cs` and `Content/Items/Summon/Deepclaws/DeepclawLobster.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Summon/BloomCallers/BloomCallerSprout.cs:168` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1486 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1486-1491 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:968-973 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 408 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1486` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:979` calls `StartPulse` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1497` does not — after which the two agree again for 3 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 (6 lines × 2) Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSim.cs:257 — Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSim.cs:257-262 | Content/Scenarios/Kiyume/Fog/KiyumeFogSim.cs:380-385 — before extracting anything, compare `Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSim.cs` and `Content/Scenarios/Kiyume/Fog/KiyumeFogSim.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 174 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSim.cs:257` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) Content/Cyberwares/UIs/CyberwareUI.cs:274 — Content/Cyberwares/UIs/CyberwareUI.cs:274-279 | Content/NPCs/Victors/UIs/VictorClinicUI.cs:179-184 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (6 lines × 2) Content/GameModes/BrutalMobs/Ambience/Frostveil/Projectiles/FrostveilGaleWallProj.cs:134 — Content/GameModes/BrutalMobs/Ambience/Frostveil/Projectiles/FrostveilGaleWallProj.cs:134-139 | Content/GameModes/BrutalMobs/Ambience/Frostveil/Projectiles/FrostveilGaleWallProj.cs:388-393 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/Frostveil/Projectiles/FrostveilGaleWallProj.cs:134` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 2) Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclFrankSparkProj.cs:67 — Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclFrankSparkProj.cs:67-72 | Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornArcResidue.cs:48-53 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (6 lines × 2) Content/Items/Accessories/BrutalRelics/Skeletron/SoulbindingArmRender.cs:120 — Content/Items/Accessories/BrutalRelics/Skeletron/SoulbindingArmRender.cs:120-125 | Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadCommandRender.cs:34-39 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/Skeletron/SoulbindingArmRender.cs:120` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) Content/Items/Magic/NeutronWands/NeutronPulsar.cs:336 — Content/Items/Magic/NeutronWands/NeutronPulsar.cs:336-341 | Content/Items/Magic/NeutronWands/NeutronStarquake.cs:139-144 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/NeutronWands/NeutronPulsar.cs:336` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 2) Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:651 — Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:651-656 | Content/Items/Melee/NeutronGlaive.cs:424-429 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:651` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) Content/Items/Melee/DragonsScaleGreatsword.cs:444 — Content/Items/Melee/DragonsScaleGreatsword.cs:444-449 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:443-448 — before extracting anything, compare `Content/Items/Melee/DragonsScaleGreatsword.cs` and `Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 415 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DragonsScaleGreatsword.cs:444` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainSky.cs:154 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainSky.cs:154-159 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainSky.cs:127-132 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainSky.cs` and `Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainSky.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1421 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1421-1426 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1606-1611 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1421` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraPetalWave.cs:126 — Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraPetalWave.cs:126-131 | Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraSporeCloud.cs:94-99 — 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 × 2) Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:452 — Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:452-457 | Content/Scenarios/Kiyume/UI/KiyumeLoadingScreen.cs:409-414 — before extracting anything, compare `Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs` and `Content/Scenarios/Kiyume/UI/KiyumeLoadingScreen.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 214 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:452` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Scenarios/Kiyume/UI/KiyumeLoadingScreen.cs:417` calls `Sin` and `Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:460` 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 (6 lines × 2) Content/Scenarios/Shepel/CybCourses/HackTimeTutorialLead.cs:526 — Content/Scenarios/Shepel/CybCourses/HackTimeTutorialLead.cs:526-531 | Content/Scenarios/Shepel/CybCourses/HackTimeTutorialLead.cs:554-559 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Shepel/CybCourses/HackTimeTutorialLead.cs:526` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) Content/EntrustManager/Styles/DraedonManagerStyle.cs:160 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:160-165 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:148-153 — before extracting anything, compare `Content/EntrustManager/Styles/DraedonManagerStyle.cs` and `Content/EntrustManager/Styles/HotwindManagerStyle.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 442 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/EntrustManager/Styles/DraedonManagerStyle.cs:160` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) Content/GameModes/BrutalMobs/EvilBiome/Projectiles/MummyWrapProj.cs:66 — Content/GameModes/BrutalMobs/EvilBiome/Projectiles/MummyWrapProj.cs:66-71 | Content/GameModes/BrutalMobs/EvilBiome/Projectiles/VileLanceProj.cs:64-69 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/EvilBiome/Projectiles/MummyWrapProj.cs:66` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:366 — Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:366-371 | Content/GameModes/GodSmith/Weapons/Broadswords/GsKatana.cs:85-90 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:366` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) Content/Items/Magic/Elysiums/Disciples/Andrew.cs:41 — Content/Items/Magic/Elysiums/Disciples/Andrew.cs:41-46 | Content/Items/Magic/Elysiums/Disciples/James.cs:40-45 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/Elysiums/Disciples/Andrew.cs:41` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • + 362 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×284
  • Duplicated block (7 lines × 2) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/PrimeCannonAI.cs:77 — Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/PrimeCannonAI.cs:77-83 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/PrimeLaserAI.cs:55-61 — 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 (7 lines × 2) Content/EntrustManager/BaseQuestAcceptUI.cs:290 — Content/EntrustManager/BaseQuestAcceptUI.cs:290-296 | Content/UIs/OverhaulSettings/OverhaulSettingsUI.cs:399-405 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/EntrustManager/BaseQuestAcceptUI.cs:290` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:334 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:334-340 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:400-406 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:334` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) Content/GameModes/BrutalMobs/Ambience/Frostveil/FrostveilPlayer.cs:170 — Content/GameModes/BrutalMobs/Ambience/Frostveil/FrostveilPlayer.cs:170-176 | Content/GameModes/BrutalMobs/Ambience/Verdant/VerdantPlayer.cs:155-161 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/Frostveil/FrostveilPlayer.cs:170` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) Content/GameModes/BrutalMobs/Sky/Projectiles/SkyGaleDiveOmen.cs:101 — Content/GameModes/BrutalMobs/Sky/Projectiles/SkyGaleDiveOmen.cs:101-107 | Content/GameModes/BrutalMobs/Temple/Projectiles/TempleDiveOmen.cs:113-119 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Sky/Projectiles/SkyGaleDiveOmen.cs:101` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) Content/HackTimes/HackTimeRender.cs:130 — Content/HackTimes/HackTimeRender.cs:130-136 | Content/HackTimes/HackTimeRender.cs:151-157 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaReset.cs:656 — Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaReset.cs:656-662 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Restart/CyberRestart.cs:258-264 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (7 lines × 2) Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenChandelierProj.cs:208 — Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenChandelierProj.cs:208-214 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenRoyalChandelierProj.cs:230-236 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenChandelierProj.cs` and `Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenRoyalChandelierProj.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 79 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenChandelierProj.cs:208` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) Content/NPCs/SeaShrimp/States/SeaShrimpCavitationPunchState.cs:86 — Content/NPCs/SeaShrimp/States/SeaShrimpCavitationPunchState.cs:86-92 | Content/NPCs/SeaShrimp/States/SeaShrimpClawJabState.cs:74-80 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/SeaShrimp/States/SeaShrimpCavitationPunchState.cs:86` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/SeaShrimp/States/SeaShrimpClawJabState.cs:71` calls `PlaySound` and `Content/NPCs/SeaShrimp/States/SeaShrimpCavitationPunchState.cs:83` 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) Content/Items/Melee/DestroyersBlade.cs:35 — Content/Items/Melee/DestroyersBlade.cs:35-41 | Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEX.cs:31-37 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (7 lines × 2) Content/Items/Melee/StormGoddessSpears/StormGoddess.cs:659 — Content/Items/Melee/StormGoddessSpears/StormGoddess.cs:659-665 | Content/Items/Melee/StormGoddessSpears/StormGoddess.cs:697-703 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/StormGoddessSpears/StormGoddess.cs:659` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:547 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:547-553 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:852-858 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 491 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:547` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (7 lines × 2) Content/NPCs/BloomsandSerpents/BssBody.cs:185 — Content/NPCs/BloomsandSerpents/BssBody.cs:185-191 | Content/NPCs/FestersandSerpents/FssBody.cs:230-236 — before extracting anything, compare `Content/NPCs/BloomsandSerpents/BssBody.cs` and `Content/NPCs/FestersandSerpents/FssBody.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BloomsandSerpents/BssBody.cs:185` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) Content/NPCs/BloomsandSerpents/BssPortrait.cs:90 — Content/NPCs/BloomsandSerpents/BssPortrait.cs:90-96 | Content/NPCs/FestersandSerpents/Rendering/FssPortrait.cs:103-109 — before extracting anything, compare `Content/NPCs/BloomsandSerpents/BssPortrait.cs` and `Content/NPCs/FestersandSerpents/Rendering/FssPortrait.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 108 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BloomsandSerpents/BssPortrait.cs:90` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistEclipseState.cs:86 — Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistEclipseState.cs:86-92 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistSeekerStarsState.cs:54-60 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistEclipseState.cs:86` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistSeekerStarsState.cs:52` calls `StarCount` and `Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistEclipseState.cs:84` does not — after which the two agree again for 3 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) Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdHammerConeOmen.cs:170 — Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdHammerConeOmen.cs:170-176 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmYetiConeOmen.cs:178-184 — before extracting anything, compare `Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdHammerConeOmen.cs` and `Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmYetiConeOmen.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdHammerConeOmen.cs:170` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) Content/GameModes/BrutalMobs/Legion/Projectiles/LegionSurfOmen.cs:123 — Content/GameModes/BrutalMobs/Legion/Projectiles/LegionSurfOmen.cs:123-129 | Content/GameModes/BrutalMobs/Ocean/Projectiles/OceanSharkOmen.cs:158-164 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Legion/Projectiles/LegionSurfOmen.cs:123` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) Content/Items/Magic/Everdeeps/EverdeepMaelstrom.cs:140 — Content/Items/Magic/Everdeeps/EverdeepMaelstrom.cs:140-146 | Content/Items/Magic/Everdeeps/EverdeepRing.cs:189-195 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/Everdeeps/EverdeepMaelstrom.cs:140` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) Content/Items/Melee/DragonsScaleGreatsword.cs:39 — Content/Items/Melee/DragonsScaleGreatsword.cs:39-45 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:39-45 — before extracting anything, compare `Content/Items/Melee/DragonsScaleGreatsword.cs` and `Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 415 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) Content/Items/Melee/NeutronGlaive.cs:435 — Content/Items/Melee/NeutronGlaive.cs:435-441 | Content/Items/Modifys/RBloodButcherer.cs:478-484 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/NeutronGlaive.cs:435` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBanishParticles.cs:26 — Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBanishParticles.cs:26-32 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreezeParticles.cs:23-29 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBanishParticles.cs:26` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Core/EmpressMotion.cs:129 — Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Core/EmpressMotion.cs:129-135 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Core/EmpressMotion.cs:143-149 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemTelegraph.cs:97 — Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemTelegraph.cs:97-103 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeTelegraphLine.cs:132-138 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemTelegraph.cs` and `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeTelegraphLine.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemTelegraph.cs:97` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistOrreryRenderer.cs:128 — Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistOrreryRenderer.cs:128-134 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistOrreryRenderer.cs:265-271 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistOrreryRenderer.cs:263` calls `SetValue` and `Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistOrreryRenderer.cs:126` 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) Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenChandelierProj.cs:93 — Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenChandelierProj.cs:93-99 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenRoyalChandelierProj.cs:114-120 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenChandelierProj.cs` and `Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenRoyalChandelierProj.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 79 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenChandelierProj.cs:93` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • + 259 more in this group — see findings.md.
D15 · Churn × Complexity Hotspots · Hotspot · ×272
  • Hotspot: Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs:531 — Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs changed 47 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 60 in OnikiriPlayer.PostUpdate at line 531. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-14..2026-10-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-14 04:34:11 +08:00' --until='2026-10-12 04:34:11 +08:00' --full-history --no-merges -- Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:808 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs changed 53 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 39 in CrimsonRendSlash.UpdateBladePose at line 808. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-14..2026-10-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-14 04:34:11 +08:00' --until='2026-10-12 04:34:11 +08:00' --full-history --no-merges -- Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Content/LegendWeapon/OnikiriLegend/UI/OniMeiUI.cs Content/LegendWeapon/OnikiriLegend/UI/OniMeiUI.cs:619 — Content/LegendWeapon/OnikiriLegend/UI/OniMeiUI.cs changed 26 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 61 in OniMeiUI.UpdateInteraction at line 619. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-14..2026-10-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-14 04:34:11 +08:00' --until='2026-10-12 04:34:11 +08:00' --full-history --no-merges -- Content/LegendWeapon/OnikiriLegend/UI/OniMeiUI.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Content/LegendWeapon/OnikiriLegend/OniDismembers/OniSeverStrike.cs Content/LegendWeapon/OnikiriLegend/OniDismembers/OniSeverStrike.cs:936 — Content/LegendWeapon/OnikiriLegend/OniDismembers/OniSeverStrike.cs changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 73 in OniSeverStrike.AcceptAuthoritySnapshot at line 936. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-14..2026-10-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-14 04:34:11 +08:00' --until='2026-10-12 04:34:11 +08:00' --full-history --no-merges -- Content/LegendWeapon/OnikiriLegend/OniDismembers/OniSeverStrike.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPour.cs Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPour.cs:161 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPour.cs changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 77 in KikasaInkPour.AI at line 161. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-14..2026-10-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-14 04:34:11 +08:00' --until='2026-10-12 04:34:11 +08:00' --full-history --no-merges -- Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPour.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Content/LegendWeapon/OnikiriLegend/UI/OniTalismanHud.cs Content/LegendWeapon/OnikiriLegend/UI/OniTalismanHud.cs:232 — Content/LegendWeapon/OnikiriLegend/UI/OniTalismanHud.cs changed 31 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in OniTalismanHud.LogicUpdate at line 232. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-14..2026-10-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-14 04:34:11 +08:00' --until='2026-10-12 04:34:11 +08:00' --full-history --no-merges -- Content/LegendWeapon/OnikiriLegend/UI/OniTalismanHud.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:197 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 50 in KikasaInkDrop.AI at line 197. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-14..2026-10-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-14 04:34:11 +08:00' --until='2026-10-12 04:34:11 +08:00' --full-history --no-merges -- Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaServantPlayer.cs Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaServantPlayer.cs:579 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaServantPlayer.cs changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 60 in KikasaServantPlayer.LoadData at line 579. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-14..2026-10-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-14 04:34:11 +08:00' --until='2026-10-12 04:34:11 +08:00' --full-history --no-merges -- Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaServantPlayer.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Content/LegendWeapon/OnikiriLegend/UI/OniRegisterUI.cs Content/LegendWeapon/OnikiriLegend/UI/OniRegisterUI.cs:353 — Content/LegendWeapon/OnikiriLegend/UI/OniRegisterUI.cs changed 25 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in OniRegisterUI.UpdateInteraction at line 353. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-14..2026-10-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-14 04:34:11 +08:00' --until='2026-10-12 04:34:11 +08:00' --full-history --no-merges -- Content/LegendWeapon/OnikiriLegend/UI/OniRegisterUI.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashStep.cs Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashStep.cs:827 — Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashStep.cs changed 38 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in OniFlashStep.UpdateTailPose at line 827. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-14..2026-10-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-14 04:34:11 +08:00' --until='2026-10-12 04:34:11 +08:00' --full-history --no-merges -- Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashStep.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainPlayer.cs Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainPlayer.cs:378 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainPlayer.cs changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in KikasaDomainPlayer.HandleMutateKey at line 378. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-14..2026-10-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-14 04:34:11 +08:00' --until='2026-10-12 04:34:11 +08:00' --full-history --no-merges -- Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainPlayer.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Content/LegendWeapon/KikasaLegend/UI/Panorama/KikasaPanoramaUI.cs Content/LegendWeapon/KikasaLegend/UI/Panorama/KikasaPanoramaUI.cs:2064 — Content/LegendWeapon/KikasaLegend/UI/Panorama/KikasaPanoramaUI.cs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 58 in KikasaPanoramaUI.DrawHoverTipPanel at line 2064. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-14..2026-10-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-14 04:34:11 +08:00' --until='2026-10-12 04:34:11 +08:00' --full-history --no-merges -- Content/LegendWeapon/KikasaLegend/UI/Panorama/KikasaPanoramaUI.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Content/LegendWeapon/KikasaLegend/UI/KikasaHud.cs Content/LegendWeapon/KikasaLegend/UI/KikasaHud.cs:786 — Content/LegendWeapon/KikasaLegend/UI/KikasaHud.cs changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in KikasaHud.DrawTooltipOverlay at line 786. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-14..2026-10-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-14 04:34:11 +08:00' --until='2026-10-12 04:34:11 +08:00' --full-history --no-merges -- Content/LegendWeapon/KikasaLegend/UI/KikasaHud.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistPlanetProj.cs Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistPlanetProj.cs:126 — Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistPlanetProj.cs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 97 in CultistPlanetProj.AI at line 126. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-14..2026-10-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-14 04:34:11 +08:00' --until='2026-10-12 04:34:11 +08:00' --full-history --no-merges -- Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistPlanetProj.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Content/HackTimes/HackTimeNetSync.cs Content/HackTimes/HackTimeNetSync.cs:212 — Content/HackTimes/HackTimeNetSync.cs changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 44 in HackNetworkTarget.TryCapture at line 212. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-14..2026-10-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-14 04:34:11 +08:00' --until='2026-10-12 04:34:11 +08:00' --full-history --no-merges -- Content/HackTimes/HackTimeNetSync.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Content/NPCs/BloomsandSerpents/States/BssHubState.cs Content/NPCs/BloomsandSerpents/States/BssHubState.cs:140 — Content/NPCs/BloomsandSerpents/States/BssHubState.cs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 75 in BssHubState.PickAttack at line 140. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-14..2026-10-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-14 04:34:11 +08:00' --until='2026-10-12 04:34:11 +08:00' --full-history --no-merges -- Content/NPCs/BloomsandSerpents/States/BssHubState.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Content/LegendWeapon/OnikiriLegend/Tutorial/OnikiriTutorialRenderer.cs Content/LegendWeapon/OnikiriLegend/Tutorial/OnikiriTutorialRenderer.cs:376 — Content/LegendWeapon/OnikiriLegend/Tutorial/OnikiriTutorialRenderer.cs changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in OnikiriTutorialRenderer.BuildAndDrawButtons at line 376. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-14..2026-10-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-14 04:34:11 +08:00' --until='2026-10-12 04:34:11 +08:00' --full-history --no-merges -- Content/LegendWeapon/OnikiriLegend/Tutorial/OnikiriTutorialRenderer.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Content/LegendWeapon/KikasaLegend/UI/KikasaHudLead.cs Content/LegendWeapon/KikasaLegend/UI/KikasaHudLead.cs:549 — Content/LegendWeapon/KikasaLegend/UI/KikasaHudLead.cs changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in KikasaHudLead.DrawOverlay at line 549. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-14..2026-10-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-14 04:34:11 +08:00' --until='2026-10-12 04:34:11 +08:00' --full-history --no-merges -- Content/LegendWeapon/KikasaLegend/UI/KikasaHudLead.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:327 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in KikasaRainUmbrella.AI at line 327. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-14..2026-10-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-14 04:34:11 +08:00' --until='2026-10-12 04:34:11 +08:00' --full-history --no-merges -- Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Content/Wraiths/Runtime/WraithPlayer.cs Content/Wraiths/Runtime/WraithPlayer.cs:546 — Content/Wraiths/Runtime/WraithPlayer.cs changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in WraithPlayer.LoadData at line 546. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-14..2026-10-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-14 04:34:11 +08:00' --until='2026-10-12 04:34:11 +08:00' --full-history --no-merges -- Content/Wraiths/Runtime/WraithPlayer.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Content/NPCs/BloomsandSerpents/BssHead.cs Content/NPCs/BloomsandSerpents/BssHead.cs:272 — Content/NPCs/BloomsandSerpents/BssHead.cs changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in BssHead.AI at line 272. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-14..2026-10-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-14 04:34:11 +08:00' --until='2026-10-12 04:34:11 +08:00' --full-history --no-merges -- Content/NPCs/BloomsandSerpents/BssHead.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamHound.cs Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamHound.cs:185 — Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamHound.cs changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in KikasaDreamHound.AI at line 185. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-14..2026-10-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-14 04:34:11 +08:00' --until='2026-10-12 04:34:11 +08:00' --full-history --no-merges -- Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamHound.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1040 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 62 in KikasaGunServant.UpdateGuns at line 1040. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-14..2026-10-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-14 04:34:11 +08:00' --until='2026-10-12 04:34:11 +08:00' --full-history --no-merges -- Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendParticles.cs Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendParticles.cs:269 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendParticles.cs changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in PRT_CrimsonBloodStain.TryEnterStuck at line 269. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-14..2026-10-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-14 04:34:11 +08:00' --until='2026-10-12 04:34:11 +08:00' --full-history --no-merges -- Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendParticles.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordCoreAI.cs Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordCoreAI.cs:185 — Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordCoreAI.cs changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in MoonLordCoreAI.EvaluateGlobalTransitions at line 185. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-14..2026-10-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-14 04:34:11 +08:00' --until='2026-10-12 04:34:11 +08:00' --full-history --no-merges -- Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordCoreAI.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • + 247 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×238
  • Duplicated block (8 lines × 2) Content/LegendWeapon/HalibutLegend/FishSkills/FishBat.cs:602 — Content/LegendWeapon/HalibutLegend/FishSkills/FishBat.cs:602-609 | Content/LegendWeapon/HalibutLegend/FishSkills/FishSwarm.cs:783-790 — 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 (8 lines × 2) Content/LegendWeapon/HalibutLegend/FishSkills/FishBat.cs:631 — Content/LegendWeapon/HalibutLegend/FishSkills/FishBat.cs:631-638 | Content/LegendWeapon/HalibutLegend/FishSkills/FishSwarm.cs:819-826 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishBat.cs:631` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) Content/GameModes/GodSmith/Prefixes/Accessory/GodSmithSwiftFootEndow.cs:130 — Content/GameModes/GodSmith/Prefixes/Accessory/GodSmithSwiftFootEndow.cs:130-137 | Content/GameModes/GodSmith/Prefixes/Speed/GodSmithAfterimageEndow.cs:109-116 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Prefixes/Accessory/GodSmithSwiftFootEndow.cs:130` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) Content/HackTimes/Chips/HackChipGlyph.cs:91 — Content/HackTimes/Chips/HackChipGlyph.cs:91-98 | Content/Industrials/ElectricPowers/MiningMachines/MiningModuleGlyph.cs:86-93 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/HackTimes/Chips/HackChipGlyph.cs:91` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) Content/Items/Melee/Abyssrends/AbyssrendFX.cs:145 — Content/Items/Melee/Abyssrends/AbyssrendFX.cs:145-152 | Content/NPCs/SeaShrimp/Rendering/SeaShrimpVFX.cs:63-70 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (8 lines × 2) Content/Items/Ranged/Thornstrings/ThornstringHeld.cs:130 — Content/Items/Ranged/Thornstrings/ThornstringHeld.cs:130-137 | Content/Items/Ranged/Undertows/UndertowHeld.cs:137-144 — before extracting anything, compare `Content/Items/Ranged/Thornstrings/ThornstringHeld.cs` and `Content/Items/Ranged/Undertows/UndertowHeld.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 177 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Ranged/Thornstrings/ThornstringHeld.cs:130` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:280 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:280-287 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:393-400 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:280` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) Content/EntrustManager/Styles/ForestManagerStyle.cs:619 — Content/EntrustManager/Styles/ForestManagerStyle.cs:619-626 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:615-622 — before extracting anything, compare `Content/EntrustManager/Styles/ForestManagerStyle.cs` and `Content/EntrustManager/Styles/HotwindManagerStyle.cs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 398 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/EntrustManager/Styles/ForestManagerStyle.cs:619` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) Content/GameModes/BrutalMobs/Ambience/Rimehollow/RimehollowDirector.cs:228 — Content/GameModes/BrutalMobs/Ambience/Rimehollow/RimehollowDirector.cs:228-235 | Content/GameModes/BrutalMobs/Ambience/Verdant/VerdantAmbience.cs:90-97 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/Rimehollow/RimehollowDirector.cs:228` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaBurst.cs:323 — Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaBurst.cs:323-330 | Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraSporeCloud.cs:84-91 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (8 lines × 2) Content/Items/Melee/Arbiters/Arbiter.cs:453 — Content/Items/Melee/Arbiters/Arbiter.cs:453-460 | Content/Items/Melee/Cloudwalking.cs:401-408 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Arbiters/Arbiter.cs:453` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) Content/Items/Melee/NeutronGlaive.cs:240 — Content/Items/Melee/NeutronGlaive.cs:240-247 | Content/Items/Modifys/RBloodButcherer.cs:228-235 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/NeutronGlaive.cs:240` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) Content/Cyberwares/Implementation/SelfHackCrystals/SelfHackCrystalNet.cs:142 — Content/Cyberwares/Implementation/SelfHackCrystals/SelfHackCrystalNet.cs:142-149 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspaceActionNet.cs:251-258 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspaceActionNet.cs:260` calls `Write` and `Content/Cyberwares/Implementation/SelfHackCrystals/SelfHackCrystalNet.cs:151` 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 × 2) Content/GameModes/BrutalMobs/Ambience/Rimehollow/Projectiles/RimehollowIcicleProj.cs:372 — Content/GameModes/BrutalMobs/Ambience/Rimehollow/Projectiles/RimehollowIcicleProj.cs:372-379 | Content/GameModes/BrutalMobs/Ambience/Rimehollow/Projectiles/RimehollowIcicleProj.cs:521-528 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/Rimehollow/Projectiles/RimehollowIcicleProj.cs:372` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (8 lines × 2) Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdCastOmen.cs:237 — Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdCastOmen.cs:237-244 | Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomVineWhipOmen.cs:114-121 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdCastOmen.cs:237` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgStabGlintOmen.cs:104 — Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgStabGlintOmen.cs:104-111 | Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyRavenSwoopOmen.cs:118-125 — before extracting anything, compare `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgStabGlintOmen.cs` and `Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyRavenSwoopOmen.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgStabGlintOmen.cs:104` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipDurendalProj.cs:79 — Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipDurendalProj.cs:79-86 | Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipMorningStarProj.cs: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 both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadCommandRender.cs:178 — Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadCommandRender.cs:178-185 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/HeadPrimeAI.cs:804-811 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (8 lines × 2) Content/Items/Accessories/NinjaCthulsparkBoots.cs:372 — Content/Items/Accessories/NinjaCthulsparkBoots.cs:372-379 | Content/Items/Stones/Granites/GraniteWalkingBoots.cs:194-201 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) Content/Items/BloomArsenal.cs:172 — Content/Items/BloomArsenal.cs:172-179 | Content/NPCs/BloomsandSerpents/Projectiles/BssNeedleProj.cs:37-44 — before extracting anything, compare `Content/Items/BloomArsenal.cs` and `Content/NPCs/BloomsandSerpents/Projectiles/BssNeedleProj.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 98 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/BloomArsenal.cs:172` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) Content/Items/Melee/DivineSourceBlades/DivineSourceBlade.cs:22 — Content/Items/Melee/DivineSourceBlades/DivineSourceBlade.cs:22-29 | Content/Items/Melee/Shatterfangs/Shatterfang.cs:19-26 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DivineSourceBlades/DivineSourceBlade.cs:22` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) Content/Items/Stones/Granites/GraniteThrowingKnife.cs:23 — Content/Items/Stones/Granites/GraniteThrowingKnife.cs:23-30 | Content/Items/Stones/Marbles/MarbleDisc.cs:23-30 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (8 lines × 2) Content/Items/Tools/EncyclopediaofOceanicKnowledge.cs:596 — Content/Items/Tools/EncyclopediaofOceanicKnowledge.cs:596-603 | Content/Items/Tools/TheForgottenTome.cs:460-467 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Tools/EncyclopediaofOceanicKnowledge.cs:596` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) Content/LegendWeapon/HalibutLegend/FishSkills/FishDrizzle.cs:167 — Content/LegendWeapon/HalibutLegend/FishSkills/FishDrizzle.cs:167-174 | Content/LegendWeapon/HalibutLegend/FishSkills/FishSparkling.cs:62-69 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishDrizzle.cs:167` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:420 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:420-427 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:503-510 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:420` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • + 213 more in this group — see findings.md.
D3 · God Classes · FileTooLong · ×178
  • FileTooLong: OnikiriLegend/OnikiriPlayer.cs Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs — FileTooLong — 2171 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1671 over it, 4.34× 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: NPCs/DeepGaolWraith.cs Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs — FileTooLong — 2073 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1573 over it, 4.15× 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: Panorama/KikasaPanoramaUI.cs Content/LegendWeapon/KikasaLegend/UI/Panorama/KikasaPanoramaUI.cs — FileTooLong — 1627 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1127 over it, 3.25× 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: CrimsonRendSlashs/CrimsonRendSlash.cs Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs — FileTooLong — 1288 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 788 over it, 2.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: NPCs/Undrowned.cs Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs — FileTooLong — 1278 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 778 over it, 2.56× 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: OniSlashs/OniSlash.cs Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs — FileTooLong — 1197 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 697 over it, 2.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: KikasaTwins/KikasaTwinsServant.cs Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs — FileTooLong — 1168 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 668 over it, 2.34× 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: KikasaSkeletron/KikasaSkeletronServant.cs Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs — FileTooLong — 1150 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 650 over it, 2.30× 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: CrimsonRendSlashs/CrimsonSweepSlash.cs Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs — FileTooLong — 1125 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 625 over it, 2.25× 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: KikasaPrime/KikasaPrimeServant.cs Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs — FileTooLong — 1114 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 614 over it, 2.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: KikasaGuns/KikasaGunServant.cs Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs — FileTooLong — 1110 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 610 over it, 2.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.
  • FileTooLong: KikasaPlantera/KikasaPlanteraServant.cs Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs — FileTooLong — 1085 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 585 over it, 2.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: KikasaRains/KikasaRainUmbrella.cs Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs — FileTooLong — 1074 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 574 over it, 2.15× 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: HackTimes/HackTimeNetSync.cs Content/HackTimes/HackTimeNetSync.cs — FileTooLong — 1073 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 573 over it, 2.15× 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: Melee/OniMacheteHands.cs Content/Items/Melee/OniMacheteHands.cs — FileTooLong — 1069 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 569 over it, 2.14× 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: KikasaQueenSlime/KikasaQueenSlimeServant.cs Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs — FileTooLong — 1058 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 558 over it, 2.12× 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: KikasaDomains/KikasaDomainPlayer.cs Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainPlayer.cs — FileTooLong — 1050 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 550 over it, 2.10× 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: KikasaZenith/KikasaZenithServant.cs Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs — FileTooLong — 1031 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 531 over it, 2.06× 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: KikasaEater/KikasaEaterServant.cs Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs — FileTooLong — 1018 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 518 over it, 2.04× 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: KikasaMoonLord/KikasaMoonLordServant.cs Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs — FileTooLong — 1017 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 517 over it, 2.03× 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: UI/OniMeiUI.cs Content/LegendWeapon/OnikiriLegend/UI/OniMeiUI.cs — FileTooLong — 1009 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 509 over it, 2.02× 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: KikasaKingSlime/KikasaKingSlimeServant.cs Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs — FileTooLong — 1001 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 501 over it, 2.00× 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: ./CWRRef.cs CWRRef.cs — FileTooLong — 996 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 496 over it, 1.99× 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: OniDismembers/OniSeverStrike.cs Content/LegendWeapon/OnikiriLegend/OniDismembers/OniSeverStrike.cs — FileTooLong — 990 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 490 over it, 1.98× 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: KikasaDeerclops/KikasaDeerclopsServant.cs Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs — FileTooLong — 976 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 476 over it, 1.95× 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.
  • + 153 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×177
  • Duplicated block (9 lines × 2) Content/Scenarios/OldDuke/Campsites/CampsiteLocationFinder.cs:222 — Content/Scenarios/OldDuke/Campsites/CampsiteLocationFinder.cs:222-230 | Content/Scenarios/OldDuke/Campsites/CampsiteLocationFinder.cs:323-331 — 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) Content/Wraiths/Abilities/GhostRains/GhostRainFx.cs:222 — Content/Wraiths/Abilities/GhostRains/GhostRainFx.cs:222-230 | Content/Wraiths/Deaths/Performances/RainSeizurePerformance.cs:396-404 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Wraiths/Abilities/GhostRains/GhostRainFx.cs:222` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:84 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:84-92 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:89-97 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs` as WHOLE FILES: this scan already matched 70 separate duplicated blocks between them, totalling at least 835 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 2) Content/Items/Ranged/SnowQuayMK2.cs:141 — Content/Items/Ranged/SnowQuayMK2.cs:141-149 | Content/Items/Ranged/UniversalFrost.cs:159-167 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Ranged/SnowQuayMK2.cs:141` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) Content/Items/Summon/ElementWhip.cs:102 — Content/Items/Summon/ElementWhip.cs:102-110 | Content/Items/Summon/GhostFireWhip.cs:108-116 — before extracting anything, compare `Content/Items/Summon/ElementWhip.cs` and `Content/Items/Summon/GhostFireWhip.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 61 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Summon/ElementWhip.cs:102` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) Content/Items/Stones/Marbles/MarbleClub.cs:595 — Content/Items/Stones/Marbles/MarbleClub.cs:595-603 | Content/Items/Stones/Marbles/MarbleHuntingKnife.cs:412-420 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Stones/Marbles/MarbleClub.cs:595` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeSlash.cs:175 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeSlash.cs:175-183 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithSlash.cs:190-198 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeSlash.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithSlash.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithSlash.cs:189` calls `Size` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeSlash.cs:174` does not — after which the two agree again for 3 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 × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:303 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:303-311 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:298-306 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs` as WHOLE FILES: this scan already matched 75 separate duplicated blocks between them, totalling at least 932 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:303` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (9 lines × 2) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismDashingState.cs:46 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismDashingState.cs:46-54 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismPhase2DashingState.cs:54-62 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismDashingState.cs` and `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismPhase2DashingState.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 45 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismDashingState.cs:46` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismPhase2DashingState.cs:51` calls `SpazmatismSoloRageState` and `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismDashingState.cs:44` 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 × 2) Content/Scenarios/Draedon/Quest/DeploySignaltowers/DeploySignaltowerRender.cs:532 — Content/Scenarios/Draedon/Quest/DeploySignaltowers/DeploySignaltowerRender.cs:532-540 | Content/Scenarios/Draedon/Quest/DeploySignaltowers/DeploySignaltowerRender.cs:888-896 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Draedon/Quest/DeploySignaltowers/DeploySignaltowerRender.cs:532` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) Content/UIs/UIEffect/FlameWispPRT.cs:18 — Content/UIs/UIEffect/FlameWispPRT.cs:18-26 | Content/UIs/UIEffect/FlameWispPRT.cs:59-67 — 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) Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserMarkLine.cs:151 — Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserMarkLine.cs:151-159 | Content/GameModes/BrutalMobs/NightPack/Projectiles/NightDiveOmen.cs:106-114 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserMarkLine.cs:151` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) Content/Industrials/ElectricPowers/HealingStations/HealStationTP.cs:85 — Content/Industrials/ElectricPowers/HealingStations/HealStationTP.cs:85-93 | Content/Industrials/ElectricPowers/Suppressors/PacifierTowerTP.cs:103-111 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/HealingStations/HealStationTP.cs:85` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) Content/Industrials/ElectricPowers/Sensors/SensorTP.cs:245 — Content/Industrials/ElectricPowers/Sensors/SensorTP.cs:245-253 | Content/Industrials/ElectricPowers/WireInterfaces/WireInterfaceTP.cs:114-122 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 2) Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFistProj.cs:377 — Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFistProj.cs:377-385 | Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFistProj.cs:537-545 — 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) Content/Items/Magic/Pandemoniums/PandemoniumBlastWave.cs:16 — Content/Items/Magic/Pandemoniums/PandemoniumBlastWave.cs:16-24 | Content/Items/Magic/Pandemoniums/PandemoniumLightning.cs:28-36 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/Pandemoniums/PandemoniumBlastWave.cs:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) Content/Items/Melee/Arbiters/ArbiterManifestationSystem.cs:515 — Content/Items/Melee/Arbiters/ArbiterManifestationSystem.cs:515-523 | Content/Items/Melee/WeaverGrievanceses/WGManifestationSystem.cs:505-513 — before extracting anything, compare `Content/Items/Melee/Arbiters/ArbiterManifestationSystem.cs` and `Content/Items/Melee/WeaverGrievanceses/WGManifestationSystem.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 2) Content/Items/Melee/CommandersChainsaw.cs:19 — Content/Items/Melee/CommandersChainsaw.cs:19-27 | Content/Items/Melee/CommandersChainsaw.cs:48-56 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/CommandersChainsaw.cs:19` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) Content/Items/Melee/Shatterfangs/ShatterfangFX.cs:128 — Content/Items/Melee/Shatterfangs/ShatterfangFX.cs:128-136 | Content/Items/Modifys/RBloodButcherer.cs:616-624 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Shatterfangs/ShatterfangFX.cs:128` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:556 — Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:556-564 | Content/Items/Modifys/RBloodButcherer.cs:499-507 — before extracting anything, compare `Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs` and `Content/Items/Modifys/RBloodButcherer.cs` as WHOLE FILES: this scan already matched 36 separate duplicated blocks between them, totalling at least 458 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:556` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) Content/Items/Ranged/Thornstrings/ThornstringHeld.cs:264 — Content/Items/Ranged/Thornstrings/ThornstringHeld.cs:264-272 | Content/Items/Ranged/Undertows/UndertowHeld.cs:270-278 — before extracting anything, compare `Content/Items/Ranged/Thornstrings/ThornstringHeld.cs` and `Content/Items/Ranged/Undertows/UndertowHeld.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 177 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Ranged/Thornstrings/ThornstringHeld.cs:264` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (9 lines × 2) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:219 — Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:219-227 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaReset.cs:248-256 — before extracting anything, compare `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs` and `Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaReset.cs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 2) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:781 — Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:781-789 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaReset.cs:762-770 — before extracting anything, compare `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs` and `Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaReset.cs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:781` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamHound.cs:1060 — Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamHound.cs:1060-1068 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1407-1415 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (9 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:465 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:465-473 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:706-714 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:465` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • + 152 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×169
  • Duplicated block (10 lines × 2) Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs:326 — Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs:326-335 | Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs:397-406 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs:326` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerSeizeHandProj.cs:265 — Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerSeizeHandProj.cs:265-274 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerShadowHandProj.cs:174-183 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerSeizeHandProj.cs:265` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:260 — Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:260-269 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowBurrowAmbushState.cs:222-231 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs` and `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowBurrowAmbushState.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 70 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:260` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `context` to `DestroyerStateContext` in one and `EowStateContext` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (10 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressPetal.cs:89 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressPetal.cs:89-98 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressRibbon.cs:126-135 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressPetal.cs:89` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) Content/Items/Summon/ElementWhip.cs:138 — Content/Items/Summon/ElementWhip.cs:138-147 | Content/Items/Summon/GhostFireWhip.cs:132-141 — before extracting anything, compare `Content/Items/Summon/ElementWhip.cs` and `Content/Items/Summon/GhostFireWhip.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 61 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Summon/ElementWhip.cs:138` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Summon/ElementWhip.cs:149` calls `Vector2` and `Content/Items/Summon/GhostFireWhip.cs:143` does not — after which the two agree again for 3 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 (10 lines × 2) Content/LegendWeapon/HalibutLegend/FishSkills/FishHarpy.cs:615 — Content/LegendWeapon/HalibutLegend/FishSkills/FishHarpy.cs:615-624 | Content/LegendWeapon/HalibutLegend/FishSkills/FishHarpy.cs:636-645 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishHarpy.cs:615` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/States/EmpressDeathState.cs:82 — Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/States/EmpressDeathState.cs:82-91 | Content/NPCs/BrutalNPCs/BrutalQueenBee/States/QBDeathState.cs:95-104 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/States/EmpressDeathState.cs:82` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note first that the copies are not typed on the same thing: the declarations holding them bind `context` to `EmpressStateContext` in one and `QueenBeeStateContext` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (10 lines × 2) Content/UIs/OverhaulSettings/WorldGenSettingsCategory.cs:465 — Content/UIs/OverhaulSettings/WorldGenSettingsCategory.cs:465-474 | Content/UIs/OverhaulSettings/WorldGenSettingsCategory.cs:487-496 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/UIs/OverhaulSettings/WorldGenSettingsCategory.cs:465` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) Content/GameModes/BrutalMobs/Ambience/Starfall/Projectiles/StarfallAfterburstProj.cs:191 — Content/GameModes/BrutalMobs/Ambience/Starfall/Projectiles/StarfallAfterburstProj.cs:191-200 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandGeyserProj.cs:151-160 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/Starfall/Projectiles/StarfallAfterburstProj.cs:191` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) Content/Items/Ranged/Thornstrings/ThornstringHeld.cs:175 — Content/Items/Ranged/Thornstrings/ThornstringHeld.cs:175-184 | Content/Items/Ranged/Undertows/UndertowHeld.cs:181-190 — before extracting anything, compare `Content/Items/Ranged/Thornstrings/ThornstringHeld.cs` and `Content/Items/Ranged/Undertows/UndertowHeld.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 177 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Ranged/Thornstrings/ThornstringHeld.cs:175` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) Content/Items/Ranged/Thornstrings/ThornstringHeld.cs:197 — Content/Items/Ranged/Thornstrings/ThornstringHeld.cs:197-206 | Content/Items/Ranged/Undertows/UndertowHeld.cs:203-212 — before extracting anything, compare `Content/Items/Ranged/Thornstrings/ThornstringHeld.cs` and `Content/Items/Ranged/Undertows/UndertowHeld.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 177 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Ranged/Thornstrings/ThornstringHeld.cs:197` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs:105 — Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs:105-114 | Content/Scenarios/Kiame/KiameWakeResetRender.cs:103-112 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs` and `Content/Scenarios/Kiame/KiameWakeResetRender.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 168 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1277 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1277-1286 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1676-1685 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs` as WHOLE FILES: this scan already matched 68 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1277` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:543 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:543-552 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:623-632 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:543` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:620` calls `Vector2`, `Configure` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:541` 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 (10 lines × 2) Content/LegendWeapon/OnikiriLegend/OniSakuraFlights/OniSakuraFlight.cs:1084 — Content/LegendWeapon/OnikiriLegend/OniSakuraFlights/OniSakuraFlight.cs:1084-1093 | Content/LegendWeapon/OnikiriLegend/OniZanshinSlashs/OniZanshinSlash.cs:634-643 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/OnikiriLegend/OniSakuraFlights/OniSakuraFlight.cs:1080` calls `Clear`, `AddRange` and `Content/LegendWeapon/OnikiriLegend/OniZanshinSlashs/OniZanshinSlash.cs:630` 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 (10 lines × 2) Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberPixelDecomposeProj.cs:41 — Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberPixelDecomposeProj.cs:41-50 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberReformProj.cs:44-53 — before extracting anything, compare `Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberPixelDecomposeProj.cs` and `Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberReformProj.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 183 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberPixelDecomposeProj.cs:41` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 2) Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocMawDragState.cs:585 — Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocMawDragState.cs:585-594 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocMawFrenzyState.cs:196-205 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocMawDragState.cs:585` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 2) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerSoloRageState.cs:67 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerSoloRageState.cs:67-76 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismSoloRageState.cs:67-76 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerSoloRageState.cs:67` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordHandAI.cs:243 — Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordHandAI.cs:243-252 | Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordHeadAI.cs:110-119 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordHandAI.cs:243` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Core/WofWallField.cs:106 — Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Core/WofWallField.cs:106-115 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Core/WofWallField.cs:134-143 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Core/WofWallField.cs:106` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) Content/Scenarios/OldNet/NPCs/OldNetSweepEye.cs:261 — Content/Scenarios/OldNet/NPCs/OldNetSweepEye.cs:261-270 | Content/Scenarios/OldNet/NPCs/OldNetTurretICE.cs:196-205 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/OldNet/NPCs/OldNetSweepEye.cs:261` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (10 lines × 2) Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsRallyFieldProj.cs:37 — Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsRallyFieldProj.cs:37-46 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkGeyser.cs:127-136 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsRallyFieldProj.cs:37` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:194 — Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:194-203 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:688-697 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:194` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 2) Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaRender.cs:252 — Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaRender.cs:252-261 | Content/NPCs/BrutalNPCs/BrutalPlantera/Rendering/PlanteraBloomRender.cs:73-82 — before extracting anything, compare `Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaRender.cs` and `Content/NPCs/BrutalNPCs/BrutalPlantera/Rendering/PlanteraBloomRender.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaRender.cs:252` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/NPCs/BrutalNPCs/BrutalPlantera/Rendering/PlanteraBloomRender.cs:83` calls `SetValue` and `Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaRender.cs:262` does not — after which the two agree again for 4 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 (10 lines × 2) Content/Items/Magic/Elysiums/Disciples/James.cs:79 — Content/Items/Magic/Elysiums/Disciples/James.cs:79-88 | Content/Items/Magic/Elysiums/Revelations/CelestialMeteor.cs:35-44 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/Elysiums/Disciples/James.cs:79` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • + 144 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×157
  • Duplicated block (11 lines × 2) Content/HackTimes/Targets/ItemTargetType.cs:27 — Content/HackTimes/Targets/ItemTargetType.cs:27-37 | Content/HackTimes/Targets/ProjectileTargetType.cs:27-37 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/HackTimes/Targets/ItemTargetType.cs:27` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11 lines × 2) Content/Items/Melee/DestroyersBlade.cs:599 — Content/Items/Melee/DestroyersBlade.cs:599-609 | Content/Items/Melee/DestroyersBladeEXs/DestroyersBeamEX.cs:61-71 — before extracting anything, compare `Content/Items/Melee/DestroyersBlade.cs` and `Content/Items/Melee/DestroyersBladeEXs/DestroyersBeamEX.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DestroyersBlade.cs:599` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:833 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:833-843 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1193-1203 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 491 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:833` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) Content/LegendWeapon/OnikiriLegend/OniDismembers/OniDismemberRender.cs:83 — Content/LegendWeapon/OnikiriLegend/OniDismembers/OniDismemberRender.cs:83-93 | Content/LegendWeapon/OnikiriLegend/OniOmokages/OniOmokageRender.cs:130-140 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/OniDismembers/OniDismemberRender.cs:83` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) Content/NPCs/BloomsandSerpents/BssVfx.cs:44 — Content/NPCs/BloomsandSerpents/BssVfx.cs:44-54 | Content/NPCs/FestersandSerpents/FssVfx.cs:57-67 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (11 lines × 2) Content/Items/Magic/Pandemoniums/PandemoniumQSkill.cs:218 — Content/Items/Magic/Pandemoniums/PandemoniumQSkill.cs:218-228 | Content/Items/Magic/Pandemoniums/PandemoniumRSkill.cs:376-386 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/Pandemoniums/PandemoniumQSkill.cs:218` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) Content/Items/Summon/Deepclaws/DeepclawLobster.cs:222 — Content/Items/Summon/Deepclaws/DeepclawLobster.cs:222-232 | Content/Items/Summon/EyekiteStaffs/EyekiteMinion.cs:238-248 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (11 lines × 2) Content/NPCs/BloomsandSerpents/States/BssDespawnState.cs:32 — Content/NPCs/BloomsandSerpents/States/BssDespawnState.cs:32-42 | Content/NPCs/FestersandSerpents/States/FssDespawnState.cs:31-41 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BloomsandSerpents/States/BssDespawnState.cs:32` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/BloomsandSerpents/States/BssDespawnState.cs:30` calls `DeclareJaw` and `Content/NPCs/FestersandSerpents/States/FssDespawnState.cs:29` does not — after which the two agree again for 4 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 × 2) Content/NPCs/FestersandSerpents/States/FssFesterRippleState.cs:100 — Content/NPCs/FestersandSerpents/States/FssFesterRippleState.cs:100-110 | Content/NPCs/FestersandSerpents/States/FssVenomSkimState.cs:100-110 — 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) Content/NPCs/TBUGs/TBUG.cs:237 — Content/NPCs/TBUGs/TBUG.cs:237-247 | Content/NPCs/Victors/Victor.cs:326-336 — before extracting anything, compare `Content/NPCs/TBUGs/TBUG.cs` and `Content/NPCs/Victors/Victor.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 117 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/TBUGs/TBUG.cs:237` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) Content/PRTTypes/PRT_AccretionDiskImpact.cs:60 — Content/PRTTypes/PRT_AccretionDiskImpact.cs:60-70 | Content/PRTTypes/PRT_GammaImpact.cs:83-93 — before extracting anything, compare `Content/PRTTypes/PRT_AccretionDiskImpact.cs` and `Content/PRTTypes/PRT_GammaImpact.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 65 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 × 2) Content/GameModes/BrutalMobs/Graveyard/GraveyardBrutalNPC.cs:320 — Content/GameModes/BrutalMobs/Graveyard/GraveyardBrutalNPC.cs:320-330 | Content/GameModes/BrutalMobs/Graveyard/GraveyardBrutalNPC.cs:474-484 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Graveyard/GraveyardBrutalNPC.cs:320` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (11 lines × 2) Content/Items/Accessories/ArcaneThroneOfEternity.cs:172 — Content/Items/Accessories/ArcaneThroneOfEternity.cs:172-182 | Content/Items/Accessories/ArcaneThroneOfEternity.cs:319-329 — 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) Content/Items/Accessories/BrutalRelics/KingSlime/RoyalGelField.cs:127 — Content/Items/Accessories/BrutalRelics/KingSlime/RoyalGelField.cs:127-137 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSGelPoolProj.cs:80-90 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/KingSlime/RoyalGelField.cs:127` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) Content/Items/Magic/AriaofTheCosmoses/AriaofTheCosmos.cs:44 — Content/Items/Magic/AriaofTheCosmoses/AriaofTheCosmos.cs:44-54 | Content/Items/Magic/Elysiums/Elysium.cs:72-82 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/AriaofTheCosmoses/AriaofTheCosmos.cs:44` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) Content/Items/Melee/Arbiters/ArbiterManifestationRenderer.cs:244 — Content/Items/Melee/Arbiters/ArbiterManifestationRenderer.cs:244-254 | Content/Items/Melee/WeaverGrievanceses/WGMaterializationRenderer.cs:411-421 — before extracting anything, compare `Content/Items/Melee/Arbiters/ArbiterManifestationRenderer.cs` and `Content/Items/Melee/WeaverGrievanceses/WGMaterializationRenderer.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Arbiters/ArbiterManifestationRenderer.cs:244` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) Content/Items/Melee/Arbiters/ArbiterManifestationSystem.cs:335 — Content/Items/Melee/Arbiters/ArbiterManifestationSystem.cs:335-345 | Content/Items/Melee/WeaverGrievanceses/WGManifestationSystem.cs:328-338 — before extracting anything, compare `Content/Items/Melee/Arbiters/ArbiterManifestationSystem.cs` and `Content/Items/Melee/WeaverGrievanceses/WGManifestationSystem.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Arbiters/ArbiterManifestationSystem.cs:335` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) Content/Items/Melee/DivineSourceBlades/DivineSourceWaveProjectile.cs:372 — Content/Items/Melee/DivineSourceBlades/DivineSourceWaveProjectile.cs:372-382 | Content/Items/Melee/NeutronGlaive.cs:1054-1064 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DivineSourceBlades/DivineSourceWaveProjectile.cs:372` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11 lines × 2) Content/Items/Melee/EnergySword.cs:29 — Content/Items/Melee/EnergySword.cs:29-39 | Content/Items/Melee/NeutronGlaive.cs:40-50 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/EnergySword.cs:29` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) Content/Items/Melee/NeutronGlaive.cs:94 — Content/Items/Melee/NeutronGlaive.cs:94-104 | Content/Items/Melee/RebelBlade.cs:101-111 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/NeutronGlaive.cs:94` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11 lines × 2) Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:802 — Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:802-812 | Content/Items/Modifys/RBloodButcherer.cs:784-794 — before extracting anything, compare `Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs` and `Content/Items/Modifys/RBloodButcherer.cs` as WHOLE FILES: this scan already matched 36 separate duplicated blocks between them, totalling at least 458 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:802` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:815` calls `NextVector2Circular` and `Content/Items/Modifys/RBloodButcherer.cs:797` 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 × 2) Content/LegendWeapon/HalibutLegend/FishSkills/FishDirt.cs:302 — Content/LegendWeapon/HalibutLegend/FishSkills/FishDirt.cs:302-312 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDirt.cs:366-376 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishDirt.cs:302` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) Content/LegendWeapon/HalibutLegend/FishSkills/FishDrizzle.cs:256 — Content/LegendWeapon/HalibutLegend/FishSkills/FishDrizzle.cs:256-266 | Content/LegendWeapon/HalibutLegend/FishSkills/FishSparkling.cs:158-168 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishDrizzle.cs:256` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainRender.cs:79 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainRender.cs:79-89 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainRender.cs:62-72 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (11 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1088 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1088-1098 | Content/LegendWeapon/KikasaLegend/KikasaVaults/KikasaLakeFX.cs:635-645 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • + 132 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×141
  • Edited copy of a member (11 corresponding lines) Content/EntrustManager/Styles/DraedonManagerStyle.cs:234 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:234-244 | Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:733-744 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidPool.cs:122 — Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidPool.cs:122-132 | Content/NPCs/FestersandSerpents/Projectiles/FssIchorPool.cs:242-252 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerMotionFX.cs:176 — Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerMotionFX.cs:176-188 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Rendering/EowMotionFX.cs:184-194 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Barrel/CumulusBarrelModule.cs:34 — Content/LegendWeapon/SHPCLegend/Modules/Barrel/CumulusBarrelModule.cs:34-47 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/SandstormBarrelModule.cs:34-44 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Content/EntrustManager/Styles/ForestManagerStyle.cs:207 — Content/EntrustManager/Styles/ForestManagerStyle.cs:207-217 | Content/QuestLogs/Styles/ForestQuestLogStyle.cs:684-696 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberChargeOrbProj.cs:477 — Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberChargeOrbProj.cs:477-494 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberPrismLaserProj.cs:294-304 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Optic/ZoomOpticModule.cs:28 — Content/LegendWeapon/SHPCLegend/Modules/Optic/ZoomOpticModule.cs:28-38 | Content/LegendWeapon/SHPCLegend/Modules/Optic/ZoomOpticModule.cs:40-52 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Content/GameModes/GodSmith/Weapons/Spears/GsChlorophytePartisan.cs:103 — Content/GameModes/GodSmith/Weapons/Spears/GsChlorophytePartisan.cs:103-113 | Content/GameModes/GodSmith/Weapons/Spears/GsNorthPole.cs:133-147 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Content/NPCs/BrutalNPCs/BrutalGolem/GolemFreeHeadAI.cs:241 — Content/NPCs/BrutalNPCs/BrutalGolem/GolemFreeHeadAI.cs:241-251 | Content/NPCs/BrutalNPCs/BrutalGolem/GolemHeadAI.cs:158-170 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Content/GameModes/GodSmith/Armors/Reset/GsFrostArmor.cs:40 — Content/GameModes/GodSmith/Armors/Reset/GsFrostArmor.cs:40-53 | Content/GameModes/GodSmith/Armors/Reset/GsMeteorArmor.cs:33-43 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Content/NPCs/BloomsandSerpents/BssClawScript.cs:139 — Content/NPCs/BloomsandSerpents/BssClawScript.cs:139-149 | Content/NPCs/BloomsandSerpents/BssClawScript.cs:155-165 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Content/NPCs/BrutalNPCs/BrutalKingSlime/Rendering/KingSlimeGelFX.cs:258 — Content/NPCs/BrutalNPCs/BrutalKingSlime/Rendering/KingSlimeGelFX.cs:258-269 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Rendering/KingSlimeGelFX.cs:272-282 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Content/Scenarios/OldNet/Tiles/OldNetEchoNodeTile.cs:137 — Content/Scenarios/OldNet/Tiles/OldNetEchoNodeTile.cs:137-147 | Content/Scenarios/OldNet/Tiles/OldNetEncryptedNodeTile.cs:175-188 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Barrel/FrostfernBarrelModule.cs:180 — Content/LegendWeapon/SHPCLegend/Modules/Barrel/FrostfernBarrelModule.cs:180-190 | Content/LegendWeapon/SHPCLegend/Modules/Frame/ArchiveFrameModule.cs:70-80 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Content/NPCs/BloomsandSerpents/BssLegRig.cs:571 — Content/NPCs/BloomsandSerpents/BssLegRig.cs:571-582 | Content/NPCs/FestersandSerpents/FssLegRig.cs:388-398 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Content/GameModes/BrutalMobs/Ambience/Duskhall/DuskhallAmbience.cs:388 — Content/GameModes/BrutalMobs/Ambience/Duskhall/DuskhallAmbience.cs:388-398 | Content/GameModes/BrutalMobs/Ambience/Mireheart/MireheartAmbience.cs:240-258 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishAmanitaVFX.cs:263 — Content/LegendWeapon/HalibutLegend/FishSkills/FishAmanitaVFX.cs:263-275 | Content/LegendWeapon/HalibutLegend/FishSkills/FishAmanitaVFX.cs:277-287 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Barrel/MoondewBarrelModule.cs:95 — Content/LegendWeapon/SHPCLegend/Modules/Barrel/MoondewBarrelModule.cs:95-105 | Content/LegendWeapon/SHPCLegend/Modules/Power/PlasmaInjectorModule.cs:135-146 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:258 — Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:258-268 | Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:227-238 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Content/NPCs/BloomsandSerpents/BssJawDraw.cs:69 — Content/NPCs/BloomsandSerpents/BssJawDraw.cs:69-80 | Content/NPCs/BloomsandSerpents/BssJawDraw.cs:82-92 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendCleave.cs:385 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendCleave.cs:385-398 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendCleave.cs:401-411 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Content/Items/Accessories/BrutalRelics/Destroyer/ProbeDroneProj.cs:254 — Content/Items/Accessories/BrutalRelics/Destroyer/ProbeDroneProj.cs:254-267 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Core/CultistMotion.cs:134-144 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Content/GameModes/GodSmith/Weapons/Bows/BetsyBowScheme.cs:85 — Content/GameModes/GodSmith/Weapons/Bows/BetsyBowScheme.cs:85-95 | Content/GameModes/GodSmith/Weapons/Bows/TsunamiScheme.cs:132-142 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Content/Items/Ranged/Starships/StarshipComet.cs:138 — Content/Items/Ranged/Starships/StarshipComet.cs:138-149 | Content/Items/Ranged/Starships/StarshipMeteor.cs:108-118 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Content/NPCs/BloomsandSerpents/BssLegRig.cs:347 — Content/NPCs/BloomsandSerpents/BssLegRig.cs:347-357 | Content/NPCs/FestersandSerpents/FssLegRig.cs:216-226 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • + 116 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×136
  • Edited copy of a member (9 corresponding lines) Content/Narrative/Presentation/Skins/Brimstone/BrimstonePanelDraw.cs:30 — Content/Narrative/Presentation/Skins/Brimstone/BrimstonePanelDraw.cs:30-38 | Content/Narrative/Presentation/Skins/StarStream/StarStreamPanelDraw.cs:93-102 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Content/Narrative/Presentation/Skins/Draedon/DraedonPanelDraw.cs:263 — Content/Narrative/Presentation/Skins/Draedon/DraedonPanelDraw.cs:263-279 | Content/Narrative/Presentation/Skins/SHPC/SHPCPanelState.cs:227-244 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Content/LegendWeapon/KikasaLegend/UI/KikasaHudLead.cs:891 — Content/LegendWeapon/KikasaLegend/UI/KikasaHudLead.cs:891-931 | Content/LegendWeapon/KikasaLegend/UI/Panorama/KikasaPanoramaRenderer.cs:270-303 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Content/GameModes/BrutalMobs/EvilBiome/Projectiles/ErosionCloudSeed.cs:100 — Content/GameModes/BrutalMobs/EvilBiome/Projectiles/ErosionCloudSeed.cs:100-108 | Content/GameModes/BrutalMobs/EvilBiome/Projectiles/VileLanceProj.cs:108-116 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Content/EntrustManager/Styles/HotwindManagerStyle.cs:193 — Content/EntrustManager/Styles/HotwindManagerStyle.cs:193-204 | Content/QuestLogs/QuestCompletionEntry.cs:166-174 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:257 — Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:257-267 | Content/Industrials/ElectricPowers/TeleportStations/TeleportStationUI.cs:266-274 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Content/LegendWeapon/HalibutLegend/UI/Atlas/AtlasFishStudyPanel.cs:387 — Content/LegendWeapon/HalibutLegend/UI/Atlas/AtlasFishStudyPanel.cs:387-395 | Content/LegendWeapon/HalibutLegend/UI/Atlas/HalibutAtlas.cs:440-449 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteMoltenGlob.cs:157 — Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteMoltenGlob.cs:157-165 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Projectiles/EocBloodShot.cs:108-117 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Content/Items/Magic/DragonsWord.cs:122 — Content/Items/Magic/DragonsWord.cs:122-130 | Content/Items/Melee/WeaverGrievanceses/WGMaterializationRenderer.cs:399-409 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraFinaleFeedback.cs:34 — Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraFinaleFeedback.cs:34-42 | Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraFinaleFeedback.cs:45-53 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Content/NPCs/BloomsandSerpents/BssClawRig.cs:391 — Content/NPCs/BloomsandSerpents/BssClawRig.cs:391-399 | Content/NPCs/FestersandSerpents/FssClawRig.cs:343-351 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Content/Items/Summon/Deepclaws/DeepclawLobster.cs:169 — Content/Items/Summon/Deepclaws/DeepclawLobster.cs:169-177 | Content/Items/Summon/EyekiteStaffs/EyekiteMinion.cs:155-163 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Content/GameModes/BrutalMobs/Ambience/DuneStorm/Projectiles/DuneStormGustWaveProj.cs:162 — Content/GameModes/BrutalMobs/Ambience/DuneStorm/Projectiles/DuneStormGustWaveProj.cs:162-172 | Content/GameModes/BrutalMobs/Ambience/DuneStorm/Projectiles/DuneStormGustWaveProj.cs:175-183 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Content/EntrustManager/BaseQuestAcceptUI.cs:572 — Content/EntrustManager/BaseQuestAcceptUI.cs:572-580 | Content/UIs/OverhaulSettings/OverhaulSettingsUI.cs:995-1003 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Content/HackTimes/Protocols/CompensationProtocol.cs:204 — Content/HackTimes/Protocols/CompensationProtocol.cs:204-212 | Content/HackTimes/Protocols/MeltdownProtocol.cs:63-74 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspaceRender.cs:438 — Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspaceRender.cs:438-446 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspaceRender.cs:506-514 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishBatVFX.cs:256 — Content/LegendWeapon/HalibutLegend/FishSkills/FishBatVFX.cs:256-264 | Content/PRTTypes/PRT_SHPCHoneyDrop.cs:43-53 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishIchorn.cs:94 — Content/LegendWeapon/HalibutLegend/FishSkills/FishIchorn.cs:94-104 | Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamHound.cs:750-758 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:902 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:902-910 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:902-910 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamHound.cs:336 — Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamHound.cs:336-344 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1135-1143 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Content/NPCs/BrutalNPCs/BrutalDukeFishron/Rendering/FishronMotionFX.cs:37 — Content/NPCs/BrutalNPCs/BrutalDukeFishron/Rendering/FishronMotionFX.cs:37-48 | Content/Wraiths/Deaths/Performances/HandSeizurePerformance.cs:397-405 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Content/GameModes/GodSmith/Armors/Reset/GsCrystalAssassinArmor.cs:97 — Content/GameModes/GodSmith/Armors/Reset/GsCrystalAssassinArmor.cs:97-111 | Content/GameModes/GodSmith/Armors/Reset/GsOreArmorsPreHardmode.cs:380-388 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Content/Items/Summon/StaffoftheDestroyer.cs:378 — Content/Items/Summon/StaffoftheDestroyer.cs:378-386 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeMortarShellProj.cs:148-160 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Optic/PrecisionOpticModule.cs:208 — Content/LegendWeapon/SHPCLegend/Modules/Optic/PrecisionOpticModule.cs:208-216 | Content/LegendWeapon/SHPCLegend/Modules/Stock/LightStockModule.cs:236-247 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Content/Scenarios/Kiyume/Ambience/KiyumeLampEvents.cs:444 — Content/Scenarios/Kiyume/Ambience/KiyumeLampEvents.cs:444-452 | Content/Wraiths/Deaths/Performances/HandSeizurePerformance.cs:407-416 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • + 111 more in this group — see findings.md.
D3 · God Classes · TooManyMethods · ×132
  • TooManyMethods: OnikiriPlayer Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs — TooManyMethods — 2112 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: GodSmithScheme Content/GameModes/GodSmith/Framework/GodSmithScheme.cs — TooManyMethods — 228 significant lines (blank, comment-only and punctuation-only lines excluded), 146 methods. The bar is 30 methods; this is 116 over it, 4.87× 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: CWRRef CWRRef.cs — TooManyMethods — 963 significant lines (blank, comment-only and punctuation-only lines excluded), 119 methods. The bar is 30 methods; this is 89 over it, 3.97× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • TooManyMethods: CyberDomainFreeze Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.Net.cs — TooManyMethods — 1384 significant lines (blank, comment-only and punctuation-only lines excluded), 90 methods, declared across 2 files: DomainFreeze/CyberDomainFreeze.Net.cs (57), DomainFreeze/CyberDomainFreeze.cs (33). The bar is 30 methods; this is 60 over it, 3.00× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • TooManyMethods: OnikiriTutorialPlayer Content/LegendWeapon/OnikiriLegend/Tutorial/OnikiriTutorialPlayer.cs — TooManyMethods — 907 significant lines (blank, comment-only and punctuation-only lines excluded), 78 methods. The bar is 30 methods; this is 48 over it, 2.60× 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: DeepGaolWraith Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs — TooManyMethods — 1690 significant lines (blank, comment-only and punctuation-only lines excluded), 75 methods. The bar is 30 methods; this is 45 over it, 2.50× 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: CrimsonRendSlash Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs — TooManyMethods — 1238 significant lines (blank, comment-only and punctuation-only lines excluded), 69 methods. The bar is 30 methods; this is 39 over it, 2.30× 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: CyberBanish Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBanish.cs — TooManyMethods — 815 significant lines (blank, comment-only and punctuation-only lines excluded), 63 methods, declared across 2 files: Banish/CyberBanish.cs (35), Banish/CyberBanish.Net.cs (28). The bar is 30 methods; this is 33 over it, 2.10× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • TooManyMethods: Undrowned Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs — TooManyMethods — 1264 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: OniSlash Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs — TooManyMethods — 1147 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: KikasaTwinsServant Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs — TooManyMethods — 1155 significant lines (blank, comment-only and punctuation-only lines excluded), 59 methods. The bar is 30 methods; this is 29 over it, 1.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: KikasaGunServant Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs — TooManyMethods — 1095 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: KikasaDomainPlayer Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainPlayer.cs — TooManyMethods — 1025 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: KikasaZenithServant Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs — TooManyMethods — 1015 significant lines (blank, comment-only and punctuation-only lines excluded), 57 methods. The bar is 30 methods; this is 27 over it, 1.90× 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: KikasaPrimeServant Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs — TooManyMethods — 1101 significant lines (blank, comment-only and punctuation-only lines excluded), 55 methods. The bar is 30 methods; this is 25 over it, 1.83× 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: CrimsonSweepSlash Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs — TooManyMethods — 1081 significant lines (blank, comment-only and punctuation-only lines excluded), 55 methods. The bar is 30 methods; this is 25 over it, 1.83× 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: KikasaQueenSlimeServant Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs — TooManyMethods — 1046 significant lines (blank, comment-only and punctuation-only lines excluded), 55 methods. The bar is 30 methods; this is 25 over it, 1.83× 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: KikasaPanoramaUI Content/LegendWeapon/KikasaLegend/UI/Panorama/KikasaPanoramaUI.cs — TooManyMethods — 1588 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: KikasaSkeletronServant Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs — TooManyMethods — 1137 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: KikasaPlanteraServant Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs — TooManyMethods — 1072 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: ChronicleQuestLogStyle Content/QuestLogs/Styles/Chronicle/ChronicleQuestLogStyle.cs — TooManyMethods — 547 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: OniSeverStrike Content/LegendWeapon/OnikiriLegend/OniDismembers/OniSeverStrike.cs — TooManyMethods — 961 significant lines (blank, comment-only and punctuation-only lines excluded), 51 methods. The bar is 30 methods; this is 21 over it, 1.70× 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: LegionNPC Content/GameModes/BrutalMobs/Legion/LegionNPC.cs — TooManyMethods — 824 significant lines (blank, comment-only and punctuation-only lines excluded), 51 methods. The bar is 30 methods; this is 21 over it, 1.70× 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: ItemPipelineTP Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs — TooManyMethods — 688 significant lines (blank, comment-only and punctuation-only lines excluded), 51 methods. The bar is 30 methods; this is 21 over it, 1.70× 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: RAMPlayer Content/RAMSystems/RAMPlayer.cs — TooManyMethods — 471 significant lines (blank, comment-only and punctuation-only lines excluded), 51 methods. The bar is 30 methods; this is 21 over it, 1.70× 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.
  • + 107 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×126
  • Edited copy of a member (12 corresponding lines) Content/EntrustManager/BaseQuestAcceptUI.cs:557 — Content/EntrustManager/BaseQuestAcceptUI.cs:557-570 | Content/UIs/OverhaulSettings/OverhaulSettingsUI.cs:982-993 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:255 — Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:255-269 | Content/Scenarios/Kiyume/UI/KiyumeLoadingScreen.cs:162-173 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Content/NPCs/SeaShrimp/Projectiles/SeaShrimpLeapVortex.cs:157 — Content/NPCs/SeaShrimp/Projectiles/SeaShrimpLeapVortex.cs:157-168 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpVortexWall.cs:158-169 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Content/LegendWeapon/SHPCLegend/TrialQuests/SHPCTrackerWidgetStyle.cs:81 — Content/LegendWeapon/SHPCLegend/TrialQuests/SHPCTrackerWidgetStyle.cs:81-92 | Content/Scenarios/SupCal/Quest/BrimstoneTrackerWidgetStyle.cs:82-106 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Content/NPCs/BloomsandSerpents/BssPortrait.cs:243 — Content/NPCs/BloomsandSerpents/BssPortrait.cs:243-254 | Content/NPCs/FestersandSerpents/Rendering/FssPortrait.cs:311-322 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSlashRenderer.cs:264 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSlashRenderer.cs:264-275 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleRenderer.cs:200-213 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Content/HackTimes/Protocols/NpcProtocolHooks.cs:236 — Content/HackTimes/Protocols/NpcProtocolHooks.cs:236-248 | Content/Narrative/Common/BaseRecipeDisplayUI.cs:419-430 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Content/EntrustManager/EntrustStatusEntry.cs:152 — Content/EntrustManager/EntrustStatusEntry.cs:152-164 | Content/HackTimes/HackTimeAccessDeniedEntry.cs:117-128 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Barrel/MoondewBarrelModule.cs:34 — Content/LegendWeapon/SHPCLegend/Modules/Barrel/MoondewBarrelModule.cs:34-45 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/MossboundBarrelModule.cs:41-54 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Optic/PrecisionOpticModule.cs:255 — Content/LegendWeapon/SHPCLegend/Modules/Optic/PrecisionOpticModule.cs:255-266 | Content/LegendWeapon/SHPCLegend/Modules/Optic/SniperOpticModule.cs:634-649 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaBloodColumnFX.cs:51 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaBloodColumnFX.cs:51-62 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaBloodColumnFX.cs:79-90 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Content/Narrative/Common/BaseRecipeDisplayUI.cs:261 — Content/Narrative/Common/BaseRecipeDisplayUI.cs:261-272 | Content/Scenarios/Draedon/Quest/DeploySignaltowers/DeploySignaltowerRender.cs:361-372 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Content/PRTTypes/PRT_ProcIntake.cs:61 — Content/PRTTypes/PRT_ProcIntake.cs:61-72 | Content/PRTTypes/PRT_ProcSpark.cs:66-79 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Content/HackTimes/Protocols/TileConscript.cs:70 — Content/HackTimes/Protocols/TileConscript.cs:70-85 | Content/HackTimes/Protocols/TileDetonate.cs:60-71 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1034 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1034-1045 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1110-1121 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Content/Scenarios/OldNet/NPCs/OldNetICEDirector.cs:425 — Content/Scenarios/OldNet/NPCs/OldNetICEDirector.cs:425-439 | Content/Scenarios/OldNet/NPCs/OldNetICEDirector.cs:494-505 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishIchornVFX.cs:236 — Content/LegendWeapon/HalibutLegend/FishSkills/FishIchornVFX.cs:236-247 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:379-390 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishPengVFX.cs:67 — Content/LegendWeapon/HalibutLegend/FishSkills/FishPengVFX.cs:67-78 | Content/LegendWeapon/HalibutLegend/FishSkills/FishPengVFX.cs:81-92 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Content/EntrustManager/EntrustStatusEntry.cs:184 — Content/EntrustManager/EntrustStatusEntry.cs:184-195 | Content/HackTimes/HackTimeAccessDeniedEntry.cs:130-141 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Content/NPCs/ScrapCommanders/Projectiles/ScrapJunkPile.cs:98 — Content/NPCs/ScrapCommanders/Projectiles/ScrapJunkPile.cs:98-109 | Content/NPCs/ScrapCommanders/Projectiles/ScrapLaserPulse.cs:32-46 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Content/Items/Magic/CommandersStaff.cs:303 — Content/Items/Magic/CommandersStaff.cs:303-314 | Content/Items/Magic/Elysiums/Serpents/HolySerpent.cs:310-322 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Content/NPCs/SeaShrimp/Projectiles/SeaShrimpSparkBubble.cs:241 — Content/NPCs/SeaShrimp/Projectiles/SeaShrimpSparkBubble.cs:241-253 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpVoltBubble.cs:220-231 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Content/Scenarios/Dungeonworld/UI/DungeonworldLoadingScreen.cs:631 — Content/Scenarios/Dungeonworld/UI/DungeonworldLoadingScreen.cs:631-642 | Content/Scenarios/Hadalworld/UI/HadalworldLoadingScreen.cs:492-503 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Content/HackTimes/HackCostEvaluator.cs:257 — Content/HackTimes/HackCostEvaluator.cs:257-271 | Content/HackTimes/Scannables/NpcScannable.cs:116-127 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Content/Wraiths/Projectiles/HeadlessShadeRig.cs:156 — Content/Wraiths/Projectiles/HeadlessShadeRig.cs:156-167 | Content/Wraiths/Projectiles/HeadlessShadeRig.cs:219-235 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • + 101 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×126
  • Edited copy of a member (10 corresponding lines) Content/Narrative/Presentation/Skins/Brimstone/BrimstonePanelState.cs:246 — Content/Narrative/Presentation/Skins/Brimstone/BrimstonePanelState.cs:246-255 | Content/UIs/UIEffect/EmberPRT.cs:63-74 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:927 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:927-939 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:894-913 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerShockwave.cs:75 — Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerShockwave.cs:75-84 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/TwinsSupernovaBlast.cs:89-105 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Content/EntrustManager/EntrustStatusEntry.cs:250 — Content/EntrustManager/EntrustStatusEntry.cs:250-259 | Content/Scenarios/Kiyume/UI/KiyumeLoadingScreen.cs:311-322 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Content/LegendWeapon/HalibutLegend/UI/HalibutRenderer.cs:162 — Content/LegendWeapon/HalibutLegend/UI/HalibutRenderer.cs:162-171 | Content/LegendWeapon/OnikiriLegend/Tutorial/OnikiriTutorialRenderer.cs:542-551 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Content/Narrative/Presentation/Skins/Kikasa/KikasaPanelDraw.cs:29 — Content/Narrative/Presentation/Skins/Kikasa/KikasaPanelDraw.cs:29-38 | Content/Narrative/Presentation/Skins/Onikiri/OnikiriPanelDraw.cs:28-37 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Content/EntrustManager/Styles/HotwindManagerStyle.cs:182 — Content/EntrustManager/Styles/HotwindManagerStyle.cs:182-191 | Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:115-128 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Barrel/HiveBarrelModule.cs:125 — Content/LegendWeapon/SHPCLegend/Modules/Barrel/HiveBarrelModule.cs:125-134 | Content/LegendWeapon/SHPCLegend/Modules/Power/HighVoltageCoreModule.cs:209-218 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Content/NPCs/BloomsandSerpents/BssLegRig.cs:324 — Content/NPCs/BloomsandSerpents/BssLegRig.cs:324-333 | Content/NPCs/FestersandSerpents/FssLegRig.cs:196-205 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Content/GameModes/BrutalMobs/Ambience/Bloodveil/BloodveilAmbience.cs:83 — Content/GameModes/BrutalMobs/Ambience/Bloodveil/BloodveilAmbience.cs:83-97 | Content/GameModes/BrutalMobs/Ambience/Woodsong/WoodsongAmbience.cs:399-408 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Content/Narrative/Presentation/Skins/Brimstone/BrimstoneChoiceSkin.cs:91 — Content/Narrative/Presentation/Skins/Brimstone/BrimstoneChoiceSkin.cs:91-115 | Content/Narrative/Presentation/Skins/Sea/SeaChoiceSkin.cs:42-51 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Content/Scenarios/Shenyo/Gifts/ShenyoEvilBossGift.cs:31 — Content/Scenarios/Shenyo/Gifts/ShenyoEvilBossGift.cs:31-40 | Content/Scenarios/Shenyo/Gifts/ShenyoQueenBeeOrDeerclopsGift.cs:31-40 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Content/EntrustManager/BaseQuestAcceptUI.cs:594 — Content/EntrustManager/BaseQuestAcceptUI.cs:594-603 | Content/UIs/OverhaulSettings/OverhaulSettingsUI.cs:1018-1031 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Content/Items/Accessories/BrutalRelics/EyeOfCthulhu/BloodfogIrisFX.cs:198 — Content/Items/Accessories/BrutalRelics/EyeOfCthulhu/BloodfogIrisFX.cs:198-208 | Content/Items/Accessories/BrutalRelics/EyeOfCthulhu/BloodfogIrisFX.cs:217-226 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Content/Narrative/Presentation/Skins/Sulfsea/SulfseaDialogueSkin.cs:33 — Content/Narrative/Presentation/Skins/Sulfsea/SulfseaDialogueSkin.cs:33-42 | Content/Narrative/Presentation/Skins/Tzeentch/TzeentchDialogueSkin.cs:33-47 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Content/Industrials/ElectricPowers/Sensors/SensorTP.cs:354 — Content/Industrials/ElectricPowers/Sensors/SensorTP.cs:354-363 | Content/Industrials/ElectricPowers/Sensors/SensorUI.cs:421-430 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Content/Items/Accessories/BrutalRelics/EyeOfCthulhu/BloodfogIrisFX.cs:49 — Content/Items/Accessories/BrutalRelics/EyeOfCthulhu/BloodfogIrisFX.cs:49-58 | Content/Items/Magic/Eyetooths/EyetoothVFX.cs:152-163 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Content/Buffs/AbyssalPressure.cs:21 — Content/Buffs/AbyssalPressure.cs:21-32 | Content/Buffs/MarblePetrify.cs:24-33 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Content/EntrustManager/BaseManagerStyle.cs:254 — Content/EntrustManager/BaseManagerStyle.cs:254-263 | Content/HackTimes/HackTimeAccessDeniedEntry.cs:228-240 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Content/PRTTypes/PRT_LampeaterEmber.cs:62 — Content/PRTTypes/PRT_LampeaterEmber.cs:62-71 | Content/PRTTypes/PRT_LampeaterLightMote.cs:69-79 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Content/Items/Magic/TomeofFungalDecay.cs:132 — Content/Items/Magic/TomeofFungalDecay.cs:132-141 | Content/Items/Ranged/SporeBubbleBlaster.cs:131-141 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Content/Items/Melee/OniMacheteHands.cs:1128 — Content/Items/Melee/OniMacheteHands.cs:1128-1137 | Content/LegendWeapon/HalibutLegend/FishSkills/Fishotroning.cs:1387-1405 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Content/HackTimes/Protocols/StressInvert.cs:200 — Content/HackTimes/Protocols/StressInvert.cs:200-214 | Content/HackTimes/Protocols/StressInvert.cs:238-247 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Content/Items/Magic/Elysiums/Disciples/Thaddaeus.cs:90 — Content/Items/Magic/Elysiums/Disciples/Thaddaeus.cs:90-100 | Content/Items/Magic/FocusingGrimoire.cs:217-226 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterTP.cs:441 — Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterTP.cs:441-450 | Content/Industrials/Generator/MagmaThermal/MagmaThermalGenerator.cs:251-262 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • + 101 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×125
  • Edited copy of a member (8 corresponding lines) Content/Industrials/Modifys/ChargingStationUI.cs:415 — Content/Industrials/Modifys/ChargingStationUI.cs:415-423 | Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersUIs/OceanRaidersRenderer.cs:213-221 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) Content/LegendWeapon/HalibutLegend/DomainSkills/SeaDomain.cs:429 — Content/LegendWeapon/HalibutLegend/DomainSkills/SeaDomain.cs:429-437 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutDomain.cs:196-203 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) Content/Wraiths/Deaths/Performances/ShadeSeizurePerformance.cs:300 — Content/Wraiths/Deaths/Performances/ShadeSeizurePerformance.cs:300-307 | Content/Wraiths/Projectiles/HeadlessShadeProj.cs:936-950 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordCometProj.cs:108 — Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordCometProj.cs:108-115 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordOrbProj.cs:347-356 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishBloodyManowarVFX.cs:48 — Content/LegendWeapon/HalibutLegend/FishSkills/FishBloodyManowarVFX.cs:48-59 | Content/LegendWeapon/HalibutLegend/FishSkills/FishFallenStarVFX.cs:49-56 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Grip/VampireGripModule.cs:17 — Content/LegendWeapon/SHPCLegend/Modules/Grip/VampireGripModule.cs:17-25 | Content/LegendWeapon/SHPCLegend/Modules/Grip/VampireGripModule.cs:27-34 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) Content/HackTimes/PvP/Protocols/CyberwareOffline.cs:155 — Content/HackTimes/PvP/Protocols/CyberwareOffline.cs:155-165 | Content/HackTimes/PvP/Protocols/GaugePollution.cs:181-188 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaCavitationOrb.cs:154 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaCavitationOrb.cs:154-161 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpCavitationBubble.cs:152-161 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) Content/GameModes/GodSmith/Weapons/Broadswords/GsBreakerBlade.cs:164 — Content/GameModes/GodSmith/Weapons/Broadswords/GsBreakerBlade.cs:164-172 | Content/GameModes/GodSmith/Weapons/Broadswords/GsFetidBaghnakhs.cs:226-233 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) Content/Scenarios/Kiyume/NPCs/ShallowHandsYokai.cs:280 — Content/Scenarios/Kiyume/NPCs/ShallowHandsYokai.cs:280-287 | Content/Scenarios/Kiyume/NPCs/ShallowHandsYokai.cs:289-300 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) Content/Items/Magic/MelodyTheSand.cs:289 — Content/Items/Magic/MelodyTheSand.cs:289-297 | Content/Items/Magic/UnderTheSand.cs:357-364 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) Content/GameModes/GodSmith/Weapons/MagicConduit/GsHeatRay.cs:44 — Content/GameModes/GodSmith/Weapons/MagicConduit/GsHeatRay.cs:44-51 | Content/GameModes/GodSmith/Weapons/MagicConduit/GsMedusaHead.cs:53-60 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) Content/Narrative/Presentation/Skins/Brimstone/BrimstoneDialogueSkin.cs:67 — Content/Narrative/Presentation/Skins/Brimstone/BrimstoneDialogueSkin.cs:67-74 | Content/Narrative/Presentation/Skins/Sea/SeaDialogueSkin.cs:65-72 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetHourglass.cs:340 — Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetHourglass.cs:340-347 | Content/Scenarios/Kiame/KiameWakeResetRender.cs:314-321 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) Content/GameModes/GodSmith/Armors/Reset/GsJungleArmor.cs:33 — Content/GameModes/GodSmith/Armors/Reset/GsJungleArmor.cs:33-40 | Content/GameModes/GodSmith/Armors/Reset/GsPillarArmors.cs:116-123 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) Content/HackTimes/Protocols/DataLeech.cs:135 — Content/HackTimes/Protocols/DataLeech.cs:135-142 | Content/HackTimes/Protocols/LiveCellTap.cs:205-214 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Frame/ResonanceFrameModule.cs:474 — Content/LegendWeapon/SHPCLegend/Modules/Frame/ResonanceFrameModule.cs:474-483 | Content/LegendWeapon/SHPCLegend/Modules/Frame/VolatileFrameModule.cs:567-574 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) Content/Wraiths/Abilities/CrimsonBrides/BrideHallRenderer.cs:310 — Content/Wraiths/Abilities/CrimsonBrides/BrideHallRenderer.cs:310-317 | Content/Wraiths/Deaths/Performances/BrideSeizurePerformance.cs:236-243 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) Content/Industrials/Generator/Hydroelectrics/Hydroelectric.cs:213 — Content/Industrials/Generator/Hydroelectrics/Hydroelectric.cs:213-220 | Content/Industrials/Generator/Hydroelectrics/HydroelectricMK2.cs:240-250 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) Content/Items/Melee/DragonsScaleGreatsword.cs:591 — Content/Items/Melee/DragonsScaleGreatsword.cs:591-598 | Content/Items/Melee/DragonsScaleGreatsword.cs:622-630 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) Content/Narrative/Presentation/Skins/StarStream/StarStreamChoiceSkin.cs:37 — Content/Narrative/Presentation/Skins/StarStream/StarStreamChoiceSkin.cs:37-44 | Content/Narrative/Presentation/Skins/Sulfsea/SulfseaDialogueSkin.cs:58-65 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Frame/MultiCellFrameModule.cs:328 — Content/LegendWeapon/SHPCLegend/Modules/Frame/MultiCellFrameModule.cs:328-335 | Content/LegendWeapon/SHPCLegend/Modules/Grip/EfficientGripModule.cs:494-503 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) Content/PRTTypes/PRT_ToxicBubble.cs:25 — Content/PRTTypes/PRT_ToxicBubble.cs:25-38 | Content/PRTTypes/PRT_ToxicBubble.cs:39-46 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendParticles.cs:930 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendParticles.cs:930-937 | Content/PRTTypes/PRT_Smoke.cs:59-67 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) Content/LegendWeapon/HalibutLegend/UI/SkillWheel/HalibutWheelController.cs:183 — Content/LegendWeapon/HalibutLegend/UI/SkillWheel/HalibutWheelController.cs:183-190 | Content/LegendWeapon/SHPCLegend/UI/DomainWheel/SHPCDomainWheelController.cs:198-206 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • + 100 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×119
  • Edited copy of a member (7 corresponding lines) Content/Narrative/Presentation/Skins/Draedon/DraedonPanelDraw.cs:133 — Content/Narrative/Presentation/Skins/Draedon/DraedonPanelDraw.cs:133-139 | Content/Narrative/Presentation/Skins/StarStream/StarStreamPanelDraw.cs:253-259 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Content/UIs/OverhaulSettings/OverhaulSettingsUI.cs:931 — Content/UIs/OverhaulSettings/OverhaulSettingsUI.cs:931-937 | Content/UIs/OverhaulSettings/WorldGenSettingsCategory.cs:543-549 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Content/EntrustManager/EntrustTrackerWidget.cs:377 — Content/EntrustManager/EntrustTrackerWidget.cs:377-384 | Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:747-753 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Content/NPCs/Modifys/Crabulons/CrabulonBehavior.cs:308 — Content/NPCs/Modifys/Crabulons/CrabulonBehavior.cs:308-314 | Content/NPCs/Modifys/Crabulons/CrabulonNetworking.cs:142-152 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Barrel/CoralReefBarrelModule.cs:185 — Content/LegendWeapon/SHPCLegend/Modules/Barrel/CoralReefBarrelModule.cs:185-191 | Content/NPCs/ScrapCommanders/Projectiles/ScrapFlungTool.cs:85-96 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Content/LegendWeapon/HalibutLegend/DomainSkills/FishTeleport.cs:402 — Content/LegendWeapon/HalibutLegend/DomainSkills/FishTeleport.cs:402-408 | Content/LegendWeapon/HalibutLegend/DomainSkills/RestartFish.cs:473-479 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Content/Items/Ranged/AvalancheM60.cs:418 — Content/Items/Ranged/AvalancheM60.cs:418-426 | Content/LegendWeapon/SHPCLegend/Modules/Power/CryoCoreModule.cs:74-80 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Content/Scenarios/OldDuke/Campsites/CampsitePotActor.cs:121 — Content/Scenarios/OldDuke/Campsites/CampsitePotActor.cs:121-127 | Content/Scenarios/OldDuke/Campsites/CampsitePotActor.cs:129-138 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Content/Narrative/Presentation/Skins/StarStream/StarStreamPanelDraw.cs:10 — Content/Narrative/Presentation/Skins/StarStream/StarStreamPanelDraw.cs:10-18 | Content/Narrative/Presentation/Skins/StarStream/StarStreamPanelDraw.cs:20-26 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Content/LegendWeapon/HalibutLegend/DomainSkills/FishTeleport.cs:394 — Content/LegendWeapon/HalibutLegend/DomainSkills/FishTeleport.cs:394-400 | Content/LegendWeapon/HalibutLegend/DomainSkills/RestartFish.cs:481-488 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Content/Cyberwares/Implementation/SCCA32CRPs/SCCA32CRPPlayer.cs:104 — Content/Cyberwares/Implementation/SCCA32CRPs/SCCA32CRPPlayer.cs:104-110 | Content/Cyberwares/Implementation/SelfHealingSkelents/SelfHealingSkelentPlayer.cs:72-80 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Content/Scenarios/Dungeonworld/Ambience/AmbientEmitters.cs:413 — Content/Scenarios/Dungeonworld/Ambience/AmbientEmitters.cs:413-420 | Content/Scenarios/Dungeonworld/Ambience/DungeonworldSnuff.cs:361-367 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs:120 — Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs:120-126 | Content/Scenarios/Kiame/KiameWakeResetRender.cs:118-124 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Content/Buffs/SoulBurning.cs:13 — Content/Buffs/SoulBurning.cs:13-19 | Content/Buffs/SoulBurning.cs:21-27 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1039 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1039-1045 | Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:1631-1637 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Content/GameModes/GodSmith/Accessories/Defense/GodSmithExpertRelics.cs:153 — Content/GameModes/GodSmith/Accessories/Defense/GodSmithExpertRelics.cs:153-159 | Content/GameModes/GodSmith/Accessories/Offense/GodSmithGloveChain.cs:224-230 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Content/LegendWeapon/HalibutLegend/DomainSkills/SeaDomain.cs:975 — Content/LegendWeapon/HalibutLegend/DomainSkills/SeaDomain.cs:975-981 | Content/LegendWeapon/HalibutLegend/DomainSkills/SeaDomain.cs:1055-1063 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberCascadeNodeProj.cs:142 — Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberCascadeNodeProj.cs:142-148 | Content/LegendWeapon/SHPCLegend/Modules/Power/HighVoltageCoreModule.cs:191-197 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Content/GameModes/GodSmith/Weapons/SummonWhips/Schemes/GsKaleidoscope.cs:32 — Content/GameModes/GodSmith/Weapons/SummonWhips/Schemes/GsKaleidoscope.cs:32-41 | Content/GameModes/GodSmith/Weapons/SummonWhips/Schemes/GsLeatherWhip.cs:62-68 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineTP.cs:454 — Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineTP.cs:454-460 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterTP.cs:691-699 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs:496 — Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs:496-502 | Content/Industrials/ElectricPowers/Lumberjacks/WGGLumberjack.cs:819-825 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaTalismans/KikasaTalismanGlyph.cs:29 — Content/LegendWeapon/KikasaLegend/KikasaTalismans/KikasaTalismanGlyph.cs:29-35 | Content/LegendWeapon/OnikiriLegend/UI/OniMeiGlyph.cs:52-58 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Content/Scenarios/Dungeonworld/Ambience/AmbientPRT.cs:215 — Content/Scenarios/Dungeonworld/Ambience/AmbientPRT.cs:215-222 | Content/Scenarios/Dungeonworld/Ambience/AmbientPRT.cs:476-482 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawWormProj.cs:236 — Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawWormProj.cs:236-242 | Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawWormProj.cs:336-345 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Content/Scenarios/Kiyume/NPCs/MinoFisherYokai.cs:307 — Content/Scenarios/Kiyume/NPCs/MinoFisherYokai.cs:307-313 | Content/Scenarios/Kiyume/NPCs/MinoFisherYokai.cs:315-325 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • + 94 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×114
  • Duplicated block (5 lines × 3) Content/Items/Magic/MelodyTheSand.cs:18 — Content/Items/Magic/MelodyTheSand.cs:18-22 | Content/Items/Magic/SandVortexOfTheDecayedSea.cs:20-24 | Content/Items/Magic/UnderTheSand.cs:19-23 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/MelodyTheSand.cs:18` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 3) Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:753 — Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:753-757 | Content/Items/Modifys/RTerraBlades/RTerraBladeHeld.cs:981-985 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Rendering/KingSlimeGelFX.cs:238-242 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/NPCs/BrutalNPCs/BrutalKingSlime/Rendering/KingSlimeGelFX.cs:244` calls `SetValue`, `GetTransfromMatrix` and `Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:759` 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 (5 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainRender.cs:81 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainRender.cs:81-85 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainRender.cs:64-68 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainRender.cs:191-195 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainRender.cs:186` calls `SetValue` and `Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainRender.cs:60` does not — after which the two agree again for 3 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 (5 lines × 3) Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteRingRender.cs:25 — Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteRingRender.cs:25-29 | Content/Items/Accessories/BrutalRelics/Skeletron/SoulbindingArmRender.cs:121-125 | Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadCommandRender.cs:35-39 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteRingRender.cs:25` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 3) Content/Items/Melee/OniMacheteHands.cs:1497 — Content/Items/Melee/OniMacheteHands.cs:1497-1501 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDemonicHell.cs:280-284 | Content/LegendWeapon/HalibutLegend/FishSkills/FishRock.cs:764-768 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (5 lines × 3) Content/EntrustManager/Styles/DraedonManagerStyle.cs:418 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:418-422 | Content/EntrustManager/Styles/ForestManagerStyle.cs:427-431 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:416-420 — before extracting anything, compare `Content/EntrustManager/Styles/DraedonManagerStyle.cs` and `Content/EntrustManager/Styles/ForestManagerStyle.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 334 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 (5 lines × 3) Content/EntrustManager/Styles/DraedonManagerStyle.cs:666 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:666-670 | Content/EntrustManager/Styles/ForestManagerStyle.cs:689-693 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:677-681 — before extracting anything, compare `Content/EntrustManager/Styles/DraedonManagerStyle.cs` and `Content/EntrustManager/Styles/ForestManagerStyle.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 334 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 3) Content/GameModes/GodSmith/Armors/Reset/GsBeetleArmors.cs:166 — Content/GameModes/GodSmith/Armors/Reset/GsBeetleArmors.cs:166-170 | Content/GameModes/GodSmith/Armors/Reset/GsSpectreArmors.cs:113-117 | Content/GameModes/GodSmith/Armors/Reset/GsTikiArmor.cs:78-82 — before extracting anything, compare `Content/GameModes/GodSmith/Armors/Reset/GsSpectreArmors.cs` and `Content/GameModes/GodSmith/Armors/Reset/GsTikiArmor.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 57 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 (5 lines × 3) Content/GameModes/GodSmith/Armors/Reset/GsPillarArmors.cs:302 — Content/GameModes/GodSmith/Armors/Reset/GsPillarArmors.cs:302-306 | Content/GameModes/GodSmith/Armors/Reset/GsSpectreArmors.cs:113-117 | Content/GameModes/GodSmith/Armors/Reset/GsTikiArmor.cs:78-82 — 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 (5 lines × 3) Content/Items/Melee/OniMacheteHands.cs:1497 — Content/Items/Melee/OniMacheteHands.cs:1497-1501 | Content/LegendWeapon/HalibutLegend/FishSkills/FishMud.cs:778-782 | Content/LegendWeapon/HalibutLegend/FishSkills/FishRock.cs:764-768 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/HalibutLegend/FishSkills/FishMud.cs:785` calls `GetColor`, `Vector2`, `ToTileCoordinates` and `Content/LegendWeapon/HalibutLegend/FishSkills/FishRock.cs:770` does not — after which the two agree again for 3 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 (5 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:82 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:82-86 | Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs:91-95 | Content/Scenarios/Kiame/Overlay/OniRainWorldRender.cs:76-80 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs` and `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 192 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:931 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:931-935 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1559-1563 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:1120-1124 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:931` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 3) Content/GameModes/GodSmith/Armors/Reset/GsFrostArmor.cs:97 — Content/GameModes/GodSmith/Armors/Reset/GsFrostArmor.cs:97-101 | Content/GameModes/GodSmith/Armors/Reset/GsMoltenArmor.cs:87-91 | Content/GameModes/GodSmith/Armors/Reset/GsOreArmorsHardmode.cs:571-575 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/GodSmith/Armors/Reset/GsFrostArmor.cs:94` calls `AI`, `UpdateFallGate` and `Content/GameModes/GodSmith/Armors/Reset/GsMoltenArmor.cs:85` 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 (5 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:233 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:233-237 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistIceShard.cs:179-183 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsHail.cs:151-155 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (5 lines × 3) Content/NPCs/BloomsandSerpents/States/BssBurrowLungeState.cs:313 — Content/NPCs/BloomsandSerpents/States/BssBurrowLungeState.cs:313-317 | Content/NPCs/BloomsandSerpents/States/BssLoopCascadeState.cs:270-274 | Content/NPCs/BloomsandSerpents/States/BssSandSurgeState.cs:245-249 — 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 (5 lines × 3) Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenChandelierProj.cs:141 — Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenChandelierProj.cs:141-145 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenCrystalPrisonProj.cs:159-163 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenRoyalChandelierProj.cs:150-154 — 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 (5 lines × 3) Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenCrystalSpikeProj.cs:249 — Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenCrystalSpikeProj.cs:249-253 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenGelPearlProj.cs:86-90 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofBloodClot.cs:71-75 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (5 lines × 3) Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryWatcher.cs:130 — Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryWatcher.cs:130-134 | Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolBossRoomWatcher.cs:113-117 | Content/Scenarios/Dungeonworld/Gen/BossRooms/ProofingHallWatcher.cs:100-104 — before extracting anything, compare `Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryWatcher.cs` and `Content/Scenarios/Dungeonworld/Gen/BossRooms/ProofingHallWatcher.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 62 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryWatcher.cs:130` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 3) Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:1039 — Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:1039-1043 | Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:1229-1233 | Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:1262-1266 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:1039` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 3) Content/Scenarios/Kiyume/Ambience/KiyumeCrowFlight.cs:347 — Content/Scenarios/Kiyume/Ambience/KiyumeCrowFlight.cs:347-351 | Content/Scenarios/Kiyume/Ambience/KiyumeCrowRoost.cs:500-504 | Content/Scenarios/Kiyume/Fog/KiyumeHoundShade.cs:195-199 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Note first that the copies are not typed on the same thing: the declarations holding them bind `c` to `Crow` in one and `PerchCrow` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Scenarios/Kiyume/Fog/KiyumeHoundShade.cs:193` calls `Sin` and `Content/Scenarios/Kiyume/Ambience/KiyumeCrowFlight.cs:345` does not — after which the two agree again for 3 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 (5 lines × 3) Content/GameModes/GodSmith/Weapons/Bows/Projectiles/GsVolleyBurstProj.cs:90 — Content/GameModes/GodSmith/Weapons/Bows/Projectiles/GsVolleyBurstProj.cs:90-94 | Content/GameModes/GodSmith/Weapons/MagicCataclysm/Projectiles/GsCataclysmRiderBurstProj.cs:94-98 | Content/GameModes/GodSmith/Weapons/SummonSentries/Projectiles/GsSentryBurstProj.cs:81-85 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/Bows/Projectiles/GsVolleyBurstProj.cs:90` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (5 lines × 3) Content/Items/Melee/Arbiters/Arbiter.cs:534 — Content/Items/Melee/Arbiters/Arbiter.cs:534-538 | Content/Items/Melee/Arbiters/Arbiter.cs:777-781 | Content/Items/Melee/Arbiters/Arbiter.cs:790-794 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Arbiters/Arbiter.cs:534` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 3) Content/Items/Melee/DestroyersBlade.cs:278 — Content/Items/Melee/DestroyersBlade.cs:278-282 | Content/Items/Melee/DragonsScaleGreatsword.cs:291-295 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:301-305 — before extracting anything, compare `Content/Items/Melee/DestroyersBlade.cs` and `Content/Items/Melee/DragonsScaleGreatsword.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 419 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 (5 lines × 3) Content/Items/Melee/Heartcarver.cs:1264 — Content/Items/Melee/Heartcarver.cs:1264-1268 | Content/Items/Melee/Heartcarver.cs:1440-1444 | Content/Items/Melee/HeartcarverHeart.cs:215-219 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Heartcarver.cs:1264` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 3) Content/LegendWeapon/SHPCLegend/Modules/Frame/MultiCellFrameModule.cs:379 — Content/LegendWeapon/SHPCLegend/Modules/Frame/MultiCellFrameModule.cs:379-383 | Content/LegendWeapon/SHPCLegend/Modules/Grip/EfficientGripModule.cs:543-547 | Content/LegendWeapon/SHPCLegend/Modules/Stock/ErgonomicStockModule.cs:458-462 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/Modules/Frame/MultiCellFrameModule.cs:379` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • + 89 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×112
  • Duplicated block (12 lines × 2) Content/Scenarios/Dungeonworld/UI/DungeonworldLoadTheme.cs:52 — Content/Scenarios/Dungeonworld/UI/DungeonworldLoadTheme.cs:52-63 | Content/Scenarios/Hadalworld/UI/HadalworldLoadTheme.cs:51-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (12 lines × 2) Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:749 — Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:749-760 | Content/Items/Modifys/RTerraBlades/RTerraBladeHeld.cs:977-988 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:749` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) Content/LegendWeapon/HalibutLegend/FishSkills/FishFallenStar.cs:336 — Content/LegendWeapon/HalibutLegend/FishSkills/FishFallenStar.cs:336-347 | Content/LegendWeapon/HalibutLegend/FishSkills/FishFallenStar.cs:564-575 — 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 × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:272 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:272-283 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:436-447 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:272` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) Content/NPCs/BloomsandSerpents/BssHead.cs:348 — Content/NPCs/BloomsandSerpents/BssHead.cs:348-359 | Content/NPCs/FestersandSerpents/FssHead.cs:301-312 — before extracting anything, compare `Content/NPCs/BloomsandSerpents/BssHead.cs` and `Content/NPCs/FestersandSerpents/FssHead.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 321 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BloomsandSerpents/BssHead.cs:348` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:257 — Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:257-268 | Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:297-308 — 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 × 2) Content/Scenarios/Dungeonworld/NPCs/OverseerDormantRig.cs:261 — Content/Scenarios/Dungeonworld/NPCs/OverseerDormantRig.cs:261-272 | Content/Scenarios/Dungeonworld/NPCs/UndrownedThrone.cs:263-274 — before extracting anything, compare `Content/Scenarios/Dungeonworld/NPCs/OverseerDormantRig.cs` and `Content/Scenarios/Dungeonworld/NPCs/UndrownedThrone.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 73 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/NPCs/OverseerDormantRig.cs:261` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) Content/Industrials/MaterialFlow/LaserEnergyTrans.cs:159 — Content/Industrials/MaterialFlow/LaserEnergyTrans.cs:159-170 | Content/Industrials/MaterialFlow/LaserEnergyTrans.cs:193-204 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/MaterialFlow/LaserEnergyTrans.cs:159` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Rendering/TwinsRenderHelper.cs:317 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Rendering/TwinsRenderHelper.cs:317-328 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Rendering/TwinsRenderHelper.cs:489-500 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Rendering/TwinsRenderHelper.cs:317` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) Content/GameModes/BrutalMobs/Martians/MartiansNPC.cs:628 — Content/GameModes/BrutalMobs/Martians/MartiansNPC.cs:628-639 | Content/GameModes/BrutalMobs/Meteorite/MeteoriteBrutalNPC.cs:165-176 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Martians/MartiansNPC.cs:628` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) Content/GameModes/BrutalMobs/Martians/Projectiles/MrtWrenchProj.cs:165 — Content/GameModes/BrutalMobs/Martians/Projectiles/MrtWrenchProj.cs:165-176 | Content/GameModes/BrutalMobs/NightPack/Projectiles/NightBoneProj.cs:164-175 — before extracting anything, compare `Content/GameModes/BrutalMobs/Martians/Projectiles/MrtWrenchProj.cs` and `Content/GameModes/BrutalMobs/NightPack/Projectiles/NightBoneProj.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Martians/Projectiles/MrtWrenchProj.cs:165` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (12 lines × 2) Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawCorrosionNPC.cs:232 — Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawCorrosionNPC.cs:232-243 | Content/LegendWeapon/KikasaLegend/KikasaWisps/KikasaWispBurnNPC.cs:61-72 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (12 lines × 2) Content/Items/Accessories/JusticeUnveileds/JusticeCrossMark.cs:200 — Content/Items/Accessories/JusticeUnveileds/JusticeCrossMark.cs:200-211 | Content/Items/Magic/Pandemoniums/PandemoniumFirePillar.cs:76-87 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/JusticeUnveileds/JusticeCrossMark.cs:200` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (12 lines × 2) Content/Items/Melee/DawnshatterAzures/DawnshatterDash.cs:384 — Content/Items/Melee/DawnshatterAzures/DawnshatterDash.cs:384-395 | Content/Items/Melee/DawnshatterAzures/DawnshatterDive.cs:374-385 — 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 (12 lines × 2) Content/Items/Melee/DestroyersBlade.cs:226 — Content/Items/Melee/DestroyersBlade.cs:226-237 | Content/Items/Melee/DragonsScaleGreatsword.cs:234-245 — before extracting anything, compare `Content/Items/Melee/DestroyersBlade.cs` and `Content/Items/Melee/DragonsScaleGreatsword.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 419 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DestroyersBlade.cs:226` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Melee/DragonsScaleGreatsword.cs:246` calls `PlaySound` and `Content/Items/Melee/DestroyersBlade.cs:238` does not — after which the two agree again for 4 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 (12 lines × 2) Content/Items/Ranged/SneezingWyrms/SneezingWyrm.cs:26 — Content/Items/Ranged/SneezingWyrms/SneezingWyrm.cs:26-37 | Content/Items/Ranged/TiroFinales/TiroFinale.cs:28-39 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Ranged/SneezingWyrms/SneezingWyrm.cs:26` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Ranged/TiroFinales/TiroFinale.cs:44` calls `AltFunctionUse` and `Content/Items/Ranged/SneezingWyrms/SneezingWyrm.cs:42` does not — after which the two agree again for 3 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 (12 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:783 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:783-794 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:949-960 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs` as WHOLE FILES: this scan already matched 68 separate duplicated blocks between them, totalling at least 933 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:783` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:240 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:240-251 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:243-254 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs` as WHOLE FILES: this scan already matched 70 separate duplicated blocks between them, totalling at least 835 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:240` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (12 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:630 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:630-641 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:756-767 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:630` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraDashProj.cs:159 — Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraDashProj.cs:159-170 | Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraSlashProj.cs:161-172 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraDashProj.cs:159` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (12 lines × 2) Content/LegendWeapon/OnikiriLegend/UI/OniMeiRenderer.cs:1063 — Content/LegendWeapon/OnikiriLegend/UI/OniMeiRenderer.cs:1063-1074 | Content/LegendWeapon/OnikiriLegend/UI/OniRegisterRenderer.cs:211-222 — 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 (12 lines × 2) Content/NPCs/BloomsandSerpents/BssHead.cs:178 — Content/NPCs/BloomsandSerpents/BssHead.cs:178-189 | Content/NPCs/FestersandSerpents/FssHead.cs:161-172 — before extracting anything, compare `Content/NPCs/BloomsandSerpents/BssHead.cs` and `Content/NPCs/FestersandSerpents/FssHead.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 321 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (12 lines × 2) Content/NPCs/BrutalNPCs/BrutalGolem/GolemFreeHeadAI.cs:51 — Content/NPCs/BrutalNPCs/BrutalGolem/GolemFreeHeadAI.cs:51-62 | Content/NPCs/BrutalNPCs/BrutalGolem/GolemHeadAI.cs:48-59 — 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 (12 lines × 2) Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordEclipseSky.cs:170 — Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordEclipseSky.cs:170-181 | Content/Scenarios/Himayo/ToriiShrines/ToriiDusk.cs:191-202 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordEclipseSky.cs:166` calls `DrawFallback` and `Content/Scenarios/Himayo/ToriiShrines/ToriiDusk.cs:187` 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 (12 lines × 2) Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronCursedSkull.cs:72 — Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronCursedSkull.cs:72-83 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronOrbitSkull.cs:102-113 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronCursedSkull.cs` and `Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronOrbitSkull.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 55 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronCursedSkull.cs:69` calls `OrientSkull` and `Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronOrbitSkull.cs:99` 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.
  • + 87 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×104
  • Edited copy of a member (13 corresponding lines) Content/EntrustManager/Styles/DraedonManagerStyle.cs:770 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:770-782 | Content/EntrustManager/Styles/ForestManagerStyle.cs:766-778 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Content/QuestLogs/Styles/ForestQuestLogStyle.cs:711 — Content/QuestLogs/Styles/ForestQuestLogStyle.cs:711-725 | Content/QuestLogs/Styles/ForestQuestLogStyle.cs:727-741 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Content/LegendWeapon/HalibutLegend/DomainSkills/RestartFish.cs:448 — Content/LegendWeapon/HalibutLegend/DomainSkills/RestartFish.cs:448-471 | Content/LegendWeapon/HalibutLegend/DomainSkills/Superposition.cs:478-503 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Content/EntrustManager/Styles/HotwindManagerStyle.cs:761 — Content/EntrustManager/Styles/HotwindManagerStyle.cs:761-773 | Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:705-718 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Content/Narrative/Presentation/Skins/Sulfsea/SulfseaChoiceSkin.cs:48 — Content/Narrative/Presentation/Skins/Sulfsea/SulfseaChoiceSkin.cs:48-60 | Content/Narrative/Presentation/Skins/Tzeentch/TzeentchChoiceSkin.cs:48-64 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Content/Narrative/Presentation/Skins/StarStream/StarStreamPanelState.cs:200 — Content/Narrative/Presentation/Skins/StarStream/StarStreamPanelState.cs:200-212 | Content/UIs/UIEffect/StarStreamPRT.cs:34-50 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingUI.cs:347 — Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingUI.cs:347-359 | Content/LegendWeapon/SHPCLegend/UI/SHPCModuleSelectPanel.cs:280-297 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishNeonTetraVFX.cs:60 — Content/LegendWeapon/HalibutLegend/FishSkills/FishNeonTetraVFX.cs:60-77 | Content/LegendWeapon/HalibutLegend/FishSkills/FishNeonTetraVFX.cs:96-108 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Content/Scenarios/OldNet/Tiles/OldNetRelicTile.cs:185 — Content/Scenarios/OldNet/Tiles/OldNetRelicTile.cs:185-197 | Content/Scenarios/OldNet/Tiles/OldNetRelicTile.cs:254-269 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Content/EntrustManager/EntrustStatusEntry.cs:202 — Content/EntrustManager/EntrustStatusEntry.cs:202-219 | Content/HackTimes/HackTimeAccessDeniedEntry.cs:144-156 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Content/Items/Accessories/BrutalRelics/BrainOfCthulhu/MirrorheartPulse.cs:117 — Content/Items/Accessories/BrutalRelics/BrainOfCthulhu/MirrorheartPulse.cs:117-131 | Content/LegendWeapon/SHPCLegend/Modules/Frame/ResonanceFrameModule.cs:630-642 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Content/QuestLogs/QLNodes/AdventurerQuests.cs:531 — Content/QuestLogs/QLNodes/AdventurerQuests.cs:531-543 | Content/QuestLogs/QLNodes/AdventurerQuests.cs:969-981 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Content/GameModes/BrutalMobs/Ambience/Aetherglim/AetherglimPRT.cs:135 — Content/GameModes/BrutalMobs/Ambience/Aetherglim/AetherglimPRT.cs:135-148 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Rendering/EmpressPRT.cs:66-78 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Content/GameModes/BrutalMobs/Ambience/Frostveil/FrostveilPRT.cs:62 — Content/GameModes/BrutalMobs/Ambience/Frostveil/FrostveilPRT.cs:62-75 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Rendering/BKSParticles.cs:63-75 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Content/Wraiths/Deaths/Performances/RainSeizurePerformance.cs:444 — Content/Wraiths/Deaths/Performances/RainSeizurePerformance.cs:444-457 | Content/Wraiths/Deaths/Performances/RainSeizurePerformance.cs:459-471 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainDeco.cs:214 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainDeco.cs:214-226 | Content/Wraiths/Deaths/Performances/RainSeizurePerformance.cs:416-429 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Content/Items/Melee/Heartcarver.cs:1056 — Content/Items/Melee/Heartcarver.cs:1056-1071 | Content/Items/Melee/HeartcarverHeart.cs:329-341 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeSlash.cs:135 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeSlash.cs:135-147 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithSlash.cs:147-159 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Content/GameModes/GodSmith/Weapons/Bows/PhantasmScheme.cs:400 — Content/GameModes/GodSmith/Weapons/Bows/PhantasmScheme.cs:400-416 | Content/GameModes/GodSmith/Weapons/Bows/Projectiles/GsPursuitArrow.cs:32-44 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Content/Items/Magic/NeutronWands/NeutronPulsar.cs:336 — Content/Items/Magic/NeutronWands/NeutronPulsar.cs:336-348 | Content/Items/Magic/NeutronWands/NeutronStarquake.cs:139-152 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemTrapUnit.cs:670 — Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemTrapUnit.cs:670-683 | Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemTrapUnit.cs:708-720 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordOrbProj.cs:169 — Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordOrbProj.cs:169-181 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordOrbProj.cs:236-249 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Barrel/HeavyBarrelModule.cs:229 — Content/LegendWeapon/SHPCLegend/Modules/Barrel/HeavyBarrelModule.cs:229-249 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/HypersonicBarrelModule.cs:157-169 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Content/GameModes/GodSmith/Weapons/Boomerangs/GsIceBoomerang.cs:32 — Content/GameModes/GodSmith/Weapons/Boomerangs/GsIceBoomerang.cs:32-45 | Content/GameModes/GodSmith/Weapons/Boomerangs/GsThornChakram.cs:32-44 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Content/GameModes/GodSmith/Armors/Reset/GsCactusArmor.cs:32 — Content/GameModes/GodSmith/Armors/Reset/GsCactusArmor.cs:32-44 | Content/GameModes/GodSmith/Armors/Reset/GsTurtleArmor.cs:33-46 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • + 79 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×104
  • Duplicated block (6 lines × 3) Content/Industrials/ElectricPowers/GridSwitches/GridSwitchTP.cs:269 — Content/Industrials/ElectricPowers/GridSwitches/GridSwitchTP.cs:269-274 | Content/Industrials/ElectricPowers/Sensors/SensorTP.cs:380-385 | Content/Industrials/ElectricPowers/WireInterfaces/WireInterfaceTP.cs:306-311 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Industrials/ElectricPowers/WireInterfaces/WireInterfaceTP.cs:314` calls `Draw`, `Rectangle`, `Color` and `Content/Industrials/ElectricPowers/Sensors/SensorTP.cs:388` 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 (6 lines × 3) Content/Items/Magic/Pandemoniums/PandemoniumCircle.cs:248 — Content/Items/Magic/Pandemoniums/PandemoniumCircle.cs:248-253 | Content/Items/Magic/Pandemoniums/PandemoniumQSkill.cs:219-224 | Content/Items/Magic/Pandemoniums/PandemoniumRSkill.cs:377-382 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/Pandemoniums/PandemoniumCircle.cs:248` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 3) Content/Items/Ranged/NeutronBows/NeutronBow.cs:278 — Content/Items/Ranged/NeutronBows/NeutronBow.cs:278-283 | Content/Items/Ranged/Thornstrings/ThornstringHeld.cs:197-202 | Content/Items/Ranged/Undertows/UndertowHeld.cs:203-208 — before extracting anything, compare `Content/Items/Ranged/NeutronBows/NeutronBow.cs` and `Content/Items/Ranged/Thornstrings/ThornstringHeld.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 98 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 3) Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs:143 — Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs:143-148 | Content/LegendWeapon/SHPCLegend/TrialQuests/SHPCTrackerWidgetStyle.cs:134-139 | Content/Scenarios/Draedon/Quest/DraedonTrackerWidgetStyle.cs:165-170 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs:143` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs:153` calls `Sin` and `Content/LegendWeapon/SHPCLegend/TrialQuests/SHPCTrackerWidgetStyle.cs:143` 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 (6 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:1051 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:1051-1056 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1625-1630 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1704-1709 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:1051` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:1062 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:1062-1067 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:920-925 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1314-1319 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:1062` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 3) Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemSpikyBall.cs:106 — Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemSpikyBall.cs:106-111 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronCursedSkull.cs:124-129 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronOrbitSkull.cs:161-166 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronCursedSkull.cs` and `Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronOrbitSkull.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 55 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemSpikyBall.cs:106` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronCursedSkull.cs:119` calls `Pow`, `Clamp`, `Sin` and `Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronOrbitSkull.cs:158` 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 (6 lines × 3) Content/EntrustManager/Styles/DraedonManagerStyle.cs:137 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:137-142 | Content/EntrustManager/Styles/ForestManagerStyle.cs:135-140 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:132-137 — before extracting anything, compare `Content/EntrustManager/Styles/DraedonManagerStyle.cs` and `Content/EntrustManager/Styles/ForestManagerStyle.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 334 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/EntrustManager/Styles/DraedonManagerStyle.cs:137` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 3) Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawCorrosionNPC.cs:251 — Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawCorrosionNPC.cs:251-256 | Content/LegendWeapon/KikasaLegend/KikasaWisps/KikasaWispBurnNPC.cs:83-88 | Content/Scenarios/Dungeonworld/NPCs/Elites/DrownedTurnkey.cs:800-805 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaWisps/KikasaWispBurnNPC.cs:81` calls `SetValue` and `Content/Scenarios/Dungeonworld/NPCs/Elites/DrownedTurnkey.cs:798` 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 (6 lines × 3) Content/Items/Melee/DragonsScaleGreatsword.cs:40 — Content/Items/Melee/DragonsScaleGreatsword.cs:40-45 | Content/Items/Melee/EnergySword.cs:37-42 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:40-45 — before extracting anything, compare `Content/Items/Melee/DragonsScaleGreatsword.cs` and `Content/Items/Melee/EnergySword.cs` as WHOLE FILES: this scan already matched 26 separate duplicated blocks between them, totalling at least 308 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 (6 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:69 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:69-74 | Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs:78-83 | Content/Scenarios/Kiame/Overlay/OniRainWorldRender.cs:65-70 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs` and `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 192 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 3) Content/LegendWeapon/OnikiriLegend/UI/OniMeiUI.cs:698 — Content/LegendWeapon/OnikiriLegend/UI/OniMeiUI.cs:698-703 | Content/LegendWeapon/OnikiriLegend/UI/OniRegisterUI.cs:380-385 | Content/LegendWeapon/OnikiriLegend/UI/OniSigilUI.cs:384-389 — 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 (6 lines × 3) Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:102 — Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:102-107 | Content/QuestLogs/Styles/ForestQuestLogStyle.cs:103-108 | Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:67-72 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:102` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:98` calls `Color` and `Content/QuestLogs/Styles/ForestQuestLogStyle.cs:99` 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 (6 lines × 3) Content/UIs/UIEffect/DraedonDataPRT.cs:9 — Content/UIs/UIEffect/DraedonDataPRT.cs:9-14 | Content/UIs/UIEffect/NeonMaidPRT.cs:10-15 | Content/UIs/UIEffect/StarStreamPRT.cs:10-15 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/UIs/UIEffect/StarStreamPRT.cs:17` calls `NextFloat` and `Content/UIs/UIEffect/DraedonDataPRT.cs:17` does not — after which the two agree again for 3 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 (6 lines × 3) Content/Wraiths/Projectiles/GhostHandProj.cs:666 — Content/Wraiths/Projectiles/GhostHandProj.cs:666-671 | Content/Wraiths/Projectiles/GhostHandProj.cs:693-698 | Content/Wraiths/Projectiles/GhostHandProj.cs:721-726 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Wraiths/Projectiles/GhostHandProj.cs:666` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 3) Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs:150 — Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs:150-155 | Content/LegendWeapon/KikasaLegend/UI/ServantWheel/KikasaServantWheelUI.cs:506-511 | Content/LegendWeapon/SHPCLegend/UI/DomainWheel/SHPCDomainWheelUI.cs:425-430 — before extracting anything, compare `Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs` and `Content/LegendWeapon/SHPCLegend/UI/DomainWheel/SHPCDomainWheelUI.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 3) Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyMaggotBolt.cs:97 — Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyMaggotBolt.cs:97-102 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhShellSpike.cs:53-58 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhStingerBolt.cs:62-67 — before extracting anything, compare `Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhShellSpike.cs` and `Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhStingerBolt.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 77 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyMaggotBolt.cs:97` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhStingerBolt.cs:58` calls `OnHitPlayer`, `AddBuff` and `Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhShellSpike.cs:51` 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 (6 lines × 3) Content/Industrials/MaterialFlow/Fluids/FluidPipeline.cs:495 — Content/Industrials/MaterialFlow/Fluids/FluidPipeline.cs:495-500 | Content/Industrials/MaterialFlow/Fluids/FluidPipeline.cs:506-511 | Content/Industrials/MaterialFlow/Fluids/FluidPipeline.cs:517-522 — 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 (6 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomNeedle.cs:78 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomNeedle.cs:78-83 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeLaserBolt.cs:94-99 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaShrimpWaterBolt.cs:81-86 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomNeedle.cs:78` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:1060 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:1060-1065 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1431-1436 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1237-1242 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:1060` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsHail.cs:140 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsHail.cs:140-145 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeBloodBee.cs:158-163 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenCrystalShard.cs:167-172 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (6 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:456 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:456-461 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:742-747 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:865-870 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:456` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 3) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistEclipseDragon.cs:260 — Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistEclipseDragon.cs:260-265 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistSeekerStar.cs:170-175 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistStarBead.cs:162-167 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistEclipseDragon.cs:260` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 3) Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdHammerConeOmen.cs:154 — Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdHammerConeOmen.cs:154-159 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmYetiConeOmen.cs:169-174 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandConeTelegraph.cs:177-182 — before extracting anything, compare `Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdHammerConeOmen.cs` and `Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmYetiConeOmen.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 3) Content/GameModes/GodSmith/Armors/Reset/GsBeetleArmors.cs:180 — Content/GameModes/GodSmith/Armors/Reset/GsBeetleArmors.cs:180-185 | Content/GameModes/GodSmith/Armors/Reset/GsBeetleArmors.cs:217-222 | Content/GameModes/GodSmith/Armors/Reset/GsTurtleArmor.cs:72-77 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Armors/Reset/GsBeetleArmors.cs:180` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • + 79 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×99
  • Edited copy of a member (15 corresponding lines) Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:932 — Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:932-946 | Content/Industrials/Modifys/ChargingStationUI.cs:608-623 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Content/LegendWeapon/HalibutLegend/DomainSkills/YourLevelIsTooLow.cs:303 — Content/LegendWeapon/HalibutLegend/DomainSkills/YourLevelIsTooLow.cs:303-323 | Content/LegendWeapon/HalibutLegend/DomainSkills/YourLevelIsTooLow.cs:332-351 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Content/EntrustManager/EntrustStatusEntry.cs:262 — Content/EntrustManager/EntrustStatusEntry.cs:262-276 | Content/Scenarios/Draedon/Quest/DraedonTrackerWidgetStyle.cs:91-114 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Content/EntrustManager/Styles/ForestManagerStyle.cs:191 — Content/EntrustManager/Styles/ForestManagerStyle.cs:191-205 | Content/QuestLogs/Styles/ForestQuestLogStyle.cs:666-682 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:199 — Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:199-214 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconUI.cs:201-215 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Content/Industrials/ElectricPowers/Crushers/CrusherTP.cs:273 — Content/Industrials/ElectricPowers/Crushers/CrusherTP.cs:273-290 | Content/Industrials/ElectricPowers/Crushers/CrusherTP.cs:293-307 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Frame/RecursiveFrameModule.cs:54 — Content/LegendWeapon/SHPCLegend/Modules/Frame/RecursiveFrameModule.cs:54-68 | Content/LegendWeapon/SHPCLegend/Modules/Frame/ReplicatorFrameModule.cs:50-67 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Content/Narrative/Presentation/Skins/Brimstone/BrimstonePopupSkin.cs:70 — Content/Narrative/Presentation/Skins/Brimstone/BrimstonePopupSkin.cs:70-98 | Content/Narrative/Presentation/Skins/Sea/SeaPopupSkin.cs:36-50 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:444 — Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:444-458 | Content/Items/Modifys/RTerraBlades/RTerraBladeHeld.cs:505-524 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Barrel/ForkBarrelModule.cs:47 — Content/LegendWeapon/SHPCLegend/Modules/Barrel/ForkBarrelModule.cs:47-66 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/PrismaticBarrelModule.cs:45-59 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1157 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1157-1171 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:960-974 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1242 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1242-1256 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:1191-1205 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuPoFX.cs:31 — Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuPoFX.cs:31-45 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuPoFX.cs:79-94 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Content/Narrative/Presentation/Skins/Kikasa/KikasaPopupSkin.cs:47 — Content/Narrative/Presentation/Skins/Kikasa/KikasaPopupSkin.cs:47-61 | Content/Narrative/Presentation/Skins/Onikiri/OnikiriPopupSkin.cs:46-60 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Content/Items/Accessories/Unsunghero.cs:189 — Content/Items/Accessories/Unsunghero.cs:189-203 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:348-362 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Content/LegendWeapon/HalibutLegend/OceanCurrentParticles.cs:317 — Content/LegendWeapon/HalibutLegend/OceanCurrentParticles.cs:317-332 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendParticles.cs:433-447 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Content/Items/Magic/Elysiums/Serpents/SnakeConversionWave.cs:82 — Content/Items/Magic/Elysiums/Serpents/SnakeConversionWave.cs:82-104 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBellWave.cs:121-135 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Content/PRTTypes/PRT_SHPCRedlineCinder.cs:55 — Content/PRTTypes/PRT_SHPCRedlineCinder.cs:55-72 | Content/PRTTypes/PRT_SHPCThermalEmber.cs:54-68 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Content/Scenarios/Draedon/Quest/DeploySignaltowers/DeploySignaltowerRender.cs:781 — Content/Scenarios/Draedon/Quest/DeploySignaltowers/DeploySignaltowerRender.cs:781-811 | Content/UIs/UIEffect/TechPRT.cs:36-50 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaBloodSurgeWave.cs:145 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaBloodSurgeWave.cs:145-160 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaMiniBloodSlime.cs:176-190 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordRayRender.cs:103 — Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordRayRender.cs:103-117 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordRayRender.cs:120-137 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishZombieVFX.cs:161 — Content/LegendWeapon/HalibutLegend/FishSkills/FishZombieVFX.cs:161-177 | Content/LegendWeapon/HalibutLegend/FishSkills/FishZombieVFX.cs:218-232 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Content/LegendWeapon/SHPCLegend/TrialQuests/SHPCTrackerWidgetStyle.cs:134 — Content/LegendWeapon/SHPCLegend/TrialQuests/SHPCTrackerWidgetStyle.cs:134-148 | Content/Scenarios/Draedon/Quest/DraedonTrackerWidgetStyle.cs:165-179 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Content/Items/Melee/EnergySword.cs:465 — Content/Items/Melee/EnergySword.cs:465-479 | Content/Items/Melee/RebelBlade.cs:462-478 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Content/GameModes/GodSmith/Weapons/Boomerangs/GsAnchor.cs:107 — Content/GameModes/GodSmith/Weapons/Boomerangs/GsAnchor.cs:107-122 | Content/GameModes/GodSmith/Weapons/Boomerangs/GsPaladinsHammer.cs:156-170 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • + 74 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×96
  • Edited copy of a member (14 corresponding lines) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Rendering/EmpressBeamDraw.cs:14 — Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Rendering/EmpressBeamDraw.cs:14-28 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Rendering/EmpressBeamDraw.cs:47-61 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1420 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1420-1435 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1570-1586 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) Content/EntrustManager/BaseQuestAcceptUI.cs:281 — Content/EntrustManager/BaseQuestAcceptUI.cs:281-296 | Content/UIs/OverhaulSettings/OverhaulSettingsUI.cs:389-405 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:237 — Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:237-250 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterUI.cs:240-259 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:717 — Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:717-730 | Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:733-746 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) Content/Items/Ranged/TiroFinales/FinaleMagicBolt.cs:78 — Content/Items/Ranged/TiroFinales/FinaleMagicBolt.cs:78-91 | Content/Items/Ranged/TiroFinales/FinaleMusketRound.cs:81-95 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowGeyserProj.cs:117 — Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowGeyserProj.cs:117-130 | Content/NPCs/FestersandSerpents/Projectiles/FssGeyserColumn.cs:115-128 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistAmbience.cs:72 — Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistAmbience.cs:72-85 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistAmbience.cs:129-146 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) Content/Items/Melee/DestroyersBlade.cs:611 — Content/Items/Melee/DestroyersBlade.cs:611-624 | Content/Items/Melee/DestroyersBladeEXs/DestroyersBeamEX.cs:90-104 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) Content/Items/Magic/AriaofTheCosmoses/AriaofTheCosmos.cs:165 — Content/Items/Magic/AriaofTheCosmoses/AriaofTheCosmos.cs:165-181 | Content/Items/Magic/Pandemoniums/Pandemonium.cs:199-212 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) Content/Scenarios/OldNet/NPCs/OldNetThreatField.cs:870 — Content/Scenarios/OldNet/NPCs/OldNetThreatField.cs:870-883 | Content/Scenarios/OldNet/OldNetAbsorbFX.cs:14-36 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) Content/NPCs/BloomsandSerpents/BssVfx.cs:110 — Content/NPCs/BloomsandSerpents/BssVfx.cs:110-123 | Content/NPCs/FestersandSerpents/FssVfx.cs:153-166 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) Content/PRTTypes/PRT_KikasaInkDrip.cs:52 — Content/PRTTypes/PRT_KikasaInkDrip.cs:52-65 | Content/PRTTypes/PRT_OniPuddleRise.cs:69-88 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) Content/Items/Magic/Elysiums/Revelations/RevelationSealJudgment.cs:116 — Content/Items/Magic/Elysiums/Revelations/RevelationSealJudgment.cs:116-129 | Content/Items/Magic/Elysiums/Revelations/RevelationSealJudgment.cs:132-149 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) Content/LegendWeapon/HalibutLegend/UI/HalibutHudLead.cs:702 — Content/LegendWeapon/HalibutLegend/UI/HalibutHudLead.cs:702-718 | Content/LegendWeapon/OnikiriLegend/Tutorial/OnikiriTutorialRenderer.cs:661-674 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadArcProj.cs:174 — Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadArcProj.cs:174-194 | Content/Items/Stones/Granites/GraniteThrowingKnife.cs:327-340 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishScorpioPRT.cs:70 — Content/LegendWeapon/HalibutLegend/FishSkills/FishScorpioPRT.cs:70-83 | Content/LegendWeapon/HalibutLegend/FishSkills/FishofCthuluVFX.cs:227-242 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishHarpyVFX.cs:143 — Content/LegendWeapon/HalibutLegend/FishSkills/FishHarpyVFX.cs:143-156 | Content/LegendWeapon/HalibutLegend/FishSkills/FishUnicornVFX.cs:64-78 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) Content/GameModes/GodSmith/Weapons/MagicChant/GsVilethorn.cs:42 — Content/GameModes/GodSmith/Weapons/MagicChant/GsVilethorn.cs:42-55 | Content/GameModes/GodSmith/Weapons/MagicChant/GsWandOfFrosting.cs:58-73 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) Content/Items/Magic/AriaofTheCosmoses/AriaofTheCosmosHeld.cs:80 — Content/Items/Magic/AriaofTheCosmoses/AriaofTheCosmosHeld.cs:80-93 | Content/Items/Magic/AriaofTheCosmoses/AriaofTheCosmosHeld.cs:179-192 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishNeonTetraVFX.cs:170 — Content/LegendWeapon/HalibutLegend/FishSkills/FishNeonTetraVFX.cs:170-189 | Content/PRTTypes/PRT_DefEmber.cs:57-70 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) Content/GameModes/GodSmith/Weapons/MagicMorph/GsLeafBlower.cs:66 — Content/GameModes/GodSmith/Weapons/MagicMorph/GsLeafBlower.cs:66-82 | Content/LegendWeapon/SHPCLegend/Modules/Stock/StormStockModule.cs:237-250 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:769 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:769-784 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:1260-1273 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) Content/NPCs/BrutalNPCs/BrutalMoonLord/States/MLordConcertoState.cs:139 — Content/NPCs/BrutalNPCs/BrutalMoonLord/States/MLordConcertoState.cs:139-154 | Content/NPCs/BrutalNPCs/BrutalMoonLord/States/MLordDeathrayScanState.cs:141-154 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) Content/Items/Magic/AriaofTheCosmoses/AriaRSkill.cs:130 — Content/Items/Magic/AriaofTheCosmoses/AriaRSkill.cs:130-143 | Content/Items/Magic/AriaofTheCosmoses/FlattenedAccretionDisk.cs:142-156 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • + 71 more in this group — see findings.md.
D3 · God Classes · ClassTooLong · ×94
  • ClassTooLong: TwinsRenderHelper Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Rendering/TwinsRenderHelper.cs — ClassTooLong — 759 significant lines (blank, comment-only and punctuation-only lines excluded), 18 methods. The bar is 400 significant lines; this is 359 over it, 1.90× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • ClassTooLong: OverhaulSettingsUI Content/UIs/OverhaulSettings/OverhaulSettingsUI.cs — ClassTooLong — 691 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 291 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.
  • ClassTooLong: KikasaHud Content/LegendWeapon/KikasaLegend/UI/KikasaHud.cs — ClassTooLong — 656 significant lines (blank, comment-only and punctuation-only lines excluded), 18 methods. The bar is 400 significant lines; this is 256 over it, 1.64× 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: CyberBodyRenderer Content/Cyberwares/UIs/CyberBodyRenderer.cs — ClassTooLong — 650 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. The bar is 400 significant lines; this is 250 over it, 1.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.
  • ClassTooLong: AtlasSkillSea Content/LegendWeapon/HalibutLegend/UI/Atlas/AtlasSkillSea.cs — ClassTooLong — 648 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 248 over it, 1.62× 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: OniRegisterRenderer Content/LegendWeapon/OnikiriLegend/UI/OniRegisterRenderer.cs — ClassTooLong — 609 significant lines (blank, comment-only and punctuation-only lines excluded), 25 methods. The bar is 400 significant lines; this is 209 over it, 1.52× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • ClassTooLong: ThrowerUI Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs — ClassTooLong — 605 significant lines (blank, comment-only and punctuation-only lines excluded), 25 methods. The bar is 400 significant lines; this is 205 over it, 1.51× 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: DraedonQuestLogStyle Content/QuestLogs/Styles/DraedonQuestLogStyle.cs — ClassTooLong — 597 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 197 over it, 1.49× 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: OceanBrutalNPC Content/GameModes/BrutalMobs/Ocean/OceanBrutalNPC.cs — ClassTooLong — 577 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 177 over it, 1.44× 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: SHPCCyberPanel Content/LegendWeapon/SHPCLegend/UI/SHPCCyberPanel.cs — ClassTooLong — 577 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. The bar is 400 significant lines; this is 177 over it, 1.44× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • ClassTooLong: CollectorUI Content/Industrials/ElectricPowers/Collectors/CollectorUI.cs — ClassTooLong — 553 significant lines (blank, comment-only and punctuation-only lines excluded), 22 methods. The bar is 400 significant lines; this is 153 over it, 1.38× 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: OniMeiStrikes Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiStrikes.cs — ClassTooLong — 552 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. The bar is 400 significant lines; this is 152 over it, 1.38× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • ClassTooLong: PandemoniumChannel Content/Items/Magic/Pandemoniums/PandemoniumChannel.cs — ClassTooLong — 551 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 151 over it, 1.38× 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: KikasaInkDrop Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs — ClassTooLong — 548 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 148 over it, 1.37× 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: OnikiriTutorialRenderer Content/LegendWeapon/OnikiriLegend/Tutorial/OnikiriTutorialRenderer.cs — ClassTooLong — 546 significant lines (blank, comment-only and punctuation-only lines excluded), 25 methods. The bar is 400 significant lines; this is 146 over it, 1.37× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • ClassTooLong: OldNetDebriefPanel Content/Scenarios/OldNet/UI/OldNetDebriefPanel.cs — ClassTooLong — 545 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 145 over it, 1.36× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • ClassTooLong: CollectorArm Content/Industrials/ElectricPowers/Collectors/CollectorArm.cs — ClassTooLong — 535 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 135 over it, 1.34× 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: ForestManagerStyle Content/EntrustManager/Styles/ForestManagerStyle.cs — ClassTooLong — 532 significant lines (blank, comment-only and punctuation-only lines excluded), 27 methods. The bar is 400 significant lines; this is 132 over it, 1.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: OniDomainPlayer Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainPlayer.cs — ClassTooLong — 532 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 132 over it, 1.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: CthulhuEye Content/LegendWeapon/HalibutLegend/FishSkills/FishofCthulu.cs — ClassTooLong — 530 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 130 over it, 1.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: DraedonManagerStyle Content/EntrustManager/Styles/DraedonManagerStyle.cs — ClassTooLong — 529 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 129 over it, 1.32× 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: HotwindManagerStyle Content/EntrustManager/Styles/HotwindManagerStyle.cs — ClassTooLong — 529 significant lines (blank, comment-only and punctuation-only lines excluded), 25 methods. The bar is 400 significant lines; this is 129 over it, 1.32× 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: ShenyoGhostLakeScene Content/MainMenus/Shenyo/ShenyoGhostLakeScene.cs — ClassTooLong — 527 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 127 over it, 1.32× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • ClassTooLong: HotwindQuestLogStyle Content/QuestLogs/Styles/HotwindQuestLogStyle.cs — ClassTooLong — 523 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 123 over it, 1.31× 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: SakuraKiriPlayerProj Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraKiriPlayerProj.cs — ClassTooLong — 519 significant lines (blank, comment-only and punctuation-only lines excluded), 19 methods. The bar is 400 significant lines; this is 119 over it, 1.30× 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.
  • + 69 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×89
  • Duplicated block (13 lines × 2) Content/Items/Melee/NeutronGlaive.cs:216 — Content/Items/Melee/NeutronGlaive.cs:216-228 | Content/Items/Modifys/RBloodButcherer.cs:202-214 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/NeutronGlaive.cs:216` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) Content/GameModes/BrutalMobs/Martians/Projectiles/MrtWrenchProj.cs:147 — Content/GameModes/BrutalMobs/Martians/Projectiles/MrtWrenchProj.cs:147-159 | Content/GameModes/BrutalMobs/NightPack/Projectiles/NightBoneProj.cs:145-157 — before extracting anything, compare `Content/GameModes/BrutalMobs/Martians/Projectiles/MrtWrenchProj.cs` and `Content/GameModes/BrutalMobs/NightPack/Projectiles/NightBoneProj.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Martians/Projectiles/MrtWrenchProj.cs:147` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/BrutalMobs/Martians/Projectiles/MrtWrenchProj.cs:145` calls `Lerp` and `Content/GameModes/BrutalMobs/NightPack/Projectiles/NightBoneProj.cs:143` 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 (13 lines × 2) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistPlanetProj.cs:535 — Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistPlanetProj.cs:535-547 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistPlanetProj.cs:563-575 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistPlanetProj.cs:535` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteFireSpot.cs:87 — Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteFireSpot.cs:87-99 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkEmberProj.cs:111-123 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteFireSpot.cs:87` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:148 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:148-160 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:214-226 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:148` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (13 lines × 2) Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:422 — Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:422-434 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleCut.cs:403-415 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:422` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) Content/Narrative/MusicToast.cs:572 — Content/Narrative/MusicToast.cs:572-584 | Content/Narrative/MusicToast.cs:649-661 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Narrative/MusicToast.cs:572` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (13 lines × 2) Content/Scenarios/Himayo/ToriiShrines/ToriiShrinePromptRender.cs:45 — Content/Scenarios/Himayo/ToriiShrines/ToriiShrinePromptRender.cs:45-57 | Content/Scenarios/OldDuke/Campsites/OldDukeWanderingActor.cs:623-635 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (13 lines × 2) Content/Items/Melee/EnergySword.cs:129 — Content/Items/Melee/EnergySword.cs:129-141 | Content/Items/Melee/RebelBlade.cs:154-166 — before extracting anything, compare `Content/Items/Melee/EnergySword.cs` and `Content/Items/Melee/RebelBlade.cs` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 375 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 (13 lines × 2) Content/Items/Melee/EnergySword.cs:249 — Content/Items/Melee/EnergySword.cs:249-261 | Content/Items/Melee/RebelBlade.cs:275-287 — before extracting anything, compare `Content/Items/Melee/EnergySword.cs` and `Content/Items/Melee/RebelBlade.cs` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 375 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/EnergySword.cs:249` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:53 — Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:53-65 | Content/Items/Modifys/RBloodButcherer.cs:136-148 — before extracting anything, compare `Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs` and `Content/Items/Modifys/RBloodButcherer.cs` as WHOLE FILES: this scan already matched 36 separate duplicated blocks between them, totalling at least 458 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) Content/Industrials/ElectricPowers/Crushers/CrusherStorageProvider.cs:159 — Content/Industrials/ElectricPowers/Crushers/CrusherStorageProvider.cs:159-171 | Content/Industrials/ElectricPowers/Incinerators/IncineratorStorageProvider.cs:169-181 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Crushers/CrusherStorageProvider.cs:159` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (13 lines × 2) Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaRender.cs:236 — Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaRender.cs:236-248 | Content/NPCs/BrutalNPCs/BrutalPlantera/Rendering/PlanteraBloomRender.cs:58-70 — before extracting anything, compare `Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaRender.cs` and `Content/NPCs/BrutalNPCs/BrutalPlantera/Rendering/PlanteraBloomRender.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaRender.cs:236` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:348 — Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:348-360 | Content/Items/Melee/WeaverGrievanceses/WGManifestationActor.cs:283-295 — before extracting anything, compare `Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs` and `Content/Items/Melee/WeaverGrievanceses/WGManifestationActor.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 237 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:348` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) Content/Items/Melee/Arbiters/ArbiterManifestationSystem.cs:281 — Content/Items/Melee/Arbiters/ArbiterManifestationSystem.cs:281-293 | Content/Items/Melee/WeaverGrievanceses/WGManifestationSystem.cs:273-285 — before extracting anything, compare `Content/Items/Melee/Arbiters/ArbiterManifestationSystem.cs` and `Content/Items/Melee/WeaverGrievanceses/WGManifestationSystem.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Arbiters/ArbiterManifestationSystem.cs:281` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) Content/Items/Melee/DivineSourceBlades/DivineSourceWaveProjectile.cs:400 — Content/Items/Melee/DivineSourceBlades/DivineSourceWaveProjectile.cs:400-412 | Content/Items/Melee/NeutronGlaive.cs:1083-1095 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DivineSourceBlades/DivineSourceWaveProjectile.cs:400` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) Content/Items/Melee/DragonsScaleGreatsword.cs:659 — Content/Items/Melee/DragonsScaleGreatsword.cs:659-671 | Content/Items/Melee/DragonsScaleGreatsword.cs:869-881 — 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) Content/LegendWeapon/HalibutLegend/DomainSkills/RestartFish.cs:193 — Content/LegendWeapon/HalibutLegend/DomainSkills/RestartFish.cs:193-205 | Content/LegendWeapon/HalibutLegend/DomainSkills/YourLevelIsTooLow.cs:761-773 — 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 (13 lines × 2) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:706 — Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:706-718 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaReset.cs:683-695 — before extracting anything, compare `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs` and `Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaReset.cs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:706` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaReset.cs:699` calls `RevertBorrowOnEnd` and `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:722` does not — after which the two agree again for 3 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 (13 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuLaoFX.cs:119 — Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuLaoFX.cs:119-131 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuXiFX.cs:166-178 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuLaoFX.cs:119` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) Content/NPCs/BloomsandSerpents/States/BssHubState.cs:90 — Content/NPCs/BloomsandSerpents/States/BssHubState.cs:90-102 | Content/NPCs/FestersandSerpents/States/FssHubState.cs:100-112 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BloomsandSerpents/States/BssHubState.cs:90` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note first that the copies are not typed on the same thing: the declarations holding them bind `ctx` to `BssStateContext` in one and `FssStateContext` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (13 lines × 2) Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronCursedSkull.cs:125 — Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronCursedSkull.cs:125-137 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronOrbitSkull.cs:162-174 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronCursedSkull.cs` and `Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronOrbitSkull.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 55 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronCursedSkull.cs:125` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) Content/NPCs/ScrapCommanders/Projectiles/ScrapMortarShell.cs:116 — Content/NPCs/ScrapCommanders/Projectiles/ScrapMortarShell.cs:116-128 | Content/NPCs/ScrapCommanders/Projectiles/ScrapShellFrag.cs:59-71 — before extracting anything, compare `Content/NPCs/ScrapCommanders/Projectiles/ScrapMortarShell.cs` and `Content/NPCs/ScrapCommanders/Projectiles/ScrapShellFrag.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/ScrapCommanders/Projectiles/ScrapMortarShell.cs:116` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) Content/TimeFreezes/WorldFreezeGlobals.cs:227 — Content/TimeFreezes/WorldFreezeGlobals.cs:227-239 | Content/TimeFreezes/WorldFreezeGlobals.cs:527-539 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/TimeFreezes/WorldFreezeGlobals.cs:227` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) Content/GameModes/BrutalMobs/FrostLegion/FrostLegionNPC.cs:346 — Content/GameModes/BrutalMobs/FrostLegion/FrostLegionNPC.cs:346-358 | Content/GameModes/BrutalMobs/Graveyard/GraveyardBrutalNPC.cs:279-291 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • + 64 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×84
  • Duplicated block (7 lines × 3) Content/LegendWeapon/HalibutLegend/FishSkills/FishEaterofPlanktonVFX.cs:189 — Content/LegendWeapon/HalibutLegend/FishSkills/FishEaterofPlanktonVFX.cs:189-195 | Content/LegendWeapon/HalibutLegend/FishSkills/FishHungerVFX.cs:253-259 | Content/LegendWeapon/HalibutLegend/FishSkills/FishRockParticles.cs:186-192 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishEaterofPlanktonVFX.cs:189` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 3) Content/Industrials/ElectricPowers/Collectors/CollectorTP.cs:519 — Content/Industrials/ElectricPowers/Collectors/CollectorTP.cs:519-525 | Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs:1067-1073 | Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersTP.cs:483-489 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Collectors/CollectorTP.cs:519` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 3) Content/Items/Melee/Heartcarver.cs:1181 — Content/Items/Melee/Heartcarver.cs:1181-1187 | Content/LegendWeapon/HalibutLegend/FishSkills/FishHarpy.cs:165-171 | Content/LegendWeapon/SHPCLegend/Modules/Grip/CrystalGripModule.cs:68-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (7 lines × 3) Content/Items/Summon/AzureDragonRage.cs:117 — Content/Items/Summon/AzureDragonRage.cs:117-123 | Content/Items/Summon/BleedingScourge.cs:100-106 | Content/Items/Summon/WhiplashGalactica.cs:126-132 — before extracting anything, compare `Content/Items/Summon/AzureDragonRage.cs` and `Content/Items/Summon/BleedingScourge.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 93 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Summon/AzureDragonRage.cs:117` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 3) Content/Items/Summon/AzureDragonRage.cs:137 — Content/Items/Summon/AzureDragonRage.cs:137-143 | Content/Items/Summon/BleedingScourge.cs:120-126 | Content/Items/Summon/ElementWhip.cs:152-158 — before extracting anything, compare `Content/Items/Summon/AzureDragonRage.cs` and `Content/Items/Summon/BleedingScourge.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 93 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Summon/ElementWhip.cs:159` calls `EntitySpriteDraw` and `Content/Items/Summon/AzureDragonRage.cs:144` does not — after which the two agree again for 4 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 × 3) Content/EntrustManager/Styles/DraedonManagerStyle.cs:425 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:425-431 | Content/EntrustManager/Styles/ForestManagerStyle.cs:434-440 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:423-429 — before extracting anything, compare `Content/EntrustManager/Styles/DraedonManagerStyle.cs` and `Content/EntrustManager/Styles/ForestManagerStyle.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 334 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/EntrustManager/Styles/DraedonManagerStyle.cs:425` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 3) Content/Items/Magic/Elysiums/ElysiumHeld.cs:289 — Content/Items/Magic/Elysiums/ElysiumHeld.cs:289-295 | Content/Items/Magic/Elysiums/ElysiumHeld.cs:321-327 | Content/Items/Magic/Elysiums/Serpents/SnakeConversionWave.cs:195-201 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Magic/Elysiums/ElysiumHeld.cs:317` calls `SetValue` and `Content/Items/Magic/Elysiums/ElysiumHeld.cs:285` 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 × 3) Content/LegendWeapon/HalibutLegend/FishSkills/FishBat.cs:631 — Content/LegendWeapon/HalibutLegend/FishSkills/FishBat.cs:631-637 | Content/LegendWeapon/HalibutLegend/FishSkills/FishSwarm.cs:713-719 | Content/LegendWeapon/HalibutLegend/FishSkills/FishSwarm.cs:819-825 — 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 (7 lines × 3) Content/UIs/UIEffect/AshPRT.cs:9 — Content/UIs/UIEffect/AshPRT.cs:9-15 | Content/UIs/UIEffect/EmberPRT.cs:9-15 | Content/UIs/UIEffect/TzeentchRunePRT.cs:11-17 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/UIs/UIEffect/TzeentchRunePRT.cs:19` calls `NextFloat` and `Content/UIs/UIEffect/AshPRT.cs:18` 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 × 3) Content/Items/Magic/Elysiums/ElysiumHeld.cs:287 — Content/Items/Magic/Elysiums/ElysiumHeld.cs:287-293 | Content/Items/Magic/Elysiums/ElysiumHeld.cs:319-325 | Content/Items/Magic/Elysiums/UI/ElysiumRoseWindow.cs:231-237 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/Elysiums/ElysiumHeld.cs:287` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Magic/Elysiums/ElysiumHeld.cs:317` calls `SetValue` and `Content/Items/Magic/Elysiums/ElysiumHeld.cs:285` does not — after which the two agree again for 3 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 × 3) Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:722 — Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:722-728 | Content/LegendWeapon/HalibutLegend/FishSkills/FishFrostMinnow.cs:560-566 | Content/LegendWeapon/HalibutLegend/FishSkills/FishPrincess.cs:614-620 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:722` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:978 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:978-984 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1319-1325 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:769-775 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs` as WHOLE FILES: this scan already matched 68 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1510 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1510-1516 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:1363-1369 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:993-999 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1510` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:375 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:375-381 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:369-375 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:447-453 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:375` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:955 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:955-961 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1419-1425 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:965-971 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (7 lines × 3) Content/LegendWeapon/SHPCLegend/Modules/Barrel/RapidBarrelModule.cs:640 — Content/LegendWeapon/SHPCLegend/Modules/Barrel/RapidBarrelModule.cs:640-646 | Content/LegendWeapon/SHPCLegend/Modules/Optic/SniperOpticModule.cs:383-389 | Content/LegendWeapon/SHPCLegend/Modules/Stock/SteadyStockModule.cs:547-553 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (7 lines × 3) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs:170 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs:170-176 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeHeatRay.cs:159-165 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeSkullBeamProj.cs:170-176 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs` and `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeHeatRay.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs:170` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (7 lines × 3) Content/EntrustManager/Styles/DraedonManagerStyle.cs:667 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:667-673 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:678-684 | Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:166-172 — before extracting anything, compare `Content/EntrustManager/Styles/DraedonManagerStyle.cs` and `Content/EntrustManager/Styles/HotwindManagerStyle.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 442 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/EntrustManager/Styles/DraedonManagerStyle.cs:667` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 3) Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipBoneProj.cs:153 — Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipBoneProj.cs:153-159 | Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipMorningStarProj.cs:177-183 | Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipReapProj.cs:124-130 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipBoneProj.cs:153` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 3) Content/HackTimes/Protocols/Cyberpsychosis.cs:20 — Content/HackTimes/Protocols/Cyberpsychosis.cs:20-26 | Content/HackTimes/Protocols/MemoryWipe.cs:20-26 | Content/HackTimes/Protocols/SystemReset.cs:21-27 — before extracting anything, compare `Content/HackTimes/Protocols/Cyberpsychosis.cs` and `Content/HackTimes/Protocols/MemoryWipe.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 39 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/HackTimes/Protocols/Cyberpsychosis.cs:20` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 3) Content/Items/Melee/StormGoddessSpears/AncientStormGoddessSpear.cs:322 — Content/Items/Melee/StormGoddessSpears/AncientStormGoddessSpear.cs:322-328 | Content/Items/Melee/StormGoddessSpears/AncientStormGoddessSpear.cs:487-493 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerLaser.cs:129-135 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/StormGoddessSpears/AncientStormGoddessSpear.cs:322` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:559 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:559-565 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaMiniBloodSlime.cs:193-199 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeBloodBee.cs:120-126 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:559` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 3) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs:101 — Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs:101-107 | Content/NPCs/FestersandSerpents/Projectiles/FssCascadeDrop.cs:72-78 | Content/NPCs/FestersandSerpents/Projectiles/FssIchorGlob.cs:99-105 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs` and `Content/NPCs/FestersandSerpents/Projectiles/FssCascadeDrop.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs:101` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 3) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs:138 — Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs:138-144 | Content/NPCs/FestersandSerpents/Projectiles/FssCascadeDrop.cs:97-103 | Content/NPCs/FestersandSerpents/Projectiles/FssIchorGlob.cs:136-142 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs` and `Content/NPCs/FestersandSerpents/Projectiles/FssCascadeDrop.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs:138` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 3) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Rendering/EmpressBeamDraw.cs:17 — Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Rendering/EmpressBeamDraw.cs:17-23 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Rendering/EmpressBeamDraw.cs:50-56 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Rendering/EmpressBeamDraw.cs:83-89 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Rendering/EmpressBeamDraw.cs:17` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • + 59 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×70
  • Edited copy of a member (16 corresponding lines) Content/PRTTypes/PRT_Light.cs:55 — Content/PRTTypes/PRT_Light.cs:55-72 | Content/PRTTypes/PRT_SoulLight.cs:61-78 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) Content/NPCs/BrutalNPCs/BrutalGolem/States/GolemDeathState.cs:360 — Content/NPCs/BrutalNPCs/BrutalGolem/States/GolemDeathState.cs:360-375 | Content/NPCs/BrutalNPCs/BrutalGolem/States/GolemDeathState.cs:378-393 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) Content/Industrials/ElectricPowers/ElectricMinRocket.cs:218 — Content/Industrials/ElectricPowers/ElectricMinRocket.cs:218-233 | Content/Industrials/MachineTP.cs:235-253 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) Content/Narrative/Presentation/Skins/Kikasa/KikasaDialogueSkin.cs:43 — Content/Narrative/Presentation/Skins/Kikasa/KikasaDialogueSkin.cs:43-58 | Content/Narrative/Presentation/Skins/Onikiri/OnikiriDialogueSkin.cs:43-58 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) Content/Items/Stones/Granites/GraniteEffects.cs:85 — Content/Items/Stones/Granites/GraniteEffects.cs:85-103 | Content/Items/Stones/Granites/GraniteFlower.cs:213-228 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Barrel/ObsidianBarrelModule.cs:209 — Content/LegendWeapon/SHPCLegend/Modules/Barrel/ObsidianBarrelModule.cs:209-224 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/ScattershotBarrelModule.cs:343-359 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerFrostPulseProj.cs:179 — Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerFrostPulseProj.cs:179-194 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Rendering/DeerclopsVeilFX.cs:88-104 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistParticles.cs:49 — Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistParticles.cs:49-68 | Content/PRTTypes/PRT_GraniteShard.cs:80-95 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) Content/Items/Accessories/BrutalRelics/Twins/PRT_TwinPupilSpark.cs:65 — Content/Items/Accessories/BrutalRelics/Twins/PRT_TwinPupilSpark.cs:65-80 | Content/PRTTypes/PRT_TwinsSpark.cs:66-84 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) Content/Items/Accessories/BrutalRelics/KingSlime/FallenCrownProj.cs:181 — Content/Items/Accessories/BrutalRelics/KingSlime/FallenCrownProj.cs:181-196 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSCrownProj.cs:440-460 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) Content/NPCs/BloomsandSerpents/BssVfx.cs:43 — Content/NPCs/BloomsandSerpents/BssVfx.cs:43-62 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Core/QueenMotion.cs:160-175 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) Content/Narrative/Presentation/Skins/Draedon/DraedonChoiceSkin.cs:45 — Content/Narrative/Presentation/Skins/Draedon/DraedonChoiceSkin.cs:45-60 | Content/Narrative/Presentation/Skins/StarStream/StarStreamPanelDraw.cs:70-91 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Optic/SniperOpticModule.cs:576 — Content/LegendWeapon/SHPCLegend/Modules/Optic/SniperOpticModule.cs:576-591 | Content/LegendWeapon/SHPCLegend/Modules/Stock/AssaultStockModule.cs:232-250 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) Content/HackTimes/Chips/HackChipGlyph.cs:135 — Content/HackTimes/Chips/HackChipGlyph.cs:135-150 | Content/Industrials/ElectricPowers/MiningMachines/MiningModuleGlyph.cs:130-146 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1468 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1468-1483 | Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:2263-2278 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) Content/Items/Melee/DestroyersBlade.cs:626 — Content/Items/Melee/DestroyersBlade.cs:626-641 | Content/Items/Melee/DestroyersBladeEXs/DestroyersBeamEX.cs:106-125 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersUIs/OceanRaidersRenderer.cs:76 — Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersUIs/OceanRaidersRenderer.cs:76-91 | Content/Scenarios/OldDuke/OldDuchests/OldDuchestUIs/OldDuchestRenderer.cs:103-118 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) Content/Items/Magic/Pandemoniums/PandemoniumLightning.cs:145 — Content/Items/Magic/Pandemoniums/PandemoniumLightning.cs:145-166 | Content/Items/Magic/Pandemoniums/PandemoniumLightning.cs:168-183 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) Content/Items/Magic/Pandemoniums/PandemoniumChannel.cs:850 — Content/Items/Magic/Pandemoniums/PandemoniumChannel.cs:850-865 | Content/Items/Magic/Pandemoniums/PandemoniumRSkill.cs:499-515 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) Content/LegendWeapon/HalibutLegend/DomainSkills/YourLevelIsTooLow.cs:760 — Content/LegendWeapon/HalibutLegend/DomainSkills/YourLevelIsTooLow.cs:760-779 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutDomain.cs:332-347 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenBallroomStepState.cs:142 — Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenBallroomStepState.cs:142-169 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenSpikeRondoState.cs:150-165 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) Content/Items/Melee/DragonsScaleGreatsword.cs:433 — Content/Items/Melee/DragonsScaleGreatsword.cs:433-449 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:433-448 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) Content/HackTimes/Protocols/BeaconForge.cs:155 — Content/HackTimes/Protocols/BeaconForge.cs:155-170 | Content/HackTimes/Protocols/GridBlackout.cs:38-54 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainBloodPulseState.cs:122 — Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainBloodPulseState.cs:122-138 | Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainOrbitCageState.cs:166-181 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) Content/Items/Melee/OniMacheteHands.cs:1198 — Content/Items/Melee/OniMacheteHands.cs:1198-1213 | Content/LegendWeapon/HalibutLegend/FishSkills/Fishotroning.cs:991-1018 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • + 45 more in this group — see findings.md.
D3 · God Classes · MethodTooLong · ×68
  • MethodTooLong: KikasaGunServant.UpdateGuns Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1040 — MethodTooLong — UpdateGuns runs 200 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 100 over it, 2.00× 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: OniMeiGlyph.BuildGlyphs Content/LegendWeapon/OnikiriLegend/UI/OniMeiGlyph.cs:85 — MethodTooLong — BuildGlyphs runs 189 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 89 over it, 1.89× 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: HackTime.SetStaticDefaults Content/HackTimes/HackTime.cs:234 — MethodTooLong — SetStaticDefaults runs 183 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 83 over it, 1.83× 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: OniSlash.UpdateBladePose Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:764 — MethodTooLong — UpdateBladePose runs 182 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 82 over it, 1.82× 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: DeepGaolWraith.UpdateCuffs Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:1642 — MethodTooLong — UpdateCuffs runs 179 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 79 over it, 1.79× 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: KikasaInkPour.AI Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPour.cs:161 — MethodTooLong — AI runs 178 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 78 over it, 1.78× 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: KikasaPanoramaUI.DrawHoverTipPanel Content/LegendWeapon/KikasaLegend/UI/Panorama/KikasaPanoramaUI.cs:2064 — MethodTooLong — DrawHoverTipPanel runs 175 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 75 over it, 1.75× 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: LegendTooltipPanel.Draw Content/LegendWeapon/LegendTooltipLayout.cs:290 — MethodTooLong — Draw runs 172 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 72 over it, 1.72× 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: ValidatePass.ApplyPass Content/Scenarios/Dungeonworld/Gen/Passes/ValidatePass.cs:21 — MethodTooLong — ApplyPass runs 172 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 72 over it, 1.72× 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: CultistPlanetProj.AI Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistPlanetProj.cs:126 — MethodTooLong — AI runs 170 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 70 over it, 1.70× 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: CrimsonSweepSlash.UpdateBladePose Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:609 — MethodTooLong — UpdateBladePose runs 162 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 62 over it, 1.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: CrimsonRendSlash.UpdateBladePose Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:808 — MethodTooLong — UpdateBladePose runs 153 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 53 over it, 1.53× 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: BssHubState.PickAttack Content/NPCs/BloomsandSerpents/States/BssHubState.cs:140 — MethodTooLong — PickAttack runs 147 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 47 over it, 1.47× 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: OldNetTexts.SetStaticDefaults Content/Scenarios/OldNet/OldNetTexts.cs:123 — MethodTooLong — SetStaticDefaults runs 143 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 43 over it, 1.43× 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: KikasaHud.DrawTooltipOverlay Content/LegendWeapon/KikasaLegend/UI/KikasaHud.cs:786 — MethodTooLong — DrawTooltipOverlay runs 142 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 42 over it, 1.42× 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: HadalValidatePass.ApplyPass Content/Scenarios/Hadalworld/Gen/Passes/HadalValidatePass.cs:17 — MethodTooLong — ApplyPass runs 142 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 42 over it, 1.42× 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: CultistConjunctionState.UpdateRelease Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistConjunctionState.cs:149 — MethodTooLong — UpdateRelease runs 141 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 41 over it, 1.41× 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: FishronVortexGrabState.OnUpdate Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronVortexGrabStates.cs:313 — MethodTooLong — OnUpdate runs 138 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× 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: KikasaOnikiriServant.UpdateBlade Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:805 — MethodTooLong — UpdateBlade runs 136 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 36 over it, 1.36× 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: KikasaTwinsServant.UpdateEyes Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:989 — MethodTooLong — UpdateEyes runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× 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: SHPCUI.Update Content/LegendWeapon/SHPCLegend/UI/SHPCUI.cs:472 — MethodTooLong — Update runs 134 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× 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: KikasaQueenBeeServant.UpdateRake Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:517 — MethodTooLong — UpdateRake runs 131 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 31 over it, 1.31× 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: TileNameFallbackRegistry.RegisterInitialData Content/HackTimes/TileNameFallbackRegistry.cs:79 — MethodTooLong — RegisterInitialData runs 130 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× 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: KikasaBladeServant.UpdateBlades Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:787 — MethodTooLong — UpdateBlades runs 130 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× 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: KikasaSkeletronServant.UpdateHands Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1050 — MethodTooLong — UpdateHands runs 130 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× 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.
  • + 43 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×65
  • Edited copy of a member (6 corresponding lines) Content/Narrative/Presentation/Skins/Sulfsea/SulfseaPanelDraw.cs:84 — Content/Narrative/Presentation/Skins/Sulfsea/SulfseaPanelDraw.cs:84-95 | Content/Narrative/Presentation/Skins/Sulfsea/SulfseaPanelDraw.cs:98-104 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamFogRender.cs:106 — Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamFogRender.cs:106-111 | Content/Scenarios/Kiyume/Fog/KiyumeGroundFogRender.cs:335-340 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) Content/UIs/StorageUIs/BaseChestRenderer.cs:183 — Content/UIs/StorageUIs/BaseChestRenderer.cs:183-189 | Content/UIs/WeaponSkills/WeaponSkillBrush.cs:39-44 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) Content/MainMenus/Himayo/HimayoMenuButtons.cs:119 — Content/MainMenus/Himayo/HimayoMenuButtons.cs:119-124 | Content/MainMenus/Shenyo/ShenyoMenuButtons.cs:121-126 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomSporeBoltProj.cs:49 — Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomSporeBoltProj.cs:49-56 | Content/Items/Magic/FocusingGrimoire.cs:385-390 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:975 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:975-980 | Content/NPCs/ScrapCommanders/ScrapCommander.cs:421-426 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:460 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:460-465 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:422-427 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) Content/LegendWeapon/HalibutLegend/DomainSkills/CloneFish.cs:471 — Content/LegendWeapon/HalibutLegend/DomainSkills/CloneFish.cs:471-477 | Content/LegendWeapon/HalibutLegend/DomainSkills/SeaDomain.cs:569-574 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) Content/Items/Accessories/BrutalRelics/EmpressOfLight/InterferenceWingRender.cs:85 — Content/Items/Accessories/BrutalRelics/EmpressOfLight/InterferenceWingRender.cs:85-90 | Content/Items/Accessories/BrutalRelics/Skeletron/SoulbindingArmRender.cs:110-115 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) Content/Industrials/ElectricPowers/ItemFilters/ItemFilterRenderer.cs:175 — Content/Industrials/ElectricPowers/ItemFilters/ItemFilterRenderer.cs:175-180 | Content/Scenarios/Draedon/PQCDs/DraedonShops/DraedonShopRenderer.cs:127-132 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) Content/Items/Stones/GraniteMarbleVFX.cs:89 — Content/Items/Stones/GraniteMarbleVFX.cs:89-94 | Content/Items/Stones/GraniteMarbleVFX.cs:99-105 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) Content/HackTimes/Scannables/ItemScannable.cs:134 — Content/HackTimes/Scannables/ItemScannable.cs:134-140 | Content/HackTimes/Scannables/ItemScannable.cs:161-166 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Optic/CrosslinkOpticModule.cs:24 — Content/LegendWeapon/SHPCLegend/Modules/Optic/CrosslinkOpticModule.cs:24-29 | Content/LegendWeapon/SHPCLegend/Modules/Optic/CrosslinkOpticModule.cs:31-38 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) Content/Items/Accessories/BrutalRelics/KingSlime/RoyalGelField.cs:53 — Content/Items/Accessories/BrutalRelics/KingSlime/RoyalGelField.cs:53-58 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSGelPoolProj.cs:62-69 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) Content/NPCs/BloomsandSerpents/BssLegRig.cs:336 — Content/NPCs/BloomsandSerpents/BssLegRig.cs:336-341 | Content/NPCs/FestersandSerpents/FssLegRig.cs:208-213 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) Content/Items/Stones/GraniteMarbleVFX.cs:66 — Content/Items/Stones/GraniteMarbleVFX.cs:66-74 | Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashStep.cs:198-203 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) Content/NPCs/BloomsandSerpents/BssClawScript.cs:87 — Content/NPCs/BloomsandSerpents/BssClawScript.cs:87-92 | Content/NPCs/BloomsandSerpents/BssClawScript.cs:202-207 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) Content/HackTimes/Protocols/ProjectileFreeze.cs:87 — Content/HackTimes/Protocols/ProjectileFreeze.cs:87-94 | Content/HackTimes/Protocols/Cryostasis.cs:179-184 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:874 — Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:874-880 | Content/Items/Modifys/RBloodButcherer.cs:812-817 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) Content/LegendWeapon/HalibutLegend/UI/HalibutRenderer.cs:113 — Content/LegendWeapon/HalibutLegend/UI/HalibutRenderer.cs:113-119 | Content/MainMenus/Overs/AckRenderer.cs:82-87 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBreathArc.cs:68 — Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBreathArc.cs:68-76 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleScar.cs:43-48 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) Content/GameModes/BrutalMobs/Ambience/Ashreign/Projectiles/AshreignAshStormProj.cs:35 — Content/GameModes/BrutalMobs/Ambience/Ashreign/Projectiles/AshreignAshStormProj.cs:35-40 | Content/GameModes/BrutalMobs/Ambience/Brinefume/Projectiles/BrinefumeHazeTideProj.cs:37-42 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) Content/Items/Magic/NeutronWands/NeutronWand.cs:259 — Content/Items/Magic/NeutronWands/NeutronWand.cs:259-265 | Content/Items/Ranged/AvalancheM60.cs:239-244 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) Content/PRTTypes/PRT_DefSmoke.cs:50 — Content/PRTTypes/PRT_DefSmoke.cs:50-58 | Content/PRTTypes/PRT_DefCryoMist.cs:72-77 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:909 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:909-914 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:917-923 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • + 40 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×61
  • Duplicated block (8 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:338 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:338-345 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:339-346 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:396-403 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs` as WHOLE FILES: this scan already matched 70 separate duplicated blocks between them, totalling at least 835 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:338` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 3) Content/Items/Ranged/NeutronBows/NeutronBow.cs:39 — Content/Items/Ranged/NeutronBows/NeutronBow.cs:39-46 | Content/Items/Ranged/Thornstrings/Thornstring.cs:25-32 | Content/Items/Ranged/Undertows/Undertow.cs:25-32 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (8 lines × 3) Content/LegendWeapon/HalibutLegend/FishSkills/FishDirt.cs:456 — Content/LegendWeapon/HalibutLegend/FishSkills/FishDirt.cs:456-463 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDirt.cs:486-493 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDirt.cs:514-521 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishDirt.cs:456` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:457 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:457-464 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:540-547 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:455-462 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs` as WHOLE FILES: this scan already matched 75 separate duplicated blocks between them, totalling at least 912 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:457` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:280 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:280-287 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:444-451 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:393-400 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:280` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 3) Content/Scenarios/OldNet/Tiles/OldNetBreakerTile.cs:108 — Content/Scenarios/OldNet/Tiles/OldNetBreakerTile.cs:108-115 | Content/Scenarios/OldNet/Tiles/OldNetSentryMineTile.cs:162-169 | Content/Scenarios/OldNet/Tiles/OldNetTripwireTile.cs:151-158 — before extracting anything, compare `Content/Scenarios/OldNet/Tiles/OldNetBreakerTile.cs` and `Content/Scenarios/OldNet/Tiles/OldNetSentryMineTile.cs` as WHOLE FILES: this scan already matched 5 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/OldNet/Tiles/OldNetBreakerTile.cs:108` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 3) Content/Items/Stones/Granites/GraniteThrowingKnife.cs:20 — Content/Items/Stones/Granites/GraniteThrowingKnife.cs:20-27 | Content/Items/Stones/Marbles/MarbleDisc.cs:20-27 | Content/Items/Stones/Marbles/MarblePebble.cs:19-26 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Stones/Granites/GraniteThrowingKnife.cs:20` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1286 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1286-1293 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1300-1307 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1588-1595 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1286` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 3) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1684 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1684-1691 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1356-1363 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1548-1555 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1684` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 3) Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:410 — Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:410-417 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleCut.cs:391-398 | Content/LegendWeapon/OnikiriLegend/OniZanshinSlashs/OniZanshinSlash.cs:500-507 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:410` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 3) Content/LegendWeapon/SHPCLegend/Modules/Barrel/HeavyBarrelModule.cs:299 — Content/LegendWeapon/SHPCLegend/Modules/Barrel/HeavyBarrelModule.cs:299-306 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/HypersonicBarrelModule.cs:193-200 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/ScattershotBarrelModule.cs:365-372 — before extracting anything, compare `Content/LegendWeapon/SHPCLegend/Modules/Barrel/HeavyBarrelModule.cs` and `Content/LegendWeapon/SHPCLegend/Modules/Barrel/HypersonicBarrelModule.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 91 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/SHPCLegend/Modules/Barrel/HeavyBarrelModule.cs:297` calls `IsPointOnScreen` and `Content/LegendWeapon/SHPCLegend/Modules/Barrel/HypersonicBarrelModule.cs:191` does not — after which the two agree again for 3 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) Content/NPCs/SeaShrimp/Projectiles/SeaShrimpCavitationBubble.cs:98 — Content/NPCs/SeaShrimp/Projectiles/SeaShrimpCavitationBubble.cs:98-105 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpSparkBubble.cs:168-175 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpVoltBubble.cs:152-159 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpCavitationBubble.cs:98` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpVoltBubble.cs:149` calls `PlaySound` and `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpSparkBubble.cs:166` 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) Content/Scenarios/Kiame/KiameWakeResetRender.cs:54 — Content/Scenarios/Kiame/KiameWakeResetRender.cs:54-61 | Content/Scenarios/Kiame/Overlay/OniRainDescentRender.cs:60-67 | Content/Scenarios/Kiame/Overlay/OniRainWorldRender.cs:33-40 — before extracting anything, compare `Content/Scenarios/Kiame/KiameWakeResetRender.cs` and `Content/Scenarios/Kiame/Overlay/OniRainDescentRender.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 3) Content/Cyberwares/Implementation/PlowSteelClampArms/MonomolecularWire.cs:248 — Content/Cyberwares/Implementation/PlowSteelClampArms/MonomolecularWire.cs:248-255 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPour.cs:456-463 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuLongFX.cs:122-129 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 3) Content/GameModes/GodSmith/Armors/Reset/GsOreArmorsHardmode.cs:273 — Content/GameModes/GodSmith/Armors/Reset/GsOreArmorsHardmode.cs:273-280 | Content/GameModes/GodSmith/Armors/Reset/GsShroomiteArmor.cs:148-155 | Content/GameModes/GodSmith/Armors/Reset/GsSpiderArmor.cs:75-82 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/GameModes/GodSmith/Armors/Reset/GsShroomiteArmor.cs:157` calls `AddLight` and `Content/GameModes/GodSmith/Armors/Reset/GsSpiderArmor.cs:84` does not — after which the two agree again for 3 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) Content/GameModes/GodSmith/Weapons/Broadswords/GsCobaltSword.cs:206 — Content/GameModes/GodSmith/Weapons/Broadswords/GsCobaltSword.cs:206-213 | Content/GameModes/GodSmith/Weapons/Broadswords/GsLightsBane.cs:117-124 | Content/GameModes/GodSmith/Weapons/Broadswords/GsTitaniumSword.cs:161-168 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/Broadswords/GsCobaltSword.cs:206` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 3) Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipBoneProj.cs:155 — Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipBoneProj.cs:155-162 | Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipLeatherCrackProj.cs:54-61 | Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipReapProj.cs:126-133 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipBoneProj.cs:155` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 3) Content/Items/Magic/Elysiums/Disciples/James.cs:41 — Content/Items/Magic/Elysiums/Disciples/James.cs:41-48 | Content/Items/Magic/Elysiums/Disciples/Thaddaeus.cs:105-112 | Content/Items/Magic/Elysiums/Serpents/HolySerpent.cs:264-271 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/Elysiums/Disciples/James.cs:41` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:672 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:672-679 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1194-1201 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:622-629 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs` as WHOLE FILES: this scan already matched 68 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:672` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 3) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowDevourState.cs:446 — Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowDevourState.cs:446-453 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Core/WofWallField.cs:213-220 | Content/Scenarios/OldNet/NPCs/OldNetTracerICE.cs:160-167 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 3) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistPhaseSkyEffect.cs:179 — Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistPhaseSkyEffect.cs:179-186 | Content/Wraiths/Abilities/CrimsonBrides/BrideHallSky.cs:174-181 | Content/Wraiths/Abilities/GhostRains/GhostRainAmbience.cs:175-182 — before extracting anything, compare `Content/Wraiths/Abilities/CrimsonBrides/BrideHallSky.cs` and `Content/Wraiths/Abilities/GhostRains/GhostRainAmbience.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistPhaseSkyEffect.cs:179` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 3) Content/NPCs/BrutalNPCs/BrutalQueenBee/States/QBSwarmArrowState.cs:129 — Content/NPCs/BrutalNPCs/BrutalQueenBee/States/QBSwarmArrowState.cs:129-136 | Content/NPCs/BrutalNPCs/BrutalQueenBee/States/QBSwarmVortexState.cs:141-148 | Content/NPCs/BrutalNPCs/BrutalQueenBee/States/QBSwarmWallState.cs:108-115 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalQueenBee/States/QBSwarmArrowState.cs:129` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 3) Content/Scenarios/Draedon/ExoMechdusaSums/ExoMechdusaSumRender.cs:581 — Content/Scenarios/Draedon/ExoMechdusaSums/ExoMechdusaSumRender.cs:581-588 | Content/Scenarios/Draedon/Quest/DeploySignaltowers/DeploySignaltowerRender.cs:761-768 | Content/UIs/UIEffect/TechPRT.cs:17-24 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (8 lines × 3) Content/EntrustManager/Styles/DraedonManagerStyle.cs:201 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:201-208 | Content/EntrustManager/Styles/ForestManagerStyle.cs:238-245 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:223-230 — before extracting anything, compare `Content/EntrustManager/Styles/DraedonManagerStyle.cs` and `Content/EntrustManager/Styles/ForestManagerStyle.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 334 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 (8 lines × 3) Content/GameModes/BrutalMobs/DungeonDeep/DungeonDeepNPC.Melee.cs:53 — Content/GameModes/BrutalMobs/DungeonDeep/DungeonDeepNPC.Melee.cs:53-60 | Content/GameModes/BrutalMobs/FrostLegion/FrostLegionNPC.cs:519-526 | Content/GameModes/BrutalMobs/Graveyard/GraveyardBrutalNPC.cs:394-401 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/DungeonDeep/DungeonDeepNPC.Melee.cs:53` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • + 36 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (19 corresponding lines) · ×58
  • Edited copy of a member (19 corresponding lines) Content/EntrustManager/Styles/ForestManagerStyle.cs:390 — Content/EntrustManager/Styles/ForestManagerStyle.cs:390-408 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:379-397 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Content/Items/Melee/CursedflameBloodfists/CursedflamePRT.cs:111 — Content/Items/Melee/CursedflameBloodfists/CursedflamePRT.cs:111-129 | Content/PRTTypes/PRT_PallbearerEmber.cs:56-74 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Content/Scenarios/Kiyume/NPCs/KiyumeHoundDirector.cs:235 — Content/Scenarios/Kiyume/NPCs/KiyumeHoundDirector.cs:235-292 | Content/Scenarios/Kiyume/NPCs/KiyumeWhiteHound.cs:385-406 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Content/NPCs/Victors/UIs/VictorClinicPanel.cs:498 — Content/NPCs/Victors/UIs/VictorClinicPanel.cs:498-520 | Content/NPCs/Victors/UIs/VictorClinicPanel.cs:522-540 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Content/GameModes/BrutalMobs/Ambience/Duskhall/DuskhallAmbience.cs:235 — Content/GameModes/BrutalMobs/Ambience/Duskhall/DuskhallAmbience.cs:235-253 | Content/Scenarios/Dungeonworld/Ambience/DungeonworldAmbientFX.cs:130-153 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Common/ShockRingDraw.cs:79 — Common/ShockRingDraw.cs:79-107 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteRingRender.cs:148-166 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:199 — Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:199-217 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpJetBeam.cs:224-242 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Content/EntrustManager/BaseQuestAcceptUI.cs:537 — Content/EntrustManager/BaseQuestAcceptUI.cs:537-555 | Content/UIs/OverhaulSettings/OverhaulSettingsUI.cs:961-980 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Content/LegendWeapon/OnikiriLegend/UI/OniMeiCodexRenderer.cs:371 — Content/LegendWeapon/OnikiriLegend/UI/OniMeiCodexRenderer.cs:371-391 | Content/LegendWeapon/OnikiriLegend/UI/OniMeiCodexRenderer.cs:486-504 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Content/Items/Magic/WheezingWyrms/WyrmfirePRT.cs:154 — Content/Items/Magic/WheezingWyrms/WyrmfirePRT.cs:154-173 | Content/Items/Melee/CursedflameBloodfists/CursedflamePRT.cs:111-129 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Content/Items/Melee/DawnshatterAzures/DawnshatterPRT.cs:64 — Content/Items/Melee/DawnshatterAzures/DawnshatterPRT.cs:64-83 | Content/PRTTypes/PRT_PallbearerEmber.cs:56-74 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Content/Items/BloomArsenal.cs:192 — Content/Items/BloomArsenal.cs:192-210 | Content/NPCs/BloomsandSerpents/Projectiles/BssNeedleProj.cs:57-75 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Content/Items/Melee/TideReapers/TideReaper.cs:290 — Content/Items/Melee/TideReapers/TideReaper.cs:290-311 | Content/Items/Melee/TideReapers/TideReaperWave.cs:97-115 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Content/NPCs/BloomsandSerpents/States/BssFinHuntState.cs:156 — Content/NPCs/BloomsandSerpents/States/BssFinHuntState.cs:156-177 | Content/NPCs/FestersandSerpents/FssLegRig.cs:420-438 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Content/Items/Accessories/BrutalRelics/EmpressOfLight/InterferenceBursts.cs:46 — Content/Items/Accessories/BrutalRelics/EmpressOfLight/InterferenceBursts.cs:46-64 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Projectiles/EmpressBloomBurst.cs:38-63 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Rendering/EowMotionFX.cs:140 — Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Rendering/EowMotionFX.cs:140-158 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Rendering/EowMotionFX.cs:161-181 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Content/Items/Magic/Pandemoniums/PandemoniumCircle.cs:240 — Content/Items/Magic/Pandemoniums/PandemoniumCircle.cs:240-271 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumCircle.cs:300-318 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Content/Items/Melee/CursedflameBloodfists/CursedflameBloodfistHeld.cs:293 — Content/Items/Melee/CursedflameBloodfists/CursedflameBloodfistHeld.cs:293-312 | Content/Items/Melee/CursedflameBloodfists/CursedflameFistProj.cs:90-108 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Frame/MultiCellFrameModule.cs:235 — Content/LegendWeapon/SHPCLegend/Modules/Frame/MultiCellFrameModule.cs:235-255 | Content/LegendWeapon/SHPCLegend/Modules/Grip/EfficientGripModule.cs:452-470 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:457 — Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:457-478 | Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:480-498 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraFrenzyPounceState.cs:77 — Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraFrenzyPounceState.cs:77-95 | Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraGrapplePounceState.cs:80-100 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Content/Scenarios/OldNet/Gen/Passes/OldNetZonePlanPass.cs:59 — Content/Scenarios/OldNet/Gen/Passes/OldNetZonePlanPass.cs:59-79 | Content/Scenarios/OldNet/Gen/Passes/OldNetZonePlanPass.cs:82-100 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Content/Industrials/ElectricPowers/LifeWeavers/LifeWeaverAcorn.cs:181 — Content/Industrials/ElectricPowers/LifeWeavers/LifeWeaverAcorn.cs:181-207 | Content/Industrials/ElectricPowers/Lumberjacks/LumberjackModeIndicator.cs:134-152 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetNet.cs:33 — Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetNet.cs:33-52 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetNet.cs:33-51 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Content/Items/Magic/MelodyTheSand.cs:81 — Content/Items/Magic/MelodyTheSand.cs:81-101 | Content/Items/Magic/SandVortexOfTheDecayedSea.cs:76-94 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • + 33 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×56
  • Edited copy of a member (17 corresponding lines) Content/LegendWeapon/OnikiriLegend/UI/OniMeiRenderer.cs:130 — Content/LegendWeapon/OnikiriLegend/UI/OniMeiRenderer.cs:130-183 | Content/LegendWeapon/OnikiriLegend/UI/OniMeiRenderer.cs:455-498 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) Content/EntrustManager/BaseQuestAcceptUI.cs:519 — Content/EntrustManager/BaseQuestAcceptUI.cs:519-535 | Content/UIs/OverhaulSettings/OverhaulSettingsUI.cs:939-959 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) Content/Items/Accessories/GodslayerScabbard.cs:167 — Content/Items/Accessories/GodslayerScabbard.cs:167-183 | Content/Items/Accessories/GodslayerScabbard.cs:194-219 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaWisps/KikasaWispBurn.cs:19 — Content/LegendWeapon/KikasaLegend/KikasaWisps/KikasaWispBurn.cs:19-38 | Content/LegendWeapon/KikasaLegend/KikasaWisps/KikasaWispFX.cs:167-183 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) Content/Industrials/MachineTileDraw.cs:20 — Content/Industrials/MachineTileDraw.cs:20-45 | Content/Tiles/FoodStallChair.cs:92-108 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:428 — Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:428-444 | Content/Items/Modifys/RBloodButcherer.cs:438-456 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) Content/Items/Magic/Eyetooths/EyetoothVFX.cs:48 — Content/Items/Magic/Eyetooths/EyetoothVFX.cs:48-64 | Content/Items/Magic/Eyetooths/EyetoothVFX.cs:113-132 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuXiaFX.cs:20 — Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuXiaFX.cs:20-36 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuYuFX.cs:115-132 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiNueDive.cs:231 — Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiNueDive.cs:231-247 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiStrikes.cs:540-557 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclFrankSparkProj.cs:77 — Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclFrankSparkProj.cs:77-96 | Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornArcResidue.cs:58-74 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) Content/EntrustManager/Styles/ForestManagerStyle.cs:644 — Content/EntrustManager/Styles/ForestManagerStyle.cs:644-662 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:634-650 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailHead.cs:169 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailHead.cs:169-191 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipLash.cs:109-125 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) Content/Narrative/Presentation/Skins/SHPC/SHPCDialogueSkin.cs:133 — Content/Narrative/Presentation/Skins/SHPC/SHPCDialogueSkin.cs:133-163 | Content/Narrative/Presentation/Skins/Sea/SeaDialogueSkin.cs:74-90 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) Content/Items/Stones/GraniteMarbleVFX.cs:109 — Content/Items/Stones/GraniteMarbleVFX.cs:109-125 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDoubleCodVFX.cs:46-63 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) Content/Scenarios/Dungeonworld/NPCs/GaolDormantSkull.cs:274 — Content/Scenarios/Dungeonworld/NPCs/GaolDormantSkull.cs:274-290 | Content/Scenarios/Dungeonworld/NPCs/UndrownedThrone.cs:373-391 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1218 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1218-1234 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1290-1307 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSGelGlobProj.cs:31 — Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSGelGlobProj.cs:31-50 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Projectiles/HoneyGlobProj.cs:31-47 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) Content/GameModes/GodSmith/Armors/Reset/GsEskimoArmors.cs:30 — Content/GameModes/GodSmith/Armors/Reset/GsEskimoArmors.cs:30-46 | Content/GameModes/GodSmith/Armors/Reset/GsFrostArmor.cs:55-71 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) Content/Items/Ranged/Starships/StarshipMaxRateRing.cs:44 — Content/Items/Ranged/Starships/StarshipMaxRateRing.cs:44-60 | Content/Items/Ranged/Starships/StarshipMicroGalaxy.cs:115-131 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) Content/GameModes/GodSmith/Weapons/Broadswords/GsFrostbrand.cs:78 — Content/GameModes/GodSmith/Weapons/Broadswords/GsFrostbrand.cs:78-98 | Content/GameModes/GodSmith/Weapons/Broadswords/GsIceBlade.cs:60-76 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomNeedle.cs:71 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomNeedle.cs:71-89 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeStinger.cs:168-184 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) Content/NPCs/BloomsandSerpents/Projectiles/BssDashOmen.cs:81 — Content/NPCs/BloomsandSerpents/Projectiles/BssDashOmen.cs:81-97 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronTelegraph.cs:82-100 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryWatcher.cs:228 — Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryWatcher.cs:228-244 | Content/Scenarios/Dungeonworld/Gen/BossRooms/ProofingHallWatcher.cs:199-221 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) Content/MainMenus/Shenyo/ShenyoGhostLakeScene.cs:397 — Content/MainMenus/Shenyo/ShenyoGhostLakeScene.cs:397-413 | Content/MainMenus/Shenyo/ShenyoGhostLakeScene.cs:693-713 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) Content/GameModes/BrutalMobs/EvilBiome/Projectiles/ErosionCloudSeed.cs:81 — Content/GameModes/BrutalMobs/EvilBiome/Projectiles/ErosionCloudSeed.cs:81-98 | Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilCursedBeadProj.cs:70-86 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • + 31 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (5 corresponding lines) · ×55
  • Edited copy of a member (5 corresponding lines) Content/LegendWeapon/OnikiriLegend/UI/OniMeiCodexRenderer.cs:632 — Content/LegendWeapon/OnikiriLegend/UI/OniMeiCodexRenderer.cs:632-638 | Content/LegendWeapon/OnikiriLegend/UI/OniMeiRenderer.cs:696-701 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Content/Industrials/UIs/IndustrialTerminalRenderer.cs:77 — Content/Industrials/UIs/IndustrialTerminalRenderer.cs:77-81 | Content/MainMenus/Characters/CharacterDockRenderer.cs:45-49 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Content/Cyberwares/Implementation/OmniElectricFoots/OmniElectricFootHUD.cs:292 — Content/Cyberwares/Implementation/OmniElectricFoots/OmniElectricFootHUD.cs:292-297 | Content/Cyberwares/Implementation/PlowSteelClampArms/MonomolecularWire.cs:238-242 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkMortarMarkerProj.cs:128 — Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkMortarMarkerProj.cs:128-137 | Content/GameModes/GodSmith/Weapons/MagicConduit/GsHeatPlayer.cs:181-185 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Content/NPCs/FestersandSerpents/FssClawRig.cs:250 — Content/NPCs/FestersandSerpents/FssClawRig.cs:250-257 | Content/NPCs/FestersandSerpents/FssClawRig.cs:259-263 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Content/Scenarios/Himayo/Gifts/HimayoBossRushGift.cs:25 — Content/Scenarios/Himayo/Gifts/HimayoBossRushGift.cs:25-29 | Content/Scenarios/Himayo/Gifts/HimayoCultistGift.cs:24-28 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Content/Narrative/Common/BaseDamageTracker.cs:197 — Content/Narrative/Common/BaseDamageTracker.cs:197-201 | Content/Narrative/Common/BaseDamageTracker.cs:203-207 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Content/GameModes/Blessings/UI/BlessingRenderer.cs:240 — Content/GameModes/Blessings/UI/BlessingRenderer.cs:240-244 | Content/GameModes/Blessings/UI/BlessingRenderer.cs:250-255 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberPrismLaserProj.cs:203 — Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberPrismLaserProj.cs:203-209 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDataArcProj.cs:99-103 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Projectiles/EmpressEcho.cs:82 — Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Projectiles/EmpressEcho.cs:82-86 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Projectiles/EmpressLance.cs:175-182 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Content/GameModes/GodSmith/Weapons/MagicChant/Projectiles/GsChantStormChoirProj.cs:31 — Content/GameModes/GodSmith/Weapons/MagicChant/Projectiles/GsChantStormChoirProj.cs:31-35 | Content/GameModes/GodSmith/Weapons/MagicChant/Projectiles/GsChantFlameFieldProj.cs:31-35 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Content/NPCs/BloomsandSerpents/Projectiles/BssDustDevilProj.cs:40 — Content/NPCs/BloomsandSerpents/Projectiles/BssDustDevilProj.cs:40-44 | Content/NPCs/BloomsandSerpents/Projectiles/BssSandSurgeProj.cs:32-36 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Content/Narrative/Presentation/Skins/Kikasa/KikasaChoiceSkin.cs:45 — Content/Narrative/Presentation/Skins/Kikasa/KikasaChoiceSkin.cs:45-49 | Content/Narrative/Presentation/Skins/Onikiri/OnikiriChoiceSkin.cs:40-44 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Content/LegendWeapon/OnikiriLegend/OniBladeProfile.cs:161 — Content/LegendWeapon/OnikiriLegend/OniBladeProfile.cs:161-166 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBladeEngrave.cs:324-328 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Content/LegendWeapon/OnikiriLegend/OniDismembers/OniDismemberNPC.cs:213 — Content/LegendWeapon/OnikiriLegend/OniDismembers/OniDismemberNPC.cs:213-217 | Content/LegendWeapon/OnikiriLegend/OniDismembers/OniPlayerDismember.cs:678-682 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Content/Narrative/Presentation/Skins/Sulfsea/SulfseaChoiceSkin.cs:24 — Content/Narrative/Presentation/Skins/Sulfsea/SulfseaChoiceSkin.cs:24-28 | Content/Narrative/Presentation/Skins/Tzeentch/TzeentchChoiceSkin.cs:24-28 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Content/Items/Tools/EncyclopediaofOceanicKnowledge.cs:385 — Content/Items/Tools/EncyclopediaofOceanicKnowledge.cs:385-390 | Content/Items/Tools/TheForgottenTome.cs:320-324 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraKiriPlayerProj.cs:841 — Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraKiriPlayerProj.cs:841-845 | Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraSlashProj.cs:227-235 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraSlashProj.cs:238 — Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraSlashProj.cs:238-246 | Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraKiriPlayerProj.cs:849-853 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPour.cs:139 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPour.cs:139-144 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkGeyser.cs:117-121 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:468 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:468-472 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:438-442 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Content/Scenarios/Dungeonworld/NPCs/Elites/LampeaterWisp.cs:465 — Content/Scenarios/Dungeonworld/NPCs/Elites/LampeaterWisp.cs:465-469 | Content/Scenarios/Dungeonworld/NPCs/Elites/LanternWarden.cs:614-618 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Content/Industrials/ElectricPowers/Lumberjacks/Lumberjack.cs:19 — Content/Industrials/ElectricPowers/Lumberjacks/Lumberjack.cs:19-24 | Content/Industrials/ElectricPowers/Collectors/Collector.cs:24-28 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs:504 — Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs:504-510 | Content/Industrials/ElectricPowers/Lumberjacks/WGGLumberjack.cs:827-831 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Content/HackTimes/Scannables/WaterScannable.cs:206 — Content/HackTimes/Scannables/WaterScannable.cs:206-210 | Content/Items/Stones/Marbles/MarbleClub.cs:396-402 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • + 30 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×54
  • Edited copy of a member (18 corresponding lines) Content/Cyberwares/UIs/CyberInventoryPanel.cs:328 — Content/Cyberwares/UIs/CyberInventoryPanel.cs:328-360 | Content/NPCs/Victors/UIs/VictorClinicPanel.cs:409-426 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) Content/Scenarios/Shepel/CybCourses/CybCourseCompletePanel.cs:140 — Content/Scenarios/Shepel/CybCourses/CybCourseCompletePanel.cs:140-157 | Content/Scenarios/Shepel/CybCourses/CybCourseKeyBindReminderPanel.cs:180-200 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:352 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:352-374 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs:368-385 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberTraceBeamProj.cs:496 — Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberTraceBeamProj.cs:496-521 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberTraceBeamProj.cs:573-590 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) Content/Narrative/Presentation/Skins/Brimstone/BrimstoneDialogueSkin.cs:76 — Content/Narrative/Presentation/Skins/Brimstone/BrimstoneDialogueSkin.cs:76-93 | Content/Narrative/Presentation/Skins/StarStream/StarStreamDialogueSkin.cs:83-105 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) Content/GameModes/BrutalMobs/Ambience/Fleshfen/FleshfenHazeRender.cs:185 — Content/GameModes/BrutalMobs/Ambience/Fleshfen/FleshfenHazeRender.cs:185-204 | Content/GameModes/BrutalMobs/Ambience/Fleshfen/FleshfenHazeRender.cs:207-224 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) Content/Industrials/ElectricPowers/LifeWeavers/WGGLifeWeaver.cs:462 — Content/Industrials/ElectricPowers/LifeWeavers/WGGLifeWeaver.cs:462-480 | Content/Industrials/ElectricPowers/Lumberjacks/WGGLumberjack.cs:709-726 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuWenFX.cs:229 — Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuWenFX.cs:229-249 | Content/Wraiths/Projectiles/GhostHandProj.cs:689-706 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBanishParticles.cs:53 — Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBanishParticles.cs:53-70 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreezeParticles.cs:51-72 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) Content/NPCs/ScrapCommanders/Projectiles/ScrapMortarShell.cs:116 — Content/NPCs/ScrapCommanders/Projectiles/ScrapMortarShell.cs:116-133 | Content/NPCs/ScrapCommanders/Projectiles/ScrapShellFrag.cs:59-76 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishIchornVFX.cs:76 — Content/LegendWeapon/HalibutLegend/FishSkills/FishIchornVFX.cs:76-94 | Content/LegendWeapon/HalibutLegend/FishSkills/FishTunabeardVFX.cs:82-99 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) Content/NPCs/BloomsandSerpents/BssSandPillar.cs:632 — Content/NPCs/BloomsandSerpents/BssSandPillar.cs:632-649 | Content/NPCs/BloomsandSerpents/Projectiles/BssBreachOmen.cs:120-138 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1738 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1738-1756 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:1181-1198 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuLaoFX.cs:119 — Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuLaoFX.cs:119-136 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuXiFX.cs:166-183 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) Content/NPCs/TBUGs/TBUG.cs:335 — Content/NPCs/TBUGs/TBUG.cs:335-352 | Content/NPCs/Victors/Victor.cs:164-181 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) Content/Items/Summon/BloomCallers/BloomCallerSprout.cs:161 — Content/Items/Summon/BloomCallers/BloomCallerSprout.cs:161-178 | Content/Items/Summon/Deepclaws/DeepclawLobster.cs:179-196 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:1071 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:1071-1088 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:1080-1097 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) Content/Items/Melee/NeutronGlaive.cs:810 — Content/Items/Melee/NeutronGlaive.cs:810-829 | Content/Items/Melee/NeutronGlaive.cs:961-978 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishSlime.cs:726 — Content/LegendWeapon/HalibutLegend/FishSkills/FishSlime.cs:726-748 | Content/LegendWeapon/HalibutLegend/FishSkills/FishVariegatedLard.cs:393-410 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) Content/Scenarios/Kiyume/NPCs/LanternGuideYokai.cs:263 — Content/Scenarios/Kiyume/NPCs/LanternGuideYokai.cs:263-280 | Content/Scenarios/Kiyume/NPCs/RidgeWalkerYokai.cs:319-339 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) Content/Industrials/ElectricPowers/Sensors/SensorTP.cs:220 — Content/Industrials/ElectricPowers/Sensors/SensorTP.cs:220-242 | Content/Industrials/ElectricPowers/WireInterfaces/WireInterfaceTP.cs:94-111 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) ModCall.cs:196 — ModCall.cs:196-213 | ModCall.cs:215-235 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) Content/HackTimes/HackStatusDisplay.cs:166 — Content/HackTimes/HackStatusDisplay.cs:166-183 | Content/HackTimes/HackStatusDisplay.cs:185-203 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) Content/Tiles/BloodAltars/BloodAltarFx.cs:98 — Content/Tiles/BloodAltars/BloodAltarFx.cs:98-116 | Content/Tiles/BloodAltars/BloodAltarFx.cs:141-158 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/Arms/PrimeSawStates.cs:167 — Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/Arms/PrimeSawStates.cs:167-184 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/Arms/PrimeViceStates.cs:131-153 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • + 29 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×54
  • Duplicated block (14 lines × 2) Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:120 — Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:120-133 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerIceSpikeProj.cs:107-120 — before extracting anything, compare `Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs` and `Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerIceSpikeProj.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 189 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:120` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:126 — Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:126-139 | Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:84-97 — before extracting anything, compare `Content/QuestLogs/Styles/DraedonQuestLogStyle.cs` and `Content/QuestLogs/Styles/HotwindQuestLogStyle.cs` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 377 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 (14 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:301 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:301-314 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:345-358 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:301` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallMeltFX.cs:398 — Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallMeltFX.cs:398-411 | Content/Scenarios/Kiame/KasaOnis/KasaOniActor.cs:891-904 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallMeltFX.cs:398` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (14 lines × 2) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerDespawnState.cs:123 — Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerDespawnState.cs:123-136 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsDeathState.cs:85-98 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerDespawnState.cs` and `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsDeathState.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 111 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerDespawnState.cs:123` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `context` to `DestroyerStateContext` in one and `TwinsStateContext` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsDeathState.cs:101` calls `RecordPerformanceKill` and `Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerDespawnState.cs:137` does not — after which the two agree again for 3 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 × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:466 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:466-479 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:561-574 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs` as WHOLE FILES: this scan already matched 70 separate duplicated blocks between them, totalling at least 835 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:466` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) Content/LegendWeapon/SHPCLegend/TrialQuests/SHPCTrackerWidgetStyle.cs:52 — Content/LegendWeapon/SHPCLegend/TrialQuests/SHPCTrackerWidgetStyle.cs:52-65 | Content/Scenarios/Draedon/Quest/DraedonTrackerWidgetStyle.cs:51-64 — before extracting anything, compare `Content/LegendWeapon/SHPCLegend/TrialQuests/SHPCTrackerWidgetStyle.cs` and `Content/Scenarios/Draedon/Quest/DraedonTrackerWidgetStyle.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 103 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (14 lines × 2) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowGeyserProj.cs:54 — Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowGeyserProj.cs:54-67 | Content/NPCs/FestersandSerpents/Projectiles/FssGeyserColumn.cs:54-67 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowGeyserProj.cs` and `Content/NPCs/FestersandSerpents/Projectiles/FssGeyserColumn.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 156 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowGeyserProj.cs:54` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (14 lines × 2) Content/NPCs/ScrapCommanders/States/ScrapAllOutCommandState.cs:38 — Content/NPCs/ScrapCommanders/States/ScrapAllOutCommandState.cs:38-51 | Content/NPCs/ScrapCommanders/States/ScrapSawCannonComboState.cs:54-67 — 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 (14 lines × 2) Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs:523 — Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs:523-536 | Content/Scenarios/Shenyo/ShenyoPortraitRainRenderer.cs:514-527 — before extracting anything, compare `Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs` and `Content/Scenarios/Shenyo/ShenyoPortraitRainRenderer.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 211 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (14 lines × 2) Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:517 — Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:517-530 | Content/Items/Melee/WeaverGrievanceses/WGManifestationActor.cs:427-440 — before extracting anything, compare `Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs` and `Content/Items/Melee/WeaverGrievanceses/WGManifestationActor.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 237 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:517` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (14 lines × 2) Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:520 — Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:520-533 | Content/Items/Modifys/RBloodButcherer.cs:459-472 — before extracting anything, compare `Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs` and `Content/Items/Modifys/RBloodButcherer.cs` as WHOLE FILES: this scan already matched 36 separate duplicated blocks between them, totalling at least 458 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:520` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainNet.cs:64 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainNet.cs:64-77 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainNet.cs:50-63 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainNet.cs:64` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Rendering/TwinsRenderHelper.cs:793 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Rendering/TwinsRenderHelper.cs:793-806 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Rendering/TwinsRenderHelper.cs:940-953 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Rendering/TwinsRenderHelper.cs:793` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (14 lines × 2) Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersTP.cs:362 — Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersTP.cs:362-375 | Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersVortexEffect.cs:151-164 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersTP.cs:362` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (14 lines × 2) Content/GameModes/BrutalMobs/FrostMoon/FrmMeleeNPC.cs:270 — Content/GameModes/BrutalMobs/FrostMoon/FrmMeleeNPC.cs:270-283 | Content/GameModes/BrutalMobs/FrostMoon/FrmSiegeNPC.cs:199-212 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/FrostMoon/FrmMeleeNPC.cs:270` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) Content/Items/Magic/CommandersStaff.cs:23 — Content/Items/Magic/CommandersStaff.cs:23-36 | Content/Items/Magic/CommandersStaff.cs:56-69 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Magic/CommandersStaff.cs:39` calls `CWR` and `Content/Items/Magic/CommandersStaff.cs:72` 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 × 2) Content/Items/Melee/Observer.cs:26 — Content/Items/Melee/Observer.cs:26-39 | Content/Items/Melee/SporeboundRoller.cs:29-42 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Observer.cs:26` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) Content/Items/Ranged/DarkFrostSolstice.cs:294 — Content/Items/Ranged/DarkFrostSolstice.cs:294-307 | Content/Items/Ranged/DarkFrostSolstice.cs:310-323 — 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 (14 lines × 2) Content/Items/Tools/EncyclopediaofOceanicKnowledge.cs:193 — Content/Items/Tools/EncyclopediaofOceanicKnowledge.cs:193-206 | Content/Items/Tools/TheForgottenTome.cs:152-165 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Tools/EncyclopediaofOceanicKnowledge.cs:193` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (14 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:964 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:964-977 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:941-954 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:964` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistCometProj.cs:118 — Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistCometProj.cs:118-131 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistFallingStar.cs:151-164 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistCometProj.cs:118` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) Content/NPCs/TBUGs/TBUG.cs:335 — Content/NPCs/TBUGs/TBUG.cs:335-348 | Content/NPCs/Victors/Victor.cs:164-177 — before extracting anything, compare `Content/NPCs/TBUGs/TBUG.cs` and `Content/NPCs/Victors/Victor.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 117 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/TBUGs/TBUG.cs:335` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolRoomAmbienceRender.cs:50 — Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolRoomAmbienceRender.cs:50-63 | Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolRoomAmbienceRender.cs:89-102 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolRoomAmbienceRender.cs:50` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (14 lines × 2) Content/Scenarios/Kiame/Overlay/OniRainDescentRender.cs:69 — Content/Scenarios/Kiame/Overlay/OniRainDescentRender.cs:69-82 | Content/Scenarios/Kiame/Overlay/OniRainWorldRender.cs:43-56 — before extracting anything, compare `Content/Scenarios/Kiame/Overlay/OniRainDescentRender.cs` and `Content/Scenarios/Kiame/Overlay/OniRainWorldRender.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 98 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Kiame/Overlay/OniRainDescentRender.cs:69` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • + 29 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (6 lines × 4) · ×54
  • Duplicated block (6 lines × 4) Content/HackTimes/Targets/BossPartTargetType.cs:93 — Content/HackTimes/Targets/BossPartTargetType.cs:93-98 | Content/HackTimes/Targets/ItemTargetType.cs:32-37 | Content/HackTimes/Targets/NpcTargetType.cs:32-37 | Content/HackTimes/Targets/ProjectileTargetType.cs:32-37 — 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 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Content/HackTimes/Targets/BossPartTargetType.cs:93` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 4) Content/Scenarios/SupCal/End/EternalBlazingNow/EbnEffect.cs:328 — Content/Scenarios/SupCal/End/EternalBlazingNow/EbnEffect.cs:328-333 | Content/Scenarios/SupCal/End/EternalBlazingNow/EbnEffect.cs:346-351 | Content/Scenarios/SupCal/SupCalEffect.cs:152-157 | Content/Scenarios/SupCal/SupCalEffect.cs:173-178 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/SupCal/End/EternalBlazingNow/EbnEffect.cs:328` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 4) Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:223 — Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:223-228 | Content/Scenarios/Kiame/Overlay/OniRainExitTransition.cs:180-185 | Content/Scenarios/Kiame/Overlay/OniRainWorldTransition.cs:253-258 | Content/Scenarios/Kiame/Overlay/OniRainWorldTransition.cs:281-286 — before extracting anything, compare `Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs` and `Content/Scenarios/Kiame/Overlay/OniRainExitTransition.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 186 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:223` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 4) Content/GameModes/BrutalMobs/Ambience/Rainveil/Projectiles/RainveilThunderboltProj.cs:189 — Content/GameModes/BrutalMobs/Ambience/Rainveil/Projectiles/RainveilThunderboltProj.cs:189-194 | Content/GameModes/BrutalMobs/Ambience/Rotmire/Projectiles/RotmireVentProj.cs:182-187 | Content/GameModes/BrutalMobs/Ambience/Starfall/Projectiles/StarfallAfterburstProj.cs:204-209 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandGeyserProj.cs:164-169 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/Rainveil/Projectiles/RainveilThunderboltProj.cs:189` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/GameModes/BrutalMobs/Ambience/Starfall/Projectiles/StarfallAfterburstProj.cs:211` calls `OnHitPlayer`, `AddBuff` and `Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandGeyserProj.cs:171` 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 (6 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:1113 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:1113-1118 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1358-1363 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1482-1487 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1371-1376 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:1113` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:274 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:274-279 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:1056-1061 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1287-1292 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1341-1346 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:274` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1339` calls `Clamp` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:272` 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 (6 lines × 4) Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgSnowShardProj.cs:83 — Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgSnowShardProj.cs:83-88 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmIceShardProj.cs:68-73 | Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyMaggotBolt.cs:115-120 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesIceShardProj.cs:69-74 — before extracting anything, compare `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgSnowShardProj.cs` and `Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmIceShardProj.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgSnowShardProj.cs:83` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 4) Content/Industrials/ElectricPowers/Apiaries/ApiaryTP.cs:209 — Content/Industrials/ElectricPowers/Apiaries/ApiaryTP.cs:209-214 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerTP.cs:233-238 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:154-159 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatTP.cs:188-193 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Apiaries/ApiaryTP.cs:209` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 4) Content/Items/Ranged/PallbearerAssets.cs:141 — Content/Items/Ranged/PallbearerAssets.cs:141-146 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDoubleCodVFX.cs:33-38 | Content/LegendWeapon/HalibutLegend/FishSkills/FishSwarmVFX.cs:41-46 | Content/LegendWeapon/HalibutLegend/FishSkills/FishTropicalBarracudaVFX.cs:40-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (6 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangProj.cs:173 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangProj.cs:173-178 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailHead.cs:177-182 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipLash.cs:212-217 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoProj.cs:199-204 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangProj.cs:173` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangProj.cs:171` calls `EnterHover` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoProj.cs:198` 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 (6 lines × 4) Content/Industrials/Generator/WindGriven/WGGMK2Wilderness.cs:128 — Content/Industrials/Generator/WindGriven/WGGMK2Wilderness.cs:128-133 | Content/Industrials/Generator/WindGriven/WGGWilderness.cs:125-130 | Content/Industrials/Generator/WindGriven/WindGrivenGenerator.cs:119-124 | Content/Industrials/Generator/WindGriven/WindGrivenGeneratorMk2.cs:124-129 — before extracting anything, compare `Content/Industrials/Generator/WindGriven/WGGMK2Wilderness.cs` and `Content/Industrials/Generator/WindGriven/WGGWilderness.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 69 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Industrials/Generator/WindGriven/WindGrivenGenerator.cs:126` calls `DrawChargeBar` and `Content/Industrials/Generator/WindGriven/WGGMK2Wilderness.cs:134` does not — after which the two agree again for 3 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 (6 lines × 4) Content/LegendWeapon/OnikiriLegend/UI/OniUIParticles.cs:88 — Content/LegendWeapon/OnikiriLegend/UI/OniUIParticles.cs:88-93 | Content/LegendWeapon/OnikiriLegend/UI/OniUIParticles.cs:122-127 | Content/LegendWeapon/OnikiriLegend/UI/OniUIParticles.cs:137-142 | Content/LegendWeapon/OnikiriLegend/UI/OniUIParticles.cs:167-172 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/UI/OniUIParticles.cs:88` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 4) Content/NPCs/BloomsandSerpents/Projectiles/BssDashOmen.cs:122 — Content/NPCs/BloomsandSerpents/Projectiles/BssDashOmen.cs:122-127 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerStrikeTelegraph.cs:111-116 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronTelegraph.cs:125-130 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Projectiles/QueenBeeTelegraphLine.cs:106-111 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (6 lines × 4) Content/EntrustManager/Styles/DraedonManagerStyle.cs:667 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:667-672 | Content/EntrustManager/Styles/ForestManagerStyle.cs:690-695 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:678-683 | Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:166-171 — before extracting anything, compare `Content/EntrustManager/Styles/DraedonManagerStyle.cs` and `Content/EntrustManager/Styles/ForestManagerStyle.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 334 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/EntrustManager/Styles/DraedonManagerStyle.cs:667` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6 lines × 4) Content/EntrustManager/Styles/DraedonManagerStyle.cs:740 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:740-745 | Content/EntrustManager/Styles/ForestManagerStyle.cs:745-750 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:740-745 | Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:682-688 — before extracting anything, compare `Content/EntrustManager/Styles/DraedonManagerStyle.cs` and `Content/EntrustManager/Styles/ForestManagerStyle.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 334 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/EntrustManager/Styles/DraedonManagerStyle.cs:740` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 4) Content/GameModes/BrutalMobs/Ambience/Stratos/Projectiles/StratosFallingStarProj.cs:195 — Content/GameModes/BrutalMobs/Ambience/Stratos/Projectiles/StratosFallingStarProj.cs:195-200 | Content/GameModes/GodSmith/Weapons/Flails/GsGolemFist.cs:195-200 | Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipMorningStarProj.cs:101-106 | Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipMorningStarProj.cs:169-174 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/Stratos/Projectiles/StratosFallingStarProj.cs:195` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 4) Content/GameModes/BrutalMobs/EvilBiome/Projectiles/ErosionCloudSeed.cs:65 — Content/GameModes/BrutalMobs/EvilBiome/Projectiles/ErosionCloudSeed.cs:65-70 | Content/GameModes/BrutalMobs/EvilBiome/Projectiles/MummyWrapProj.cs:83-88 | Content/GameModes/BrutalMobs/EvilBiome/Projectiles/SiphonPounceOmen.cs:116-121 | Content/GameModes/BrutalMobs/EvilBiome/Projectiles/VileBurstOmen.cs:73-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 4 call sites, so a change lands once. 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 (6 lines × 4) Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmYetiConeOmen.cs:196 — Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmYetiConeOmen.cs:196-201 | Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomSporeMistTelegraph.cs:188-193 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesIceShatterCore.cs:148-153 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandConeTelegraph.cs:199-204 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmYetiConeOmen.cs:196` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (6 lines × 4) Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhImpFireBolt.cs:65 — Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhImpFireBolt.cs:65-70 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhTridentBolt.cs:65-70 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkEmberSeedProj.cs:82-87 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkMortarShellProj.cs:84-89 — before extracting anything, compare `Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhImpFireBolt.cs` and `Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhTridentBolt.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 79 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhImpFireBolt.cs:65` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkEmberSeedProj.cs:81` calls `PlaySound` and `Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhImpFireBolt.cs:64` does not — after which the two agree again for 3 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 (6 lines × 4) Content/GameModes/BrutalMobs/Martians/Projectiles/MrtScutlixHeavyBolt.cs:52 — Content/GameModes/BrutalMobs/Martians/Projectiles/MrtScutlixHeavyBolt.cs:52-59 | Content/GameModes/GodSmith/Armors/Reset/GsPillarArmors.cs:302-307 | Content/GameModes/GodSmith/Armors/Reset/GsSpectreArmors.cs:113-118 | Content/GameModes/GodSmith/Armors/Reset/GsTikiArmor.cs:78-83 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. 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 (6 lines × 4) Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteFireSpot.cs:110 — Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteFireSpot.cs:110-115 | Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteMoltenGlob.cs:83-88 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkEmberProj.cs:105-110 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkEmberProj.cs:145-150 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteFireSpot.cs:110` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 4) Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:554 — Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:554-559 | Content/GameModes/GodSmith/Weapons/Shortswords/GsThrustHeldBase.cs:968-973 | Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:589-594 | Content/Items/Modifys/RBloodButcherer.cs:532-537 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:554` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6 lines × 4) Content/Industrials/ElectricPowers/Collectors/CollectorUI.cs:550 — Content/Industrials/ElectricPowers/Collectors/CollectorUI.cs:550-555 | Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:493-500 | Content/Industrials/Modifys/ChargingStationUI.cs:336-342 | Content/Scenarios/OldDuke/Campsites/CampsiteDirectionIndicator.cs:274-280 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Collectors/CollectorUI.cs:550` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6 lines × 4) Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:349 — Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:349-354 | Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:393-398 | Content/Industrials/MaterialFlow/Batterys/CapacitorMatrix.cs:188-193 | Content/LegendWeapon/SHPCLegend/Modules/Grip/ConductorGripModule.cs:55-61 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:349` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6 lines × 4) Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:553 — Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:553-559 | Content/Industrials/Modifys/ChargingStationUI.cs:398-403 | Content/Narrative/Presentation/Skins/StarStream/StarStreamPanelDraw.cs:194-199 | Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersUIs/OceanRaidersRenderer.cs:196-201 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • + 29 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×53
  • Duplicated block (15 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeSlash.cs:188 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeSlash.cs:188-202 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithSlash.cs:203-217 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeSlash.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithSlash.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeSlash.cs:188` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordEyeLinkProj.cs:79 — Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordEyeLinkProj.cs:79-93 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordScanRayProj.cs:69-83 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordEyeLinkProj.cs` and `Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordScanRayProj.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordEyeLinkProj.cs:79` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordScanRayProj.cs:66` calls `Punch` and `Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordEyeLinkProj.cs:76` 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 (15 lines × 2) Content/Items/Magic/AriaofTheCosmoses/AccretionDisk.cs:476 — Content/Items/Magic/AriaofTheCosmoses/AccretionDisk.cs:476-490 | Content/Items/Magic/AriaofTheCosmoses/FlattenedAccretionDisk.cs:222-236 — 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 (15 lines × 2) Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:102 — Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:102-116 | Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:67-81 — before extracting anything, compare `Content/QuestLogs/Styles/DraedonQuestLogStyle.cs` and `Content/QuestLogs/Styles/HotwindQuestLogStyle.cs` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 377 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 (15 lines × 2) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:538 — Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:538-552 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaReset.cs:521-535 — before extracting anything, compare `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs` and `Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaReset.cs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:538` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) Content/GameModes/BrutalMobs/Ambience/Fleshfen/FleshfenAmbience.cs:237 — Content/GameModes/BrutalMobs/Ambience/Fleshfen/FleshfenAmbience.cs:237-251 | Content/GameModes/BrutalMobs/Ambience/Fleshfen/FleshfenAmbience.cs:324-338 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/Fleshfen/FleshfenAmbience.cs:237` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) Content/GameModes/GodSmith/Weapons/Guns/GsMinishark.cs:50 — Content/GameModes/GodSmith/Weapons/Guns/GsMinishark.cs:50-64 | Content/GameModes/GodSmith/Weapons/Guns/GsPhoenixBlaster.cs:55-69 — before extracting anything, compare `Content/GameModes/GodSmith/Weapons/Guns/GsMinishark.cs` and `Content/GameModes/GodSmith/Weapons/Guns/GsPhoenixBlaster.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 74 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/Guns/GsMinishark.cs:50` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) Content/Items/Melee/OniMacheteHands.cs:548 — Content/Items/Melee/OniMacheteHands.cs:548-562 | Content/Items/Melee/OniMacheteHands.cs:613-627 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/OniMacheteHands.cs:548` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:459 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:459-473 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:544-558 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs` as WHOLE FILES: this scan already matched 66 separate duplicated blocks between them, totalling at least 737 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:459` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:1371 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:1371-1385 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1466-1480 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:1371` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) Content/NPCs/BloomsandSerpents/BssHead.cs:690 — Content/NPCs/BloomsandSerpents/BssHead.cs:690-704 | Content/NPCs/FestersandSerpents/FssHead.cs:627-641 — before extracting anything, compare `Content/NPCs/BloomsandSerpents/BssHead.cs` and `Content/NPCs/FestersandSerpents/FssHead.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 321 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BloomsandSerpents/BssHead.cs:690` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:70 — Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:70-84 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowBurrowAmbushState.cs:67-81 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs` and `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowBurrowAmbushState.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 70 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:70` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `context` to `DestroyerStateContext` in one and `EowStateContext` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (15 lines × 2) Content/NPCs/ScrapCommanders/States/ScrapSawLaunchState.cs:51 — Content/NPCs/ScrapCommanders/States/ScrapSawLaunchState.cs:51-65 | Content/NPCs/ScrapCommanders/States/ScrapViceSnatchState.cs:47-61 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/NPCs/ScrapCommanders/States/ScrapViceSnatchState.cs:63` calls `AddTelegraph`, `GetArmPos`, `Clamp` and `Content/NPCs/ScrapCommanders/States/ScrapSawLaunchState.cs:67` does not — after which the two agree again for 3 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 (15 lines × 2) Content/NPCs/TBUGs/TBUGDialogue.cs:35 — Content/NPCs/TBUGs/TBUGDialogue.cs:35-49 | Content/NPCs/Victors/VictorDialogue.cs:37-51 — before extracting anything, compare `Content/NPCs/TBUGs/TBUGDialogue.cs` and `Content/NPCs/Victors/VictorDialogue.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (15 lines × 2) Content/Scenarios/Dungeonworld/Gen/Layers/L1/L1Style.cs:193 — Content/Scenarios/Dungeonworld/Gen/Layers/L1/L1Style.cs:193-207 | Content/Scenarios/Dungeonworld/Gen/Layers/L7/L7Style.cs:323-337 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/Gen/Layers/L1/L1Style.cs:193` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (15 lines × 2) Content/UIs/OverhaulSettings/SettingsCategory.cs:205 — Content/UIs/OverhaulSettings/SettingsCategory.cs:205-219 | Content/UIs/OverhaulSettings/WorldGenSettingsCategory.cs:335-349 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/UIs/OverhaulSettings/SettingsCategory.cs:205` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:63 — Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:63-77 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsScourgeoftheCorruptor.cs:52-66 — 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 (15 lines × 2) Content/HackTimes/Protocols/TilePhase.cs:37 — Content/HackTimes/Protocols/TilePhase.cs:37-51 | Content/HackTimes/Protocols/TilePhase.cs:126-140 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/HackTimes/Protocols/TilePhase.cs:37` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) Content/Industrials/ElectricPowers/HealingStations/HealStationTP.cs:112 — Content/Industrials/ElectricPowers/HealingStations/HealStationTP.cs:112-126 | Content/Industrials/ElectricPowers/ShieldGenerators/ShieldGeneratorTP.cs:195-209 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/HealingStations/HealStationTP.cs:112` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) Content/Industrials/ElectricPowers/LifeWeavers/LifeWeaverAcorn.cs:218 — Content/Industrials/ElectricPowers/LifeWeavers/LifeWeaverAcorn.cs:218-232 | Content/Industrials/ElectricPowers/TreeRegrowths/FallingAcorn.cs:103-117 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/LifeWeavers/LifeWeaverAcorn.cs:218` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:338 — Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:338-352 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:366-380 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:338` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:187 — Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:187-201 | Content/Items/Melee/WeaverGrievanceses/WGManifestationActor.cs:171-185 — before extracting anything, compare `Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs` and `Content/Items/Melee/WeaverGrievanceses/WGManifestationActor.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 237 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:187` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs:328 — Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs:328-342 | Content/Items/Melee/WeaverGrievanceses/WGManifestationNet.cs:329-343 — before extracting anything, compare `Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs` and `Content/Items/Melee/WeaverGrievanceses/WGManifestationNet.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 145 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs:328` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (15 lines × 2) Content/Items/Melee/Flawless.cs:510 — Content/Items/Melee/Flawless.cs:510-524 | Content/Items/Melee/StormGoddessSpears/StormGoddessSpearHeld.cs:486-500 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Flawless.cs:510` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) Content/Items/Ranged/Thornstrings/ThornstringHeld.cs:24 — Content/Items/Ranged/Thornstrings/ThornstringHeld.cs:24-38 | Content/Items/Ranged/Undertows/UndertowHeld.cs:26-40 — before extracting anything, compare `Content/Items/Ranged/Thornstrings/ThornstringHeld.cs` and `Content/Items/Ranged/Undertows/UndertowHeld.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 177 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • + 28 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (4 corresponding lines) · ×49
  • Edited copy of a member (4 corresponding lines) Content/Cyberwares/Implementation/Sandevistans/SandevistanNet.cs:323 — Content/Cyberwares/Implementation/Sandevistans/SandevistanNet.cs:323-326 | Content/RAMSystems/RamNet.cs:427-440 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Content/Narrative/Presentation/Skins/Sulfsea/SulfseaChoiceSkin.cs:43 — Content/Narrative/Presentation/Skins/Sulfsea/SulfseaChoiceSkin.cs:43-46 | Content/Narrative/Presentation/Skins/Tzeentch/TzeentchChoiceSkin.cs:43-46 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:1297 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:1297-1301 | Content/NPCs/SeaShrimp/Rendering/SeaShrimpRenderer.cs:474-477 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkRitualWispProj.cs:58 — Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkRitualWispProj.cs:58-61 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkScytheBladeProj.cs:57-60 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Content/LegendWeapon/HalibutLegend/UI/HalibutRenderer.cs:178 — Content/LegendWeapon/HalibutLegend/UI/HalibutRenderer.cs:178-181 | Content/MainMenus/Overs/AckRenderer.cs:90-93 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Content/GameModes/BrutalMobs/Ambience/Frostveil/Projectiles/FrostveilGaleWallProj.cs:270 — Content/GameModes/BrutalMobs/Ambience/Frostveil/Projectiles/FrostveilGaleWallProj.cs:270-273 | Content/GameModes/BrutalMobs/Ambience/Mireheart/Projectiles/MireheartMiasmaProj.cs:222-225 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaTalismans/KikasaTalismanGlyph.cs:90 — Content/LegendWeapon/KikasaLegend/KikasaTalismans/KikasaTalismanGlyph.cs:90-93 | Content/LegendWeapon/OnikiriLegend/UI/OniMeiGlyph.cs:367-370 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Palette.cs:117 — Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Palette.cs:117-120 | Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Palette.cs:178-181 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Content/Cyberwares/Implementation/PlowSteelClampArms/MonomolecularWire.cs:233 — Content/Cyberwares/Implementation/PlowSteelClampArms/MonomolecularWire.cs:233-236 | Content/Scenarios/OldNet/Tiles/OldNetRelicTile.cs:168-171 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishDrizzle.cs:713 — Content/LegendWeapon/HalibutLegend/FishSkills/FishDrizzle.cs:713-717 | Content/LegendWeapon/HalibutLegend/FishSkills/FishSparkling.cs:430-433 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs:1089 — Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs:1089-1092 | Content/Industrials/MaterialFlow/Pipelines/UEPipeline.cs:279-282 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs:1094 — Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs:1094-1097 | Content/Industrials/MaterialFlow/Pipelines/UEPipeline.cs:288-291 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Content/Items/Ranged/TiroFinales/TiroFinaleRig.cs:58 — Content/Items/Ranged/TiroFinales/TiroFinaleRig.cs:58-61 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Core/CultistOrreryRig.cs:82-85 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzShardProj.cs:111 — Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzShardProj.cs:111-114 | Content/Scenarios/Himayo/ToriiShrines/ToriiShrineActor.cs:676-679 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Content/Items/Melee/DivineSourceBlades/DivineSourceWaveProjectile.cs:52 — Content/Items/Melee/DivineSourceBlades/DivineSourceWaveProjectile.cs:52-55 | Content/Items/Melee/NeutronGlaive.cs:774-777 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistUmbraShade.cs:71 — Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistUmbraShade.cs:71-74 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistZodiacSpokeProj.cs:67-70 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Content/GameModes/BrutalMobs/Ambience/Sporeshine/Projectiles/SporeshineSporeFogProj.cs:70 — Content/GameModes/BrutalMobs/Ambience/Sporeshine/Projectiles/SporeshineSporeFogProj.cs:70-73 | Content/GameModes/BrutalMobs/EvilBiome/Projectiles/ErosionCloudProj.cs:49-52 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Content/Items/Accessories/GodslayerScabbard.cs:35 — Content/Items/Accessories/GodslayerScabbard.cs:35-42 | Content/Items/Melee/CosmicCalamity.cs:92-95 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Content/Narrative/Presentation/Skins/SHPC/SHPCChoiceSkin.cs:21 — Content/Narrative/Presentation/Skins/SHPC/SHPCChoiceSkin.cs:21-24 | Content/Narrative/Presentation/Skins/SHPC/SHPCDialogueSkin.cs:57-63 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Content/Items/Melee/DivineSourceBlades/DivineSourceHitFXProjectile.cs:100 — Content/Items/Melee/DivineSourceBlades/DivineSourceHitFXProjectile.cs:100-103 | Content/Items/Melee/Shatterfangs/ShatterfangBurstFX.cs:76-79 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Content/Items/Stones/Marbles/MarbleBalloon.cs:277 — Content/Items/Stones/Marbles/MarbleBalloon.cs:277-280 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocMawDragState.cs:679-682 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Content/Scenarios/Dungeonworld/UI/DungeonworldLoadTheme.cs:83 — Content/Scenarios/Dungeonworld/UI/DungeonworldLoadTheme.cs:83-86 | Content/Scenarios/Hadalworld/UI/HadalworldLoadTheme.cs:115-118 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Content/GameModes/Blessings/UI/BlessingTheme.cs:56 — Content/GameModes/Blessings/UI/BlessingTheme.cs:56-60 | Content/LegendWeapon/KikasaLegend/UI/Panorama/KikasaPanoramaTheme.cs:62-65 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofGrabTongueProj.cs:251 — Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofGrabTongueProj.cs:251-254 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofTongueLashProj.cs:170-173 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Content/Scenarios/Dungeonworld/UI/DungeonworldTransitionGate.cs:161 — Content/Scenarios/Dungeonworld/UI/DungeonworldTransitionGate.cs:161-164 | Content/Scenarios/Hadalworld/UI/HadalworldTransitionGate.cs:160-163 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • + 24 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×48
  • Duplicated block (9 lines × 3) Content/Items/Magic/Everdeeps/Everdeep.cs:25 — Content/Items/Magic/Everdeeps/Everdeep.cs:25-33 | Content/Items/Magic/Eyetooths/Eyetooth.cs:32-40 | Content/Items/Magic/WheezingWyrms/WheezingWyrm.cs:23-31 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (9 lines × 3) Content/Items/Melee/DestroyersBlade.cs:228 — Content/Items/Melee/DestroyersBlade.cs:228-236 | Content/Items/Melee/DragonsScaleGreatsword.cs:236-244 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:264-272 — before extracting anything, compare `Content/Items/Melee/DestroyersBlade.cs` and `Content/Items/Melee/DragonsScaleGreatsword.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 419 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DestroyersBlade.cs:228` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Melee/DragonsScaleGreatsword.cs:246` calls `PlaySound` and `Content/Items/Melee/DestroyersBlade.cs:238` does not — after which the two agree again for 3 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 × 3) Content/NPCs/BloomsandSerpents/BssHead.cs:591 — Content/NPCs/BloomsandSerpents/BssHead.cs:591-599 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/EowHeadAI.cs:384-392 | Content/NPCs/FestersandSerpents/FssHead.cs:532-540 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (9 lines × 3) Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2EscapeTunnel.cs:390 — Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2EscapeTunnel.cs:390-398 | Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2Palette.cs:68-76 | Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Palette.cs:75-83 — before extracting anything, compare `Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2Palette.cs` and `Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Palette.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 3) Content/Items/Modifys/RBloodButcherer.cs:1026 — Content/Items/Modifys/RBloodButcherer.cs:1026-1034 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunBullet.cs:270-278 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:252-260 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (9 lines × 3) Content/Items/Ranged/NeutronBows/NeutronBow.cs:257 — Content/Items/Ranged/NeutronBows/NeutronBow.cs:257-265 | Content/Items/Ranged/Thornstrings/ThornstringHeld.cs:175-183 | Content/Items/Ranged/Undertows/UndertowHeld.cs:181-189 — before extracting anything, compare `Content/Items/Ranged/NeutronBows/NeutronBow.cs` and `Content/Items/Ranged/Thornstrings/ThornstringHeld.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 98 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 3) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:562 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:562-570 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:378-386 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:498-506 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:562` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 3) Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:157 — Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:157-165 | Content/Scenarios/Kiame/Overlay/OniRainExitTransition.cs:120-128 | Content/Scenarios/Kiame/Overlay/OniRainWorldTransition.cs:172-180 — before extracting anything, compare `Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs` and `Content/Scenarios/Kiame/Overlay/OniRainExitTransition.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 186 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 (9 lines × 3) Content/Items/Magic/AriaofTheCosmoses/AccretionDisk.cs:437 — Content/Items/Magic/AriaofTheCosmoses/AccretionDisk.cs:437-445 | Content/Items/Magic/AriaofTheCosmoses/AriaQSkill.cs:153-161 | Content/Items/Magic/AriaofTheCosmoses/FlattenedAccretionDisk.cs:178-186 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Magic/AriaofTheCosmoses/AccretionDisk.cs:446` calls `Size` and `Content/Items/Magic/AriaofTheCosmoses/AriaQSkill.cs:162` does not — after which the two agree again for 4 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 × 3) Content/Items/Magic/Elysiums/Disciples/Philip.cs:49 — Content/Items/Magic/Elysiums/Disciples/Philip.cs:49-57 | Content/Items/Magic/Elysiums/Disciples/Thaddaeus.cs:32-40 | Content/Items/Magic/Elysiums/Disciples/Thomas.cs:25-33 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/Elysiums/Disciples/Philip.cs:49` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 3) Content/LegendWeapon/HalibutLegend/UI/HalibutItemTooltipPanel.cs:41 — Content/LegendWeapon/HalibutLegend/UI/HalibutItemTooltipPanel.cs:41-49 | Content/LegendWeapon/OnikiriLegend/UI/OniItemTooltipPanel.cs:46-54 | Content/LegendWeapon/SHPCLegend/UI/SHPCItemTooltipPanel.cs:44-52 — before extracting anything, compare `Content/LegendWeapon/HalibutLegend/UI/HalibutItemTooltipPanel.cs` and `Content/LegendWeapon/OnikiriLegend/UI/OniItemTooltipPanel.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/UI/HalibutItemTooltipPanel.cs:41` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:468 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:468-476 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:466-474 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:431-439 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs` as WHOLE FILES: this scan already matched 75 separate duplicated blocks between them, totalling at least 912 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:468` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 3) Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBellWave.cs:47 — Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBellWave.cs:47-55 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiInkThread.cs:126-134 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiThunderColumn.cs:48-56 — 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 (9 lines × 3) Content/Items/Melee/DragonsScaleGreatsword.cs:632 — Content/Items/Melee/DragonsScaleGreatsword.cs:632-640 | Content/Items/Melee/DragonsScaleGreatsword.cs:836-844 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:985-993 — before extracting anything, compare `Content/Items/Melee/DragonsScaleGreatsword.cs` and `Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 415 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DragonsScaleGreatsword.cs:632` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 3) Content/Items/Melee/NeutronGlaive.cs:1240 — Content/Items/Melee/NeutronGlaive.cs:1240-1248 | Content/Items/Melee/NeutronScythe.cs:310-318 | Content/Items/Ranged/NeutronBows/NeutronExplosionRanged.cs:16-24 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/NeutronGlaive.cs:1240` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:796 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:796-804 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:758-766 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:790-798 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs` as WHOLE FILES: this scan already matched 78 separate duplicated blocks between them, totalling at least 968 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:796` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (9 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:286 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:286-294 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterPool.cs:56-64 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsFlameBreath.cs:42-50 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterPool.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:286` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 3) Content/Scenarios/Dungeonworld/NPCs/GaolDormantSkull.cs:201 — Content/Scenarios/Dungeonworld/NPCs/GaolDormantSkull.cs:201-209 | Content/Scenarios/Dungeonworld/NPCs/OverseerDormantRig.cs:275-283 | Content/Scenarios/Dungeonworld/NPCs/UndrownedThrone.cs:278-286 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 3) Content/Scenarios/Kiame/KiameAmbience.cs:176 — Content/Scenarios/Kiame/KiameAmbience.cs:176-184 | Content/Scenarios/Kiame/Overlay/OniRainWorldState.cs:294-302 | Content/Wraiths/Abilities/GhostRains/GhostRainFx.cs:163-171 — before extracting anything, compare `Content/Scenarios/Kiame/KiameAmbience.cs` and `Content/Scenarios/Kiame/Overlay/OniRainWorldState.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Kiame/KiameAmbience.cs:176` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 3) Content/GameModes/GodSmith/Weapons/Broadswords/GsMeowmere.cs:307 — Content/GameModes/GodSmith/Weapons/Broadswords/GsMeowmere.cs:307-316 | Content/GameModes/GodSmith/Weapons/Broadswords/GsSeedler.cs:126-135 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuXianFX.cs:95-103 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuXianFX.cs:95` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (9 lines × 3) Content/HackTimes/HackTimeNetSync.cs:526 — Content/HackTimes/HackTimeNetSync.cs:526-535 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBanish.Net.cs:104-113 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.Net.cs:127-135 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/HackTimes/HackTimeNetSync.cs:526` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 3) Content/Items/Melee/Abyssrends/AbyssrendFX.cs:115 — Content/Items/Melee/Abyssrends/AbyssrendFX.cs:115-123 | Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:753-762 | Content/Items/Modifys/RTerraBlades/RTerraBladeHeld.cs:981-990 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. 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 (9 lines × 3) Content/Items/Melee/DivineSourceBlades/DivineSourceHitFXProjectile.cs:189 — Content/Items/Melee/DivineSourceBlades/DivineSourceHitFXProjectile.cs:189-199 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:1286-1294 | Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:1394-1403 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. 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 (9 lines × 3) Content/Items/Melee/OniMacheteHands.cs:913 — Content/Items/Melee/OniMacheteHands.cs:913-921 | Content/LegendWeapon/HalibutLegend/FishSkills/FishRock.cs:585-593 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Core/DeerclopsMotion.cs:119-127 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/OniMacheteHands.cs:913` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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 (9 lines × 3) Content/LegendWeapon/HalibutLegend/DomainSkills/Superposition.cs:132 — Content/LegendWeapon/HalibutLegend/DomainSkills/Superposition.cs:132-141 | Content/LegendWeapon/HalibutLegend/DomainSkills/YourLevelIsTooLow.cs:588-597 | Content/LegendWeapon/HalibutLegend/DomainSkills/YourLevelIsTooLow.cs:737-745 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/DomainSkills/Superposition.cs:132` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
  • + 23 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (5 lines × 4) · ×47
  • Duplicated block (5 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkFX.cs:562 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkFX.cs:562-566 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkSplashFX.cs:469-473 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:112-116 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:184-188 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkFX.cs:562` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:191` calls `SetValue` and `Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkFX.cs:568` does not — after which the two agree again for 4 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 (5 lines × 4) Content/EntrustManager/Styles/DraedonManagerStyle.cs:172 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:172-176 | Content/EntrustManager/Styles/DraedonManagerStyle.cs:700-704 | Content/EntrustManager/Styles/ForestManagerStyle.cs:719-723 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:711-715 — before extracting anything, compare `Content/EntrustManager/Styles/DraedonManagerStyle.cs` and `Content/EntrustManager/Styles/ForestManagerStyle.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 334 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/EntrustManager/Styles/DraedonManagerStyle.cs:172` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/EntrustManager/Styles/HotwindManagerStyle.cs:717` calls `Sin`, `FillRect`, `Color` and `Content/EntrustManager/Styles/ForestManagerStyle.cs:724` does not — after which the two agree again for 3 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 (5 lines × 4) Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkEmberSeedProj.cs:96 — Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkEmberSeedProj.cs:96-100 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkMortarShellProj.cs:98-102 | Content/Items/Melee/DestroyersBladeEXs/DestroyerHeadMissile.cs:155-159 | Content/NPCs/BloomsandSerpents/Projectiles/BssSandGlob.cs:68-72 — before extracting anything, compare `Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkEmberSeedProj.cs` and `Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkMortarShellProj.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 61 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkEmberSeedProj.cs:96` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 4) Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:571 — Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:571-575 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsSickle.cs:168-172 | Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:607-611 | Content/Items/Modifys/RBloodButcherer.cs:550-554 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:571` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 4) Content/Items/Magic/SandVortexOfTheDecayedSea.cs:434 — Content/Items/Magic/SandVortexOfTheDecayedSea.cs:434-438 | Content/Items/Melee/RebelBlade.cs:770-774 | Content/Items/Ranged/RaiderGun.cs:466-470 | Content/Items/Tools/FungalFeed.cs:117-121 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/SandVortexOfTheDecayedSea.cs:434` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1512 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1512-1516 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:1365-1369 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:995-999 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:1601-1605 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1512` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:1599` calls `OrderMinesMelt` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1510` does not — after which the two agree again for 3 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 (5 lines × 4) Content/GameModes/GodSmith/Armors/Reset/GsOreArmorsHardmode.cs:272 — Content/GameModes/GodSmith/Armors/Reset/GsOreArmorsHardmode.cs:272-276 | Content/GameModes/GodSmith/Armors/Reset/GsPillarArmors.cs:293-297 | Content/GameModes/GodSmith/Armors/Reset/GsShroomiteArmor.cs:147-151 | Content/GameModes/GodSmith/Armors/Reset/GsSpiderArmor.cs:74-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 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Armors/Reset/GsOreArmorsHardmode.cs:272` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 4) Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:443 — Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:443-447 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:463-467 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:525-529 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:631-635 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:443` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 4) Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzShardProj.cs:124 — Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzShardProj.cs:124-128 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBunny.cs:784-788 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenCrystalSpikeProj.cs:248-252 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofBloodClot.cs:70-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzShardProj.cs:124` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzShardProj.cs:121` calls `PrismHue` and `Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofBloodClot.cs:67` does not — after which the two agree again for 3 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 (5 lines × 4) Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:927 — Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:927-931 | Content/Items/Melee/NeutronGlaive.cs:601-605 | Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:737-741 | Content/Items/Modifys/RBloodButcherer.cs:722-726 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:736` calls `Pow` and `Content/Items/Melee/NeutronGlaive.cs:599` does not — after which the two agree again for 4 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 (5 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomain.cs:136 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomain.cs:136-140 | Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomain.cs:163-167 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomain.cs:114-118 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Cyberspace.cs:118-122 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomain.cs:136` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainRender.cs:59 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainRender.cs:59-63 | Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainRender.cs:210-214 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainRender.cs:39-43 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainRender.cs:164-168 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainRender.cs:59` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainRender.cs:215` calls `DrawLowQualityFallback` and `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainRender.cs:64` does not — after which the two agree again for 4 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 (5 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:153 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:153-157 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:219-223 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:278-282 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:468-472 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:153` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:274` calls `DrawCanopyGhosts` and `Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:148` 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 (5 lines × 4) Content/Scenarios/Draedon/Tzeentch/FirstMetTzeentch.cs:24 — Content/Scenarios/Draedon/Tzeentch/FirstMetTzeentch.cs:24-28 | Content/Scenarios/Helen/Gifts/HellGift.cs:16-20 | Content/Scenarios/OldDuke/FirstMetOldDuke.cs:24-28 | Content/Scenarios/OldDuke/Quest/FindFragments/FirstCampsiteDialogue.cs:14-18 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (5 lines × 4) Content/Cyberwares/Tutorial/CyberwareGuideLead.cs:402 — Content/Cyberwares/Tutorial/CyberwareGuideLead.cs:402-406 | Content/EntrustManager/Styles/DraedonManagerStyle.cs:109-113 | Content/EntrustManager/Styles/ForestManagerStyle.cs:108-112 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:104-108 — before extracting anything, compare `Content/EntrustManager/Styles/DraedonManagerStyle.cs` and `Content/EntrustManager/Styles/ForestManagerStyle.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 334 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 (5 lines × 4) Content/GameModes/BrutalMobs/FrostLegion/FrostLegionNPC.cs:417 — Content/GameModes/BrutalMobs/FrostLegion/FrostLegionNPC.cs:417-422 | Content/GameModes/BrutalMobs/Graveyard/GraveyardBrutalNPC.cs:345-350 | Content/GameModes/BrutalMobs/Graveyard/GraveyardBrutalNPC.cs:498-502 | Content/GameModes/BrutalMobs/Stoneborn/StonebornBrutalNPC.cs:429-434 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/FrostLegion/FrostLegionNPC.cs:417` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 4) Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:552 — Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:552-556 | Content/GameModes/GodSmith/Weapons/Broadswords/GsMandibleBlade.cs:93-97 | Content/GameModes/GodSmith/Weapons/Shortswords/GsThrustHeldBase.cs:966-970 | Content/Items/Modifys/RBloodButcherer.cs:530-534 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:552` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 4) Content/GameModes/GodSmith/Weapons/Flails/GsChainGuillotines.cs:147 — Content/GameModes/GodSmith/Weapons/Flails/GsChainGuillotines.cs:147-151 | Content/GameModes/GodSmith/Weapons/Flails/GsDaoofPow.cs:140-144 | Content/GameModes/GodSmith/Weapons/Flails/GsGolemFist.cs:212-216 | Content/GameModes/GodSmith/Weapons/Flails/GsKOCannon.cs:170-174 — 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 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/Flails/GsChainGuillotines.cs:147` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (5 lines × 4) Content/HackTimes/Protocols/TilePhase.cs:46 — Content/HackTimes/Protocols/TilePhase.cs:46-50 | Content/HackTimes/Protocols/TilePhase.cs:135-139 | Content/HackTimes/Scannables/ContainerScannable.cs:248-253 | Content/HackTimes/Scannables/TileScannable.cs:329-335 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 4) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:91 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:91-95 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs:95-99 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:84-88 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:93-97 — before extracting anything, compare `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs` and `Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 226 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:90` calls `GetLocalization`, `nameof` and `Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:83` does not — after which the two agree again for 4 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 (5 lines × 4) Content/Items/Accessories/BrutalRelics/BrainOfCthulhu/MirrorheartPulse.cs:122 — Content/Items/Accessories/BrutalRelics/BrainOfCthulhu/MirrorheartPulse.cs:122-127 | Content/Items/Magic/Elysiums/Serpents/SnakeConversionWave.cs:92-97 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBellWave.cs:122-128 | Content/LegendWeapon/SHPCLegend/Modules/Frame/ResonanceFrameModule.cs:633-637 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. 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 (5 lines × 4) Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs:136 — Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs:136-141 | Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs:164-168 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronSharkTornadoProj.cs:249-254 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronSharkTornadoProj.cs:277-282 — before extracting anything, compare `Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs` and `Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronSharkTornadoProj.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 181 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs:136` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (5 lines × 4) Content/Items/Magic/Elysiums/Disciples/BaseDisciple.cs:274 — Content/Items/Magic/Elysiums/Disciples/BaseDisciple.cs:274-278 | Content/Items/Magic/Elysiums/ElysiumHeld.cs:292-296 | Content/Items/Magic/Elysiums/ElysiumHeld.cs:324-328 | Content/Items/Magic/Elysiums/Revelations/ApocalypseHorseman.cs:181-185 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Magic/Elysiums/Disciples/BaseDisciple.cs:273` calls `End` and `Content/Items/Magic/Elysiums/ElysiumHeld.cs:290` 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 (5 lines × 4) Content/Items/Magic/Eyetooths/EyetoothVFX.cs:119 — Content/Items/Magic/Eyetooths/EyetoothVFX.cs:119-123 | Content/LegendWeapon/HalibutLegend/FishSkills/Fishotroning.cs:756-767 | Content/LegendWeapon/HalibutLegend/FishSkills/Fishotroning.cs:1027-1038 | Content/LegendWeapon/HalibutLegend/FishSkills/Fishotroning.cs:1169-1178 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/Eyetooths/EyetoothVFX.cs:119` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 4) Content/Items/Magic/FocusingGrimoire.cs:347 — Content/Items/Magic/FocusingGrimoire.cs:347-351 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs:186-190 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeHeatRay.cs:174-178 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeSkullBeamProj.cs:185-189 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs` and `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeHeatRay.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeHeatRay.cs:174` calls `Clamp` and `Content/Items/Magic/FocusingGrimoire.cs:347` does not — after which the two agree again for 5 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.
  • + 22 more in this group — see findings.md.
D4 · Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) · ×45
  • Edited copies of one member (3 members, 11+ corresponding lines) Content/PRTTypes/PRT_SulfuricCore.cs:120 — Content/PRTTypes/PRT_SulfuricCore.cs:120-130 | Content/PRTTypes/PRT_SulfuricCore.cs:132-142 | Content/PRTTypes/PRT_SulfuricCore.cs:144-156 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Core/EocMotion.cs:108 — Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Core/EocMotion.cs:108-120 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Core/EocMotion.cs:158-168 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Projectiles/EocBloodShot.cs:75-88 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) Content/Items/Ranged/PallbearerAssets.cs:140 — Content/Items/Ranged/PallbearerAssets.cs:140-150 | Content/LegendWeapon/HalibutLegend/FishSkills/FishJewelVFX.cs:53-64 | Content/LegendWeapon/HalibutLegend/FishSkills/FishTropicalBarracudaVFX.cs:39-49 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistPlanetProj.cs:678 — Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistPlanetProj.cs:678-690 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistPlanetProj.cs:704-719 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistPlanetProj.cs:767-777 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) Content/Items/Melee/GeminisTribute.cs:327 — Content/Items/Melee/GeminisTribute.cs:327-339 | Content/Items/Melee/GeminisTribute.cs:376-386 | Content/Items/Melee/GeminisTribute.cs:637-648 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) Content/HackTimes/Protocols/DelayFuse.cs:51 — Content/HackTimes/Protocols/DelayFuse.cs:51-63 | Content/HackTimes/Protocols/ProjectileFreeze.cs:25-38 | Content/HackTimes/Protocols/ProjectileTithe.cs:87-97 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) Content/NPCs/BloomsandSerpents/Core/BssStateContext.cs:295 — Content/NPCs/BloomsandSerpents/Core/BssStateContext.cs:295-308 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Core/EowStateContext.cs:102-112 | Content/NPCs/FestersandSerpents/Core/FssStateContext.cs:265-278 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishHarpyVFX.cs:106 — Content/LegendWeapon/HalibutLegend/FishSkills/FishHarpyVFX.cs:106-119 | Content/LegendWeapon/HalibutLegend/FishSkills/FishVoodooParticles.cs:38-48 | Content/PRTTypes/PRT_OniSakuraDrift.cs:43-59 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalPlantera/Rendering/PlanteraPRT.cs:64 — Content/NPCs/BrutalNPCs/BrutalPlantera/Rendering/PlanteraPRT.cs:64-74 | Content/PRTTypes/PRT_BrideDryPetal.cs:57-67 | Content/PRTTypes/PRT_OniSakuraDrift.cs:61-72 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) Content/GameModes/GodSmith/Weapons/MagicChant/GsVilethorn.cs:29 — Content/GameModes/GodSmith/Weapons/MagicChant/GsVilethorn.cs:29-40 | Content/GameModes/GodSmith/Weapons/MagicChant/GsWandOfFrosting.cs:30-41 | Content/GameModes/GodSmith/Weapons/MagicChant/GsWandOfSparking.cs:29-39 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) Content/Cyberwares/Tutorial/CyberwareGuideLead.cs:385 — Content/Cyberwares/Tutorial/CyberwareGuideLead.cs:385-395 | Content/LegendWeapon/KikasaLegend/UI/KikasaHudLead.cs:857-867 | Content/Scenarios/OldNet/UI/OldNetGuideLead.cs:319-331 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) Content/Scenarios/Kiyume/NPCs/FacelessOneYokai.cs:368 — Content/Scenarios/Kiyume/NPCs/FacelessOneYokai.cs:368-378 | Content/Scenarios/Kiyume/NPCs/LanternGuideYokai.cs:439-449 | Content/Scenarios/Kiyume/NPCs/RidgeWalkerYokai.cs:507-517 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) Content/Items/Melee/OniMacheteHands.cs:938 — Content/Items/Melee/OniMacheteHands.cs:938-949 | Content/Items/Melee/OniMacheteHands.cs:967-977 | Content/Items/Melee/OniMacheteHands.cs:1239-1250 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) Content/GameModes/BrutalMobs/EvilBiome/Projectiles/VileLanceProj.cs:76 — Content/GameModes/BrutalMobs/EvilBiome/Projectiles/VileLanceProj.cs:76-87 | Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomSporeBoltProj.cs:125-136 | Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilCursedBeadProj.cs:97-107 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) Content/HackTimes/Scannables/ContainerScannable.cs:294 — Content/HackTimes/Scannables/ContainerScannable.cs:294-304 | Content/HackTimes/Scannables/ContainerScannable.cs:307-320 | Content/HackTimes/Scannables/ContainerScannable.cs:323-338 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) Content/GameModes/BrutalMobs/Ambience/Silkcrypt/Projectiles/SilkcryptWebPatchProj.cs:219 — Content/GameModes/BrutalMobs/Ambience/Silkcrypt/Projectiles/SilkcryptWebPatchProj.cs:219-230 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtRicochetShot.cs:329-339 | Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornQuakeWave.cs:131-141 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:242 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:242-252 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs:292-305 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:187-200 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) Content/Scenarios/Kiame/KiameWorld.cs:76 — Content/Scenarios/Kiame/KiameWorld.cs:76-92 | Content/Scenarios/Kiyume/KiyumeWorld.cs:77-87 | Content/Scenarios/OldNet/OldNetWorld.cs:77-90 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) Content/Items/Melee/StormGoddessSpears/StormGoddess.cs:655 — Content/Items/Melee/StormGoddessSpears/StormGoddess.cs:655-665 | Content/Items/Melee/StormGoddessSpears/StormGoddess.cs:692-704 | Content/Items/Melee/StormGoddessSpears/StormGoddess.cs:878-891 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) Content/GameModes/GodSmith/Weapons/Throwing/GsThrowShared.cs:382 — Content/GameModes/GodSmith/Weapons/Throwing/GsThrowShared.cs:382-392 | Content/LegendWeapon/HalibutLegend/FishSkills/FishObsidian.cs:247-257 | Content/LegendWeapon/HalibutLegend/FishSkills/FishObsidian.cs:259-272 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) Content/NPCs/BloomsandSerpents/BssBloomBud.cs:21 — Content/NPCs/BloomsandSerpents/BssBloomBud.cs:21-31 | Content/NPCs/FestersandSerpents/FssFesterBud.cs:22-32 | Content/NPCs/ScrapCommanders/ScrapBeacon.cs:20-30 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishDirtParticles.cs:196 — Content/LegendWeapon/HalibutLegend/FishSkills/FishDirtParticles.cs:196-207 | Content/LegendWeapon/HalibutLegend/FishSkills/FishPengVFX.cs:233-245 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendParticles.cs:772-782 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) Content/Items/Melee/DivineSourceBlades/DivineSourcePRT.cs:45 — Content/Items/Melee/DivineSourceBlades/DivineSourcePRT.cs:45-55 | Content/PRTTypes/PRT_CyberSquare.cs:43-53 | Content/PRTTypes/PRT_SHPCHexBit.cs:42-52 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuNi.cs:154 — Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuNi.cs:154-164 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuPo.cs:159-169 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuWen.cs:109-119 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) Content/GameModes/GodSmith/Weapons/MagicChant/GsCursedFlames.cs:235 — Content/GameModes/GodSmith/Weapons/MagicChant/GsCursedFlames.cs:235-245 | Content/GameModes/GodSmith/Weapons/MagicChant/GsGoldenShower.cs:204-214 | Content/GameModes/GodSmith/Weapons/MagicChant/GsNettleBurst.cs:122-132 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • + 20 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×45
  • Duplicated block (16 lines × 2) Content/HackTimes/Targets/BossPartTargetType.cs:83 — Content/HackTimes/Targets/BossPartTargetType.cs:83-98 | Content/HackTimes/Targets/NpcTargetType.cs:22-37 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/HackTimes/Targets/BossPartTargetType.cs:83` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/HackTimes/Targets/BossPartTargetType.cs:81` calls `TryGetPart` and `Content/HackTimes/Targets/NpcTargetType.cs:20` does not — after which the two agree again for 4 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 (16 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:289 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:289-304 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:335-350 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 491 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:333` calls `AngleLerp` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:287` does not — after which the two agree again for 4 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 (16 lines × 2) Content/GameModes/GodSmith/Weapons/MagicChant/GsCursedFlames.cs:102 — Content/GameModes/GodSmith/Weapons/MagicChant/GsCursedFlames.cs:102-117 | Content/GameModes/GodSmith/Weapons/MagicChant/GsGoldenShower.cs:142-157 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/MagicChant/GsCursedFlames.cs:102` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs:1063 — Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs:1063-1078 | Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersTP.cs:479-494 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs:1063` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (16 lines × 2) Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteRing.cs:330 — Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteRing.cs:330-345 | Content/Items/Accessories/NinjaCthulsparkBoots.cs:201-216 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteRing.cs:330` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (16 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainPlayer.cs:1301 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainPlayer.cs:1301-1316 | Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamFX.cs:47-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamFX.cs:45` calls `Wuff`, `Vector2` and `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainPlayer.cs:1299` does not — after which the two agree again for 3 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 (16 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainSky.cs:92 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainSky.cs:92-107 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainSky.cs:73-88 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainSky.cs` and `Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainSky.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainSky.cs:92` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (16 lines × 2) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:562 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:562-577 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:498-513 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 870 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:562` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:258 — Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:258-273 | Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:479-494 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:258` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) Content/EntrustManager/Styles/DraedonManagerStyle.cs:264 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:264-279 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:258-273 — before extracting anything, compare `Content/EntrustManager/Styles/DraedonManagerStyle.cs` and `Content/EntrustManager/Styles/HotwindManagerStyle.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 442 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/EntrustManager/Styles/DraedonManagerStyle.cs:264` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) Content/Items/Modifys/RBloodButcherer.cs:902 — Content/Items/Modifys/RBloodButcherer.cs:902-917 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:125-140 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Modifys/RBloodButcherer.cs:902` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaScourgeFX.cs:487 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaScourgeFX.cs:487-502 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaScourgeFX.cs:575-590 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaScourgeFX.cs:487` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1112 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1112-1127 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1118-1133 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 870 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1112` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs:129 — Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs:129-144 | Content/NPCs/FestersandSerpents/Projectiles/FssIchorGlob.cs:127-142 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs` and `Content/NPCs/FestersandSerpents/Projectiles/FssIchorGlob.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 149 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs:129` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) Content/Narrative/Presentation/Skins/Kikasa/KikasaDialogueSkin.cs:96 — Content/Narrative/Presentation/Skins/Kikasa/KikasaDialogueSkin.cs:96-111 | Content/Narrative/Presentation/Skins/Onikiri/OnikiriDialogueSkin.cs:96-111 — before extracting anything, compare `Content/Narrative/Presentation/Skins/Kikasa/KikasaDialogueSkin.cs` and `Content/Narrative/Presentation/Skins/Onikiri/OnikiriDialogueSkin.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Narrative/Presentation/Skins/Kikasa/KikasaDialogueSkin.cs:96` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) Content/Narrative/Presentation/Skins/Sulfsea/SulfseaPanelDraw.cs:59 — Content/Narrative/Presentation/Skins/Sulfsea/SulfseaPanelDraw.cs:59-74 | Content/Narrative/Presentation/Skins/Tzeentch/TzeentchPanelDraw.cs:58-73 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Narrative/Presentation/Skins/Sulfsea/SulfseaPanelDraw.cs:59` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) Content/GameModes/GodSmith/Weapons/Bows/GsChargeBowHeld.cs:293 — Content/GameModes/GodSmith/Weapons/Bows/GsChargeBowHeld.cs:293-308 | Content/GameModes/GodSmith/Weapons/Bows/PhantasmScheme.cs:327-342 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/Bows/GsChargeBowHeld.cs:293` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:37 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:37-52 | Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs:39-54 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs` and `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 192 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs:56` calls `LoadNPC` and `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:54` does not — after which the two agree again for 3 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 (16 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:399 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:399-414 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:467-482 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:399` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) Content/LegendWeapon/OnikiriLegend/UI/OniSigilRenderer.cs:722 — Content/LegendWeapon/OnikiriLegend/UI/OniSigilRenderer.cs:722-737 | Content/UIs/WeaponSkills/WeaponSkillBrush.cs:51-66 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/UI/OniSigilRenderer.cs:722` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/UIs/WeaponSkills/WeaponSkillBrush.cs:68` calls `DrawRing`, `DrawArc` and `Content/LegendWeapon/OnikiriLegend/UI/OniSigilRenderer.cs:740` 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 (16 lines × 2) Content/NPCs/BloomsandSerpents/BssHead.cs:502 — Content/NPCs/BloomsandSerpents/BssHead.cs:502-517 | Content/NPCs/FestersandSerpents/FssHead.cs:453-468 — before extracting anything, compare `Content/NPCs/BloomsandSerpents/BssHead.cs` and `Content/NPCs/FestersandSerpents/FssHead.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 321 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BloomsandSerpents/BssHead.cs:502` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerLaser.cs:113 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerLaser.cs:113-128 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/DeadLaser.cs:71-86 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerLaser.cs` and `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/DeadLaser.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerLaser.cs:113` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryWatcher.cs:178 — Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryWatcher.cs:178-193 | Content/Scenarios/Dungeonworld/Gen/BossRooms/ProofingHallWatcher.cs:151-166 — before extracting anything, compare `Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryWatcher.cs` and `Content/Scenarios/Dungeonworld/Gen/BossRooms/ProofingHallWatcher.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 62 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryWatcher.cs:178` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryWatcher.cs:177` calls `ApplyWater` and `Content/Scenarios/Dungeonworld/Gen/BossRooms/ProofingHallWatcher.cs:150` does not — after which the two agree again for 4 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 (16 lines × 2) Content/Scenarios/OldDuke/Campsites/CampsiteLocationFinder.cs:76 — Content/Scenarios/OldDuke/Campsites/CampsiteLocationFinder.cs:76-91 | Content/Scenarios/OldDuke/Campsites/CampsiteLocationFinder.cs:94-109 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (16 lines × 2) Content/Wraiths/Abilities/CrimsonBrides/BrideHallSky.cs:150 — Content/Wraiths/Abilities/CrimsonBrides/BrideHallSky.cs:150-165 | Content/Wraiths/Abilities/GhostRains/GhostRainAmbience.cs:150-165 — before extracting anything, compare `Content/Wraiths/Abilities/CrimsonBrides/BrideHallSky.cs` and `Content/Wraiths/Abilities/GhostRains/GhostRainAmbience.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Wraiths/Abilities/CrimsonBrides/BrideHallSky.cs:150` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Wraiths/Abilities/GhostRains/GhostRainAmbience.cs:166` calls `SetValue` and `Content/Wraiths/Abilities/CrimsonBrides/BrideHallSky.cs:166` does not — after which the two agree again for 4 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.
  • + 20 more in this group — see findings.md.
D4 · Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) · ×43
  • Edited copies of one member (3 members, 10+ corresponding lines) Content/NPCs/CommonUIs/NPCUIStyle.cs:73 — Content/NPCs/CommonUIs/NPCUIStyle.cs:73-87 | Content/Scenarios/OldNet/UI/OldNetDebriefPanel.cs:813-822 | Content/Scenarios/Shepel/CybCourses/CybCourseCardStyle.cs:184-194 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsDeathState.cs:198 — Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsDeathState.cs:198-207 | Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsFrostQuakeState.cs:67-78 | Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsSpikeWaveState.cs:62-72 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiDebuffs.cs:28 — Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiDebuffs.cs:28-37 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiDebuffs.cs:55-64 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiPaperEffigy.cs:367-378 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishBatVFX.cs:306 — Content/LegendWeapon/HalibutLegend/FishSkills/FishBatVFX.cs:306-316 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCloudEffects.cs:114-123 | Content/LegendWeapon/HalibutLegend/OceanCurrentParticles.cs:424-438 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) Content/Items/Accessories/BrutalRelics/Skeletron/SoulbindingCounterFlame.cs:99 — Content/Items/Accessories/BrutalRelics/Skeletron/SoulbindingCounterFlame.cs:99-111 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronBoneWheel.cs:136-146 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronGhostArmProj.cs:292-301 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordDrawHelper.cs:124 — Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordDrawHelper.cs:124-134 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordDrawHelper.cs:416-428 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordDrawHelper.cs:431-440 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) Content/GameModes/GodSmith/Weapons/MagicMorph/GsLeafBlower.cs:144 — Content/GameModes/GodSmith/Weapons/MagicMorph/GsLeafBlower.cs:144-155 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistThunderOrb.cs:193-205 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuTingFX.cs:153-162 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) Content/HackTimes/Protocols/MeltdownProtocol.cs:76 — Content/HackTimes/Protocols/MeltdownProtocol.cs:76-87 | Content/HackTimes/Protocols/ShortCircuit.cs:21-30 | Content/HackTimes/Protocols/SynapseBurn.cs:40-50 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuShaFX.cs:56 — Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuShaFX.cs:56-65 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuShuFX.cs:83-92 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuXiaoFX.cs:22-32 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) Content/GameModes/GodSmith/Armors/Reset/GsBeetleArmors.cs:180 — Content/GameModes/GodSmith/Armors/Reset/GsBeetleArmors.cs:180-189 | Content/GameModes/GodSmith/Armors/Reset/GsCrimsonArmor.cs:109-121 | Content/GameModes/GodSmith/Armors/Reset/GsFrostArmor.cs:111-121 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistPlanetProj.cs:642 — Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistPlanetProj.cs:642-654 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistPlanetProj.cs:780-789 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistZodiacRing.cs:125-134 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:188 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:188-199 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1058-1067 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1553-1566 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhImpFireBolt.cs:61 — Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhImpFireBolt.cs:61-70 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhTridentBolt.cs:61-70 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkMortarShellProj.cs:79-89 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) Content/GameModes/GodSmith/Prefixes/Accessory/GodSmithViolentSurgeEndow.cs:119 — Content/GameModes/GodSmith/Prefixes/Accessory/GodSmithViolentSurgeEndow.cs:119-128 | Content/GameModes/GodSmith/Prefixes/Offense/GodSmithEchoSlashEndow.cs:91-101 | Content/GameModes/GodSmith/Prefixes/Offense/GodSmithShockwaveEndow.cs:93-102 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyMaggotBolt.cs:97 — Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyMaggotBolt.cs:97-106 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhShellSpike.cs:53-62 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhStingerBolt.cs:62-71 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) Content/GameModes/BrutalMobs/SlimeKin/SlimeKinFlavor.cs:101 — Content/GameModes/BrutalMobs/SlimeKin/SlimeKinFlavor.cs:101-110 | Content/NPCs/BrutalNPCs/BrutalGolem/Core/GolemAiContracts.cs:198-207 | Content/NPCs/BrutalNPCs/BrutalGolem/States/GolemHookSwingState.cs:105-114 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) Content/HackTimes/Protocols/Cryostasis.cs:166 — Content/HackTimes/Protocols/Cryostasis.cs:166-177 | Content/HackTimes/Protocols/Electrolysis.cs:101-110 | Content/HackTimes/Protocols/TileMagPull.cs:45-55 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishPrincessVFX.cs:46 — Content/LegendWeapon/HalibutLegend/FishSkills/FishPrincessVFX.cs:46-56 | Content/LegendWeapon/HalibutLegend/FishSkills/FishofCthuluVFX.cs:49-59 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Rendering/KingSlimeGelFX.cs:144-153 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) Content/PRTTypes/PRT_HeavenfallStar.cs:25 — Content/PRTTypes/PRT_HeavenfallStar.cs:25-34 | Content/PRTTypes/PRT_Spark.cs:30-45 | Content/PRTTypes/PRT_SparkAlpha.cs:27-41 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Rendering/EmpressDaySky.cs:105 — Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Rendering/EmpressDaySky.cs:105-114 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordEclipseSky.cs:92-101 | Content/Wraiths/Abilities/CrimsonBrides/BrideHallSky.cs:86-95 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Rendering/PRT_WofBloodMist.cs:28 — Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Rendering/PRT_WofBloodMist.cs:28-39 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Rendering/PRT_WofGore.cs:29-38 | Content/PRTTypes/PRT_LWarden.cs:94-104 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) Content/PRTTypes/PRT_DragonsWordCut.cs:32 — Content/PRTTypes/PRT_DragonsWordCut.cs:32-43 | Content/PRTTypes/PRT_Line.cs:32-41 | Content/PRTTypes/PRT_Line_FormPlayer.cs:23-35 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:70 — Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:70-79 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Core/EmpressCast.cs:106-117 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofRetinaScanBeam.cs:79-88 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) Content/Items/Melee/CosmicCalamity.cs:160 — Content/Items/Melee/CosmicCalamity.cs:160-169 | Content/Items/Melee/Heartcarver.cs:186-195 | Content/Items/Melee/StormGoddessSpears/StormGoddessSpearHeld.cs:87-96 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) Content/GameModes/BrutalMobs/Mushroom/MushroomBrutalNPC.cs:338 — Content/GameModes/BrutalMobs/Mushroom/MushroomBrutalNPC.cs:338-347 | Content/GameModes/BrutalMobs/Pirates/PirateShipNPC.cs:114-124 | Content/GameModes/BrutalMobs/Temple/TempleBrutalNPC.cs:712-722 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • + 18 more in this group — see findings.md.
D4 · Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) · ×43
  • Edited copies of one member (3 members, 8+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:708 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:708-716 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1203-1210 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:992-999 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) Content/Items/Accessories/ArcaneThroneOfEternity.cs:137 — Content/Items/Accessories/ArcaneThroneOfEternity.cs:137-145 | Content/Items/Accessories/EmblemOfDread.cs:175-182 | Content/Items/Accessories/EyeOfSingularity.cs:162-170 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) Content/HackTimes/Protocols/Electrolysis.cs:113 — Content/HackTimes/Protocols/Electrolysis.cs:113-120 | Content/HackTimes/Protocols/PressureSurge.cs:192-201 | Content/HackTimes/PvP/Protocols/ForceUninstall.cs:78-89 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) Content/Items/Tools/EncyclopediaofOceanicKnowledge.cs:365 — Content/Items/Tools/EncyclopediaofOceanicKnowledge.cs:365-372 | Content/Items/Tools/EncyclopediaofOceanicKnowledge.cs:374-383 | Content/Items/Tools/TheForgottenTome.cs:291-298 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) Content/Industrials/MaterialFlow/Fluids/FluidPipeline.cs:293 — Content/Industrials/MaterialFlow/Fluids/FluidPipeline.cs:293-300 | Content/Industrials/MaterialFlow/Pipelines/PipelineSideState.cs:174-181 | Content/Industrials/MaterialFlow/Pipelines/PipelineSideState.cs:184-192 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) Content/GameModes/BrutalMobs/Ambience/Verdant/VerdantPRT.cs:57 — Content/GameModes/BrutalMobs/Ambience/Verdant/VerdantPRT.cs:57-66 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBoneParticles.cs:154-161 | Content/LegendWeapon/HalibutLegend/FishSkills/FishZombieVFX.cs:290-298 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) Content/Scenarios/Dungeonworld/Gen/Layers/L1/L1Style.cs:85 — Content/Scenarios/Dungeonworld/Gen/Layers/L1/L1Style.cs:85-92 | Content/Scenarios/Dungeonworld/Gen/Layers/L1/L1Style.cs:104-111 | Content/Scenarios/Dungeonworld/Gen/Layers/L7/L7Style.cs:174-181 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) Content/HackTimes/Protocols/NeuralOverclock.cs:124 — Content/HackTimes/Protocols/NeuralOverclock.cs:124-132 | Content/HackTimes/Protocols/ShellRequisition.cs:134-141 | Content/HackTimes/Protocols/WraithForceDrive.cs:148-157 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaTalismans/KikasaTalismanGlyph.cs:43 — Content/LegendWeapon/KikasaLegend/KikasaTalismans/KikasaTalismanGlyph.cs:43-50 | Content/LegendWeapon/OnikiriLegend/UI/OniMeiGlyph.cs:65-72 | Content/LegendWeapon/OnikiriLegend/UI/OniMeiGlyph.cs:75-83 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) Content/Scenarios/Draedon/Quest/DeploySignaltowers/SignalTower/SignalTowerTargetRenderer.cs:214 — Content/Scenarios/Draedon/Quest/DeploySignaltowers/SignalTower/SignalTowerTargetRenderer.cs:214-225 | Content/Scenarios/OldDuke/Campsites/CampsiteDirectionIndicator.cs:231-251 | Content/UIs/StorageUIs/BaseChestRenderer.cs:174-181 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallFX.cs:86 — Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallFX.cs:86-95 | Content/UIs/UIEffect/SvgPathPen.cs:152-159 | Content/UIs/WeaponSkills/WeaponSkillBrush.cs:91-100 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) Content/HackTimes/Protocols/TurretMesh.cs:267 — Content/HackTimes/Protocols/TurretMesh.cs:267-274 | Content/HackTimes/Protocols/VeinResonance.cs:305-312 | Content/HackTimes/Protocols/WraithForceDrive.cs:159-168 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/ServantOfCthulhuAI.cs:242 — Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/ServantOfCthulhuAI.cs:242-249 | Content/NPCs/BrutalNPCs/BrutalPlantera/PlanteraAI.cs:583-590 | Content/NPCs/BrutalNPCs/BrutalPlantera/PlanteraTentacleAI.cs:96-103 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdHammerConeOmen.cs:59 — Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdHammerConeOmen.cs:59-66 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmYetiConeOmen.cs:60-67 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandConeTelegraph.cs:69-76 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) Content/GameModes/GodSmith/Core/GodSmithPlayer.cs:92 — Content/GameModes/GodSmith/Core/GodSmithPlayer.cs:92-99 | Content/GameModes/GodSmith/Core/GodSmithPlayer.cs:101-111 | Content/GameModes/GodSmith/Core/GodSmithPlayer.cs:116-126 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) Content/Items/Tools/SirenMusicalBox.cs:849 — Content/Items/Tools/SirenMusicalBox.cs:849-856 | Content/PRTTypes/PRT_AcidSplash.cs:22-35 | Content/PRTTypes/PRT_AcidSplash.cs:36-46 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) Content/Scenarios/Helen/Gifts/DevourerOfGodsGift.cs:31 — Content/Scenarios/Helen/Gifts/DevourerOfGodsGift.cs:31-38 | Content/Scenarios/Helen/Gifts/LeviathanGift.cs:31-38 | Content/Scenarios/Helen/Gifts/SupremeCalamitasGift.cs:35-42 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) Content/Scenarios/Helen/Gifts/CalamitasCloneGift.cs:32 — Content/Scenarios/Helen/Gifts/CalamitasCloneGift.cs:32-39 | Content/Scenarios/Helen/Gifts/CryogenGift.cs:31-38 | Content/Scenarios/Helen/Gifts/PerforatorGift.cs:31-38 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) Content/Scenarios/Helen/Gifts/BrimstoneElementalGift.cs:31 — Content/Scenarios/Helen/Gifts/BrimstoneElementalGift.cs:31-38 | Content/Scenarios/Helen/Gifts/ProvidenceGift.cs:31-38 | Content/Scenarios/Helen/Gifts/SlimeGodGift.cs:31-38 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) Content/HackTimes/Protocols/StressInvert.cs:249 — Content/HackTimes/Protocols/StressInvert.cs:249-257 | Content/HackTimes/Protocols/TileConscript.cs:292-299 | Content/HackTimes/Protocols/VeinResonance.cs:314-324 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) Content/HackTimes/HackQueueRenderer.cs:228 — Content/HackTimes/HackQueueRenderer.cs:228-235 | Content/HackTimes/HackQueueRenderer.cs:238-246 | Content/HackTimes/HackQueueRenderer.cs:249-257 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) Content/Items/Melee/DestroyersBlade.cs:54 — Content/Items/Melee/DestroyersBlade.cs:54-61 | Content/Items/Melee/EnergySword.cs:69-77 | Content/Items/Modifys/RBloodButcherer.cs:79-87 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishBoneParticles.cs:133 — Content/LegendWeapon/HalibutLegend/FishSkills/FishBoneParticles.cs:133-140 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBunnyParticles.cs:176-183 | Content/LegendWeapon/HalibutLegend/FishSkills/FishZombieVFX.cs:267-275 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) Content/QuestLogs/QuestWorldDecision.cs:54 — Content/QuestLogs/QuestWorldDecision.cs:54-61 | Content/QuestLogs/QuestWorldDecision.cs:63-70 | Content/QuestLogs/QuestWorldDecision.cs:72-81 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:922 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:922-932 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:731-738 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:1007-1018 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • + 18 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×43
  • Duplicated block (10 lines × 3) Content/LegendWeapon/HalibutLegend/DomainSkills/FishTeleport.cs:141 — Content/LegendWeapon/HalibutLegend/DomainSkills/FishTeleport.cs:141-150 | Content/LegendWeapon/HalibutLegend/DomainSkills/SeaDomain.cs:928-937 | Content/LegendWeapon/HalibutLegend/DomainSkills/YourLevelIsTooLow.cs:743-752 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/DomainSkills/FishTeleport.cs:141` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/HalibutLegend/DomainSkills/FishTeleport.cs:139` calls `GetAlpha` and `Content/LegendWeapon/HalibutLegend/DomainSkills/SeaDomain.cs:926` does not — after which the two agree again for 4 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 (10 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPuddle.cs:146 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPuddle.cs:146-155 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuXiFX.cs:96-105 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuXiaoFX.cs:82-91 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPuddle.cs:146` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 3) Content/EntrustManager/Styles/DraedonManagerStyle.cs:334 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:334-343 | Content/EntrustManager/Styles/ForestManagerStyle.cs:343-352 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:332-341 — before extracting anything, compare `Content/EntrustManager/Styles/DraedonManagerStyle.cs` and `Content/EntrustManager/Styles/ForestManagerStyle.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 334 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/EntrustManager/Styles/DraedonManagerStyle.cs:334` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 3) Content/GameModes/BrutalMobs/Ambience/DuneStorm/DuneStormRender.cs:207 — Content/GameModes/BrutalMobs/Ambience/DuneStorm/DuneStormRender.cs:207-216 | Content/GameModes/BrutalMobs/Ambience/Starfall/StarfallAmbientRender.cs:216-225 | Content/Scenarios/Dungeonworld/Ambience/DungeonworldAmbientRender.cs:133-142 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/DuneStorm/DuneStormRender.cs:207` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 3) Content/GameModes/GodSmith/Weapons/Broadswords/GsTheHorsemansBlade.cs:290 — Content/GameModes/GodSmith/Weapons/Broadswords/GsTheHorsemansBlade.cs:290-299 | Content/Items/Melee/DivineSourceBlades/DivineSourceBoltProjectile.cs:173-182 | Content/Items/Modifys/RTerraBlades/TerraLightProj.cs:127-136 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/Broadswords/GsTheHorsemansBlade.cs:290` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 3) Content/NPCs/BloomsandSerpents/States/BssSandDashState.cs:93 — Content/NPCs/BloomsandSerpents/States/BssSandDashState.cs:93-102 | Content/NPCs/BloomsandSerpents/States/BssTailSweepState.cs:101-110 | Content/NPCs/FestersandSerpents/States/FssVenomSkimState.cs:88-97 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Note first that the copies are not typed on the same thing: the declarations holding them bind `ctx` to `BssStateContext` in one and `FssStateContext` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (10 lines × 3) Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:140 — Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:140-149 | Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgStabGlintOmen.cs:128-137 | Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyRavenSwoopOmen.cs:142-151 — before extracting anything, compare `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs` and `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgStabGlintOmen.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 89 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:140` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 3) Content/GameModes/GodSmith/Weapons/MagicChant/GsGrayZapinator.cs:40 — Content/GameModes/GodSmith/Weapons/MagicChant/GsGrayZapinator.cs:40-49 | Content/GameModes/GodSmith/Weapons/MagicChant/GsSpaceGun.cs:35-44 | Content/GameModes/GodSmith/Weapons/MagicChant/GsWaterBolt.cs:40-49 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/MagicChant/GsGrayZapinator.cs:40` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/GameModes/GodSmith/Weapons/MagicChant/GsWaterBolt.cs:51` calls `ChantProjOnSpawnMarked` and `Content/GameModes/GodSmith/Weapons/MagicChant/GsGrayZapinator.cs:50` 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 (10 lines × 3) Content/Items/Magic/Pandemoniums/PandemoniumChannel.cs:465 — Content/Items/Magic/Pandemoniums/PandemoniumChannel.cs:465-474 | Content/Items/Magic/Pandemoniums/PandemoniumCircle.cs:188-197 | Content/Items/Magic/Pandemoniums/PandemoniumRSkill.cs:392-401 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/Pandemoniums/PandemoniumChannel.cs:465` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (10 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:40 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:40-49 | Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs:42-51 | Content/Scenarios/Kiame/Overlay/OniRainWorldRender.cs:36-45 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs` and `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 192 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:40` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 3) Content/GameModes/GodSmith/Weapons/Bows/Projectiles/GsTideSpoutProj.cs:23 — Content/GameModes/GodSmith/Weapons/Bows/Projectiles/GsTideSpoutProj.cs:23-32 | Content/GameModes/GodSmith/Weapons/Bows/Projectiles/GsVolleyBurstProj.cs:39-48 | Content/GameModes/GodSmith/Weapons/Bows/TsunamiScheme.cs:166-175 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/Bows/Projectiles/GsTideSpoutProj.cs:23` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 3) Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:566 — Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:566-575 | Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:602-611 | Content/Items/Modifys/RBloodButcherer.cs:545-554 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:566` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 3) Content/Industrials/ElectricPowers/Launchers/PlayerLauncherTile.cs:33 — Content/Industrials/ElectricPowers/Launchers/PlayerLauncherTile.cs:33-42 | Content/Industrials/ElectricPowers/Sundials/ElectricSundialTile.cs:39-48 | Content/Industrials/ElectricPowers/Throwers/ThrowerTile.cs:39-48 — before extracting anything, compare `Content/Industrials/ElectricPowers/Sundials/ElectricSundialTile.cs` and `Content/Industrials/ElectricPowers/Throwers/ThrowerTile.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Launchers/PlayerLauncherTile.cs:33` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 3) Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs:226 — Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs:226-235 | Content/Items/Magic/Everdeeps/EverdeepMaelstrom.cs:350-359 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronSharkTornadoProj.cs:343-352 — before extracting anything, compare `Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs` and `Content/Items/Magic/Everdeeps/EverdeepMaelstrom.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs:226` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 3) Content/Items/Magic/Elysiums/Disciples/BaseDisciple.cs:54 — Content/Items/Magic/Elysiums/Disciples/BaseDisciple.cs:54-63 | Content/Items/Magic/Elysiums/Disciples/James.cs:76-85 | Content/Items/Magic/Elysiums/Revelations/CelestialMeteor.cs:32-41 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/Elysiums/Disciples/BaseDisciple.cs:54` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 3) Content/LegendWeapon/HalibutLegend/FishSkills/FishDemonicHell.cs:322 — Content/LegendWeapon/HalibutLegend/FishSkills/FishDemonicHell.cs:322-331 | Content/LegendWeapon/HalibutLegend/FishSkills/FishHarpy.cs:162-171 | Content/LegendWeapon/SHPCLegend/Modules/Grip/CrystalGripModule.cs:65-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishDemonicHell.cs:322` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 3) Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberExecutionBoltProj.cs:391 — Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberExecutionBoltProj.cs:391-400 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberGlitchBoltProj.cs:134-143 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberRiftSlashProj.cs:137-146 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 3) Content/GameModes/GodSmith/Weapons/MagicCataclysm/GsBetsysWrath.cs:34 — Content/GameModes/GodSmith/Weapons/MagicCataclysm/GsBetsysWrath.cs:34-43 | Content/GameModes/GodSmith/Weapons/MagicCataclysm/GsRazorpine.cs:33-42 | Content/GameModes/GodSmith/Weapons/MagicMorph/GsMorphFangStaves.cs:25-34 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (10 lines × 3) Content/GameModes/GodSmith/Weapons/MagicChant/GsCursedFlames.cs:35 — Content/GameModes/GodSmith/Weapons/MagicChant/GsCursedFlames.cs:35-44 | Content/GameModes/GodSmith/Weapons/MagicChant/GsGoldenShower.cs:51-60 | Content/GameModes/GodSmith/Weapons/MagicChant/GsUnholyTrident.cs:34-43 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/GodSmith/Weapons/MagicChant/GsGoldenShower.cs:47` calls `InPressure` and `Content/GameModes/GodSmith/Weapons/MagicChant/GsUnholyTrident.cs:30` does not — after which the two agree again for 3 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 (10 lines × 3) Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:98 — Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:98-107 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsScourgeoftheCorruptor.cs:85-94 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsVampireKnives.cs:169-178 — 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) Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:396 — Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:396-405 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:425-434 | Content/Industrials/ElectricPowers/Recyclers/RecyclerUI.cs:402-411 — before extracting anything, compare `Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs` and `Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 303 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 3) Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs:188 — Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs:188-197 | Content/Items/Magic/Everdeeps/EverdeepMaelstrom.cs:312-322 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronSharkTornadoProj.cs:304-313 — before extracting anything, compare `Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs` and `Content/Items/Magic/Everdeeps/EverdeepMaelstrom.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (10 lines × 3) Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMoonFlare.cs:279 — Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMoonFlare.cs:279-288 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteStarSurge.cs:193-202 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistZodiacRing.cs:182-191 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMoonFlare.cs:279` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (10 lines × 3) Content/Items/BloomArsenal.cs:181 — Content/Items/BloomArsenal.cs:181-190 | Content/Items/Summon/BloomCallers/BloomCallerSprout.cs:428-437 | Content/NPCs/BloomsandSerpents/Projectiles/BssNeedleProj.cs:46-55 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (10 lines × 3) Content/Items/Magic/CommandersStaff.cs:22 — Content/Items/Magic/CommandersStaff.cs:22-31 | Content/Items/Magic/CommandersStaff.cs:55-64 | Content/Items/Magic/FocusingGrimoire.cs:25-34 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/CommandersStaff.cs:22` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Magic/FocusingGrimoire.cs:23` calls `VaultLoaden` and `Content/Items/Magic/CommandersStaff.cs:21` does not — after which the two agree again for 3 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.
  • + 18 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×40
  • Edited copy of a member (20 corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSlashRenderer.cs:312 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSlashRenderer.cs:312-336 | Content/LegendWeapon/OnikiriLegend/OniSakuraFlights/OniSakuraFlowRenderer.cs:50-73 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) Content/Items/Magic/Elysiums/Revelations/CelestialMeteor.cs:81 — Content/Items/Magic/Elysiums/Revelations/CelestialMeteor.cs:81-103 | Content/Items/Magic/Elysiums/Revelations/RevelationSealJudgment.cs:152-171 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaHandRig.cs:192 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaHandRig.cs:192-211 | Content/Wraiths/Projectiles/GhostHandRig.cs:200-219 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) Content/Items/Ranged/Starships/StarshipMicroStar.cs:42 — Content/Items/Ranged/Starships/StarshipMicroStar.cs:42-64 | Content/Items/Ranged/Starships/StarshipWingman.cs:79-98 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) Content/NPCs/BloomsandSerpents/States/BssBurrowLungeState.cs:296 — Content/NPCs/BloomsandSerpents/States/BssBurrowLungeState.cs:296-323 | Content/NPCs/BloomsandSerpents/States/BssSandSurgeState.cs:232-251 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) Content/Items/Magic/Elysiums/Disciples/John.cs:32 — Content/Items/Magic/Elysiums/Disciples/John.cs:32-52 | Content/Items/Magic/Elysiums/Disciples/Matthew.cs:35-54 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhShellSpike.cs:64 — Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhShellSpike.cs:64-83 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomNeedle.cs:91-117 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) Content/Scenarios/Dungeonworld/Gen/BossRooms/ProofingHallRoom.cs:343 — Content/Scenarios/Dungeonworld/Gen/BossRooms/ProofingHallRoom.cs:343-362 | Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Palette.cs:114-133 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) Content/Items/Melee/SporeburstPouch.cs:127 — Content/Items/Melee/SporeburstPouch.cs:127-147 | Content/Items/Melee/SporeburstPouch.cs:212-231 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Optic/EchoOpticModule.cs:23 — Content/LegendWeapon/SHPCLegend/Modules/Optic/EchoOpticModule.cs:23-42 | Content/LegendWeapon/SHPCLegend/Modules/Stock/LaunchStockModule.cs:20-41 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) Content/Wraiths/Deaths/Performances/ScapeSeizurePerformance.cs:144 — Content/Wraiths/Deaths/Performances/ScapeSeizurePerformance.cs:144-166 | Content/Wraiths/VFX/ScapeArmRenderer.cs:367-386 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) Content/GameModes/GodSmith/Weapons/Spears/GsNorthPole.cs:82 — Content/GameModes/GodSmith/Weapons/Spears/GsNorthPole.cs:82-102 | Content/GameModes/GodSmith/Weapons/Spears/GsSwordfish.cs:72-91 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) Content/Scenarios/Dungeonworld/Gen/Rooms/RoomPlacer.cs:15 — Content/Scenarios/Dungeonworld/Gen/Rooms/RoomPlacer.cs:15-34 | Content/Scenarios/OldNet/Gen/Rooms/OldNetRoomPlacer.cs:16-35 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishVariegatedLard.cs:83 — Content/LegendWeapon/HalibutLegend/FishSkills/FishVariegatedLard.cs:83-103 | Content/LegendWeapon/HalibutLegend/FishSkills/FishVariegatedLard.cs:432-451 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) Content/GameModes/BrutalMobs/Ambience/Rotmire/RotmireVentSystem.cs:186 — Content/GameModes/BrutalMobs/Ambience/Rotmire/RotmireVentSystem.cs:186-209 | Content/GameModes/BrutalMobs/Ambience/Rotmire/RotmireVentSystem.cs:244-263 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) Content/Scenarios/Dungeonworld/Ambience/AmbientPRT.cs:135 — Content/Scenarios/Dungeonworld/Ambience/AmbientPRT.cs:135-154 | Content/Scenarios/Dungeonworld/Ambience/AmbientPRT.cs:408-429 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) Content/GameModes/BrutalMobs/Ambience/Bloodveil/BloodveilAmbience.cs:147 — Content/GameModes/BrutalMobs/Ambience/Bloodveil/BloodveilAmbience.cs:147-167 | Content/GameModes/BrutalMobs/Ambience/Woodsong/WoodsongAmbience.cs:720-739 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) Content/Items/Magic/BloomTomes/BloomTome.cs:78 — Content/Items/Magic/BloomTomes/BloomTome.cs:78-97 | Content/Items/Ranged/Thornstrings/ThornstringArrow.cs:38-58 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/MoldProcessingTableTile.cs:21 — Content/LegendWeapon/SHPCLegend/MoldProcessingTables/MoldProcessingTableTile.cs:21-40 | Content/Scenarios/Draedon/Quest/DeploySignaltowers/DeploySignaltower.cs:40-61 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs:78 — Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs:78-99 | Content/NPCs/FestersandSerpents/Projectiles/FssIchorGlob.cs:78-97 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) Content/Scenarios/Dungeonworld/Fog/DungeonworldFogTheme.cs:34 — Content/Scenarios/Dungeonworld/Fog/DungeonworldFogTheme.cs:34-54 | Content/Scenarios/Kiyume/Fog/KiyumeFogTheme.cs:25-44 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) Content/Items/Melee/CommandersChainsaw.cs:19 — Content/Items/Melee/CommandersChainsaw.cs:19-39 | Content/Items/Melee/CommandersChainsaw.cs:48-67 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs:181 — Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs:181-200 | Content/Items/Melee/WeaverGrievanceses/WGManifestationNet.cs:182-201 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/States/EmpressEchoState.cs:89 — Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/States/EmpressEchoState.cs:89-112 | Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:1891-1910 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) Content/Industrials/ElectricPowers/Lumberjacks/LumberjackSaw.cs:485 — Content/Industrials/ElectricPowers/Lumberjacks/LumberjackSaw.cs:485-521 | Content/Industrials/ElectricPowers/Lumberjacks/WGGLumberjack.cs:778-797 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • + 15 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (21 corresponding lines) · ×39
  • Edited copy of a member (21 corresponding lines) Content/Narrative/Common/BaseRecipeDisplayUI.cs:225 — Content/Narrative/Common/BaseRecipeDisplayUI.cs:225-248 | Content/Scenarios/Draedon/Quest/DeploySignaltowers/DeploySignaltowerRender.cs:245-265 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) Content/Items/Magic/WheezingWyrms/WheezingWyrmHeld.cs:201 — Content/Items/Magic/WheezingWyrms/WheezingWyrmHeld.cs:201-227 | Content/Items/Magic/WheezingWyrms/WheezingWyrmHeld.cs:292-312 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) Content/GameModes/GodSmith/Weapons/MagicChant/GsCursedFlames.cs:99 — Content/GameModes/GodSmith/Weapons/MagicChant/GsCursedFlames.cs:99-119 | Content/GameModes/GodSmith/Weapons/MagicChant/GsGoldenShower.cs:138-159 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaWisps/KikasaWispPRT.cs:57 — Content/LegendWeapon/KikasaLegend/KikasaWisps/KikasaWispPRT.cs:57-77 | Content/LegendWeapon/KikasaLegend/KikasaWisps/KikasaWispPRT.cs:141-161 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) Content/Industrials/ElectricPowers/TreeRegrowths/TreeBlueprint.cs:454 — Content/Industrials/ElectricPowers/TreeRegrowths/TreeBlueprint.cs:454-477 | Content/Industrials/ElectricPowers/TreeRegrowths/TreeBlueprint.cs:479-499 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishWyverntailVFX.cs:93 — Content/LegendWeapon/HalibutLegend/FishSkills/FishWyverntailVFX.cs:93-115 | Content/LegendWeapon/HalibutLegend/FishSkills/FishWyverntailVFX.cs:118-138 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:825 — Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:825-845 | Content/Items/Melee/WeaverGrievanceses/WGManifestationActor.cs:717-737 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) Content/PRTTypes/PRT_SHPCExtenderShred.cs:50 — Content/PRTTypes/PRT_SHPCExtenderShred.cs:50-74 | Content/PRTTypes/PRT_SHPCHeavySpall.cs:55-75 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) Content/Scenarios/Kiame/Gen/Passes/KiameSkeletonPass.cs:71 — Content/Scenarios/Kiame/Gen/Passes/KiameSkeletonPass.cs:71-91 | Content/Scenarios/Kiyume/Gen/Passes/KiyumeSkeletonPass.cs:65-85 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1107 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1107-1127 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1113-1133 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishCursedVFX.cs:241 — Content/LegendWeapon/HalibutLegend/FishSkills/FishCursedVFX.cs:241-262 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDemonicHell.cs:756-776 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishIchorn.cs:307 — Content/LegendWeapon/HalibutLegend/FishSkills/FishIchorn.cs:307-328 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonOrb.cs:229-249 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserBoltProj.cs:54 — Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserBoltProj.cs:54-75 | Content/GameModes/BrutalMobs/Martians/Projectiles/MrtScutlixHeavyBolt.cs:45-65 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerShockwave.cs:46 — Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerShockwave.cs:46-66 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/TwinsSupernovaBlast.cs:59-80 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspacePlayer.cs:675 — Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspacePlayer.cs:675-695 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspacePlayer.cs:697-721 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) Content/GameModes/GodSmith/Weapons/MagicMorph/Projectiles/GsNimbusCorridorProj.cs:125 — Content/GameModes/GodSmith/Weapons/MagicMorph/Projectiles/GsNimbusCorridorProj.cs:125-148 | Content/GameModes/GodSmith/Weapons/MagicMorph/Projectiles/GsRiftProj.cs:69-89 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Barrel/RapidBarrelModule.cs:358 — Content/LegendWeapon/SHPCLegend/Modules/Barrel/RapidBarrelModule.cs:358-378 | Content/LegendWeapon/SHPCLegend/Modules/Stock/SteadyStockModule.cs:369-395 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs:580 — Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs:580-603 | Content/Scenarios/Shenyo/ShenyoPortraitRainRenderer.cs:562-582 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:131 — Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:131-151 | Content/Scenarios/Kiyume/UI/KiyumeLoadingScreen.cs:129-151 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) Content/Items/Melee/CommandersClaw.cs:277 — Content/Items/Melee/CommandersClaw.cs:277-301 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeSeekerMissile.cs:164-184 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) Content/Wraiths/Projectiles/LanternBoyProj.cs:523 — Content/Wraiths/Projectiles/LanternBoyProj.cs:523-543 | Content/Wraiths/Projectiles/LanternBoyProj.cs:545-568 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberChargeOrbProj.cs:537 — Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberChargeOrbProj.cs:537-557 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberTraceBeamProj.cs:593-614 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmNutShellProj.cs:62 — Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmNutShellProj.cs:62-82 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtRicochetShot.cs:166-187 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) Content/GameModes/BrutalMobs/Ambience/Frostveil/FrostveilPlayer.cs:163 — Content/GameModes/BrutalMobs/Ambience/Frostveil/FrostveilPlayer.cs:163-183 | Content/GameModes/BrutalMobs/Ambience/Verdant/VerdantPlayer.cs:148-168 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) Content/GameModes/GodSmith/Weapons/Bows/GsChargeBowHeld.cs:288 — Content/GameModes/GodSmith/Weapons/Bows/GsChargeBowHeld.cs:288-308 | Content/GameModes/GodSmith/Weapons/Bows/PhantasmScheme.cs:322-342 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • + 14 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (6 lines × 5) · ×39
  • Duplicated block (6 lines × 5) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:393 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:393-398 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs:404-409 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:320-325 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconUI.cs:355-360 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:393-398 — before extracting anything, compare `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs` and `Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 226 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs:414` calls `Sin` and `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:402` 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 (6 lines × 5) Content/NPCs/ScrapCommanders/ScrapCommander.cs:142 — Content/NPCs/ScrapCommanders/ScrapCommander.cs:142-147 | Content/NPCs/SeaShrimp/SeaShrimpBoss.cs:69-74 | Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:263-268 | Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:237-242 | Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:283-288 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.
  • Duplicated block (6 lines × 5) Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteDiveOmen.cs:146 — Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteDiveOmen.cs:146-151 | Content/GameModes/BrutalMobs/NightPack/Projectiles/NightDiveOmen.cs:159-164 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkChargeOmen.cs:171-176 | Content/GameModes/BrutalMobs/Sky/Projectiles/SkyGaleDiveOmen.cs:140-145 | Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornDiveLane.cs:142-147 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteDiveOmen.cs:146` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (6 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:274 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:274-279 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:1056-1061 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1287-1292 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1341-1346 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1427-1432 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:274` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1339` calls `Clamp` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:272` 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 (6 lines × 5) Content/Scenarios/Shepel/Dialogues/Situational/ShepelDungeonDialogue.cs:11 — Content/Scenarios/Shepel/Dialogues/Situational/ShepelDungeonDialogue.cs:11-16 | Content/Scenarios/Shepel/Dialogues/Situational/ShepelJungleDialogue.cs:11-16 | Content/Scenarios/Shepel/Dialogues/Situational/ShepelOceanDialogue.cs:11-16 | Content/Scenarios/Shepel/Dialogues/Situational/ShepelSnowBiomeDialogue.cs:11-16 | Content/Scenarios/Shepel/Dialogues/Situational/ShepelUnderworldDialogue.cs:11-16 — 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 5 call sites, so a change lands once.
  • Duplicated block (6 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:358 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:358-363 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:499-504 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:359-364 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:463-468 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:411-416 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:358` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:367` calls `PlaySound` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:419` 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 (6 lines × 5) Content/Scenarios/Shepel/Dialogues/Situational/ShepelDungeonDialogue.cs:11 — Content/Scenarios/Shepel/Dialogues/Situational/ShepelDungeonDialogue.cs:11-16 | Content/Scenarios/Shepel/Dialogues/Situational/ShepelFirstNightDialogue.cs:13-18 | Content/Scenarios/Shepel/Dialogues/Situational/ShepelJungleDialogue.cs:11-16 | Content/Scenarios/Shepel/Dialogues/Situational/ShepelOceanDialogue.cs:11-16 | Content/Scenarios/Shepel/Dialogues/Situational/ShepelUnderworldDialogue.cs:11-16 — 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 5 call sites, so a change lands once.
  • Duplicated block (6 lines × 5) Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:571 — Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:571-576 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsSickle.cs:168-173 | Content/GameModes/GodSmith/Weapons/Shortswords/GsThrustHeldBase.cs:985-990 | Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:607-612 | Content/Items/Modifys/RBloodButcherer.cs:550-555 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:571` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6 lines × 5) Content/Items/Melee/Flawless.cs:561 — Content/Items/Melee/Flawless.cs:561-566 | Content/Items/Melee/StormGoddessSpears/StormGoddessSpearHeld.cs:527-532 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:796-801 | Content/Items/Stones/Marbles/MarbleClub.cs:589-594 | Content/Items/Stones/Marbles/MarbleHuntingKnife.cs:406-411 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Flawless.cs:561` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6 lines × 5) Content/Items/Modifys/RBloodButcherer.cs:1027 — Content/Items/Modifys/RBloodButcherer.cs:1027-1035 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunBullet.cs:271-279 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:222-227 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:253-261 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterGlob.cs:198-203 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Modifys/RBloodButcherer.cs:1027` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6 lines × 5) Content/LegendWeapon/HalibutLegend/FishSkills/FishBone.cs:607 — Content/LegendWeapon/HalibutLegend/FishSkills/FishBone.cs:607-612 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDoubleCod.cs:355-360 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDynamite.cs:399-404 | Content/LegendWeapon/HalibutLegend/FishSkills/FishHarpy.cs:668-673 | Content/LegendWeapon/HalibutLegend/FishSkills/FishPrincess.cs:662-667 — 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 5 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/HalibutLegend/FishSkills/FishDoubleCod.cs:361` calls `ToRotation` and `Content/LegendWeapon/HalibutLegend/FishSkills/FishPrincess.cs:669` does not — after which the two agree again for 4 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 (6 lines × 5) Content/LegendWeapon/HalibutLegend/FishSkills/FishIchornVFX.cs:185 — Content/LegendWeapon/HalibutLegend/FishSkills/FishIchornVFX.cs:185-191 | Content/LegendWeapon/HalibutLegend/FishSkills/FishScorpioPRT.cs:72-79 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:325-330 | Content/PRTTypes/PRT_KikasaInkBead.cs:62-67 | Content/Scenarios/Dungeonworld/NPCs/GaolFireBolt.cs:275-280 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. 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 (6 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainDeco.cs:145 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainDeco.cs:145-150 | Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:190-195 | Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:209-214 | Content/Scenarios/Kiame/Overlay/OniRainExitTransition.cs:147-152 | Content/Scenarios/Kiame/Overlay/OniRainExitTransition.cs:166-171 — before extracting anything, compare `Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs` and `Content/Scenarios/Kiame/Overlay/OniRainExitTransition.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 186 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainDeco.cs:145` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainDeco.cs:152` calls `NextBool`, `RippleAt`, `Vector2` and `Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:215` 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 (6 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPour.cs:531 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPour.cs:531-536 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPuddle.cs:144-149 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuXiFX.cs:94-99 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuXiaoFX.cs:80-85 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuYuFX.cs:52-57 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPour.cs:531` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1180 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1180-1186 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1202-1207 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1533-1540 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:1003-1008 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:961-967 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs` as WHOLE FILES: this scan already matched 55 separate duplicated blocks between them, totalling at least 611 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1180` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangProj.cs:176 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangProj.cs:176-181 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailHead.cs:180-185 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipLash.cs:215-220 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoProj.cs:202-207 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshEyeLaser.cs:182-187 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangProj.cs:176` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshEyeLaser.cs:190` calls `PlaySound` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipLash.cs:223` 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 (6 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:802 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:802-807 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:883-888 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1058-1063 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:798-803 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:965-970 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:802` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:208 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:208-213 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1503-1508 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1375-1380 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1561-1566 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:1174-1179 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:208` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:518 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:518-524 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:373-378 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:367-372 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:445-450 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:462-467 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:518` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:379` calls `PlaySound` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:525` 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 (6 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:530 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:530-536 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:423-429 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:379-385 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:457-463 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:474-479 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:530` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1513 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1513-1518 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:1366-1371 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:996-1001 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:938-943 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:1602-1607 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1513` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:1599` calls `OrderMinesMelt` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1510` does not — after which the two agree again for 3 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 (6 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:1059 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:1059-1064 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1276-1281 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1344-1349 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1430-1435 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1236-1241 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. 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 (6 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:1063 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:1063-1068 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:921-926 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1356-1361 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1561-1566 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1315-1320 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:1063` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:936 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:936-941 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeLaserBolt.cs:96-101 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeMortar.cs:226-231 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:465-470 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:401-406 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:936` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6 lines × 5) Content/LegendWeapon/OnikiriLegend/UI/OniLedgerSwapFX.cs:131 — Content/LegendWeapon/OnikiriLegend/UI/OniLedgerSwapFX.cs:131-136 | Content/LegendWeapon/OnikiriLegend/UI/OniMeiStandDraw.cs:39-46 | Content/LegendWeapon/OnikiriLegend/UI/OniMoonDraw.cs:44-50 | Content/LegendWeapon/OnikiriLegend/UI/OniSigilBoardDraw.cs:62-67 | Content/LegendWeapon/OnikiriLegend/UI/OniVigorInkDraw.cs:57-64 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/UI/OniLedgerSwapFX.cs` and `Content/LegendWeapon/OnikiriLegend/UI/OniVigorInkDraw.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 44 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/UI/OniLedgerSwapFX.cs:131` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • + 14 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (23 corresponding lines) · ×38
  • Edited copy of a member (23 corresponding lines) Content/Narrative/MusicToast.cs:547 — Content/Narrative/MusicToast.cs:547-569 | Content/Narrative/MusicToast.cs:624-646 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) Content/NPCs/BrutalNPCs/BrutalSkeletron/Rendering/SkeletronFlameRender.cs:114 — Content/NPCs/BrutalNPCs/BrutalSkeletron/Rendering/SkeletronFlameRender.cs:114-136 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Rendering/SkeletronFlameRender.cs:139-167 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuMeiFX.cs:25 — Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuMeiFX.cs:25-58 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuXiaFX.cs:43-65 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) Content/PRTTypes/PRT_ProcChip.cs:63 — Content/PRTTypes/PRT_ProcChip.cs:63-85 | Content/PRTTypes/PRT_SHPCObsidianChip.cs:64-87 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) Content/GameModes/BrutalMobs/Ambience/AmbientFogDraw.cs:225 — Content/GameModes/BrutalMobs/Ambience/AmbientFogDraw.cs:225-252 | Content/GameModes/BrutalMobs/Ambience/AmbientFogDraw.cs:255-277 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) Content/Items/Ranged/AnnihilatingUniverses/CelestialObliterationArrow.cs:96 — Content/Items/Ranged/AnnihilatingUniverses/CelestialObliterationArrow.cs:96-118 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/DeadLaser.cs:71-93 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) Content/GameModes/GodSmith/Armors/Reset/GsSpectreArmors.cs:103 — Content/GameModes/GodSmith/Armors/Reset/GsSpectreArmors.cs:103-125 | Content/GameModes/GodSmith/Armors/Reset/GsTikiArmor.cs:68-90 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaRender.cs:280 — Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaRender.cs:280-302 | Content/NPCs/BrutalNPCs/BrutalPlantera/Rendering/PlanteraBloomRender.cs:102-125 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSGelGlobProj.cs:76 — Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSGelGlobProj.cs:76-98 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSMassGlobProj.cs:184-210 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraSeed.cs:100 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraSeed.cs:100-122 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenCrystalShard.cs:138-161 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) Content/Scenarios/Kiame/KiameWake.cs:225 — Content/Scenarios/Kiame/KiameWake.cs:225-247 | Content/Scenarios/Kiyume/Stealth/KiyumeDreamWake.cs:127-160 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsFlameBreath.cs:155 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsFlameBreath.cs:155-177 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshEyeLaser.cs:139-163 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) Content/Items/Stones/Marbles/MarbleClub.cs:552 — Content/Items/Stones/Marbles/MarbleClub.cs:552-574 | Content/Items/Stones/Marbles/MarbleHuntingKnife.cs:367-390 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) Content/GameModes/GodSmith/Weapons/Guns/GsHarpoon.cs:316 — Content/GameModes/GodSmith/Weapons/Guns/GsHarpoon.cs:316-338 | Content/Items/Melee/Budcrowns/Budcrown.cs:271-296 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) Content/GameModes/BrutalMobs/Legion/LegionNPC.cs:489 — Content/GameModes/BrutalMobs/Legion/LegionNPC.cs:489-513 | Content/GameModes/BrutalMobs/Legion/LegionNPC.cs:517-539 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) Content/Items/Melee/StormGoddessSpears/StormGoddess.cs:622 — Content/Items/Melee/StormGoddessSpears/StormGoddess.cs:622-648 | Content/Items/Melee/StormGoddessSpears/StormGoddessSpearHeld.cs:347-369 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1350 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1350-1374 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1546-1568 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishTunabeardVFX.cs:164 — Content/LegendWeapon/HalibutLegend/FishSkills/FishTunabeardVFX.cs:164-186 | Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniKamuiFlowRenderer.cs:36-58 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) Content/NPCs/BloomsandSerpents/States/BssPillarVaultState.cs:342 — Content/NPCs/BloomsandSerpents/States/BssPillarVaultState.cs:342-364 | Content/NPCs/BloomsandSerpents/States/BssVortexDashState.cs:240-264 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) Content/TimeFreezes/TimeFreezeSystem.cs:945 — Content/TimeFreezes/TimeFreezeSystem.cs:945-977 | Content/TimeFreezes/TimeFreezeSystem.cs:1093-1115 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) Content/Items/Melee/DestroyersBlade.cs:587 — Content/Items/Melee/DestroyersBlade.cs:587-609 | Content/Items/Melee/DestroyersBladeEXs/DestroyersBeamEX.cs:41-71 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) Content/Items/Armor/Deepcrystals/DeepcrystalNet.cs:29 — Content/Items/Armor/Deepcrystals/DeepcrystalNet.cs:29-51 | Content/LegendWeapon/KikasaLegend/KikasaVaults/KikasaLakeNet.cs:31-65 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) Content/Scenarios/OldNet/Tiles/OldNetEventNodeTile.cs:48 — Content/Scenarios/OldNet/Tiles/OldNetEventNodeTile.cs:48-70 | Content/Scenarios/OldNet/Tiles/OldNetLedgerDockTile.cs:48-73 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) Content/GameModes/BrutalMobs/Ambience/Stonewake/StonewakeAmbience.cs:273 — Content/GameModes/BrutalMobs/Ambience/Stonewake/StonewakeAmbience.cs:273-295 | Content/GameModes/BrutalMobs/Ambience/Stonewake/StonewakeAmbience.cs:298-320 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) Content/Scenarios/Dungeonworld/Gen/Layers/L4/L4WaterWorks.cs:158 — Content/Scenarios/Dungeonworld/Gen/Layers/L4/L4WaterWorks.cs:158-180 | Content/Scenarios/Dungeonworld/Gen/Zones/SlagVentBelt.cs:329-356 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • + 13 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (25 corresponding lines) · ×35
  • Edited copy of a member (25 corresponding lines) Content/PRTTypes/PRT_CyberConverge.cs:94 — Content/PRTTypes/PRT_CyberConverge.cs:94-118 | Content/PRTTypes/PRT_CyberSquare.cs:55-79 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishBunny.cs:541 — Content/LegendWeapon/HalibutLegend/FishSkills/FishBunny.cs:541-565 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBunny.cs:618-646 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs:147 — Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs:147-171 | Content/NPCs/FestersandSerpents/Projectiles/FssIchorGlob.cs:145-169 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuLaoFX.cs:139 — Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuLaoFX.cs:139-163 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuXiFX.cs:186-213 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) Content/NPCs/BloomsandSerpents/Projectiles/BssDashOmen.cs:131 — Content/NPCs/BloomsandSerpents/Projectiles/BssDashOmen.cs:131-155 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronTelegraph.cs:134-160 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) Content/Industrials/ElectricPowers/TeleportStations/TeleportStationTP.cs:214 — Content/Industrials/ElectricPowers/TeleportStations/TeleportStationTP.cs:214-238 | Content/Industrials/ElectricPowers/TeleportStations/TeleportStationTP.cs:241-265 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) Content/Items/Accessories/BrutalRelics/Destroyer/ProbeLockBolt.cs:114 — Content/Items/Accessories/BrutalRelics/Destroyer/ProbeLockBolt.cs:114-140 | Content/Items/Ranged/UniversalFrost.cs:255-279 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Rendering/EowMotionFX.cs:107 — Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Rendering/EowMotionFX.cs:107-135 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Core/QueenMotion.cs:133-157 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) Content/GameModes/UI/GameModeRenderer.cs:681 — Content/GameModes/UI/GameModeRenderer.cs:681-705 | Content/LegendWeapon/KikasaLegend/UI/KikasaItemTooltipPanel.cs:34-65 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) Content/Scenarios/Kiame/Gen/Passes/KiameScatterPass.cs:56 — Content/Scenarios/Kiame/Gen/Passes/KiameScatterPass.cs:56-80 | Content/Scenarios/Kiyume/Gen/Passes/KiyumeScatterPass.cs:53-78 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiStrikes.cs:619 — Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiStrikes.cs:619-643 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiStrikes.cs:711-738 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) Content/Cyberwares/Tutorial/CyberwareGuideLead.cs:397 — Content/Cyberwares/Tutorial/CyberwareGuideLead.cs:397-421 | Content/Scenarios/Shepel/CybCourses/CybCourseCardStyle.cs:57-81 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) Content/GameModes/BrutalMobs/Martians/Projectiles/MrtGuardShieldProj.cs:125 — Content/GameModes/BrutalMobs/Martians/Projectiles/MrtGuardShieldProj.cs:125-153 | Content/GameModes/BrutalMobs/Martians/Projectiles/MrtReinforceSignalProj.cs:92-116 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) Content/Narrative/Presentation/Skins/Kikasa/KikasaDialogueSkin.cs:60 — Content/Narrative/Presentation/Skins/Kikasa/KikasaDialogueSkin.cs:60-84 | Content/Narrative/Presentation/Skins/Onikiri/OnikiriDialogueSkin.cs:60-84 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) Content/NPCs/BloomsandSerpents/BssVfx.cs:132 — Content/NPCs/BloomsandSerpents/BssVfx.cs:132-156 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/CultistBossAI.cs:275-299 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) Content/NPCs/BloomsandSerpents/States/BssIntroState.cs:33 — Content/NPCs/BloomsandSerpents/States/BssIntroState.cs:33-67 | Content/NPCs/FestersandSerpents/States/FssIntroState.cs:34-58 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishCursedVFX.cs:173 — Content/LegendWeapon/HalibutLegend/FishSkills/FishCursedVFX.cs:173-197 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCursedVFX.cs:396-422 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerCoilCrushState.cs:300 — Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerCoilCrushState.cs:300-324 | Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerEncircleState.cs:117-144 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) Content/GameModes/BrutalMobs/Mushroom/MushroomBrutalNPC.cs:433 — Content/GameModes/BrutalMobs/Mushroom/MushroomBrutalNPC.cs:433-465 | Content/GameModes/BrutalMobs/Mushroom/MushroomBrutalNPC.cs:495-519 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishMud.cs:61 — Content/LegendWeapon/HalibutLegend/FishSkills/FishMud.cs:61-85 | Content/LegendWeapon/HalibutLegend/FishSkills/FishScorpio.cs:66-97 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) Content/Items/Ranged/CrystalDimming.cs:120 — Content/Items/Ranged/CrystalDimming.cs:120-144 | Content/Items/Ranged/UniversalFrost.cs:136-173 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:348 — Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:348-372 | Content/Items/Melee/WeaverGrievanceses/WGManifestationActor.cs:283-307 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) Content/GameModes/BrutalMobs/Mushroom/MushroomBrutalNPC.cs:351 — Content/GameModes/BrutalMobs/Mushroom/MushroomBrutalNPC.cs:351-375 | Content/GameModes/BrutalMobs/Mushroom/MushroomBrutalNPC.cs:542-568 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishTunabeard.cs:38 — Content/LegendWeapon/HalibutLegend/FishSkills/FishTunabeard.cs:38-62 | Content/LegendWeapon/HalibutLegend/FishSkills/FishUnicorn.cs:37-61 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) Content/NPCs/BrutalNPCs/BrutalDeerclops/DeerclopsDeathCutscene.cs:17 — Content/NPCs/BrutalNPCs/BrutalDeerclops/DeerclopsDeathCutscene.cs:17-42 | Content/NPCs/BrutalNPCs/BrutalGolem/GolemDeathCutscene.cs:17-41 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • + 10 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (22 corresponding lines) · ×35
  • Edited copy of a member (22 corresponding lines) Content/EntrustManager/Styles/ForestManagerStyle.cs:223 — Content/EntrustManager/Styles/ForestManagerStyle.cs:223-246 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:210-231 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) Content/Scenarios/Draedon/Quest/DeploySignaltowers/CQETConstructor.cs:473 — Content/Scenarios/Draedon/Quest/DeploySignaltowers/CQETConstructor.cs:473-495 | Content/Scenarios/Draedon/Quest/DeploySignaltowers/CQETConstructor.cs:604-625 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeSlash.cs:76 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeSlash.cs:76-97 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithSlash.cs:89-110 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs:284 — Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs:284-311 | Content/LegendWeapon/SHPCLegend/UI/DomainWheel/SHPCDomainWheelUI.cs:252-273 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) Content/Scenarios/Dungeonworld/UI/DungeonworldLoadingScreen.cs:553 — Content/Scenarios/Dungeonworld/UI/DungeonworldLoadingScreen.cs:553-574 | Content/Scenarios/Hadalworld/UI/HadalworldLoadingScreen.cs:408-431 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:1363 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:1363-1384 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:1597-1621 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) Content/Items/Accessories/BrutalRelics/KingSlime/FallenCrownProj.cs:202 — Content/Items/Accessories/BrutalRelics/KingSlime/FallenCrownProj.cs:202-223 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSCrownProj.cs:406-437 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:1153 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:1153-1176 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1631-1652 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) Content/Wraiths/Abilities/GhostRains/GhostRainFx.cs:215 — Content/Wraiths/Abilities/GhostRains/GhostRainFx.cs:215-250 | Content/Wraiths/Deaths/Performances/RainSeizurePerformance.cs:392-413 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmPineNeedleProj.cs:57 — Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmPineNeedleProj.cs:57-78 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmStrafeBulletProj.cs:57-79 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Core/BrainMotion.cs:64 — Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Core/BrainMotion.cs:64-86 | Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Core/BrainMotion.cs:153-174 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) Content/Scenarios/OldNet/UI/OldNetCipherPanel.cs:483 — Content/Scenarios/OldNet/UI/OldNetCipherPanel.cs:483-508 | Content/Scenarios/OldNet/UI/OldNetDebriefPanel.cs:488-509 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallProj.cs:827 — Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallProj.cs:827-851 | Content/Scenarios/Shenyo/Dolls/ScapegoatDollWalker.cs:141-162 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaShrimpWaterBolt.cs:98 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaShrimpWaterBolt.cs:98-124 | Content/NPCs/BloomsandSerpents/Projectiles/BssSandGlob.cs:62-83 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) Content/Wraiths/Abilities/CrimsonBrides/BrideHallRenderer.cs:319 — Content/Wraiths/Abilities/CrimsonBrides/BrideHallRenderer.cs:319-344 | Content/Wraiths/Deaths/Performances/BrideSeizurePerformance.cs:245-266 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) Content/Items/Ranged/Thornstrings/ThornstringHeld.cs:313 — Content/Items/Ranged/Thornstrings/ThornstringHeld.cs:313-334 | Content/Items/Ranged/Undertows/UndertowHeld.cs:317-338 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) Content/Items/Magic/WheezingWyrms/WyrmFlame.cs:93 — Content/Items/Magic/WheezingWyrms/WyrmFlame.cs:93-121 | Content/Items/Ranged/SneezingWyrms/WyrmstrikeRound.cs:63-84 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishBunny.cs:505 — Content/LegendWeapon/HalibutLegend/FishSkills/FishBunny.cs:505-538 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCat.cs:412-433 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) Content/NPCs/BrutalNPCs/BrutalSkeletron/States/Hands/SkeletronHandStates.cs:372 — Content/NPCs/BrutalNPCs/BrutalSkeletron/States/Hands/SkeletronHandStates.cs:372-393 | Content/NPCs/BrutalNPCs/BrutalSkeletron/States/SkeletronPalmSnatchState.cs:364-389 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:177 — Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:177-198 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsScourgeoftheCorruptor.cs:159-180 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:665 — Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:665-691 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaReset.cs:652-673 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocMawDragState.cs:570 — Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocMawDragState.cs:570-598 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocMawFrenzyState.cs:188-209 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolBossRoomWatcher.cs:228 — Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolBossRoomWatcher.cs:228-252 | Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolBossRoomWatcher.cs:255-276 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) Content/NPCs/TBUGs/TBUGRiftSpawner.cs:50 — Content/NPCs/TBUGs/TBUGRiftSpawner.cs:50-71 | Content/NPCs/Victors/VictorPortalSpawner.cs:51-72 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:773 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:773-794 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:939-960 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • + 10 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (empty catch) · ×34
  • Swallowed exception (empty catch) Content/Cyberwares/CyberwareNet.cs:233 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) Content/Cyberwares/CyberwareNet.cs:234 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) Content/Cyberwares/Implementation/SelfHackCrystals/SelfHackCrystalNet.cs:82 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) Content/Cyberwares/Implementation/SelfHackCrystals/SelfHackCrystalNet.cs:83 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) Content/HackTimes/HackTimeNetSync.cs:455 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) Content/HackTimes/HackTimeNetSync.cs:456 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) Content/Items/Accessories/BrutalRelics/Skeletron/SoulbindingArmNet.cs:100 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) Content/Items/Accessories/BrutalRelics/Skeletron/SoulbindingArmNet.cs:101 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainNet.cs:59 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainNet.cs:86 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaLakeHighlight.cs:226 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaLakeHighlight.cs:243 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaLakeHighlight.cs:251 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaLakeHighlight.cs:260 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) Content/LegendWeapon/OnikiriLegend/OniBladeProfile.cs:156 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) Content/LegendWeapon/OnikiriLegend/OniDismembers/OniDismemberRender.cs:148 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) Content/LegendWeapon/OnikiriLegend/OniDismembers/OniDismemberRender.cs:157 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) Content/LegendWeapon/OnikiriLegend/OniDismembers/OniPlayerDismember.cs:483 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) Content/LegendWeapon/OnikiriLegend/OniDismembers/OniPlayerDismember.cs:490 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) Content/LegendWeapon/OnikiriLegend/OniDismembers/OniSeverReplicationSystem.cs:191 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) Content/LegendWeapon/OnikiriLegend/OniDismembers/OniSeverReplicationSystem.cs:192 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) Content/LegendWeapon/OnikiriLegend/OniDismembers/OniSeverStrike.cs:369 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) Content/LegendWeapon/OnikiriLegend/OniDismembers/OniSeverStrike.cs:370 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainNet.cs:72 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraSlashProj.cs:197 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • + 9 more in this group — see findings.md.
AX2 · Stateful singletons · Stateful shared instance · ×33
  • Stateful shared instance: ExternalQuestNode Content/QuestLogs/Core/ExternalQuestNode.cs:13 — `ExternalQuestNode` is not registered, but `QuestLogsAPI` creates it and keeps it in the static `QuestNode._quests`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_title, _summary, _detail, _objective, _completeBool, _completeFloat; e.g. `_title` at line 56).
  • Stateful shared instance: HackUploadOverlay Content/HackTimes/HackUploadOverlay.cs:8 — `HackUploadOverlay` is not registered, but `HackTimeRender` creates it and keeps it in the static `UploadOverlay`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (pulseTimer; e.g. `pulseTimer` at line 14).
  • Stateful shared instance: OreDropRule Content/Industrials/ElectricPowers/MiningMachines/MiningMachineSystem.cs:270 — `OreDropRule` is not registered, but `MiningMachineSystem` creates it and keeps it in the static `DropRules`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (Relevance, Progress, WorldState, NeedDedicatedDrill, IsRareByproduct, VeinWeightPerTile; e.g. `Relevance` at line 300).
  • Stateful shared instance: LegendUpgradeDecision Content/LegendWeapon/LegendUpgradeDecision.cs:12 — `LegendUpgradeDecision` keeps one instance of itself in the static `Instance`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (cachedName, cachedLevel, cachedItemType; e.g. `cachedName` at line 27).
  • Stateful shared instance: RestartFishBoid Content/LegendWeapon/HalibutLegend/DomainSkills/RestartFish.cs:97 — `RestartFishBoid` is not registered, but `HalibutReset` creates it and keeps it in the static `garnishFish`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (Life, LifeProgress, spiralAngle, Velocity, Position, Frame; e.g. `Life` at line 136).
  • Stateful shared instance: Track Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetHistory.cs:36 — `Track` is not registered, but `KikasaResetHistory` creates it and keeps it in the static `npcTracks`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (Head, Count; e.g. `Head` at line 43).
  • Stateful shared instance: OniStancePreviewSource Content/LegendWeapon/OnikiriLegend/UI/OniStanceData.cs:59 — `OniStancePreviewSource` is not registered, but `OniStance` creates it and keeps it in the static `preview`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (lastTick, fullHold, value, gainCountdown; e.g. `lastTick` at line 71).
  • Stateful shared instance: OniVigorPreviewSource Content/LegendWeapon/OnikiriLegend/UI/OniVigorData.cs:58 — `OniVigorPreviewSource` is not registered, but `OniVigor` creates it and keeps it in the static `preview`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (lastTick, value, spendCountdown; e.g. `lastTick` at line 69).
  • Stateful shared instance: SHPCModuleSection Content/LegendWeapon/SHPCLegend/UI/SHPCItemTooltipPanel.cs:113 — `SHPCModuleSection` is not registered, but `SHPCItemTooltipPanel` creates it and keeps it in the static `moduleSection`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (modules, bonus; e.g. `modules` at line 128).
  • Stateful shared instance: BssPortraitActor Content/NPCs/BloomsandSerpents/BssPortrait.cs:15 — `BssPortraitActor` keeps one instance of itself in the static `instance`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (petalTimer, flowerTimer, dustTimer; e.g. `petalTimer` at line 60).
  • Stateful shared instance: FssPortraitActor Content/NPCs/FestersandSerpents/Rendering/FssPortrait.cs:17 — `FssPortraitActor` keeps one instance of itself in the static `instance`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (dripTimer, dustTimer; e.g. `dripTimer` at line 64).
  • Stateful shared instance: CrabulonLife Content/NPCs/Modifys/Crabulons/CrabulonUIs/CrabulonMountLifeBar.cs:126 — `CrabulonLife` is not registered, but `CrabulonMountLifeBar` creates it and keeps it in the static `crabulonLives`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (waveShakeOffset, shakeTime, damageShakeOffset, dynamicRotation, lifeValue, dynamicScale; e.g. `waveShakeOffset` at line 151).
  • Stateful shared instance: SeaShrimpPortraitActor Content/NPCs/SeaShrimp/Rendering/SeaShrimpPortrait.cs:15 — `SeaShrimpPortraitActor` keeps one instance of itself in the static `instance`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (ctx, headPos, heading; e.g. `ctx` at line 31).
  • Stateful shared instance: QuestWorldDecision Content/QuestLogs/QuestWorldDecision.cs:11 — `QuestWorldDecision` keeps one instance of itself in the static `current`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (answered; e.g. `answered` at line 55).
  • Stateful shared instance: GlyphLayout Content/Rarities/RarityNameEffects.cs:64 — `GlyphLayout` is not registered, but `RarityNameEffects` creates it and keeps it in the static `sharedLayout`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (Glyphs, Positions, Widths; e.g. `Glyphs` at line 82).
  • Stateful shared instance: TechParticle Content/Scenarios/Draedon/ExoMechdusaSums/ExoMechdusaSumRender.cs:570 — `TechParticle` is not registered, but `ExoMechdusaSumRender` creates it and keeps it in the static `techParticles`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (Life, Position, Velocity, Rotation; e.g. `Life` at line 593).
  • Stateful shared instance: MatrixRain Content/Scenarios/Draedon/Quest/DeploySignaltowers/DeploySignaltowerRender.cs:399 — `MatrixRain` is not registered, but `DeploySignaltowerRender` creates it and keeps it in the static `matrixRains`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (Y, UpdateTimer, Characters; e.g. `Y` at line 425).
  • Stateful shared instance: HexDataBlock Content/Scenarios/Draedon/Quest/DeploySignaltowers/DeploySignaltowerRender.cs:490 — `HexDataBlock` is not registered, but `DeploySignaltowerRender` creates it and keeps it in the static `hexBlocks`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (Life; e.g. `Life` at line 514).
  • Stateful shared instance: TechParticle Content/Scenarios/Draedon/Quest/DeploySignaltowers/DeploySignaltowerRender.cs:750 — `TechParticle` is not registered, but `DeploySignaltowerRender` creates it and keeps it in the static `techParticles`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (Life, Position, Velocity, Rotation; e.g. `Life` at line 773).
  • Stateful shared instance: DataStream Content/Scenarios/Draedon/Quest/DeploySignaltowers/DeploySignaltowerRender.cs:847 — `DataStream` is not registered, but `DeploySignaltowerRender` creates it and keeps it in the static `dataStreams`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (Life, Position; e.g. `Life` at line 868).
  • Stateful shared instance: OldNetNodeBudget Content/Scenarios/OldNet/Gen/OldNetBuildContext.cs:51 — `OldNetNodeBudget` is not registered, but `OldNetPlans` creates it and keeps it in the static `Budget`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (UnderPlainPlaced; e.g. `UnderPlainPlaced` at line 81).
  • Stateful shared instance: EnchantmentHandler Content/Scenarios/SupCal/End/EternalBlazingNow/Enchants/EnchantmentHandler.cs:11 — `EnchantmentHandler` is not registered, but `EnchantUI` creates it and keeps it in the static `EnchantmentHandler`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (EnchantProgress, SelectedEnchantment, SelectedEnchantmentIndex, IsEnchanting, CurrentItem; e.g. `EnchantProgress` at line 43).
  • Stateful shared instance: CyberBossHPUI Content/UIs/BossBars/CyberBossBarStyle.cs:83 — `CyberBossHPUI` is not registered, but `CyberBossBarStyle` creates it and keeps it in the static `Bars`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (CloseTimer, OpenTimer, InitMaxLife, HitFlash, PrevLife, SmoothRatio; e.g. `CloseTimer` at line 134).
  • Stateful shared instance: PortraitMotes OtherMods/BossChecklist/PortraitMotes.cs:11 — `PortraitMotes` is not registered, but the singleton `BssPortraitActor` creates it and keeps it in `motes`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (motes; e.g. `motes` at line 32).
  • Stateful shared instance: SerpentPortraitRig OtherMods/BossChecklist/SerpentPortraitRig.cs:19 — `SerpentPortraitRig` is not registered, but the singleton `BssPortraitActor` creates it and keeps it in `rig`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (headPos, prevHeadPos, heading, displayHeading, snapHeading, gait; e.g. `headPos` at line 163).
  • + 8 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (8 lines × 4) · ×33
  • Duplicated block (8 lines × 4) Content/GameModes/BrutalMobs/NightPack/Projectiles/NightDiveOmen.cs:154 — Content/GameModes/BrutalMobs/NightPack/Projectiles/NightDiveOmen.cs:154-161 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkChargeOmen.cs:166-173 | Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornDiveLane.cs:137-144 | Content/GameModes/BrutalMobs/Temple/Projectiles/TempleDiveOmen.cs:150-157 — before extracting anything, compare `Content/GameModes/BrutalMobs/NightPack/Projectiles/NightDiveOmen.cs` and `Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkChargeOmen.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/NightPack/Projectiles/NightDiveOmen.cs:154` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:58 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:58-65 | Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs:63-70 | Content/Renders/WarpEffectRender.cs:76-83 | Content/Scenarios/Kiame/Overlay/OniRainWorldRender.cs:54-61 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs` and `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 192 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 4) Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:476 — Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:476-483 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:510-517 | Content/Industrials/ElectricPowers/Recyclers/RecyclerUI.cs:437-444 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterUI.cs:474-481 — before extracting anything, compare `Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs` and `Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 303 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:476` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 4) Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT1.cs:152 — Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT1.cs:152-159 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT3.cs:80-87 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsSolarEruption.cs:116-123 | Content/GameModes/GodSmith/Weapons/Spears/GsJoustingLances.cs:129-136 — before extracting anything, compare `Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT1.cs` and `Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT3.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 89 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT1.cs:152` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 4) Content/Items/Magic/BloomTomes/BloomTome.cs:25 — Content/Items/Magic/BloomTomes/BloomTome.cs:25-32 | Content/Items/Magic/Everdeeps/Everdeep.cs:21-28 | Content/Items/Magic/Eyetooths/Eyetooth.cs:28-35 | Content/Items/Magic/WheezingWyrms/WheezingWyrm.cs:19-26 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/BloomTomes/BloomTome.cs:25` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 4) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:37 — Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:37-44 | Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:37-44 | Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs:39-46 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs:56-63 — before extracting anything, compare `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs` and `Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:701 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:701-708 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:742-749 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:427-434 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:529-536 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs` as WHOLE FILES: this scan already matched 66 separate duplicated blocks between them, totalling at least 737 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:384 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:384-391 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:547-554 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:386-393 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:435-442 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs` as WHOLE FILES: this scan already matched 48 separate duplicated blocks between them, totalling at least 508 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:384` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 4) Content/Industrials/ElectricPowers/Apiaries/ApiaryStorageProvider.cs:143 — Content/Industrials/ElectricPowers/Apiaries/ApiaryStorageProvider.cs:143-150 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherStorageProvider.cs:142-149 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerStorageProvider.cs:142-149 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconStorageProvider.cs:145-152 — before extracting anything, compare `Content/Industrials/ElectricPowers/Apiaries/ApiaryStorageProvider.cs` and `Content/Industrials/ElectricPowers/AutoFishers/AutoFisherStorageProvider.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Apiaries/ApiaryStorageProvider.cs:143` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 4) Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:846 — Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:846-853 | Content/Items/Melee/NeutronGlaive.cs:550-557 | Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:681-688 | Content/Items/Modifys/RBloodButcherer.cs:669-676 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (8 lines × 4) Content/Items/Melee/SpearOfLonginuses/LonginusAssets.cs:222 — Content/Items/Melee/SpearOfLonginuses/LonginusAssets.cs:222-229 | Content/Items/Melee/SpearOfLonginuses/LonginusAssets.cs:267-274 | Content/Items/Melee/SpearOfLonginuses/LonginusAssets.cs:306-313 | Content/Items/Melee/SpearOfLonginuses/LonginusAssets.cs:377-384 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Melee/SpearOfLonginuses/LonginusAssets.cs:387` calls `SetValue` and `Content/Items/Melee/SpearOfLonginuses/LonginusAssets.cs:277` 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 × 4) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1008 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1008-1015 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaMinionDrownFX.cs:446-453 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaPlayerDrownFX.cs:484-491 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaScourgeFX.cs:745-752 — 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 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1008` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:646 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:646-653 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:652-659 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:608-615 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:641-648 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs` as WHOLE FILES: this scan already matched 75 separate duplicated blocks between them, totalling at least 912 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:646` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:719 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:719-726 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:735-742 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:681-688 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:713-720 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs` as WHOLE FILES: this scan already matched 75 separate duplicated blocks between them, totalling at least 912 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:719` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:718` calls `Min` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:712` does not — after which the two agree again for 4 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 × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:868 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:868-875 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1044-1051 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:666-673 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:990-997 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs` as WHOLE FILES: this scan already matched 66 separate duplicated blocks between them, totalling at least 737 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:868` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 4) Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberExecutionBoltProj.cs:391 — Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberExecutionBoltProj.cs:391-398 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDataArcProj.cs:113-120 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberGlitchBoltProj.cs:134-141 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberRiftSlashProj.cs:137-144 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 4) Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs:87 — Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs:87-94 | Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteDiveOmen.cs:76-85 | Content/GameModes/BrutalMobs/Sky/Projectiles/SkyGaleDiveOmen.cs:89-98 | Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornDiveLane.cs:85-94 — before extracting anything, compare `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs` and `Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteDiveOmen.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs:87` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs:95` calls `PlaySound` and `Content/GameModes/BrutalMobs/Sky/Projectiles/SkyGaleDiveOmen.cs:99` 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 × 4) Content/GameModes/GodSmith/Armors/Reset/GsJungleArmor.cs:76 — Content/GameModes/GodSmith/Armors/Reset/GsJungleArmor.cs:76-83 | Content/GameModes/GodSmith/Armors/Reset/GsPillarArmors.cs:239-246 | Content/GameModes/GodSmith/Armors/Reset/GsSpectreArmors.cs:113-120 | Content/GameModes/GodSmith/Armors/Reset/GsTikiArmor.cs:78-85 — 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 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Armors/Reset/GsJungleArmor.cs:76` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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) Content/GameModes/GodSmith/Weapons/Bows/DaedalusStormbowScheme.cs:190 — Content/GameModes/GodSmith/Weapons/Bows/DaedalusStormbowScheme.cs:190-198 | Content/GameModes/GodSmith/Weapons/Bows/RepeaterSchemes.cs:374-381 | Content/GameModes/GodSmith/Weapons/MagicCataclysm/GsNebulaArcanum.cs:29-37 | Content/GameModes/GodSmith/Weapons/MagicCataclysm/GsNebulaBlaze.cs:32-40 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/Bows/DaedalusStormbowScheme.cs:190` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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) Content/Items/Accessories/BrutalRelics/Twins/TwinPupilTetherBeam.cs:213 — Content/Items/Accessories/BrutalRelics/Twins/TwinPupilTetherBeam.cs:213-220 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs:194-202 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeHeatRay.cs:180-187 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeSkullBeamProj.cs:191-198 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs` and `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeHeatRay.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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) Content/Items/Melee/DivineSourceBlades/DivineSourceHitFXProjectile.cs:188 — Content/Items/Melee/DivineSourceBlades/DivineSourceHitFXProjectile.cs:188-197 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:942-949 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:1285-1293 | Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:1393-1400 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (8 lines × 4) Content/Items/Melee/Shatterfangs/ShatterfangPRT.cs:50 — Content/Items/Melee/Shatterfangs/ShatterfangPRT.cs:50-57 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBoneParticles.cs:57-65 | Content/LegendWeapon/HalibutLegend/FishSkills/FishRockParticles.cs:142-150 | Content/PRTTypes/PRT_GraniteShard.cs:53-61 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Shatterfangs/ShatterfangPRT.cs:50` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1249 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1249-1256 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1603-1610 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:1030-1037 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1637-1644 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs` as WHOLE FILES: this scan already matched 68 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1249` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:400 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:400-407 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:391-399 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:364-371 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:407-415 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 598 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:400` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:408` calls `PlaySound` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:399` does not — after which the two agree again for 3 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 × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:134 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:134-142 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:168-176 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:138-145 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:185-193 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs` as WHOLE FILES: this scan already matched 48 separate duplicated blocks between them, totalling at least 508 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:134` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • + 8 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×32
  • Duplicated block (11 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:737 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:737-747 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:699-709 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:731-741 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs` as WHOLE FILES: this scan already matched 78 separate duplicated blocks between them, totalling at least 968 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:737` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11 lines × 3) Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:229 — Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:229-239 | Content/Scenarios/Kiame/Overlay/OniRainExitTransition.cs:186-196 | Content/Scenarios/Kiame/Overlay/OniRainWorldTransition.cs:287-297 — before extracting anything, compare `Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs` and `Content/Scenarios/Kiame/Overlay/OniRainExitTransition.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 186 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:229` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 3) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistArcaneNovaState.cs:35 — Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistArcaneNovaState.cs:35-45 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistSeekerStarsState.cs:28-38 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistStasisMinesState.cs:33-43 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistArcaneNovaState.cs:35` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistArcaneNovaState.cs:32` calls `PulseCount` and `Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistStasisMinesState.cs:31` 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 × 3) Common/NpcGroupHelper.cs:119 — Common/NpcGroupHelper.cs:119-129 | Common/NpcGroupHelper.cs:185-195 | Common/NpcGroupHelper.cs:263-273 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Common/NpcGroupHelper.cs:119` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsBloodSpike.cs:223 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsBloodSpike.cs:223-233 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:1257-1267 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:1312-1322 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsBloodSpike.cs:223` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 3) Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerRenderHelper.cs:53 — Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerRenderHelper.cs:53-63 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerRenderHelper.cs:114-124 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerRenderHelper.cs:217-227 — 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) Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomSporeMistTelegraph.cs:99 — Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomSporeMistTelegraph.cs:99-109 | Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomVineWhipOmen.cs:75-85 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandConeTelegraph.cs:116-126 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomSporeMistTelegraph.cs:99` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomVineWhipOmen.cs:71` calls `PlaySound` and `Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandConeTelegraph.cs:112` 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 × 3) Content/Items/Magic/Elysiums/ElysiumThunder.cs:32 — Content/Items/Magic/Elysiums/ElysiumThunder.cs:32-42 | Content/Items/Magic/Elysiums/Revelations/RevelationSealJudgment.cs:44-54 | Content/Items/Magic/Elysiums/Serpents/SnakeConversionWave.cs:41-51 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/Elysiums/ElysiumThunder.cs:32` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:795 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:795-805 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:883-893 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:696-706 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:795` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 3) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1348 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1348-1358 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1063-1073 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1255-1265 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1348` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11 lines × 3) Content/QuestLogs/QLNodes/CalamityMaterialQuests.cs:182 — Content/QuestLogs/QLNodes/CalamityMaterialQuests.cs:182-192 | Content/QuestLogs/QLNodes/CalamityMaterialQuests.cs:216-226 | Content/QuestLogs/QLNodes/CalamityMaterialQuests.cs:324-334 — 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) Content/GameModes/BrutalMobs/Ocean/Projectiles/OceanPulseRing.cs:125 — Content/GameModes/BrutalMobs/Ocean/Projectiles/OceanPulseRing.cs:125-135 | Content/GameModes/BrutalMobs/Ocean/Projectiles/OceanSandMound.cs:60-70 | Content/GameModes/BrutalMobs/Ocean/Projectiles/OceanSharkOmen.cs:70-80 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11 lines × 3) Content/GameModes/GodSmith/Weapons/Guns/GsMinishark.cs:279 — Content/GameModes/GodSmith/Weapons/Guns/GsMinishark.cs:279-289 | Content/GameModes/GodSmith/Weapons/Guns/GsPhoenixBlaster.cs:246-256 | Content/GameModes/GodSmith/Weapons/Specials/GsChainGun.cs:217-227 — before extracting anything, compare `Content/GameModes/GodSmith/Weapons/Guns/GsMinishark.cs` and `Content/GameModes/GodSmith/Weapons/Guns/GsPhoenixBlaster.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 74 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/Guns/GsMinishark.cs:279` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 3) Content/HackTimes/HackTimeRender.cs:85 — Content/HackTimes/HackTimeRender.cs:85-97 | Content/HackTimes/HackTimeTileCyberPass.cs:105-116 | Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:54-64 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/HackTimes/HackTimeRender.cs:85` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/HackTimes/HackTimeTileCyberPass.cs:101` calls `EnsureRT` and `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:51` 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 × 3) Content/HackTimes/Protocols/TileConscript.cs:75 — Content/HackTimes/Protocols/TileConscript.cs:75-85 | Content/HackTimes/Protocols/TileDetonate.cs:61-71 | Content/HackTimes/Scannables/TileScannable.cs:256-266 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/HackTimes/Protocols/TileConscript.cs:75` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/HackTimes/Protocols/TileDetonate.cs:56` calls `GetVanillaMinPick` and `Content/HackTimes/Protocols/TileConscript.cs:74` 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 × 3) Content/Industrials/ElectricPowers/FluidInjectors/FluidInjectorTP.cs:341 — Content/Industrials/ElectricPowers/FluidInjectors/FluidInjectorTP.cs:341-351 | Content/Industrials/ElectricPowers/ShieldGenerators/ShieldDomeRender.cs:159-169 | Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:584-594 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/FluidInjectors/FluidInjectorTP.cs:341` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 3) Content/Items/Ranged/Pallbearer.cs:1243 — Content/Items/Ranged/Pallbearer.cs:1243-1253 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBellWave.cs:273-283 | Content/Wraiths/VFX/ScapeArmRenderer.cs:128-138 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Ranged/Pallbearer.cs:1243` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Wraiths/VFX/ScapeArmRenderer.cs:127` calls `DrawFallback` and `Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBellWave.cs:272` does not — after which the two agree again for 4 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 × 3) Content/LegendWeapon/HalibutLegend/DomainSkills/FishTeleport.cs:158 — Content/LegendWeapon/HalibutLegend/DomainSkills/FishTeleport.cs:158-168 | Content/LegendWeapon/HalibutLegend/DomainSkills/RestartFish.cs:192-202 | Content/LegendWeapon/HalibutLegend/DomainSkills/YourLevelIsTooLow.cs:760-770 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/DomainSkills/FishTeleport.cs:158` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:401 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:401-412 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:373-384 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:413-423 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs` as WHOLE FILES: this scan already matched 55 separate duplicated blocks between them, totalling at least 611 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:401` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:425` calls `PlaySound` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:412` does not — after which the two agree again for 3 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 × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:548 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:548-558 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:745-755 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:829-839 — 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. 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 (11 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:50 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:50-60 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs:63-73 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshEyeLaser.cs:53-63 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 161 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (11 lines × 3) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1895 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1895-1905 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1545-1555 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1760-1770 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/TwinsGrabPerformancePlayer.cs:185 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/TwinsGrabPerformancePlayer.cs:185-195 | Content/TimeFreezes/WorldFreezePlayer.cs:111-122 | Content/TimeFreezes/WorldFreezePlayer.cs:195-205 — 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. Note what the matched lines are: every one of them assigns one field to another, so the block is a hand-written mapper between two data shapes rather than behaviour with a helper inside it. Extracting one shared function only works if both sites map the SAME pair of types in the same direction — check that first, because inverse or differently-typed mappers have no single function they can both call. Where they do not, the moves that exist are a generated or reflective mapper, a common embedded/base type the fields live on once, or accepting the run and covering it with a test that fails when a field is added to one side only.
  • Duplicated block (11 lines × 3) Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolRoomSealTile.cs:27 — Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolRoomSealTile.cs:27-37 | Content/Scenarios/OldNet/Tiles/OldNetBulkheadTile.cs:20-30 | Content/Scenarios/OldNet/Tiles/OldNetSealGateTile.cs:20-30 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolRoomSealTile.cs:39` calls `CanExplode`, `CanKillTile` and `Content/Scenarios/OldNet/Tiles/OldNetBulkheadTile.cs:32` does not — after which the two agree again for 3 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 × 3) Content/Scenarios/OldNet/NPCs/OldNetBlackICE.cs:84 — Content/Scenarios/OldNet/NPCs/OldNetBlackICE.cs:84-94 | Content/Scenarios/OldNet/NPCs/OldNetTaggerICE.cs:83-93 | Content/Scenarios/OldNet/NPCs/OldNetTracerICE.cs:82-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 3 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Scenarios/OldNet/NPCs/OldNetTaggerICE.cs:80` calls `Max`, `TickGhostTrail` and `Content/Scenarios/OldNet/NPCs/OldNetBlackICE.cs:82` does not — after which the two agree again for 3 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.
  • + 7 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (7 lines × 4) · ×32
  • Duplicated block (7 lines × 4) Content/Items/Melee/Heartcarver.cs:1181 — Content/Items/Melee/Heartcarver.cs:1181-1187 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDemonicHell.cs:325-331 | Content/LegendWeapon/HalibutLegend/FishSkills/FishHarpy.cs:165-171 | Content/LegendWeapon/SHPCLegend/Modules/Grip/CrystalGripModule.cs:68-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (7 lines × 4) Content/Items/Summon/AzureDragonRage.cs:137 — Content/Items/Summon/AzureDragonRage.cs:137-143 | Content/Items/Summon/BleedingScourge.cs:120-126 | Content/Items/Summon/ElementWhip.cs:152-158 | Content/Items/Summon/GhostFireWhip.cs:145-151 — before extracting anything, compare `Content/Items/Summon/AzureDragonRage.cs` and `Content/Items/Summon/BleedingScourge.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 93 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Summon/ElementWhip.cs:159` calls `EntitySpriteDraw` and `Content/Items/Summon/AzureDragonRage.cs:144` does not — after which the two agree again for 4 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 × 4) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:630 — Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:630-636 | Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:505-511 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:539-545 | Content/Industrials/ElectricPowers/Recyclers/RecyclerUI.cs:466-472 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:630` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:1071 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:1071-1077 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:1220-1226 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1542-1548 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:1080-1086 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:1071` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:837 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:837-843 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:828-834 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1048-1054 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:927-933 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:837` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsBloodSpike.cs:169 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsBloodSpike.cs:169-175 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:1462-1468 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:390-396 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonVesselWhip.cs:260-266 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsBloodSpike.cs:169` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonVesselWhip.cs:258` calls `CanCutTiles` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:388` 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 × 4) Content/Scenarios/Dungeonworld/Gen/BossRooms/ProofingHallRoom.cs:348 — Content/Scenarios/Dungeonworld/Gen/BossRooms/ProofingHallRoom.cs:348-354 | Content/Scenarios/Dungeonworld/Gen/Layers/L1/L1Style.cs:198-204 | Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Palette.cs:119-125 | Content/Scenarios/Dungeonworld/Gen/Layers/L7/L7Style.cs:328-334 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/Gen/BossRooms/ProofingHallRoom.cs:348` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs:202 — Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs:202-208 | Content/Scenarios/Kiame/KiameWakeResetRender.cs:197-203 | Content/Scenarios/Kiame/Overlay/OniRainDescentRender.cs:160-166 | Content/Scenarios/Kiame/Overlay/OniRainWorldRender.cs:222-228 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs` and `Content/Scenarios/Kiame/KiameWakeResetRender.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 168 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Scenarios/Kiame/KiameWakeResetRender.cs:205` calls `Draw`, `Color` and `Content/Scenarios/Kiame/Overlay/OniRainDescentRender.cs:167` 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 × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:672 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:672-678 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1194-1200 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:622-628 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:539-545 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs` as WHOLE FILES: this scan already matched 68 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:672` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 4) Content/NPCs/BloomsandSerpents/States/BssBurrowLungeState.cs:301 — Content/NPCs/BloomsandSerpents/States/BssBurrowLungeState.cs:301-307 | Content/NPCs/BloomsandSerpents/States/BssFinHuntState.cs:308-314 | Content/NPCs/BloomsandSerpents/States/BssQuicksandState.cs:292-298 | Content/NPCs/BloomsandSerpents/States/BssSandSurgeState.cs:235-241 — 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 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BloomsandSerpents/States/BssBurrowLungeState.cs:301` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 4) Content/EntrustManager/EntrustTrackerWidget.cs:388 — Content/EntrustManager/EntrustTrackerWidget.cs:388-394 | Content/EntrustManager/Styles/DraedonManagerStyle.cs:266-272 | Content/EntrustManager/Styles/ForestManagerStyle.cs:271-277 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:260-266 — before extracting anything, compare `Content/EntrustManager/Styles/DraedonManagerStyle.cs` and `Content/EntrustManager/Styles/ForestManagerStyle.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 334 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 (7 lines × 4) Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs:88 — Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs:88-94 | Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteDiveOmen.cs:78-85 | Content/GameModes/BrutalMobs/Sky/Projectiles/SkyFeatherFanOmen.cs:103-109 | Content/GameModes/BrutalMobs/Sky/Projectiles/SkyGaleDiveOmen.cs:91-98 — before extracting anything, compare `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs` and `Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteDiveOmen.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs:88` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs:95` calls `PlaySound` and `Content/GameModes/BrutalMobs/Sky/Projectiles/SkyGaleDiveOmen.cs:99` 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 × 4) Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:157 — Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:157-163 | Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgStabGlintOmen.cs:145-151 | Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyGhostNameThread.cs:174-180 | Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyRavenSwoopOmen.cs:159-165 — before extracting anything, compare `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs` and `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgStabGlintOmen.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 89 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:157` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (7 lines × 4) Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhScytheBolt.cs:86 — Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhScytheBolt.cs:86-92 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhStingerBolt.cs:86-93 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhTridentBolt.cs:85-91 | Content/GameModes/BrutalMobs/Sky/Projectiles/SkyFeatherBolt.cs:79-86 — before extracting anything, compare `Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhScytheBolt.cs` and `Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhStingerBolt.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 67 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhScytheBolt.cs:86` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (7 lines × 4) Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhShellSpike.cs:38 — Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhShellSpike.cs:38-44 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhStingerBolt.cs:42-48 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhTridentBolt.cs:41-47 | Content/GameModes/BrutalMobs/Sky/Projectiles/SkyFeatherBolt.cs:42-48 — before extracting anything, compare `Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhShellSpike.cs` and `Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhStingerBolt.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 77 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhShellSpike.cs:38` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/BrutalMobs/Sky/Projectiles/SkyFeatherBolt.cs:40` calls `CanDamage` and `Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhShellSpike.cs:36` does not — after which the two agree again for 4 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 × 4) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:413 — Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:413-419 | Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:398-404 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:427-433 | Content/Industrials/ElectricPowers/Recyclers/RecyclerUI.cs:404-410 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:413` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (7 lines × 4) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:55 — Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:55-64 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs:76-82 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainRender.cs:205-211 | Content/Scenarios/Kiame/KiameWakeResetRender.cs:74-80 — before extracting anything, compare `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs` and `Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:55` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:757 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:757-765 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:598-607 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:482-488 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:931-940 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 408 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:757` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 4) Content/LegendWeapon/KikasaLegend/TrialQuests/KikasaTrackerWidgetStyle.cs:97 — Content/LegendWeapon/KikasaLegend/TrialQuests/KikasaTrackerWidgetStyle.cs:97-104 | Content/LegendWeapon/OnikiriLegend/TrialQuests/OnikiriTrackerWidgetStyle.cs:85-91 | Content/LegendWeapon/SHPCLegend/TrialQuests/SHPCTrackerWidgetStyle.cs:114-121 | Content/Scenarios/Draedon/Quest/DraedonTrackerWidgetStyle.cs:145-152 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/TrialQuests/KikasaTrackerWidgetStyle.cs` and `Content/LegendWeapon/OnikiriLegend/TrialQuests/OnikiriTrackerWidgetStyle.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/TrialQuests/KikasaTrackerWidgetStyle.cs:97` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (7 lines × 4) Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerStrikeTelegraph.cs:105 — Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerStrikeTelegraph.cs:105-111 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerMotionFX.cs:115-122 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronTelegraph.cs:119-125 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Projectiles/QueenBeeTelegraphLine.cs:100-106 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerStrikeTelegraph.cs` and `Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronTelegraph.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 70 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerStrikeTelegraph.cs:105` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (7 lines × 4) Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerMotionFX.cs:252 — Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerMotionFX.cs:252-258 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Rendering/FishronMotionFX.cs:147-153 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Rendering/EowMotionFX.cs:34-40 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordScreenFX.cs:67-73 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerMotionFX.cs:252` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 4) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistArcaneNovaState.cs:42 — Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistArcaneNovaState.cs:42-48 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistRingPrisonState.cs:33-39 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistSeekerStarsState.cs:35-41 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistStasisMinesState.cs:40-46 — 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 4 call sites, so a change lands once.
  • Duplicated block (7 lines × 4) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsCombinedAttackState.cs:222 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsCombinedAttackState.cs:222-228 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsCrossDashState.cs:163-169 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsPincerGrabState.cs:366-372 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismDashingState.cs:54-60 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsCombinedAttackState.cs:222` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (7 lines × 4) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/PrimeBarrageCommandState.cs:20 — Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/PrimeBarrageCommandState.cs:20-26 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/PrimeIonOverloadState.cs:23-29 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/PrimeRocketCurtainState.cs:24-30 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/PrimeSkullCannonState.cs:31-37 — 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 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/PrimeBarrageCommandState.cs:20` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 4) Content/Narrative/MusicToast.cs:357 — Content/Narrative/MusicToast.cs:357-363 | Content/Narrative/Presentation/Skins/StarStream/StarStreamPanelDraw.cs:114-120 | Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersUIs/OceanRaidersRenderer.cs:139-145 | Content/Scenarios/SupCal/End/EternalBlazingNow/Enchants/EnchantUI.cs:407-413 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Scenarios/SupCal/End/EternalBlazingNow/Enchants/EnchantUI.cs:415` calls `Sin` and `Content/Narrative/Presentation/Skins/StarStream/StarStreamPanelDraw.cs:122` 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.
  • + 7 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (10 lines × 4) · ×31
  • Duplicated block (10 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamGroundField.cs:108 — Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamGroundField.cs:108-117 | Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSim.cs:118-127 | Content/Scenarios/Kiyume/Fog/KiyumeFogSim.cs:188-197 | Content/Scenarios/Kiyume/Fog/KiyumeGroundField.cs:123-132 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamGroundField.cs` and `Content/Scenarios/Kiyume/Fog/KiyumeGroundField.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamGroundField.cs:108` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 4) Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsDeadlySphereSawProj.cs:45 — Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsDeadlySphereSawProj.cs:45-54 | Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsImpPyreProj.cs:37-46 | Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsStardustDragonRiftProj.cs:51-60 | Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsTempestSurgeProj.cs:52-61 — 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 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsDeadlySphereSawProj.cs:45` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 4) Content/Items/Modifys/RBloodButcherer.cs:990 — Content/Items/Modifys/RBloodButcherer.cs:990-999 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunBullet.cs:233-242 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressRibbon.cs:284-293 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:216-225 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Modifys/RBloodButcherer.cs:990` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 4) Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.Net.cs:580 — Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.Net.cs:580-589 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.Net.cs:621-630 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.cs:352-361 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.cs:435-444 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart. Note first that the copies are not typed on the same thing: the declarations holding them bind `target` to `NPCFreezeTarget` in one and `ProjectileFreezeTarget` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (10 lines × 4) Content/GameModes/GodSmith/Prefixes/Ranged/GodSmithBallisticEndow.cs:84 — Content/GameModes/GodSmith/Prefixes/Ranged/GodSmithBallisticEndow.cs:84-93 | Content/LegendWeapon/HalibutLegend/FishSkills/FishAmanita.cs:345-354 | Content/LegendWeapon/HalibutLegend/FishSkills/FishJewel.cs:209-218 | Content/LegendWeapon/HalibutLegend/FishSkills/FishJewel.cs:382-391 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Prefixes/Ranged/GodSmithBallisticEndow.cs:84` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/HalibutLegend/FishSkills/FishJewel.cs:394` calls `NextFloat`, `NextBool`, `ToDirectionInt` and `Content/LegendWeapon/HalibutLegend/FishSkills/FishAmanita.cs:356` 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 (10 lines × 4) Content/Industrials/Generator/Biomass/BiomassGenerator.cs:122 — Content/Industrials/Generator/Biomass/BiomassGenerator.cs:122-131 | Content/Industrials/Generator/Thermal/ThermalGenerator.cs:89-98 | Content/Industrials/Generator/Thermal/ThermalGeneratorMK2.cs:89-98 | Content/Scenarios/Draedon/Quest/DeploySignaltowers/CQETConstructor.cs:102-111 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/Generator/Biomass/BiomassGenerator.cs:122` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 4) Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:318 — Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:318-327 | Content/Items/Ranged/Undertows/UndertowSpine.cs:177-186 | Content/Items/Summon/Deepclaws/DeepclawLobster.cs:471-480 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpWaterBolt.cs:107-116 — before extracting anything, compare `Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs` and `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpWaterBolt.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 116 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:521 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:521-530 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:514-523 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:476-485 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:497-506 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 467 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:521` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:1291 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:1291-1300 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:1306-1315 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Rendering/QueenSlimeRenderHelper.cs:22-31 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Rendering/QueenSlimeRenderHelper.cs:37-46 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:1291` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 4) Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerMotionFX.cs:238 — Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerMotionFX.cs:238-247 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Rendering/FishronMotionFX.cs:132-141 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Rendering/EowMotionFX.cs:59-68 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Rendering/WofMotionFX.cs:31-40 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 4) Content/Scenarios/Himayo/ToriiShrines/ToriiDusk.cs:188 — Content/Scenarios/Himayo/ToriiShrines/ToriiDusk.cs:188-197 | Content/Scenarios/Shepel/CybCourses/CybCourseSky.cs:57-66 | Content/Wraiths/Abilities/CrimsonBrides/BrideHallSky.cs:152-161 | Content/Wraiths/Abilities/GhostRains/GhostRainAmbience.cs:152-161 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Himayo/ToriiShrines/ToriiDusk.cs:188` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 4) Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:92 — Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:92-101 | Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyRavenSwoopOmen.cs:102-111 | Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserMarkLine.cs:149-158 | Content/GameModes/BrutalMobs/NightPack/Projectiles/NightDiveOmen.cs:104-113 — before extracting anything, compare `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs` and `Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyRavenSwoopOmen.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 120 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:92` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 4) Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs:324 — Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs:324-335 | Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs:395-406 | Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs:467-476 | Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs:678-687 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs:324` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 4) Content/Items/Melee/DestroyersBlade.cs:334 — Content/Items/Melee/DestroyersBlade.cs:334-343 | Content/Items/Melee/DragonsScaleGreatsword.cs:347-356 | Content/Items/Melee/EnergySword.cs:363-372 | Content/Items/Melee/RebelBlade.cs:384-393 — before extracting anything, compare `Content/Items/Melee/DestroyersBlade.cs` and `Content/Items/Melee/DragonsScaleGreatsword.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 419 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 × 4) Content/Items/Melee/NeutronGlaive.cs:1238 — Content/Items/Melee/NeutronGlaive.cs:1238-1247 | Content/Items/Melee/NeutronGlaive.cs:1302-1311 | Content/Items/Ranged/NeutronBows/EXNeutronExplosionRanged.cs:14-23 | Content/Items/Ranged/NeutronBows/NeutronExplosionRanged.cs:14-23 — before extracting anything, compare `Content/Items/Melee/NeutronGlaive.cs` and `Content/Items/Ranged/NeutronBows/EXNeutronExplosionRanged.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/NeutronGlaive.cs:1238` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 4) Content/LegendWeapon/HalibutLegend/DomainSkills/FishTeleport.cs:143 — Content/LegendWeapon/HalibutLegend/DomainSkills/FishTeleport.cs:143-152 | Content/LegendWeapon/HalibutLegend/DomainSkills/RestartFish.cs:176-186 | Content/LegendWeapon/HalibutLegend/DomainSkills/SeaDomain.cs:930-939 | Content/LegendWeapon/HalibutLegend/DomainSkills/YourLevelIsTooLow.cs:745-754 — 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 4 call sites, so a change lands once. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/HalibutLegend/DomainSkills/FishTeleport.cs:139` calls `GetAlpha` and `Content/LegendWeapon/HalibutLegend/DomainSkills/SeaDomain.cs:926` 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 (10 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunBullet.cs:124 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunBullet.cs:124-133 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsHail.cs:89-99 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:102-112 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenCrystalShard.cs:91-101 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunBullet.cs:124` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (10 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:835 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:835-844 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:589-598 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:544-553 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:436-445 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 491 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:835` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemMagmaBall.cs:71 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemMagmaBall.cs:71-80 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeMortar.cs:68-77 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeStinger.cs:77-86 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsPulseShot.cs:56-65 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 4) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Core/BrainMotion.cs:34 — Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Core/BrainMotion.cs:34-43 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Core/EocMotion.cs:48-57 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Core/TwinsMotion.cs:36-45 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Core/QueenBeeMotion.cs:33-42 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (10 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:701 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:701-710 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:719-728 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:663-672 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:696-705 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs` as WHOLE FILES: this scan already matched 75 separate duplicated blocks between them, totalling at least 912 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:701` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:965 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:965-974 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:1136-1145 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1352-1361 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:963-972 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (10 lines × 4) Content/GameModes/BrutalMobs/EliteMove/Projectiles/EMScatterBoltProj.cs:37 — Content/GameModes/BrutalMobs/EliteMove/Projectiles/EMScatterBoltProj.cs:37-46 | Content/GameModes/BrutalMobs/EvilBiome/Projectiles/VileLanceProj.cs:34-43 | Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserBoltProj.cs:43-52 | Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteMoltenGlob.cs:42-51 — before extracting anything, compare `Content/GameModes/BrutalMobs/EliteMove/Projectiles/EMScatterBoltProj.cs` and `Content/GameModes/BrutalMobs/EvilBiome/Projectiles/VileLanceProj.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 4) Content/GameModes/GodSmith/Armors/Hardmode/GsForbiddenArmor.cs:187 — Content/GameModes/GodSmith/Armors/Hardmode/GsForbiddenArmor.cs:187-196 | Content/GameModes/GodSmith/Armors/Hardmode/GsSpookyWoodArmor.cs:204-213 | Content/GameModes/GodSmith/Armors/PreHardmode/GsPumpkinArmor.cs:163-172 | Content/GameModes/GodSmith/Armors/Reset/GsOreArmorsPreHardmode.cs:369-378 — before extracting anything, compare `Content/GameModes/GodSmith/Armors/Hardmode/GsForbiddenArmor.cs` and `Content/GameModes/GodSmith/Armors/Hardmode/GsSpookyWoodArmor.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 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 × 4) Content/GameModes/GodSmith/Armors/Reset/GsPillarArmors.cs:161 — Content/GameModes/GodSmith/Armors/Reset/GsPillarArmors.cs:161-170 | Content/GameModes/GodSmith/Armors/Reset/GsShroomiteArmor.cs:136-145 | Content/GameModes/GodSmith/Weapons/Bows/BetsyBowScheme.cs:122-131 | Content/GameModes/GodSmith/Weapons/Bows/PhantasmScheme.cs:389-398 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • + 6 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (10–11 lines × 2) · ×31
  • Duplicated block (10–11 lines × 2) Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs:63 — Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs:63-73 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmStrafeBulletProj.cs:46-55 — before extracting anything, compare `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs` and `Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmStrafeBulletProj.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (10–11 lines × 2) Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmPresentShellProj.cs:61 — Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmPresentShellProj.cs:61-71 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtFanShot.cs:64-73 — before extracting anything, compare `Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmPresentShellProj.cs` and `Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtFanShot.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (10–11 lines × 2) Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaRender.cs:267 — Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaRender.cs:267-277 | Content/NPCs/BrutalNPCs/BrutalPlantera/Rendering/PlanteraBloomRender.cs:91-100 — before extracting anything, compare `Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaRender.cs` and `Content/NPCs/BrutalNPCs/BrutalPlantera/Rendering/PlanteraBloomRender.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaRender.cs:267` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10–11 lines × 2) Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzBeamProj.cs:282 — Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzBeamProj.cs:282-291 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenPrismBeamProj.cs:295-305 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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 (10–11 lines × 2) Content/Items/Accessories/BrutalRelics/Skeletron/SoulbindingArmRender.cs:121 — Content/Items/Accessories/BrutalRelics/Skeletron/SoulbindingArmRender.cs:121-130 | Content/Items/Accessories/BrutalRelics/Skeletron/SoulbindingArmRender.cs:274-284 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/Skeletron/SoulbindingArmRender.cs:121` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Accessories/BrutalRelics/Skeletron/SoulbindingArmRender.cs:132` calls `AdvanceVisuals` and `Content/Items/Accessories/BrutalRelics/Skeletron/SoulbindingArmRender.cs:285` does not — after which the two agree again for 3 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 (10–11 lines × 2) Content/Items/Accessories/BrutalRelics/Twins/TwinPupilOrbiter.cs:81 — Content/Items/Accessories/BrutalRelics/Twins/TwinPupilOrbiter.cs:81-91 | Content/Items/Accessories/BrutalRelics/Twins/TwinPupilTetherBeam.cs:48-57 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/Twins/TwinPupilOrbiter.cs:81` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Accessories/BrutalRelics/Twins/TwinPupilOrbiter.cs:77` calls `SendExtraAI`, `WriteVector2`, `ReceiveExtraAI` and `Content/Items/Accessories/BrutalRelics/Twins/TwinPupilTetherBeam.cs:46` does not — after which the two agree again for 3 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 (10–11 lines × 2) Content/Items/BloomArsenal.cs:124 — Content/Items/BloomArsenal.cs:124-133 | Content/NPCs/BloomsandSerpents/Projectiles/BssPetalProj.cs:84-94 — before extracting anything, compare `Content/Items/BloomArsenal.cs` and `Content/NPCs/BloomsandSerpents/Projectiles/BssPetalProj.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/BloomArsenal.cs:124` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10–11 lines × 2) Content/Items/Melee/DivineSourceBlades/DivineSourceHitFXProjectile.cs:145 — Content/Items/Melee/DivineSourceBlades/DivineSourceHitFXProjectile.cs:145-155 | Content/Items/Melee/Shatterfangs/ShatterfangBurstFX.cs:123-132 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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 (10–11 lines × 2) Content/Items/Melee/Heartcarver.cs:1436 — Content/Items/Melee/Heartcarver.cs:1436-1445 | Content/Items/Melee/HeartcarverHeart.cs:210-220 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10–11 lines × 2) Content/Items/Melee/NeutronGlaive.cs:371 — Content/Items/Melee/NeutronGlaive.cs:371-381 | Content/Items/Modifys/RBloodButcherer.cs:422-431 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/NeutronGlaive.cs:371` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10–11 lines × 2) Content/LegendWeapon/HalibutLegend/FishSkills/FishMudVFX.cs:154 — Content/LegendWeapon/HalibutLegend/FishSkills/FishMudVFX.cs:154-163 | Content/PRTTypes/PRT_MarbleChip.cs:31-41 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (10–11 lines × 2) Content/LegendWeapon/HalibutLegend/HalibutSave.cs:393 — Content/LegendWeapon/HalibutLegend/HalibutSave.cs:393-403 | Content/LegendWeapon/HalibutLegend/HalibutSave.cs:417-426 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/HalibutSave.cs:393` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10–11 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaScourgeFX.cs:712 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaScourgeFX.cs:712-721 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaScourgeFX.cs:773-783 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaScourgeFX.cs:712` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10–11 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkFX.cs:563 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkFX.cs:563-573 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkFX.cs:603-612 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkFX.cs:563` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10–11 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkFX.cs:558 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkFX.cs:558-568 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkSplashFX.cs:465-474 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkFX.cs:558` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (10–11 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutDomain.cs:154 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutDomain.cs:154-164 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumCircle.cs:155-164 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutDomain.cs:154` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutDomain.cs:153` calls `IsOwnedByLocalPlayer` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumCircle.cs:154` 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 (10–11 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuJi.cs:100 — Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuJi.cs:100-110 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuPi.cs:94-103 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuJi.cs:100` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10–11 lines × 2) Content/LegendWeapon/KikasaLegend/UI/KikasaHudTooltip.cs:81 — Content/LegendWeapon/KikasaLegend/UI/KikasaHudTooltip.cs:81-91 | Content/LegendWeapon/OnikiriLegend/UI/OniHudTooltipOverlay.cs:81-90 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/UI/KikasaHudTooltip.cs` and `Content/LegendWeapon/OnikiriLegend/UI/OniHudTooltipOverlay.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/UI/KikasaHudTooltip.cs:81` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/OnikiriLegend/UI/OniHudTooltipOverlay.cs:79` calls `FitLinesToHeight`, `Max` and `Content/LegendWeapon/KikasaLegend/UI/KikasaHudTooltip.cs:81` does not — after which the two agree again for 3 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 (10–11 lines × 2) Content/LegendWeapon/OnikiriLegend/UI/OniRegisterRenderer.cs:47 — Content/LegendWeapon/OnikiriLegend/UI/OniRegisterRenderer.cs:47-56 | Content/QuestLogs/Styles/Chronicle/ChroniclePen.cs:76-86 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/UI/OniRegisterRenderer.cs:47` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10–11 lines × 2) Content/NPCs/BloomsandSerpents/BssLegRig.cs:661 — Content/NPCs/BloomsandSerpents/BssLegRig.cs:661-671 | Content/NPCs/FestersandSerpents/FssLegRig.cs:498-507 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BloomsandSerpents/BssLegRig.cs:661` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (10–11 lines × 2) Content/NPCs/BloomsandSerpents/BssLegRig.cs:673 — Content/NPCs/BloomsandSerpents/BssLegRig.cs:673-683 | Content/NPCs/FestersandSerpents/FssLegRig.cs:508-517 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (10–11 lines × 2) Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerMotionFX.cs:75 — Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerMotionFX.cs:75-85 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Rendering/EocRenderHelper.cs:193-202 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerMotionFX.cs:75` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10–11 lines × 2) Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerMotionFX.cs:111 — Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerMotionFX.cs:111-121 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Projectiles/HoneyPuddleZone.cs:131-140 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (10–11 lines × 2) Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemSunBolt.cs:35 — Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemSunBolt.cs:35-44 | Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemSunMortar.cs:36-46 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemSunBolt.cs:35` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (10–11 lines × 2) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistOrbitLanceState.cs:29 — Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistOrbitLanceState.cs:29-39 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistZodiacSealState.cs:42-51 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistOrbitLanceState.cs:29` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • + 6 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (24 corresponding lines) · ×30
  • Edited copy of a member (24 corresponding lines) Content/Industrials/ElectricPowers/MiningMachines/MiningMachineUI.cs:366 — Content/Industrials/ElectricPowers/MiningMachines/MiningMachineUI.cs:366-401 | Content/Industrials/ElectricPowers/Turrets/TurretControlUI.cs:255-278 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishEaterofPlanktonVFX.cs:63 — Content/LegendWeapon/HalibutLegend/FishSkills/FishEaterofPlanktonVFX.cs:63-86 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Rendering/WofMotionFX.cs:43-72 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) Content/Items/Magic/Elysiums/Disciples/ElysiumBuffs.cs:13 — Content/Items/Magic/Elysiums/Disciples/ElysiumBuffs.cs:13-41 | Content/Items/Magic/Elysiums/Disciples/ElysiumBuffs.cs:100-123 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) Content/Scenarios/Dungeonworld/NPCs/GaolDormantSkull.cs:293 — Content/Scenarios/Dungeonworld/NPCs/GaolDormantSkull.cs:293-327 | Content/Scenarios/Dungeonworld/NPCs/UndrownedThrone.cs:394-417 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) Content/NPCs/TBUGs/TBUG.cs:170 — Content/NPCs/TBUGs/TBUG.cs:170-193 | Content/NPCs/Victors/Victor.cs:255-279 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaTalismans/KikasaTalismanGlyph.cs:160 — Content/LegendWeapon/KikasaLegend/KikasaTalismans/KikasaTalismanGlyph.cs:160-183 | Content/LegendWeapon/OnikiriLegend/UI/OniMeiGlyph.cs:401-425 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) Content/Items/Ranged/Thornstrings/ThornstringHeld.cs:285 — Content/Items/Ranged/Thornstrings/ThornstringHeld.cs:285-310 | Content/Items/Ranged/Undertows/UndertowHeld.cs:291-314 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Rendering/WofRenderHelper.cs:66 — Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Rendering/WofRenderHelper.cs:66-95 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Rendering/WofRenderHelper.cs:131-154 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowHuskMine.cs:82 — Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowHuskMine.cs:82-107 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowDeathState.cs:172-195 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerMotionFX.cs:102 — Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerMotionFX.cs:102-129 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Projectiles/HoneyPuddleZone.cs:126-149 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) Content/Items/Summon/Deepclaws/DeepclawLobster.cs:221 — Content/Items/Summon/Deepclaws/DeepclawLobster.cs:221-244 | Content/Items/Summon/EyekiteStaffs/EyekiteMinion.cs:237-260 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:788 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:788-811 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaMinionDrownFX.cs:364-387 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuJi.cs:94 — Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuJi.cs:94-117 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuPi.cs:80-110 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Optic/PrecisionOpticModule.cs:143 — Content/LegendWeapon/SHPCLegend/Modules/Optic/PrecisionOpticModule.cs:143-166 | Content/LegendWeapon/SHPCLegend/Modules/Optic/SniperOpticModule.cs:486-516 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryWatcher.cs:310 — Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryWatcher.cs:310-339 | Content/Scenarios/Dungeonworld/Gen/BossRooms/ProofingHallWatcher.cs:241-264 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) Content/PRTTypes/PRT_BanishGlitch.cs:113 — Content/PRTTypes/PRT_BanishGlitch.cs:113-137 | Content/PRTTypes/PRT_TBUGGlitch.cs:108-131 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) Content/GameModes/GodSmith/Weapons/SummonSentries/Schemes/GsFlameburstTowers.cs:62 — Content/GameModes/GodSmith/Weapons/SummonSentries/Schemes/GsFlameburstTowers.cs:62-88 | Content/GameModes/GodSmith/Weapons/SummonSentries/Schemes/GsFrostHydraStaff.cs:52-75 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) Content/NPCs/BloomsandSerpents/States/BssBurrowLungeState.cs:235 — Content/NPCs/BloomsandSerpents/States/BssBurrowLungeState.cs:235-259 | Content/NPCs/BloomsandSerpents/States/BssCoilRingState.cs:228-251 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspaceDeco.cs:73 — Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspaceDeco.cs:73-96 | Content/Scenarios/OldNet/OldNetDeco.cs:194-218 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Core/EocStateContext.cs:191 — Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Core/EocStateContext.cs:191-223 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Core/CultistStateContext.cs:166-189 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) Content/LegendWeapon/OnikiriLegend/OniDismembers/OniDismemberNPC.cs:64 — Content/LegendWeapon/OnikiriLegend/OniDismembers/OniDismemberNPC.cs:64-92 | Content/LegendWeapon/OnikiriLegend/OniDismembers/OniPlayerDismember.cs:543-566 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:203 — Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:203-226 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleCut.cs:237-270 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:420 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:420-444 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:294-317 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:144 — Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:144-169 | Content/Items/Melee/WeaverGrievanceses/WGManifestationActor.cs:130-153 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs:45 — Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs:45-68 | Content/Items/Melee/WeaverGrievanceses/WGManifestationNet.cs:46-69 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • + 5 more in this group — see findings.md.
D4 · Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) · ×30
  • Edited copies of one member (3 members, 9+ corresponding lines) Content/Narrative/Presentation/Skins/Brimstone/BrimstonePanelDraw.cs:63 — Content/Narrative/Presentation/Skins/Brimstone/BrimstonePanelDraw.cs:63-71 | Content/Narrative/Presentation/Skins/StarStream/StarStreamPanelDraw.cs:261-271 | Content/Narrative/Presentation/Skins/Tzeentch/TzeentchPanelDraw.cs:101-110 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Content/LegendWeapon/HalibutLegend/DomainSkills/SeaDomain.cs:548 — Content/LegendWeapon/HalibutLegend/DomainSkills/SeaDomain.cs:548-556 | Content/LegendWeapon/HalibutLegend/DomainSkills/SeaDomain.cs:558-567 | Content/LegendWeapon/HalibutLegend/DomainSkills/SeaDomain.cs:576-584 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Content/LegendWeapon/HalibutLegend/UI/HalibutItemTooltipPanel.cs:52 — Content/LegendWeapon/HalibutLegend/UI/HalibutItemTooltipPanel.cs:52-60 | Content/LegendWeapon/OnikiriLegend/UI/OniItemTooltipPanel.cs:57-65 | Content/LegendWeapon/SHPCLegend/UI/SHPCItemTooltipPanel.cs:55-63 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsDeathState.cs:210 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsDeathState.cs:210-221 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/PrimeDeathState.cs:446-457 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/PrimeViceExecutionState.cs:332-340 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Content/EntrustManager/EntrustStatusEntry.cs:38 — Content/EntrustManager/EntrustStatusEntry.cs:38-46 | Content/EntrustManager/EntrustStatusEntry.cs:48-56 | Content/EntrustManager/EntrustStatusEntry.cs:58-66 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeSlash.cs:105 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeSlash.cs:105-113 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearThrust.cs:43-51 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithSlash.cs:118-126 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Content/Items/Magic/WheezingWyrms/WyrmfirePRT.cs:142 — Content/Items/Magic/WheezingWyrms/WyrmfirePRT.cs:142-152 | Content/Items/Melee/CursedflameBloodfists/CursedflamePRT.cs:101-109 | Content/Items/Melee/DawnshatterAzures/DawnshatterPRT.cs:48-62 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Content/PRTTypes/PRT_CyberConverge.cs:41 — Content/PRTTypes/PRT_CyberConverge.cs:41-51 | Content/PRTTypes/PRT_CyberSquare.cs:21-29 | Content/PRTTypes/PRT_SHPCShardGlass.cs:23-33 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:253 — Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:253-261 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:259-269 | Content/Industrials/ElectricPowers/Recyclers/RecyclerUI.cs:253-261 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Content/GameModes/GodSmith/Core/GodSmithTooltip.cs:35 — Content/GameModes/GodSmith/Core/GodSmithTooltip.cs:35-48 | Content/Items/Modifys/RBloodButcherer.cs:89-97 | Content/Items/Modifys/RTerraBlades/RTerraBlade.cs:95-103 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Content/Industrials/ElectricPowers/Turrets/TurretControlUI.cs:321 — Content/Industrials/ElectricPowers/Turrets/TurretControlUI.cs:321-329 | Content/Industrials/Generator/Biomass/BiomassGeneratorUI.cs:339-348 | Content/Industrials/Generator/Thermal/ThermalGeneratorUI.cs:332-341 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:561 — Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:561-569 | Content/Items/Melee/WeaverGrievanceses/WGManifestationActor.cs:444-452 | Content/Items/Melee/WeaverGrievanceses/WGManifestationActor.cs:456-464 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Content/Scenarios/Dungeonworld/Gen/Layers/L1/L1Style.cs:214 — Content/Scenarios/Dungeonworld/Gen/Layers/L1/L1Style.cs:214-222 | Content/Scenarios/Dungeonworld/Gen/Layers/L1/L1Style.cs:307-316 | Content/Scenarios/Dungeonworld/Gen/Layers/L7/L7Style.cs:344-352 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Content/Scenarios/Dungeonworld/Gen/Layers/L4/L4MuteBell.cs:106 — Content/Scenarios/Dungeonworld/Gen/Layers/L4/L4MuteBell.cs:106-115 | Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Leviathan.cs:189-198 | Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Palette.cs:156-164 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishAmanitaVFX.cs:138 — Content/LegendWeapon/HalibutLegend/FishSkills/FishAmanitaVFX.cs:138-149 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBunnyParticles.cs:41-50 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Rendering/SkeletronPRT.cs:68-76 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:586 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:586-594 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:396-404 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:522-530 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdChargeOmen.cs:96 — Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdChargeOmen.cs:96-105 | Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdChargeOmen.cs:108-117 | Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdGuardStanceProj.cs:28-36 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomain.cs:204 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomain.cs:204-212 | Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDream.cs:76-86 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomain.cs:136-147 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryPass.cs:21 — Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryPass.cs:21-29 | Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolBossRoomPass.cs:24-32 | Content/Scenarios/Dungeonworld/Gen/BossRooms/ProofingHallPass.cs:21-29 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishCrimsonTiger.cs:576 — Content/LegendWeapon/HalibutLegend/FishSkills/FishCrimsonTiger.cs:576-585 | Content/LegendWeapon/HalibutLegend/FishSkills/FishFrostMinnow.cs:419-427 | Content/LegendWeapon/HalibutLegend/FishSkills/FishPrincess.cs:423-435 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Content/Cyberwares/Implementation/MimicPerchedAuxBrains/MimicPerchedAuxBrainPlayer.cs:39 — Content/Cyberwares/Implementation/MimicPerchedAuxBrains/MimicPerchedAuxBrainPlayer.cs:39-47 | Content/GameModes/GodSmith/Armors/Hardmode/GsChlorophyteArmor.cs:40-49 | Content/GameModes/GodSmith/Weapons/Guns/GsHarpoon.cs:113-122 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistFallingStar.cs:111 — Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistFallingStar.cs:111-119 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistSeekerStar.cs:136-144 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordEyeLinkProj.cs:114-122 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Content/GameModes/GodSmith/Weapons/Boomerangs/GsEnchantedBoomerang.cs:60 — Content/GameModes/GodSmith/Weapons/Boomerangs/GsEnchantedBoomerang.cs:60-68 | Content/GameModes/GodSmith/Weapons/Flamethrowers/FlamethrowersShared.cs:266-277 | Content/GameModes/GodSmith/Weapons/Guns/GsPhoenixBlaster.cs:395-403 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Content/GameModes/GodSmith/Weapons/Guns/GsPhoenixBlaster.cs:316 — Content/GameModes/GodSmith/Weapons/Guns/GsPhoenixBlaster.cs:316-324 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomNeedle.cs:42-52 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaShrimpWaterBolt.cs:32-41 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Content/Items/Ranged/BloodshotBombs/BloodshotBombThrown.cs:222 — Content/Items/Ranged/BloodshotBombs/BloodshotBombThrown.cs:222-230 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCursed.cs:190-200 | Content/LegendWeapon/HalibutLegend/FishSkills/FishIchorn.cs:141-152 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • + 5 more in this group — see findings.md.
D4 · Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) · ×30
  • Edited copies of one member (3 members, 12+ corresponding lines) Content/Industrials/Generator/Biomass/BiomassGeneratorUI.cs:171 — Content/Industrials/Generator/Biomass/BiomassGeneratorUI.cs:171-182 | Content/Industrials/Generator/GeneratorReadout.cs:203-214 | Content/Industrials/Generator/Thermal/ThermalGeneratorUI.cs:200-213 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) Content/GameModes/BrutalMobs/Ambience/Aetherglim/AetherglimPRT.cs:67 — Content/GameModes/BrutalMobs/Ambience/Aetherglim/AetherglimPRT.cs:67-86 | Content/GameModes/BrutalMobs/Ambience/Aetherglim/AetherglimPRT.cs:262-278 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Rendering/EmpressPRT.cs:242-253 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) Content/Items/Melee/SeasonalKunai.cs:189 — Content/Items/Melee/SeasonalKunai.cs:189-200 | Content/Items/Melee/WraithKunai.cs:258-269 | Content/Items/Ranged/FungalRevolver.cs:200-211 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) Content/GameModes/GodSmith/Prefixes/Magic/GodSmithMythicEchoEndow.cs:150 — Content/GameModes/GodSmith/Prefixes/Magic/GodSmithMythicEchoEndow.cs:150-161 | Content/GameModes/GodSmith/Prefixes/Offense/GodSmithOverkillEndow.cs:110-127 | Content/GameModes/GodSmith/Prefixes/Ranged/GodSmithRicochetEndow.cs:110-126 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalPlantera/Rendering/PlanteraPRT.cs:76 — Content/NPCs/BrutalNPCs/BrutalPlantera/Rendering/PlanteraPRT.cs:76-92 | Content/PRTTypes/PRT_BrideDryPetal.cs:69-85 | Content/PRTTypes/PRT_TurnkeyFoam.cs:64-75 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:410 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:410-425 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuJiFX.cs:171-182 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuPiFX.cs:84-95 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsBloodSpike.cs:184 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsBloodSpike.cs:184-196 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonVesselWhip.cs:393-404 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraVine.cs:253-264 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Rendering/EmpressBeamDraw.cs:32 — Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Rendering/EmpressBeamDraw.cs:32-43 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Rendering/EmpressBeamDraw.cs:65-76 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Rendering/EmpressBeamDraw.cs:97-108 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) Content/GameModes/GodSmith/Armors/Reset/GsFrostArmor.cs:94 — Content/GameModes/GodSmith/Armors/Reset/GsFrostArmor.cs:94-105 | Content/GameModes/GodSmith/Armors/Reset/GsMoltenArmor.cs:81-95 | Content/GameModes/GodSmith/Armors/Reset/GsOreArmorsHardmode.cs:565-579 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhImpFireBolt.cs:41 — Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhImpFireBolt.cs:41-52 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhScytheBolt.cs:41-57 | Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilCursedBeadProj.cs:51-68 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishDoubleCodVFX.cs:67 — Content/LegendWeapon/HalibutLegend/FishSkills/FishDoubleCodVFX.cs:67-78 | Content/LegendWeapon/HalibutLegend/FishSkills/FishofCthuluVFX.cs:62-74 | Content/LegendWeapon/HalibutLegend/FishSkills/FishofCthuluVFX.cs:77-89 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishTropicalBarracuda.cs:94 — Content/LegendWeapon/HalibutLegend/FishSkills/FishTropicalBarracuda.cs:94-105 | Content/LegendWeapon/HalibutLegend/FishSkills/FishTropicalBarracuda.cs:107-118 | Content/LegendWeapon/HalibutLegend/FishSkills/FishTropicalBarracuda.cs:120-131 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) Content/GameModes/GodSmith/Weapons/Broadswords/GsStarWrath.cs:186 — Content/GameModes/GodSmith/Weapons/Broadswords/GsStarWrath.cs:186-200 | Content/GameModes/GodSmith/Weapons/Broadswords/GsStarWrath.cs:482-494 | Content/GameModes/GodSmith/Weapons/Spears/GsNorthPole.cs:414-425 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishDirtParticles.cs:140 — Content/LegendWeapon/HalibutLegend/FishSkills/FishDirtParticles.cs:140-151 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistParticles.cs:180-192 | Content/PRTTypes/PRT_AcidSplash.cs:78-110 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Barrel/ConcussionBarrelModule.cs:24 — Content/LegendWeapon/SHPCLegend/Modules/Barrel/ConcussionBarrelModule.cs:24-36 | Content/LegendWeapon/SHPCLegend/Modules/Power/ResonanceReactorModule.cs:50-61 | Content/LegendWeapon/SHPCLegend/Modules/Power/ScrambleFieldModule.cs:23-35 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2Rooms.cs:312 — Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2Rooms.cs:312-323 | Content/Scenarios/Dungeonworld/Gen/Layers/L4/L4Palette.cs:102-113 | Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Leviathan.cs:480-491 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiFalseBody.cs:158 — Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiFalseBody.cs:158-172 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiGroundBurn.cs:227-242 | Content/LegendWeapon/SHPCLegend/Modules/Grip/EfficientGripModule.cs:165-176 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) Content/Items/Melee/NeutronGlaive.cs:1283 — Content/Items/Melee/NeutronGlaive.cs:1283-1294 | Content/Items/Melee/NeutronGlaive.cs:1362-1374 | Content/Items/Ranged/NeutronBows/EXNeutronExplosionRanged.cs:60-72 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaTalismans/KikasaTalismanStackNPC.cs:92 — Content/LegendWeapon/KikasaLegend/KikasaTalismans/KikasaTalismanStackNPC.cs:92-103 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/KikasaTalismanStackNPC.cs:105-116 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/KikasaTalismanStackNPC.cs:118-130 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) Content/Scenarios/Dungeonworld/Gen/Layers/L4/L4Content.cs:531 — Content/Scenarios/Dungeonworld/Gen/Layers/L4/L4Content.cs:531-542 | Content/Scenarios/Dungeonworld/Gen/Layers/L4/L4Content.cs:544-558 | Content/Scenarios/Dungeonworld/Gen/Layers/L4/L4Content.cs:560-574 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) Content/GameModes/BrutalMobs/EliteMove/EliteMoveNPC.cs:145 — Content/GameModes/BrutalMobs/EliteMove/EliteMoveNPC.cs:145-156 | Content/GameModes/BrutalMobs/Ocean/OceanBrutalNPC.cs:272-283 | Content/GameModes/BrutalMobs/Sky/SkyBrutalNPC.cs:144-155 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) Content/Items/Modifys/RBloodButcherer.cs:972 — Content/Items/Modifys/RBloodButcherer.cs:972-984 | Content/Items/Modifys/RTerraBlades/TerraLightProj.cs:204-215 | Content/LegendWeapon/HalibutLegend/FishSkills/FishIchorn.cs:291-304 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Barrel/CoralReefBarrelModule.cs:94 — Content/LegendWeapon/SHPCLegend/Modules/Barrel/CoralReefBarrelModule.cs:94-105 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/MagmaVentBarrelModule.cs:104-115 | Content/LegendWeapon/SHPCLegend/Modules/Power/PlasmaInjectorModule.cs:61-73 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) Content/GameModes/BrutalMobs/Ambience/Fleshfen/FleshfenBloodDew.cs:183 — Content/GameModes/BrutalMobs/Ambience/Fleshfen/FleshfenBloodDew.cs:183-194 | Content/GameModes/BrutalMobs/Ambience/Rimehollow/RimehollowDirector.cs:224-235 | Content/GameModes/BrutalMobs/Ambience/Verdant/VerdantAmbience.cs:86-97 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) Content/Items/Magic/Eyetooths/EyetoothDart.cs:59 — Content/Items/Magic/Eyetooths/EyetoothDart.cs:59-72 | Content/Items/Magic/Pandemoniums/PandemoniumCircle.cs:48-59 | Content/Items/Magic/Pandemoniums/PandemoniumFirePillar.cs:24-35 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • + 5 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×30
  • Duplicated block (11–12 lines × 2) Content/HackTimes/HackTimeNPCDraw.cs:27 — Content/HackTimes/HackTimeNPCDraw.cs:27-38 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBanishNPCDraw.cs:44-54 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/HackTimes/HackTimeNPCDraw.cs:27` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (11–12 lines × 2) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterTile.cs:96 — Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterTile.cs:96-106 | Content/Industrials/ElectricPowers/Crushers/CrusherTile.cs:94-105 — before extracting anything, compare `Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterTile.cs` and `Content/Industrials/ElectricPowers/Crushers/CrusherTile.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 74 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (11–12 lines × 2) Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMoonFlare.cs:107 — Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMoonFlare.cs:107-118 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteStarSurge.cs:58-68 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMoonFlare.cs:107` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMoonFlare.cs:122` calls `RayLength` and `Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteStarSurge.cs:70` 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–12 lines × 2) Content/Items/Accessories/BrutalRelics/Plantera/BloomVineSnare.cs:97 — Content/Items/Accessories/BrutalRelics/Plantera/BloomVineSnare.cs:97-108 | Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraSnareVine.cs:87-97 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/Plantera/BloomVineSnare.cs:97` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (11–12 lines × 2) Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:431 — Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:431-441 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpBubble.cs:81-92 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (11–12 lines × 2) Content/Items/Magic/Elysiums/Revelations/CelestialMeteor.cs:156 — Content/Items/Magic/Elysiums/Revelations/CelestialMeteor.cs:156-167 | Content/Items/Magic/Elysiums/Revelations/RevelationDomain.cs:121-131 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/Elysiums/Revelations/CelestialMeteor.cs:156` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Magic/Elysiums/Revelations/CelestialMeteor.cs:154` calls `SetValue` and `Content/Items/Magic/Elysiums/Revelations/RevelationDomain.cs:121` does not — after which the two agree again for 3 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–12 lines × 2) Content/Items/Magic/Everdeeps/EverdeepVFX.cs:57 — Content/Items/Magic/Everdeeps/EverdeepVFX.cs:57-67 | Content/LegendWeapon/HalibutLegend/OceanCurrentParticles.cs:113-124 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/Everdeeps/EverdeepVFX.cs:57` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (11–12 lines × 2) Content/Items/Melee/Abyssrends/AbyssrendFX.cs:115 — Content/Items/Melee/Abyssrends/AbyssrendFX.cs:115-125 | Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:753-764 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:765` calls `SetValue`, `Max` and `Content/Items/Melee/Abyssrends/AbyssrendFX.cs:126` 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–12 lines × 2) Content/Items/Melee/DivineSourceBlades/DivineSourceBoltProjectile.cs:86 — Content/Items/Melee/DivineSourceBlades/DivineSourceBoltProjectile.cs:86-97 | Content/Items/Modifys/RTerraBlades/TerraLightProj.cs:77-87 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DivineSourceBlades/DivineSourceBoltProjectile.cs:86` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Modifys/RTerraBlades/TerraLightProj.cs:88` calls `ToRotation` and `Content/Items/Melee/DivineSourceBlades/DivineSourceBoltProjectile.cs:99` does not — after which the two agree again for 3 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–12 lines × 2) Content/Items/Modifys/RBloodButcherer.cs:48 — Content/Items/Modifys/RBloodButcherer.cs:48-58 | Content/Items/Modifys/RTerraBlades/RTerraBlade.cs:51-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Modifys/RBloodButcherer.cs:48` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11–12 lines × 2) Content/Items/Stones/Granites/GraniteFlower.cs:22 — Content/Items/Stones/Granites/GraniteFlower.cs:22-32 | Content/Items/Stones/Granites/GraniteTome.cs:22-33 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Stones/Granites/GraniteFlower.cs:22` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (11–12 lines × 2) Content/LegendWeapon/HalibutLegend/FishSkills/FishTunabeardVFX.cs:292 — Content/LegendWeapon/HalibutLegend/FishSkills/FishTunabeardVFX.cs:292-302 | Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniKamuiFlowRenderer.cs:195-206 — before extracting anything, compare `Content/LegendWeapon/HalibutLegend/FishSkills/FishTunabeardVFX.cs` and `Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniKamuiFlowRenderer.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 112 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishTunabeardVFX.cs:292` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11–12 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamFogRender.cs:79 — Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamFogRender.cs:79-89 | Content/Scenarios/Kiyume/Fog/KiyumeGroundFogRender.cs:116-127 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Kiyume/Fog/KiyumeGroundFogRender.cs:116` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (11–12 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutDomain.cs:81 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutDomain.cs:81-92 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumCircle.cs:84-94 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11–12 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1461 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1461-1472 | Content/NPCs/ScrapCommanders/ScrapCommander.cs:764-774 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1461` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (11–12 lines × 2) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:995 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:995-1005 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:978-989 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 870 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:995` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (11–12 lines × 2) Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:408 — Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:408-418 | Content/LegendWeapon/OnikiriLegend/OniZanshinSlashs/OniZanshinSlash.cs:497-508 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:408` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11–12 lines × 2) Content/LegendWeapon/OnikiriLegend/UI/OniItemTooltipPanel.cs:43 — Content/LegendWeapon/OnikiriLegend/UI/OniItemTooltipPanel.cs:43-53 | Content/LegendWeapon/OnikiriLegend/UI/OniRegisterRenderer.cs:44-55 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/UI/OniRegisterRenderer.cs:44` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (11–12 lines × 2) Content/LegendWeapon/OnikiriLegend/UI/OniMeiCodexUI.cs:462 — Content/LegendWeapon/OnikiriLegend/UI/OniMeiCodexUI.cs:462-472 | Content/LegendWeapon/OnikiriLegend/UI/OniMeiUI.cs:1122-1133 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/UI/OniMeiCodexUI.cs:462` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11–12 lines × 2) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:372 — Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:372-382 | Content/LegendWeapon/SHPCLegend/UI/SHPCModuleSelectPanel.cs:384-395 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:372` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:371` calls `DrawFilledRect`, `Rectangle` and `Content/LegendWeapon/SHPCLegend/UI/SHPCModuleSelectPanel.cs:384` does not — after which the two agree again for 3 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–12 lines × 2) Content/MainMenus/Shenyo/ShenyoGhostLakeScene.cs:462 — Content/MainMenus/Shenyo/ShenyoGhostLakeScene.cs:462-472 | Content/MainMenus/Shenyo/ShenyoGhostLakeScene.cs:530-541 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/MainMenus/Shenyo/ShenyoGhostLakeScene.cs:462` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (11–12 lines × 2) Content/NPCs/BloomsandSerpents/BssBody.cs:306 — Content/NPCs/BloomsandSerpents/BssBody.cs:306-317 | Content/NPCs/BloomsandSerpents/BssHead.cs:800-810 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BloomsandSerpents/BssBody.cs:306` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11–12 lines × 2) Content/NPCs/BloomsandSerpents/States/BssPincerSnapState.cs:104 — Content/NPCs/BloomsandSerpents/States/BssPincerSnapState.cs:104-114 | Content/NPCs/BloomsandSerpents/States/BssPounceState.cs:129-140 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BloomsandSerpents/States/BssPincerSnapState.cs:104` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (11–12 lines × 2) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Rendering/TwinsRenderHelper.cs:164 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Rendering/TwinsRenderHelper.cs:164-175 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Rendering/TwinsRenderHelper.cs:214-224 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Rendering/TwinsRenderHelper.cs:164` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (11–12 lines × 2) Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordHandAI.cs:329 — Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordHandAI.cs:329-340 | Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordHandAI.cs:374-384 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordHandAI.cs:329` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
  • + 5 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (9–10 lines × 2) · ×30
  • Duplicated block (9–10 lines × 2) Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs:284 — Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs:284-293 | Content/LegendWeapon/SHPCLegend/UI/DomainWheel/SHPCDomainWheelUI.cs:252-260 — before extracting anything, compare `Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs` and `Content/LegendWeapon/SHPCLegend/UI/DomainWheel/SHPCDomainWheelUI.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs:284` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs:297` calls `DrawArcStroke` and `Content/LegendWeapon/SHPCLegend/UI/DomainWheel/SHPCDomainWheelUI.cs:260` does not — after which the two agree again for 3 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–10 lines × 2) Content/Cyberwares/UIs/CyberwareUI.cs:290 — Content/Cyberwares/UIs/CyberwareUI.cs:290-299 | Content/NPCs/Victors/UIs/VictorClinicUI.cs:195-203 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Cyberwares/UIs/CyberwareUI.cs:290` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9–10 lines × 2) Content/GameModes/BrutalMobs/Ambience/Fleshfen/FleshfenAmbience.cs:376 — Content/GameModes/BrutalMobs/Ambience/Fleshfen/FleshfenAmbience.cs:376-384 | Content/Scenarios/OldNet/Backgrounds/OldNetAmbience.cs:114-123 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (9–10 lines × 2) Content/GameModes/BrutalMobs/EvilBiome/Projectiles/MummyWrapProj.cs:79 — Content/GameModes/BrutalMobs/EvilBiome/Projectiles/MummyWrapProj.cs:79-88 | Content/GameModes/BrutalMobs/EvilBiome/Projectiles/SiphonPounceOmen.cs:113-121 — 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. 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 (9–10 lines × 2) Content/GameModes/GodSmith/Armors/Endgame/GsHuntressArmor.cs:162 — Content/GameModes/GodSmith/Armors/Endgame/GsHuntressArmor.cs:162-170 | Content/GameModes/GodSmith/Weapons/SummonSentries/Projectiles/GsSentryChainLightningProj.cs:41-50 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (9–10 lines × 2) Content/HackTimes/HackEffectNPC.cs:66 — Content/HackTimes/HackEffectNPC.cs:66-75 | Content/HackTimes/HackEffectNPC.cs:77-85 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9–10 lines × 2) Content/Items/Accessories/ArcaneThroneOfEternity.cs:634 — Content/Items/Accessories/ArcaneThroneOfEternity.cs:634-643 | Content/Items/Accessories/EyeOfSingularity.cs:637-645 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/ArcaneThroneOfEternity.cs:634` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (9–10 lines × 2) Content/Items/Accessories/BrutalRelics/BrainOfCthulhu/MirrorheartRender.cs:127 — Content/Items/Accessories/BrutalRelics/BrainOfCthulhu/MirrorheartRender.cs:127-135 | Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Rendering/BrainRenderHelper.cs:53-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (9–10 lines × 2) Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMoonFlare.cs:275 — Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMoonFlare.cs:275-284 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistGazeBeam.cs:340-348 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMoonFlare.cs:275` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (9–10 lines × 2) Content/Items/Magic/Elysiums/Disciples/BaseDisciple.cs:231 — Content/Items/Magic/Elysiums/Disciples/BaseDisciple.cs:231-240 | Content/Items/Magic/Elysiums/Revelations/ApocalypseHorseman.cs:141-149 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/Elysiums/Disciples/BaseDisciple.cs:231` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9–10 lines × 2) Content/Items/Melee/Abyssrends/AbyssrendUndercurrent.cs:123 — Content/Items/Melee/Abyssrends/AbyssrendUndercurrent.cs:123-132 | Content/Items/Melee/TideReapers/TideReaperWave.cs:87-95 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9–10 lines × 2) Content/Items/Melee/Arbiters/Arbiter.cs:337 — Content/Items/Melee/Arbiters/Arbiter.cs:337-346 | Content/Items/Melee/Cloudwalking.cs:310-318 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Arbiters/Arbiter.cs:337` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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 (9–10 lines × 2) Content/LegendWeapon/HalibutLegend/FishSkills/FishDemonicHell.cs:746 — Content/LegendWeapon/HalibutLegend/FishSkills/FishDemonicHell.cs:746-754 | Content/PRTTypes/PRT_PallbearerEmber.cs:45-54 — before extracting anything, compare `Content/LegendWeapon/HalibutLegend/FishSkills/FishDemonicHell.cs` and `Content/PRTTypes/PRT_PallbearerEmber.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishDemonicHell.cs:746` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/PRTTypes/PRT_PallbearerEmber.cs:44` calls `AI` and `Content/LegendWeapon/HalibutLegend/FishSkills/FishDemonicHell.cs:743` 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–10 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:568 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:568-576 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:774-783 — 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–10 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetHourglass.cs:368 — Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetHourglass.cs:368-376 | Content/Scenarios/Kiame/KiameWakeResetRender.cs:283-292 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (9–10 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:447 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:447-456 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:719-727 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:447` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9–10 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuShaFX.cs:100 — Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuShaFX.cs:100-108 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuYuFX.cs:247-256 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuShaFX.cs:100` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (9–10 lines × 2) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1694 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1694-1703 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1560-1568 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs` as WHOLE FILES: this scan already matched 50 separate duplicated blocks between them, totalling at least 870 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1694` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9–10 lines × 2) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberChargeOrbProj.cs:547 — Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberChargeOrbProj.cs:547-556 | Content/LegendWeapon/SHPCLegend/Modules/Grip/SentinelGripModule.cs:34-42 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberChargeOrbProj.cs:547` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9–10 lines × 2) Content/LegendWeapon/SHPCLegend/Modules/Barrel/ReflectionBarrelModule.cs:47 — Content/LegendWeapon/SHPCLegend/Modules/Barrel/ReflectionBarrelModule.cs:47-56 | Content/LegendWeapon/SHPCLegend/Modules/Optic/EchoOpticModule.cs:32-40 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/Modules/Barrel/ReflectionBarrelModule.cs:47` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9–10 lines × 2) Content/LegendWeapon/SHPCLegend/Modules/Optic/PrecisionOpticModule.cs:96 — Content/LegendWeapon/SHPCLegend/Modules/Optic/PrecisionOpticModule.cs:96-105 | Content/LegendWeapon/SHPCLegend/Modules/Power/HighVoltageCoreModule.cs:63-71 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/Modules/Optic/PrecisionOpticModule.cs:96` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9–10 lines × 2) Content/NPCs/BloomsandSerpents/States/BssCoilRingState.cs:153 — Content/NPCs/BloomsandSerpents/States/BssCoilRingState.cs:153-162 | Content/NPCs/BloomsandSerpents/States/BssPillarVaultState.cs:311-319 — 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 (9–10 lines × 2) Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerSeizeHandProj.cs:247 — Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerSeizeHandProj.cs:247-255 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerShadowHandProj.cs:152-161 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerSeizeHandProj.cs:247` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (9–10 lines × 2) Content/NPCs/BrutalNPCs/BrutalGolem/Rendering/GolemRenderHelper.cs:49 — Content/NPCs/BrutalNPCs/BrutalGolem/Rendering/GolemRenderHelper.cs:49-57 | Content/NPCs/BrutalNPCs/BrutalGolem/Rendering/GolemRenderHelper.cs:110-119 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalGolem/Rendering/GolemRenderHelper.cs:49` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/BrutalNPCs/BrutalGolem/Rendering/GolemRenderHelper.cs:107` calls `SetValue`, `ToVector4` and `Content/NPCs/BrutalNPCs/BrutalGolem/Rendering/GolemRenderHelper.cs:46` does not — after which the two agree again for 3 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–10 lines × 2) Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraPoisonSeed.cs:59 — Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraPoisonSeed.cs:59-68 | Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraThornBall.cs:74-82 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraPoisonSeed.cs:59` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraThornBall.cs:83` calls `SpawnPetalBurst` and `Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraPoisonSeed.cs:69` does not — after which the two agree again for 4 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.
  • + 5 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (26 corresponding lines) · ×29
  • Edited copy of a member (26 corresponding lines) Content/EntrustManager/Styles/ForestManagerStyle.cs:739 — Content/EntrustManager/Styles/ForestManagerStyle.cs:739-764 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:734-759 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) Content/LegendWeapon/HalibutLegend/DomainSkills/Superposition.cs:206 — Content/LegendWeapon/HalibutLegend/DomainSkills/Superposition.cs:206-257 | Content/LegendWeapon/HalibutLegend/DomainSkills/YourLevelIsTooLow.cs:864-889 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) Content/EntrustManager/Styles/ForestManagerStyle.cs:131 — Content/EntrustManager/Styles/ForestManagerStyle.cs:131-165 | Content/QuestLogs/Styles/ForestQuestLogStyle.cs:99-124 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) Content/Scenarios/Dungeonworld/NPCs/Elites/BoneStitcher.cs:928 — Content/Scenarios/Dungeonworld/NPCs/Elites/BoneStitcher.cs:928-953 | Content/Scenarios/Dungeonworld/NPCs/Elites/DrownedTurnkey.cs:726-753 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaVaults/KikasaVaultRenderer.cs:25 — Content/LegendWeapon/KikasaLegend/KikasaVaults/KikasaVaultRenderer.cs:25-52 | Content/LegendWeapon/KikasaLegend/UI/Panorama/KikasaPanoramaRenderer.cs:35-60 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) Content/NPCs/BloomsandSerpents/Projectiles/BssPetalProj.cs:72 — Content/NPCs/BloomsandSerpents/Projectiles/BssPetalProj.cs:72-98 | Content/NPCs/BloomsandSerpents/Projectiles/BssWindPetalProj.cs:91-116 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) Content/EntrustManager/BaseQuestAcceptUI.cs:329 — Content/EntrustManager/BaseQuestAcceptUI.cs:329-354 | Content/UIs/OverhaulSettings/OverhaulSettingsUI.cs:436-461 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) Content/Items/Accessories/BrutalRelics/EmpressOfLight/InterferenceBursts.cs:77 — Content/Items/Accessories/BrutalRelics/EmpressOfLight/InterferenceBursts.cs:77-102 | Content/Items/Accessories/BrutalRelics/EmpressOfLight/InterferenceBursts.cs:182-209 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) Content/Items/Ranged/RaiderGun.cs:354 — Content/Items/Ranged/RaiderGun.cs:354-379 | Content/Items/Ranged/RaiderGun.cs:425-462 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) Content/Items/Accessories/BrutalRelics/KingSlime/FallenCrownProj.cs:227 — Content/Items/Accessories/BrutalRelics/KingSlime/FallenCrownProj.cs:227-252 | Content/Items/Accessories/BrutalRelics/KingSlime/KingsVerdictWave.cs:142-167 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) Content/Cyberwares/Implementation/OmniElectricFoots/OmniElectricFootVFX.cs:317 — Content/Cyberwares/Implementation/OmniElectricFoots/OmniElectricFootVFX.cs:317-342 | Content/Cyberwares/Implementation/OmniElectricFoots/OmniElectricFootVFX.cs:345-381 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) Content/GameModes/GodSmith/Weapons/MagicChant/GsCursedFlames.cs:174 — Content/GameModes/GodSmith/Weapons/MagicChant/GsCursedFlames.cs:174-206 | Content/GameModes/GodSmith/Weapons/MagicChant/GsNettleBurst.cs:199-224 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailHead.cs:256 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailHead.cs:256-281 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:941-969 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowApexFrenzyState.cs:111 — Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowApexFrenzyState.cs:111-136 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowSplitPincerState.cs:107-149 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerSoloRageState.cs:55 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerSoloRageState.cs:55-81 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismSoloRageState.cs:56-81 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) Content/Industrials/ElectricPowers/Lumberjacks/LumberjackSaw.cs:105 — Content/Industrials/ElectricPowers/Lumberjacks/LumberjackSaw.cs:105-144 | Content/Industrials/ElectricPowers/Lumberjacks/WGGLumberjack.cs:728-753 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) Content/HackTimes/HackTimeNetSync.cs:1234 — Content/HackTimes/HackTimeNetSync.cs:1234-1261 | Content/HackTimes/HackTimeNetSync.cs:1277-1302 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) Content/Items/Melee/Shatterfangs/ShatterfangPRT.cs:49 — Content/Items/Melee/Shatterfangs/ShatterfangPRT.cs:49-74 | Content/LegendWeapon/HalibutLegend/FishSkills/FishRockParticles.cs:141-168 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrown.cs:367 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrown.cs:367-399 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaScourge.cs:219-244 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) Content/GameModes/GodSmith/Armors/Reset/GsBeeArmor.cs:36 — Content/GameModes/GodSmith/Armors/Reset/GsBeeArmor.cs:36-61 | Content/Items/Melee/OniMachete.cs:131-161 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) Content/NPCs/TBUGs/TBUGMood.cs:41 — Content/NPCs/TBUGs/TBUGMood.cs:41-66 | Content/NPCs/Victors/VictorMood.cs:41-66 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) Content/Industrials/ElectricPowers/IndustrialServiceNet.cs:52 — Content/Industrials/ElectricPowers/IndustrialServiceNet.cs:52-77 | Content/Industrials/ElectricPowers/IndustrialServiceNet.cs:130-157 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) Content/Items/Magic/TomeofFungalDecay.cs:79 — Content/Items/Magic/TomeofFungalDecay.cs:79-104 | Content/Items/Ranged/SporeBubbleBlaster.cs:81-108 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) Content/NPCs/BrutalNPCs/BrutalSkeletron/States/Hands/HandApplaudState.cs:26 — Content/NPCs/BrutalNPCs/BrutalSkeletron/States/Hands/HandApplaudState.cs:26-51 | Content/NPCs/BrutalNPCs/BrutalSkeletron/States/Hands/HandSnatchState.cs:31-60 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1355 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1355-1380 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1420-1447 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • + 4 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×29
  • Duplicated block (17 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:394 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:394-410 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:387-403 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (17 lines × 2) Content/Scenarios/Draedon/Quest/DeploySignaltowers/SignalTower/SignalTowerTargetManager.cs:191 — Content/Scenarios/Draedon/Quest/DeploySignaltowers/SignalTower/SignalTowerTargetManager.cs:191-207 | Content/Scenarios/Draedon/Quest/DeploySignaltowers/SignalTower/SignalTowerTargetManager.cs:217-233 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Draedon/Quest/DeploySignaltowers/SignalTower/SignalTowerTargetManager.cs:191` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerLaserMatrixState.cs:174 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerLaserMatrixState.cs:174-190 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerSoloRageState.cs:470-486 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerLaserMatrixState.cs:174` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) Content/NPCs/TBUGs/TBUGRiftSpawner.cs:15 — Content/NPCs/TBUGs/TBUGRiftSpawner.cs:15-31 | Content/NPCs/Victors/VictorPortalSpawner.cs:16-32 — before extracting anything, compare `Content/NPCs/TBUGs/TBUGRiftSpawner.cs` and `Content/NPCs/Victors/VictorPortalSpawner.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 130 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (17 lines × 2) Common/NpcGroupHelper.cs:113 — Common/NpcGroupHelper.cs:113-129 | Common/NpcGroupHelper.cs:179-195 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Common/NpcGroupHelper.cs:113` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `output` to `List<NPC>` in one and `List<int>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (17 lines × 2) Content/GameModes/GodSmith/Weapons/MeleeOddities/GsScourgeoftheCorruptor.cs:117 — Content/GameModes/GodSmith/Weapons/MeleeOddities/GsScourgeoftheCorruptor.cs:117-133 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsVampireKnives.cs:201-217 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/MeleeOddities/GsScourgeoftheCorruptor.cs:117` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) Content/Industrials/ElectricPowers/TeleportStations/TeleportStationTP.cs:222 — Content/Industrials/ElectricPowers/TeleportStations/TeleportStationTP.cs:222-238 | Content/Industrials/ElectricPowers/TeleportStations/TeleportStationTP.cs:249-265 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/TeleportStations/TeleportStationTP.cs:222` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) Content/Items/Accessories/NinjaCthulsparkBoots.cs:387 — Content/Items/Accessories/NinjaCthulsparkBoots.cs:387-403 | Content/Items/Stones/Granites/GraniteWalkingBoots.cs:209-225 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/NinjaCthulsparkBoots.cs:387` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) Content/Items/Melee/SeasonalKunai.cs:20 — Content/Items/Melee/SeasonalKunai.cs:20-36 | Content/Items/Melee/WraithKunai.cs:24-40 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/SeasonalKunai.cs:20` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleCut.cs:337 — Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleCut.cs:337-353 | Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashMark.cs:232-248 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleCut.cs:337` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/Arms/PrimeViceStates.cs:286 — Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/Arms/PrimeViceStates.cs:286-302 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/Arms/PrimeViceStates.cs:335-351 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/Arms/PrimeViceStates.cs:286` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSystem.cs:155 — Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSystem.cs:155-171 | Content/Scenarios/Kiyume/Fog/KiyumeFogSystem.cs:193-209 — before extracting anything, compare `Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSystem.cs` and `Content/Scenarios/Kiyume/Fog/KiyumeFogSystem.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSystem.cs:155` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) Content/EntrustManager/Styles/DraedonManagerStyle.cs:692 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:692-708 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:703-719 — before extracting anything, compare `Content/EntrustManager/Styles/DraedonManagerStyle.cs` and `Content/EntrustManager/Styles/HotwindManagerStyle.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 442 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 (17 lines × 2) Content/GameModes/GodSmith/Armors/Reset/GsSpectreArmors.cs:103 — Content/GameModes/GodSmith/Armors/Reset/GsSpectreArmors.cs:103-119 | Content/GameModes/GodSmith/Armors/Reset/GsTikiArmor.cs:68-84 — before extracting anything, compare `Content/GameModes/GodSmith/Armors/Reset/GsSpectreArmors.cs` and `Content/GameModes/GodSmith/Armors/Reset/GsTikiArmor.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 57 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Armors/Reset/GsSpectreArmors.cs:103` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT1.cs:338 — Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT1.cs:338-354 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT3.cs:217-233 — before extracting anything, compare `Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT1.cs` and `Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT3.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 89 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (17 lines × 2) Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:193 — Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:193-209 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerIceSpikeProj.cs:176-192 — before extracting anything, compare `Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs` and `Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerIceSpikeProj.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 189 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:193` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) Content/Items/Accessories/BrutalRelics/Twins/TwinPupilShots.cs:129 — Content/Items/Accessories/BrutalRelics/Twins/TwinPupilShots.cs:129-145 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/CursedFlameJet.cs:26-42 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/Twins/TwinPupilShots.cs:129` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (17 lines × 2) Content/Items/Magic/AriaofTheCosmoses/AccretionDisk.cs:431 — Content/Items/Magic/AriaofTheCosmoses/AccretionDisk.cs:431-447 | Content/Items/Magic/AriaofTheCosmoses/FlattenedAccretionDisk.cs:172-188 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/AriaofTheCosmoses/AccretionDisk.cs:431` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:322 — Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:322-338 | Content/Items/Melee/WeaverGrievanceses/WGManifestationActor.cs:257-273 — before extracting anything, compare `Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs` and `Content/Items/Melee/WeaverGrievanceses/WGManifestationActor.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 237 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (17 lines × 2) Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:302 — Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:302-318 | Content/Items/Melee/NeutronGlaive.cs:304-320 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:302` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Melee/NeutronGlaive.cs:323` calls `Sin` and `Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:319` 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 (17 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:710 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:710-726 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:940-956 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:710` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) Content/LegendWeapon/SHPCLegend/Modules/SHPCModuleLootSystem.cs:108 — Content/LegendWeapon/SHPCLegend/Modules/SHPCModuleLootSystem.cs:108-124 | Content/RAMSystems/RamUpgradeChipLootSystem.cs:77-93 — before extracting anything, compare `Content/LegendWeapon/SHPCLegend/Modules/SHPCModuleLootSystem.cs` and `Content/RAMSystems/RamUpgradeChipLootSystem.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (17 lines × 2) Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemEyeRay.cs:128 — Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemEyeRay.cs:128-144 | Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemGrabRay.cs:129-145 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemEyeRay.cs` and `Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemGrabRay.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 49 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemEyeRay.cs:128` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordHandAI.cs:622 — Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordHandAI.cs:622-638 | Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordHeadAI.cs:199-215 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (17 lines × 2) Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2Palette.cs:68 — Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2Palette.cs:68-84 | Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Palette.cs:75-91 — before extracting anything, compare `Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2Palette.cs` and `Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Palette.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2Palette.cs:68` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • + 4 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (12 lines × 3) · ×29
  • Duplicated block (12 lines × 3) Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:540 — Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:540-551 | Content/QuestLogs/Styles/ForestQuestLogStyle.cs:452-463 | Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:461-472 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:540` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:538` calls `Color` and `Content/QuestLogs/Styles/ForestQuestLogStyle.cs:450` does not — after which the two agree again for 4 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 (12 lines × 3) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1078 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1078-1089 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:840-851 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1038-1049 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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 (12 lines × 3) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:257 — Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:257-268 | Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:231-242 | Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:277-288 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:257` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 3) Content/EntrustManager/Styles/DraedonManagerStyle.cs:302 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:302-313 | Content/EntrustManager/Styles/ForestManagerStyle.cs:307-318 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:296-307 — before extracting anything, compare `Content/EntrustManager/Styles/DraedonManagerStyle.cs` and `Content/EntrustManager/Styles/ForestManagerStyle.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 334 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/EntrustManager/Styles/DraedonManagerStyle.cs:302` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (12 lines × 3) Content/Items/Modifys/RBloodButcherer.cs:988 — Content/Items/Modifys/RBloodButcherer.cs:988-999 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunBullet.cs:231-242 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:214-225 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (12 lines × 3) Content/Items/Modifys/RBloodButcherer.cs:1005 — Content/Items/Modifys/RBloodButcherer.cs:1005-1016 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunBullet.cs:248-259 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:231-242 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Modifys/RBloodButcherer.cs:1005` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:246 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:246-257 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:246-257 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:244-255 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs` as WHOLE FILES: this scan already matched 75 separate duplicated blocks between them, totalling at least 912 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:246` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:994 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:994-1005 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1474-1485 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:1005-1016 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs` as WHOLE FILES: this scan already matched 48 separate duplicated blocks between them, totalling at least 508 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:994` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 3) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistPhaseSkyEffect.cs:145 — Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistPhaseSkyEffect.cs:145-156 | Content/Wraiths/Abilities/CrimsonBrides/BrideHallSky.cs:149-160 | Content/Wraiths/Abilities/GhostRains/GhostRainAmbience.cs:149-160 — before extracting anything, compare `Content/Wraiths/Abilities/CrimsonBrides/BrideHallSky.cs` and `Content/Wraiths/Abilities/GhostRains/GhostRainAmbience.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistPhaseSkyEffect.cs:145` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:54 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:54-65 | Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs:59-70 | Content/Scenarios/Kiame/Overlay/OniRainWorldRender.cs:50-61 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs` and `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 192 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs:56` calls `LoadNPC` and `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:52` does not — after which the two agree again for 3 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 (12 lines × 3) Content/NPCs/BrutalNPCs/BrutalGolem/GolemBodyAI.cs:162 — Content/NPCs/BrutalNPCs/BrutalGolem/GolemBodyAI.cs:162-173 | Content/NPCs/BrutalNPCs/BrutalSkeletron/SkeletronHeadAI.cs:137-148 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/HeadPrimeAI.cs:222-233 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalGolem/GolemBodyAI.cs:162` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 3) Content/Cyberwares/Implementation/Sandevistans/SandevistanRender.cs:41 — Content/Cyberwares/Implementation/Sandevistans/SandevistanRender.cs:41-54 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainRender.cs:43-57 | Content/Scenarios/OldNet/Renders/OldNetGradeRender.cs:41-52 — before extracting anything, compare `Content/Cyberwares/Implementation/Sandevistans/SandevistanRender.cs` and `Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainRender.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Cyberwares/Implementation/Sandevistans/SandevistanRender.cs:41` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 3) Content/GameModes/BrutalMobs/FrostMoon/FrmMeleeNPC.cs:206 — Content/GameModes/BrutalMobs/FrostMoon/FrmMeleeNPC.cs:206-217 | Content/GameModes/BrutalMobs/FrostMoon/FrmMiniBossNPC.cs:153-164 | Content/GameModes/BrutalMobs/FrostMoon/FrmSiegeNPC.cs:155-166 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (12 lines × 3) Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkChargeOmen.cs:140 — Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkChargeOmen.cs:140-151 | Content/GameModes/BrutalMobs/Sky/Projectiles/SkyGaleDiveOmen.cs:116-127 | Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornDiveLane.cs:115-126 — before extracting anything, compare `Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkChargeOmen.cs` and `Content/GameModes/BrutalMobs/Sky/Projectiles/SkyGaleDiveOmen.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (12 lines × 3) Content/GameModes/GodSmith/Armors/Reset/GsCrimsonArmor.cs:55 — Content/GameModes/GodSmith/Armors/Reset/GsCrimsonArmor.cs:55-66 | Content/GameModes/GodSmith/Armors/Reset/GsOreArmorsHardmode.cs:315-326 | Content/GameModes/GodSmith/Armors/Reset/GsOreArmorsPreHardmode.cs:328-339 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/GameModes/GodSmith/Armors/Reset/GsOreArmorsHardmode.cs:328` calls `GetAlpha`, `Color` and `Content/GameModes/GodSmith/Armors/Reset/GsCrimsonArmor.cs:68` does not — after which the two agree again for 4 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 (12 lines × 3) Content/GameModes/GodSmith/Armors/Reset/GsCrystalAssassinArmor.cs:84 — Content/GameModes/GodSmith/Armors/Reset/GsCrystalAssassinArmor.cs:84-95 | Content/GameModes/GodSmith/Armors/Reset/GsHallowedArmor.cs:91-102 | Content/GameModes/GodSmith/Armors/Reset/GsOreArmorsHardmode.cs:471-482 — 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 (12 lines × 3) Content/GameModes/GodSmith/Weapons/Bows/Projectiles/GsFaeOrbiterProj.cs:24 — Content/GameModes/GodSmith/Weapons/Bows/Projectiles/GsFaeOrbiterProj.cs:24-35 | Content/GameModes/GodSmith/Weapons/Launchers/GsElectrosphereLauncher.cs:106-117 | Content/GameModes/GodSmith/Weapons/Launchers/GsJackOLanternLauncher.cs:50-61 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (12 lines × 3) Content/GameModes/GodSmith/Weapons/MagicChant/GsCursedFlames.cs:273 — Content/GameModes/GodSmith/Weapons/MagicChant/GsCursedFlames.cs:273-284 | Content/GameModes/GodSmith/Weapons/MagicChant/GsGoldenShower.cs:242-253 | Content/GameModes/GodSmith/Weapons/MagicChant/GsNettleBurst.cs:160-171 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (12 lines × 3) Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:265 — Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:265-276 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaShrimpWaterBolt.cs:54-66 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpWaterBolt.cs:55-66 — before extracting anything, compare `Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs` and `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpWaterBolt.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 116 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:265` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (12 lines × 3) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:49 — Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:49-60 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainRender.cs:169-182 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspaceRender.cs:122-134 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:49` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangProj.cs:228 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangProj.cs:228-239 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailHead.cs:242-253 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoProj.cs:257-268 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangProj.cs:228` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (12 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistIceShard.cs:161 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistIceShard.cs:161-173 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressPetal.cs:166-177 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsPulseShot.cs:157-169 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistIceShard.cs:161` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (12 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:936 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:936-948 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:890-901 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:965-977 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:936` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (12 lines × 3) Content/Scenarios/Dungeonworld/NPCs/Elites/BoneStitcher.cs:81 — Content/Scenarios/Dungeonworld/NPCs/Elites/BoneStitcher.cs:81-92 | Content/Scenarios/Dungeonworld/NPCs/Elites/BoneStitcher.cs:783-794 | Content/Scenarios/Dungeonworld/NPCs/Elites/LanternWarden.cs:98-109 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/NPCs/Elites/BoneStitcher.cs:81` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 3) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs:214 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs:214-225 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeHeatRay.cs:198-209 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeSkullBeamProj.cs:209-220 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs` and `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeHeatRay.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • + 4 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (5 lines × 5) · ×29
  • Duplicated block (5 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:394 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:394-398 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:387-391 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:497-501 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:503-507 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:481-485 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:394` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:502` calls `RebuildArms` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:399` does not — after which the two agree again for 4 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 (5 lines × 5) Content/Items/Melee/OniMachete.cs:451 — Content/Items/Melee/OniMachete.cs:451-455 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSlashRenderer.cs:431-435 | Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilateRenderer.cs:105-109 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleCut.cs:585-589 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleRenderer.cs:317-321 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/OniMachete.cs:451` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 5) Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:305 — Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:305-309 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpCavitationBubble.cs:101-105 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpSparkBubble.cs:171-175 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpVoltBubble.cs:155-159 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpWaterBolt.cs:93-97 — before extracting anything, compare `Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs` and `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpWaterBolt.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 116 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:305` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (5 lines × 5) Content/Items/Melee/CursedflameBloodfists/CursedflameFistProj.cs:175 — Content/Items/Melee/CursedflameBloodfists/CursedflameFistProj.cs:175-179 | Content/Items/Melee/StormGoddessSpears/AncientStormGoddessSpear.cs:302-306 | Content/Items/Melee/StormGoddessSpears/AncientStormGoddessSpear.cs:467-471 | Content/Items/Ranged/NeutronBows/EXNeutronArrow.cs:66-70 | Content/Items/Summon/WhiplashGalactica.cs:222-226 — before extracting anything, compare `Content/Items/Melee/StormGoddessSpears/AncientStormGoddessSpear.cs` and `Content/Items/Ranged/NeutronBows/EXNeutronArrow.cs` 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/CursedflameBloodfists/CursedflameFistProj.cs:175` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Melee/CursedflameBloodfists/CursedflameFistProj.cs:174` calls `SafeNormalize` and `Content/Items/Melee/StormGoddessSpears/AncientStormGoddessSpear.cs:299` 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 (5 lines × 5) Content/Cyberwares/UIs/CyberwareTheme.cs:76 — Content/Cyberwares/UIs/CyberwareTheme.cs:76-81 | Content/HackTimes/HackRamRenderer.cs:558-563 | Content/Items/Magic/Pandemoniums/PandemoniumChannel.cs:885-889 | Content/Items/Magic/Pandemoniums/PandemoniumCircle.cs:366-371 | Content/Items/Magic/Pandemoniums/PandemoniumRSkill.cs:517-522 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Cyberwares/UIs/CyberwareTheme.cs:76` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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 (5 lines × 5) Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs:76 — Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs:76-80 | Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgSnowShardProj.cs:78-82 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmNutShellProj.cs:97-101 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmPoseTelegraphProj.cs:147-151 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmSnowballProj.cs:108-112 — before extracting anything, compare `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs` and `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgSnowShardProj.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 51 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. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs:82` calls `Lerp`, `Color` and `Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmNutShellProj.cs:105` does not — after which the two agree again for 3 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 (5 lines × 5) Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhImpFireBolt.cs:65 — Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhImpFireBolt.cs:65-69 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhTridentBolt.cs:65-69 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkEmberSeedProj.cs:82-86 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkMortarShellProj.cs:84-88 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeSeekerMissile.cs:152-156 — before extracting anything, compare `Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhImpFireBolt.cs` and `Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhTridentBolt.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 79 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkEmberSeedProj.cs:81` calls `PlaySound` and `Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhImpFireBolt.cs:64` does not — after which the two agree again for 3 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 (5 lines × 5) Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhImpFireBolt.cs:90 — Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhImpFireBolt.cs:90-94 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhScytheBolt.cs:91-95 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhStingerBolt.cs:91-96 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhTridentBolt.cs:90-94 | Content/GameModes/BrutalMobs/Sky/Projectiles/SkyFeatherBolt.cs:84-89 — before extracting anything, compare `Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhImpFireBolt.cs` and `Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhScytheBolt.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 59 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhImpFireBolt.cs:90` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (5 lines × 5) Content/GameModes/GodSmith/Weapons/MagicCataclysm/GsBetsysWrath.cs:63 — Content/GameModes/GodSmith/Weapons/MagicCataclysm/GsBetsysWrath.cs:63-67 | Content/GameModes/GodSmith/Weapons/MagicCataclysm/GsBlizzardStaff.cs:64-68 | Content/GameModes/GodSmith/Weapons/MagicCataclysm/GsNebulaBlaze.cs:56-60 | Content/GameModes/GodSmith/Weapons/MagicCataclysm/GsResonanceScepter.cs:63-67 | Content/GameModes/GodSmith/Weapons/MagicCataclysm/GsStellarTune.cs:73-77 — 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 5 call sites, so a change lands once. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/GodSmith/Weapons/MagicCataclysm/GsBlizzardStaff.cs:63` calls `IsOwnedByLocalPlayer` and `Content/GameModes/GodSmith/Weapons/MagicCataclysm/GsBetsysWrath.cs:61` 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 (5 lines × 5) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:221 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:221-225 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs:243-247 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs:229-233 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:200-204 | Content/Industrials/ElectricPowers/Sensors/SensorUI.cs:184-188 — before extracting anything, compare `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs` and `Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 188 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:221` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs:248` calls `Rectangle` and `Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:205` 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 (5 lines × 5) Content/Items/Accessories/BrutalRelics/BrainOfCthulhu/MirrorheartRender.cs:130 — Content/Items/Accessories/BrutalRelics/BrainOfCthulhu/MirrorheartRender.cs:130-135 | Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Projectiles/BrainTeleportRift.cs:118-124 | Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Rendering/BrainRenderHelper.cs:56-62 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordBlackHoleProj.cs:805-809 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordUltArms.cs:489-494 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.
  • Duplicated block (5 lines × 5) Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:313 — Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:313-317 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenGaleFieldProj.cs:108-112 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenPrismBeamProj.cs:277-281 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofRetinaScanBeam.cs:224-228 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofRotBeamProj.cs:154-158 — before extracting anything, compare `Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs` and `Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenGaleFieldProj.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 5) Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaBurst.cs:341 — Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaBurst.cs:341-345 | Content/Items/Melee/GeminisTribute.cs:507-513 | Content/Items/Melee/GeminisTribute.cs:737-743 | Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraPetalWave.cs:136-141 | Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraSporeCloud.cs:103-108 — there are 5 copies across 4 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 (5 lines × 5) Content/LegendWeapon/HalibutLegend/FishSkills/FishBoneParticles.cs:44 — Content/LegendWeapon/HalibutLegend/FishSkills/FishBoneParticles.cs:44-49 | Content/LegendWeapon/HalibutLegend/FishSkills/FishTunabeardVFX.cs:369-373 | Content/LegendWeapon/HalibutLegend/FishSkills/FishotroningVFX.cs:40-45 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistParticles.cs:155-159 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistParticles.cs:403-407 — there are 5 copies across 4 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishBoneParticles.cs:44` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1249 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1249-1253 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1270-1274 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1603-1607 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:1030-1034 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1637-1641 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs` as WHOLE FILES: this scan already matched 55 separate duplicated blocks between them, totalling at least 611 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1249` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:842 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:842-846 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:902-907 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:569-575 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:471-476 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:431-436 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs` as WHOLE FILES: this scan already matched 44 separate duplicated blocks between them, totalling at least 499 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:842` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (5 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:966 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:966-970 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:1137-1141 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1353-1357 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:964-968 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:1493-1497 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.
  • Duplicated block (5 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:753 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:753-757 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1012-1016 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:738-742 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeStinger.cs:174-178 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:616-620 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:753` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:735` calls `Configure` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:749` 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 (5 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:336 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:336-341 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:291-295 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:458-462 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:337-341 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:402-407 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:336` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:333` calls `AngleLerp` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:287` does not — after which the two agree again for 3 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 (5 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressLance.cs:233 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressLance.cs:233-237 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:141-145 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeMortar.cs:96-100 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeBloodBee.cs:146-150 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeStinger.cs:193-197 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressLance.cs:233` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:656 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:656-660 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:999-1003 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1401-1405 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1001-1005 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1736-1740 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 491 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (5 lines × 5) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCategorySidebar.cs:68 — Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCategorySidebar.cs:68-72 | Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:220-224 | Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingUI.cs:310-314 | Content/LegendWeapon/SHPCLegend/UI/SHPCModPanel.cs:300-306 | Content/LegendWeapon/SHPCLegend/UI/SHPCModPanel.cs:537-543 — there are 5 copies across 4 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. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/SHPCLegend/UI/SHPCModPanel.cs:545` calls `Color` and `Content/LegendWeapon/SHPCLegend/UI/SHPCModPanel.cs:307` 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 (5 lines × 5) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:270 — Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:270-274 | Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingPanel.cs:411-415 | Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingPanel.cs:516-520 | Content/LegendWeapon/SHPCLegend/UI/SHPCModPanel.cs:449-453 | Content/LegendWeapon/SHPCLegend/UI/SHPCModuleSelectPanel.cs:319-323 — there are 5 copies across 4 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:270` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (5 lines × 5) Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2EscapeTunnel.cs:451 — Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2EscapeTunnel.cs:451-455 | Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2Preview.cs:22-28 | Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Leviathan.cs:546-550 | Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Preview.cs:23-27 | Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Preview.cs:22-27 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2EscapeTunnel.cs:451` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Preview.cs:22` calls `Reset` and `Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2EscapeTunnel.cs:451` does not — after which the two agree again for 4 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 (5 lines × 5) Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:190 — Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:190-194 | Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:209-213 | Content/Scenarios/Kiame/Overlay/OniRainExitTransition.cs:147-151 | Content/Scenarios/Kiame/Overlay/OniRainExitTransition.cs:166-170 | Content/Scenarios/Kiame/Overlay/OniRainWorldTransition.cs:228-232 — before extracting anything, compare `Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs` and `Content/Scenarios/Kiame/Overlay/OniRainExitTransition.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 186 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:190` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • + 4 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (7–8 lines × 2) · ×29
  • Duplicated block (7–8 lines × 2) Content/Cyberwares/Implementation/OmniElectricFoots/OmniElectricFoot.cs:78 — Content/Cyberwares/Implementation/OmniElectricFoots/OmniElectricFoot.cs:78-85 | Content/Cyberwares/Implementation/SelfHackCrystals/SelfHackCrystal.cs:58-64 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (7–8 lines × 2) Content/HackTimes/Protocols/StressInvert.cs:200 — Content/HackTimes/Protocols/StressInvert.cs:200-207 | Content/HackTimes/Protocols/StressInvert.cs:238-244 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/HackTimes/Protocols/StressInvert.cs:200` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (7–8 lines × 2) Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:393 — Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:393-399 | Content/LegendWeapon/SHPCLegend/Modules/Grip/ConductorGripModule.cs:55-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:393` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (7–8 lines × 2) Content/Items/Accessories/BrutalRelics/EmpressOfLight/InterferenceBursts.cs:68 — Content/Items/Accessories/BrutalRelics/EmpressOfLight/InterferenceBursts.cs:68-75 | Content/Items/Accessories/BrutalRelics/EmpressOfLight/InterferenceBursts.cs:174-180 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7–8 lines × 2) Content/Items/Magic/Elysiums/ElysiumThunder.cs:65 — Content/Items/Magic/Elysiums/ElysiumThunder.cs:65-72 | Content/Items/Magic/Elysiums/Revelations/ApocalypseHorseman.cs:65-71 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/Elysiums/ElysiumThunder.cs:65` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (7–8 lines × 2) Content/Items/Stones/Granites/GraniteFlower.cs:218 — Content/Items/Stones/Granites/GraniteFlower.cs:218-224 | Content/Items/Stones/Granites/GraniteTome.cs:421-428 — 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. 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 (7–8 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:540 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:540-547 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:873-879 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:540` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (7–8 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:938 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:938-944 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:969-976 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:938` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (7–8 lines × 2) Content/LegendWeapon/KikasaLegend/UI/Panorama/KikasaPanoramaUI.cs:1650 — Content/LegendWeapon/KikasaLegend/UI/Panorama/KikasaPanoramaUI.cs:1650-1657 | Content/LegendWeapon/KikasaLegend/UI/Panorama/KikasaPanoramaUI.cs:1665-1671 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/UI/Panorama/KikasaPanoramaUI.cs:1650` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (7–8 lines × 2) Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilateRenderer.cs:78 — Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilateRenderer.cs:78-85 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleRenderer.cs:289-295 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilateRenderer.cs` and `Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleRenderer.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note first that the copies are not typed on the same thing: the declarations holding them bind `d` to `in OFR.BladeDef` in one and `in BladeDef` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (7–8 lines × 2) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspacePlayer.cs:497 — Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspacePlayer.cs:497-504 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspacePlayer.cs:775-781 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspacePlayer.cs:497` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7–8 lines × 2) Content/LegendWeapon/SHPCLegend/Modules/Barrel/ForkBarrelModule.cs:30 — Content/LegendWeapon/SHPCLegend/Modules/Barrel/ForkBarrelModule.cs:30-37 | Content/LegendWeapon/SHPCLegend/Modules/Frame/HarmonicFrameModule.cs:34-40 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/Modules/Barrel/ForkBarrelModule.cs:30` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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 (7–8 lines × 2) Content/LegendWeapon/SHPCLegend/Modules/Grip/VampireGripModule.cs:17 — Content/LegendWeapon/SHPCLegend/Modules/Grip/VampireGripModule.cs:17-24 | Content/LegendWeapon/SHPCLegend/Modules/Grip/VampireGripModule.cs:27-33 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/Modules/Grip/VampireGripModule.cs:17` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7–8 lines × 2) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:366 — Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:366-372 | Content/LegendWeapon/SHPCLegend/UI/SHPCModPanel.cs:425-432 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:366` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (7–8 lines × 2) Content/NPCs/BloomsandSerpents/BssPortrait.cs:131 — Content/NPCs/BloomsandSerpents/BssPortrait.cs:131-138 | Content/NPCs/FestersandSerpents/Rendering/FssPortrait.cs:189-195 — before extracting anything, compare `Content/NPCs/BloomsandSerpents/BssPortrait.cs` and `Content/NPCs/FestersandSerpents/Rendering/FssPortrait.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 108 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BloomsandSerpents/BssPortrait.cs:131` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (7–8 lines × 2) Content/NPCs/BloomsandSerpents/Projectiles/BssBreachOmen.cs:55 — Content/NPCs/BloomsandSerpents/Projectiles/BssBreachOmen.cs:55-62 | Content/NPCs/BloomsandSerpents/States/BssSandSurgeState.cs:138-144 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BloomsandSerpents/Projectiles/BssBreachOmen.cs:55` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (7–8 lines × 2) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Projectiles/BrainBloodShard.cs:89 — Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Projectiles/BrainBloodShard.cs:89-96 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerBolt.cs:74-80 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Projectiles/BrainBloodShard.cs:89` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (7–8 lines × 2) Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerStrikeTelegraph.cs:76 — Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerStrikeTelegraph.cs:76-83 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Projectiles/QueenBeeTelegraphLine.cs:71-77 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerStrikeTelegraph.cs` and `Content/NPCs/BrutalNPCs/BrutalQueenBee/Projectiles/QueenBeeTelegraphLine.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 128 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerStrikeTelegraph.cs:76` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7–8 lines × 2) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowBreachOmen.cs:91 — Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowBreachOmen.cs:91-98 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowDevourOmen.cs:126-132 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowBreachOmen.cs` and `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowDevourOmen.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 47 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 (7–8 lines × 2) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistArcanePulse.cs:118 — Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistArcanePulse.cs:118-124 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistGoldRingSeal.cs:204-211 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistArcanePulse.cs:118` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (7–8 lines × 2) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerVerticalBarrageState.cs:122 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerVerticalBarrageState.cs:122-128 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismHoverShootState.cs:79-86 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerVerticalBarrageState.cs:122` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7–8 lines × 2) Content/NPCs/TBUGs/TBUGShopNet.cs:319 — Content/NPCs/TBUGs/TBUGShopNet.cs:319-326 | Content/NPCs/TBUGs/TBUGStock.cs:203-209 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/TBUGs/TBUGShopNet.cs:319` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7–8 lines × 2) Content/QuestLogs/Styles/ForestQuestLogStyle.cs:339 — Content/QuestLogs/Styles/ForestQuestLogStyle.cs:339-345 | Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:334-341 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/QuestLogs/Styles/ForestQuestLogStyle.cs:339` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (7–8 lines × 2) Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Palette.cs:235 — Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Palette.cs:235-242 | Content/Scenarios/Dungeonworld/Gen/Layers/L7/L7Style.cs:303-309 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Palette.cs:235` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (7–8 lines × 2) Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:1018 — Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:1018-1025 | Content/Scenarios/Dungeonworld/NPCs/OverseerPressStrike.cs:137-143 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:1018` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
  • + 4 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (8–9 lines × 2) · ×28
  • Duplicated block (8–9 lines × 2) Content/GameModes/BrutalMobs/Ambience/Hollowdeep/HollowdeepPRT.cs:42 — Content/GameModes/BrutalMobs/Ambience/Hollowdeep/HollowdeepPRT.cs:42-49 | Content/GameModes/BrutalMobs/Ambience/Hollowdeep/HollowdeepPRT.cs:98-106 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/Hollowdeep/HollowdeepPRT.cs:42` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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–9 lines × 2) Content/GameModes/GodSmith/Weapons/Spears/GsNorthPole.cs:202 — Content/GameModes/GodSmith/Weapons/Spears/GsNorthPole.cs:202-210 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Projectiles/EmpressMoonShard.cs:80-87 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/Spears/GsNorthPole.cs:202` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/GodSmith/Weapons/Spears/GsNorthPole.cs:199` calls `OnHitNPC`, `AddBuff` and `Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Projectiles/EmpressMoonShard.cs:78` 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–9 lines × 2) Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawCorrosionNPC.cs:238 — Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawCorrosionNPC.cs:238-246 | Content/Scenarios/Dungeonworld/NPCs/Elites/DrownedTurnkey.cs:784-791 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/NPCs/Elites/DrownedTurnkey.cs:784` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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–9 lines × 2) Content/Items/Melee/DestroyersBladeEXs/DestroyerBiteProj.cs:278 — Content/Items/Melee/DestroyersBladeEXs/DestroyerBiteProj.cs:278-286 | Content/Items/Melee/DestroyersBladeEXs/DestroyerHeadMissile.cs:124-131 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DestroyersBladeEXs/DestroyerBiteProj.cs:278` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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–9 lines × 2) Content/Items/Melee/TideReapers/TideReaper.cs:294 — Content/Items/Melee/TideReapers/TideReaper.cs:294-302 | Content/Items/Melee/TideReapers/TideReaperWave.cs:99-106 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/TideReapers/TideReaper.cs:294` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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–9 lines × 2) Content/Items/Ranged/BloodshotBombs/BloodshotBombHeld.cs:208 — Content/Items/Ranged/BloodshotBombs/BloodshotBombHeld.cs:208-216 | Content/Items/Ranged/BloodshotBombs/BloodshotBombThrown.cs:200-207 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Ranged/BloodshotBombs/BloodshotBombHeld.cs:208` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8–9 lines × 2) Content/Items/Ranged/CrystalDimming.cs:204 — Content/Items/Ranged/CrystalDimming.cs:204-212 | Content/Items/Ranged/SnowQuayMK2.cs:243-250 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Ranged/CrystalDimming.cs:204` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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–9 lines × 2) Content/Items/Ranged/RaiderGun.cs:214 — Content/Items/Ranged/RaiderGun.cs:214-221 | Content/Items/Ranged/RaiderGun.cs:320-328 — 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–9 lines × 2) Content/Items/Summon/EyekiteStaffs/EyekiteVFX.cs:136 — Content/Items/Summon/EyekiteStaffs/EyekiteVFX.cs:136-143 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Rendering/EocRenderHelper.cs:188-196 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Summon/EyekiteStaffs/EyekiteVFX.cs:136` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8–9 lines × 2) Content/LegendWeapon/HalibutLegend/FishSkills/FishCrimsonTiger.cs:657 — Content/LegendWeapon/HalibutLegend/FishSkills/FishCrimsonTiger.cs:657-664 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCrimsonTiger.cs:684-692 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishCrimsonTiger.cs:657` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8–9 lines × 2) Content/LegendWeapon/HalibutLegend/FishSkills/FishTropicalBarracudaVFX.cs:346 — Content/LegendWeapon/HalibutLegend/FishSkills/FishTropicalBarracudaVFX.cs:346-353 | Content/PRTTypes/PRT_PallbearerTracer.cs:53-61 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (8–9 lines × 2) Content/LegendWeapon/HalibutLegend/UI/HalibutHudLead.cs:49 — Content/LegendWeapon/HalibutLegend/UI/HalibutHudLead.cs:49-57 | Content/LegendWeapon/OnikiriLegend/Tutorial/OnikiriTutorialLead.cs:29-36 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (8–9 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamHound.cs:289 — Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamHound.cs:289-297 | Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamHound.cs:708-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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamHound.cs:289` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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–9 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:439 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:439-446 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:348-356 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:439` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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–9 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:701 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:701-709 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:694-701 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:701` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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–9 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressPetal.cs:281 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressPetal.cs:281-288 | Content/PRTTypes/PRT_KikasaInkBead.cs:68-76 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressPetal.cs:281` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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–9 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:438 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:438-446 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:667-674 — 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–9 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuMeiFX.cs:38 — Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuMeiFX.cs:38-46 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuXiaFX.cs:52-59 — 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 (8–9 lines × 2) Content/MainMenus/Shenyo/ShenyoGhostLakeScene.cs:494 — Content/MainMenus/Shenyo/ShenyoGhostLakeScene.cs:494-501 | Content/MainMenus/Shenyo/ShenyoGhostLakeScene.cs:563-571 — 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–9 lines × 2) Content/NPCs/BloomsandSerpents/Projectiles/BssPetalProj.cs:90 — Content/NPCs/BloomsandSerpents/Projectiles/BssPetalProj.cs:90-98 | Content/NPCs/BloomsandSerpents/Projectiles/BssWindPetalProj.cs:109-116 — before extracting anything, compare `Content/NPCs/BloomsandSerpents/Projectiles/BssPetalProj.cs` and `Content/NPCs/BloomsandSerpents/Projectiles/BssWindPetalProj.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 89 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BloomsandSerpents/Projectiles/BssPetalProj.cs:90` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (8–9 lines × 2) Content/NPCs/BloomsandSerpents/States/BssApexBloomState.cs:49 — Content/NPCs/BloomsandSerpents/States/BssApexBloomState.cs:49-56 | Content/NPCs/BloomsandSerpents/States/BssStormTransitionState.cs:92-100 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BloomsandSerpents/States/BssApexBloomState.cs:49` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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–9 lines × 2) Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerCoilRingProj.cs:110 — Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerCoilRingProj.cs:110-118 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerCoilRingProj.cs:143-150 — 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–9 lines × 2) Content/NPCs/BrutalNPCs/BrutalGolem/Rendering/GolemRenderHelper.cs:51 — Content/NPCs/BrutalNPCs/BrutalGolem/Rendering/GolemRenderHelper.cs:51-59 | Content/NPCs/BrutalNPCs/BrutalGolem/Rendering/GolemRenderHelper.cs:123-130 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalGolem/Rendering/GolemRenderHelper.cs:51` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8–9 lines × 2) Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSGelGlobProj.cs:76 — Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSGelGlobProj.cs:76-84 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSMassGlobProj.cs:184-191 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSGelGlobProj.cs:76` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSMassGlobProj.cs:192` calls `ToRotation` and `Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSGelGlobProj.cs:87` 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–9 lines × 2) Content/Scenarios/Dungeonworld/Gen/Passes/MacroRoutePass.cs:65 — Content/Scenarios/Dungeonworld/Gen/Passes/MacroRoutePass.cs:65-72 | Content/Scenarios/Dungeonworld/Gen/Passes/MacroRoutePass.cs:95-103 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/Gen/Passes/MacroRoutePass.cs:65` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • + 3 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (30 corresponding lines) · ×26
  • Edited copy of a member (30 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishHungerVFX.cs:84 — Content/LegendWeapon/HalibutLegend/FishSkills/FishHungerVFX.cs:84-113 | Content/LegendWeapon/HalibutLegend/FishSkills/FishTropicalBarracudaVFX.cs:103-133 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemSunBolt.cs:71 — Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemSunBolt.cs:71-106 | Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemSunMortar.cs:102-131 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronCursedSkull.cs:112 — Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronCursedSkull.cs:112-146 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronOrbitSkull.cs:154-183 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsDeathState.cs:160 — Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsDeathState.cs:160-196 | Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsEyeGrabState.cs:223-252 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunBullet.cs:230 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunBullet.cs:230-259 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:213-242 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) Content/Items/Melee/DivineSourceBlades/DivineSourceWaveProjectile.cs:195 — Content/Items/Melee/DivineSourceBlades/DivineSourceWaveProjectile.cs:195-225 | Content/Items/Melee/NeutronGlaive.cs:891-920 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) Content/Items/Modifys/RBloodButcherer.cs:987 — Content/Items/Modifys/RBloodButcherer.cs:987-1016 | Content/LegendWeapon/HalibutLegend/FishSkills/FishIchornVFX.cs:43-72 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) Content/Scenarios/Kiyume/NPCs/LanternGuideYokai.cs:625 — Content/Scenarios/Kiyume/NPCs/LanternGuideYokai.cs:625-656 | Content/Scenarios/Kiyume/NPCs/LanternGuideYokai.cs:727-756 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuJiFX.cs:20 — Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuJiFX.cs:20-50 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuMeiFX.cs:64-93 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPuddle.cs:203 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPuddle.cs:203-233 | Content/LegendWeapon/KikasaLegend/KikasaTeleports/KikasaTeleportProj.cs:496-525 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) Content/Scenarios/OldNet/Tiles/OldNetDataNodeTile.cs:45 — Content/Scenarios/OldNet/Tiles/OldNetDataNodeTile.cs:45-74 | Content/Scenarios/OldNet/Tiles/OldNetEchoNodeTile.cs:49-86 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) Content/Narrative/Presentation/Skins/Kikasa/KikasaDialogueSkin.cs:92 — Content/Narrative/Presentation/Skins/Kikasa/KikasaDialogueSkin.cs:92-121 | Content/Narrative/Presentation/Skins/Onikiri/OnikiriDialogueSkin.cs:92-121 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSim.cs:233 — Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSim.cs:233-262 | Content/Scenarios/Kiyume/Fog/KiyumeFogSim.cs:354-385 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) Content/LegendWeapon/HalibutLegend/UI/HalibutPilotChart.cs:170 — Content/LegendWeapon/HalibutLegend/UI/HalibutPilotChart.cs:170-203 | Content/LegendWeapon/OnikiriLegend/Tutorial/OniKeikoRune.cs:164-193 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/SHPCModuleRender.cs:60 — Content/LegendWeapon/SHPCLegend/Modules/SHPCModuleRender.cs:60-89 | Content/LegendWeapon/SHPCLegend/UI/SHPCModuleSelectPanel.cs:299-330 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) Content/GameModes/GodSmith/Weapons/Flamethrowers/FlamethrowersShared.cs:133 — Content/GameModes/GodSmith/Weapons/Flamethrowers/FlamethrowersShared.cs:133-167 | Content/GameModes/GodSmith/Weapons/Specials/GsChainGun.cs:205-234 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawCorrosionNPC.cs:338 — Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawCorrosionNPC.cs:338-367 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/KikasaTalismanStackNPC.cs:190-219 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:441 — Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:441-471 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:473-502 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) Content/GameModes/GodSmith/Weapons/Guns/GsBlowpipe.cs:57 — Content/GameModes/GodSmith/Weapons/Guns/GsBlowpipe.cs:57-86 | Content/GameModes/GodSmith/Weapons/Guns/GsPewMaticHorn.cs:79-112 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs:389 — Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs:389-418 | Content/Items/Melee/WeaverGrievanceses/WGManifestationNet.cs:390-419 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) Content/Items/Melee/NeutronGlaive.cs:355 — Content/Items/Melee/NeutronGlaive.cs:355-385 | Content/Items/Modifys/RBloodButcherer.cs:406-435 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs:357 — Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs:357-386 | Content/Items/Melee/WeaverGrievanceses/WGManifestationNet.cs:358-387 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) Content/GameModes/BrutalMobs/FrostMoon/FrmMeleeNPC.cs:330 — Content/GameModes/BrutalMobs/FrostMoon/FrmMeleeNPC.cs:330-359 | Content/GameModes/BrutalMobs/FrostMoon/FrmMeleeNPC.cs:604-634 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) Content/MainMenus/Himayo/HimayoMenuOverride.cs:128 — Content/MainMenus/Himayo/HimayoMenuOverride.cs:128-161 | Content/MainMenus/Shenyo/ShenyoMenuOverride.cs:97-126 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocFeintDashState.cs:71 — Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocFeintDashState.cs:71-100 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocServantEncircleState.cs:56-85 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • + 1 more in this group — see findings.md.
D4 · Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) · ×26
  • Edited copies of one member (3 members, 6+ corresponding lines) Content/EntrustManager/BaseManagerStyle.cs:214 — Content/EntrustManager/BaseManagerStyle.cs:214-219 | Content/Narrative/Presentation/Skins/Common/SkinDrawUtil.cs:9-15 | Content/Narrative/Presentation/Skins/Draedon/DraedonPanelDraw.cs:281-286 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) Content/Industrials/UIs/IndustrialTerminalRenderer.cs:101 — Content/Industrials/UIs/IndustrialTerminalRenderer.cs:101-107 | Content/Industrials/UIs/IndustrialTerminalRenderer.cs:404-412 | Content/Industrials/UIs/IndustrialTerminalRenderer.cs:417-422 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) Content/Scenarios/Shenyo/Gifts/ShenyoEmpressGift.cs:26 — Content/Scenarios/Shenyo/Gifts/ShenyoEmpressGift.cs:26-31 | Content/Scenarios/Shenyo/Gifts/ShenyoFesterSerpentGift.cs:26-31 | Content/Scenarios/Shenyo/Gifts/ShenyoYharonGift.cs:26-31 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) Content/EntrustManager/Styles/DraedonManagerStyle.cs:714 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:714-719 | Content/EntrustManager/Styles/ForestManagerStyle.cs:784-789 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:779-784 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) Content/Scenarios/SupCal/Quest/DoGQuest/DoGQuestUI.cs:16 — Content/Scenarios/SupCal/Quest/DoGQuest/DoGQuestUI.cs:16-21 | Content/Scenarios/SupCal/Quest/PallbearerQuest/PallbearerQuestUI.cs:16-21 | Content/Scenarios/SupCal/Quest/YharonQuest/YharonQuestUI.cs:16-21 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:977 — Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:977-983 | Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:1008-1013 | Content/Narrative/MusicToast.cs:866-872 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:272 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:272-277 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterPool.cs:42-47 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronBloodnado.cs:136-141 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdRocketProj.cs:59 — Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdRocketProj.cs:59-67 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:354-359 | Content/LegendWeapon/OnikiriLegend/OniDismembers/OniSeverStrike.cs:1239-1244 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) Content/Items/Melee/BudPiercers/BudPiercer.cs:199 — Content/Items/Melee/BudPiercers/BudPiercer.cs:199-204 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/Fireball.cs:56-62 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/RocketSkeleton.cs:69-74 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) Content/Items/Ranged/AnnihilatingUniverses/AnnihilatingUniverseHeldProj.cs:93 — Content/Items/Ranged/AnnihilatingUniverses/AnnihilatingUniverseHeldProj.cs:93-105 | Content/Items/Ranged/AnnihilatingUniverses/AnnihilatingUniverseHeldProj.cs:107-120 | Content/Items/Ranged/NeutronBows/EXNeutronArrow.cs:92-97 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSGeyserProj.cs:117 — Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSGeyserProj.cs:117-127 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronBoneSpike.cs:98-103 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpCrystalSpike.cs:106-114 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:288 — Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:288-293 | Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:263-269 | Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:309-314 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawCorrosionNPC.cs:283 — Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawCorrosionNPC.cs:283-290 | Content/Scenarios/Dungeonworld/NPCs/Elites/BoneStitcherRendering.cs:160-165 | Content/Scenarios/Dungeonworld/NPCs/OverseerVfx.cs:74-82 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishBatVFX.cs:365 — Content/LegendWeapon/HalibutLegend/FishSkills/FishBatVFX.cs:365-370 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCatVFX.cs:343-348 | Content/LegendWeapon/HalibutLegend/FishSkills/FishWyverntailVFX.cs:75-80 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) Content/GameModes/GodSmith/Weapons/Broadswords/GsDD2SquireBetsySword.cs:186 — Content/GameModes/GodSmith/Weapons/Broadswords/GsDD2SquireBetsySword.cs:186-191 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:220-225 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistOrreryRingProj.cs:189-197 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) Content/NPCs/BloomsandSerpents/BssBody.cs:38 — Content/NPCs/BloomsandSerpents/BssBody.cs:38-44 | Content/NPCs/BloomsandSerpents/BssTail.cs:13-19 | Content/NPCs/ScrapCommanders/ScrapLegionProbe.cs:35-40 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishDirtParticles.cs:214 — Content/LegendWeapon/HalibutLegend/FishSkills/FishDirtParticles.cs:214-219 | Content/LegendWeapon/HalibutLegend/FishSkills/FishPengVFX.cs:252-257 | Content/LegendWeapon/HalibutLegend/OceanCurrentParticles.cs:487-492 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) Content/Scenarios/Dungeonworld/NPCs/GaolDormantSkull.cs:224 — Content/Scenarios/Dungeonworld/NPCs/GaolDormantSkull.cs:224-229 | Content/Scenarios/Dungeonworld/NPCs/OverseerDormantRig.cs:313-318 | Content/Scenarios/Dungeonworld/NPCs/UndrownedThrone.cs:309-314 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) Content/Items/Summon/BloomCallers/BloomCallerSprout.cs:58 — Content/Items/Summon/BloomCallers/BloomCallerSprout.cs:58-63 | Content/Items/Summon/Deepclaws/DeepclawLobster.cs:73-78 | Content/Items/Summon/EyekiteStaffs/EyekiteMinion.cs:57-62 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashStepHideOverride.cs:12 — Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashStepHideOverride.cs:12-23 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Restart/CyberRestartHideOverride.cs:12-17 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberTeleportHideOverride.cs:12-18 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) Content/LegendWeapon/OnikiriLegend/OniDismembers/OniSeverStrike.cs:1167 — Content/LegendWeapon/OnikiriLegend/OniDismembers/OniSeverStrike.cs:1167-1172 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBossExecution.cs:198-203 | Content/LegendWeapon/SHPCLegend/Cyberspaces/SHPCNPCEffects.Net.cs:194-199 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) Content/HackTimes/CircuitNodes/SignalTowerActor.cs:177 — Content/HackTimes/CircuitNodes/SignalTowerActor.cs:177-183 | Content/HackTimes/HackEffectNPCCombat.cs:65-70 | Content/LegendWeapon/SHPCLegend/Cyberspaces/SHPCNPCEffects.cs:671-677 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) Content/Industrials/ElectricPowers/Spectrometers/Spectrometer.cs:81 — Content/Industrials/ElectricPowers/Spectrometers/Spectrometer.cs:81-86 | Content/Industrials/MaterialFlow/LaserEnergyTrans.cs:92-97 | Content/Industrials/Modifys/ModifyDyeVat.cs:23-28 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsIntroState.cs:109 — Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsIntroState.cs:109-114 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronIntroState.cs:180-185 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowMoltTransitionState.cs:108-114 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) Content/Items/Melee/CosmicCalamity.cs:285 — Content/Items/Melee/CosmicCalamity.cs:285-290 | Content/Items/Melee/DawnshatterAzures/DawnshatterDash.cs:364-369 | Content/Items/Melee/DawnshatterAzures/DawnshatterHeld.cs:945-950 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • + 1 more in this group — see findings.md.
D4 · Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) · ×26
  • Edited copies of one member (3 members, 7+ corresponding lines) Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:571 — Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:571-579 | Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:581-592 | Content/Narrative/Presentation/Skins/Sea/SeaPanelState.cs:164-170 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) Content/Industrials/UIs/IndustrialTerminalRenderer.cs:119 — Content/Industrials/UIs/IndustrialTerminalRenderer.cs:119-126 | Content/Industrials/UIs/IndustrialTerminalRenderer.cs:129-135 | Content/Industrials/UIs/IndustrialTerminalRenderer.cs:312-319 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) Content/GameModes/GodSmith/Weapons/MagicChant/GsCursedFlames.cs:50 — Content/GameModes/GodSmith/Weapons/MagicChant/GsCursedFlames.cs:50-56 | Content/GameModes/GodSmith/Weapons/MagicChant/GsNettleBurst.cs:54-60 | Content/GameModes/GodSmith/Weapons/MagicChant/GsWaspGun.cs:61-68 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuNiFX.cs:135 — Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuNiFX.cs:135-142 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuPeiFX.cs:104-110 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuPoFX.cs:228-235 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) Content/HackTimes/Protocols/BallisticOverclock.cs:81 — Content/HackTimes/Protocols/BallisticOverclock.cs:81-89 | Content/HackTimes/Protocols/FirmwareRollback.cs:125-132 | Content/HackTimes/Protocols/MachineOverclock.cs:143-149 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) Content/Items/Accessories/ArcaneThroneOfEternity.cs:288 — Content/Items/Accessories/ArcaneThroneOfEternity.cs:288-294 | Content/Items/Accessories/ArcaneThroneOfEternity.cs:413-420 | Content/Items/Stones/Marbles/MarbleEffects.cs:115-121 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) Content/HackTimes/Protocols/DataPurge.cs:90 — Content/HackTimes/Protocols/DataPurge.cs:90-97 | Content/HackTimes/Protocols/DelayFuse.cs:239-245 | Content/HackTimes/Protocols/ProjectileSample.cs:102-108 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) Content/Scenarios/Helen/HalibutState.cs:10 — Content/Scenarios/Helen/HalibutState.cs:10-16 | Content/Scenarios/Helen/HalibutState.cs:28-34 | Content/Scenarios/SupCal/End/EternalBlazingNow/EbnState.cs:49-55 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) Content/HackTimes/Protocols/DataLeech.cs:126 — Content/HackTimes/Protocols/DataLeech.cs:126-132 | Content/HackTimes/Protocols/Exorcise.cs:80-87 | Content/HackTimes/Protocols/FirmwareRollback.cs:116-122 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) Content/NPCs/BloomsandSerpents/BssClawRig.cs:361 — Content/NPCs/BloomsandSerpents/BssClawRig.cs:361-367 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordArmIK.cs:267-273 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordArmIK.cs:276-282 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) Content/Scenarios/Shepel/Gifts/ShepelBoCGift.cs:29 — Content/Scenarios/Shepel/Gifts/ShepelBoCGift.cs:29-35 | Content/Scenarios/Shepel/Gifts/ShepelBrimstoneElementalGift.cs:28-34 | Content/Scenarios/Shepel/Gifts/ShepelSkeletronPrimeGift.cs:29-35 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) Content/HackTimes/Scannables/ItemScannable.cs:85 — Content/HackTimes/Scannables/ItemScannable.cs:85-91 | Content/HackTimes/Scannables/NpcScannable.cs:146-152 | Content/HackTimes/Scannables/ProjectileScannable.cs:90-96 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) Content/Items/Accessories/BrutalRelics/EyeOfCthulhu/BloodfogIrisFX.cs:136 — Content/Items/Accessories/BrutalRelics/EyeOfCthulhu/BloodfogIrisFX.cs:136-142 | Content/PRTTypes/PRT_KiyumeFootprint.cs:62-68 | Content/PRTTypes/PRT_ProcRing.cs:51-58 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) Content/GameModes/BrutalMobs/Ambience/Cindercrag/CindercragAmbience.cs:344 — Content/GameModes/BrutalMobs/Ambience/Cindercrag/CindercragAmbience.cs:344-350 | Content/GameModes/BrutalMobs/Ambience/Cindercrag/CindercragGlowRender.cs:232-238 | Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Palette.cs:241-247 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) Content/LegendWeapon/SHPCLegend/Cyberspaces/SHPCNPCEffects.cs:663 — Content/LegendWeapon/SHPCLegend/Cyberspaces/SHPCNPCEffects.cs:663-669 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberTeleport.cs:27-36 | Content/RAMSystems/RamSystem.cs:36-43 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) Content/GameModes/BrutalMobs/Martians/Projectiles/MrtTeslaArcProj.cs:55 — Content/GameModes/BrutalMobs/Martians/Projectiles/MrtTeslaArcProj.cs:55-61 | Content/LegendWeapon/OnikiriLegend/OniOmokages/OniOmokage.cs:892-899 | Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs:1240-1246 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) Content/HackTimes/CircuitNodes/SentryTurretActor.cs:220 — Content/HackTimes/CircuitNodes/SentryTurretActor.cs:220-226 | Content/HackTimes/Protocols/CompensationProtocol.cs:160-167 | Content/HackTimes/Protocols/TurretMesh.cs:247-253 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) Content/GameModes/GodSmith/Weapons/MagicMorph/Projectiles/GsNimbusCorridorProj.cs:117 — Content/GameModes/GodSmith/Weapons/MagicMorph/Projectiles/GsNimbusCorridorProj.cs:117-123 | Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzBeamProj.cs:207-215 | Content/Items/Accessories/BrutalRelics/Twins/TwinPupilTetherBeam.cs:128-135 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) Content/Narrative/Presentation/Skins/SHPC/SHPCPanelState.cs:129 — Content/Narrative/Presentation/Skins/SHPC/SHPCPanelState.cs:129-135 | Content/Narrative/Presentation/Skins/Sea/SeaPanelState.cs:129-135 | Content/Narrative/Presentation/Skins/Sulfsea/SulfseaPanelState.cs:104-110 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsEyeGrabState.cs:109 — Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsEyeGrabState.cs:109-116 | Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsSeizeHuntState.cs:171-178 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/States/WofRotGuillotineState.cs:36-42 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) Content/GameModes/GodSmith/Weapons/Broadswords/GsPiercingStarlight.cs:210 — Content/GameModes/GodSmith/Weapons/Broadswords/GsPiercingStarlight.cs:210-216 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT2.cs:287-293 | Content/GameModes/GodSmith/Weapons/Spears/GsJoustingLances.cs:288-294 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) Content/GameModes/GodSmith/Weapons/MagicCataclysm/GsBatScepter.cs:78 — Content/GameModes/GodSmith/Weapons/MagicCataclysm/GsBatScepter.cs:78-85 | Content/GameModes/GodSmith/Weapons/MagicCataclysm/GsRazorpine.cs:85-92 | Content/GameModes/GodSmith/Weapons/MagicCataclysm/GsSpectreStaff.cs:78-84 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishDynamiteParticles.cs:125 — Content/LegendWeapon/HalibutLegend/FishSkills/FishDynamiteParticles.cs:125-132 | Content/LegendWeapon/HalibutLegend/FishSkills/FishPrismiteVFX.cs:179-186 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistParticles.cs:206-212 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) Content/Scenarios/Dungeonworld/NPCs/Elites/DungeonworldEliteGate.cs:77 — Content/Scenarios/Dungeonworld/NPCs/Elites/DungeonworldEliteGate.cs:77-83 | Content/Scenarios/Kiyume/NPCs/KiyumeHound.cs:816-822 | Content/Scenarios/Kiyume/NPCs/KiyumeYokaiGate.cs:123-129 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) Content/Industrials/ElectricPowers/Crushers/CrusherTP.cs:175 — Content/Industrials/ElectricPowers/Crushers/CrusherTP.cs:175-181 | Content/Industrials/ElectricPowers/Incinerators/IncineratorTP.cs:128-134 | Content/Industrials/ElectricPowers/Recyclers/RecyclerTP.cs:177-183 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • + 1 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (27 corresponding lines) · ×24
  • Edited copy of a member (27 corresponding lines) Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:821 — Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:821-851 | Content/QuestLogs/Styles/ForestQuestLogStyle.cs:570-596 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) Content/EntrustManager/Styles/DraedonManagerStyle.cs:663 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:663-690 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:675-701 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaHandRig.cs:103 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaHandRig.cs:103-129 | Content/Wraiths/Projectiles/GhostHandRig.cs:97-125 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkEmberSeedProj.cs:89 — Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkEmberSeedProj.cs:89-115 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkMortarShellProj.cs:91-117 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1134 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1134-1161 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:952-978 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishTropicalBarracudaVFX.cs:340 — Content/LegendWeapon/HalibutLegend/FishSkills/FishTropicalBarracudaVFX.cs:340-366 | Content/PRTTypes/PRT_PallbearerTracer.cs:47-74 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMirrorPhantom.cs:283 — Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMirrorPhantom.cs:283-310 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerBolt.cs:85-111 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:771 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:771-797 | Content/NPCs/SeaShrimp/Kinematics/ShrimpSkeleton.cs:146-175 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemTelegraph.cs:93 — Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemTelegraph.cs:93-119 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeTelegraphLine.cs:128-154 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) Content/Scenarios/Himayo/HimayoFullBodyPortrait.cs:48 — Content/Scenarios/Himayo/HimayoFullBodyPortrait.cs:48-74 | Content/Scenarios/Shenyo/ShenyoFullBodyPortrait.cs:72-104 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) Content/HackTimes/Targets/ItemTargetType.cs:14 — Content/HackTimes/Targets/ItemTargetType.cs:14-40 | Content/HackTimes/Targets/ProjectileTargetType.cs:14-40 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) Content/LegendWeapon/OnikiriLegend/OniOmokages/OniOmokage.cs:547 — Content/LegendWeapon/OnikiriLegend/OniOmokages/OniOmokage.cs:547-573 | Content/LegendWeapon/OnikiriLegend/OniOmokages/OniOmokage.cs:986-1020 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) Content/GameModes/BrutalMobs/Meteorite/MeteoriteBrutalNPC.cs:241 — Content/GameModes/BrutalMobs/Meteorite/MeteoriteBrutalNPC.cs:241-269 | Content/GameModes/BrutalMobs/Sky/SkyBrutalNPC.cs:342-368 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaScourge.cs:116 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaScourge.cs:116-148 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaScourge.cs:246-272 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) Content/Scenarios/Draedon/Quest/DeploySignaltowers/DeploySignaltowerRender.cs:527 — Content/Scenarios/Draedon/Quest/DeploySignaltowers/DeploySignaltowerRender.cs:527-553 | Content/Scenarios/Draedon/Quest/DeploySignaltowers/DeploySignaltowerRender.cs:883-910 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBanish.Net.cs:212 — Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBanish.Net.cs:212-238 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBossExecution.Net.cs:152-178 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs:328 — Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs:328-354 | Content/Items/Melee/WeaverGrievanceses/WGManifestationNet.cs:329-355 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) Content/Wraiths/Abilities/GhostRainAbility.cs:28 — Content/Wraiths/Abilities/GhostRainAbility.cs:28-54 | Content/Wraiths/Abilities/LanternBoyAbility.cs:32-60 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) Content/Items/Magic/Pandemoniums/PandemoniumChannel.cs:656 — Content/Items/Magic/Pandemoniums/PandemoniumChannel.cs:656-684 | Content/Items/Magic/Pandemoniums/PandemoniumChannel.cs:687-713 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) Content/UIs/RadialWheels/RadialWheelHub.cs:179 — Content/UIs/RadialWheels/RadialWheelHub.cs:179-210 | Content/UIs/RadialWheels/RadialWheelHub.cs:213-239 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBanish.Net.cs:68 — Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBanish.Net.cs:68-94 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.Net.cs:85-119 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) Content/Cyberwares/CyberwareNet.cs:210 — Content/Cyberwares/CyberwareNet.cs:210-236 | Content/NPCs/TBUGs/TBUGShopNet.cs:386-412 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) Content/Scenarios/Kiyume/NPCs/FacelessOneYokai.cs:102 — Content/Scenarios/Kiyume/NPCs/FacelessOneYokai.cs:102-128 | Content/Scenarios/Kiyume/NPCs/MinoFisherYokai.cs:94-120 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:428 — Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:428-454 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:458-487 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (29 corresponding lines) · ×24
  • Edited copy of a member (29 corresponding lines) Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserBoltProj.cs:103 — Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserBoltProj.cs:103-131 | Content/GameModes/BrutalMobs/Martians/Projectiles/MrtScutlixHeavyBolt.cs:86-120 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) Content/Scenarios/SupCal/End/EternalBlazingNow/EbnEffect.cs:371 — Content/Scenarios/SupCal/End/EternalBlazingNow/EbnEffect.cs:371-399 | Content/Scenarios/SupCal/SupCalEffect.cs:193-228 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclEyezorOrbProj.cs:92 — Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclEyezorOrbProj.cs:92-122 | Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclNailheadNailProj.cs:85-113 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSim.cs:266 — Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSim.cs:266-294 | Content/Scenarios/Kiyume/Fog/KiyumeFogSim.cs:389-417 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) Content/LegendWeapon/OnikiriLegend/UI/OniGhostShadowDraw.cs:32 — Content/LegendWeapon/OnikiriLegend/UI/OniGhostShadowDraw.cs:32-60 | Content/LegendWeapon/OnikiriLegend/UI/OniPaperBurnDraw.cs:16-45 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenCrystalSpikeProj.cs:233 — Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenCrystalSpikeProj.cs:233-263 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenGelPearlProj.cs:69-97 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) Content/Scenarios/Dungeonworld/Gen/Layers/L1/L1Rooms.cs:79 — Content/Scenarios/Dungeonworld/Gen/Layers/L1/L1Rooms.cs:79-107 | Content/Scenarios/Dungeonworld/Gen/Layers/L1/L1Rooms.cs:320-349 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) Content/Items/Melee/DawnshatterAzures/DawnshatterDash.cs:405 — Content/Items/Melee/DawnshatterAzures/DawnshatterDash.cs:405-433 | Content/Items/Melee/DawnshatterAzures/DawnshatterDive.cs:390-420 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) Content/Industrials/Generator/WindGriven/WGGMK2Wilderness.cs:94 — Content/Industrials/Generator/WindGriven/WGGMK2Wilderness.cs:94-123 | Content/Industrials/Generator/WindGriven/WGGWilderness.cs:92-120 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordCometProj.cs:117 — Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordCometProj.cs:117-145 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordOrbProj.cs:358-388 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) Content/GameModes/BrutalMobs/Legion/Projectiles/LegionInkOmen.cs:112 — Content/GameModes/BrutalMobs/Legion/Projectiles/LegionInkOmen.cs:112-142 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionScoutOmen.cs:84-112 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) Content/Scenarios/Dungeonworld/Ambience/DungeonworldAmbience.cs:255 — Content/Scenarios/Dungeonworld/Ambience/DungeonworldAmbience.cs:255-283 | Content/Scenarios/Kiyume/Ambience/KiyumeSoundscape.cs:251-287 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:138 — Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:138-172 | Content/Scenarios/Kiame/Overlay/OniRainExitTransition.cs:101-129 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) Content/GameModes/BrutalMobs/Ambience/Rotmire/RotmireVentSystem.cs:152 — Content/GameModes/BrutalMobs/Ambience/Rotmire/RotmireVentSystem.cs:152-180 | Content/GameModes/BrutalMobs/Ambience/Rotmire/RotmireVentSystem.cs:213-241 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemEyeRay.cs:58 — Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemEyeRay.cs:58-90 | Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemGrabRay.cs:74-102 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) Content/NPCs/BrutalNPCs/BrutalSkeletron/States/SkeletronHandCrushState.cs:21 — Content/NPCs/BrutalNPCs/BrutalSkeletron/States/SkeletronHandCrushState.cs:21-50 | Content/NPCs/BrutalNPCs/BrutalSkeletron/States/SkeletronHandCrushState.cs:66-94 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFist.cs:610 — Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFist.cs:610-643 | Content/Items/Accessories/BrutalRelics/MoonLord/BlackFlashSigil.cs:384-412 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) Content/NPCs/BloomsandSerpents/BssHead.cs:489 — Content/NPCs/BloomsandSerpents/BssHead.cs:489-517 | Content/NPCs/FestersandSerpents/FssHead.cs:440-468 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) Content/NPCs/BrutalNPCs/BrutalDestroyer/DestroyerHeadAI.cs:278 — Content/NPCs/BrutalNPCs/BrutalDestroyer/DestroyerHeadAI.cs:278-306 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/DukeFishronAI.cs:295-324 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) Content/Cyberwares/CyberwareNet.cs:404 — Content/Cyberwares/CyberwareNet.cs:404-432 | Content/Cyberwares/CyberwareNet.cs:437-467 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs:70 — Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs:70-98 | Content/Items/Melee/WeaverGrievanceses/WGManifestationNet.cs:71-99 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) Content/Industrials/MaterialFlow/Pipelines/UEPipeline.cs:201 — Content/Industrials/MaterialFlow/Pipelines/UEPipeline.cs:201-229 | Content/Industrials/MaterialFlow/Pipelines/UEPipeline.cs:232-260 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) Content/Wraiths/Projectiles/GhostHandProj.cs:327 — Content/Wraiths/Projectiles/GhostHandProj.cs:327-362 | Content/Wraiths/Projectiles/HeadlessShadeProj.cs:322-350 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:598 — Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:598-626 | Content/Items/Melee/WeaverGrievanceses/WGManifestationActor.cs:493-521 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) · ×23
  • Edited copies of one member (3 members, 14+ corresponding lines) Content/Items/Melee/CommandersClaw.cs:212 — Content/Items/Melee/CommandersClaw.cs:212-225 | Content/Items/Melee/CommandersClaw.cs:227-241 | Content/Items/Melee/CommandersClaw.cs:243-260 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 14+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishTropicalBarracudaVFX.cs:279 — Content/LegendWeapon/HalibutLegend/FishSkills/FishTropicalBarracudaVFX.cs:279-292 | Content/PRTTypes/PRT_CampfireBubble.cs:44-59 | Content/PRTTypes/PRT_KikasaLakeBubble.cs:64-80 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 14+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:700 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:700-713 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:907-922 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:703-716 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 14+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1495 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1495-1508 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1367-1380 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1615-1629 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 14+ corresponding lines) Content/HackTimes/HackRamRenderer.cs:532 — Content/HackTimes/HackRamRenderer.cs:532-546 | Content/LegendWeapon/SHPCLegend/UI/SHPCRenderer.cs:51-65 | Content/MainMenus/Overs/AckRenderer.cs:56-69 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 14+ corresponding lines) Content/GameModes/GodSmith/Weapons/MagicChant/GsBookOfSkulls.cs:79 — Content/GameModes/GodSmith/Weapons/MagicChant/GsBookOfSkulls.cs:79-99 | Content/GameModes/GodSmith/Weapons/MagicChant/GsGemStaves.cs:119-135 | Content/GameModes/GodSmith/Weapons/MagicChant/GsWaterBolt.cs:75-88 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 14+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishJewelVFX.cs:312 — Content/LegendWeapon/HalibutLegend/FishSkills/FishJewelVFX.cs:312-325 | Content/LegendWeapon/HalibutLegend/FishSkills/FishVoodooParticles.cs:134-147 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistParticles.cs:361-374 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 14+ corresponding lines) Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipFrostBloomProj.cs:75 — Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipFrostBloomProj.cs:75-89 | Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipReapProj.cs:70-84 | Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipThornProj.cs:49-62 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 14+ corresponding lines) Content/Items/Magic/Pandemoniums/PandemoniumChannel.cs:460 — Content/Items/Magic/Pandemoniums/PandemoniumChannel.cs:460-474 | Content/Items/Magic/Pandemoniums/PandemoniumCircle.cs:183-197 | Content/Items/Magic/Pandemoniums/PandemoniumRSkill.cs:388-401 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 14+ corresponding lines) Content/GameModes/GodSmith/Weapons/MagicChant/GsGrayZapinator.cs:36 — Content/GameModes/GodSmith/Weapons/MagicChant/GsGrayZapinator.cs:36-49 | Content/GameModes/GodSmith/Weapons/MagicChant/GsSpaceGun.cs:31-44 | Content/GameModes/GodSmith/Weapons/MagicChant/GsWaterBolt.cs:35-49 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 14+ corresponding lines) Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersTP.cs:158 — Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersTP.cs:158-171 | Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersTP.cs:359-375 | Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersVortexEffect.cs:148-164 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 14+ corresponding lines) Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclEyezorOrbProj.cs:77 — Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclEyezorOrbProj.cs:77-90 | Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclManFlyFlaskProj.cs:139-153 | Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclNailheadNailProj.cs:70-83 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 14+ corresponding lines) Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT1.cs:152 — Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT1.cs:152-165 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT3.cs:80-93 | Content/GameModes/GodSmith/Weapons/Spears/GsJoustingLances.cs:129-142 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 14+ corresponding lines) Content/NPCs/BloomsandSerpents/States/BssPounceState.cs:252 — Content/NPCs/BloomsandSerpents/States/BssPounceState.cs:252-270 | Content/NPCs/BloomsandSerpents/States/BssQuicksandState.cs:270-283 | Content/NPCs/BloomsandSerpents/States/BssWindBladeState.cs:250-263 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 14+ corresponding lines) Content/Items/Melee/Arbiters/Arbiter.cs:317 — Content/Items/Melee/Arbiters/Arbiter.cs:317-333 | Content/Items/Stones/Marbles/MarbleClub.cs:525-540 | Content/Items/Stones/Marbles/MarbleHuntingKnife.cs:346-359 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 14+ corresponding lines) Content/NPCs/BloomsandSerpents/BssBloomBud.cs:41 — Content/NPCs/BloomsandSerpents/BssBloomBud.cs:41-55 | Content/NPCs/FestersandSerpents/FssFesterBud.cs:41-55 | Content/NPCs/ScrapCommanders/ScrapBeacon.cs:39-52 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 14+ corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1345 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1345-1358 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1060-1073 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1252-1265 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 14+ corresponding lines) Content/Items/Melee/DawnshatterAzures/DawnshatterDash.cs:62 — Content/Items/Melee/DawnshatterAzures/DawnshatterDash.cs:62-76 | Content/Items/Melee/DawnshatterAzures/DawnshatterDive.cs:67-81 | Content/Items/Melee/StormGoddessSpears/AncientStormGoddessSpear.cs:85-98 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 14+ corresponding lines) Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsOpticCrossrayProj.cs:47 — Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsOpticCrossrayProj.cs:47-62 | Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsPygmyTotemProj.cs:40-57 | Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsStardustDragonRiftProj.cs:62-75 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 14+ corresponding lines) Content/Items/Placeable/StarflowPlatedBlock.cs:28 — Content/Items/Placeable/StarflowPlatedBlock.cs:28-41 | Content/Items/Summon/AzureDragonRage.cs:27-41 | Content/Items/Summon/WhiplashGalactica.cs:33-47 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 14+ corresponding lines) Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineStorageProvider.cs:137 — Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineStorageProvider.cs:137-150 | Content/Industrials/ElectricPowers/Recyclers/RecyclerStorageProvider.cs:144-159 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterStorageProvider.cs:143-156 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 14+ corresponding lines) Content/Items/Ranged/NeutronBows/NeutronBow.cs:176 — Content/Items/Ranged/NeutronBows/NeutronBow.cs:176-189 | Content/Items/Ranged/Thornstrings/ThornstringHeld.cs:99-112 | Content/Items/Ranged/Undertows/UndertowHeld.cs:102-115 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 14+ corresponding lines) Content/Scenarios/Shepel/CybCourses/CybTutorialLead.cs:100 — Content/Scenarios/Shepel/CybCourses/CybTutorialLead.cs:100-114 | Content/Scenarios/Shepel/CybCourses/HackTimeTutorialLead.cs:150-166 | Content/Scenarios/Shepel/CybCourses/WheelTutorialLead.cs:111-124 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×23
  • Duplicated block (18 lines × 2) Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBellWave.cs:219 — Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBellWave.cs:219-236 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiSandGarden.cs:229-246 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBellWave.cs` and `Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiSandGarden.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 97 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBellWave.cs:219` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) Content/HackTimes/Targets/SignalTowerTargetType.cs:25 — Content/HackTimes/Targets/SignalTowerTargetType.cs:25-42 | Content/HackTimes/Targets/TurretTargetType.cs:25-42 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/HackTimes/Targets/SignalTowerTargetType.cs:25` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (18 lines × 2) Content/LegendWeapon/HalibutLegend/FishSkills/FishMud.cs:68 — Content/LegendWeapon/HalibutLegend/FishSkills/FishMud.cs:68-85 | Content/LegendWeapon/HalibutLegend/FishSkills/FishScorpio.cs:80-97 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishMud.cs:68` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (18 lines × 2) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowGeyserProj.cs:79 — Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowGeyserProj.cs:79-96 | Content/NPCs/FestersandSerpents/Projectiles/FssGeyserColumn.cs:77-94 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowGeyserProj.cs` and `Content/NPCs/FestersandSerpents/Projectiles/FssGeyserColumn.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 156 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowGeyserProj.cs:79` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) Content/Items/Ranged/TiroFinales/FinaleMagicBolt.cs:102 — Content/Items/Ranged/TiroFinales/FinaleMagicBolt.cs:102-119 | Content/Items/Ranged/TiroFinales/FinaleMusketRound.cs:104-121 — before extracting anything, compare `Content/Items/Ranged/TiroFinales/FinaleMagicBolt.cs` and `Content/Items/Ranged/TiroFinales/FinaleMusketRound.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 81 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Ranged/TiroFinales/FinaleMagicBolt.cs:102` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallProj.cs:834 — Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallProj.cs:834-851 | Content/Scenarios/Shenyo/Dolls/ScapegoatDollWalker.cs:145-162 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallProj.cs:834` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) Content/NPCs/BloomsandSerpents/Core/BssStateContext.cs:121 — Content/NPCs/BloomsandSerpents/Core/BssStateContext.cs:121-138 | Content/NPCs/FestersandSerpents/Core/FssStateContext.cs:108-125 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (18 lines × 2) Content/NPCs/BloomsandSerpents/States/BssIntroState.cs:37 — Content/NPCs/BloomsandSerpents/States/BssIntroState.cs:37-54 | Content/NPCs/FestersandSerpents/States/FssIntroState.cs:37-54 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BloomsandSerpents/States/BssIntroState.cs:37` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `ctx` to `BssStateContext` in one and `FssStateContext` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (18 lines × 2) Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryRoom.cs:191 — Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryRoom.cs:191-208 | Content/Scenarios/Dungeonworld/Gen/BossRooms/ProofingHallRoom.cs:222-239 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (18 lines × 2) Content/EntrustManager/Styles/ForestManagerStyle.cs:314 — Content/EntrustManager/Styles/ForestManagerStyle.cs:314-331 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:303-320 — before extracting anything, compare `Content/EntrustManager/Styles/ForestManagerStyle.cs` and `Content/EntrustManager/Styles/HotwindManagerStyle.cs` as WHOLE FILES: this scan already matched 34 separate duplicated blocks between them, totalling at least 398 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/EntrustManager/Styles/ForestManagerStyle.cs:314` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:138 — Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:138-155 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerIceSpikeProj.cs:125-142 — before extracting anything, compare `Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs` and `Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerIceSpikeProj.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 189 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:138` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:157` calls `OnHitNPC`, `AddBuff` and `Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerIceSpikeProj.cs:146` 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 (18 lines × 2) Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:912 — Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:912-929 | Content/Items/Melee/DivineSourceBlades/DivineSourceWaveProjectile.cs:342-359 — 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 (18 lines × 2) Content/Items/Ranged/AvalancheM60.cs:397 — Content/Items/Ranged/AvalancheM60.cs:397-414 | Content/LegendWeapon/SHPCLegend/Modules/Power/CryoCoreModule.cs:53-70 — before extracting anything, compare `Content/Items/Ranged/AvalancheM60.cs` and `Content/LegendWeapon/SHPCLegend/Modules/Power/CryoCoreModule.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Ranged/AvalancheM60.cs:397` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:135 — Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:135-152 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaReset.cs:144-161 — before extracting anything, compare `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs` and `Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaReset.cs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:135` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (18 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaTalismans/KikasaTalismanPaperDraw.cs:28 — Content/LegendWeapon/KikasaLegend/KikasaTalismans/KikasaTalismanPaperDraw.cs:28-45 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/KikasaTalismanPaperDraw.cs:51-68 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaTalismans/KikasaTalismanPaperDraw.cs:28` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (18 lines × 2) Content/NPCs/TBUGs/TBUGDialogue.cs:199 — Content/NPCs/TBUGs/TBUGDialogue.cs:199-216 | Content/NPCs/Victors/VictorDialogue.cs:199-216 — before extracting anything, compare `Content/NPCs/TBUGs/TBUGDialogue.cs` and `Content/NPCs/Victors/VictorDialogue.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/TBUGs/TBUGDialogue.cs:199` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (18 lines × 2) Content/GameModes/BrutalMobs/EvilBiome/Projectiles/VileLanceProj.cs:89 — Content/GameModes/BrutalMobs/EvilBiome/Projectiles/VileLanceProj.cs:89-106 | Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteMoltenGlob.cs:138-155 — before extracting anything, compare `Content/GameModes/BrutalMobs/EvilBiome/Projectiles/VileLanceProj.cs` and `Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteMoltenGlob.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 74 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (18 lines × 2) Content/HackTimes/Chips/HackChipGlyph.cs:113 — Content/HackTimes/Chips/HackChipGlyph.cs:113-130 | Content/Industrials/ElectricPowers/MiningMachines/MiningModuleGlyph.cs:108-125 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/HackTimes/Chips/HackChipGlyph.cs:113` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (18 lines × 2) Content/LegendWeapon/HalibutLegend/DomainSkills/FishTeleport.cs:513 — Content/LegendWeapon/HalibutLegend/DomainSkills/FishTeleport.cs:513-530 | Content/LegendWeapon/HalibutLegend/DomainSkills/YourLevelIsTooLow.cs:812-829 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/DomainSkills/FishTeleport.cs:513` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (18 lines × 2) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:581 — Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:581-598 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaReset.cs:632-649 — before extracting anything, compare `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs` and `Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaReset.cs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (18 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallProj.cs:469 — Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallProj.cs:469-487 | Content/Scenarios/Kiame/KasaOnis/KasaOniActor.cs:660-677 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (18 lines × 2) Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs:260 — Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs:260-277 | Content/Scenarios/Shenyo/ShenyoPortraitRainRenderer.cs:256-273 — before extracting anything, compare `Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs` and `Content/Scenarios/Shenyo/ShenyoPortraitRainRenderer.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 211 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs:260` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (18 lines × 2) Content/Tiles/CalSelfPortraitTile.cs:13 — Content/Tiles/CalSelfPortraitTile.cs:13-30 | Content/Tiles/WUTIVSelfPortraitTile.cs:13-30 — 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.
D4 · Code Duplication · Edited copy of a member (31 corresponding lines) · ×22
  • Edited copy of a member (31 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaBloodColumnDraw.cs:64 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaBloodColumnDraw.cs:64-94 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkGeyser.cs:292-340 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:435 — Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:435-465 | Content/Scenarios/Kiyume/UI/KiyumeLoadingScreen.cs:389-424 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowArrow.cs:101 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowArrow.cs:101-131 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearThrust.cs:75-113 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingPanel.cs:452 — Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingPanel.cs:452-482 | Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingUI.cs:308-344 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunBullet.cs:171 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunBullet.cs:171-206 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsPulseShot.cs:123-153 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) Content/Items/Melee/DawnshatterAzures/DawnshatterDash.cs:371 — Content/Items/Melee/DawnshatterAzures/DawnshatterDash.cs:371-401 | Content/Items/Melee/DawnshatterAzures/DawnshatterHeld.cs:952-993 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkFX.cs:550 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkFX.cs:550-586 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkFX.cs:592-622 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) Content/Scenarios/Shepel/CybCourses/HackTimeTutorialLead.cs:457 — Content/Scenarios/Shepel/CybCourses/HackTimeTutorialLead.cs:457-492 | Content/Scenarios/Shepel/CybCourses/WheelTutorialLead.cs:300-330 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) Content/NPCs/TBUGs/TBUGRiftSpawner.cs:117 — Content/NPCs/TBUGs/TBUGRiftSpawner.cs:117-147 | Content/NPCs/Victors/VictorPortalSpawner.cs:138-168 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:178 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:178-208 | Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs:246-277 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) Content/LegendWeapon/HalibutLegend/UI/HalibutHudLead.cs:505 — Content/LegendWeapon/HalibutLegend/UI/HalibutHudLead.cs:505-535 | Content/LegendWeapon/HalibutLegend/UI/HalibutHudLead.cs:638-673 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs:1051 — Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs:1051-1081 | Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersTP.cs:468-501 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) Content/GameModes/BrutalMobs/FrostLegion/FrostLegionNPC.cs:374 — Content/GameModes/BrutalMobs/FrostLegion/FrostLegionNPC.cs:374-404 | Content/GameModes/BrutalMobs/FrostLegion/FrostLegionNPC.cs:519-549 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) Content/Items/Accessories/BrutalRelics/Deerclops/WhiteoutVeilRender.cs:23 — Content/Items/Accessories/BrutalRelics/Deerclops/WhiteoutVeilRender.cs:23-53 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Rendering/DeerclopsVeilRender.cs:14-52 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraFrenzyPounceState.cs:132 — Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraFrenzyPounceState.cs:132-170 | Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraGrapplePounceState.cs:140-170 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:497 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:497-530 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:579-609 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) Content/NPCs/BrutalNPCs/BrutalGolem/States/GolemHeadDetachState.cs:22 — Content/NPCs/BrutalNPCs/BrutalGolem/States/GolemHeadDetachState.cs:22-52 | Content/NPCs/BrutalNPCs/BrutalGolem/States/GolemSolarOverdriveState.cs:24-56 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) Content/MainMenus/Himayo/HimayoMenuOverride.cs:163 — Content/MainMenus/Himayo/HimayoMenuOverride.cs:163-194 | Content/MainMenus/Shenyo/ShenyoMenuOverride.cs:128-158 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs:1166 — Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs:1166-1196 | Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs:1919-1954 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/BrainOfCthulhuAI.cs:179 — Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/BrainOfCthulhuAI.cs:179-214 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/EowHeadAI.cs:327-357 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:742 — Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:742-778 | Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:1040-1070 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:547 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:547-577 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:353-393 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (12–13 lines × 2) · ×22
  • Duplicated block (12–13 lines × 2) Content/GameModes/BrutalMobs/Ambience/Ashreign/AshreignHeatHazeRender.cs:34 — Content/GameModes/BrutalMobs/Ambience/Ashreign/AshreignHeatHazeRender.cs:34-45 | Content/Industrials/Generator/Thermal/ThermalHeatHazeRender.cs:34-46 — before extracting anything, compare `Content/GameModes/BrutalMobs/Ambience/Ashreign/AshreignHeatHazeRender.cs` and `Content/Industrials/Generator/Thermal/ThermalHeatHazeRender.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (12–13 lines × 2) Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclEyezorOrbProj.cs:55 — Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclEyezorOrbProj.cs:55-67 | Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclNailheadNailProj.cs:55-66 — before extracting anything, compare `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclEyezorOrbProj.cs` and `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclNailheadNailProj.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 63 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 (12–13 lines × 2) Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilSurgeColumnProj.cs:207 — Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilSurgeColumnProj.cs:207-218 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandGeyserProj.cs:191-203 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilSurgeColumnProj.cs:207` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (12–13 lines × 2) Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:284 — Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:284-295 | Content/Industrials/Generator/Thermal/ThermalGeneratorUI.cs:242-254 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:284` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12–13 lines × 2) Content/Items/Accessories/BrutalRelics/EmpressOfLight/InterferenceBursts.cs:32 — Content/Items/Accessories/BrutalRelics/EmpressOfLight/InterferenceBursts.cs:32-44 | Content/Items/Accessories/BrutalRelics/EmpressOfLight/InterferenceBursts.cs:125-136 — 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–13 lines × 2) Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:197 — Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:197-209 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:259-270 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:197` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:197` calls `Lerp`, `SmoothStep01` and `Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:259` does not — after which the two agree again for 5 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 (12–13 lines × 2) Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:717 — Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:717-729 | Content/Items/Melee/WeaverGrievanceses/WGManifestationActor.cs:612-623 — before extracting anything, compare `Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs` and `Content/Items/Melee/WeaverGrievanceses/WGManifestationActor.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 237 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:717` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:730` calls `PlaySound`, `SpawnWrenchBurst` and `Content/Items/Melee/WeaverGrievanceses/WGManifestationActor.cs:624` does not — after which the two agree again for 3 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 (12–13 lines × 2) Content/Items/Melee/DawnshatterAzures/DawnshatterDash.cs:465 — Content/Items/Melee/DawnshatterAzures/DawnshatterDash.cs:465-476 | Content/LegendWeapon/OnikiriLegend/OniSakuraFlights/OniSakuraFlight.cs:1251-1263 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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 (12–13 lines × 2) Content/LegendWeapon/HalibutLegend/FishSkills/FishDrizzle.cs:441 — Content/LegendWeapon/HalibutLegend/FishSkills/FishDrizzle.cs:441-452 | Content/LegendWeapon/HalibutLegend/FishSkills/FishSparkling.cs:318-330 — 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 (12–13 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomain.cs:223 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomain.cs:223-235 | Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomain.cs:252-263 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomain.cs:223` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (12–13 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrown.cs:228 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrown.cs:228-240 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaPlayerDrown.cs:265-276 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrown.cs:228` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrown.cs:226` calls `Inflate`, `Contains`, `ToPoint` and `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaPlayerDrown.cs:264` 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 (12–13 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPour.cs:356 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPour.cs:356-367 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:1435-1447 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPour.cs:356` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12–13 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:316 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:316-327 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs:390-402 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 161 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:316` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (12–13 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:690 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:690-701 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:546-558 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:690` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (12–13 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1203 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1203-1215 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonVesselWhip.cs:312-323 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1203` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonVesselWhip.cs:311` calls `SlumpT`, `Clamp` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1203` does not — after which the two agree again for 3 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 (12–13 lines × 2) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendCleave.cs:94 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendCleave.cs:94-105 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleRing.cs:57-69 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12–13 lines × 2) Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBanish.Net.cs:101 — Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBanish.Net.cs:101-113 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.Net.cs:124-135 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBanish.Net.cs:101` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (12–13 lines × 2) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:294 — Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:294-306 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowBurrowAmbushState.cs:253-264 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs` and `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowBurrowAmbushState.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 70 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:294` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `context` to `DestroyerStateContext` in one and `EowStateContext` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (12–13 lines × 2) Content/NPCs/BrutalNPCs/BrutalDukeFishron/FishronSharkronGlow.cs:51 — Content/NPCs/BrutalNPCs/BrutalDukeFishron/FishronSharkronGlow.cs:51-63 | Content/NPCs/BrutalNPCs/BrutalQueenBee/BrutalBeeAI.cs:253-264 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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 (12–13 lines × 2) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Core/EmpressArena.cs:69 — Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Core/EmpressArena.cs:69-80 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/EmpressDeathCutscene.cs:82-94 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Core/EmpressArena.cs:69` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (12–13 lines × 2) Content/NPCs/ScrapCommanders/ScrapLegionProbe.cs:42 — Content/NPCs/ScrapCommanders/ScrapLegionProbe.cs:42-53 | Content/Scenarios/OldNet/NPCs/OldNetTaggerICE.cs:52-64 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/ScrapCommanders/ScrapLegionProbe.cs:42` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (12–13 lines × 2) Content/Scenarios/Hadalworld/Ambience/HadalSky.cs:148 — Content/Scenarios/Hadalworld/Ambience/HadalSky.cs:148-159 | Content/Scenarios/OldNet/Backgrounds/OldNetSky.cs:143-155 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Hadalworld/Ambience/HadalSky.cs:148` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) · ×21
  • Edited copies of one member (3 members, 13+ corresponding lines) Content/EntrustManager/Styles/DraedonManagerStyle.cs:220 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:220-232 | Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:713-729 | Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:595-610 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 13+ corresponding lines) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:302 — Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:302-314 | Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingPanel.cs:485-497 | Content/LegendWeapon/SHPCLegend/UI/SHPCModuleSelectPanel.cs:265-277 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 13+ corresponding lines) Content/Scenarios/Kiame/KiameAmbience.cs:172 — Content/Scenarios/Kiame/KiameAmbience.cs:172-184 | Content/Scenarios/Kiame/Overlay/OniRainWorldState.cs:290-302 | Content/Wraiths/Abilities/GhostRains/GhostRainFx.cs:154-171 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 13+ corresponding lines) Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT1.cs:380 — Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT1.cs:380-392 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT2.cs:376-389 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT3.cs:254-266 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 13+ corresponding lines) Content/Items/Stones/Marbles/MarbleEffects.cs:194 — Content/Items/Stones/Marbles/MarbleEffects.cs:194-209 | Content/Items/Stones/Marbles/MarblePebble.cs:122-135 | Content/LegendWeapon/HalibutLegend/FishSkills/FishObsidian.cs:515-527 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 13+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1069 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1069-1081 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1405-1419 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:856-868 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 13+ corresponding lines) Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdHammerConeOmen.cs:123 — Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdHammerConeOmen.cs:123-135 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmYetiConeOmen.cs:138-150 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandConeTelegraph.cs:144-157 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 13+ corresponding lines) Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:513 — Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:513-525 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:547-559 | Content/Industrials/ElectricPowers/Recyclers/RecyclerUI.cs:474-486 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 13+ corresponding lines) Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:150 — Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:150-162 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconTP.cs:117-132 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatTP.cs:182-196 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 13+ corresponding lines) Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:292 — Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:292-304 | Content/Items/Melee/EnergySword.cs:331-343 | Content/Items/Melee/RebelBlade.cs:350-364 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 13+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishFallenStar.cs:129 — Content/LegendWeapon/HalibutLegend/FishSkills/FishFallenStar.cs:129-143 | Content/LegendWeapon/HalibutLegend/FishSkills/FishFallenStar.cs:307-320 | Content/LegendWeapon/HalibutLegend/FishSkills/FishFallenStar.cs:521-533 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 13+ corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Optic/PrecisionOpticModule.cs:95 — Content/LegendWeapon/SHPCLegend/Modules/Optic/PrecisionOpticModule.cs:95-107 | Content/LegendWeapon/SHPCLegend/Modules/Optic/SniperOpticModule.cs:230-244 | Content/LegendWeapon/SHPCLegend/Modules/Power/HighVoltageCoreModule.cs:60-73 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 13+ corresponding lines) Content/GameModes/GodSmith/Weapons/SummonWhips/Schemes/GsMorningStar.cs:54 — Content/GameModes/GodSmith/Weapons/SummonWhips/Schemes/GsMorningStar.cs:54-66 | Content/GameModes/GodSmith/Weapons/SummonWhips/Schemes/GsSpinalTap.cs:62-74 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Core/DeerclopsMotion.cs:119-131 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 13+ corresponding lines) Content/Scenarios/Dungeonworld/NPCs/Elites/BoneStitcher.cs:81 — Content/Scenarios/Dungeonworld/NPCs/Elites/BoneStitcher.cs:81-93 | Content/Scenarios/Dungeonworld/NPCs/Elites/BoneStitcher.cs:783-796 | Content/Scenarios/Dungeonworld/NPCs/Elites/LanternWarden.cs:98-111 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 13+ corresponding lines) Content/Items/Ranged/DuneStalker.cs:296 — Content/Items/Ranged/DuneStalker.cs:296-309 | Content/LegendWeapon/HalibutLegend/FishSkills/FishHoney.cs:356-368 | Content/LegendWeapon/HalibutLegend/FishSkills/Fishotroning.cs:220-236 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 13+ corresponding lines) Content/Cyberwares/Tutorial/CyberwareGuideLead.cs:137 — Content/Cyberwares/Tutorial/CyberwareGuideLead.cs:137-158 | Content/LegendWeapon/KikasaLegend/UI/KikasaHudLead.cs:275-287 | Content/Scenarios/OldNet/UI/OldNetGuideLead.cs:80-92 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 13+ corresponding lines) Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomChargeGlowProj.cs:58 — Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomChargeGlowProj.cs:58-71 | Content/Items/Accessories/BrutalRelics/Destroyer/ProbeDroneProj.cs:308-320 | Content/NPCs/BrutalNPCs/BrutalQueenBee/BrutalBeeAI.cs:227-240 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 13+ corresponding lines) Content/NPCs/ScrapCommanders/Projectiles/ScrapArmHitbox.cs:30 — Content/NPCs/ScrapCommanders/Projectiles/ScrapArmHitbox.cs:30-43 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpClawHitbox.cs:30-42 | Content/Scenarios/Dungeonworld/NPCs/GaolCuffHitbox.cs:29-42 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 13+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeSlash.cs:61 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeSlash.cs:61-73 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriSlash.cs:121-134 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithSlash.cs:72-86 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 13+ corresponding lines) Common/NpcGroupHelper.cs:300 — Common/NpcGroupHelper.cs:300-312 | Common/NpcGroupHelper.cs:315-327 | Common/NpcGroupHelper.cs:330-342 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 13+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalQueenBee/Projectiles/WaxHiveTurret.cs:131 — Content/NPCs/BrutalNPCs/BrutalQueenBee/Projectiles/WaxHiveTurret.cs:131-145 | Content/Scenarios/Kiyume/NPCs/FuneralCortegeYokai.cs:1074-1088 | Content/Scenarios/Kiyume/NPCs/ShallowHandsYokai.cs:429-441 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) · ×21
  • Edited copies of one member (3 members, 15+ corresponding lines) Content/GameModes/UI/GameModeRenderer.cs:522 — Content/GameModes/UI/GameModeRenderer.cs:522-536 | Content/LegendWeapon/KikasaLegend/UI/KikasaHudTooltip.cs:116-138 | Content/LegendWeapon/OnikiriLegend/UI/OniHudTooltipOverlay.cs:148-170 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:348 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:348-369 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:349-371 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:406-420 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:991 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:991-1005 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1332-1347 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:782-796 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) Content/Items/Melee/OniMacheteHands.cs:320 — Content/Items/Melee/OniMacheteHands.cs:320-336 | Content/Items/Melee/OniMacheteHands.cs:951-965 | Content/Items/Melee/OniMacheteHands.cs:1257-1271 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) Content/GameModes/GodSmith/Accessories/Offense/GodSmithEmblems.cs:186 — Content/GameModes/GodSmith/Accessories/Offense/GodSmithEmblems.cs:186-200 | Content/GameModes/GodSmith/Accessories/Offense/GodSmithManaFlowerChain.cs:125-143 | Content/GameModes/GodSmith/Accessories/Offense/GodSmithQuiverChain.cs:29-46 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) Content/Items/Melee/DestroyersBlade.cs:300 — Content/Items/Melee/DestroyersBlade.cs:300-314 | Content/Items/Melee/DragonsScaleGreatsword.cs:313-327 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:323-337 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:350 — Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:350-365 | Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:354-368 | Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:383-398 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Barrel/MagmaVentBarrelModule.cs:164 — Content/LegendWeapon/SHPCLegend/Modules/Barrel/MagmaVentBarrelModule.cs:164-178 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Rendering/WofMotionFX.cs:150-164 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Rendering/WofMotionFX.cs:167-181 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) Content/GameModes/GodSmith/Weapons/SummonMinions/Schemes/GsHornetStaff.cs:225 — Content/GameModes/GodSmith/Weapons/SummonMinions/Schemes/GsHornetStaff.cs:225-239 | Content/GameModes/GodSmith/Weapons/SummonMinions/Schemes/GsImpStaff.cs:41-62 | Content/GameModes/GodSmith/Weapons/SummonMinions/Schemes/GsStardustDragonStaff.cs:46-60 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) Content/Industrials/ElectricPowers/GridSwitches/GridSwitch.cs:27 — Content/Industrials/ElectricPowers/GridSwitches/GridSwitch.cs:27-41 | Content/Industrials/ElectricPowers/Sensors/Sensor.cs:68-84 | Content/Industrials/Generator/Biomass/BiomassGenerator.cs:35-51 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Leviathan.cs:248 — Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Leviathan.cs:248-264 | Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Colossus.cs:115-129 | Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Colossus.cs:235-249 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/EyeOfCthulhuAI.cs:133 — Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/EyeOfCthulhuAI.cs:133-147 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/CultistBossAI.cs:116-130 | Content/NPCs/BrutalNPCs/BrutalPlantera/PlanteraAI.cs:194-211 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:32 — Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:32-48 | Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingPanel.cs:50-64 | Content/LegendWeapon/SHPCLegend/UI/SHPCModuleSelectPanel.cs:67-82 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) Content/Scenarios/Dungeonworld/Gen/Layers/L1/L1Style.cs:248 — Content/Scenarios/Dungeonworld/Gen/Layers/L1/L1Style.cs:248-263 | Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Palette.cs:258-272 | Content/Scenarios/Dungeonworld/Gen/Layers/L7/L7Style.cs:282-296 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) Content/GameModes/GodSmith/Weapons/MagicCataclysm/GsCataclysmRiderNPC.cs:37 — Content/GameModes/GodSmith/Weapons/MagicCataclysm/GsCataclysmRiderNPC.cs:37-51 | Content/GameModes/GodSmith/Weapons/MagicChant/GsChantScheme.cs:316-330 | Content/GameModes/GodSmith/Weapons/MagicChant/GsWaspGun.cs:94-113 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) Content/Items/Accessories/JusticeUnveileds/JusticeCrossMark.cs:70 — Content/Items/Accessories/JusticeUnveileds/JusticeCrossMark.cs:70-84 | Content/Items/Accessories/JusticeUnveileds/JusticeUnveiledCross.cs:118-135 | Content/Items/Accessories/JusticeUnveileds/JusticeUnveiledCross.cs:189-207 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishHarpy.cs:463 — Content/LegendWeapon/HalibutLegend/FishSkills/FishHarpy.cs:463-477 | Content/LegendWeapon/HalibutLegend/FishSkills/FishHarpy.cs:610-624 | Content/LegendWeapon/HalibutLegend/FishSkills/FishHarpy.cs:626-645 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) Content/Scenarios/Kiyume/Ambience/KiyumeLampEvents.cs:82 — Content/Scenarios/Kiyume/Ambience/KiyumeLampEvents.cs:82-98 | Content/Scenarios/Kiyume/Ambience/KiyumeSkyEvents.cs:59-73 | Content/Scenarios/Kiyume/Ambience/KiyumeTraces.cs:66-81 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:129 — Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:129-143 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleScar.cs:54-68 | Content/Scenarios/Dungeonworld/NPCs/GaolAnchorWeapon.cs:68-82 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) Content/Items/Magic/Everdeeps/EverdeepMaelstrom.cs:137 — Content/Items/Magic/Everdeeps/EverdeepMaelstrom.cs:137-151 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronSharkTornadoProj.cs:162-176 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpSwarmBubble.cs:86-100 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendParticles.cs:226 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendParticles.cs:226-244 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Rendering/BKSParticles.cs:34-48 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Rendering/BKSParticles.cs:110-124 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (9 lines × 5) · ×20
  • Duplicated block (9 lines × 5) Content/Items/Modifys/RBloodButcherer.cs:865 — Content/Items/Modifys/RBloodButcherer.cs:865-873 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:64-72 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:69-77 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterGlob.cs:60-68 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenCrystalShard.cs:57-65 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Modifys/RBloodButcherer.cs:865` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 5) Content/Items/Melee/DestroyersBlade.cs:350 — Content/Items/Melee/DestroyersBlade.cs:350-358 | Content/Items/Melee/DragonsScaleGreatsword.cs:363-371 | Content/Items/Melee/EnergySword.cs:378-386 | Content/Items/Melee/RebelBlade.cs:400-408 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:362-370 — before extracting anything, compare `Content/Items/Melee/DestroyersBlade.cs` and `Content/Items/Melee/DragonsScaleGreatsword.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 419 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DestroyersBlade.cs:350` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 5) Content/Items/Melee/NeutronGlaive.cs:1283 — Content/Items/Melee/NeutronGlaive.cs:1283-1291 | Content/Items/Melee/NeutronGlaive.cs:1362-1370 | Content/Items/Melee/NeutronScythe.cs:354-362 | Content/Items/Ranged/NeutronBows/EXNeutronExplosionRanged.cs:60-68 | Content/Items/Ranged/NeutronBows/NeutronExplosionRanged.cs:59-67 — there are 5 copies across 4 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/NeutronGlaive.cs:1283` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 5) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:57 — Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:57-65 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs:95-103 | Content/Scenarios/Kiame/KiameWakeResetRender.cs:93-101 | Content/Scenarios/Kiame/Overlay/OniUmbrellaPuddleRender.cs:69-77 | Content/Scenarios/Kiame/Water/KiameWaterRender.cs:118-126 — before extracting anything, compare `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs` and `Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:54` calls `GetRenderTargets` and `Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs:92` 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 × 5) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainSky.cs:109 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainSky.cs:109-117 | Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamSky.cs:69-77 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainSky.cs:90-98 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspaceSky.cs:69-77 | Content/Scenarios/Himayo/ToriiShrines/ToriiDusk.cs:185-193 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainSky.cs` and `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamSky.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 5) Content/NPCs/BrutalNPCs/BrutalDukeFishron/Rendering/FishronStormSky.cs:233 — Content/NPCs/BrutalNPCs/BrutalDukeFishron/Rendering/FishronStormSky.cs:233-241 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/MachineEffect.cs:136-144 | Content/Scenarios/Draedon/Tzeentch/TzeentchEffect.cs:78-86 | Content/Scenarios/OldDuke/OldDukeEffect.cs:92-100 | Content/Scenarios/Shepel/CybCourses/CybCourseSky.cs:79-87 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/MachineEffect.cs` and `Content/Scenarios/Draedon/Tzeentch/TzeentchEffect.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalDukeFishron/Rendering/FishronStormSky.cs:233` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/BrutalNPCs/BrutalDukeFishron/Rendering/FishronStormSky.cs:228` calls `SetValue` and `Content/Scenarios/OldDuke/OldDukeEffect.cs:91` 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 × 5) Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserBoltProj.cs:110 — Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserBoltProj.cs:110-118 | Content/GameModes/BrutalMobs/Martians/Projectiles/MrtScutlixHeavyBolt.cs:95-103 | Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornQuakeWave.cs:151-159 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMirrorPhantom.cs:291-299 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerBolt.cs:89-97 — before extracting anything, compare `Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserBoltProj.cs` and `Content/GameModes/BrutalMobs/Martians/Projectiles/MrtScutlixHeavyBolt.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 77 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserBoltProj.cs:110` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/GameModes/BrutalMobs/Martians/Projectiles/MrtScutlixHeavyBolt.cs:104` calls `EntitySpriteDraw`, `Vector2` and `Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserBoltProj.cs:119` 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 × 5) Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteDiveOmen.cs:103 — Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteDiveOmen.cs:103-111 | Content/GameModes/BrutalMobs/NightPack/Projectiles/NightDiveOmen.cs:129-137 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkChargeOmen.cs:140-148 | Content/GameModes/BrutalMobs/Sky/Projectiles/SkyGaleDiveOmen.cs:116-124 | Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornDiveLane.cs:115-123 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.
  • Duplicated block (9 lines × 5) Content/Items/Melee/DestroyersBlade.cs:411 — Content/Items/Melee/DestroyersBlade.cs:411-419 | Content/Items/Melee/DragonsScaleGreatsword.cs:423-431 | Content/Items/Melee/EnergySword.cs:448-456 | Content/Items/Melee/RebelBlade.cs:445-453 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:423-431 — before extracting anything, compare `Content/Items/Melee/DestroyersBlade.cs` and `Content/Items/Melee/DragonsScaleGreatsword.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 419 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 (9 lines × 5) Content/Items/Melee/Shatterfangs/ShatterfangPRT.cs:56 — Content/Items/Melee/Shatterfangs/ShatterfangPRT.cs:56-64 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBoneParticles.cs:64-72 | Content/LegendWeapon/HalibutLegend/FishSkills/FishEaterofPlanktonVFX.cs:153-162 | Content/LegendWeapon/HalibutLegend/FishSkills/FishHungerVFX.cs:217-226 | Content/LegendWeapon/HalibutLegend/FishSkills/FishRockParticles.cs:149-158 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Shatterfangs/ShatterfangPRT.cs:56` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 5) Content/Items/Summon/AzureDragonRage.cs:115 — Content/Items/Summon/AzureDragonRage.cs:115-123 | Content/Items/Summon/BleedingScourge.cs:98-106 | Content/Items/Summon/ElementWhip.cs:106-114 | Content/Items/Summon/GhostFireWhip.cs:112-120 | Content/Items/Summon/WhiplashGalactica.cs:124-132 — before extracting anything, compare `Content/Items/Summon/AzureDragonRage.cs` and `Content/Items/Summon/BleedingScourge.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 93 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Summon/AzureDragonRage.cs:115` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Summon/WhiplashGalactica.cs:122` calls `LoadProjectile` and `Content/Items/Summon/ElementWhip.cs:104` does not — after which the two agree again for 3 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 × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:143 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:143-151 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:137-145 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs:106-114 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeHeatRay.cs:105-113 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeSkullBeamProj.cs:108-116 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs` and `Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 216 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:143` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:143` calls `CameraPunch` and `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs:106` does not — after which the two agree again for 3 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 × 5) Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuBao.cs:133 — Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuBao.cs:133-141 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuFei.cs:91-99 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuSha.cs:130-138 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuXia.cs:114-122 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuXiao.cs:77-86 — 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 5 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuBao.cs:133` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 5) Content/Narrative/MusicToast.cs:351 — Content/Narrative/MusicToast.cs:351-359 | Content/Narrative/MusicToast.cs:411-419 | Content/Narrative/MusicToast.cs:490-498 | Content/Narrative/MusicToast.cs:523-531 | Content/Scenarios/SupCal/End/EternalBlazingNow/Enchants/EnchantUI.cs:401-409 — there are 5 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 5 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Narrative/MusicToast.cs:351` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 5) Content/PRTTypes/PRT_HeavenfallStar.cs:25 — Content/PRTTypes/PRT_HeavenfallStar.cs:25-33 | Content/PRTTypes/PRT_Line_FormPlayer.cs:23-31 | Content/PRTTypes/PRT_LonginusStar.cs:37-45 | Content/PRTTypes/PRT_Spark.cs:30-38 | Content/PRTTypes/PRT_SparkAlpha.cs:27-35 — before extracting anything, compare `Content/PRTTypes/PRT_Spark.cs` and `Content/PRTTypes/PRT_SparkAlpha.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/PRTTypes/PRT_HeavenfallStar.cs:25` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/PRTTypes/PRT_Spark.cs:29` calls `SetProperty` and `Content/PRTTypes/PRT_HeavenfallStar.cs:24` 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 × 5) Content/Scenarios/Dungeonworld/DungeonworldGuard.cs:42 — Content/Scenarios/Dungeonworld/DungeonworldGuard.cs:42-50 | Content/Scenarios/Hadalworld/HadalworldGuard.cs:42-50 | Content/Scenarios/Kiame/KiameGuard.cs:42-50 | Content/Scenarios/Kiyume/KiyumeGuard.cs:42-50 | Content/Scenarios/OldNet/OldNetGuard.cs:42-50 — before extracting anything, compare `Content/Scenarios/Dungeonworld/DungeonworldGuard.cs` and `Content/Scenarios/Hadalworld/HadalworldGuard.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 5) Content/Scenarios/Dungeonworld/Gen/Layers/L1/L1Style.cs:122 — Content/Scenarios/Dungeonworld/Gen/Layers/L1/L1Style.cs:122-130 | Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Palette.cs:131-139 | Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Rooms.cs:399-407 | Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Rooms.cs:411-419 | Content/Scenarios/Dungeonworld/Gen/Layers/L7/L7Style.cs:206-214 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.
  • Duplicated block (9 lines × 5) Content/GameModes/GodSmith/Weapons/Broadswords/GsBloodButcherer.cs:180 — Content/GameModes/GodSmith/Weapons/Broadswords/GsBloodButcherer.cs:180-188 | Content/GameModes/GodSmith/Weapons/Flails/GsTheMeatball.cs:107-115 | Content/GameModes/GodSmith/Weapons/MagicChant/GsCursedFlames.cs:263-271 | Content/GameModes/GodSmith/Weapons/MagicChant/GsGoldenShower.cs:232-240 | Content/GameModes/GodSmith/Weapons/MagicChant/GsNettleBurst.cs:150-158 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/GodSmith/Weapons/Flails/GsTheMeatball.cs:104` calls `OnHitNPC`, `AddBuff` and `Content/GameModes/GodSmith/Weapons/Broadswords/GsBloodButcherer.cs:178` 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 × 5) Content/GameModes/GodSmith/Weapons/Bows/DaedalusStormbowScheme.cs:228 — Content/GameModes/GodSmith/Weapons/Bows/DaedalusStormbowScheme.cs:228-236 | Content/GameModes/GodSmith/Weapons/Bows/Projectiles/GsPhantomArcherProj.cs:18-26 | Content/GameModes/GodSmith/Weapons/Bows/Projectiles/GsStakePinProj.cs:20-28 | Content/GameModes/GodSmith/Weapons/Launchers/GsSnowmanCannon.cs:84-92 | Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsBloodSipProj.cs:21-29 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/GameModes/GodSmith/Weapons/Bows/DaedalusStormbowScheme.cs:238` calls `ShouldUpdatePosition` and `Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsBloodSipProj.cs:31` 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 × 5) Content/GameModes/GodSmith/Weapons/Flails/GsBallOHurt.cs:118 — Content/GameModes/GodSmith/Weapons/Flails/GsBallOHurt.cs:118-126 | Content/GameModes/GodSmith/Weapons/Flails/GsBlueMoon.cs:89-97 | Content/GameModes/GodSmith/Weapons/Flails/GsFlairon.cs:164-172 | Content/GameModes/GodSmith/Weapons/Flails/GsFlowerPow.cs:115-123 | Content/GameModes/GodSmith/Weapons/Flails/GsSunfury.cs:88-96 — 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 5 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (7 lines × 5) · ×20
  • Duplicated block (7 lines × 5) Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:92 — Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:92-98 | Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyGhostNameThread.cs:98-104 | Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyRavenSwoopOmen.cs:102-108 | Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserMarkLine.cs:149-155 | Content/GameModes/BrutalMobs/NightPack/Projectiles/NightDiveOmen.cs:104-110 — before extracting anything, compare `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs` and `Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyGhostNameThread.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 69 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:92` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyGhostNameThread.cs:105` calls `Clamp`, `Distance` and `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:99` does not — after which the two agree again for 3 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 × 5) Content/Items/Melee/NeutronGlaive.cs:1241 — Content/Items/Melee/NeutronGlaive.cs:1241-1247 | Content/Items/Melee/NeutronGlaive.cs:1305-1311 | Content/Items/Melee/NeutronScythe.cs:311-317 | Content/Items/Ranged/NeutronBows/EXNeutronExplosionRanged.cs:17-23 | Content/Items/Ranged/NeutronBows/NeutronExplosionRanged.cs:17-23 — there are 5 copies across 4 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 (7 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:370 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:370-376 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:368-374 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:288-294 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:333-339 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:365-371 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs` as WHOLE FILES: this scan already matched 75 separate duplicated blocks between them, totalling at least 912 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:370` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 5) Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdHammerConeOmen.cs:137 — Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdHammerConeOmen.cs:137-143 | Content/GameModes/BrutalMobs/EvilBiome/Projectiles/MummyWrapOmen.cs:96-102 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmYetiConeOmen.cs:152-158 | Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomVineWhipOmen.cs:105-111 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandConeTelegraph.cs:159-165 — before extracting anything, compare `Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdHammerConeOmen.cs` and `Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmYetiConeOmen.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdHammerConeOmen.cs:137` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 5) Content/NPCs/BrutalNPCs/BrutalDeerclops/DeerclopsAI.cs:169 — Content/NPCs/BrutalNPCs/BrutalDeerclops/DeerclopsAI.cs:169-175 | Content/NPCs/BrutalNPCs/BrutalDestroyer/DestroyerHeadAI.cs:220-226 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/EmpressOfLightAI.cs:216-222 | Content/NPCs/BrutalNPCs/BrutalKingSlime/KingSlimeAI.cs:175-181 | Content/NPCs/BrutalNPCs/BrutalQueenBee/BrutalQueenBeeAI.cs:159-165 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalDeerclops/DeerclopsAI.cs:169` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 5) Content/GameModes/BrutalMobs/Ambience/Tidecall/Projectiles/TidecallRogueWaveProj.cs:361 — Content/GameModes/BrutalMobs/Ambience/Tidecall/Projectiles/TidecallRogueWaveProj.cs:361-368 | Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:178-184 | Content/Scenarios/Dungeonworld/NPCs/UndrownedDepthMine.cs:202-208 | Content/Scenarios/Dungeonworld/NPCs/UndrownedTideWave.cs:156-163 | Content/Scenarios/Dungeonworld/NPCs/UndrownedVFX.cs:57-64 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.
  • Duplicated block (7 lines × 5) Content/GameModes/BrutalMobs/EliteMove/Projectiles/EMScatterBoltProj.cs:91 — Content/GameModes/BrutalMobs/EliteMove/Projectiles/EMScatterBoltProj.cs:91-97 | Content/GameModes/BrutalMobs/NightPack/Projectiles/NightBoneProj.cs:171-177 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtBroadsideBall.cs:96-102 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtFanShot.cs:82-88 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtRicochetShot.cs:274-280 — before extracting anything, compare `Content/GameModes/BrutalMobs/EliteMove/Projectiles/EMScatterBoltProj.cs` and `Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtBroadsideBall.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/EliteMove/Projectiles/EMScatterBoltProj.cs:91` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (7 lines × 5) Content/GameModes/GodSmith/Weapons/Broadswords/GsHamBat.cs:173 — Content/GameModes/GodSmith/Weapons/Broadswords/GsHamBat.cs:173-179 | Content/GameModes/GodSmith/Weapons/Broadswords/GsMythrilSword.cs:189-195 | Content/GameModes/GodSmith/Weapons/Broadswords/GsPiercingStarlight.cs:370-376 | Content/GameModes/GodSmith/Weapons/Broadswords/GsSeedler.cs:270-276 | Content/GameModes/GodSmith/Weapons/Broadswords/GsSlapHand.cs:173-179 — 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 5 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 5) Content/GameModes/GodSmith/Weapons/MeleeOddities/GsSolarEruption.cs:308 — Content/GameModes/GodSmith/Weapons/MeleeOddities/GsSolarEruption.cs:308-317 | Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:558-564 | Content/Items/Melee/Flawless.cs:438-446 | Content/Items/Melee/Heartcarver.cs:338-346 | Content/Items/Melee/StormGoddessSpears/StormGoddessSpearHeld.cs:399-408 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/MeleeOddities/GsSolarEruption.cs:308` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/GodSmith/Weapons/MeleeOddities/GsSolarEruption.cs:305` calls `ModifyHitNPC` and `Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:556` 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 × 5) Content/HackTimes/Protocols/ArmorParse.cs:90 — Content/HackTimes/Protocols/ArmorParse.cs:90-96 | Content/HackTimes/Protocols/CommandLinkCut.cs:149-155 | Content/HackTimes/Protocols/LimbSeizure.cs:186-192 | Content/HackTimes/Protocols/NeuralOverclock.cs:134-140 | Content/HackTimes/Protocols/PayloadRewrite.cs:103-109 — 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 5 call sites, so a change lands once.
  • Duplicated block (7 lines × 5) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:602 — Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:602-609 | Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:477-483 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:511-517 | Content/Industrials/ElectricPowers/Recyclers/RecyclerUI.cs:438-444 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterUI.cs:475-481 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:602` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:218 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:218-224 | Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs:287-293 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs:201-207 | Content/Scenarios/Kiame/KiameWakeResetRender.cs:196-202 | Content/Scenarios/Kiame/Overlay/OniRainWorldRender.cs:221-227 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs` and `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 192 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:218` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (7 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkFX.cs:561 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkFX.cs:561-568 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkSplashFX.cs:468-474 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:111-117 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:183-191 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:250-257 — 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. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:191` calls `SetValue` and `Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkFX.cs:568` does not — after which the two agree again for 4 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 × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:440 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:440-446 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:296-302 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:342-348 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:330-336 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:349-356 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 408 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:440` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (7 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:836 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:836-842 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1302-1308 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonOrb.cs:141-149 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeBloodBee.cs:164-172 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1196-1202 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:836` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 5) Content/NPCs/BloomsandSerpents/States/BssCactusBallState.cs:58 — Content/NPCs/BloomsandSerpents/States/BssCactusBallState.cs:58-65 | Content/NPCs/BloomsandSerpents/States/BssDustDevilState.cs:51-57 | Content/NPCs/BloomsandSerpents/States/BssNeedleRippleState.cs:72-78 | Content/NPCs/BloomsandSerpents/States/BssStormTransitionState.cs:68-74 | Content/NPCs/BloomsandSerpents/States/BssWindBladeState.cs:137-143 — 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 5 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BloomsandSerpents/States/BssCactusBallState.cs:58` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (7 lines × 5) Content/NPCs/BrutalNPCs/BrutalGolem/Rendering/GolemScreenEffectRender.cs:70 — Content/NPCs/BrutalNPCs/BrutalGolem/Rendering/GolemScreenEffectRender.cs:70-78 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordScreenRender.cs:39-45 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Rendering/SkeletronScreenRender.cs:36-42 | Content/Renders/PrimeScreenEffectRender.cs:92-101 | Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:2966-2972 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalGolem/Rendering/GolemScreenEffectRender.cs` and `Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordScreenRender.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 74 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalGolem/Rendering/GolemScreenEffectRender.cs:70` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 5) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/MachineEffect.cs:135 — Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/MachineEffect.cs:135-141 | Content/Scenarios/Draedon/Tzeentch/TzeentchEffect.cs:77-83 | Content/Scenarios/OldDuke/OldDukeEffect.cs:91-97 | Content/Scenarios/Shepel/CybCourses/CybCourseSky.cs:78-84 | Content/Scenarios/Shepel/CybCourses/CybCourseWorld.cs:162-169 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/MachineEffect.cs` and `Content/Scenarios/Draedon/Tzeentch/TzeentchEffect.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/MachineEffect.cs:135` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/MachineEffect.cs:132` calls `SetValue` and `Content/Scenarios/OldDuke/OldDukeEffect.cs:89` 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 × 5) Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordScheme.cs:62 — Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordScheme.cs:62-68 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsOdditiesComboScheme.cs:53-59 | Content/GameModes/GodSmith/Weapons/_Exemplars/GsIronBroadsword.cs:52-58 | Content/Items/Modifys/RBloodButcherer.cs:70-76 | Content/Items/Modifys/RTerraBlades/RTerraBlade.cs:74-80 — before extracting anything, compare `Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordScheme.cs` and `Content/GameModes/GodSmith/Weapons/MeleeOddities/GsOdditiesComboScheme.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordScheme.cs:58` calls `GsUseItemHitbox` and `Content/GameModes/GodSmith/Weapons/MeleeOddities/GsOdditiesComboScheme.cs:50` 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 × 5) Content/Scenarios/Dungeonworld/DungeonworldGuard.cs:70 — Content/Scenarios/Dungeonworld/DungeonworldGuard.cs:70-76 | Content/Scenarios/Hadalworld/HadalworldGuard.cs:70-76 | Content/Scenarios/Kiame/KiameGuard.cs:70-76 | Content/Scenarios/Kiyume/KiyumeGuard.cs:70-76 | Content/Scenarios/OldNet/OldNetGuard.cs:70-76 — before extracting anything, compare `Content/Scenarios/Dungeonworld/DungeonworldGuard.cs` and `Content/Scenarios/Hadalworld/HadalworldGuard.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Edited copy of a member (38 corresponding lines) · ×19
  • Edited copy of a member (38 corresponding lines) Content/Items/Ranged/Starships/StarshipComet.cs:63 — Content/Items/Ranged/Starships/StarshipComet.cs:63-100 | Content/Items/Ranged/Starships/StarshipMeteor.cs:120-162 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (38 corresponding lines) Content/EntrustManager/BaseQuestAcceptUI.cs:472 — Content/EntrustManager/BaseQuestAcceptUI.cs:472-515 | Content/UIs/OverhaulSettings/OverhaulSettingsUI.cs:870-907 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (38 corresponding lines) Content/Items/Modifys/RBloodButcherer.cs:926 — Content/Items/Modifys/RBloodButcherer.cs:926-963 | Content/LegendWeapon/HalibutLegend/FishSkills/FishIchornVFX.cs:97-140 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (38 corresponding lines) Common/ShockRingDraw.cs:27 — Common/ShockRingDraw.cs:27-75 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteRingRender.cs:108-145 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (38 corresponding lines) Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocDeathState.cs:160 — Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocDeathState.cs:160-197 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocPhaseTransitionState.cs:161-199 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (38 corresponding lines) Content/GameModes/GodSmith/Weapons/Broadswords/GsMeowmere.cs:403 — Content/GameModes/GodSmith/Weapons/Broadswords/GsMeowmere.cs:403-440 | Content/GameModes/GodSmith/Weapons/Broadswords/GsMeowmere.cs:538-575 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (38 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishDrizzle.cs:149 — Content/LegendWeapon/HalibutLegend/FishSkills/FishDrizzle.cs:149-186 | Content/LegendWeapon/HalibutLegend/FishSkills/FishSparkling.cs:36-80 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (38 corresponding lines) Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraPetalWave.cs:101 — Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraPetalWave.cs:101-143 | Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraSporeCloud.cs:73-110 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (38 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1363 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1363-1400 | Content/NPCs/ScrapCommanders/ScrapCommander.cs:646-691 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (38 corresponding lines) Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs:446 — Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs:446-483 | Content/Items/Melee/WeaverGrievanceses/WGManifestationNet.cs:447-484 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (38 corresponding lines) Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclNestFuryProj.cs:52 — Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclNestFuryProj.cs:52-94 | Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclOpeningProj.cs:48-85 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (38 corresponding lines) Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBanishParticles.cs:12 — Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBanishParticles.cs:12-50 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreezeParticles.cs:11-48 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (38 corresponding lines) Content/Items/Melee/NeutronGlaive.cs:215 — Content/Items/Melee/NeutronGlaive.cs:215-252 | Content/Items/Modifys/RBloodButcherer.cs:201-242 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (38 corresponding lines) Content/Items/Armor/Deepcrystals/DeepcrystalPlayer.cs:288 — Content/Items/Armor/Deepcrystals/DeepcrystalPlayer.cs:288-325 | Content/NPCs/SeaShrimp/Rendering/SeaShrimpBubbleRender.cs:43-85 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (38 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainNet.cs:39 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainNet.cs:39-88 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainNet.cs:37-74 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (38 corresponding lines) Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:707 — Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:707-747 | Content/Items/Melee/WeaverGrievanceses/WGManifestationActor.cs:602-639 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (38 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:482 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:482-525 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:568-605 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (38 corresponding lines) Content/GameModes/BrutalMobs/Martians/Projectiles/MrtTeslaArcProj.cs:140 — Content/GameModes/BrutalMobs/Martians/Projectiles/MrtTeslaArcProj.cs:140-177 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/PincerBindTether.cs:130-169 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (38 corresponding lines) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerDespawnState.cs:92 — Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerDespawnState.cs:92-140 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsDeathState.cs:68-105 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (28 corresponding lines) · ×19
  • Edited copy of a member (28 corresponding lines) Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:518 — Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:518-547 | Content/Scenarios/Kiyume/UI/KiyumeLoadingScreen.cs:457-484 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (28 corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendParticles.cs:467 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendParticles.cs:467-494 | Content/Tiles/BloodAltars/BloodAltarPRT.cs:110-138 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (28 corresponding lines) Content/Items/Melee/Abyssrends/AbyssrendFX.cs:136 — Content/Items/Melee/Abyssrends/AbyssrendFX.cs:136-163 | Content/NPCs/SeaShrimp/Rendering/SeaShrimpVFX.cs:54-81 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (28 corresponding lines) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberCascadeNodeProj.cs:91 — Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberCascadeNodeProj.cs:91-122 | Content/LegendWeapon/SHPCLegend/Modules/Power/StormCellModule.cs:27-54 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (28 corresponding lines) Content/EntrustManager/BaseQuestAcceptUI.cs:298 — Content/EntrustManager/BaseQuestAcceptUI.cs:298-327 | Content/UIs/OverhaulSettings/OverhaulSettingsUI.cs:407-434 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (28 corresponding lines) Content/GameModes/BrutalMobs/Ambience/Hollowdeep/Projectiles/HollowdeepRockfallProj.cs:132 — Content/GameModes/BrutalMobs/Ambience/Hollowdeep/Projectiles/HollowdeepRockfallProj.cs:132-159 | Content/GameModes/BrutalMobs/Ambience/Mireheart/Projectiles/MireheartGasPocketProj.cs:142-178 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (28 corresponding lines) Content/Items/Accessories/BrutalRelics/KingSlime/RoyalGelField.cs:118 — Content/Items/Accessories/BrutalRelics/KingSlime/RoyalGelField.cs:118-148 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSGelPoolProj.cs:71-98 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (28 corresponding lines) Content/GameModes/GodSmith/Armors/Hardmode/GsForbiddenArmor.cs:44 — Content/GameModes/GodSmith/Armors/Hardmode/GsForbiddenArmor.cs:44-72 | Content/GameModes/GodSmith/Armors/Hardmode/GsSpookyWoodArmor.cs:44-71 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (28 corresponding lines) Content/GameModes/BrutalMobs/DungeonDeep/DungeonDeepNPC.Melee.cs:53 — Content/GameModes/BrutalMobs/DungeonDeep/DungeonDeepNPC.Melee.cs:53-91 | Content/GameModes/BrutalMobs/DungeonDeep/DungeonDeepNPC.Melee.cs:239-266 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (28 corresponding lines) Content/NPCs/BloomsandSerpents/States/BssCoilOrbitState.cs:192 — Content/NPCs/BloomsandSerpents/States/BssCoilOrbitState.cs:192-219 | Content/NPCs/BloomsandSerpents/States/BssTailSweepState.cs:251-280 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (28 corresponding lines) Content/TimeFreezes/TimeControlReplicationSystem.cs:200 — Content/TimeFreezes/TimeControlReplicationSystem.cs:200-227 | Content/TimeFreezes/TimeControlReplicationSystem.cs:229-257 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (28 corresponding lines) Content/Items/Ranged/SnowQuay.cs:166 — Content/Items/Ranged/SnowQuay.cs:166-193 | Content/Items/Ranged/SnowQuayMK2.cs:135-167 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (28 corresponding lines) Content/PRTTypes/PRT_AccretionDiskImpact.cs:52 — Content/PRTTypes/PRT_AccretionDiskImpact.cs:52-79 | Content/PRTTypes/PRT_GammaImpact.cs:75-102 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (28 corresponding lines) Content/NPCs/BrutalNPCs/BrutalSkeletron/SkeletronDeathCutscene.cs:16 — Content/NPCs/BrutalNPCs/BrutalSkeletron/SkeletronDeathCutscene.cs:16-43 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/PrimeDeathCutscene.cs:17-47 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (28 corresponding lines) Content/NPCs/BrutalNPCs/BrutalGolem/GolemGrabCutscene.cs:25 — Content/NPCs/BrutalNPCs/BrutalGolem/GolemGrabCutscene.cs:25-52 | Content/NPCs/BrutalNPCs/BrutalMoonLord/MLordGrabCutscene.cs:20-52 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (28 corresponding lines) Content/Scenarios/Dungeonworld/Gen/Layers/L1/L1Style.cs:114 — Content/Scenarios/Dungeonworld/Gen/Layers/L1/L1Style.cs:114-141 | Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Palette.cs:123-151 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (28 corresponding lines) Content/Scenarios/Himayo/ToriiShrines/ToriiShrine.cs:130 — Content/Scenarios/Himayo/ToriiShrines/ToriiShrine.cs:130-157 | Content/Scenarios/Kiame/Overlay/OniUmbrellaWorldSpawn.cs:138-170 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (28 corresponding lines) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:178 — Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:178-205 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaReset.cs:207-234 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (28 corresponding lines) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/CultistBossAI.cs:87 — Content/NPCs/BrutalNPCs/BrutalLunaticCultist/CultistBossAI.cs:87-114 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/QueenSlimeAI.cs:72-103 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (5 lines × 6) · ×19
  • Duplicated block (5 lines × 6) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:394 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:394-398 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:387-391 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:497-501 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:465-469 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:503-507 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:481-485 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:394` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:502` calls `RebuildArms` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:399` does not — after which the two agree again for 4 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 (5 lines × 6) Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs:219 — Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs:219-223 | Content/Items/Magic/Everdeeps/EverdeepMaelstrom.cs:343-347 | Content/Items/Magic/Everdeeps/EverdeepRing.cs:373-377 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronSharkTornadoProj.cs:336-340 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronTsunamiWallProj.cs:189-193 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowBreachOmen.cs:96-100 — before extracting anything, compare `Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs` and `Content/Items/Magic/Everdeeps/EverdeepMaelstrom.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs:219` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (5 lines × 6) Common/ShockRingDraw.cs:69 — Common/ShockRingDraw.cs:69-74 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMoonFlare.cs:284-288 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteRingRender.cs:139-144 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteStarSurge.cs:198-202 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistUmbraShade.cs:516-520 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistZodiacRing.cs:187-191 — before extracting anything, compare `Common/ShockRingDraw.cs` and `Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteRingRender.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 6) Content/GameModes/BrutalMobs/Ambience/Duskwatch/PRT_DuskwatchAsh.cs:67 — Content/GameModes/BrutalMobs/Ambience/Duskwatch/PRT_DuskwatchAsh.cs:67-71 | Content/GameModes/BrutalMobs/Ambience/Frostveil/FrostveilPRT.cs:70-75 | Content/GameModes/BrutalMobs/Ambience/Silkcrypt/PRT_SilkcryptLint.cs:64-68 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Rendering/BKSParticles.cs:71-75 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Rendering/QueenBeePRT.cs:78-82 | Content/PRTTypes/PRT_SewageGlob.cs:127-132 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/Duskwatch/PRT_DuskwatchAsh.cs:67` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (5 lines × 6) Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:170 — Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:170-174 | Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarRingOmen.cs:176-180 | Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs:75-79 | Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgSnowShardProj.cs:77-81 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmNutShellProj.cs:96-100 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmSnowballProj.cs:107-111 — before extracting anything, compare `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs` and `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgSnowShardProj.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 51 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:170` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs:82` calls `Lerp`, `Color` and `Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmNutShellProj.cs:105` 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 (5 lines × 6) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:604 — Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:604-609 | Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:479-483 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:513-517 | Content/Industrials/ElectricPowers/MiningMachines/MiningMachineUI.cs:714-718 | Content/Industrials/ElectricPowers/Recyclers/RecyclerUI.cs:440-444 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterUI.cs:477-481 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:604` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 6) Content/Items/Accessories/BrutalRelics/QueenBee/SwarmVortexProj.cs:377 — Content/Items/Accessories/BrutalRelics/QueenBee/SwarmVortexProj.cs:377-382 | Content/Items/Magic/Elysiums/Disciples/BaseDisciple.cs:278-283 | Content/Items/Magic/Elysiums/Revelations/RevelationDomain.cs:131-137 | Content/Items/Magic/Elysiums/Serpents/SnakeConversionWave.cs:202-208 | Content/NPCs/TBUGs/TBUGRiftPortalProj.cs:375-379 | Content/NPCs/Victors/VictorRiftPortalProj.cs:564-568 — before extracting anything, compare `Content/Items/Magic/Elysiums/Revelations/RevelationDomain.cs` and `Content/Items/Magic/Elysiums/Serpents/SnakeConversionWave.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Magic/Elysiums/Disciples/BaseDisciple.cs:285` calls `DrawEmblem`, `ExtraDraw` and `Content/Items/Magic/Elysiums/Revelations/RevelationDomain.cs:138` 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 (5 lines × 6) Content/Items/Melee/CommandersClaw.cs:284 — Content/Items/Melee/CommandersClaw.cs:284-289 | Content/Items/Ranged/Starships/StarshipComet.cs:73-77 | Content/Items/Ranged/Starships/StarshipMeteor.cs:135-139 | Content/Items/Ranged/Starships/StarshipMicroStar.cs:48-52 | Content/Items/Ranged/Starships/StarshipPlanet.cs:146-150 | Content/Items/Ranged/Starships/StarshipPlasmaBolt.cs:65-69 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/CommandersClaw.cs:284` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Ranged/Starships/StarshipComet.cs:70` calls `Sin` and `Content/Items/Ranged/Starships/StarshipMicroStar.cs:46` does not — after which the two agree again for 3 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 (5 lines × 6) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPour.cs:532 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPour.cs:532-536 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPuddle.cs:145-149 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuXiFX.cs:95-99 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuXiaoFX.cs:81-85 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuYuFX.cs:53-57 | Content/LegendWeapon/KikasaLegend/KikasaTeleports/KikasaTeleportProj.cs:355-360 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPour.cs:532` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (5 lines × 6) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeSlash.cs:121 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeSlash.cs:121-125 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangProj.cs:177-181 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailHead.cs:181-185 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipLash.cs:216-220 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoProj.cs:203-207 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshEyeLaser.cs:183-187 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeSlash.cs:121` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshEyeLaser.cs:190` calls `PlaySound` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipLash.cs:223` 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 (5 lines × 6) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:453 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:453-458 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:404-408 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:353-359 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:423-429 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:824-830 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:449-454 — there are 6 copies across 5 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 6 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:453` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 6) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:359 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:359-363 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:500-504 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:360-364 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:935-939 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:464-468 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:412-416 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:359` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:367` calls `PlaySound` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:419` 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 (5 lines × 6) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:748 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:748-753 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:588-593 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:783-787 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:537-542 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:922-927 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:732-737 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 408 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:748` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 6) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:749 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:749-754 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:807-811 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:589-594 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:784-788 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:923-928 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:733-738 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:749` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:805` calls `ShakeViewer` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:783` 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 (5 lines × 6) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1503 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1503-1507 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:1070-1074 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1375-1379 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1561-1565 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonVesselWhip.cs:268-272 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:1174-1178 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1503` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:1076` calls `ShakeViewer` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1508` 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 (5 lines × 6) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1503 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1503-1507 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:1070-1074 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1375-1379 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1561-1565 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1623-1627 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1643-1647 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1503` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:1076` calls `ShakeViewer` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1508` 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 (5 lines × 6) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:1059 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:1059-1063 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1276-1280 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1290-1294 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1344-1348 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1430-1434 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1236-1240 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. 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 (5 lines × 6) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:965 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:965-969 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1402-1406 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:994-998 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1002-1006 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1737-1741 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1745-1749 — there are 6 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 6 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:965` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 6) Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:663 — Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:663-667 | Content/GameModes/GodSmith/Weapons/Broadswords/GsMeowmere.cs:630-634 | Content/GameModes/GodSmith/Weapons/Broadswords/GsStarWrath.cs:270-274 | Content/GameModes/GodSmith/Weapons/Broadswords/GsStarWrath.cs:476-480 | Content/GameModes/GodSmith/Weapons/Broadswords/GsStarfury.cs:130-134 | Content/GameModes/GodSmith/Weapons/Broadswords/GsTheHorsemansBlade.cs:182-186 — there are 6 copies across 5 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 6 sites; resolving a subset leaves the remainder to drift apart. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/GameModes/GodSmith/Weapons/Broadswords/GsStarWrath.cs:277` calls `ShouldUpdatePosition`, `CanDamage` and `Content/GameModes/GodSmith/Weapons/Broadswords/GsStarWrath.cs:482` 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.
D4 · Code Duplication · Duplicated block (6–7 lines × 2) · ×19
  • Duplicated block (6–7 lines × 2) Content/GameModes/BrutalMobs/Ambience/Astralveil/Projectiles/AstralveilSpearMarkProj.cs:146 — Content/GameModes/BrutalMobs/Ambience/Astralveil/Projectiles/AstralveilSpearMarkProj.cs:146-152 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkMortarMarkerProj.cs:94-99 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/Astralveil/Projectiles/AstralveilSpearMarkProj.cs:146` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6–7 lines × 2) Content/GameModes/BrutalMobs/Ambience/Starfall/StarfallAmbience.cs:152 — Content/GameModes/BrutalMobs/Ambience/Starfall/StarfallAmbience.cs:152-158 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionClownBomb.cs:131-136 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/Starfall/StarfallAmbience.cs:152` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6–7 lines × 2) Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomSporeMistTelegraph.cs:166 — Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomSporeMistTelegraph.cs:166-171 | Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomVineWhipOmen.cs:142-148 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomSporeMistTelegraph.cs:166` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6–7 lines × 2) Content/Items/Accessories/BrutalRelics/Twins/TwinPupilOrbiter.cs:527 — Content/Items/Accessories/BrutalRelics/Twins/TwinPupilOrbiter.cs:527-533 | Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemTelegraph.cs:112-117 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/Twins/TwinPupilOrbiter.cs:527` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6–7 lines × 2) Content/Items/Accessories/EmblemOfDread.cs:287 — Content/Items/Accessories/EmblemOfDread.cs:287-292 | Content/Items/Accessories/EyeOfSingularity.cs:300-306 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/EmblemOfDread.cs:287` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6–7 lines × 2) Content/Items/Magic/Pandemoniums/PandemoniumChannel.cs:770 — Content/Items/Magic/Pandemoniums/PandemoniumChannel.cs:770-776 | Content/Items/Ranged/Starships/StarshipMicroGalaxy.cs:77-82 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/Pandemoniums/PandemoniumChannel.cs:770` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6–7 lines × 2) Content/LegendWeapon/HalibutLegend/FishSkills/FishBunny.cs:547 — Content/LegendWeapon/HalibutLegend/FishSkills/FishBunny.cs:547-552 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBunny.cs:710-716 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishBunny.cs:547` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6–7 lines × 2) Content/LegendWeapon/HalibutLegend/FishSkills/FishFrostMinnow.cs:165 — Content/LegendWeapon/HalibutLegend/FishSkills/FishFrostMinnow.cs:165-170 | Content/LegendWeapon/HalibutLegend/FishSkills/FishFrostMinnow.cs:587-593 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishFrostMinnow.cs:165` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6–7 lines × 2) Content/LegendWeapon/HalibutLegend/UI/HalibutHud.cs:394 — Content/LegendWeapon/HalibutLegend/UI/HalibutHud.cs:394-399 | Content/LegendWeapon/HalibutLegend/UI/SkillWheel/HalibutSkillWheel.cs:224-230 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/UI/HalibutHud.cs:394` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6–7 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:588 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:588-594 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:783-788 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 491 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:588` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6–7 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaVaults/KikasaVaultRenderer.cs:175 — Content/LegendWeapon/KikasaLegend/KikasaVaults/KikasaVaultRenderer.cs:175-180 | Content/LegendWeapon/KikasaLegend/UI/Panorama/KikasaPanoramaRenderer.cs:125-131 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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 (6–7 lines × 2) Content/LegendWeapon/SHPCLegend/Modules/Barrel/HypersonicBarrelModule.cs:62 — Content/LegendWeapon/SHPCLegend/Modules/Barrel/HypersonicBarrelModule.cs:62-68 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/RapidBarrelModule.cs:509-514 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/Modules/Barrel/HypersonicBarrelModule.cs:62` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6–7 lines × 2) Content/LegendWeapon/SHPCLegend/Modules/Barrel/MossboundBarrelModule.cs:148 — Content/LegendWeapon/SHPCLegend/Modules/Barrel/MossboundBarrelModule.cs:148-154 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/MossboundBarrelModule.cs:211-216 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/Modules/Barrel/MossboundBarrelModule.cs:148` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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 (6–7 lines × 2) Content/LegendWeapon/SHPCLegend/Modules/Power/ResonanceReactorModule.cs:42 — Content/LegendWeapon/SHPCLegend/Modules/Power/ResonanceReactorModule.cs:42-48 | Content/LegendWeapon/SHPCLegend/Modules/Power/StormCellModule.cs:49-54 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/Modules/Power/ResonanceReactorModule.cs:42` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6–7 lines × 2) Content/LegendWeapon/SHPCLegend/UI/SHPCCyberPanel.cs:141 — Content/LegendWeapon/SHPCLegend/UI/SHPCCyberPanel.cs:141-147 | Content/LegendWeapon/SHPCLegend/UI/SHPCModPanel.cs:90-95 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/UI/SHPCCyberPanel.cs:141` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6–7 lines × 2) Content/NPCs/BloomsandSerpents/Projectiles/BssSandSurgeProj.cs:80 — Content/NPCs/BloomsandSerpents/Projectiles/BssSandSurgeProj.cs:80-86 | Content/NPCs/BloomsandSerpents/Projectiles/BssSandSurgeProj.cs:87-92 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BloomsandSerpents/Projectiles/BssSandSurgeProj.cs:80` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6–7 lines × 2) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofGrabTongueProj.cs:202 — Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofGrabTongueProj.cs:202-207 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofTongueLashProj.cs:145-151 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofGrabTongueProj.cs:202` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6–7 lines × 2) Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraSporeSowState.cs:59 — Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraSporeSowState.cs:59-65 | Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraVineLatticeState.cs:229-234 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraSporeSowState.cs:59` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (6–7 lines × 2) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:677 — Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:677-683 | Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:1361-1366 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:677` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Edited copies of one member (4 members, 11+ corresponding lines) · ×18
  • Edited copies of one member (4 members, 11+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaArmsProfiler.cs:547 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaArmsProfiler.cs:547-557 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaArmsProfiler.cs:561-572 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaArmsProfiler.cs:701-715 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaArmsProfiler.cs:750-763 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 11+ corresponding lines) Content/Items/Stones/Marbles/MarbleEffects.cs:64 — Content/Items/Stones/Marbles/MarbleEffects.cs:64-74 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaCavitationOrb.cs:128-139 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpCavitationBubble.cs:133-144 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpVoltBubble.cs:198-210 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 11+ corresponding lines) Content/GameModes/BrutalMobs/Ambience/Nyxdepth/Projectiles/NyxdepthSinkColumnProj.cs:236 — Content/GameModes/BrutalMobs/Ambience/Nyxdepth/Projectiles/NyxdepthSinkColumnProj.cs:236-254 | Content/GameModes/BrutalMobs/Ambience/Stratos/Projectiles/StratosUpdraftProj.cs:166-178 | Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomSporePatchZone.cs:141-151 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesIceSlickZone.cs:188-198 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 11+ corresponding lines) Content/Items/BloomArsenal.cs:166 — Content/Items/BloomArsenal.cs:166-179 | Content/Items/Melee/BudPiercers/BudPiercer.cs:71-85 | Content/Items/Summon/BloomCallers/BloomCallerSprout.cs:416-426 | Content/NPCs/BloomsandSerpents/Projectiles/BssNeedleProj.cs:32-44 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 11+ corresponding lines) Content/UIs/UIEffect/DraedonDataPRT.cs:17 — Content/UIs/UIEffect/DraedonDataPRT.cs:17-29 | Content/UIs/UIEffect/NeonMaidPRT.cs:19-31 | Content/UIs/UIEffect/SeaStarPRT.cs:26-36 | Content/UIs/UIEffect/StarStreamPRT.cs:19-32 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 11+ corresponding lines) Content/GameModes/GodSmith/Armors/Reset/GsMoltenArmor.cs:101 — Content/GameModes/GodSmith/Armors/Reset/GsMoltenArmor.cs:101-111 | Content/GameModes/GodSmith/Armors/Reset/GsOreArmorsHardmode.cs:291-301 | Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemSunBolt.cs:59-69 | Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemSunMortar.cs:90-100 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 11+ corresponding lines) Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserBoltProj.cs:91 — Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserBoltProj.cs:91-101 | Content/GameModes/BrutalMobs/Martians/Projectiles/MrtReinforceSignalProj.cs:79-90 | Content/GameModes/BrutalMobs/Martians/Projectiles/MrtScutlixHeavyBolt.cs:74-84 | Content/GameModes/BrutalMobs/Martians/Projectiles/MrtWrenchProj.cs:126-137 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 11+ corresponding lines) Content/GameModes/BrutalMobs/Ambience/Astralveil/Projectiles/AstralveilBloomProj.cs:146 — Content/GameModes/BrutalMobs/Ambience/Astralveil/Projectiles/AstralveilBloomProj.cs:146-156 | Content/NPCs/BloomsandSerpents/Projectiles/BssDustDevilProj.cs:152-162 | Content/NPCs/BloomsandSerpents/Projectiles/BssSandSurgeProj.cs:109-120 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSTideWaveProj.cs:173-185 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 11+ corresponding lines) Content/UIs/UIEffect/AshPRT.cs:18 — Content/UIs/UIEffect/AshPRT.cs:18-28 | Content/UIs/UIEffect/AshPRT.cs:30-40 | Content/UIs/UIEffect/EmberPRT.cs:28-39 | Content/UIs/UIEffect/EmberPRT.cs:41-52 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 11+ corresponding lines) Content/GameModes/GodSmith/Weapons/Broadswords/GsBladetongue.cs:165 — Content/GameModes/GodSmith/Weapons/Broadswords/GsBladetongue.cs:165-176 | Content/GameModes/GodSmith/Weapons/Broadswords/GsChlorophyteClaymore.cs:210-220 | Content/GameModes/GodSmith/Weapons/Broadswords/GsChlorophyteSaber.cs:146-156 | Content/GameModes/GodSmith/Weapons/Broadswords/GsSeedler.cs:237-247 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 11+ corresponding lines) Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:62 — Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:62-76 | Content/Items/Accessories/BrutalRelics/Deerclops/WhiteoutBurstProj.cs:39-52 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteStarSurge.cs:224-234 | Content/Items/Melee/HeartcarverHeart.cs:290-302 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 11+ corresponding lines) Content/NPCs/BloomsandSerpents/BssHead.cs:376 — Content/NPCs/BloomsandSerpents/BssHead.cs:376-386 | Content/NPCs/FestersandSerpents/FssHead.cs:330-340 | Content/NPCs/ScrapCommanders/ScrapCommander.cs:296-306 | Content/NPCs/SeaShrimp/SeaShrimpBoss.cs:238-248 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 11+ corresponding lines) Content/GameModes/GodSmith/Weapons/MagicCataclysm/Projectiles/GsOrogenyDirector.cs:39 — Content/GameModes/GodSmith/Weapons/MagicCataclysm/Projectiles/GsOrogenyDirector.cs:39-51 | Content/GameModes/GodSmith/Weapons/MagicConduit/GsLastPrism.cs:114-124 | Content/GameModes/GodSmith/Weapons/MagicConduit/GsLastPrism.cs:211-221 | Content/GameModes/GodSmith/Weapons/MagicMorph/Projectiles/GsMorphBurstProj.cs:38-50 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 11+ corresponding lines) Content/NPCs/BloomsandSerpents/BssHead.cs:468 — Content/NPCs/BloomsandSerpents/BssHead.cs:468-478 | Content/NPCs/FestersandSerpents/FssHead.cs:418-428 | Content/NPCs/ScrapCommanders/ScrapCommander.cs:382-392 | Content/NPCs/SeaShrimp/SeaShrimpBoss.cs:354-364 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 11+ corresponding lines) Content/Items/Accessories/BrutalRelics/KingSlime/KingsVerdictWave.cs:33 — Content/Items/Accessories/BrutalRelics/KingSlime/KingsVerdictWave.cs:33-46 | Content/Items/Magic/NeutronWands/NeutronStarquake.cs:42-55 | Content/Items/Stones/Granites/GraniteFlower.cs:246-256 | Content/Items/Stones/Marbles/MarbleEffects.cs:23-33 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 11+ corresponding lines) Content/GameModes/GodSmith/Weapons/Boomerangs/GsShroomerang.cs:59 — Content/GameModes/GodSmith/Weapons/Boomerangs/GsShroomerang.cs:59-69 | Content/Items/Accessories/BrutalRelics/BrainOfCthulhu/MirrorheartPulse.cs:44-57 | Content/Items/Ranged/CrystalDimming.cs:273-283 | Content/Items/Ranged/UniversalFrost.cs:297-307 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 11+ corresponding lines) Content/GameModes/GodSmith/Weapons/Specials/GsCoinGun.cs:103 — Content/GameModes/GodSmith/Weapons/Specials/GsCoinGun.cs:103-113 | Content/Items/Melee/SporeboundRoller.cs:130-141 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeSlash.cs:47-59 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunBullet.cs:59-74 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 11+ corresponding lines) Content/GameModes/BrutalMobs/Ambience/Rimehollow/Projectiles/RimehollowIcicleProj.cs:82 — Content/GameModes/BrutalMobs/Ambience/Rimehollow/Projectiles/RimehollowIcicleProj.cs:82-93 | Content/Items/Accessories/BrutalRelics/Skeletron/SoulbindingGhostHand.cs:60-73 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistPlanetProj.cs:112-124 | Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraPetalWave.cs:34-44 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (6 lines × 6) · ×18
  • Duplicated block (6 lines × 6) Content/Scenarios/Dungeonworld/DungeonworldGuard.cs:83 — Content/Scenarios/Dungeonworld/DungeonworldGuard.cs:83-88 | Content/Scenarios/Hadalworld/HadalworldGuard.cs:83-88 | Content/Scenarios/Kiame/KiameGuard.cs:83-88 | Content/Scenarios/Kiyume/KiyumeGuard.cs:83-88 | Content/Scenarios/OldNet/OldNetGuard.cs:83-88 | Content/Scenarios/Shepel/CybCourses/CybCourseWorldGuard.cs:87-92 — before extracting anything, compare `Content/Scenarios/Dungeonworld/DungeonworldGuard.cs` and `Content/Scenarios/Hadalworld/HadalworldGuard.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/DungeonworldGuard.cs:83` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 6) Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdCastOmen.cs:229 — Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdCastOmen.cs:229-234 | Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdHammerConeOmen.cs:138-143 | Content/GameModes/BrutalMobs/EvilBiome/Projectiles/MummyWrapOmen.cs:97-102 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmYetiConeOmen.cs:153-158 | Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomVineWhipOmen.cs:106-111 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandConeTelegraph.cs:160-165 — before extracting anything, compare `Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdHammerConeOmen.cs` and `Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmYetiConeOmen.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdCastOmen.cs:229` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdCastOmen.cs:226` calls `TryGetRow` and `Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdHammerConeOmen.cs:137` 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 (6 lines × 6) Content/Items/Ranged/PallbearerAssets.cs:141 — Content/Items/Ranged/PallbearerAssets.cs:141-146 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDoubleCodVFX.cs:33-38 | Content/LegendWeapon/HalibutLegend/FishSkills/FishJewelVFX.cs:55-60 | Content/LegendWeapon/HalibutLegend/FishSkills/FishNeonTetraVFX.cs:46-51 | Content/LegendWeapon/HalibutLegend/FishSkills/FishSwarmVFX.cs:41-46 | Content/LegendWeapon/HalibutLegend/FishSkills/FishTropicalBarracudaVFX.cs:40-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/HalibutLegend/FishSkills/FishNeonTetraVFX.cs:52` calls `SetValue`, `Clamp` and `Content/Items/Ranged/PallbearerAssets.cs:147` does not — after which the two agree again for 3 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 (6 lines × 6) Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs:142 — Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs:142-147 | Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteDiveOmen.cs:146-151 | Content/GameModes/BrutalMobs/NightPack/Projectiles/NightDiveOmen.cs:159-164 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkChargeOmen.cs:171-176 | Content/GameModes/BrutalMobs/Sky/Projectiles/SkyGaleDiveOmen.cs:140-145 | Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornDiveLane.cs:142-147 — before extracting anything, compare `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs` and `Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteDiveOmen.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs:142` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteDiveOmen.cs:152` calls `Color` and `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs:148` 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 (6 lines × 6) Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:331 — Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:331-336 | Content/Items/Magic/CommandersStaff.cs:361-366 | Content/Items/Melee/DestroyersBlade.cs:689-694 | Content/Items/Melee/DestroyersBladeEXs/DestroyersBeamEX.cs:173-178 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:285-290 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:234-239 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:331` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6 lines × 6) Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawWormProj.cs:591 — Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawWormProj.cs:591-596 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowBreachOmen.cs:93-98 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowDevourOmen.cs:127-132 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowGeyserProj.cs:199-204 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Rendering/EocRenderHelper.cs:395-400 | Content/NPCs/FestersandSerpents/Projectiles/FssGeyserColumn.cs:203-208 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times.
  • Duplicated block (6 lines × 6) Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawWormProj.cs:592 — Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawWormProj.cs:592-597 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidPool.cs:113-119 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowDevourOmen.cs:128-133 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowGeyserProj.cs:200-205 | Content/NPCs/FestersandSerpents/Projectiles/FssGeyserColumn.cs:204-209 | Content/NPCs/FestersandSerpents/Projectiles/FssIchorPool.cs:233-239 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawWormProj.cs:592` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 6) Content/Items/Accessories/EmblemOfDread.cs:141 — Content/Items/Accessories/EmblemOfDread.cs:141-146 | Content/Items/Accessories/EyeOfSingularity.cs:97-102 | Content/Items/Melee/NeutronGlaive.cs:1253-1258 | Content/Items/Melee/NeutronScythe.cs:323-328 | Content/Items/Ranged/NeutronBows/EXNeutronExplosionRanged.cs:30-35 | Content/Items/Ranged/NeutronBows/NeutronExplosionRanged.cs:29-34 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/EmblemOfDread.cs:141` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6 lines × 6) Content/Items/Magic/WheezingWyrms/WyrmfirePRT.cs:162 — Content/Items/Magic/WheezingWyrms/WyrmfirePRT.cs:162-167 | Content/Items/Melee/CursedflameBloodfists/CursedflamePRT.cs:118-123 | Content/Items/Melee/DawnshatterAzures/DawnshatterPRT.cs:72-77 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCursedVFX.cs:250-255 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDemonicHell.cs:764-769 | Content/PRTTypes/PRT_PallbearerEmber.cs:63-68 — before extracting anything, compare `Content/Items/Magic/WheezingWyrms/WyrmfirePRT.cs` and `Content/Items/Melee/CursedflameBloodfists/CursedflamePRT.cs` 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 6) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1056 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1056-1061 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaMinionDrownFX.cs:494-499 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaPlayerDrownFX.cs:530-535 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaScourgeFX.cs:791-796 | Content/Wraiths/Deaths/Performances/HandSeizurePerformance.cs:325-330 | Content/Wraiths/Projectiles/GhostHandProj.cs:962-967 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1056` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6 lines × 6) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1108 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1108-1113 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1249-1254 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:994-999 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:820-825 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:1063-1068 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1389-1394 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 598 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1108` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 6) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:667 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:667-672 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:1076-1081 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:878-883 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1547-1552 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:672-677 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:1085-1090 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs` as WHOLE FILES: this scan already matched 48 separate duplicated blocks between them, totalling at least 508 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:667` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:673` calls `SandTrickle`, `IsFlowerSeg`, `NextBool` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:884` 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 (6 lines × 6) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:1055 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:1055-1060 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1501-1506 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:1068-1073 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1373-1378 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1436-1441 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1621-1626 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:1055` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:1053` calls `SandBurst` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1499` does not — after which the two agree again for 3 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 (6 lines × 6) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:1171 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:1171-1176 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1392-1397 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1459-1464 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1516-1521 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1647-1652 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1412-1417 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:1171` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 6) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:837 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:837-842 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1303-1308 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonOrb.cs:144-149 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeBloodBee.cs:167-172 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1197-1202 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeStinger.cs:219-224 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:837` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 6) Content/Scenarios/Shepel/Dialogues/Situational/ShepelDungeonDialogue.cs:11 — Content/Scenarios/Shepel/Dialogues/Situational/ShepelDungeonDialogue.cs:11-16 | Content/Scenarios/Shepel/Dialogues/Situational/ShepelFirstNightDialogue.cs:13-18 | Content/Scenarios/Shepel/Dialogues/Situational/ShepelJungleDialogue.cs:11-16 | Content/Scenarios/Shepel/Dialogues/Situational/ShepelOceanDialogue.cs:11-16 | Content/Scenarios/Shepel/Dialogues/Situational/ShepelSnowBiomeDialogue.cs:11-16 | Content/Scenarios/Shepel/Dialogues/Situational/ShepelUnderworldDialogue.cs:11-16 — 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 6 call sites, so a change lands once.
  • Duplicated block (6 lines × 6) Content/Items/Melee/DestroyersBlade.cs:471 — Content/Items/Melee/DestroyersBlade.cs:471-476 | Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:609-614 | Content/Items/Melee/DragonsScaleGreatsword.cs:497-502 | Content/Items/Melee/EnergySword.cs:508-513 | Content/Items/Melee/RebelBlade.cs:534-539 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:479-484 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times.
  • Duplicated block (6 lines × 6) Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolRoomSealTile.cs:43 — Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolRoomSealTile.cs:43-49 | Content/Scenarios/OldNet/Tiles/OldNetBulkheadTile.cs:32-37 | Content/Scenarios/OldNet/Tiles/OldNetCacheTile.cs:88-93 | Content/Scenarios/OldNet/Tiles/OldNetEscrowTile.cs:120-125 | Content/Scenarios/OldNet/Tiles/OldNetLedgerDockTile.cs:75-80 | Content/Scenarios/OldNet/Tiles/OldNetSealGateTile.cs:32-37 — before extracting anything, compare `Content/Scenarios/OldNet/Tiles/OldNetCacheTile.cs` and `Content/Scenarios/OldNet/Tiles/OldNetEscrowTile.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 31 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolRoomSealTile.cs:39` calls `CanExplode`, `CanKillTile` and `Content/Scenarios/OldNet/Tiles/OldNetBulkheadTile.cs:30` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Edited copy of a member (39 corresponding lines) · ×17
  • Edited copy of a member (39 corresponding lines) Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerMotionFX.cs:195 — Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerMotionFX.cs:195-233 | Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerDespawnState.cs:207-254 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (39 corresponding lines) Content/GameModes/BrutalMobs/Ambience/Tidecall/Projectiles/TidecallRogueWaveProj.cs:338 — Content/GameModes/BrutalMobs/Ambience/Tidecall/Projectiles/TidecallRogueWaveProj.cs:338-376 | Content/Scenarios/Dungeonworld/NPCs/UndrownedTideWave.cs:126-175 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (39 corresponding lines) Content/NPCs/TBUGs/TBUGRiftPortalProj.cs:345 — Content/NPCs/TBUGs/TBUGRiftPortalProj.cs:345-383 | Content/NPCs/Victors/VictorRiftPortalProj.cs:530-569 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (39 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishBloodyManowarVFX.cs:91 — Content/LegendWeapon/HalibutLegend/FishSkills/FishBloodyManowarVFX.cs:91-130 | Content/LegendWeapon/HalibutLegend/FishSkills/FishHoneyVFX.cs:71-109 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (39 corresponding lines) Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:787 — Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:787-837 | Content/Items/Modifys/RBloodButcherer.cs:771-809 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (39 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaWisps/KikasaWispBurnNPC.cs:48 — Content/LegendWeapon/KikasaLegend/KikasaWisps/KikasaWispBurnNPC.cs:48-93 | Content/Scenarios/Dungeonworld/NPCs/Elites/DrownedTurnkey.cs:772-810 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (39 corresponding lines) Content/GameModes/BrutalMobs/Sky/Projectiles/SkyGaleDiveOmen.cs:75 — Content/GameModes/BrutalMobs/Sky/Projectiles/SkyGaleDiveOmen.cs:75-113 | Content/GameModes/BrutalMobs/Temple/Projectiles/TempleDiveOmen.cs:73-127 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (39 corresponding lines) Content/HackTimes/Protocols/TilePhase.cs:35 — Content/HackTimes/Protocols/TilePhase.cs:35-77 | Content/HackTimes/Protocols/TilePhase.cs:124-162 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (39 corresponding lines) Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:324 — Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:324-362 | Content/LegendWeapon/OnikiriLegend/OniZanshinSlashs/OniZanshinSlash.cs:412-451 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (39 corresponding lines) Content/Items/Stones/Marbles/MarbleClub.cs:576 — Content/Items/Stones/Marbles/MarbleClub.cs:576-614 | Content/Items/Stones/Marbles/MarbleHuntingKnife.cs:392-431 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (39 corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1372 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1372-1410 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1279-1319 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (39 corresponding lines) Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmAimLaneOmen.cs:83 — Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmAimLaneOmen.cs:83-126 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmStrafeLaneProj.cs:60-98 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (39 corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1066 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1066-1104 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:829-867 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (39 corresponding lines) Content/Industrials/Generator/Biomass/BiomassGenerator.cs:186 — Content/Industrials/Generator/Biomass/BiomassGenerator.cs:186-224 | Content/Industrials/Generator/Thermal/ThermalGenerator.cs:143-181 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (39 corresponding lines) Content/NPCs/TBUGs/TBUGRiftPortalProj.cs:124 — Content/NPCs/TBUGs/TBUGRiftPortalProj.cs:124-162 | Content/NPCs/Victors/VictorRiftPortalProj.cs:153-195 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (39 corresponding lines) Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.Net.cs:577 — Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.Net.cs:577-615 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.Net.cs:618-657 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (39 corresponding lines) Content/Cyberwares/Skills/CyberwareSkillRadialController.cs:288 — Content/Cyberwares/Skills/CyberwareSkillRadialController.cs:288-334 | Content/LegendWeapon/HalibutLegend/UI/SkillWheel/HalibutWheelController.cs:142-180 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) · ×17
  • Edited copies of one member (3 members, 17+ corresponding lines) Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:704 — Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:704-720 | Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:816-848 | Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:850-882 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 17+ corresponding lines) Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs:226 — Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs:226-242 | Content/Items/Magic/Everdeeps/EverdeepMaelstrom.cs:350-366 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronSharkTornadoProj.cs:343-359 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 17+ corresponding lines) Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:393 — Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:393-409 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:421-439 | Content/Industrials/ElectricPowers/Recyclers/RecyclerUI.cs:399-415 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 17+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:974 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:974-990 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:935-951 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:968-984 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 17+ corresponding lines) Content/Items/Melee/DragonsScaleGreatsword.cs:632 — Content/Items/Melee/DragonsScaleGreatsword.cs:632-648 | Content/Items/Melee/DragonsScaleGreatsword.cs:836-858 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:985-1007 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 17+ corresponding lines) Content/Scenarios/Dungeonworld/NPCs/OverseerSlagGlob.cs:251 — Content/Scenarios/Dungeonworld/NPCs/OverseerSlagGlob.cs:251-268 | Content/Scenarios/Dungeonworld/NPCs/OverseerVfx.cs:305-321 | Content/Scenarios/Dungeonworld/NPCs/UndrownedTideWave.cs:243-262 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 17+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1133 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1133-1152 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1488-1505 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:917-933 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 17+ corresponding lines) Content/Scenarios/OldNet/Renders/OldNetTileFXRender.cs:322 — Content/Scenarios/OldNet/Renders/OldNetTileFXRender.cs:322-344 | Content/Scenarios/OldNet/Renders/OldNetTileFXRender.cs:346-366 | Content/Scenarios/OldNet/Renders/OldNetTileFXRender.cs:368-384 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 17+ corresponding lines) Content/Items/Placeable/HoChaMeditatorItem.cs:41 — Content/Items/Placeable/HoChaMeditatorItem.cs:41-57 | Content/Items/Tools/SirenMusicalBox.cs:59-75 | Content/Tiles/BloodAltars/BloodAltar.cs:32-49 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 17+ corresponding lines) Content/Narrative/Presentation/Skins/Common/SkinDrawUtil.cs:23 — Content/Narrative/Presentation/Skins/Common/SkinDrawUtil.cs:23-39 | Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersUIs/OceanRaidersRenderer.cs:224-240 | Content/Scenarios/OldDuke/OldDukeShops/OldDukeShopRenderer.cs:173-190 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 17+ corresponding lines) Content/Items/Magic/Pandemoniums/PandemoniumChannel.cs:867 — Content/Items/Magic/Pandemoniums/PandemoniumChannel.cs:867-883 | Content/Items/Magic/Pandemoniums/PandemoniumCircle.cs:347-364 | Content/Items/Magic/Pandemoniums/PandemoniumRSkill.cs:481-497 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 17+ corresponding lines) Content/Industrials/ElectricPowers/HealingStations/HealStation.cs:29 — Content/Industrials/ElectricPowers/HealingStations/HealStation.cs:29-45 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVat.cs:31-47 | Content/Industrials/ElectricPowers/Sundials/ElectricSundial.cs:29-45 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 17+ corresponding lines) Content/Industrials/ElectricPowers/ShieldGenerators/ShieldGenerator.cs:29 — Content/Industrials/ElectricPowers/ShieldGenerators/ShieldGenerator.cs:29-45 | Content/Industrials/ElectricPowers/Turrets/CryoTurrets/CryoTurret.cs:29-45 | Content/Industrials/ElectricPowers/WeatherControllers/WeatherController.cs:29-45 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 17+ corresponding lines) Content/GameModes/GodSmith/Prefixes/Accessory/GodSmithSwiftFootEndow.cs:48 — Content/GameModes/GodSmith/Prefixes/Accessory/GodSmithSwiftFootEndow.cs:48-64 | Content/GameModes/GodSmith/Prefixes/Offense/GodSmithEchoSlashEndow.cs:46-62 | Content/GameModes/GodSmith/Prefixes/Ranged/GodSmithRicochetEndow.cs:53-75 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 17+ corresponding lines) Content/QuestLogs/QLNodes/CalamityBiomeQuests.cs:118 — Content/QuestLogs/QLNodes/CalamityBiomeQuests.cs:118-136 | Content/QuestLogs/QLNodes/CalamityMaterialQuests.cs:84-100 | Content/QuestLogs/QLNodes/CalamityMaterialQuests.cs:112-129 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 17+ corresponding lines) Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzBeamProj.cs:74 — Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzBeamProj.cs:74-91 | Content/Items/Accessories/BrutalRelics/Twins/TwinPupilTetherBeam.cs:91-107 | Content/LegendWeapon/SHPCLegend/Modules/Frame/VolatileFrameModule.cs:485-504 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 17+ corresponding lines) Content/Items/Melee/StormGoddessSpears/StormArc.cs:126 — Content/Items/Melee/StormGoddessSpears/StormArc.cs:126-142 | Content/Items/Melee/StormGoddessSpears/StormArc.cs:145-161 | Content/LegendWeapon/HalibutLegend/FishSkills/FishMud.cs:625-642 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×17
  • Duplicated block (19 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:503 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:503-521 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:467-485 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs` as WHOLE FILES: this scan already matched 78 separate duplicated blocks between them, totalling at least 968 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:503` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19 lines × 2) Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:164 — Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:164-182 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpJetBeam.cs:188-206 — before extracting anything, compare `Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs` and `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpJetBeam.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:164` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19 lines × 2) Content/MainMenus/Himayo/HimayoMenuButtons.cs:200 — Content/MainMenus/Himayo/HimayoMenuButtons.cs:200-218 | Content/MainMenus/Shenyo/ShenyoMenuButtons.cs:202-220 — before extracting anything, compare `Content/MainMenus/Himayo/HimayoMenuButtons.cs` and `Content/MainMenus/Shenyo/ShenyoMenuButtons.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 174 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/MainMenus/Himayo/HimayoMenuButtons.cs:200` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19 lines × 2) Content/MainMenus/Himayo/HimayoMenuOverride.cs:176 — Content/MainMenus/Himayo/HimayoMenuOverride.cs:176-194 | Content/MainMenus/Shenyo/ShenyoMenuOverride.cs:140-158 — before extracting anything, compare `Content/MainMenus/Himayo/HimayoMenuOverride.cs` and `Content/MainMenus/Shenyo/ShenyoMenuOverride.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/MainMenus/Himayo/HimayoMenuOverride.cs:176` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19 lines × 2) Content/NPCs/TBUGs/TBUGRiftPortalProj.cs:361 — Content/NPCs/TBUGs/TBUGRiftPortalProj.cs:361-379 | Content/NPCs/Victors/VictorRiftPortalProj.cs:550-568 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (19 lines × 2) Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSim.cs:276 — Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSim.cs:276-294 | Content/Scenarios/Kiyume/Fog/KiyumeFogSim.cs:399-417 — before extracting anything, compare `Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSim.cs` and `Content/Scenarios/Kiyume/Fog/KiyumeFogSim.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 174 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSim.cs:276` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19 lines × 2) Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs:43 — Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs:43-61 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmPresentShellProj.cs:41-59 — before extracting anything, compare `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs` and `Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmPresentShellProj.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (19 lines × 2) Content/HackTimes/HackTimeNetSync.cs:1115 — Content/HackTimes/HackTimeNetSync.cs:1115-1133 | Content/HackTimes/HackTimeNetSync.cs:1144-1167 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `record` to `HackQueueSnapshotRecord` in one and `HackEffectSnapshotRecord` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (19 lines × 2) Content/Industrials/ElectricPowers/Collectors/CollectorArm.cs:858 — Content/Industrials/ElectricPowers/Collectors/CollectorArm.cs:858-876 | Content/Industrials/ElectricPowers/Lumberjacks/LumberjackSaw.cs:712-730 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (19 lines × 2) Content/Items/Ranged/RaiderGun.cs:360 — Content/Items/Ranged/RaiderGun.cs:360-378 | Content/Items/Ranged/RaiderGun.cs:433-451 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Ranged/RaiderGun.cs:360` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:972 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:972-990 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:970-988 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs` as WHOLE FILES: this scan already matched 70 separate duplicated blocks between them, totalling at least 835 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:972` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19 lines × 2) Content/LegendWeapon/KikasaLegend/UI/ServantWheel/KikasaServantWheelController.cs:45 — Content/LegendWeapon/KikasaLegend/UI/ServantWheel/KikasaServantWheelController.cs:45-63 | Content/LegendWeapon/SHPCLegend/UI/DomainWheel/SHPCDomainWheelController.cs:39-57 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/UI/ServantWheel/KikasaServantWheelController.cs` and `Content/LegendWeapon/SHPCLegend/UI/DomainWheel/SHPCDomainWheelController.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 92 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (19 lines × 2) Content/NPCs/BossNetMotion.cs:93 — Content/NPCs/BossNetMotion.cs:93-111 | Content/NPCs/BrutalNPCs/BrutalPlantera/Core/PlanteraNetSmoother.cs:52-70 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (19 lines × 2) Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraFrenzyPounceState.cs:48 — Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraFrenzyPounceState.cs:48-66 | Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraGrapplePounceState.cs:48-66 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraFrenzyPounceState.cs` and `Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraGrapplePounceState.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 70 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 (19 lines × 2) Content/Scenarios/Dungeonworld/UI/DungeonworldTransitionGate.cs:61 — Content/Scenarios/Dungeonworld/UI/DungeonworldTransitionGate.cs:61-79 | Content/Scenarios/Hadalworld/UI/HadalworldTransitionGate.cs:60-78 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/UI/DungeonworldTransitionGate.cs:61` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19 lines × 2) Content/Scenarios/Kiyume/Gen/KiyumeMicroSites.cs:508 — Content/Scenarios/Kiyume/Gen/KiyumeMicroSites.cs:508-526 | Content/Scenarios/Kiyume/Gen/KiyumeShrine.cs:431-449 — 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 (19 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:150 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:150-168 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:144-162 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs` and `Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 216 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:150` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (14 lines × 3) · ×17
  • Duplicated block (14 lines × 3) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsCombinedAttackState.cs:69 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsCombinedAttackState.cs:69-82 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsCrossDashState.cs:64-77 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsTetherSweepState.cs:69-82 — 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 (14 lines × 3) Content/EntrustManager/Styles/DraedonManagerStyle.cs:436 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:436-449 | Content/EntrustManager/Styles/ForestManagerStyle.cs:445-458 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:434-447 — before extracting anything, compare `Content/EntrustManager/Styles/DraedonManagerStyle.cs` and `Content/EntrustManager/Styles/ForestManagerStyle.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 334 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 (14 lines × 3) Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:109 — Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:109-122 | Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:146-159 | Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:183-196 — 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 (14 lines × 3) Content/Scenarios/Kiyume/Ambience/KiyumeCrowFlight.cs:300 — Content/Scenarios/Kiyume/Ambience/KiyumeCrowFlight.cs:300-313 | Content/Scenarios/Kiyume/Ambience/KiyumeCrowRoost.cs:453-466 | Content/Scenarios/Kiyume/Fog/KiyumeHoundShade.cs:150-163 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Scenarios/Kiyume/Ambience/KiyumeCrowRoost.cs:468` calls `foreach` and `Content/Scenarios/Kiyume/Ambience/KiyumeCrowFlight.cs:315` does not — after which the two agree again for 3 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 × 3) Content/EntrustManager/Styles/DraedonManagerStyle.cs:266 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:266-279 | Content/EntrustManager/Styles/ForestManagerStyle.cs:271-284 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:260-273 — before extracting anything, compare `Content/EntrustManager/Styles/DraedonManagerStyle.cs` and `Content/EntrustManager/Styles/ForestManagerStyle.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 334 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/EntrustManager/Styles/DraedonManagerStyle.cs:266` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 3) Content/GameModes/GodSmith/Weapons/Boomerangs/GsLightDisc.cs:63 — Content/GameModes/GodSmith/Weapons/Boomerangs/GsLightDisc.cs:63-76 | Content/GameModes/GodSmith/Weapons/Boomerangs/GsSergeantUnitedShield.cs:66-79 | Content/GameModes/GodSmith/Weapons/Boomerangs/GsWoodenBoomerang.cs:58-71 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/GameModes/GodSmith/Weapons/Boomerangs/GsSergeantUnitedShield.cs:81` calls `OnCatch`, `IsOwnedByLocalPlayer` and `Content/GameModes/GodSmith/Weapons/Boomerangs/GsLightDisc.cs:77` 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 × 3) Content/GameModes/GodSmith/Weapons/SummonSentries/Schemes/GsFlameburstTowers.cs:65 — Content/GameModes/GodSmith/Weapons/SummonSentries/Schemes/GsFlameburstTowers.cs:65-78 | Content/GameModes/GodSmith/Weapons/SummonSentries/Schemes/GsFrostHydraStaff.cs:54-67 | Content/GameModes/GodSmith/Weapons/SummonSentries/Schemes/GsLightningAuras.cs:61-74 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/SummonSentries/Schemes/GsFlameburstTowers.cs:65` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (14 lines × 3) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:417 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:417-430 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:344-357 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:422-435 — before extracting anything, compare `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs` and `Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 270 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:417` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs:218 — Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs:218-231 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainRender.cs:233-246 | Content/Scenarios/Kiame/KiameWakeResetRender.cs:213-226 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (14 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:452 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:452-465 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:450-463 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:415-428 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs` as WHOLE FILES: this scan already matched 75 separate duplicated blocks between them, totalling at least 912 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (14 lines × 3) Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:308 — Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:308-321 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleCut.cs:356-369 | Content/LegendWeapon/OnikiriLegend/OniZanshinSlashs/OniZanshinSlash.cs:396-409 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:308` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 3) Content/Items/Magic/Pandemoniums/PandemoniumFirePillar.cs:151 — Content/Items/Magic/Pandemoniums/PandemoniumFirePillar.cs:151-164 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:504-517 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:804-817 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/Pandemoniums/PandemoniumFirePillar.cs:151` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:899 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:899-912 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:860-873 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:893-906 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs` as WHOLE FILES: this scan already matched 78 separate duplicated blocks between them, totalling at least 968 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (14 lines × 3) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:247 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:247-260 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:207-220 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:228-241 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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 (14 lines × 3) Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerShockwave.cs:87 — Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerShockwave.cs:87-100 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSShockwaveProj.cs:114-127 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/TwinsSupernovaBlast.cs:108-121 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (14 lines × 3) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:467 — Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:467-480 | Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:464-477 | Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:508-521 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (14 lines × 3) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1167 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1167-1180 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:985-998 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1173-1186 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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.
D4 · Code Duplication · Duplicated block (13 lines × 3) · ×17
  • Duplicated block (13 lines × 3) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs:95 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs:95-107 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeHeatRay.cs:94-106 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeSkullBeamProj.cs:92-104 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs` and `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeHeatRay.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs:95` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeSkullBeamProj.cs:108` calls `RequestShake` and `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs:110` 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 (13 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:550 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:550-562 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:556-568 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:546-558 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs` as WHOLE FILES: this scan already matched 75 separate duplicated blocks between them, totalling at least 912 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:715 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:715-727 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:731-743 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:677-689 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs` as WHOLE FILES: this scan already matched 75 separate duplicated blocks between them, totalling at least 912 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:715` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 3) Content/NPCs/BrutalNPCs/BrutalGolem/GolemBodyAI.cs:354 — Content/NPCs/BrutalNPCs/BrutalGolem/GolemBodyAI.cs:354-366 | Content/NPCs/BrutalNPCs/BrutalSkeletron/SkeletronHeadAI.cs:304-316 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/HeadPrimeAI.cs:662-674 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalGolem/GolemBodyAI.cs:354` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 3) Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineTP.cs:384 — Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineTP.cs:384-396 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterTP.cs:541-553 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterTP.cs:569-581 — 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 (13 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomain.cs:143 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomain.cs:143-155 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomain.cs:121-133 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Cyberspace.cs:125-137 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomain.cs:143` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 3) Content/Scenarios/Dungeonworld/NPCs/GaolDormantSkull.cs:55 — Content/Scenarios/Dungeonworld/NPCs/GaolDormantSkull.cs:55-67 | Content/Scenarios/Dungeonworld/NPCs/OverseerDormantRig.cs:76-88 | Content/Scenarios/Dungeonworld/NPCs/UndrownedThrone.cs:82-94 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/NPCs/GaolDormantSkull.cs:55` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 3) Content/GameModes/GodSmith/Prefixes/Accessory/GodSmithSwiftFootEndow.cs:108 — Content/GameModes/GodSmith/Prefixes/Accessory/GodSmithSwiftFootEndow.cs:108-120 | Content/GameModes/GodSmith/Prefixes/Rescue/GodSmithHiddenEdgeEndow.cs:89-101 | Content/GameModes/GodSmith/Prefixes/Speed/GodSmithAfterimageEndow.cs:87-99 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (13 lines × 3) Content/Items/Melee/DestroyersBlade.cs:300 — Content/Items/Melee/DestroyersBlade.cs:300-312 | Content/Items/Melee/DragonsScaleGreatsword.cs:313-325 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:323-335 — before extracting anything, compare `Content/Items/Melee/DestroyersBlade.cs` and `Content/Items/Melee/DragonsScaleGreatsword.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 419 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DestroyersBlade.cs:300` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (13 lines × 3) Content/Items/Melee/DragonsScaleGreatsword.cs:554 — Content/Items/Melee/DragonsScaleGreatsword.cs:554-566 | Content/Items/Melee/RebelBlade.cs:601-613 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:536-548 — before extracting anything, compare `Content/Items/Melee/DragonsScaleGreatsword.cs` and `Content/Items/Melee/RebelBlade.cs` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 301 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 (13 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangProj.cs:186 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangProj.cs:186-198 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailHead.cs:193-205 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoProj.cs:212-224 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailHead.cs:190` calls `Configure`, `Vector2`, `ToRotation` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangProj.cs:183` 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 (13 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:177 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:177-189 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:189-201 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:180-192 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (13 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaMiniBloodSlime.cs:195 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaMiniBloodSlime.cs:195-207 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeBloodBee.cs:122-134 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshLeech.cs:128-140 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaMiniBloodSlime.cs:195` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaMiniBloodSlime.cs:192` calls `FindTarget` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshLeech.cs:125` 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 (13 lines × 3) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:597 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:597-609 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:407-419 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:533-545 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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 (13 lines × 3) Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:693 — Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:693-705 | Content/QuestLogs/Styles/ForestQuestLogStyle.cs:648-660 | Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:576-588 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:693` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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 (13 lines × 3) Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSystem.cs:96 — Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSystem.cs:96-108 | Content/Scenarios/Hadalworld/Ambience/HadalAmbience.cs:115-127 | Content/Scenarios/Kiyume/Fog/KiyumeFogSystem.cs:145-157 — before extracting anything, compare `Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSystem.cs` and `Content/Scenarios/Kiyume/Fog/KiyumeFogSystem.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 3) Content/Items/Melee/DragonsScaleGreatsword.cs:664 — Content/Items/Melee/DragonsScaleGreatsword.cs:664-676 | Content/Items/Melee/DragonsScaleGreatsword.cs:874-886 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:1026-1038 — before extracting anything, compare `Content/Items/Melee/DragonsScaleGreatsword.cs` and `Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 415 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:1024` calls `Clamp` and `Content/Items/Melee/DragonsScaleGreatsword.cs:662` does not — after which the two agree again for 4 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.
D4 · Code Duplication · Duplicated block (13–14 lines × 2) · ×17
  • Duplicated block (13–14 lines × 2) Content/GameModes/BrutalMobs/Ambience/DuneStorm/DuneStormRender.cs:271 — Content/GameModes/BrutalMobs/Ambience/DuneStorm/DuneStormRender.cs:271-283 | Content/GameModes/BrutalMobs/Ambience/Starfall/StarfallAmbientRender.cs:246-259 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/DuneStorm/DuneStormRender.cs:271` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (13–14 lines × 2) Content/GameModes/BrutalMobs/Ambience/Sporeshine/SporeshineRender.cs:123 — Content/GameModes/BrutalMobs/Ambience/Sporeshine/SporeshineRender.cs:123-136 | Content/GameModes/BrutalMobs/Ambience/Sporeshine/SporeshineRender.cs:167-179 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/Sporeshine/SporeshineRender.cs:123` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13–14 lines × 2) Content/Items/Magic/NeutronWands/NeutronPulsar.cs:480 — Content/Items/Magic/NeutronWands/NeutronPulsar.cs:480-493 | Content/Items/Magic/NeutronWands/NeutronStarquake.cs:193-205 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/NeutronWands/NeutronPulsar.cs:480` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13–14 lines × 2) Content/Items/Ranged/SneezingWyrms/WyrmBreathBolt.cs:60 — Content/Items/Ranged/SneezingWyrms/WyrmBreathBolt.cs:60-72 | Content/Items/Ranged/SneezingWyrms/WyrmstrikeRound.cs:48-61 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Ranged/SneezingWyrms/WyrmBreathBolt.cs:60` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13–14 lines × 2) Content/LegendWeapon/HalibutLegend/FishSkills/FishBunny.cs:47 — Content/LegendWeapon/HalibutLegend/FishSkills/FishBunny.cs:47-60 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCat.cs:47-59 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishBunny.cs:47` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13–14 lines × 2) Content/LegendWeapon/HalibutLegend/FishSkills/FishHarpy.cs:464 — Content/LegendWeapon/HalibutLegend/FishSkills/FishHarpy.cs:464-476 | Content/LegendWeapon/HalibutLegend/FishSkills/FishHarpy.cs:630-643 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishHarpy.cs:630` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13–14 lines × 2) Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs:59 — Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs:59-72 | Content/Scenarios/OldDuke/Quest/SulfseaTrackerWidgetStyle.cs:59-71 — before extracting anything, compare `Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs` and `Content/Scenarios/OldDuke/Quest/SulfseaTrackerWidgetStyle.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 75 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs:59` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13–14 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:105 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:105-118 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs:114-126 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 161 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:105` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13–14 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronBloodSkull.cs:73 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronBloodSkull.cs:73-86 | Content/Scenarios/Dungeonworld/NPCs/GaolFireBolt.cs:61-73 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronBloodSkull.cs:73` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (13–14 lines × 2) Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniKamuiFlowRenderer.cs:117 — Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniKamuiFlowRenderer.cs:117-130 | Content/LegendWeapon/OnikiriLegend/OniSakuraFlights/OniSakuraFlowRenderer.cs:129-141 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniKamuiFlowRenderer.cs` and `Content/LegendWeapon/OnikiriLegend/OniSakuraFlights/OniSakuraFlowRenderer.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniKamuiFlowRenderer.cs:117` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `def` to `in RibbonDef` in one and `in StreamDef` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (13–14 lines × 2) Content/LegendWeapon/OnikiriLegend/UI/OniPaperBurnDraw.cs:32 — Content/LegendWeapon/OnikiriLegend/UI/OniPaperBurnDraw.cs:32-45 | Content/LegendWeapon/OnikiriLegend/UI/OniStanceBladeDraw.cs:54-66 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/UI/OniPaperBurnDraw.cs:32` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13–14 lines × 2) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerCoilCrushState.cs:300 — Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerCoilCrushState.cs:300-312 | Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerEncircleState.cs:117-130 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerCoilCrushState.cs:300` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (13–14 lines × 2) Content/NPCs/SeaShrimp/States/SeaShrimpCavitationPunchState.cs:34 — Content/NPCs/SeaShrimp/States/SeaShrimpCavitationPunchState.cs:34-46 | Content/NPCs/SeaShrimp/States/SeaShrimpClawJabState.cs:29-42 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/SeaShrimp/States/SeaShrimpCavitationPunchState.cs:34` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13–14 lines × 2) Content/PRTTypes/PRT_Spark.cs:32 — Content/PRTTypes/PRT_Spark.cs:32-45 | Content/PRTTypes/PRT_SparkAlpha.cs:29-41 — before extracting anything, compare `Content/PRTTypes/PRT_Spark.cs` and `Content/PRTTypes/PRT_SparkAlpha.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/PRTTypes/PRT_Spark.cs:32` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/PRTTypes/PRT_Spark.cs:29` calls `SetProperty` and `Content/PRTTypes/PRT_SparkAlpha.cs:26` 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 (13–14 lines × 2) Content/Scenarios/Draedon/PQCDs/DraedonShops/ShopHandle.cs:83 — Content/Scenarios/Draedon/PQCDs/DraedonShops/ShopHandle.cs:83-96 | Content/Scenarios/Draedon/PQCDs/DraedonShops/ShopHandle.cs:148-160 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Draedon/PQCDs/DraedonShops/ShopHandle.cs:83` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (13–14 lines × 2) Content/Scenarios/Dungeonworld/NPCs/GaolDormantSkull.cs:293 — Content/Scenarios/Dungeonworld/NPCs/GaolDormantSkull.cs:293-306 | Content/Scenarios/Dungeonworld/NPCs/UndrownedThrone.cs:394-406 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/NPCs/GaolDormantSkull.cs:293` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13–14 lines × 2) Content/Wraiths/Abilities/CrimsonBrides/BrideHallRenderer.cs:405 — Content/Wraiths/Abilities/CrimsonBrides/BrideHallRenderer.cs:405-418 | Content/Wraiths/Deaths/Performances/BrideSeizurePerformance.cs:379-391 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Wraiths/Abilities/CrimsonBrides/BrideHallRenderer.cs:405` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Edited copy of a member (35 corresponding lines) · ×16
  • Edited copy of a member (35 corresponding lines) Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:526 — Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:526-574 | Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:669-703 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (35 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishIchornVFX.cs:249 — Content/LegendWeapon/HalibutLegend/FishSkills/FishIchornVFX.cs:249-285 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:392-426 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (35 corresponding lines) Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:217 — Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:217-251 | Content/Scenarios/Kiyume/UI/KiyumeLoadingScreen.cs:211-254 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (35 corresponding lines) Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs:355 — Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs:355-389 | Content/Scenarios/Shenyo/ShenyoPortraitRainRenderer.cs:349-385 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (35 corresponding lines) Content/LegendWeapon/SHPCLegend/Cyberspaces/Restart/CyberRestartProj.cs:313 — Content/LegendWeapon/SHPCLegend/Cyberspaces/Restart/CyberRestartProj.cs:313-355 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Restart/CyberRestartProj.cs:532-566 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (35 corresponding lines) Content/Items/Melee/Arbiters/ArbiterManifestationSystem.cs:514 — Content/Items/Melee/Arbiters/ArbiterManifestationSystem.cs:514-548 | Content/Items/Melee/WeaverGrievanceses/WGManifestationSystem.cs:504-538 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (35 corresponding lines) Content/HackTimes/Chips/HackChipGlyph.cs:69 — Content/HackTimes/Chips/HackChipGlyph.cs:69-103 | Content/Industrials/ElectricPowers/MiningMachines/MiningModuleGlyph.cs:62-98 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (35 corresponding lines) Content/NPCs/BloomsandSerpents/States/BssDespawnState.cs:23 — Content/NPCs/BloomsandSerpents/States/BssDespawnState.cs:23-58 | Content/NPCs/FestersandSerpents/States/FssDespawnState.cs:23-57 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (35 corresponding lines) Content/Items/Melee/Arbiters/Arbiter.cs:192 — Content/Items/Melee/Arbiters/Arbiter.cs:192-233 | Content/Items/Melee/Cloudwalking.cs:179-213 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (35 corresponding lines) Content/Items/Accessories/ArcaneThroneOfEternity.cs:613 — Content/Items/Accessories/ArcaneThroneOfEternity.cs:613-647 | Content/Items/Accessories/EyeOfSingularity.cs:608-649 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (35 corresponding lines) Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:377 — Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:377-416 | Content/Items/Modifys/RTerraBlades/RTerraBladeHeld.cs:387-421 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (35 corresponding lines) Content/HackTimes/HackStatusDisplay.cs:130 — Content/HackTimes/HackStatusDisplay.cs:130-164 | Content/HackTimes/HackStatusDisplay.cs:205-239 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (35 corresponding lines) Content/Scenarios/Himayo/ToriiShrines/ToriiShrineLocationFinder.cs:43 — Content/Scenarios/Himayo/ToriiShrines/ToriiShrineLocationFinder.cs:43-77 | Content/Scenarios/Kiame/Overlay/OniUmbrellaWorldSpawn.cs:305-339 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (35 corresponding lines) Content/LegendWeapon/HalibutLegend/DomainSkills/Superposition.cs:505 — Content/LegendWeapon/HalibutLegend/DomainSkills/Superposition.cs:505-539 | Content/LegendWeapon/HalibutLegend/DomainSkills/YourLevelIsTooLow.cs:363-398 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (35 corresponding lines) Content/Scenarios/Kiyume/NPCs/FacelessOneYokai.cs:305 — Content/Scenarios/Kiyume/NPCs/FacelessOneYokai.cs:305-339 | Content/Scenarios/Kiyume/NPCs/RidgeWalkerYokai.cs:457-492 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (35 corresponding lines) Content/NPCs/TBUGs/TBUG.cs:53 — Content/NPCs/TBUGs/TBUG.cs:53-87 | Content/NPCs/Victors/Victor.cs:60-95 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (34 corresponding lines) · ×16
  • Edited copy of a member (34 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:158 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:158-191 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:149-189 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (34 corresponding lines) Content/GameModes/GodSmith/Weapons/Broadswords/GsMeowmere.cs:636 — Content/GameModes/GodSmith/Weapons/Broadswords/GsMeowmere.cs:636-669 | Content/GameModes/GodSmith/Weapons/Broadswords/GsStarWrath.cs:506-546 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (34 corresponding lines) Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadCommandRender.cs:146 — Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadCommandRender.cs:146-193 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/HeadPrimeAI.cs:786-819 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (34 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsHail.cs:138 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsHail.cs:138-171 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeStinger.cs:204-247 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (34 corresponding lines) Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:385 — Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:385-419 | Content/Industrials/Modifys/ChargingStationUI.cs:239-272 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (34 corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Frame/ResonanceFrameModule.cs:487 — Content/LegendWeapon/SHPCLegend/Modules/Frame/ResonanceFrameModule.cs:487-520 | Content/LegendWeapon/SHPCLegend/Modules/Frame/VolatileFrameModule.cs:578-613 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (34 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallProj.cs:1024 — Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallProj.cs:1024-1057 | Content/Scenarios/Kiame/KasaOnis/KasaOniRenderer.cs:84-124 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (34 corresponding lines) Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadArcProj.cs:56 — Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadArcProj.cs:56-95 | Content/Items/Stones/Granites/GraniteThrowingKnife.cs:236-269 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (34 corresponding lines) Content/NPCs/BrutalNPCs/BrutalDestroyer/DestroyerBodyAI.cs:578 — Content/NPCs/BrutalNPCs/BrutalDestroyer/DestroyerBodyAI.cs:578-627 | Content/NPCs/BrutalNPCs/BrutalDestroyer/DestroyerTailAI.cs:22-55 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (34 corresponding lines) Content/NPCs/SeaShrimp/Projectiles/SeaShrimpLeapVortex.cs:63 — Content/NPCs/SeaShrimp/Projectiles/SeaShrimpLeapVortex.cs:63-96 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpVortexWall.cs:62-95 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (34 corresponding lines) Content/Wraiths/Deaths/Performances/BrideSeizurePerformance.cs:196 — Content/Wraiths/Deaths/Performances/BrideSeizurePerformance.cs:196-233 | Content/Wraiths/Deaths/Performances/ScapeSeizurePerformance.cs:215-248 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (34 corresponding lines) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs:43 — Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs:43-76 | Content/NPCs/FestersandSerpents/Projectiles/FssIchorGlob.cs:43-76 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (34 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrown.cs:213 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrown.cs:213-246 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaPlayerDrown.cs:248-282 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (34 corresponding lines) Content/NPCs/TBUGs/TBUGDialogue.cs:183 — Content/NPCs/TBUGs/TBUGDialogue.cs:183-216 | Content/NPCs/Victors/VictorDialogue.cs:183-216 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (34 corresponding lines) Content/Cyberwares/CyberwareLocalSettlement.cs:91 — Content/Cyberwares/CyberwareLocalSettlement.cs:91-126 | Content/NPCs/TBUGs/TBUGShopNet.cs:143-176 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (34 corresponding lines) Content/GameModes/BrutalMobs/Ocean/OceanBrutalNPC.cs:375 — Content/GameModes/BrutalMobs/Ocean/OceanBrutalNPC.cs:375-413 | Content/GameModes/BrutalMobs/Stoneborn/StonebornBrutalNPC.cs:229-262 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (36 corresponding lines) · ×16
  • Edited copy of a member (36 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishPrincessVFX.cs:123 — Content/LegendWeapon/HalibutLegend/FishSkills/FishPrincessVFX.cs:123-158 | Content/LegendWeapon/HalibutLegend/FishSkills/FishPrincessVFX.cs:162-204 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (36 corresponding lines) Content/Wraiths/Abilities/CrimsonBrides/BrideHallRenderer.cs:348 — Content/Wraiths/Abilities/CrimsonBrides/BrideHallRenderer.cs:348-383 | Content/Wraiths/Deaths/Performances/BrideSeizurePerformance.cs:319-358 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (36 corresponding lines) Content/GameModes/GodSmith/Armors/Reset/GsCrimsonArmor.cs:70 — Content/GameModes/GodSmith/Armors/Reset/GsCrimsonArmor.cs:70-107 | Content/GameModes/GodSmith/Armors/Reset/GsOreArmorsHardmode.cs:332-367 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (36 corresponding lines) Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:83 — Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:83-118 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpJetBeam.cs:95-134 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (36 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:527 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:527-564 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:607-642 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (36 corresponding lines) Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs:291 — Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs:291-326 | Content/Items/Melee/WeaverGrievanceses/WGManifestationNet.cs:292-327 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (36 corresponding lines) Content/NPCs/BloomsandSerpents/BssLegRig.cs:530 — Content/NPCs/BloomsandSerpents/BssLegRig.cs:530-565 | Content/NPCs/FestersandSerpents/FssLegRig.cs:342-385 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (36 corresponding lines) Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:399 — Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:399-434 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleCut.cs:380-415 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (36 corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1127 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1127-1165 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1322-1357 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (36 corresponding lines) Content/Items/Accessories/BrutalRelics/Twins/TwinPupilShots.cs:129 — Content/Items/Accessories/BrutalRelics/Twins/TwinPupilShots.cs:129-164 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/CursedFlameJet.cs:26-66 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (36 corresponding lines) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerLaserBarrageState.cs:340 — Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerLaserBarrageState.cs:340-379 | Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerLaserBarrageState.cs:382-417 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (36 corresponding lines) Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs:280 — Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs:280-316 | Content/Scenarios/Shenyo/ShenyoPortraitRainRenderer.cs:275-310 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (36 corresponding lines) Content/Items/Tools/EncyclopediaofOceanicKnowledge.cs:193 — Content/Items/Tools/EncyclopediaofOceanicKnowledge.cs:193-228 | Content/Items/Tools/TheForgottenTome.cs:152-190 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (36 corresponding lines) Content/Items/Melee/Arbiters/Arbiter.cs:154 — Content/Items/Melee/Arbiters/Arbiter.cs:154-189 | Content/Items/Melee/Cloudwalking.cs:141-177 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (36 corresponding lines) Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:205 — Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:205-246 | Content/Items/Modifys/RBloodButcherer.cs:244-279 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (36 corresponding lines) Content/Scenarios/OldNet/NPCs/OldNetTaggerICE.cs:74 — Content/Scenarios/OldNet/NPCs/OldNetTaggerICE.cs:74-109 | Content/Scenarios/OldNet/NPCs/OldNetTracerICE.cs:76-122 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 8+ corresponding lines) · ×16
  • Edited copies of one member (4 members, 8+ corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Frame/MultiCellFrameModule.cs:33 — Content/LegendWeapon/SHPCLegend/Modules/Frame/MultiCellFrameModule.cs:33-40 | Content/LegendWeapon/SHPCLegend/Modules/Optic/AdaptiveOpticModule.cs:91-100 | Content/LegendWeapon/SHPCLegend/Modules/Stock/AssaultStockModule.cs:28-39 | Content/LegendWeapon/SHPCLegend/Modules/Stock/StormStockModule.cs:28-35 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 8+ corresponding lines) Content/HackTimes/Protocols/Contagion.cs:61 — Content/HackTimes/Protocols/Contagion.cs:61-68 | Content/HackTimes/Protocols/Cyberpsychosis.cs:58-65 | Content/HackTimes/Protocols/MemoryWipe.cs:45-52 | Content/HackTimes/Protocols/MemoryWipe.cs:68-75 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 8+ corresponding lines) Content/GameModes/GodSmith/Weapons/Bows/Projectiles/GsVolleyBurstProj.cs:87 — Content/GameModes/GodSmith/Weapons/Bows/Projectiles/GsVolleyBurstProj.cs:87-94 | Content/GameModes/GodSmith/Weapons/MagicCataclysm/Projectiles/GsCataclysmRiderBurstProj.cs:88-98 | Content/GameModes/GodSmith/Weapons/MagicMorph/Projectiles/GsDomainProj.cs:89-100 | Content/GameModes/GodSmith/Weapons/SummonSentries/Projectiles/GsSentryBurstProj.cs:75-85 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 8+ corresponding lines) Content/Items/Summon/AzureDragonRage.cs:14 — Content/Items/Summon/AzureDragonRage.cs:14-21 | Content/Items/Summon/BleedingScourge.cs:14-21 | Content/Items/Summon/ElementWhip.cs:15-22 | Content/Items/Summon/GhostFireWhip.cs:18-25 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 8+ corresponding lines) Content/GameModes/BrutalMobs/EvilBiome/EvilBiomeMobsNPC.cs:425 — Content/GameModes/BrutalMobs/EvilBiome/EvilBiomeMobsNPC.cs:425-432 | Content/GameModes/BrutalMobs/NightPack/NightPackNPC.cs:143-150 | Content/GameModes/BrutalMobs/NightPack/NightPackNPC.cs:152-159 | Content/GameModes/BrutalMobs/Stoneborn/StonebornBrutalNPC.cs:265-272 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 8+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishScorpioPRT.cs:116 — Content/LegendWeapon/HalibutLegend/FishSkills/FishScorpioPRT.cs:116-125 | Content/LegendWeapon/HalibutLegend/FishSkills/FishTunabeardVFX.cs:368-376 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistParticles.cs:154-161 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistParticles.cs:402-410 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 8+ corresponding lines) Content/Scenarios/Helen/Gifts/CrabulonGift.cs:31 — Content/Scenarios/Helen/Gifts/CrabulonGift.cs:31-38 | Content/Scenarios/Helen/Gifts/GolemGift.cs:31-38 | Content/Scenarios/Helen/Gifts/KingSlimeGift.cs:31-38 | Content/Scenarios/Helen/Gifts/WallOfFleshGift.cs:31-38 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 8+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalDeerclops/Core/DeerclopsMotion.cs:185 — Content/NPCs/BrutalNPCs/BrutalDeerclops/Core/DeerclopsMotion.cs:185-192 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Core/EocMotion.cs:237-245 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Rendering/KingSlimeGelFX.cs:55-62 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Core/CultistMotion.cs:190-198 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 8+ corresponding lines) Content/HackTimes/Chips/BaseHackProtocolChip.cs:140 — Content/HackTimes/Chips/BaseHackProtocolChip.cs:140-149 | Content/Industrials/MachineModules/BaseMachineModule.cs:81-89 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/KikasaTalismanItem.cs:98-105 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiRubbingItem.cs:108-115 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 8+ corresponding lines) Content/Cyberwares/CyberwareNet.cs:659 — Content/Cyberwares/CyberwareNet.cs:659-668 | Content/NPCs/TBUGs/TBUGDialogue.cs:310-318 | Content/NPCs/TBUGs/TBUGSession.cs:14-21 | Content/NPCs/Victors/VictorDialogue.cs:314-322 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 8+ corresponding lines) Content/GameModes/GodSmith/Accessories/Offense/GodSmithEmblems.cs:40 — Content/GameModes/GodSmith/Accessories/Offense/GodSmithEmblems.cs:40-47 | Content/GameModes/GodSmith/Accessories/Offense/GodSmithGloveChain.cs:45-52 | Content/GameModes/GodSmith/Accessories/Offense/GodSmithManaFlowerChain.cs:98-105 | Content/GameModes/GodSmith/Accessories/Offense/GodSmithSummonChain.cs:40-47 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 8+ corresponding lines) Content/GameModes/GodSmith/Armors/Reset/GsResetArmorScheme.cs:175 — Content/GameModes/GodSmith/Armors/Reset/GsResetArmorScheme.cs:175-182 | Content/Items/Ranged/Pallbearer.cs:1067-1074 | Content/LegendWeapon/HalibutLegend/FishSkills/FishVoodooRitual.cs:465-472 | Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashMark.cs:48-55 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 8+ corresponding lines) Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMirrorPhantom.cs:232 — Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMirrorPhantom.cs:232-240 | Content/Items/Magic/BloomTomes/BloomTome.cs:69-76 | Content/Items/Summon/BloomCallers/BloomCallerSprout.cs:407-414 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Projectiles/EocBloodShot.cs:22-31 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 8+ corresponding lines) Content/Scenarios/Himayo/ToriiShrines/ToriiShrine.cs:179 — Content/Scenarios/Himayo/ToriiShrines/ToriiShrine.cs:179-186 | Content/Scenarios/Kiame/Gate/KiameGateSpawn.cs:200-207 | Content/Scenarios/Kiame/Overlay/OniUmbrellaWorldSpawn.cs:192-199 | Content/Scenarios/OldDuke/Campsites/OldDukeCampsite.cs:222-229 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 8+ corresponding lines) Content/GameModes/BrutalMobs/Ambience/Ashreign/Ashreign.cs:74 — Content/GameModes/BrutalMobs/Ambience/Ashreign/Ashreign.cs:74-81 | Content/GameModes/BrutalMobs/Ambience/DuneStorm/DuneStorm.cs:65-72 | Content/GameModes/BrutalMobs/Ambience/Mireheart/MireheartPlayer.cs:70-77 | Content/GameModes/BrutalMobs/Ambience/Stonewake/StonewakeFX.cs:39-46 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 8+ corresponding lines) Content/Industrials/ElectricPowers/Apiaries/ApiaryStorageProvider.cs:61 — Content/Industrials/ElectricPowers/Apiaries/ApiaryStorageProvider.cs:61-71 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherStorageProvider.cs:60-70 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerStorageProvider.cs:60-70 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:511-518 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×16
  • Duplicated block (21 lines × 2) Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:27 — Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:27-47 | Content/Items/Modifys/RBloodButcherer.cs:110-130 — before extracting anything, compare `Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs` and `Content/Items/Modifys/RBloodButcherer.cs` as WHOLE FILES: this scan already matched 36 separate duplicated blocks between them, totalling at least 458 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (21 lines × 2) Content/LegendWeapon/HalibutLegend/DomainSkills/Superposition.cs:515 — Content/LegendWeapon/HalibutLegend/DomainSkills/Superposition.cs:515-535 | Content/LegendWeapon/HalibutLegend/DomainSkills/YourLevelIsTooLow.cs:372-392 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/DomainSkills/Superposition.cs:515` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:420 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:420-440 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:515-535 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs` as WHOLE FILES: this scan already matched 70 separate duplicated blocks between them, totalling at least 835 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:420` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 2) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeHeatRay.cs:133 — Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeHeatRay.cs:133-153 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeSkullBeamProj.cs:144-164 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeHeatRay.cs` and `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeSkullBeamProj.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 134 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeHeatRay.cs:133` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 2) Content/Items/Ranged/Undertows/UndertowSpine.cs:237 — Content/Items/Ranged/Undertows/UndertowSpine.cs:237-257 | Content/Items/Summon/Deepclaws/DeepclawLobster.cs:529-549 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Ranged/Undertows/UndertowSpine.cs:237` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 2) Content/Items/Melee/Shatterfangs/ShatterfangBigShard.cs:107 — Content/Items/Melee/Shatterfangs/ShatterfangBigShard.cs:107-127 | Content/Items/Melee/Shatterfangs/ShatterfangShard.cs:85-105 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Shatterfangs/ShatterfangBigShard.cs:107` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (21 lines × 2) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetNet.cs:81 — Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetNet.cs:81-101 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetNet.cs:78-98 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetNet.cs:81` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetNet.cs:79` calls `ReadSingle` and `Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetNet.cs:76` does not — after which the two agree again for 3 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 (21 lines × 2) Content/PRTTypes/PRT_KikasaBloodSpray.cs:78 — Content/PRTTypes/PRT_KikasaBloodSpray.cs:78-98 | Content/PRTTypes/PRT_KikasaInkSpray.cs:87-107 — before extracting anything, compare `Content/PRTTypes/PRT_KikasaBloodSpray.cs` and `Content/PRTTypes/PRT_KikasaInkSpray.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 70 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/PRTTypes/PRT_KikasaBloodSpray.cs:78` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 2) Content/GameModes/BrutalMobs/Ambience/Rainveil/RainveilStormSystem.cs:88 — Content/GameModes/BrutalMobs/Ambience/Rainveil/RainveilStormSystem.cs:88-108 | Content/GameModes/BrutalMobs/Ambience/Rotmire/RotmireVentSystem.cs:96-116 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (21 lines × 2) Content/GameModes/BrutalMobs/Ambience/Rainveil/RainveilStormSystem.cs:234 — Content/GameModes/BrutalMobs/Ambience/Rainveil/RainveilStormSystem.cs:234-254 | Content/GameModes/BrutalMobs/Ambience/Rotmire/RotmireVentSystem.cs:268-288 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (21 lines × 2) Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:154 — Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:154-174 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsScourgeoftheCorruptor.cs:136-156 — 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 (21 lines × 2) Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:144 — Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:144-164 | Content/Items/Melee/WeaverGrievanceses/WGManifestationActor.cs:130-150 — before extracting anything, compare `Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs` and `Content/Items/Melee/WeaverGrievanceses/WGManifestationActor.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 237 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:144` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 2) Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs:463 — Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs:463-483 | Content/Items/Melee/WeaverGrievanceses/WGManifestationNet.cs:464-484 — before extracting anything, compare `Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs` and `Content/Items/Melee/WeaverGrievanceses/WGManifestationNet.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 145 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs:463` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (21 lines × 2) Content/Items/Melee/DestroyersBlade.cs:102 — Content/Items/Melee/DestroyersBlade.cs:102-122 | Content/Items/Melee/DragonsScaleGreatsword.cs:118-138 — before extracting anything, compare `Content/Items/Melee/DestroyersBlade.cs` and `Content/Items/Melee/DragonsScaleGreatsword.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 419 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 (21 lines × 2) Content/MainMenus/Himayo/HimayoMenuOverride.cs:135 — Content/MainMenus/Himayo/HimayoMenuOverride.cs:135-156 | Content/MainMenus/Shenyo/ShenyoMenuOverride.cs:101-121 — before extracting anything, compare `Content/MainMenus/Himayo/HimayoMenuOverride.cs` and `Content/MainMenus/Shenyo/ShenyoMenuOverride.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/MainMenus/Himayo/HimayoMenuOverride.cs:135` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 2) Content/NPCs/BloomsandSerpents/Projectiles/BssBreachOmen.cs:36 — Content/NPCs/BloomsandSerpents/Projectiles/BssBreachOmen.cs:36-56 | Content/NPCs/FestersandSerpents/Projectiles/FssBreachOmen.cs:31-51 — before extracting anything, compare `Content/NPCs/BloomsandSerpents/Projectiles/BssBreachOmen.cs` and `Content/NPCs/FestersandSerpents/Projectiles/FssBreachOmen.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BloomsandSerpents/Projectiles/BssBreachOmen.cs:36` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (9–10 lines × 3) · ×16
  • Duplicated block (9–10 lines × 3) Content/Industrials/ElectricPowers/Sundials/ElectricSundialTile.cs:127 — Content/Industrials/ElectricPowers/Sundials/ElectricSundialTile.cs:127-136 | Content/Industrials/ElectricPowers/Throwers/ThrowerTile.cs:123-132 | Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersTile.cs:81-89 — before extracting anything, compare `Content/Industrials/ElectricPowers/Sundials/ElectricSundialTile.cs` and `Content/Industrials/ElectricPowers/Throwers/ThrowerTile.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Sundials/ElectricSundialTile.cs:127` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (9–10 lines × 3) Content/Items/Melee/Abyssrends/AbyssrendFX.cs:117 — Content/Items/Melee/Abyssrends/AbyssrendFX.cs:117-125 | Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:755-764 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:323-331 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:765` calls `SetValue`, `Max` and `Content/Items/Melee/Abyssrends/AbyssrendFX.cs:126` 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–10 lines × 3) Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:879 — Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:879-887 | Content/Items/Melee/NeutronGlaive.cs:560-569 | Content/Items/Modifys/RBloodButcherer.cs:679-688 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:879` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9–10 lines × 3) Content/Items/Ranged/DarkFrostSolstice.cs:278 — Content/Items/Ranged/DarkFrostSolstice.cs:278-286 | Content/Items/Ranged/DarkFrostSolstice.cs:297-306 | Content/Items/Ranged/DarkFrostSolstice.cs:313-322 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Ranged/DarkFrostSolstice.cs:278` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9–10 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:792 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:792-801 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaMinionDrownFX.cs:369-377 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaScourgeFX.cs:354-363 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaScourgeFX.cs:354` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `show` to `DrownShow` in one and `WaveShow` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaScourgeFX.cs:363` calls `Clamp`, `Distance` and `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:801` 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–10 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:941 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:941-949 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:1284-1293 | Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:1392-1400 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:941` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9–10 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:130 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:130-138 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:141-150 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:164-172 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:130` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9–10 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:161 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:161-170 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs:170-178 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:155-164 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 161 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:161` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (9–10 lines × 3) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:857 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:857-866 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:652-660 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:811-819 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:857` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9–10 lines × 3) Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:307 — Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:307-315 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleCut.cs:354-363 | Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashMark.cs:249-258 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:307` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9–10 lines × 3) Content/LegendWeapon/OnikiriLegend/UI/OniLedgerSwapFX.cs:124 — Content/LegendWeapon/OnikiriLegend/UI/OniLedgerSwapFX.cs:124-132 | Content/LegendWeapon/OnikiriLegend/UI/OniStanceBladeDraw.cs:50-59 | Content/LegendWeapon/OnikiriLegend/UI/OniVigorInkDraw.cs:50-59 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/UI/OniLedgerSwapFX.cs` and `Content/LegendWeapon/OnikiriLegend/UI/OniVigorInkDraw.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 44 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/UI/OniStanceBladeDraw.cs:50` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (9–10 lines × 3) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:270 — Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:270-279 | Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingPanel.cs:411-420 | Content/LegendWeapon/SHPCLegend/UI/SHPCModPanel.cs:449-457 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:270` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (9–10 lines × 3) Content/NPCs/BrutalNPCs/BrutalPlantera/PlanteraAI.cs:488 — Content/NPCs/BrutalNPCs/BrutalPlantera/PlanteraAI.cs:488-497 | Content/NPCs/BrutalNPCs/BrutalPlantera/PlanteraHookAI.cs:324-333 | Content/NPCs/BrutalNPCs/BrutalPlantera/PlanteraTentacleAI.cs:310-318 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalPlantera/PlanteraAI.cs:488` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (9–10 lines × 3) Content/NPCs/SeaShrimp/Projectiles/SeaShrimpLeapVortex.cs:110 — Content/NPCs/SeaShrimp/Projectiles/SeaShrimpLeapVortex.cs:110-119 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpMiniVortex.cs:102-110 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpVortexWall.cs:110-119 — before extracting anything, compare `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpLeapVortex.cs` and `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpMiniVortex.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 99 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpLeapVortex.cs:110` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (9–10 lines × 3) Content/Scenarios/Himayo/ToriiShrines/ToriiShrineLocationFinder.cs:80 — Content/Scenarios/Himayo/ToriiShrines/ToriiShrineLocationFinder.cs:80-89 | Content/Scenarios/Kiame/Gate/KiameGateSpawn.cs:274-282 | Content/Scenarios/Kiame/Overlay/OniUmbrellaWorldSpawn.cs:292-300 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9–10 lines × 3) Content/Scenarios/OldNet/Tiles/OldNetDataNodeTile.cs:65 — Content/Scenarios/OldNet/Tiles/OldNetDataNodeTile.cs:65-74 | Content/Scenarios/OldNet/Tiles/OldNetEchoNodeTile.cs:78-86 | Content/Scenarios/OldNet/Tiles/OldNetEncryptedNodeTile.cs:79-87 — before extracting anything, compare `Content/Scenarios/OldNet/Tiles/OldNetDataNodeTile.cs` and `Content/Scenarios/OldNet/Tiles/OldNetEchoNodeTile.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 43 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/OldNet/Tiles/OldNetDataNodeTile.cs:65` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Edited copy of a member (33 corresponding lines) · ×15
  • Edited copy of a member (33 corresponding lines) Content/Items/Magic/Everdeeps/EverdeepVFX.cs:38 — Content/Items/Magic/Everdeeps/EverdeepVFX.cs:38-70 | Content/LegendWeapon/HalibutLegend/OceanCurrentParticles.cs:86-128 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (33 corresponding lines) Content/Items/Magic/Elysiums/Serpents/HolySerpent.cs:362 — Content/Items/Magic/Elysiums/Serpents/HolySerpent.cs:362-405 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Rendering/EmpressBeamDraw.cs:111-143 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (33 corresponding lines) Content/Scenarios/OldNet/Tiles/OldNetCacheTile.cs:96 — Content/Scenarios/OldNet/Tiles/OldNetCacheTile.cs:96-128 | Content/Scenarios/OldNet/Tiles/OldNetLedgerDockTile.cs:83-123 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (33 corresponding lines) Content/Narrative/Presentation/Skins/Kikasa/KikasaChoiceSkin.cs:51 — Content/Narrative/Presentation/Skins/Kikasa/KikasaChoiceSkin.cs:51-89 | Content/Narrative/Presentation/Skins/Onikiri/OnikiriChoiceSkin.cs:46-78 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (33 corresponding lines) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowBreachOmen.cs:37 — Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowBreachOmen.cs:37-69 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowDevourOmen.cs:47-95 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (33 corresponding lines) Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiStrikes.cs:311 — Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiStrikes.cs:311-343 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiStrikes.cs:390-423 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (33 corresponding lines) Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleRing.cs:151 — Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleRing.cs:151-191 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleRing.cs:194-226 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (33 corresponding lines) Content/Industrials/Generator/Thermal/ThermalHeatHazeRender.cs:123 — Content/Industrials/Generator/Thermal/ThermalHeatHazeRender.cs:123-157 | Content/Scenarios/Dungeonworld/Gen/BossRooms/ProofingHallScene.cs:317-349 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (33 corresponding lines) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs:143 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs:143-176 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeHeatRay.cs:133-165 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (33 corresponding lines) Content/Scenarios/Himayo/Gifts/HimayoGiftNarrativeTracker.cs:80 — Content/Scenarios/Himayo/Gifts/HimayoGiftNarrativeTracker.cs:80-112 | Content/Scenarios/Shenyo/Gifts/ShenyoGiftNarrativeTracker.cs:77-109 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (33 corresponding lines) Content/Items/Melee/HeartcarverCore.cs:244 — Content/Items/Melee/HeartcarverCore.cs:244-276 | Content/Items/Melee/SpearOfLonginuses/LonginusAssets.cs:86-119 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (33 corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:385 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:385-417 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:347-379 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (33 corresponding lines) Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs:198 — Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs:198-232 | Content/Scenarios/Shenyo/ShenyoPortraitRainRenderer.cs:196-228 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (33 corresponding lines) Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:180 — Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:180-216 | Content/Items/Melee/WeaverGrievanceses/WGManifestationActor.cs:164-196 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (33 corresponding lines) Content/Scenarios/Shepel/CybCourses/CybCourseCompletePanel.cs:71 — Content/Scenarios/Shepel/CybCourses/CybCourseCompletePanel.cs:71-103 | Content/Scenarios/Shepel/CybCourses/CybCourseKeyBindReminderPanel.cs:118-150 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 12+ corresponding lines) · ×15
  • Edited copies of one member (4 members, 12+ corresponding lines) Content/Items/Melee/DestroyersBlade.cs:478 — Content/Items/Melee/DestroyersBlade.cs:478-492 | Content/Items/Melee/DragonsScaleGreatsword.cs:504-515 | Content/Items/Melee/EnergySword.cs:515-531 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:486-497 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 12+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:297 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:297-315 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:294-312 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:292-310 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:869-880 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 12+ corresponding lines) Content/HackTimes/HackEffectTracker.cs:92 — Content/HackTimes/HackEffectTracker.cs:92-103 | Content/HackTimes/HackEffectTracker.cs:110-121 | Content/HackTimes/HackEffectTracker.cs:124-138 | Content/HackTimes/HackEffectTracker.cs:141-155 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 12+ corresponding lines) Content/GameModes/GodSmith/Prefixes/Accessory/GodSmithSwiftFootEndow.cs:122 — Content/GameModes/GodSmith/Prefixes/Accessory/GodSmithSwiftFootEndow.cs:122-137 | Content/GameModes/GodSmith/Prefixes/Ranged/GodSmithBallisticEndow.cs:98-109 | Content/GameModes/GodSmith/Prefixes/Rescue/GodSmithHiddenEdgeEndow.cs:103-118 | Content/GameModes/GodSmith/Prefixes/Speed/GodSmithAfterimageEndow.cs:101-116 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 12+ corresponding lines) Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:375 — Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:375-388 | Content/Items/Melee/Abyssrends/AbyssrendBurst.cs:25-36 | Content/Items/Ranged/Undertows/UndertowSpine.cs:213-224 | Content/Items/Summon/Deepclaws/DeepclawLobster.cs:505-516 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 12+ corresponding lines) Content/Items/Magic/Pandemoniums/PandemoniumBlastWave.cs:16 — Content/Items/Magic/Pandemoniums/PandemoniumBlastWave.cs:16-28 | Content/Items/Magic/Pandemoniums/PandemoniumLightning.cs:28-41 | Content/Items/Magic/Pandemoniums/PandemoniumRainDrop.cs:18-29 | Content/Items/Magic/Pandemoniums/PandemoniumRainDrop.cs:166-179 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 12+ corresponding lines) Content/Items/Magic/AriaofTheCosmoses/AccretionDisk.cs:72 — Content/Items/Magic/AriaofTheCosmoses/AccretionDisk.cs:72-86 | Content/Items/Ranged/Starships/StarshipWingman.cs:16-27 | Content/LegendWeapon/HalibutLegend/FishSkills/FishTunabeard.cs:108-120 | Content/Wraiths/Projectiles/LanternBoySlashProj.cs:61-73 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 12+ corresponding lines) Content/Items/Melee/CommandersClaw.cs:70 — Content/Items/Melee/CommandersClaw.cs:70-84 | Content/Items/Melee/SeasonalKunai.cs:86-98 | Content/Items/Melee/SporeburstPouch.cs:53-64 | Content/Items/Ranged/RaiderGun.cs:389-402 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 12+ corresponding lines) Content/Cyberwares/Implementation/PlowSteelClampArms/MonomolecularWire.cs:54 — Content/Cyberwares/Implementation/PlowSteelClampArms/MonomolecularWire.cs:54-68 | Content/GameModes/GodSmith/Weapons/Guns/GunsHardShared.cs:473-484 | Content/GameModes/GodSmith/Weapons/Throwing/Projectiles/GsBurstProj.cs:20-32 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMoonFlare.cs:40-51 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 12+ corresponding lines) Content/Industrials/ElectricPowers/Incinerators/IncineratorTile.cs:48 — Content/Industrials/ElectricPowers/Incinerators/IncineratorTile.cs:48-61 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterTile.cs:58-72 | Content/Industrials/ElectricPowers/Sundials/ElectricSundialTile.cs:80-94 | Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersTile.cs:91-102 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 12+ corresponding lines) Content/Items/Magic/FocusingGrimoire.cs:137 — Content/Items/Magic/FocusingGrimoire.cs:137-150 | Content/Items/Magic/SandVortexOfTheDecayedSea.cs:361-373 | Content/Items/Melee/DestroyersBlade.cs:573-585 | Content/Items/Melee/DestroyersBladeEXs/DestroyerHeadMissile.cs:33-44 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 12+ corresponding lines) Content/Items/Melee/Budcrowns/Budcrown.cs:95 — Content/Items/Melee/Budcrowns/Budcrown.cs:95-106 | Content/LegendWeapon/HalibutLegend/DomainSkills/Superposition.cs:1074-1086 | Content/LegendWeapon/HalibutLegend/FishSkills/FishSlime.cs:199-210 | Content/LegendWeapon/HalibutLegend/FishSkills/FishVariegatedLard.cs:161-172 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 12+ corresponding lines) Content/LegendWeapon/OnikiriLegend/OniDismembers/OniSeverStrike.cs:247 — Content/LegendWeapon/OnikiriLegend/OniDismembers/OniSeverStrike.cs:247-258 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleSlash.cs:102-113 | Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashStep.cs:209-221 | Content/LegendWeapon/OnikiriLegend/OniSakuraFlights/OniSakuraFlight.cs:261-273 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 12+ corresponding lines) Content/GameModes/GodSmith/Armors/Reset/GsBeeArmor.cs:107 — Content/GameModes/GodSmith/Armors/Reset/GsBeeArmor.cs:107-120 | Content/GameModes/GodSmith/Armors/Reset/GsJungleArmor.cs:58-70 | Content/GameModes/GodSmith/Weapons/Broadswords/GsChristmasTreeSword.cs:252-263 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT2.cs:416-427 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 12+ corresponding lines) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterStorageProvider.cs:174 — Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterStorageProvider.cs:174-185 | Content/Industrials/ElectricPowers/Crushers/CrusherStorageProvider.cs:240-251 | Content/Industrials/ElectricPowers/Incinerators/IncineratorStorageProvider.cs:262-273 | Content/Industrials/ElectricPowers/Recyclers/RecyclerStorageProvider.cs:218-229 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 9+ corresponding lines) · ×15
  • Edited copies of one member (4 members, 9+ corresponding lines) Content/GameModes/GodSmith/Armors/Reset/GsPillarArmors.cs:144 — Content/GameModes/GodSmith/Armors/Reset/GsPillarArmors.cs:144-153 | Content/GameModes/GodSmith/Armors/Reset/GsSpectreArmors.cs:68-76 | Content/GameModes/GodSmith/Armors/Reset/GsSpiderArmor.cs:29-37 | Content/GameModes/GodSmith/Armors/Reset/GsTikiArmor.cs:31-40 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 9+ corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:215 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:215-223 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:175-183 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleSlash.cs:86-96 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:196-204 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 9+ corresponding lines) Content/GameModes/GodSmith/Weapons/MagicConduit/GsLastPrism.cs:228 — Content/GameModes/GodSmith/Weapons/MagicConduit/GsLastPrism.cs:228-236 | Content/Items/Magic/Elysiums/Revelations/ApocalypseHorseman.cs:203-213 | Content/Items/Modifys/RTerraBlades/TerraSoulJudgmentProj.cs:136-145 | Content/Items/Modifys/RTerraBlades/TerraSoulSpinProj.cs:116-125 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 9+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalDukeFishron/Rendering/FishronMotionFX.cs:115 — Content/NPCs/BrutalNPCs/BrutalDukeFishron/Rendering/FishronMotionFX.cs:115-123 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Core/EocMotion.cs:173-186 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Core/TwinsMotion.cs:116-124 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Core/QueenBeeMotion.cs:133-145 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 9+ corresponding lines) Content/GameModes/Blessings/UI/BlessingRenderer.cs:152 — Content/GameModes/Blessings/UI/BlessingRenderer.cs:152-160 | Content/GameModes/UI/GameModeRenderer.cs:130-138 | Content/LegendWeapon/OnikiriLegend/UI/OniMeiRenderer.cs:376-384 | Content/MainMenus/Characters/CharacterDockRenderer.cs:13-21 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 9+ corresponding lines) Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryWatcher.cs:205 — Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryWatcher.cs:205-214 | Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolBossRoomWatcher.cs:323-331 | Content/Scenarios/Dungeonworld/Gen/BossRooms/ProofingHallWatcher.cs:177-186 | Content/Scenarios/OldNet/NPCs/OldNetThreatField.cs:597-605 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 9+ corresponding lines) Content/NPCs/BloomsandSerpents/BssHead.cs:389 — Content/NPCs/BloomsandSerpents/BssHead.cs:389-397 | Content/NPCs/FestersandSerpents/FssHead.cs:343-351 | Content/NPCs/ScrapCommanders/ScrapCommander.cs:309-317 | Content/NPCs/SeaShrimp/SeaShrimpBoss.cs:251-259 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 9+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Projectiles/EocFogCloud.cs:58 — Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Projectiles/EocFogCloud.cs:58-68 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistPlanetAimLine.cs:35-45 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistUmbraShade.cs:104-112 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistZodiacRing.cs:37-48 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 9+ corresponding lines) Content/Items/Ranged/BarrenBow.cs:437 — Content/Items/Ranged/BarrenBow.cs:437-446 | Content/Items/Ranged/HyperionBarrage.cs:696-704 | Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraSporeCloud.cs:26-36 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenGaleFieldProj.cs:30-38 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 9+ corresponding lines) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetNet.cs:23 — Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetNet.cs:23-31 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownNet.cs:30-40 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownNet.cs:93-103 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaPlayerDrownNet.cs:22-31 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 9+ corresponding lines) Content/GameModes/BrutalMobs/Ambience/Ashreign/AshreignAmbience.cs:217 — Content/GameModes/BrutalMobs/Ambience/Ashreign/AshreignAmbience.cs:217-225 | Content/GameModes/BrutalMobs/Ambience/Lumindepth/LumindepthAmbience.cs:101-109 | Content/GameModes/BrutalMobs/Ambience/Mireheart/MireheartAmbience.cs:318-326 | Content/GameModes/BrutalMobs/Ambience/Nyxdepth/NyxdepthAmbience.cs:137-145 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 9+ corresponding lines) Content/GameModes/BrutalMobs/Ambience/Brinefume/BrinefumeAmbience.cs:189 — Content/GameModes/BrutalMobs/Ambience/Brinefume/BrinefumeAmbience.cs:189-197 | Content/GameModes/BrutalMobs/Ambience/Duskhall/DuskhallAmbience.cs:568-576 | Content/GameModes/BrutalMobs/Ambience/Sunkendune/SunkenduneAmbience.cs:75-83 | Content/GameModes/BrutalMobs/Ambience/Tidecall/TidecallAmbience.cs:150-158 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 9+ corresponding lines) Content/LegendWeapon/HalibutLegend/DomainSkills/FishTeleport.cs:209 — Content/LegendWeapon/HalibutLegend/DomainSkills/FishTeleport.cs:209-217 | Content/LegendWeapon/HalibutLegend/DomainSkills/RestartFish.cs:305-313 | Content/LegendWeapon/HalibutLegend/DomainSkills/Superposition.cs:293-302 | Content/LegendWeapon/HalibutLegend/DomainSkills/YourLevelIsTooLow.cs:105-113 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 9+ corresponding lines) Content/Scenarios/Dungeonworld/NPCs/Elites/DungeonworldEliteGate.cs:89 — Content/Scenarios/Dungeonworld/NPCs/Elites/DungeonworldEliteGate.cs:89-97 | Content/Scenarios/Kiyume/NPCs/KiyumeHound.cs:793-801 | Content/Scenarios/Kiyume/NPCs/KiyumeWhiteHound.cs:237-245 | Content/Scenarios/Kiyume/NPCs/KiyumeYokaiGate.cs:135-143 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 9+ corresponding lines) Content/Buffs/FrenziedMachineSoul.cs:14 — Content/Buffs/FrenziedMachineSoul.cs:14-22 | Content/Items/Summon/BloomCallers/BloomCaller.cs:60-68 | Content/Items/Summon/Deepclaws/Deepclaw.cs:77-85 | Content/Items/Summon/EyekiteStaffs/EyekiteStaff.cs:51-59 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×15
  • Duplicated block (22 lines × 2) Content/GameModes/BrutalMobs/Ambience/Fleshfen/FleshfenHazeRender.cs:118 — Content/GameModes/BrutalMobs/Ambience/Fleshfen/FleshfenHazeRender.cs:118-139 | Content/GameModes/BrutalMobs/Ambience/Sporeshine/SporeshineRender.cs:136-157 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/Fleshfen/FleshfenHazeRender.cs:118` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 2) Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:267 — Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:267-288 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpWaterBolt.cs:57-78 — before extracting anything, compare `Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs` and `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpWaterBolt.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 116 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:267` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:290` calls `OnHitNPC`, `AddBuff` and `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpWaterBolt.cs:80` 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 (22 lines × 2) Content/Items/Melee/Arbiters/ArbiterManifestationSystem.cs:296 — Content/Items/Melee/Arbiters/ArbiterManifestationSystem.cs:296-317 | Content/Items/Melee/WeaverGrievanceses/WGManifestationSystem.cs:288-309 — before extracting anything, compare `Content/Items/Melee/Arbiters/ArbiterManifestationSystem.cs` and `Content/Items/Melee/WeaverGrievanceses/WGManifestationSystem.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Arbiters/ArbiterManifestationSystem.cs:296` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainSky.cs:110 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainSky.cs:110-131 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainSky.cs:91-112 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainSky.cs` and `Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainSky.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (22 lines × 2) Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:301 — Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:301-322 | Content/Items/Modifys/RBloodButcherer.cs:246-267 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:301` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 2) Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerStorageProvider.cs:180 — Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerStorageProvider.cs:180-201 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerStorageProvider.cs:120-141 — before extracting anything, compare `Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerStorageProvider.cs` and `Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerStorageProvider.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 70 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerStorageProvider.cs:180` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (22 lines × 2) Content/Items/Melee/EnergySword.cs:289 — Content/Items/Melee/EnergySword.cs:289-310 | Content/Items/Melee/RebelBlade.cs:310-331 — before extracting anything, compare `Content/Items/Melee/EnergySword.cs` and `Content/Items/Melee/RebelBlade.cs` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 375 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/EnergySword.cs:289` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:441 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:441-462 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:457-478 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs` as WHOLE FILES: this scan already matched 68 separate duplicated blocks between them, totalling at least 933 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:441` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:933 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:933-954 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:962-983 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:933` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 2) Content/NPCs/BloomsandSerpents/BssBody.cs:226 — Content/NPCs/BloomsandSerpents/BssBody.cs:226-247 | Content/NPCs/FestersandSerpents/FssBody.cs:272-293 — before extracting anything, compare `Content/NPCs/BloomsandSerpents/BssBody.cs` and `Content/NPCs/FestersandSerpents/FssBody.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BloomsandSerpents/BssBody.cs:226` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 2) Content/Scenarios/Dungeonworld/Gen/Rooms/RoomLayout.cs:98 — Content/Scenarios/Dungeonworld/Gen/Rooms/RoomLayout.cs:98-119 | Content/Scenarios/OldNet/Gen/Rooms/OldNetRoomLayout.cs:53-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (22 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:828 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:828-849 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1003-1024 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs` as WHOLE FILES: this scan already matched 66 separate duplicated blocks between them, totalling at least 737 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:828` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:270 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:270-291 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:268-289 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs` as WHOLE FILES: this scan already matched 69 separate duplicated blocks between them, totalling at least 866 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (22 lines × 2) Content/MainMenus/Himayo/HimayoMenuButtons.cs:250 — Content/MainMenus/Himayo/HimayoMenuButtons.cs:250-271 | Content/MainMenus/Shenyo/ShenyoMenuButtons.cs:252-273 — before extracting anything, compare `Content/MainMenus/Himayo/HimayoMenuButtons.cs` and `Content/MainMenus/Shenyo/ShenyoMenuButtons.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 174 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (22 lines × 2) Content/Scenarios/Dungeonworld/UI/DungeonworldLoadingScreen.cs:645 — Content/Scenarios/Dungeonworld/UI/DungeonworldLoadingScreen.cs:645-666 | Content/Scenarios/Hadalworld/UI/HadalworldLoadingScreen.cs:506-527 — before extracting anything, compare `Content/Scenarios/Dungeonworld/UI/DungeonworldLoadingScreen.cs` and `Content/Scenarios/Hadalworld/UI/HadalworldLoadingScreen.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×15
  • Duplicated block (20 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:108 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:108-127 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:101-120 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs` as WHOLE FILES: this scan already matched 68 separate duplicated blocks between them, totalling at least 933 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (20 lines × 2) Content/NPCs/BloomsandSerpents/Core/BssDirector.cs:68 — Content/NPCs/BloomsandSerpents/Core/BssDirector.cs:68-87 | Content/NPCs/FestersandSerpents/Core/FssDirector.cs:34-53 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (20 lines × 2) Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:334 — Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:334-353 | Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:271-290 — before extracting anything, compare `Content/QuestLogs/Styles/DraedonQuestLogStyle.cs` and `Content/QuestLogs/Styles/HotwindQuestLogStyle.cs` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 377 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 (20 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaShrimpWaterBolt.cs:43 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaShrimpWaterBolt.cs:43-62 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpWaterBolt.cs:43-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaShrimpWaterBolt.cs:43` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 2) Content/NPCs/BloomsandSerpents/States/BssDeathState.cs:122 — Content/NPCs/BloomsandSerpents/States/BssDeathState.cs:122-141 | Content/NPCs/FestersandSerpents/States/FssDeathState.cs:150-169 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BloomsandSerpents/States/BssDeathState.cs:122` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note first that the copies are not typed on the same thing: the declarations holding them bind `ctx` to `BssStateContext` in one and `FssStateContext` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (20 lines × 2) Content/Items/Melee/DestroyersBladeEXs/DestroyerBiteProj.cs:424 — Content/Items/Melee/DestroyersBladeEXs/DestroyerBiteProj.cs:424-443 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:1048-1067 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (20 lines × 2) Content/LegendWeapon/KikasaLegend/UI/KikasaHudTooltip.cs:55 — Content/LegendWeapon/KikasaLegend/UI/KikasaHudTooltip.cs:55-74 | Content/LegendWeapon/OnikiriLegend/UI/OniHudTooltipOverlay.cs:49-68 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/UI/KikasaHudTooltip.cs` and `Content/LegendWeapon/OnikiriLegend/UI/OniHudTooltipOverlay.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/UI/KikasaHudTooltip.cs:55` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 2) Content/Scenarios/Dungeonworld/UI/DungeonworldLoadingScreen.cs:669 — Content/Scenarios/Dungeonworld/UI/DungeonworldLoadingScreen.cs:669-688 | Content/Scenarios/Hadalworld/UI/HadalworldLoadingScreen.cs:530-549 — before extracting anything, compare `Content/Scenarios/Dungeonworld/UI/DungeonworldLoadingScreen.cs` and `Content/Scenarios/Hadalworld/UI/HadalworldLoadingScreen.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/UI/DungeonworldLoadingScreen.cs:669` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 2) Content/EntrustManager/Styles/DraedonManagerStyle.cs:132 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:132-151 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:127-146 — before extracting anything, compare `Content/EntrustManager/Styles/DraedonManagerStyle.cs` and `Content/EntrustManager/Styles/HotwindManagerStyle.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 442 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/EntrustManager/Styles/DraedonManagerStyle.cs:132` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 2) Content/LegendWeapon/HalibutLegend/DomainSkills/Superposition.cs:133 — Content/LegendWeapon/HalibutLegend/DomainSkills/Superposition.cs:133-152 | Content/LegendWeapon/HalibutLegend/DomainSkills/YourLevelIsTooLow.cs:589-608 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/DomainSkills/Superposition.cs:133` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:759 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:759-778 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:738-757 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs` as WHOLE FILES: this scan already matched 79 separate duplicated blocks between them, totalling at least 1151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (20 lines × 2) Content/LegendWeapon/KikasaLegend/UI/KikasaHudTooltip.cs:119 — Content/LegendWeapon/KikasaLegend/UI/KikasaHudTooltip.cs:119-138 | Content/LegendWeapon/OnikiriLegend/UI/OniHudTooltipOverlay.cs:151-170 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/UI/KikasaHudTooltip.cs` and `Content/LegendWeapon/OnikiriLegend/UI/OniHudTooltipOverlay.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/UI/KikasaHudTooltip.cs:119` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (20 lines × 2) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:353 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:353-372 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:476-495 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` and `Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 850 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:353` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:374` calls `SpawnSweepFX` and `Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:496` 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 (20 lines × 2) Content/Scenarios/OldNet/Tiles/OldNetDataNodeTile.cs:95 — Content/Scenarios/OldNet/Tiles/OldNetDataNodeTile.cs:95-114 | Content/Scenarios/OldNet/Tiles/OldNetEncryptedNodeTile.cs:115-134 — before extracting anything, compare `Content/Scenarios/OldNet/Tiles/OldNetDataNodeTile.cs` and `Content/Scenarios/OldNet/Tiles/OldNetEncryptedNodeTile.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 84 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 (20 lines × 2) Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteDiveOmen.cs:137 — Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteDiveOmen.cs:137-156 | Content/GameModes/BrutalMobs/Sky/Projectiles/SkyGaleDiveOmen.cs:131-150 — before extracting anything, compare `Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteDiveOmen.cs` and `Content/GameModes/BrutalMobs/Sky/Projectiles/SkyGaleDiveOmen.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 156 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteDiveOmen.cs:137` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (5 lines × 8) · ×15
  • Duplicated block (5 lines × 8) Content/Items/Melee/OniMacheteHands.cs:1106 — Content/Items/Melee/OniMacheteHands.cs:1106-1110 | Content/Items/Melee/OniMacheteHands.cs:1349-1353 | Content/LegendWeapon/HalibutLegend/FishSkills/FishEaterofPlankton.cs:405-409 | Content/LegendWeapon/HalibutLegend/FishSkills/FishFallenStarVFX.cs:213-217 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1030-1034 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaMinionDrownFX.cs:468-472 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaPlayerDrownFX.cs:504-508 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaScourgeFX.cs:765-769 — there are 8 copies across 7 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 8 sites; resolving a subset leaves the remainder to drift apart.
  • Duplicated block (5 lines × 8) Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdMarksmanOmen.cs:186 — Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdMarksmanOmen.cs:186-190 | Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:144-148 | Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgStabGlintOmen.cs:132-136 | Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyGhostNameThread.cs:161-165 | Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyRavenSwoopOmen.cs:146-150 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkClawCrossProj.cs:185-189 | Content/GameModes/BrutalMobs/Sky/Projectiles/SkyGaleDiveOmen.cs:126-130 | Content/GameModes/BrutalMobs/Temple/Projectiles/TempleDiveOmen.cs:140-144 — before extracting anything, compare `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs` and `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgStabGlintOmen.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 89 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdMarksmanOmen.cs:186` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 8) Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:523 — Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:523-527 | Content/Items/Melee/DestroyersBlade.cs:148-152 | Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:142-146 | Content/Items/Melee/DragonsScaleGreatsword.cs:164-168 | Content/Items/Melee/EnergySword.cs:178-182 | Content/Items/Melee/RebelBlade.cs:202-206 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:183-187 | Content/Items/Modifys/RTerraBlades/RTerraBladeHeld.cs:681-685 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 8 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 8 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:523` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 8) Content/Scenarios/OldNet/Tiles/OldNetAccessTerminalTile.cs:130 — Content/Scenarios/OldNet/Tiles/OldNetAccessTerminalTile.cs:130-134 | Content/Scenarios/OldNet/Tiles/OldNetDataNodeTile.cs:106-110 | Content/Scenarios/OldNet/Tiles/OldNetEchoNodeTile.cs:106-110 | Content/Scenarios/OldNet/Tiles/OldNetEncryptedNodeTile.cs:126-130 | Content/Scenarios/OldNet/Tiles/OldNetEventNodeTile.cs:99-103 | Content/Scenarios/OldNet/Tiles/OldNetLogoutTerminalTile.cs:83-87 | Content/Scenarios/OldNet/Tiles/OldNetRelayTile.cs:93-97 | Content/Scenarios/OldNet/Tiles/OldNetTripwireTile.cs:90-94 — 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 8 call sites, so a change lands once.
  • Duplicated block (5 lines × 8) Content/GameModes/BrutalMobs/Ambience/Frostveil/FrostveilPRT.cs:67 — Content/GameModes/BrutalMobs/Ambience/Frostveil/FrostveilPRT.cs:67-72 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDoubleCodVFX.cs:148-153 | Content/LegendWeapon/HalibutLegend/FishSkills/FishHoneyVFX.cs:191-195 | Content/LegendWeapon/HalibutLegend/FishSkills/FishSwarmVFX.cs:320-325 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Rendering/BKSParticles.cs:68-73 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Rendering/QueenBeePRT.cs:76-80 | Content/PRTTypes/PRT_HeartcarverDroplet.cs:53-57 | Content/PRTTypes/PRT_OniPuddleRise.cs:75-80 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 8 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 8 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/Frostveil/FrostveilPRT.cs:67` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (5 lines × 8) Content/Industrials/ElectricPowers/HealingStations/HealStationTile.cs:99 — Content/Industrials/ElectricPowers/HealingStations/HealStationTile.cs:99-104 | Content/Industrials/ElectricPowers/ShieldGenerators/ShieldGeneratorTile.cs:99-104 | Content/Industrials/ElectricPowers/Suppressors/PacifierTowerTile.cs:99-104 | Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:180-184 | Content/Industrials/ElectricPowers/Turrets/CryoTurrets/CryoTurretTile.cs:99-104 | Content/Industrials/ElectricPowers/Turrets/FlameTurrets/FlameTurretTile.cs:99-104 | Content/Industrials/ElectricPowers/Turrets/LaserTurrets/LaserTurretTile.cs:99-104 | Content/Tiles/NeutronStarIngotTile.cs:38-42 — before extracting anything, compare `Content/Industrials/ElectricPowers/HealingStations/HealStationTile.cs` and `Content/Industrials/ElectricPowers/ShieldGenerators/ShieldGeneratorTile.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (5 lines × 8) Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:274 — Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:274-278 | Content/Items/Accessories/BrutalRelics/QueenBee/SwarmVortexProj.cs:426-430 | Content/NPCs/BloomsandSerpents/Projectiles/BssDashOmen.cs:123-127 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerStrikeTelegraph.cs:112-116 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronGeyserProj.cs:158-162 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronTelegraph.cs:126-130 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowLungeOmen.cs:187-192 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Projectiles/QueenBeeTelegraphLine.cs:107-111 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 8 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 8 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:274` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (5 lines × 8) Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadCommandRender.cs:188 — Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadCommandRender.cs:188-192 | Content/Items/Accessories/BrutalRelics/Twins/TwinPupilOrbiter.cs:530-534 | Content/Items/Accessories/BrutalRelics/Twins/TwinPupilShots.cs:339-344 | Content/Items/Accessories/BrutalRelics/Twins/TwinPupilTetherBeam.cs:222-227 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSShockwaveProj.cs:97-101 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpLeapVortex.cs:147-152 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpMiniVortex.cs:146-151 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpVortexWall.cs:148-153 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 8 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 8 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadCommandRender.cs:188` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (5 lines × 8) Content/Items/Accessories/EmblemOfDread.cs:142 — Content/Items/Accessories/EmblemOfDread.cs:142-146 | Content/Items/Accessories/EyeOfSingularity.cs:98-102 | Content/Items/Melee/NeutronGlaive.cs:1254-1258 | Content/Items/Melee/NeutronGlaive.cs:1320-1324 | Content/Items/Melee/NeutronScythe.cs:324-328 | Content/Items/Melee/SpearOfLonginuses/PilgrimsFury.cs:125-129 | Content/Items/Ranged/NeutronBows/EXNeutronExplosionRanged.cs:31-35 | Content/Items/Ranged/NeutronBows/NeutronExplosionRanged.cs:30-34 — there are 8 copies across 7 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 8 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/EmblemOfDread.cs:142` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Melee/NeutronGlaive.cs:1319` calls `PlaySound` and `Content/Items/Melee/NeutronGlaive.cs:1253` does not — after which the two agree again for 4 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 (5 lines × 8) Content/Items/Melee/CursedflameBloodfists/CursedflameFistProj.cs:187 — Content/Items/Melee/CursedflameBloodfists/CursedflameFistProj.cs:187-191 | Content/Items/Melee/StormGoddessSpears/AncientStormGoddessSpear.cs:316-320 | Content/Items/Melee/StormGoddessSpears/AncientStormGoddessSpear.cs:481-485 | Content/Items/Ranged/NeutronBows/EXNeutronArrow.cs:78-82 | Content/Items/Stones/GraniteMarbleVFX.cs:78-82 | Content/Items/Summon/WhiplashGalactica.cs:234-238 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerLaser.cs:123-127 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/DeadLaser.cs:81-85 — before extracting anything, compare `Content/Items/Melee/StormGoddessSpears/AncientStormGoddessSpear.cs` and `Content/Items/Ranged/NeutronBows/EXNeutronArrow.cs` 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (5 lines × 8) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomNeedle.cs:79 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomNeedle.cs:79-83 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:752-756 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1011-1015 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:850-854 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeLaserBolt.cs:95-99 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:737-741 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeStinger.cs:173-177 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaShrimpWaterBolt.cs:82-86 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 8 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 8 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomNeedle.cs:79` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:758` calls `Configure`, `Vector2`, `ToRotation` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:855` 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 (5 lines × 8) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:1078 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:1078-1082 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1549-1553 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:1168-1172 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:1087-1091 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1389-1393 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1456-1460 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:1362-1366 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:1189-1193 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs` as WHOLE FILES: this scan already matched 48 separate duplicated blocks between them, totalling at least 508 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:1078` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:1084` calls `IsFlowerSeg`, `PetalDrift`, `NextVector2Circular` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:1367` 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 (5 lines × 8) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:534 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:534-538 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:427-431 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:390-394 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:383-387 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:493-497 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:461-465 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:499-503 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:477-481 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 8 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 8 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:386` calls `FindTarget` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:491` does not — after which the two agree again for 3 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 (5 lines × 8) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:1166 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:1166-1170 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:871-875 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1387-1391 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:893-897 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1454-1458 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:963-967 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:940-944 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1666-1670 — there are 8 copies across 5 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 8 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:1166` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (5 lines × 8) Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:263 — Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:263-267 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:532-536 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:647-651 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDeathSickle.cs:298-302 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT2.cs:364-368 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsOdditiesFlurryHeldBase.cs:254-258 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsScourgeoftheCorruptor.cs:469-473 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsScourgeoftheCorruptor.cs:556-560 — there are 8 copies across 5 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 8 sites; resolving a subset leaves the remainder to drift apart. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:539` calls `LoadItem` and `Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:654` 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.
D4 · Code Duplication · Duplicated block (4–5 lines × 3) · ×15
  • Duplicated block (4–5 lines × 3) Content/Cyberwares/UIs/CyberBodyRenderer.cs:519 — Content/Cyberwares/UIs/CyberBodyRenderer.cs:519-523 | Content/Cyberwares/UIs/CyberBodyRenderer.cs:580-584 | Content/Cyberwares/UIs/CyberBodyRenderer.cs:626-629 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Cyberwares/UIs/CyberBodyRenderer.cs:519` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Cyberwares/UIs/CyberBodyRenderer.cs:579` calls `Lerp` and `Content/Cyberwares/UIs/CyberBodyRenderer.cs:626` does not — after which the two agree again for 3 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 (4–5 lines × 3) Content/GameModes/BrutalMobs/Ambience/Frostveil/Projectiles/FrostveilGaleWallProj.cs:159 — Content/GameModes/BrutalMobs/Ambience/Frostveil/Projectiles/FrostveilGaleWallProj.cs:159-162 | Content/GameModes/BrutalMobs/Ambience/Frostveil/Projectiles/FrostveilGaleWallProj.cs:170-174 | Content/GameModes/BrutalMobs/Ambience/Frostveil/Projectiles/FrostveilGaleWallProj.cs:407-411 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/Frostveil/Projectiles/FrostveilGaleWallProj.cs:159` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/GameModes/BrutalMobs/Ambience/Frostveil/Projectiles/FrostveilGaleWallProj.cs:162` calls `Configure`, `Next`, `NextFloat` and `Content/GameModes/BrutalMobs/Ambience/Frostveil/Projectiles/FrostveilGaleWallProj.cs:174` does not — after which the two agree again for 3 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 (4–5 lines × 3) Content/GameModes/BrutalMobs/Ambience/Sunkendune/Projectiles/SunkenduneSinkPitProj.cs:207 — Content/GameModes/BrutalMobs/Ambience/Sunkendune/Projectiles/SunkenduneSinkPitProj.cs:207-211 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmIcingPatchProj.cs:148-152 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesIceSlickZone.cs:180-183 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/Sunkendune/Projectiles/SunkenduneSinkPitProj.cs:207` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (4–5 lines × 3) Content/GameModes/GodSmith/Weapons/Broadswords/GsInfluxWaver.cs:230 — Content/GameModes/GodSmith/Weapons/Broadswords/GsInfluxWaver.cs:230-233 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsScourgeoftheCorruptor.cs:275-279 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsScourgeoftheCorruptor.cs:455-459 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/Broadswords/GsInfluxWaver.cs:230` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (4–5 lines × 3) Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:545 — Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:545-550 | Content/Industrials/Modifys/ChargingStationUI.cs:391-395 | Content/Narrative/Presentation/Skins/StarStream/StarStreamPanelDraw.cs:188-191 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:545` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (4–5 lines × 3) Content/Industrials/Modifys/ChargingStationUI.cs:538 — Content/Industrials/Modifys/ChargingStationUI.cs:538-542 | Content/Narrative/MusicToast.cs:417-421 | Content/Narrative/Presentation/Skins/Tzeentch/TzeentchPanelDraw.cs:36-39 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. 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 (4–5 lines × 3) Content/Items/Magic/CommandersStaff.cs:310 — Content/Items/Magic/CommandersStaff.cs:310-314 | Content/Items/Magic/Elysiums/Serpents/HolySerpent.cs:318-322 | Content/Items/Magic/Elysiums/Serpents/SnakeConversionWave.cs:135-138 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/CommandersStaff.cs:310` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Magic/Elysiums/Serpents/HolySerpent.cs:325` calls `PlaySound` and `Content/Items/Magic/CommandersStaff.cs:317` does not — after which the two agree again for 3 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 (4–5 lines × 3) Content/Items/Melee/DestroyersBladeEXs/DestroyerBiteProj.cs:294 — Content/Items/Melee/DestroyersBladeEXs/DestroyerBiteProj.cs:294-297 | Content/Items/Melee/DestroyersBladeEXs/DestroyerShadowBolt.cs:170-174 | Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:454-458 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DestroyersBladeEXs/DestroyerBiteProj.cs:294` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (4–5 lines × 3) Content/LegendWeapon/HalibutLegend/FishSkills/Fishotroning.cs:1217 — Content/LegendWeapon/HalibutLegend/FishSkills/Fishotroning.cs:1217-1222 | Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs:2799-2802 | Content/Wraiths/Projectiles/GhostHandProj.cs:595-599 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/Fishotroning.cs:1217` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (4–5 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonOrb.cs:241 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonOrb.cs:241-245 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeLaserBolt.cs:134-137 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeStinger.cs:232-236 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. 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 (4–5 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaWisps/KikasaWispBurn.cs:25 — Content/LegendWeapon/KikasaLegend/KikasaWisps/KikasaWispBurn.cs:25-28 | Content/LegendWeapon/KikasaLegend/KikasaWisps/KikasaWispBurn.cs:34-38 | Content/LegendWeapon/KikasaLegend/KikasaWisps/KikasaWispFX.cs:179-183 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaWisps/KikasaWispBurn.cs:34` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (4–5 lines × 3) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSlashRenderer.cs:81 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSlashRenderer.cs:81-84 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepRenderer.cs:78-82 | Content/LegendWeapon/OnikiriLegend/OniSakuraFlights/OniSakuraFlowRenderer.cs:38-43 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (4–5 lines × 3) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Rendering/EowMotionFX.cs:114 — Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Rendering/EowMotionFX.cs:114-119 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Rendering/WofMotionFX.cs:47-51 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Rendering/WofMotionFX.cs:57-60 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Rendering/EowMotionFX.cs:114` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (4–5 lines × 3) Content/NPCs/BrutalNPCs/BrutalMoonLord/States/MLordCrescentCloseState.cs:187 — Content/NPCs/BrutalNPCs/BrutalMoonLord/States/MLordCrescentCloseState.cs:187-191 | Content/NPCs/BrutalNPCs/BrutalMoonLord/States/MLordMoonBiteState.cs:126-130 | Content/NPCs/BrutalNPCs/BrutalMoonLord/States/MLordTidalPalmsState.cs:280-283 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMoonLord/States/MLordCrescentCloseState.cs:187` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (4–5 lines × 3) Content/Tiles/BloodAltars/BloodAltarRite.cs:289 — Content/Tiles/BloodAltars/BloodAltarRite.cs:289-292 | Content/Tiles/BloodAltars/BloodAltarRite.cs:334-338 | Content/Tiles/BloodAltars/BloodAltarRite.cs:357-361 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Tiles/BloodAltars/BloodAltarRite.cs:289` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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.
D4 · Code Duplication · Duplicated block (25 lines × 2) · ×14
  • Duplicated block (25 lines × 2) Content/Scenarios/SupCal/End/EternalBlazingNow/EbnBarsDisplay.cs:475 — Content/Scenarios/SupCal/End/EternalBlazingNow/EbnBarsDisplay.cs:475-499 | Content/Scenarios/SupCal/End/EternalBlazingNow/EbnBarsDisplay.cs:530-554 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/SupCal/End/EternalBlazingNow/EbnBarsDisplay.cs:475` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Scenarios/SupCal/End/EternalBlazingNow/EbnBarsDisplay.cs:555` calls `Color` and `Content/Scenarios/SupCal/End/EternalBlazingNow/EbnBarsDisplay.cs:500` 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 (25 lines × 2) Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:858 — Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:858-882 | Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:999-1023 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:858` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (25 lines × 2) Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs:365 — Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs:365-389 | Content/Scenarios/Shenyo/ShenyoPortraitRainRenderer.cs:361-385 — before extracting anything, compare `Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs` and `Content/Scenarios/Shenyo/ShenyoPortraitRainRenderer.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 211 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs:365` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Scenarios/Shenyo/ShenyoPortraitRainRenderer.cs:357` calls `SetValue`, `ToVector3` and `Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs:362` 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 (25 lines × 2) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:484 — Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:484-508 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaReset.cs:477-501 — before extracting anything, compare `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs` and `Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaReset.cs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaReset.cs:475` calls `ClearRain` and `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:483` 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 (25 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1185 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1185-1209 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:1136-1160 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs` as WHOLE FILES: this scan already matched 79 separate duplicated blocks between them, totalling at least 1151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1185` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (25 lines × 2) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberChargeOrbProj.cs:588 — Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberChargeOrbProj.cs:588-612 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberTraceBeamProj.cs:434-458 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberChargeOrbProj.cs:588` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberTraceBeamProj.cs:460` calls `Lerp` and `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberChargeOrbProj.cs:613` 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 (25 lines × 2) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowGeyserProj.cs:132 — Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowGeyserProj.cs:132-156 | Content/NPCs/FestersandSerpents/Projectiles/FssGeyserColumn.cs:136-160 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowGeyserProj.cs` and `Content/NPCs/FestersandSerpents/Projectiles/FssGeyserColumn.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 156 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowGeyserProj.cs:132` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (25 lines × 2) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsCrossDashState.cs:53 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsCrossDashState.cs:53-77 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsTetherSweepState.cs:58-82 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsCrossDashState.cs:53` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (25 lines × 2) Content/GameModes/BrutalMobs/Legion/Projectiles/LegionScoutOmen.cs:88 — Content/GameModes/BrutalMobs/Legion/Projectiles/LegionScoutOmen.cs:88-112 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionVolleyOmen.cs:69-93 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Legion/Projectiles/LegionScoutOmen.cs:88` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (25 lines × 2) Content/GameModes/BrutalMobs/Sandveil/SandveilBrutalNPC.cs:306 — Content/GameModes/BrutalMobs/Sandveil/SandveilBrutalNPC.cs:306-330 | Content/GameModes/BrutalMobs/Wastes/WastesBrutalNPC.cs:252-276 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (25 lines × 2) Content/GameModes/GodSmith/Weapons/MagicChant/GsCursedFlames.cs:174 — Content/GameModes/GodSmith/Weapons/MagicChant/GsCursedFlames.cs:174-198 | Content/GameModes/GodSmith/Weapons/MagicChant/GsNettleBurst.cs:199-223 — before extracting anything, compare `Content/GameModes/GodSmith/Weapons/MagicChant/GsCursedFlames.cs` and `Content/GameModes/GodSmith/Weapons/MagicChant/GsNettleBurst.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 59 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/MagicChant/GsCursedFlames.cs:174` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (25 lines × 2) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:750 — Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:750-774 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaReset.cs:731-755 — before extracting anything, compare `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs` and `Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaReset.cs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (25 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1538 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1538-1562 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1605-1629 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1538` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (25 lines × 2) Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:138 — Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:138-162 | Content/Scenarios/Kiame/Overlay/OniRainExitTransition.cs:101-125 — before extracting anything, compare `Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs` and `Content/Scenarios/Kiame/Overlay/OniRainExitTransition.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 186 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:138` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10 lines × 5) · ×14
  • Duplicated block (10 lines × 5) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:420 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:420-429 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs:485-494 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:347-356 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconUI.cs:382-391 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:425-434 — before extracting anything, compare `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs` and `Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 188 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:420` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 5) Content/Items/Ranged/CrystalDimming.cs:20 — Content/Items/Ranged/CrystalDimming.cs:20-29 | Content/Items/Ranged/DarkFrostSolstice.cs:26-35 | Content/Items/Ranged/SnowQuay.cs:22-31 | Content/Items/Ranged/SnowQuayMK2.cs:23-32 | Content/Items/Ranged/UniversalFrost.cs:21-30 — 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 5 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Ranged/CrystalDimming.cs:20` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Ranged/DarkFrostSolstice.cs:25` calls `SetStaticDefaults` and `Content/Items/Ranged/CrystalDimming.cs:18` does not — after which the two agree again for 3 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 (10 lines × 5) Content/GameModes/GodSmith/Weapons/SummonSentries/Projectiles/GsSentryBurstProj.cs:30 — Content/GameModes/GodSmith/Weapons/SummonSentries/Projectiles/GsSentryBurstProj.cs:30-39 | Content/GameModes/GodSmith/Weapons/SummonSentries/Projectiles/GsSentryZoneProj.cs:33-42 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangProj.cs:50-59 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailHead.cs:60-69 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoProj.cs:59-68 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/SummonSentries/Projectiles/GsSentryBurstProj.cs:30` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 5) Content/LegendWeapon/HalibutLegend/FishSkills/FishBone.cs:148 — Content/LegendWeapon/HalibutLegend/FishSkills/FishBone.cs:148-157 | Content/LegendWeapon/HalibutLegend/FishSkills/FishRock.cs:142-151 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberPrismLaserProj.cs:74-83 | Content/LegendWeapon/SHPCLegend/Modules/Frame/QuantumFrameModule.cs:210-219 | Content/LegendWeapon/SHPCLegend/Modules/Stock/LightStockModule.cs:111-120 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishBone.cs:148` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:928 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:928-937 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:1107-1116 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1315-1324 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:928-937 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1364-1373 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:928` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:544 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:544-553 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:397-406 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:390-399 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:440-449 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:468-477 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:544` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:542` calls `AddShellAt` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:395` 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 (10 lines × 5) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendCleave.cs:93 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendCleave.cs:93-102 | Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:100-109 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleCut.cs:102-111 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleRing.cs:56-65 | Content/LegendWeapon/OnikiriLegend/OniZanshinSlashs/OniZanshinSlash.cs:139-148 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendCleave.cs:93` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 5) Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaRender.cs:81 — Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaRender.cs:81-90 | Content/NPCs/BrutalNPCs/BrutalGolem/Core/GolemScreenEffects.cs:110-120 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Core/MLordScreenEffects.cs:96-106 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Core/SkeletronScreenEffects.cs:122-132 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Core/PrimeScreenEffects.cs:96-106 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalGolem/Core/GolemScreenEffects.cs` and `Content/NPCs/BrutalNPCs/BrutalMoonLord/Core/MLordScreenEffects.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaRender.cs:81` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (10 lines × 5) Content/LegendWeapon/HalibutLegend/UI/HalibutItemTooltipPanel.cs:39 — Content/LegendWeapon/HalibutLegend/UI/HalibutItemTooltipPanel.cs:39-48 | Content/LegendWeapon/OnikiriLegend/UI/OniItemTooltipPanel.cs:44-53 | Content/LegendWeapon/OnikiriLegend/UI/OniRegisterRenderer.cs:45-55 | Content/LegendWeapon/SHPCLegend/UI/SHPCItemTooltipPanel.cs:42-51 | Content/QuestLogs/Styles/Chronicle/ChroniclePen.cs:74-85 — before extracting anything, compare `Content/LegendWeapon/HalibutLegend/UI/HalibutItemTooltipPanel.cs` and `Content/LegendWeapon/OnikiriLegend/UI/OniItemTooltipPanel.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/UI/OniRegisterRenderer.cs:45` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (10 lines × 5) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1484 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1484-1495 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1200-1209 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleRing.cs:241-252 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleScar.cs:252-263 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1393-1404 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1484` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 5) Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordEclipseSky.cs:167 — Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordEclipseSky.cs:167-176 | Content/Scenarios/Himayo/ToriiShrines/ToriiDusk.cs:188-197 | Content/Scenarios/Shepel/CybCourses/CybCourseSky.cs:57-66 | Content/Wraiths/Abilities/CrimsonBrides/BrideHallSky.cs:152-161 | Content/Wraiths/Abilities/GhostRains/GhostRainAmbience.cs:152-161 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordEclipseSky.cs:167` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordEclipseSky.cs:166` calls `DrawFallback` and `Content/Scenarios/Himayo/ToriiShrines/ToriiDusk.cs:187` does not — after which the two agree again for 4 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 (10 lines × 5) Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmNutShellProj.cs:36 — Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmNutShellProj.cs:36-45 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmOrnamentProj.cs:27-36 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmPineNeedleProj.cs:24-33 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmStrafeBulletProj.cs:24-33 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtBroadsideBall.cs:31-40 — before extracting anything, compare `Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmNutShellProj.cs` and `Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmOrnamentProj.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 49 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 × 5) Content/NPCs/BloomsandSerpents/Projectiles/BssCactusBallProj.cs:31 — Content/NPCs/BloomsandSerpents/Projectiles/BssCactusBallProj.cs:31-40 | Content/NPCs/BloomsandSerpents/Projectiles/BssNeedleProj.cs:21-30 | Content/NPCs/BloomsandSerpents/Projectiles/BssPetalProj.cs:27-36 | Content/NPCs/BloomsandSerpents/Projectiles/BssSandGlob.cs:23-32 | Content/NPCs/BloomsandSerpents/Projectiles/BssWindPetalProj.cs:32-41 — before extracting anything, compare `Content/NPCs/BloomsandSerpents/Projectiles/BssNeedleProj.cs` and `Content/NPCs/BloomsandSerpents/Projectiles/BssPetalProj.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 38 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 × 5) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistArcanePulse.cs:44 — Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistArcanePulse.cs:44-53 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistCometProj.cs:36-45 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistFallingStar.cs:59-68 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistGazeBeam.cs:45-54 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistOrbitPath.cs:48-57 — 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 5 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistArcanePulse.cs:38` calls `Min`, `Clamp` and `Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistGazeBeam.cs:40` 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.
D4 · Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) · ×13
  • Edited copies of one member (3 members, 16+ corresponding lines) Content/LegendWeapon/OnikiriLegend/OniDismembers/OniDismember.cs:817 — Content/LegendWeapon/OnikiriLegend/OniDismembers/OniDismember.cs:817-840 | Content/LegendWeapon/OnikiriLegend/OniDismembers/OniPlayerDismember.cs:265-280 | Content/LegendWeapon/OnikiriLegend/OniOmokages/OniOmokage.cs:526-544 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 16+ corresponding lines) Content/Scenarios/OldNet/Tiles/OldNetRelicTile.cs:201 — Content/Scenarios/OldNet/Tiles/OldNetRelicTile.cs:201-217 | Content/Scenarios/OldNet/Tiles/OldNetRelicTile.cs:235-250 | Content/Scenarios/OldNet/Tiles/OldNetRelicTile.cs:273-288 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 16+ corresponding lines) Content/Industrials/UIs/IndustrialTerminalRenderer.cs:46 — Content/Industrials/UIs/IndustrialTerminalRenderer.cs:46-64 | Content/LegendWeapon/HalibutLegend/UI/HalibutRenderer.cs:447-463 | Content/MainMenus/Overs/AckRenderer.cs:278-293 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 16+ corresponding lines) Content/GameModes/GodSmith/Prefixes/Accessory/GodSmithViolentSurgeEndow.cs:44 — Content/GameModes/GodSmith/Prefixes/Accessory/GodSmithViolentSurgeEndow.cs:44-65 | Content/GameModes/GodSmith/Prefixes/Offense/GodSmithExecutionEndow.cs:51-66 | Content/GameModes/GodSmith/Prefixes/Rescue/GodSmithDesperationEndow.cs:56-71 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 16+ corresponding lines) Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:448 — Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:448-463 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleCut.cs:496-512 | Content/LegendWeapon/OnikiriLegend/OniZanshinSlashs/OniZanshinSlash.cs:587-603 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 16+ corresponding lines) Content/Items/Magic/Elysiums/Disciples/Bartholomew.cs:35 — Content/Items/Magic/Elysiums/Disciples/Bartholomew.cs:35-50 | Content/Items/Magic/Elysiums/Disciples/James.cs:38-53 | Content/Items/Magic/Elysiums/Disciples/Thaddaeus.cs:102-117 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 16+ corresponding lines) Content/GameModes/GodSmith/Weapons/Guns/GsVortexBeater.cs:43 — Content/GameModes/GodSmith/Weapons/Guns/GsVortexBeater.cs:43-58 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuXiFX.cs:54-69 | Content/Players/PlayerDeath.cs:509-524 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 16+ corresponding lines) Content/Industrials/ElectricPowers/Apiaries/ApiaryTP.cs:610 — Content/Industrials/ElectricPowers/Apiaries/ApiaryTP.cs:610-625 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:755-773 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatTP.cs:577-592 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 16+ corresponding lines) Content/QuestLogs/QLNodes/BossQuests.cs:634 — Content/QuestLogs/QLNodes/BossQuests.cs:634-652 | Content/QuestLogs/QLNodes/BossQuests.cs:663-678 | Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:10-25 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 16+ corresponding lines) Content/Scenarios/Himayo/ToriiShrines/ToriiShrine.cs:189 — Content/Scenarios/Himayo/ToriiShrines/ToriiShrine.cs:189-208 | Content/Scenarios/Kiame/Gate/KiameGateSpawn.cs:210-225 | Content/Scenarios/Kiame/Overlay/OniUmbrellaWorldSpawn.cs:202-217 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 16+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishAmanita.cs:108 — Content/LegendWeapon/HalibutLegend/FishSkills/FishAmanita.cs:108-124 | Content/LegendWeapon/HalibutLegend/FishSkills/FishAmanita.cs:126-141 | Content/LegendWeapon/HalibutLegend/FishSkills/FishAmanita.cs:160-176 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 16+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsDeathState.cs:30 — Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsDeathState.cs:30-45 | Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerDespawnState.cs:71-90 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowDeathState.cs:35-53 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 16+ corresponding lines) Content/Scenarios/Dungeonworld/NPCs/GaolDormantSkull.cs:74 — Content/Scenarios/Dungeonworld/NPCs/GaolDormantSkull.cs:74-90 | Content/Scenarios/Dungeonworld/NPCs/OverseerDormantRig.cs:95-110 | Content/Scenarios/Dungeonworld/NPCs/UndrownedThrone.cs:101-116 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 11+ corresponding lines) · ×13
  • Edited copies of one member (5 members, 11+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1281 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1281-1292 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:1339-1353 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1234-1248 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:1491-1501 | Content/NPCs/ScrapCommanders/ScrapCommander.cs:702-713 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 11+ corresponding lines) Content/Items/Accessories/BrutalRelics/EyeOfCthulhu/BloodfogIrisFX.cs:23 — Content/Items/Accessories/BrutalRelics/EyeOfCthulhu/BloodfogIrisFX.cs:23-33 | Content/Items/Accessories/BrutalRelics/EyeOfCthulhu/BloodfogIrisFX.cs:36-46 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Rendering/FishronMotionFX.cs:24-34 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Core/EmpressMotion.cs:196-206 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Core/EocMotion.cs:189-199 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 11+ corresponding lines) Content/GameModes/BrutalMobs/Ambience/Cindercrag/Projectiles/CindercragVentProj.cs:343 — Content/GameModes/BrutalMobs/Ambience/Cindercrag/Projectiles/CindercragVentProj.cs:343-355 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhVineLash.cs:143-153 | Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:264-275 | Content/NPCs/BloomsandSerpents/Projectiles/BssDashOmen.cs:68-79 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerIceSpikeProj.cs:247-258 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 11+ corresponding lines) Content/GameModes/GodSmith/Armors/PreHardmode/GsGladiatorArmor.cs:79 — Content/GameModes/GodSmith/Armors/PreHardmode/GsGladiatorArmor.cs:79-90 | Content/Items/Magic/Everdeeps/EverdeepRing.cs:71-81 | Content/Items/Melee/Shatterfangs/ShatterfangBigShard.cs:28-39 | Content/Items/Stones/Marbles/MarbleDisc.cs:76-86 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuXianFX.cs:62-73 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 11+ corresponding lines) Content/Industrials/ElectricPowers/Apiaries/ApiaryTile.cs:51 — Content/Industrials/ElectricPowers/Apiaries/ApiaryTile.cs:51-62 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherTile.cs:51-62 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerTile.cs:51-62 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTile.cs:51-62 | Content/Industrials/ElectricPowers/Sensors/SensorTile.cs:52-62 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 11+ corresponding lines) Content/GameModes/GodSmith/Weapons/Boomerangs/GsPossessedHatchet.cs:172 — Content/GameModes/GodSmith/Weapons/Boomerangs/GsPossessedHatchet.cs:172-182 | Content/GameModes/GodSmith/Weapons/SummonSentries/Projectiles/GsSentryBoltProj.cs:29-40 | Content/GameModes/GodSmith/Weapons/SummonSentries/Projectiles/GsSentryBurstProj.cs:30-41 | Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFistProj.cs:430-441 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBloodyManowar.cs:779-789 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 11+ corresponding lines) Content/Scenarios/Kiyume/NPCs/FacelessOneYokai.cs:88 — Content/Scenarios/Kiyume/NPCs/FacelessOneYokai.cs:88-98 | Content/Scenarios/Kiyume/NPCs/LanternGuideYokai.cs:82-95 | Content/Scenarios/Kiyume/NPCs/MinoFisherYokai.cs:66-79 | Content/Scenarios/Kiyume/NPCs/RidgeWalkerYokai.cs:77-90 | Content/Scenarios/Kiyume/NPCs/ScarecrowWatcherYokai.cs:73-87 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 11+ corresponding lines) Content/GameModes/BrutalMobs/Martians/Projectiles/MrtScutlixHeavyBolt.cs:33 — Content/GameModes/BrutalMobs/Martians/Projectiles/MrtScutlixHeavyBolt.cs:33-43 | Content/GameModes/GodSmith/Weapons/MagicCataclysm/Projectiles/GsAuroraCurtainDirector.cs:17-30 | Content/Items/Accessories/BrutalRelics/Twins/TwinPupilShots.cs:24-34 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCloud.cs:734-746 | Content/LegendWeapon/HalibutLegend/FishSkills/FishFallenStar.cs:177-188 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 11+ corresponding lines) Content/Items/Accessories/ArcaneThroneOfEternity.cs:78 — Content/Items/Accessories/ArcaneThroneOfEternity.cs:78-88 | Content/Items/Accessories/ArcaneThroneOfEternity.cs:354-364 | Content/Items/Accessories/EmblemOfDread.cs:126-136 | Content/Items/Accessories/EyeOfSingularity.cs:82-92 | Content/Items/Accessories/EyeOfSingularity.cs:234-244 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 11+ corresponding lines) Content/GameModes/BrutalMobs/Ambience/Cindercrag/Projectiles/CindercragVentProj.cs:74 — Content/GameModes/BrutalMobs/Ambience/Cindercrag/Projectiles/CindercragVentProj.cs:74-84 | Content/GameModes/BrutalMobs/Ambience/Prismglade/Projectiles/PrismgladeJudgmentProj.cs:59-69 | Content/GameModes/BrutalMobs/Ambience/Rotmire/Projectiles/RotmireVentProj.cs:50-60 | Content/GameModes/BrutalMobs/Ambience/Starfall/Projectiles/StarfallAfterburstProj.cs:44-54 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandGeyserProj.cs:43-53 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 11+ corresponding lines) Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiMirrorStand.cs:56 — Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiMirrorStand.cs:56-66 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiNueDive.cs:54-64 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiPaperEffigy.cs:53-63 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiSelfCut.cs:65-75 | Content/Scenarios/Shenyo/Dolls/ScapegoatDollWalker.cs:48-58 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 11+ corresponding lines) Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteFireSpot.cs:54 — Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteFireSpot.cs:54-64 | Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs:51-64 | Content/Items/Magic/Elysiums/ElysiumThunder.cs:32-44 | Content/Items/Magic/Elysiums/Serpents/SnakeConversionWave.cs:41-53 | Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraVineLattice.cs:40-50 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 11+ corresponding lines) Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclManFlyFlaskProj.cs:45 — Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclManFlyFlaskProj.cs:45-55 | Content/Items/Magic/MelodyTheSand.cs:131-143 | Content/Items/Magic/Pandemoniums/PandemoniumFireball.cs:21-33 | Content/Items/Magic/UnderTheSand.cs:156-168 | Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraThornBall.cs:19-30 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (9 lines × 4) · ×13
  • Duplicated block (9 lines × 4) Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdMarksmanOmen.cs:182 — Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdMarksmanOmen.cs:182-190 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkClawCrossProj.cs:181-189 | Content/GameModes/BrutalMobs/Sky/Projectiles/SkyGaleDiveOmen.cs:122-130 | Content/GameModes/BrutalMobs/Temple/Projectiles/TempleDiveOmen.cs:136-144 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdMarksmanOmen.cs:182` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 4) Content/GameModes/GodSmith/Weapons/Broadswords/GsBladetongue.cs:165 — Content/GameModes/GodSmith/Weapons/Broadswords/GsBladetongue.cs:165-173 | Content/GameModes/GodSmith/Weapons/Broadswords/GsFieryGreatsword.cs:237-245 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsOdditiesFlurryHeldBase.cs:96-104 | Content/Items/Melee/Cloudwalking.cs:104-112 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/Broadswords/GsBladetongue.cs:165` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 4) Content/Items/Ranged/NeutronBows/NeutronBow.cs:257 — Content/Items/Ranged/NeutronBows/NeutronBow.cs:257-265 | Content/Items/Ranged/NeutronBows/NeutronBow.cs:278-286 | Content/Items/Ranged/Thornstrings/ThornstringHeld.cs:175-183 | Content/Items/Ranged/Undertows/UndertowHeld.cs:181-189 — before extracting anything, compare `Content/Items/Ranged/NeutronBows/NeutronBow.cs` and `Content/Items/Ranged/Thornstrings/ThornstringHeld.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 98 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 4) Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerMotionFX.cs:254 — Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerMotionFX.cs:254-262 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Rendering/EowMotionFX.cs:36-44 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordScreenFX.cs:69-77 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Rendering/WofMotionFX.cs:154-162 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerMotionFX.cs:254` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 4) Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2EscapeTunnel.cs:390 — Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2EscapeTunnel.cs:390-398 | Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2Palette.cs:68-76 | Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Palette.cs:75-83 | Content/Scenarios/Dungeonworld/Gen/Layers/L7/L7Style.cs:75-83 — before extracting anything, compare `Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2Palette.cs` and `Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Palette.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 4) Content/Items/Melee/DestroyersBlade.cs:306 — Content/Items/Melee/DestroyersBlade.cs:306-314 | Content/Items/Melee/DragonsScaleGreatsword.cs:319-327 | Content/Items/Melee/RebelBlade.cs:356-364 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:329-337 — before extracting anything, compare `Content/Items/Melee/DestroyersBlade.cs` and `Content/Items/Melee/DragonsScaleGreatsword.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 419 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DestroyersBlade.cs:306` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 4) Content/Scenarios/Kiame/Backgrounds/KiameSky.cs:109 — Content/Scenarios/Kiame/Backgrounds/KiameSky.cs:109-117 | Content/Scenarios/Kiame/Overlay/OniRainWorldSky.cs:111-119 | Content/Wraiths/Abilities/CrimsonBrides/BrideHallSky.cs:155-163 | Content/Wraiths/Abilities/GhostRains/GhostRainAmbience.cs:155-163 — before extracting anything, compare `Content/Scenarios/Kiame/Backgrounds/KiameSky.cs` and `Content/Scenarios/Kiame/Overlay/OniRainWorldSky.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Kiame/Backgrounds/KiameSky.cs:109` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Wraiths/Abilities/GhostRains/GhostRainAmbience.cs:166` calls `SetValue` and `Content/Wraiths/Abilities/CrimsonBrides/BrideHallSky.cs:166` 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 × 4) Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdBoltProj.cs:164 — Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdBoltProj.cs:164-172 | Content/GameModes/BrutalMobs/EvilBiome/Projectiles/ErosionCloudSeed.cs:85-93 | Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs:82-90 | Content/Items/Accessories/BrutalRelics/Twins/TwinPupilShots.cs:82-90 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdBoltProj.cs:164` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 4) Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:588 — Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:588-597 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT2.cs:298-307 | Content/Items/Melee/EnergySword.cs:465-473 | Content/Items/Melee/RebelBlade.cs:462-470 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:588` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (9 lines × 4) Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:112 — Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:112-120 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsScourgeoftheCorruptor.cs:99-107 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsVampireKnives.cs:183-191 | Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:148-156 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:112` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:385 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:385-394 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:318-326 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:301-310 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:349-358 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs` as WHOLE FILES: this scan already matched 43 separate duplicated blocks between them, totalling at least 492 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:385` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (9 lines × 4) Content/Items/Ranged/BarrenBow.cs:319 — Content/Items/Ranged/BarrenBow.cs:319-327 | Content/Items/Ranged/NeutronBows/NeutronBow.cs:366-374 | Content/Items/Ranged/Thornstrings/ThornstringHeld.cs:274-282 | Content/Items/Ranged/Undertows/UndertowHeld.cs:280-288 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (9 lines × 4) Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2Scatter.cs:105 — Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2Scatter.cs:105-113 | Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Scatter.cs:212-220 | Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Scatter.cs:171-179 | Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Scatter.cs:150-158 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (6 lines × 7) · ×13
  • Duplicated block (6 lines × 7) Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs:127 — Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs:127-132 | Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:143-148 | Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgStabGlintOmen.cs:131-136 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmStrafeLaneProj.cs:115-120 | Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyRavenSwoopOmen.cs:145-150 | Content/GameModes/BrutalMobs/NightPack/Projectiles/NightDiveOmen.cs:143-148 | Content/GameModes/BrutalMobs/Sky/Projectiles/SkyGaleDiveOmen.cs:125-130 — before extracting anything, compare `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs` and `Content/GameModes/BrutalMobs/Sky/Projectiles/SkyGaleDiveOmen.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 7) Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamSky.cs:83 — Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamSky.cs:83-88 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspaceSky.cs:82-87 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordEclipseSky.cs:174-179 | Content/Scenarios/Hadalworld/Ambience/HadalSky.cs:119-124 | Content/Scenarios/Himayo/ToriiShrines/ToriiDusk.cs:195-200 | Content/Scenarios/Kiyume/Backgrounds/KiyumeSky.cs:96-101 | Content/Scenarios/OldNet/Backgrounds/OldNetSky.cs:109-114 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamSky.cs` and `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspaceSky.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Scenarios/Kiyume/Backgrounds/KiyumeSky.cs:93` calls `Clamp` and `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamSky.cs:81` 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 (6 lines × 7) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:178 — Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:178-183 | Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:199-204 | Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs:268-273 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs:168-173 | Content/Scenarios/Kiame/KiameWakeResetRender.cs:164-169 | Content/Scenarios/Kiame/Overlay/OniRainDescentRender.cs:140-145 | Content/Scenarios/Kiame/Overlay/OniRainWorldRender.cs:201-206 — before extracting anything, compare `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs` and `Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:178` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 7) Content/Scenarios/OldNet/NPCs/OldNetLurkerICE.cs:252 — Content/Scenarios/OldNet/NPCs/OldNetLurkerICE.cs:252-257 | Content/Scenarios/OldNet/NPCs/OldNetPatrolICE.cs:239-244 | Content/Scenarios/OldNet/NPCs/OldNetSweepEye.cs:186-191 | Content/Scenarios/OldNet/NPCs/OldNetTaggerICE.cs:239-244 | Content/Scenarios/OldNet/NPCs/OldNetTracerICE.cs:393-398 | Content/Scenarios/OldNet/NPCs/OldNetTurretICE.cs:135-140 | Content/Scenarios/OldNet/NPCs/OldNetWardenICE.cs:881-886 — 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 7 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/OldNet/NPCs/OldNetLurkerICE.cs:252` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 7) Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmIceShardProj.cs:78 — Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmIceShardProj.cs:78-83 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesIceShardProj.cs:79-84 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandPelletProj.cs:86-91 | Content/Items/BloomArsenal.cs:203-208 | Content/Items/Ranged/DuneStalker.cs:509-514 | Content/Items/Ranged/Thornstrings/ThornstringArrow.cs:105-110 | Content/NPCs/BloomsandSerpents/Projectiles/BssNeedleProj.cs:68-73 — before extracting anything, compare `Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmIceShardProj.cs` and `Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesIceShardProj.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmIceShardProj.cs:78` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `lightColor` to `ref Color` in one and `Color` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (6 lines × 7) Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:263 — Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:263-268 | Content/Items/Accessories/BrutalRelics/QueenBee/SwarmVortexProj.cs:363-368 | Content/Items/Accessories/BrutalRelics/QueenBee/SwarmVortexProj.cs:414-419 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerStrikeTelegraph.cs:101-106 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronGeyserProj.cs:146-151 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronTelegraph.cs:115-120 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Projectiles/QueenBeeTelegraphLine.cs:96-101 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerStrikeTelegraph.cs` and `Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronTelegraph.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 70 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronTelegraph.cs:114` calls `SetValue` and `Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:262` 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 (6 lines × 7) Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:274 — Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:274-279 | Content/Items/Accessories/BrutalRelics/QueenBee/SwarmVortexProj.cs:426-431 | Content/NPCs/BloomsandSerpents/Projectiles/BssDashOmen.cs:123-128 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerStrikeTelegraph.cs:112-117 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronGeyserProj.cs:158-163 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronTelegraph.cs:126-131 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Projectiles/QueenBeeTelegraphLine.cs:107-112 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:274` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 7) Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs:56 — Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs:56-62 | Content/LegendWeapon/KikasaLegend/TrialQuests/KikasaTrackerWidgetStyle.cs:56-62 | Content/LegendWeapon/OnikiriLegend/TrialQuests/OnikiriTrackerWidgetStyle.cs:45-50 | Content/LegendWeapon/SHPCLegend/TrialQuests/SHPCTrackerWidgetStyle.cs:59-65 | Content/Scenarios/Draedon/Quest/DraedonTrackerWidgetStyle.cs:58-64 | Content/Scenarios/OldDuke/Quest/SulfseaTrackerWidgetStyle.cs:56-62 | Content/Scenarios/SupCal/Quest/BrimstoneTrackerWidgetStyle.cs:58-63 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times.
  • Duplicated block (6 lines × 7) Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamHound.cs:960 — Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamHound.cs:960-966 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:275-280 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:1057-1062 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1288-1293 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1342-1347 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1428-1433 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1234-1239 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamHound.cs:960` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6 lines × 7) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:534 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:534-539 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:390-395 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:383-388 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:493-498 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:461-466 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:499-504 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:477-482 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:534` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:542` calls `AddShellAt` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:397` 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 (6 lines × 7) Content/GameModes/GodSmith/Weapons/Broadswords/GsAdamantiteSword.cs:159 — Content/GameModes/GodSmith/Weapons/Broadswords/GsAdamantiteSword.cs:159-165 | Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:527-532 | Content/GameModes/GodSmith/Weapons/Broadswords/GsCobaltSword.cs:120-128 | Content/GameModes/GodSmith/Weapons/Broadswords/GsHamBat.cs:81-87 | Content/GameModes/GodSmith/Weapons/Broadswords/GsKatana.cs:145-150 | Content/GameModes/GodSmith/Weapons/Broadswords/GsPearlwoodSword.cs:72-77 | Content/GameModes/GodSmith/Weapons/Broadswords/GsTitaniumSword.cs:81-86 — 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 7 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/GameModes/GodSmith/Weapons/Broadswords/GsTitaniumSword.cs:89` calls `OnHitTarget`, `PlaySound` and `Content/GameModes/GodSmith/Weapons/Broadswords/GsKatana.cs:151` 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 (6 lines × 7) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:229 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:229-235 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs:279-285 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:170-176 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs:131-137 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeHeatRay.cs:122-127 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeSkullBeamProj.cs:133-138 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofRetinaScanBeam.cs:193-198 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 161 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:178` calls `OnHitPlayer`, `AddBuff` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:237` 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 (6 lines × 7) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Core/BrainMotion.cs:26 — Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Core/BrainMotion.cs:26-31 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Core/EmpressMotion.cs:50-55 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Core/EocMotion.cs:34-39 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Core/CultistMotion.cs:100-105 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Core/TwinsMotion.cs:22-27 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Core/QueenBeeMotion.cs:25-30 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Core/QueenMotion.cs:60-65 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (5 lines × 7) · ×13
  • Duplicated block (5 lines × 7) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1001 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1001-1005 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:804-808 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:820-824 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1343-1347 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:766-770 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:792-796 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:798-802 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1001` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 7) Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:553 — Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:553-558 | Content/Industrials/Modifys/ChargingStationUI.cs:398-402 | Content/Narrative/Presentation/Skins/Brimstone/BrimstonePanelDraw.cs:47-51 | Content/Narrative/Presentation/Skins/StarStream/StarStreamPanelDraw.cs:44-48 | Content/Narrative/Presentation/Skins/StarStream/StarStreamPanelDraw.cs:194-198 | Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersUIs/OceanRaidersRenderer.cs:196-200 | Content/Scenarios/SupCal/End/EternalBlazingNow/Enchants/EnchantUI.cs:442-446 — there are 7 copies across 6 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 7 sites; resolving a subset leaves the remainder to drift apart. 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 (5 lines × 7) Content/Industrials/ElectricPowers/WeatherControllers/WeatherControllerTP.cs:141 — Content/Industrials/ElectricPowers/WeatherControllers/WeatherControllerTP.cs:141-146 | Content/NPCs/SeaShrimp/States/SeaShrimpIntroState.cs:114-118 | Content/Wraiths/Projectiles/GhostHandProj.cs:662-666 | Content/Wraiths/Projectiles/GhostHandProj.cs:669-673 | Content/Wraiths/Projectiles/GhostHandProj.cs:696-700 | Content/Wraiths/Projectiles/GhostHandProj.cs:717-721 | Content/Wraiths/Projectiles/GhostHandProj.cs:724-728 — there are 7 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 7 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/WeatherControllers/WeatherControllerTP.cs:141` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (5 lines × 7) Content/Items/Melee/DragonsScaleGreatsword.cs:680 — Content/Items/Melee/DragonsScaleGreatsword.cs:680-685 | Content/Items/Melee/DragonsScaleGreatsword.cs:890-895 | Content/Items/Melee/OniMacheteHands.cs:1353-1358 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:1042-1047 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCrimsonTiger.cs:806-810 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDemonicHell.cs:653-657 | Content/LegendWeapon/HalibutLegend/FishSkills/FishWyverntail.cs:403-407 — there are 7 copies across 6 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 7 sites; resolving a subset leaves the remainder to drift apart. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Melee/DragonsScaleGreatsword.cs:897` calls `SetValue` and `Content/Items/Melee/DragonsScaleGreatsword.cs:687` does not — after which the two agree again for 3 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 (5 lines × 7) Content/Items/Melee/OniMacheteHands.cs:1339 — Content/Items/Melee/OniMacheteHands.cs:1339-1343 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCrimsonTiger.cs:790-794 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCursed.cs:454-458 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDemonicHell.cs:637-641 | Content/LegendWeapon/HalibutLegend/FishSkills/FishFallenStarVFX.cs:203-207 | Content/LegendWeapon/HalibutLegend/FishSkills/FishPrincessVFX.cs:173-177 | Content/LegendWeapon/HalibutLegend/FishSkills/FishofCthulu.cs:952-956 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/OniMacheteHands.cs:1339` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 7) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1155 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1155-1159 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1280-1284 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1294-1298 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1348-1352 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1488-1492 | Content/LegendWeapon/KikasaLegend/KikasaVaults/KikasaLakeFX.cs:682-686 | Content/LegendWeapon/KikasaLegend/KikasaVaults/KikasaVaultRenderer.cs:123-127 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaVaults/KikasaVaultRenderer.cs:123` calls `SetValue` and `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1155` 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 (5 lines × 7) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkFX.cs:568 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkFX.cs:568-573 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkFX.cs:608-612 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:192-196 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:331-335 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetHourglass.cs:384-388 | Content/Scenarios/Kiame/KiameWakeResetRender.cs:300-304 | Content/Scenarios/Kiame/Overlay/OniRainWorldUmbrella.cs:450-454 — there are 7 copies across 5 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 7 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Kiame/Overlay/OniRainWorldUmbrella.cs:450` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:191` calls `SetValue` and `Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkFX.cs:566` does not — after which the two agree again for 4 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 (5 lines × 7) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:368 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:368-372 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:366-370 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:286-290 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:376-380 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:331-335 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:389-393 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:363-367 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs` as WHOLE FILES: this scan already matched 75 separate duplicated blocks between them, totalling at least 912 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:368` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 7) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:361 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:361-365 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:754-758 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:174-178 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:713-717 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:362-366 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraSeed.cs:111-115 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:414-418 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:361` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:369` calls `PlaySound` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:368` does not — after which the two agree again for 3 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 (5 lines × 7) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:501 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:501-506 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:936-940 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonOrb.cs:104-109 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeLaserBolt.cs:96-100 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeMortar.cs:226-230 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:465-469 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaShrimpWaterBolt.cs:83-87 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:501` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (5 lines × 7) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:1170 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:1170-1175 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1391-1396 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1458-1463 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1515-1520 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1647-1651 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1412-1416 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshLeech.cs:186-190 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:1170` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (5 lines × 7) Content/HackTimes/PvP/Protocols/ChannelScramble.cs:92 — Content/HackTimes/PvP/Protocols/ChannelScramble.cs:92-96 | Content/HackTimes/PvP/Protocols/ChannelScrambleChatHook.cs:212-216 | Content/HackTimes/PvP/Protocols/GaugePollution.cs:171-175 | Content/HackTimes/PvP/Protocols/MapBlackoutRenderer.cs:123-127 | Content/NPCs/TBUGs/TBUGRiftPortalProj.cs:386-390 | Content/PRTTypes/PRT_BanishGlitch.cs:107-111 | Content/PRTTypes/PRT_TBUGGlitch.cs:102-106 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/HackTimes/PvP/Protocols/MapBlackoutRenderer.cs:129` calls `Frac`, `Floor` and `Content/HackTimes/PvP/Protocols/ChannelScramble.cs:97` 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 (5 lines × 7) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:1145 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:1145-1149 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerRenderHelper.cs:17-21 | Content/NPCs/ScrapCommanders/ScrapVfx.cs:36-40 | Content/Scenarios/Dungeonworld/NPCs/Elites/DungeonworldEliteGate.cs:109-113 | Content/Scenarios/Kiyume/NPCs/KiyumeHound.cs:1093-1097 | Content/Scenarios/Kiyume/NPCs/KiyumeWhiteHound.cs:519-523 | Content/Scenarios/Kiyume/NPCs/KiyumeYokaiGate.cs:173-177 — before extracting anything, compare `Content/Scenarios/Dungeonworld/NPCs/Elites/DungeonworldEliteGate.cs` and `Content/Scenarios/Kiyume/NPCs/KiyumeYokaiGate.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Edited copy of a member (42 corresponding lines) · ×12
  • Edited copy of a member (42 corresponding lines) Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilateRenderer.cs:68 — Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilateRenderer.cs:68-109 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleRenderer.cs:266-321 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (42 corresponding lines) Content/NPCs/BloomsandSerpents/BssHead.cs:752 — Content/NPCs/BloomsandSerpents/BssHead.cs:752-793 | Content/NPCs/FestersandSerpents/FssHead.cs:742-788 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (42 corresponding lines) Content/Scenarios/OldNet/Gen/Zones/Z2/Z2Content.cs:155 — Content/Scenarios/OldNet/Gen/Zones/Z2/Z2Content.cs:155-196 | Content/Scenarios/OldNet/Gen/Zones/Z2/Z2Content.cs:239-281 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (42 corresponding lines) Content/Items/Melee/Flawless.cs:495 — Content/Items/Melee/Flawless.cs:495-542 | Content/Items/Melee/StormGoddessSpears/StormGoddessSpearHeld.cs:470-511 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (42 corresponding lines) Content/NPCs/BrutalNPCs/BrutalSkeletron/Core/ISkeletronState.cs:97 — Content/NPCs/BrutalNPCs/BrutalSkeletron/Core/ISkeletronState.cs:97-138 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Core/IPrimeState.cs:101-142 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (42 corresponding lines) Content/Items/Accessories/NinjaCthulsparkBoots.cs:362 — Content/Items/Accessories/NinjaCthulsparkBoots.cs:362-403 | Content/Items/Stones/Granites/GraniteWalkingBoots.cs:184-225 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (42 corresponding lines) Content/Industrials/Generator/Biomass/BiomassGenerator.cs:439 — Content/Industrials/Generator/Biomass/BiomassGenerator.cs:439-480 | Content/Industrials/Generator/Thermal/ThermalGenerator.cs:313-354 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (42 corresponding lines) Content/NPCs/BloomsandSerpents/States/BssHubState.cs:22 — Content/NPCs/BloomsandSerpents/States/BssHubState.cs:22-63 | Content/NPCs/FestersandSerpents/States/FssHubState.cs:22-68 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (42 corresponding lines) Content/Industrials/ElectricPowers/MiningMachines/MiningMachineUI.cs:215 — Content/Industrials/ElectricPowers/MiningMachines/MiningMachineUI.cs:215-269 | Content/Industrials/ElectricPowers/Turrets/TurretControlUI.cs:142-183 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (42 corresponding lines) Content/Scenarios/Himayo/ToriiShrines/ToriiShrine.cs:242 — Content/Scenarios/Himayo/ToriiShrines/ToriiShrine.cs:242-283 | Content/Scenarios/Kiame/Overlay/OniUmbrellaWorldSpawn.cs:236-281 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (42 corresponding lines) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/States/EmpressDeathState.cs:44 — Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/States/EmpressDeathState.cs:44-91 | Content/NPCs/BrutalNPCs/BrutalQueenBee/States/QBDeathState.cs:63-104 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (42 corresponding lines) Content/Items/Ranged/AvalancheM60.cs:102 — Content/Items/Ranged/AvalancheM60.cs:102-143 | Content/Items/Ranged/DarkFrostSolstice.cs:101-145 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 25+ corresponding lines) · ×12
  • Edited copies of one member (3 members, 25+ corresponding lines) Content/EntrustManager/Styles/DraedonManagerStyle.cs:350 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:350-374 | Content/EntrustManager/Styles/ForestManagerStyle.cs:359-383 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:348-372 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 25+ corresponding lines) Content/Scenarios/Himayo/ToriiShrines/ToriiShrinePromptRender.cs:38 — Content/Scenarios/Himayo/ToriiShrines/ToriiShrinePromptRender.cs:38-62 | Content/Scenarios/Kiame/Overlay/OniRainWorldUmbrella.cs:537-562 | Content/Scenarios/OldDuke/Campsites/OldDukeWanderingActor.cs:612-645 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 25+ corresponding lines) Content/EntrustManager/Styles/DraedonManagerStyle.cs:598 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:598-626 | Content/EntrustManager/Styles/ForestManagerStyle.cs:610-634 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:605-632 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 25+ corresponding lines) Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmPresentShellProj.cs:73 — Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmPresentShellProj.cs:73-97 | Content/NPCs/FestersandSerpents/Projectiles/FssMortarShard.cs:58-82 | Content/NPCs/FestersandSerpents/Projectiles/FssMortarShell.cs:119-145 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 25+ corresponding lines) Content/Items/Stones/Marbles/MarbleDisc.cs:128 — Content/Items/Stones/Marbles/MarbleDisc.cs:128-155 | Content/Items/Stones/Marbles/MarbleEffects.cs:168-192 | Content/Items/Stones/Marbles/MarblePebble.cs:95-120 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 25+ corresponding lines) Content/GameModes/BrutalMobs/EliteMove/Projectiles/EMScatterBoltProj.cs:82 — Content/GameModes/BrutalMobs/EliteMove/Projectiles/EMScatterBoltProj.cs:82-109 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtBroadsideBall.cs:89-113 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteStarSurge.cs:269-298 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 25+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemStoneShrapnel.cs:26 — Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemStoneShrapnel.cs:26-50 | Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemSunBolt.cs:30-57 | Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemSunMortar.cs:31-64 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 25+ corresponding lines) Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.Net.cs:395 — Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.Net.cs:395-420 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.Net.cs:422-446 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.Net.cs:448-477 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 25+ corresponding lines) Content/GameModes/BrutalMobs/Graveyard/GraveyardBrutalNPC.cs:308 — Content/GameModes/BrutalMobs/Graveyard/GraveyardBrutalNPC.cs:308-332 | Content/GameModes/BrutalMobs/Graveyard/GraveyardBrutalNPC.cs:462-486 | Content/GameModes/BrutalMobs/Stoneborn/StonebornBrutalNPC.cs:331-356 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 25+ corresponding lines) Content/Industrials/Generator/Biomass/BiomassStorageProvider.cs:144 — Content/Industrials/Generator/Biomass/BiomassStorageProvider.cs:144-168 | Content/Industrials/Generator/Thermal/ThermalStorageProvider.cs:160-184 | Content/Industrials/Generator/Thermal/ThermalStorageProvider.cs:400-424 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 25+ corresponding lines) Content/NPCs/BloomsandSerpents/BssBody.cs:226 — Content/NPCs/BloomsandSerpents/BssBody.cs:226-250 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/EowBodyAI.cs:221-245 | Content/NPCs/FestersandSerpents/FssBody.cs:272-296 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 25+ corresponding lines) Content/NPCs/BloomsandSerpents/BssHead.cs:244 — Content/NPCs/BloomsandSerpents/BssHead.cs:244-268 | Content/NPCs/FestersandSerpents/FssHead.cs:203-227 | Content/NPCs/ScrapCommanders/ScrapCommander.cs:177-201 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 10+ corresponding lines) · ×12
  • Edited copies of one member (4 members, 10+ corresponding lines) Content/Narrative/Presentation/Skins/Brimstone/BrimstonePanelDraw.cs:10 — Content/Narrative/Presentation/Skins/Brimstone/BrimstonePanelDraw.cs:10-20 | Content/Narrative/Presentation/Skins/Sea/SeaPanelState.cs:140-149 | Content/Narrative/Presentation/Skins/Sulfsea/SulfseaPanelDraw.cs:12-27 | Content/Narrative/Presentation/Skins/Tzeentch/TzeentchPanelDraw.cs:12-27 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 10+ corresponding lines) Content/Industrials/Generator/WindGriven/WGGMK2Wilderness.cs:125 — Content/Industrials/Generator/WindGriven/WGGMK2Wilderness.cs:125-134 | Content/Industrials/Generator/WindGriven/WGGWilderness.cs:122-131 | Content/Industrials/Generator/WindGriven/WindGrivenGenerator.cs:116-127 | Content/Industrials/Generator/WindGriven/WindGrivenGeneratorMk2.cs:121-132 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 10+ corresponding lines) Content/Items/Magic/WheezingWyrms/WyrmfirePRT.cs:91 — Content/Items/Magic/WheezingWyrms/WyrmfirePRT.cs:91-101 | Content/Items/Melee/CursedflameBloodfists/CursedflamePRT.cs:52-61 | Content/Items/Melee/DawnshatterAzures/DawnshatterPRT.cs:254-264 | Content/PRTTypes/PRT_LWarden.cs:169-182 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 10+ corresponding lines) Content/Items/Magic/MelodyTheSand.cs:103 — Content/Items/Magic/MelodyTheSand.cs:103-112 | Content/Items/Magic/SandVortexOfTheDecayedSea.cs:96-105 | Content/Items/Magic/TomeofFungalDecay.cs:106-117 | Content/Items/Magic/UnderTheSand.cs:121-130 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 10+ corresponding lines) Content/HackTimes/Protocols/CommandLinkCut.cs:132 — Content/HackTimes/Protocols/CommandLinkCut.cs:132-141 | Content/HackTimes/Protocols/DataBrand.cs:158-167 | Content/HackTimes/Protocols/ItemRecall.cs:61-70 | Content/HackTimes/Protocols/LimbSeizure.cs:167-176 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 10+ corresponding lines) Content/GameModes/GodSmith/Armors/Reset/GsBeetleArmors.cs:217 — Content/GameModes/GodSmith/Armors/Reset/GsBeetleArmors.cs:217-226 | Content/GameModes/GodSmith/Armors/Reset/GsCactusArmor.cs:70-79 | Content/GameModes/GodSmith/Armors/Reset/GsNecroArmor.cs:90-100 | Content/GameModes/GodSmith/Armors/Reset/GsTurtleArmor.cs:72-81 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 10+ corresponding lines) Content/Items/Accessories/BrutalRelics/WallOfFlesh/GluttonousLeechOrb.cs:159 — Content/Items/Accessories/BrutalRelics/WallOfFlesh/GluttonousLeechOrb.cs:159-168 | Content/Items/Melee/Heartcarver.cs:1073-1084 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBloodyManowar.cs:708-718 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Projectiles/EocBloodSpike.cs:54-63 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 10+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishVoodooRitual.cs:243 — Content/LegendWeapon/HalibutLegend/FishSkills/FishVoodooRitual.cs:243-253 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:715-725 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:1117-1126 | Content/Wraiths/Projectiles/LanternBoySlashProj.cs:159-170 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 10+ corresponding lines) Content/GameModes/BrutalMobs/Eclipse/EclMothronNPC.cs:443 — Content/GameModes/BrutalMobs/Eclipse/EclMothronNPC.cs:443-454 | Content/GameModes/BrutalMobs/PumpkinMoon/PumpkinMoonNPC.cs:389-399 | Content/GameModes/BrutalMobs/SlimeKin/SlimeKinNPC.cs:302-312 | Content/Scenarios/OldNet/NPCs/OldNetICEDirector.cs:131-140 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 10+ corresponding lines) Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomSporeBoltProj.cs:63 — Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomSporeBoltProj.cs:63-72 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerIceSpikeProj.cs:61-73 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerSeizeHandProj.cs:38-49 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerShadowHandProj.cs:32-43 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 10+ corresponding lines) Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryRoom.cs:461 — Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryRoom.cs:461-470 | Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolBossRoom.cs:240-250 | Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolBossRoom.cs:266-277 | Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolBossRoom.cs:279-289 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 10+ corresponding lines) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterStorageProvider.cs:162 — Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterStorageProvider.cs:162-171 | Content/Industrials/ElectricPowers/Crushers/CrusherStorageProvider.cs:228-237 | Content/Industrials/ElectricPowers/Incinerators/IncineratorStorageProvider.cs:247-257 | Content/Industrials/ElectricPowers/Recyclers/RecyclerStorageProvider.cs:206-215 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (15 lines × 3) · ×12
  • Duplicated block (15 lines × 3) Content/EntrustManager/Styles/DraedonManagerStyle.cs:350 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:350-364 | Content/EntrustManager/Styles/ForestManagerStyle.cs:359-373 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:348-362 — before extracting anything, compare `Content/EntrustManager/Styles/DraedonManagerStyle.cs` and `Content/EntrustManager/Styles/ForestManagerStyle.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 334 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/EntrustManager/Styles/DraedonManagerStyle.cs:350` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (15 lines × 3) Content/EntrustManager/Styles/DraedonManagerStyle.cs:385 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:385-399 | Content/EntrustManager/Styles/ForestManagerStyle.cs:394-408 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:383-397 — before extracting anything, compare `Content/EntrustManager/Styles/DraedonManagerStyle.cs` and `Content/EntrustManager/Styles/ForestManagerStyle.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 334 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/EntrustManager/Styles/DraedonManagerStyle.cs:385` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 3) Content/Items/Melee/DestroyersBladeEXs/DestroyerHeadMissile.cs:97 — Content/Items/Melee/DestroyersBladeEXs/DestroyerHeadMissile.cs:97-111 | Content/Items/Melee/DestroyersBladeEXs/DestroyerShadowBolt.cs:177-191 | Content/Items/Melee/DestroyersBladeEXs/DestroyersBeamEX.cs:74-88 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (15 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumCircle.cs:241 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumCircle.cs:241-255 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoProj.cs:161-175 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistThunderOrb.cs:175-189 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (15 lines × 3) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSlashRenderer.cs:314 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSlashRenderer.cs:314-328 | Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilateRenderer.cs:24-38 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleRenderer.cs:219-233 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (15 lines × 3) Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBellWave.cs:222 — Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBellWave.cs:222-236 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBellWave.cs:299-313 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiSandGarden.cs:232-246 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBellWave.cs` and `Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiSandGarden.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 97 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBellWave.cs:222` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 3) Content/GameModes/BrutalMobs/Legion/Projectiles/LegionInkGlob.cs:90 — Content/GameModes/BrutalMobs/Legion/Projectiles/LegionInkGlob.cs:90-104 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionScoutBolt.cs:89-103 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionVolleyArrow.cs:93-107 — before extracting anything, compare `Content/GameModes/BrutalMobs/Legion/Projectiles/LegionInkGlob.cs` and `Content/GameModes/BrutalMobs/Legion/Projectiles/LegionScoutBolt.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 74 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Legion/Projectiles/LegionInkGlob.cs:90` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (15 lines × 3) Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:177 — Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:177-191 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsScourgeoftheCorruptor.cs:159-173 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsVampireKnives.cs:243-257 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:177` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 3) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1227 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1227-1241 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1042-1056 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1233-1247 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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 (15 lines × 3) Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerMotionFX.cs:250 — Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerMotionFX.cs:250-264 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Rendering/EowMotionFX.cs:32-46 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordScreenFX.cs:65-79 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (15 lines × 3) Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2Palette.cs:68 — Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2Palette.cs:68-82 | Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Palette.cs:75-89 | Content/Scenarios/Dungeonworld/Gen/Layers/L7/L7Style.cs:75-89 — before extracting anything, compare `Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2Palette.cs` and `Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Palette.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2Palette.cs:68` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 3) Content/Scenarios/Kiyume/NPCs/FacelessOneYokai.cs:528 — Content/Scenarios/Kiyume/NPCs/FacelessOneYokai.cs:528-542 | Content/Scenarios/Kiyume/NPCs/LanternGuideYokai.cs:378-392 | Content/Scenarios/Kiyume/NPCs/RidgeWalkerYokai.cs:638-652 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Scenarios/Kiyume/NPCs/LanternGuideYokai.cs:376` calls `AdvanceState`, `ChangeState` and `Content/Scenarios/Kiyume/NPCs/RidgeWalkerYokai.cs:634` 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.
D4 · Code Duplication · Duplicated block (8 lines × 5) · ×12
  • Duplicated block (8 lines × 5) Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserMarkLine.cs:221 — Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserMarkLine.cs:221-228 | Content/GameModes/BrutalMobs/NightPack/Projectiles/NightDiveOmen.cs:157-164 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkChargeOmen.cs:169-176 | Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornDiveLane.cs:140-147 | Content/GameModes/BrutalMobs/Temple/Projectiles/TempleDiveOmen.cs:153-160 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserMarkLine.cs:221` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (8 lines × 5) Content/GameModes/GodSmith/Weapons/Broadswords/GsChlorophyteClaymore.cs:210 — Content/GameModes/GodSmith/Weapons/Broadswords/GsChlorophyteClaymore.cs:210-217 | Content/GameModes/GodSmith/Weapons/Broadswords/GsChlorophyteSaber.cs:146-153 | Content/GameModes/GodSmith/Weapons/Broadswords/GsLightsBane.cs:95-102 | Content/GameModes/GodSmith/Weapons/Broadswords/GsSeedler.cs:237-244 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT2.cs:416-423 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/Broadswords/GsChlorophyteClaymore.cs:210` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 5) Content/Items/Magic/CommandersStaff.cs:33 — Content/Items/Magic/CommandersStaff.cs:33-40 | Content/Items/Magic/FocusingGrimoire.cs:36-43 | Content/Items/Ranged/Dicoria.cs:36-43 | Content/Items/Ranged/HyperionBarrage.cs:38-45 | Content/Items/Ranged/RaiderGun.cs:33-40 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/CommandersStaff.cs:33` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Magic/FocusingGrimoire.cs:45` calls `AltFunctionUse` and `Content/Items/Magic/CommandersStaff.cs:42` does not — after which the two agree again for 4 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 × 5) Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:317 — Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:317-324 | Content/Items/Melee/Abyssrends/AbyssrendUndercurrent.cs:138-145 | Content/Items/Ranged/Undertows/UndertowSpine.cs:176-183 | Content/Items/Summon/Deepclaws/DeepclawLobster.cs:470-477 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpWaterBolt.cs:106-113 — before extracting anything, compare `Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs` and `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpWaterBolt.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 116 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:317` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Melee/Abyssrends/AbyssrendUndercurrent.cs:134` calls `PreDraw` and `Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:313` 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 × 5) Content/GameModes/UI/GameModeRenderer.cs:694 — Content/GameModes/UI/GameModeRenderer.cs:694-701 | Content/LegendWeapon/KikasaLegend/KikasaVaults/KikasaVaultRenderer.cs:43-50 | Content/LegendWeapon/KikasaLegend/UI/KikasaHud.cs:526-533 | Content/LegendWeapon/KikasaLegend/UI/Panorama/KikasaPanoramaRenderer.cs:51-58 | Content/LegendWeapon/KikasaLegend/UI/Panorama/KikasaPanoramaRenderer.cs:281-288 — there are 5 copies across 4 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/UI/KikasaHud.cs:526` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/UI/KikasaHud.cs:525` calls `SetValue` and `Content/LegendWeapon/KikasaLegend/KikasaVaults/KikasaVaultRenderer.cs:43` 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 × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:528 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:528-535 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:629-637 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:483-490 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:462-470 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:504-512 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs` as WHOLE FILES: this scan already matched 55 separate duplicated blocks between them, totalling at least 611 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:528` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 5) Content/LegendWeapon/KikasaLegend/TrialQuests/KikasaTrackerWidgetStyle.cs:105 — Content/LegendWeapon/KikasaLegend/TrialQuests/KikasaTrackerWidgetStyle.cs:105-112 | Content/LegendWeapon/OnikiriLegend/TrialQuests/OnikiriTrackerWidgetStyle.cs:91-98 | Content/LegendWeapon/SHPCLegend/TrialQuests/SHPCTrackerWidgetStyle.cs:121-129 | Content/Scenarios/Draedon/Quest/DraedonTrackerWidgetStyle.cs:152-160 | Content/Scenarios/SupCal/Quest/BrimstoneTrackerWidgetStyle.cs:145-152 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/TrialQuests/KikasaTrackerWidgetStyle.cs` and `Content/LegendWeapon/OnikiriLegend/TrialQuests/OnikiriTrackerWidgetStyle.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/TrialQuests/KikasaTrackerWidgetStyle.cs:105` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (8 lines × 5) Content/NPCs/ScrapCommanders/ScrapCommander.cs:126 — Content/NPCs/ScrapCommanders/ScrapCommander.cs:126-133 | Content/NPCs/SeaShrimp/SeaShrimpBoss.cs:53-60 | Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:247-254 | Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:220-227 | Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:266-273 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/ScrapCommanders/ScrapCommander.cs:126` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 5) Content/Narrative/Presentation/Skins/Brimstone/BrimstonePopupSkin.cs:70 — Content/Narrative/Presentation/Skins/Brimstone/BrimstonePopupSkin.cs:70-84 | Content/Narrative/Presentation/Skins/Draedon/DraedonPopupSkin.cs:35-42 | Content/Narrative/Presentation/Skins/Kikasa/KikasaPopupSkin.cs:47-54 | Content/Narrative/Presentation/Skins/Onikiri/OnikiriPopupSkin.cs:46-53 | Content/Narrative/Presentation/Skins/Sea/SeaPopupSkin.cs:36-43 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Narrative/Presentation/Skins/Brimstone/BrimstonePopupSkin.cs:70` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 5) Content/Scenarios/Kiyume/NPCs/FacelessOneYokai.cs:371 — Content/Scenarios/Kiyume/NPCs/FacelessOneYokai.cs:371-378 | Content/Scenarios/Kiyume/NPCs/FuneralCortegeYokai.cs:554-561 | Content/Scenarios/Kiyume/NPCs/FuneralCortegeYokai.cs:876-883 | Content/Scenarios/Kiyume/NPCs/LanternGuideYokai.cs:442-449 | Content/Scenarios/Kiyume/NPCs/RidgeWalkerYokai.cs:510-517 — there are 5 copies across 4 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Kiyume/NPCs/FacelessOneYokai.cs:371` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 5) Content/NPCs/BloomsandSerpents/BssVfx.cs:96 — Content/NPCs/BloomsandSerpents/BssVfx.cs:96-103 | Content/NPCs/FestersandSerpents/FssVfx.cs:139-146 | Content/NPCs/ScrapCommanders/Core/IScrapState.cs:137-144 | Content/NPCs/ScrapCommanders/ScrapVfx.cs:75-82 | Content/NPCs/SeaShrimp/Core/ISeaShrimpState.cs:133-140 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/FestersandSerpents/FssVfx.cs:134` calls `PlaySound` and `Content/NPCs/BloomsandSerpents/BssVfx.cs:91` 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 × 5) Content/Scenarios/Dungeonworld/Gen/Layers/L1/L1Content.cs:239 — Content/Scenarios/Dungeonworld/Gen/Layers/L1/L1Content.cs:239-246 | Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2Content.cs:340-347 | Content/Scenarios/Dungeonworld/Gen/Layers/L4/L4Content.cs:576-583 | Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Content.cs:630-637 | Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Content.cs:477-484 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Content.cs:473` calls `HitsShaft` and `Content/Scenarios/Dungeonworld/Gen/Layers/L1/L1Content.cs:237` 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.
D4 · Code Duplication · Edited copy of a member (53 corresponding lines) · ×11
  • Edited copy of a member (53 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:296 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:296-348 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterPool.cs:66-118 — These two members are one piece of code written twice and then edited apart: 53 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (53 corresponding lines) Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:258 — Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:258-312 | Content/Items/Modifys/RBloodButcherer.cs:292-344 — These two members are one piece of code written twice and then edited apart: 53 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (53 corresponding lines) Content/Items/Melee/Arbiters/Arbiter.cs:437 — Content/Items/Melee/Arbiters/Arbiter.cs:437-491 | Content/Items/Melee/Cloudwalking.cs:381-433 — These two members are one piece of code written twice and then edited apart: 53 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (53 corresponding lines) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismDashPrepareState.cs:37 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismDashPrepareState.cs:37-92 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismPhase2DashPrepareState.cs:36-88 — These two members are one piece of code written twice and then edited apart: 53 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (53 corresponding lines) Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:830 — Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:830-882 | Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:967-1023 — These two members are one piece of code written twice and then edited apart: 53 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (53 corresponding lines) Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSim.cs:171 — Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSim.cs:171-223 | Content/Scenarios/Kiyume/Fog/KiyumeFogSim.cs:259-312 — These two members are one piece of code written twice and then edited apart: 53 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (53 corresponding lines) Content/GameModes/BrutalMobs/Martians/Projectiles/MrtWrenchProj.cs:72 — Content/GameModes/BrutalMobs/Martians/Projectiles/MrtWrenchProj.cs:72-124 | Content/GameModes/BrutalMobs/NightPack/Projectiles/NightBoneProj.cs:73-125 — These two members are one piece of code written twice and then edited apart: 53 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (53 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:184 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:184-236 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:233-294 — These two members are one piece of code written twice and then edited apart: 53 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (53 corresponding lines) Content/GameModes/GodSmith/Weapons/Broadswords/GsKatana.cs:79 — Content/GameModes/GodSmith/Weapons/Broadswords/GsKatana.cs:79-132 | Content/GameModes/GodSmith/Weapons/Broadswords/GsMuramasa.cs:98-150 — These two members are one piece of code written twice and then edited apart: 53 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (53 corresponding lines) Content/NPCs/BloomsandSerpents/BssBody.cs:97 — Content/NPCs/BloomsandSerpents/BssBody.cs:97-150 | Content/NPCs/FestersandSerpents/FssBody.cs:95-147 — These two members are one piece of code written twice and then edited apart: 53 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (53 corresponding lines) Content/NPCs/BrutalNPCs/BrutalMoonLord/States/MLordDeathState.cs:87 — Content/NPCs/BrutalNPCs/BrutalMoonLord/States/MLordDeathState.cs:87-139 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/PrimeDeathState.cs:124-184 — These two members are one piece of code written twice and then edited apart: 53 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (32 corresponding lines) · ×11
  • Edited copy of a member (32 corresponding lines) Content/Wraiths/Projectiles/GhostHandProj.cs:648 — Content/Wraiths/Projectiles/GhostHandProj.cs:648-686 | Content/Wraiths/Projectiles/GhostHandProj.cs:709-740 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (32 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishTropicalBarracudaVFX.cs:66 — Content/LegendWeapon/HalibutLegend/FishSkills/FishTropicalBarracudaVFX.cs:66-100 | Content/LegendWeapon/HalibutLegend/FishSkills/FishTunabeardVFX.cs:37-68 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (32 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeLaserBolt.cs:110 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeLaserBolt.cs:110-141 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeMortar.cs:255-300 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (32 corresponding lines) Content/Structures/DatIO/JunkmanBase.cs:19 — Content/Structures/DatIO/JunkmanBase.cs:19-51 | Content/Structures/DatIO/RocketHut.cs:17-48 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (32 corresponding lines) Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs:163 — Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs:163-201 | Content/LegendWeapon/SHPCLegend/UI/DomainWheel/SHPCDomainWheelUI.cs:159-190 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (32 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishDoubleCodVFX.cs:212 — Content/LegendWeapon/HalibutLegend/FishSkills/FishDoubleCodVFX.cs:212-243 | Content/LegendWeapon/HalibutLegend/FishSkills/FishPengVFX.cs:378-413 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (32 corresponding lines) Content/NPCs/BrutalNPCs/BrutalGolem/Rendering/GolemScreenEffectRender.cs:65 — Content/NPCs/BrutalNPCs/BrutalGolem/Rendering/GolemScreenEffectRender.cs:65-96 | Content/Renders/PrimeScreenEffectRender.cs:87-119 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (32 corresponding lines) Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiInkThread.cs:483 — Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiInkThread.cs:483-514 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiSenjuArm.cs:245-276 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (32 corresponding lines) Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:272 — Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:272-303 | Content/Industrials/Generator/Thermal/ThermalGeneratorUI.cs:228-262 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (32 corresponding lines) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerPatrolState.cs:19 — Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerPatrolState.cs:19-55 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowWeaveState.cs:19-50 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (32 corresponding lines) Content/NPCs/BrutalNPCs/BrutalSkeletron/States/SkeletronApplauseState.cs:57 — Content/NPCs/BrutalNPCs/BrutalSkeletron/States/SkeletronApplauseState.cs:57-91 | Content/NPCs/BrutalNPCs/BrutalSkeletron/States/SkeletronPalmSnatchState.cs:106-137 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (40 corresponding lines) · ×11
  • Edited copy of a member (40 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangProj.cs:200 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangProj.cs:200-239 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailHead.cs:207-253 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (40 corresponding lines) Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs:222 — Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs:222-264 | Content/LegendWeapon/SHPCLegend/UI/DomainWheel/SHPCDomainWheelUI.cs:209-248 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (40 corresponding lines) Content/HackTimes/HackStatusDisplay.cs:242 — Content/HackTimes/HackStatusDisplay.cs:242-288 | Content/HackTimes/HackStatusDisplay.cs:291-330 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (40 corresponding lines) Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiMirrorStand.cs:214 — Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiMirrorStand.cs:214-264 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiSenjuArm.cs:200-239 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (40 corresponding lines) Content/Scenarios/Dungeonworld/Gen/Infill/AnnexPass.cs:32 — Content/Scenarios/Dungeonworld/Gen/Infill/AnnexPass.cs:32-71 | Content/Scenarios/Dungeonworld/Gen/Infill/IntersticePass.cs:37-76 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (40 corresponding lines) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/PrimeCannonAI.cs:45 — Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/PrimeCannonAI.cs:45-97 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/PrimeLaserAI.cs:35-74 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (40 corresponding lines) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/Arms/PrimeSawStates.cs:19 — Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/Arms/PrimeSawStates.cs:19-58 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/Arms/PrimeViceStates.cs:20-64 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (40 corresponding lines) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/Arms/PrimeSawStates.cs:80 — Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/Arms/PrimeSawStates.cs:80-119 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/Arms/PrimeViceStates.cs:80-119 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (40 corresponding lines) Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT1.cs:226 — Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT1.cs:226-266 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT3.cs:133-172 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (40 corresponding lines) Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs:263 — Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs:263-305 | Content/Industrials/ElectricPowers/Lumberjacks/WGGLumberjack.cs:283-322 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (40 corresponding lines) Content/Scenarios/Kiyume/NPCs/FuneralCortegeYokai.cs:76 — Content/Scenarios/Kiyume/NPCs/FuneralCortegeYokai.cs:76-116 | Content/Scenarios/Kiyume/NPCs/LanternGuideYokai.cs:99-138 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 19+ corresponding lines) · ×11
  • Edited copies of one member (3 members, 19+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalDukeFishron/Rendering/FishronMotionFX.cs:80 — Content/NPCs/BrutalNPCs/BrutalDukeFishron/Rendering/FishronMotionFX.cs:80-98 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Core/TwinsMotion.cs:80-103 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Core/QueenBeeMotion.cs:75-93 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 19+ corresponding lines) Content/Scenarios/Dungeonworld/NPCs/GaolDormantSkull.cs:179 — Content/Scenarios/Dungeonworld/NPCs/GaolDormantSkull.cs:179-197 | Content/Scenarios/Dungeonworld/NPCs/OverseerDormantRig.cs:249-272 | Content/Scenarios/Dungeonworld/NPCs/UndrownedThrone.cs:251-274 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 19+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangProj.cs:148 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangProj.cs:148-166 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailHead.cs:149-167 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoProj.cs:178-196 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 19+ corresponding lines) Content/GameModes/BrutalMobs/Temple/TempleBrutalNPC.cs:362 — Content/GameModes/BrutalMobs/Temple/TempleBrutalNPC.cs:362-382 | Content/GameModes/BrutalMobs/Temple/TempleBrutalNPC.cs:405-423 | Content/GameModes/BrutalMobs/Temple/TempleBrutalNPC.cs:635-654 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 19+ corresponding lines) Content/Items/Ranged/Dicoria.cs:25 — Content/Items/Ranged/Dicoria.cs:25-43 | Content/Items/Ranged/HyperionBarrage.cs:27-45 | Content/Items/Ranged/RaiderGun.cs:22-40 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 19+ corresponding lines) Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT2.cs:224 — Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT2.cs:224-247 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsSolarEruption.cs:210-228 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsVampireKnives.cs:243-264 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 19+ corresponding lines) Content/Items/Magic/AriaofTheCosmoses/AriaofTheCosmos.cs:44 — Content/Items/Magic/AriaofTheCosmoses/AriaofTheCosmos.cs:44-63 | Content/Items/Magic/Elysiums/Elysium.cs:72-90 | Content/Items/Magic/Pandemoniums/Pandemonium.cs:40-58 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 19+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishEaterofPlankton.cs:20 — Content/LegendWeapon/HalibutLegend/FishSkills/FishEaterofPlankton.cs:20-49 | Content/LegendWeapon/HalibutLegend/FishSkills/FishJewel.cs:87-105 | Content/LegendWeapon/HalibutLegend/FishSkills/FishofCthulu.cs:28-65 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 19+ corresponding lines) Content/QuestLogs/QLNodes/MilestoneQuests.cs:80 — Content/QuestLogs/QLNodes/MilestoneQuests.cs:80-99 | Content/QuestLogs/QLNodes/MilestoneQuests.cs:118-137 | Content/QuestLogs/QLNodes/MilestoneQuests.cs:150-168 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 19+ corresponding lines) Content/QuestLogs/QLNodes/IndustrialQuests.cs:170 — Content/QuestLogs/QLNodes/IndustrialQuests.cs:170-188 | Content/QuestLogs/QLNodes/IndustrialQuests.cs:199-217 | Content/QuestLogs/QLNodes/IndustrialQuests.cs:408-426 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 19+ corresponding lines) Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:128 — Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:128-151 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsScourgeoftheCorruptor.cs:115-133 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsVampireKnives.cs:199-217 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 18+ corresponding lines) · ×11
  • Edited copies of one member (3 members, 18+ corresponding lines) Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:624 — Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:624-645 | Content/GameModes/GodSmith/Weapons/Shortswords/GsThrustHeldBase.cs:648-667 | Content/GameModes/GodSmith/Weapons/Spears/GsSwordfish.cs:124-141 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 18+ corresponding lines) Content/NPCs/ScrapCommanders/ScrapLegionProbe.cs:140 — Content/NPCs/ScrapCommanders/ScrapLegionProbe.cs:140-159 | Content/NPCs/SeaShrimp/SeaShrimpBoss.cs:377-399 | Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:1702-1719 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 18+ corresponding lines) Content/Scenarios/Dungeonworld/Ambience/AmbientEmitters.cs:72 — Content/Scenarios/Dungeonworld/Ambience/AmbientEmitters.cs:72-89 | Content/Scenarios/Dungeonworld/Fog/FogSuppression.cs:77-95 | Content/Scenarios/Kiyume/Fog/KiyumeFogSuppression.cs:84-103 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 18+ corresponding lines) Content/Scenarios/Dungeonworld/NPCs/GaolAnchorWeapon.cs:150 — Content/Scenarios/Dungeonworld/NPCs/GaolAnchorWeapon.cs:150-169 | Content/Scenarios/Dungeonworld/NPCs/OverseerSlagGlob.cs:88-105 | Content/Scenarios/Dungeonworld/NPCs/UndrownedTideWave.cs:93-110 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 18+ corresponding lines) Content/Industrials/ElectricPowers/Apiaries/ApiaryTP.cs:199 — Content/Industrials/ElectricPowers/Apiaries/ApiaryTP.cs:199-217 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherTP.cs:226-244 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerTP.cs:224-241 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 18+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:1048 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:1048-1069 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:1061-1078 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1634-1659 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 18+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishTunabeardVFX.cs:292 — Content/LegendWeapon/HalibutLegend/FishSkills/FishTunabeardVFX.cs:292-309 | Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniKamuiFlowRenderer.cs:195-213 | Content/Wraiths/VFX/ScapeArmRenderer.cs:287-325 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 18+ corresponding lines) Content/Items/Melee/Abyssrends/Abyssrend.cs:22 — Content/Items/Melee/Abyssrends/Abyssrend.cs:22-39 | Content/Items/Melee/DivineSourceBlades/DivineSourceBlade.cs:22-39 | Content/Items/Melee/Shatterfangs/Shatterfang.cs:19-36 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 18+ corresponding lines) Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:264 — Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:264-281 | Content/Industrials/ElectricPowers/Recyclers/RecyclerUI.cs:264-281 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterUI.cs:275-295 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 18+ corresponding lines) Content/Items/Melee/CursedflameBloodfists/CursedflameBloodfist.cs:19 — Content/Items/Melee/CursedflameBloodfists/CursedflameBloodfist.cs:19-40 | Content/Items/Melee/NeutronScythe.cs:35-52 | Content/Items/Melee/TideReapers/TideReaper.cs:32-49 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 18+ corresponding lines) Content/Items/Magic/UnderTheSand.cs:19 — Content/Items/Magic/UnderTheSand.cs:19-37 | Content/Items/Ranged/DuneStalker.cs:24-42 | Content/Items/Ranged/LaserPistol.cs:15-32 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 7+ corresponding lines) · ×11
  • Edited copies of one member (4 members, 7+ corresponding lines) Content/Scenarios/Himayo/Gifts/HimayoCalamityEvilGift.cs:30 — Content/Scenarios/Himayo/Gifts/HimayoCalamityEvilGift.cs:30-37 | Content/Scenarios/Himayo/Gifts/HimayoEyeOfCthulhuGift.cs:30-37 | Content/Scenarios/Himayo/Gifts/HimayoFesterSerpentGift.cs:28-34 | Content/Scenarios/Himayo/Gifts/HimayoYharonGift.cs:28-34 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 7+ corresponding lines) Content/GameModes/GodSmith/Weapons/Bows/Projectiles/GsTideSpoutProj.cs:46 — Content/GameModes/GodSmith/Weapons/Bows/Projectiles/GsTideSpoutProj.cs:46-53 | Content/GameModes/GodSmith/Weapons/Bows/TsunamiScheme.cs:190-197 | Content/GameModes/GodSmith/Weapons/Flamethrowers/FlamethrowersShared.cs:284-292 | Content/GameModes/GodSmith/Weapons/Spears/GsTheRottedFork.cs:168-174 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 7+ corresponding lines) Content/GameModes/GodSmith/Weapons/Flails/GsChainGuillotines.cs:145 — Content/GameModes/GodSmith/Weapons/Flails/GsChainGuillotines.cs:145-151 | Content/GameModes/GodSmith/Weapons/Flails/GsDaoofPow.cs:138-144 | Content/GameModes/GodSmith/Weapons/Flails/GsGolemFist.cs:210-216 | Content/GameModes/GodSmith/Weapons/Flails/GsKOCannon.cs:168-174 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 7+ corresponding lines) Content/GameModes/BrutalMobs/Ambience/Frostveil/FrostveilPRT.cs:201 — Content/GameModes/BrutalMobs/Ambience/Frostveil/FrostveilPRT.cs:201-207 | Content/PRTTypes/PRT_GhostRainMist.cs:56-62 | Content/PRTTypes/PRT_KikasaDreamAsh.cs:65-71 | Content/Scenarios/Dungeonworld/NPCs/UndrownedAnchor.cs:269-275 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 7+ corresponding lines) Content/Items/Magic/WheezingWyrms/WyrmfirePRT.cs:222 — Content/Items/Magic/WheezingWyrms/WyrmfirePRT.cs:222-228 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/EocParticles.cs:47-53 | Content/PRTTypes/PRT_KikasaInkMist.cs:62-68 | Content/PRTTypes/PRT_SvcCloud.cs:61-67 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 7+ corresponding lines) Content/GameModes/BrutalMobs/EvilBiome/EvilBiomeMobsNPC.cs:343 — Content/GameModes/BrutalMobs/EvilBiome/EvilBiomeMobsNPC.cs:343-349 | Content/GameModes/BrutalMobs/Legion/LegionNPC.cs:674-680 | Content/GameModes/BrutalMobs/Sandveil/SandveilBrutalNPC.cs:426-433 | Content/GameModes/BrutalMobs/Temple/TempleBrutalNPC.cs:244-250 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 7+ corresponding lines) Content/Scenarios/Dungeonworld/Gen/Infill/InfillRooms.cs:90 — Content/Scenarios/Dungeonworld/Gen/Infill/InfillRooms.cs:90-96 | Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Preview.cs:144-150 | Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Preview.cs:133-141 | Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Preview.cs:105-111 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 7+ corresponding lines) Content/Scenarios/Dungeonworld/Gen/TileBrush.cs:101 — Content/Scenarios/Dungeonworld/Gen/TileBrush.cs:101-107 | Content/Scenarios/Kiame/Gen/KiameTileBrush.cs:76-82 | Content/Scenarios/Kiyume/Gen/KiyumeTileBrush.cs:91-97 | Content/Scenarios/OldNet/Gen/OldNetTileBrush.cs:70-76 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 7+ corresponding lines) Content/Industrials/ElectricPowers/HealingStations/HealStationTile.cs:59 — Content/Industrials/ElectricPowers/HealingStations/HealStationTile.cs:59-65 | Content/Industrials/ElectricPowers/ShieldGenerators/ShieldGeneratorTile.cs:59-65 | Content/Industrials/ElectricPowers/Turrets/CryoTurrets/CryoTurretTile.cs:59-65 | Content/Industrials/ElectricPowers/Turrets/LaserTurrets/LaserTurretTile.cs:59-65 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 7+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainFrenzyChaseState.cs:108 — Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainFrenzyChaseState.cs:108-114 | Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainMirrorMazeState.cs:202-208 | Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainMirrorStrikeState.cs:206-212 | Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainOrbitCageState.cs:192-199 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 7+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaTalismans/KikasaTalismanRegistry.cs:21 — Content/LegendWeapon/KikasaLegend/KikasaTalismans/KikasaTalismanRegistry.cs:21-27 | Content/MainMenus/Characters/MenuCharacter.cs:118-124 | Content/Scenarios/Himayo/Gifts/HimayoGiftCatalog.cs:106-112 | Content/Wraiths/Core/WraithRegistry.cs:17-23 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 12+ corresponding lines) · ×11
  • Edited copies of one member (5 members, 12+ corresponding lines) Content/GameModes/BrutalMobs/Ambience/Rotmire/Projectiles/RotmireVentProj.cs:281 — Content/GameModes/BrutalMobs/Ambience/Rotmire/Projectiles/RotmireVentProj.cs:281-296 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkRootSpikeProj.cs:226-239 | Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilSurgeColumnProj.cs:244-257 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandGeyserProj.cs:230-243 | Content/NPCs/BloomsandSerpents/Projectiles/BssDustDevilProj.cs:164-175 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 12+ corresponding lines) Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhStingerBolt.cs:42 — Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhStingerBolt.cs:42-53 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhTridentBolt.cs:41-52 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionScoutBolt.cs:45-60 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtFanShot.cs:43-59 | Content/GameModes/BrutalMobs/Sky/Projectiles/SkyFeatherBolt.cs:42-53 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 12+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:974 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:974-988 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1315-1329 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:765-779 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:922-934 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1188-1199 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 12+ corresponding lines) Content/GameModes/GodSmith/Prefixes/Ranged/GodSmithBallisticEndow.cs:84 — Content/GameModes/GodSmith/Prefixes/Ranged/GodSmithBallisticEndow.cs:84-96 | Content/Items/Melee/Abyssrends/AbyssrendUndercurrent.cs:37-50 | Content/Items/Melee/TideReapers/TideReaperWave.cs:27-40 | Content/LegendWeapon/HalibutLegend/FishSkills/FishAmanita.cs:345-356 | Content/LegendWeapon/HalibutLegend/FishSkills/FishJewel.cs:209-220 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 12+ corresponding lines) Content/GameModes/GodSmith/Weapons/Bows/Projectiles/GsTideSpoutProj.cs:23 — Content/GameModes/GodSmith/Weapons/Bows/Projectiles/GsTideSpoutProj.cs:23-34 | Content/GameModes/GodSmith/Weapons/Bows/Projectiles/GsVolleyBurstProj.cs:39-50 | Content/GameModes/GodSmith/Weapons/Bows/TsunamiScheme.cs:166-177 | Content/GameModes/GodSmith/Weapons/MagicCataclysm/Projectiles/GsCataclysmRiderBurstProj.cs:46-57 | Content/Items/Ranged/Starships/StarshipMicroGalaxy.cs:29-41 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 12+ corresponding lines) Content/Industrials/ElectricPowers/Turrets/FlameTurrets/FlameTurretFire.cs:19 — Content/Industrials/ElectricPowers/Turrets/FlameTurrets/FlameTurretFire.cs:19-32 | Content/Items/Accessories/Proverbs.cs:126-138 | Content/LegendWeapon/HalibutLegend/FishSkills/FishMud.cs:143-155 | Content/LegendWeapon/HalibutLegend/FishSkills/FishPeng.cs:108-119 | Content/LegendWeapon/HalibutLegend/FishSkills/FishWyverntail.cs:158-169 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 12+ corresponding lines) Content/Items/Accessories/EyeOfSingularity.cs:179 — Content/Items/Accessories/EyeOfSingularity.cs:179-191 | Content/Items/Magic/AriaofTheCosmoses/FlattenedAccretionDisk.cs:36-47 | Content/Items/Magic/AriaofTheCosmoses/GammaRayBeam.cs:44-56 | Content/Items/Ranged/NeutronBows/NeutronLaser.cs:11-25 | Content/Items/Ranged/Starships/StarshipMeteor.cs:25-39 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 12+ corresponding lines) Content/Items/Melee/CursedflameBloodfists/CursedflameBloodfistHeld.cs:87 — Content/Items/Melee/CursedflameBloodfists/CursedflameBloodfistHeld.cs:87-100 | Content/Items/Melee/CursedflameBloodfists/CursedflameFistProj.cs:41-53 | Content/Items/Modifys/RTerraBlades/TerraLightProj.cs:49-60 | Content/Items/Modifys/RTerraBlades/TerraSoulJudgmentProj.cs:41-52 | Content/Items/Modifys/RTerraBlades/TerraSoulSpinProj.cs:42-54 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 12+ corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Barrel/RapidBarrelModule.cs:87 — Content/LegendWeapon/SHPCLegend/Modules/Barrel/RapidBarrelModule.cs:87-101 | Content/LegendWeapon/SHPCLegend/Modules/Optic/SniperOpticModule.cs:75-86 | Content/LegendWeapon/SHPCLegend/Modules/SHPCModificationSystem.cs:45-56 | Content/LegendWeapon/SHPCLegend/Modules/Stock/BraceStockModule.cs:189-203 | Content/LegendWeapon/SHPCLegend/Modules/Stock/SteadyStockModule.cs:95-109 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 12+ corresponding lines) Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:375 — Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:375-386 | Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFistProj.cs:46-58 | Content/Items/Magic/Pandemoniums/PandemoniumScythe.cs:31-44 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDemonicHell.cs:322-333 | Content/LegendWeapon/SHPCLegend/Modules/Grip/CrystalGripModule.cs:65-77 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 12+ corresponding lines) Content/GameModes/GodSmith/Armors/Reset/GsArmorNpcMarks.cs:99 — Content/GameModes/GodSmith/Armors/Reset/GsArmorNpcMarks.cs:99-111 | Content/GameModes/GodSmith/Weapons/Bows/GsChargeBowBuffs.cs:35-47 | Content/Items/Accessories/BrutalRelics/Deerclops/WhiteblindDebuff.cs:54-66 | Content/Items/Accessories/BrutalRelics/Plantera/BloomSnareDebuff.cs:69-81 | Content/Items/Magic/Elysiums/Disciples/ElysiumGlobalNPC.cs:27-38 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (19–20 lines × 2) · ×11
  • Duplicated block (19–20 lines × 2) Content/EntrustManager/Styles/ForestManagerStyle.cs:68 — Content/EntrustManager/Styles/ForestManagerStyle.cs:68-86 | Content/QuestLogs/Styles/ForestQuestLogStyle.cs:44-63 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/EntrustManager/Styles/ForestManagerStyle.cs:68` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19–20 lines × 2) Content/Industrials/ElectricPowers/Spectrometers/Spectrometer.cs:134 — Content/Industrials/ElectricPowers/Spectrometers/Spectrometer.cs:134-152 | Content/Industrials/Modifys/ModifyDyeVat.cs:40-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Spectrometers/Spectrometer.cs:134` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (19–20 lines × 2) Content/Items/Melee/Arbiters/Arbiter.cs:24 — Content/Items/Melee/Arbiters/Arbiter.cs:24-43 | Content/Items/Melee/Cloudwalking.cs:25-43 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Arbiters/Arbiter.cs:24` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19–20 lines × 2) Content/Items/Melee/GeminisTribute.cs:495 — Content/Items/Melee/GeminisTribute.cs:495-514 | Content/Items/Melee/GeminisTribute.cs:726-744 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/GeminisTribute.cs:495` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19–20 lines × 2) Content/LegendWeapon/HalibutLegend/FishSkills/FishBunny.cs:23 — Content/LegendWeapon/HalibutLegend/FishSkills/FishBunny.cs:23-41 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCat.cs:23-42 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishBunny.cs:23` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (19–20 lines × 2) Content/LegendWeapon/HalibutLegend/FishSkills/FishPeng.cs:176 — Content/LegendWeapon/HalibutLegend/FishSkills/FishPeng.cs:176-194 | Content/LegendWeapon/HalibutLegend/FishSkills/FishPeng.cs:204-223 — 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. 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 (19–20 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:401 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:401-420 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:373-391 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs` as WHOLE FILES: this scan already matched 55 separate duplicated blocks between them, totalling at least 611 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:401` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19–20 lines × 2) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:317 — Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:317-335 | Content/LegendWeapon/SHPCLegend/UI/SHPCModPanel.cs:373-392 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:317` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (19–20 lines × 2) Content/NPCs/BrutalNPCs/BrutalDestroyer/Core/DestroyerStateContext.cs:14 — Content/NPCs/BrutalNPCs/BrutalDestroyer/Core/DestroyerStateContext.cs:14-32 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Core/EowStateContext.cs:15-34 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (19–20 lines × 2) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidPool.cs:43 — Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidPool.cs:43-61 | Content/NPCs/FestersandSerpents/Projectiles/FssIchorPool.cs:110-129 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidPool.cs` and `Content/NPCs/FestersandSerpents/Projectiles/FssIchorPool.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidPool.cs:43` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (19–20 lines × 2) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerHoverShootState.cs:98 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerHoverShootState.cs:98-117 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerVerticalBarrageState.cs:104-122 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerHoverShootState.cs` and `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerVerticalBarrageState.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 49 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerHoverShootState.cs:98` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (16–17 lines × 2) · ×11
  • Duplicated block (16–17 lines × 2) Common/ShockRingDraw.cs:57 — Common/ShockRingDraw.cs:57-73 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteRingRender.cs:128-143 — before extracting anything, compare `Common/ShockRingDraw.cs` and `Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteRingRender.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Common/ShockRingDraw.cs:57` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Common/ShockRingDraw.cs:55` calls `SetValue`, `ToVector3` and `Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteRingRender.cs:128` 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 (16–17 lines × 2) Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomSporeMistTelegraph.cs:96 — Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomSporeMistTelegraph.cs:96-111 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandConeTelegraph.cs:112-128 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomSporeMistTelegraph.cs:96` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16–17 lines × 2) Content/GameModes/GodSmith/Weapons/Shortswords/GsThrustHeldBase.cs:962 — Content/GameModes/GodSmith/Weapons/Shortswords/GsThrustHeldBase.cs:962-977 | Content/Items/Modifys/RBloodButcherer.cs:525-541 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (16–17 lines × 2) Content/Items/Melee/Arbiters/ArbiterManifestationRenderer.cs:222 — Content/Items/Melee/Arbiters/ArbiterManifestationRenderer.cs:222-238 | Content/Items/Melee/WeaverGrievanceses/WGMaterializationRenderer.cs:124-139 — before extracting anything, compare `Content/Items/Melee/Arbiters/ArbiterManifestationRenderer.cs` and `Content/Items/Melee/WeaverGrievanceses/WGMaterializationRenderer.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Arbiters/ArbiterManifestationRenderer.cs:222` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16–17 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:619 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:619-634 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:700-716 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs` as WHOLE FILES: this scan already matched 68 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:619` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (16–17 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:175 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:175-190 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:172-188 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:175` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (16–17 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeLaserBolt.cs:116 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeLaserBolt.cs:116-132 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeMortar.cs:264-279 — 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. 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 (16–17 lines × 2) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingPanel.cs:512 — Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingPanel.cs:512-527 | Content/LegendWeapon/SHPCLegend/UI/SHPCModuleSelectPanel.cs:314-330 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingPanel.cs:512` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16–17 lines × 2) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistGazeBeam.cs:276 — Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistGazeBeam.cs:276-291 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistGazeBeam.cs:338-354 — 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–17 lines × 2) Content/Narrative/Presentation/Skins/Sulfsea/SulfseaDialogueSkin.cs:70 — Content/Narrative/Presentation/Skins/Sulfsea/SulfseaDialogueSkin.cs:70-85 | Content/Narrative/Presentation/Skins/Tzeentch/TzeentchDialogueSkin.cs:75-91 — before extracting anything, compare `Content/Narrative/Presentation/Skins/Sulfsea/SulfseaDialogueSkin.cs` and `Content/Narrative/Presentation/Skins/Tzeentch/TzeentchDialogueSkin.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Narrative/Presentation/Skins/Sulfsea/SulfseaDialogueSkin.cs:70` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16–17 lines × 2) Content/QuestLogs/Styles/ForestQuestLogStyle.cs:180 — Content/QuestLogs/Styles/ForestQuestLogStyle.cs:180-196 | Content/QuestLogs/Styles/ForestQuestLogStyle.cs:224-239 — 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. 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.
D4 · Code Duplication · Duplicated block (15–16 lines × 2) · ×11
  • Duplicated block (15–16 lines × 2) Content/EntrustManager/BaseQuestAcceptUI.cs:298 — Content/EntrustManager/BaseQuestAcceptUI.cs:298-312 | Content/UIs/OverhaulSettings/OverhaulSettingsUI.cs:407-422 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/EntrustManager/BaseQuestAcceptUI.cs:298` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/EntrustManager/BaseQuestAcceptUI.cs:312` calls `Sin`, `Color`, `DrawRoundedRect` and `Content/UIs/OverhaulSettings/OverhaulSettingsUI.cs:422` 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 (15–16 lines × 2) Content/Industrials/ElectricPowers/Collectors/Collector.cs:112 — Content/Industrials/ElectricPowers/Collectors/Collector.cs:112-126 | Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:184-199 — before extracting anything, compare `Content/Industrials/ElectricPowers/Collectors/Collector.cs` and `Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Collectors/Collector.cs:112` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (15–16 lines × 2) Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:574 — Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:574-588 | Content/Items/Modifys/RBloodButcherer.cs:517-532 — before extracting anything, compare `Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs` and `Content/Items/Modifys/RBloodButcherer.cs` as WHOLE FILES: this scan already matched 36 separate duplicated blocks between them, totalling at least 458 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:574` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15–16 lines × 2) Content/LegendWeapon/HalibutLegend/DomainSkills/YourLevelIsTooLow.cs:305 — Content/LegendWeapon/HalibutLegend/DomainSkills/YourLevelIsTooLow.cs:305-320 | Content/LegendWeapon/HalibutLegend/DomainSkills/YourLevelIsTooLow.cs:334-348 — 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 (15–16 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:881 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:881-896 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:921-935 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:881` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15–16 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:301 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:301-315 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:251-266 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs` and `Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 216 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:301` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15–16 lines × 2) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspaceRender.cs:130 — Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspaceRender.cs:130-144 | Content/Scenarios/OldNet/Renders/OldNetGradeRender.cs:48-63 — before extracting anything, compare `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspaceRender.cs` and `Content/Scenarios/OldNet/Renders/OldNetGradeRender.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspaceRender.cs:130` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (15–16 lines × 2) Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.Net.cs:581 — Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.Net.cs:581-595 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.Net.cs:622-637 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.Net.cs:581` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `target` to `NPCFreezeTarget` in one and `ProjectileFreezeTarget` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (15–16 lines × 2) Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerRenderHelper.cs:140 — Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerRenderHelper.cs:140-154 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerRenderHelper.cs:234-249 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerRenderHelper.cs:140` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15–16 lines × 2) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerDashingState.cs:65 — Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerDashingState.cs:65-80 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronTidalDashState.cs:176-190 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerDashingState.cs:65` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (15–16 lines × 2) Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryWatcher.cs:126 — Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryWatcher.cs:126-141 | Content/Scenarios/Dungeonworld/Gen/BossRooms/ProofingHallWatcher.cs:97-111 — before extracting anything, compare `Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryWatcher.cs` and `Content/Scenarios/Dungeonworld/Gen/BossRooms/ProofingHallWatcher.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 62 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryWatcher.cs:126` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8 lines × 6) · ×11
  • Duplicated block (8 lines × 6) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:54 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:54-61 | Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs:59-66 | Content/Scenarios/Kiame/Overlay/OniRainDescentRender.cs:76-83 | Content/Scenarios/Kiame/Overlay/OniRainWorldRender.cs:50-57 | Content/Scenarios/Kiame/Overlay/OniUmbrellaPuddleRender.cs:66-73 | Content/Scenarios/Kiame/Water/KiameWaterRender.cs:115-122 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs` and `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 192 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs:56` calls `LoadNPC` and `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:52` does not — after which the two agree again for 3 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 × 6) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:452 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:452-459 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:701-708 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:450-457 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:742-749 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:427-434 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:415-422 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs` as WHOLE FILES: this scan already matched 46 separate duplicated blocks between them, totalling at least 456 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 6) Content/Items/Melee/OniMacheteHands.cs:1346 — Content/Items/Melee/OniMacheteHands.cs:1346-1353 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCrimsonTiger.cs:797-804 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCursed.cs:461-468 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDemonicHell.cs:644-651 | Content/LegendWeapon/HalibutLegend/FishSkills/FishFallenStarVFX.cs:210-217 | Content/LegendWeapon/HalibutLegend/FishSkills/FishofCthulu.cs:959-966 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/OniMacheteHands.cs:1346` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 6) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:57 — Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:57-64 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs:95-102 | Content/Scenarios/Kiame/KiameWakeResetRender.cs:93-100 | Content/Scenarios/Kiame/Overlay/OniRainDescentRender.cs:79-86 | Content/Scenarios/Kiame/Overlay/OniUmbrellaPuddleRender.cs:69-76 | Content/Scenarios/Kiame/Water/KiameWaterRender.cs:118-125 — before extracting anything, compare `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs` and `Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:54` calls `GetRenderTargets` and `Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs:92` 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 × 6) Content/Scenarios/OldNet/NPCs/OldNetLurkerICE.cs:235 — Content/Scenarios/OldNet/NPCs/OldNetLurkerICE.cs:235-242 | Content/Scenarios/OldNet/NPCs/OldNetPatrolICE.cs:220-227 | Content/Scenarios/OldNet/NPCs/OldNetSweepEye.cs:169-176 | Content/Scenarios/OldNet/NPCs/OldNetTaggerICE.cs:222-229 | Content/Scenarios/OldNet/NPCs/OldNetTracerICE.cs:376-383 | Content/Scenarios/OldNet/NPCs/OldNetTurretICE.cs:116-123 — 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 6 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/OldNet/NPCs/OldNetLurkerICE.cs:235` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Scenarios/OldNet/NPCs/OldNetPatrolICE.cs:230` calls `Get` and `Content/Scenarios/OldNet/NPCs/OldNetLurkerICE.cs:244` does not — after which the two agree again for 3 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 × 6) Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs:118 — Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs:118-125 | Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteDiveOmen.cs:102-110 | Content/GameModes/BrutalMobs/NightPack/Projectiles/NightDiveOmen.cs:128-136 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkChargeOmen.cs:139-147 | Content/GameModes/BrutalMobs/Sky/Projectiles/SkyGaleDiveOmen.cs:115-123 | Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornDiveLane.cs:114-122 — before extracting anything, compare `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs` and `Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteDiveOmen.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs:118` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 × 6) Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsDeadlySphereSawProj.cs:32 — Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsDeadlySphereSawProj.cs:32-39 | Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsEmpressFinaleProj.cs:35-42 | Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsRavenOmenProj.cs:34-41 | Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsStormTigerRendProj.cs:34-41 | Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsWebBindProj.cs:27-34 | Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsXenoOrbitalProj.cs:40-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 6 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 6) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:877 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:877-884 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1113-1120 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:902-909 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:922-929 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:836-843 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:871-878 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs` as WHOLE FILES: this scan already matched 46 separate duplicated blocks between them, totalling at least 456 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:833` calls `HeldForm`, `Lerp`, `HandForm` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:875` does not — after which the two agree again for 3 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 × 6) Content/NPCs/BloomsandSerpents/BssVfx.cs:28 — Content/NPCs/BloomsandSerpents/BssVfx.cs:28-35 | Content/NPCs/FestersandSerpents/FssVfx.cs:41-48 | Content/NPCs/ScrapCommanders/Core/IScrapState.cs:150-157 | Content/NPCs/SeaShrimp/Core/ISeaShrimpState.cs:146-153 | Content/NPCs/SeaShrimp/Kinematics/ShrimpTerrain.cs:69-76 | Content/Wraiths/Projectiles/HeadlessShadeRig.cs:144-151 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/NPCs/SeaShrimp/Kinematics/ShrimpTerrain.cs:80` calls `WetAt`, `WetCollision`, `Vector2` and `Content/NPCs/ScrapCommanders/Core/IScrapState.cs:161` 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 × 6) Content/Scenarios/Dungeonworld/Dungeonworld.cs:90 — Content/Scenarios/Dungeonworld/Dungeonworld.cs:90-97 | Content/Scenarios/Hadalworld/Hadalworld.cs:63-70 | Content/Scenarios/Kiame/KiameWorld.cs:59-66 | Content/Scenarios/Kiyume/KiyumeWorld.cs:59-66 | Content/Scenarios/OldNet/OldNetWorld.cs:60-67 | Content/Scenarios/Shepel/CybCourses/CybCourse.cs:36-43 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/Dungeonworld.cs:90` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 6) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:2001 — Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:2001-2008 | Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:1209-1216 | Content/Scenarios/Dungeonworld/NPCs/GaolDormantSkull.cs:212-219 | Content/Scenarios/Dungeonworld/NPCs/OverseerDormantRig.cs:301-308 | Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:1725-1732 | Content/Scenarios/Dungeonworld/NPCs/UndrownedThrone.cs:297-304 — 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 6 call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (7 lines × 6) · ×11
  • Duplicated block (7 lines × 6) Content/Industrials/ElectricPowers/MiningMachines/BaseMiningMachineTP.cs:424 — Content/Industrials/ElectricPowers/MiningMachines/BaseMiningMachineTP.cs:424-430 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatTile.cs:110-116 | Content/Industrials/ElectricPowers/Sundials/ElectricSundialTile.cs:114-120 | Content/Industrials/ElectricPowers/Throwers/ThrowerTile.cs:111-117 | Content/Industrials/ElectricPowers/WeatherControllers/WeatherControllerTile.cs:120-126 | Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersTile.cs:68-74 — before extracting anything, compare `Content/Industrials/ElectricPowers/SlimeVats/SlimeVatTile.cs` and `Content/Industrials/ElectricPowers/Sundials/ElectricSundialTile.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/MiningMachines/BaseMiningMachineTP.cs:424` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 6) Content/EntrustManager/Styles/DraedonManagerStyle.cs:106 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:106-112 | Content/EntrustManager/Styles/ForestManagerStyle.cs:105-111 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:101-107 | Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:70-76 | Content/QuestLogs/Styles/ForestQuestLogStyle.cs:72-78 | Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:35-41 — before extracting anything, compare `Content/EntrustManager/Styles/DraedonManagerStyle.cs` and `Content/EntrustManager/Styles/ForestManagerStyle.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 334 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 (7 lines × 6) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:1480 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:1480-1486 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1382-1388 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1449-1455 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1506-1512 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1568-1574 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1395-1401 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:1480` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:1477` calls `PlaySound` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1379` 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 × 6) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:853 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:853-859 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1092-1098 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:878-884 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:901-907 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:807-813 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:847-853 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs` as WHOLE FILES: this scan already matched 46 separate duplicated blocks between them, totalling at least 456 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (7 lines × 6) Content/GameModes/Blessings/UI/BlessingRenderer.cs:46 — Content/GameModes/Blessings/UI/BlessingRenderer.cs:46-53 | Content/Industrials/UIs/IndustrialTerminalRenderer.cs:53-60 | Content/LegendWeapon/HalibutLegend/UI/HalibutRenderer.cs:453-459 | Content/LegendWeapon/KikasaLegend/KikasaVaults/KikasaVaultRenderer.cs:32-38 | Content/LegendWeapon/KikasaLegend/UI/Panorama/KikasaPanoramaRenderer.cs:39-45 | Content/MainMenus/Overs/AckRenderer.cs:284-290 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/Blessings/UI/BlessingRenderer.cs:46` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaVaults/KikasaVaultRenderer.cs:38` calls `SetValue` and `Content/LegendWeapon/HalibutLegend/UI/HalibutRenderer.cs:459` 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 × 6) Content/Items/Melee/DragonsScaleGreatsword.cs:674 — Content/Items/Melee/DragonsScaleGreatsword.cs:674-680 | Content/Items/Melee/DragonsScaleGreatsword.cs:884-890 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:1036-1042 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs:326-332 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofRetinaScanBeam.cs:230-237 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofRotBeamProj.cs:160-167 — before extracting anything, compare `Content/Items/Melee/DragonsScaleGreatsword.cs` and `Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 415 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Melee/DragonsScaleGreatsword.cs:684` calls `SetValue` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs:336` 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 × 6) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:385 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:385-392 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:375-382 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:318-324 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:301-308 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:349-356 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:391-398 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 598 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:385` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:385` calls `PlaySound` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:395` 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 × 6) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:285 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:285-291 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:1069-1076 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1286-1293 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1300-1307 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1440-1446 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1588-1595 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:285` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 6) Content/LegendWeapon/OnikiriLegend/UI/OniLedgerSwapFX.cs:126 — Content/LegendWeapon/OnikiriLegend/UI/OniLedgerSwapFX.cs:126-132 | Content/LegendWeapon/OnikiriLegend/UI/OniMeiStandDraw.cs:34-41 | Content/LegendWeapon/OnikiriLegend/UI/OniPaperBurnDraw.cs:30-38 | Content/LegendWeapon/OnikiriLegend/UI/OniSigilBoardDraw.cs:57-63 | Content/LegendWeapon/OnikiriLegend/UI/OniStanceBladeDraw.cs:52-59 | Content/LegendWeapon/OnikiriLegend/UI/OniVigorInkDraw.cs:52-59 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/UI/OniLedgerSwapFX.cs` and `Content/LegendWeapon/OnikiriLegend/UI/OniVigorInkDraw.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 44 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/UI/OniPaperBurnDraw.cs:30` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (7 lines × 6) Content/Items/Armor/Deepcrystals/DeepcrystalArmor.cs:43 — Content/Items/Armor/Deepcrystals/DeepcrystalArmor.cs:43-49 | Content/Items/Armor/Deepcrystals/DeepcrystalArmor.cs:64-70 | Content/Items/Armor/Deepcrystals/DeepcrystalArmor.cs:85-91 | Content/Items/Armor/Deepcrystals/DeepcrystalArmor.cs:106-112 | Content/Items/Armor/Deepcrystals/DeepcrystalArmor.cs:126-132 | Content/Items/Armor/Deepcrystals/DeepcrystalArmor.cs:148-154 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Armor/Deepcrystals/DeepcrystalArmor.cs:53` calls `GetAttackSpeed` and `Content/Items/Armor/Deepcrystals/DeepcrystalArmor.cs:136` 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 × 6) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1008 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1008-1014 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1136-1142 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:914-920 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:723-729 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:977-983 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1202-1208 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 598 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (8–9 lines × 3) · ×11
  • Duplicated block (8–9 lines × 3) Content/GameModes/BrutalMobs/Ambience/Duskwatch/PRT_DuskwatchAsh.cs:61 — Content/GameModes/BrutalMobs/Ambience/Duskwatch/PRT_DuskwatchAsh.cs:61-68 | Content/GameModes/BrutalMobs/Ambience/Silkcrypt/PRT_SilkcryptLint.cs:58-65 | Content/PRTTypes/PRT_DefCrystalShard.cs:48-56 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/Duskwatch/PRT_DuskwatchAsh.cs:61` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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–9 lines × 3) Content/GameModes/BrutalMobs/Ambience/Fleshfen/FleshfenHazeRender.cs:186 — Content/GameModes/BrutalMobs/Ambience/Fleshfen/FleshfenHazeRender.cs:186-193 | Content/GameModes/BrutalMobs/Ambience/Lumindepth/LumindepthAmbientRender.cs:315-323 | Content/GameModes/BrutalMobs/Ambience/Rotmire/RotmireMistRender.cs:189-196 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/Fleshfen/FleshfenHazeRender.cs:186` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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–9 lines × 3) Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhImpFireBolt.cs:61 — Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhImpFireBolt.cs:61-68 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhTridentBolt.cs:61-68 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkMortarShellProj.cs:79-87 — before extracting anything, compare `Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhImpFireBolt.cs` and `Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhTridentBolt.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 79 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhImpFireBolt.cs:61` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8–9 lines × 3) Content/Industrials/ElectricPowers/Collectors/CollectorUI.cs:777 — Content/Industrials/ElectricPowers/Collectors/CollectorUI.cs:777-784 | Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:934-941 | Content/Industrials/Modifys/ChargingStationUI.cs:610-618 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. 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–9 lines × 3) Content/Items/Summon/ElementWhip.cs:156 — Content/Items/Summon/ElementWhip.cs:156-164 | Content/Items/Summon/GhostFireWhip.cs:149-157 | Content/Items/Summon/WhiplashGalactica.cs:154-161 — before extracting anything, compare `Content/Items/Summon/ElementWhip.cs` and `Content/Items/Summon/GhostFireWhip.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 61 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Summon/ElementWhip.cs:156` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (8–9 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangProj.cs:113 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangProj.cs:113-120 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailHead.cs:127-134 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoProj.cs:117-125 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (8–9 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:149 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:149-157 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:119-126 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:161-168 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:149` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8–9 lines × 3) Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraDashProj.cs:160 — Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraDashProj.cs:160-168 | Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraFinaleAssets.cs:80-87 | Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraSlashProj.cs:162-170 — 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 (8–9 lines × 3) Content/NPCs/ScrapCommanders/Projectiles/ScrapAutonomousTool.cs:146 — Content/NPCs/ScrapCommanders/Projectiles/ScrapAutonomousTool.cs:146-154 | Content/NPCs/ScrapCommanders/Projectiles/ScrapMortarShell.cs:126-133 | Content/NPCs/ScrapCommanders/Projectiles/ScrapShellFrag.cs:69-76 — before extracting anything, compare `Content/NPCs/ScrapCommanders/Projectiles/ScrapMortarShell.cs` and `Content/NPCs/ScrapCommanders/Projectiles/ScrapShellFrag.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/ScrapCommanders/Projectiles/ScrapAutonomousTool.cs:146` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/NPCs/ScrapCommanders/Projectiles/ScrapAutonomousTool.cs:156` calls `OnKill`, `HitSparks` and `Content/NPCs/ScrapCommanders/Projectiles/ScrapMortarShell.cs:134` 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–9 lines × 3) Content/PRTTypes/PRT_DWave.cs:34 — Content/PRTTypes/PRT_DWave.cs:34-42 | Content/PRTTypes/PRT_LonginusWave.cs:43-51 | Content/PRTTypes/PRT_StarPulseRing.cs:32-39 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/PRTTypes/PRT_DWave.cs:34` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/PRTTypes/PRT_LonginusWave.cs:42` calls `SetProperty` and `Content/PRTTypes/PRT_DWave.cs:32` does not — after which the two agree again for 3 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–9 lines × 3) Content/Scenarios/Kiame/Backgrounds/KiameSky.cs:130 — Content/Scenarios/Kiame/Backgrounds/KiameSky.cs:130-137 | Content/Scenarios/Kiame/Overlay/OniRainWorldSky.cs:132-140 | Content/Wraiths/Abilities/GhostRains/GhostRainAmbience.cs:167-174 — before extracting anything, compare `Content/Scenarios/Kiame/Backgrounds/KiameSky.cs` and `Content/Scenarios/Kiame/Overlay/OniRainWorldSky.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Kiame/Backgrounds/KiameSky.cs:130` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Scenarios/Kiame/Overlay/OniRainWorldSky.cs:132` calls `SetValue` and `Content/Scenarios/Kiame/Backgrounds/KiameSky.cs:130` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Edited copy of a member (46 corresponding lines) · ×10
  • Edited copy of a member (46 corresponding lines) Content/EntrustManager/Styles/DraedonManagerStyle.cs:132 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:132-177 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:127-176 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (46 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetHourglass.cs:350 — Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetHourglass.cs:350-395 | Content/Scenarios/Kiame/KiameWakeResetRender.cs:254-311 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (46 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:195 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:195-244 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterGlob.cs:171-216 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (46 corresponding lines) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowGeyserProj.cs:132 — Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowGeyserProj.cs:132-177 | Content/NPCs/FestersandSerpents/Projectiles/FssGeyserColumn.cs:136-181 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (46 corresponding lines) Content/Items/Ranged/Undertows/UndertowSpine.cs:226 — Content/Items/Ranged/Undertows/UndertowSpine.cs:226-271 | Content/Items/Summon/Deepclaws/DeepclawLobster.cs:518-563 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (46 corresponding lines) Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipDurendalProj.cs:58 — Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipDurendalProj.cs:58-103 | Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipMorningStarProj.cs:59-113 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (46 corresponding lines) Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineTP.cs:364 — Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineTP.cs:364-409 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterTP.cs:514-562 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (46 corresponding lines) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:232 — Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:232-283 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaReset.cs:261-306 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (46 corresponding lines) Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:189 — Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:189-237 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:683-728 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (46 corresponding lines) Content/GameModes/BrutalMobs/FrostLegion/FrostLegionNPC.cs:282 — Content/GameModes/BrutalMobs/FrostLegion/FrostLegionNPC.cs:282-327 | Content/GameModes/BrutalMobs/Graveyard/GraveyardBrutalNPC.cs:215-269 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 9+ corresponding lines) · ×10
  • Edited copies of one member (5 members, 9+ corresponding lines) Content/UIs/UIEffect/BubblePRT.cs:43 — Content/UIs/UIEffect/BubblePRT.cs:43-52 | Content/UIs/UIEffect/BubblePRT.cs:54-63 | Content/UIs/UIEffect/FlameWispPRT.cs:82-95 | Content/UIs/UIEffect/SeaStarPRT.cs:38-46 | Content/UIs/UIEffect/SeaStarPRT.cs:48-56 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 9+ corresponding lines) Content/GameModes/GodSmith/Weapons/Broadswords/BroadswordSchemes.Wood.cs:748 — Content/GameModes/GodSmith/Weapons/Broadswords/BroadswordSchemes.Wood.cs:748-756 | Content/GameModes/GodSmith/Weapons/Broadswords/GsBladetongue.cs:200-209 | Content/GameModes/GodSmith/Weapons/Broadswords/GsBloodButcherer.cs:191-203 | Content/GameModes/GodSmith/Weapons/Broadswords/GsChlorophyteClaymore.cs:252-261 | Content/GameModes/GodSmith/Weapons/Broadswords/GsChlorophyteSaber.cs:177-186 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 9+ corresponding lines) Content/GameModes/BrutalMobs/Ambience/Hollowdeep/HollowdeepPRT.cs:42 — Content/GameModes/BrutalMobs/Ambience/Hollowdeep/HollowdeepPRT.cs:42-51 | Content/GameModes/BrutalMobs/Ambience/Hollowdeep/HollowdeepPRT.cs:98-108 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCloudEffects.cs:67-75 | Content/LegendWeapon/HalibutLegend/FishSkills/FishVariegatedLardVFX.cs:144-154 | Content/PRTTypes/PRT_GaolRoomEmber.cs:50-60 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 9+ corresponding lines) Content/NPCs/ScrapCommanders/ScrapCommander.cs:126 — Content/NPCs/ScrapCommanders/ScrapCommander.cs:126-134 | Content/NPCs/SeaShrimp/SeaShrimpBoss.cs:53-61 | Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:247-255 | Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:220-229 | Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:266-275 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 9+ corresponding lines) Content/HackTimes/Protocols/CompensationProtocol.cs:192 — Content/HackTimes/Protocols/CompensationProtocol.cs:192-201 | Content/HackTimes/Protocols/HackProjectileConversion.cs:113-124 | Content/HackTimes/Protocols/PayloadRewrite.cs:83-91 | Content/HackTimes/Protocols/PayloadRewrite.cs:112-120 | Content/HackTimes/Protocols/ProjectileHijack.cs:59-69 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 9+ corresponding lines) Content/Items/Magic/AriaofTheCosmoses/GammaRayBeam.cs:140 — Content/Items/Magic/AriaofTheCosmoses/GammaRayBeam.cs:140-148 | Content/Items/Magic/CommandersStaff.cs:287-295 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPour.cs:545-553 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressLance.cs:95-103 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Projectiles/EmpressLance.cs:205-213 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 9+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/TwinsTetherArc.cs:165 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/TwinsTetherArc.cs:165-174 | Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraVineLattice.cs:198-207 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeArcChainProj.cs:173-182 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofGrabTongueProj.cs:164-172 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofTongueLashProj.cs:100-108 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 9+ corresponding lines) Content/GameModes/GodSmith/Weapons/Shortswords/GsTungstenShortsword.cs:74 — Content/GameModes/GodSmith/Weapons/Shortswords/GsTungstenShortsword.cs:74-83 | Content/GameModes/GodSmith/Weapons/Spears/GsDarkLance.cs:76-84 | Content/GameModes/GodSmith/Weapons/Spears/GsGungnir.cs:63-72 | Content/GameModes/GodSmith/Weapons/Spears/GsTheRottedFork.cs:68-77 | Content/Items/Melee/CursedflameBloodfists/CursedflameBloodfistHeld.cs:232-251 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 9+ corresponding lines) Content/GameModes/GodSmith/Weapons/MagicConduit/GsChargedBlasterCannon.cs:28 — Content/GameModes/GodSmith/Weapons/MagicConduit/GsChargedBlasterCannon.cs:28-36 | Content/GameModes/GodSmith/Weapons/MagicConduit/GsLastPrism.cs:38-46 | Content/GameModes/GodSmith/Weapons/MagicConduit/GsMedusaHead.cs:32-41 | Content/GameModes/GodSmith/Weapons/MagicConduit/GsShadowbeamStaff.cs:23-31 | Content/GameModes/GodSmith/Weapons/MagicConduit/GsSoulDrain.cs:30-38 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 9+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronSharkTornadoProj.cs:207 — Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronSharkTornadoProj.cs:207-215 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronBubbleMazeState.cs:169-177 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronSharkronStrafeState.cs:184-192 | Content/NPCs/BrutalNPCs/BrutalPlantera/PlanteraSporeAI.cs:30-38 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Core/WofStateContext.cs:86-94 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (18–19 lines × 2) · ×10
  • Duplicated block (18–19 lines × 2) Content/EntrustManager/Styles/DraedonManagerStyle.cs:69 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:69-86 | Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:42-60 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/EntrustManager/Styles/DraedonManagerStyle.cs:69` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18–19 lines × 2) Content/Items/Armor/Deepcrystals/DeepcrystalPlayer.cs:297 — Content/Items/Armor/Deepcrystals/DeepcrystalPlayer.cs:297-314 | Content/NPCs/SeaShrimp/Rendering/SeaShrimpBubbleRender.cs:55-73 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Armor/Deepcrystals/DeepcrystalPlayer.cs:297` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18–19 lines × 2) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:86 — Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:86-103 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaReset.cs:96-114 — before extracting anything, compare `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs` and `Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaReset.cs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (18–19 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:78 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:78-96 | Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs:87-104 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs` and `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 192 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:78` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18–19 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamSky.cs:70 — Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamSky.cs:70-88 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspaceSky.cs:70-87 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamSky.cs` and `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspaceSky.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (18–19 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:257 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:257-274 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:216-234 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:257` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18–19 lines × 2) Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsFrostQuakeState.cs:26 — Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsFrostQuakeState.cs:26-43 | Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsSpikeWaveState.cs:25-43 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsFrostQuakeState.cs:26` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18–19 lines × 2) Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:361 — Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:361-379 | Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:298-315 — before extracting anything, compare `Content/QuestLogs/Styles/DraedonQuestLogStyle.cs` and `Content/QuestLogs/Styles/HotwindQuestLogStyle.cs` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 377 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:361` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18–19 lines × 2) Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryRoom.cs:21 — Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryRoom.cs:21-39 | Content/Scenarios/Dungeonworld/Gen/BossRooms/ProofingHallRoom.cs:20-37 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryRoom.cs:21` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18–19 lines × 2) Content/Scenarios/Dungeonworld/NPCs/OverseerDormantRig.cs:143 — Content/Scenarios/Dungeonworld/NPCs/OverseerDormantRig.cs:143-160 | Content/Scenarios/Dungeonworld/NPCs/UndrownedThrone.cs:148-166 — before extracting anything, compare `Content/Scenarios/Dungeonworld/NPCs/OverseerDormantRig.cs` and `Content/Scenarios/Dungeonworld/NPCs/UndrownedThrone.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 73 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/NPCs/OverseerDormantRig.cs:143` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11 lines × 6) · ×10
  • Duplicated block (11 lines × 6) Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:258 — Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:258-268 | Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:298-308 | Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:341-351 | Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:387-397 | Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:433-443 | Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:479-489 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:258` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 6) Content/Cyberwares/Implementation/Sandevistans/SandevistanRender.cs:42 — Content/Cyberwares/Implementation/Sandevistans/SandevistanRender.cs:42-54 | Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:50-60 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainRender.cs:44-57 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainRender.cs:170-182 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspaceRender.cs:123-134 | Content/Scenarios/OldNet/Renders/OldNetGradeRender.cs:42-52 — before extracting anything, compare `Content/Cyberwares/Implementation/Sandevistans/SandevistanRender.cs` and `Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainRender.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Cyberwares/Implementation/Sandevistans/SandevistanRender.cs:42` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:49` calls `DrawLowQualityFallback` and `Content/Cyberwares/Implementation/Sandevistans/SandevistanRender.cs:41` does not — after which the two agree again for 3 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 × 6) Content/GameModes/GodSmith/Weapons/Broadswords/GsOrichalcumSword.cs:123 — Content/GameModes/GodSmith/Weapons/Broadswords/GsOrichalcumSword.cs:123-133 | Content/GameModes/GodSmith/Weapons/Spears/GsChlorophytePartisan.cs:142-152 | Content/GameModes/GodSmith/Weapons/Spears/GsJoustingLances.cs:493-503 | Content/GameModes/GodSmith/Weapons/Spears/GsMythrilHalberd.cs:103-113 | Content/GameModes/GodSmith/Weapons/Spears/GsOrichalcumHalberd.cs:88-98 | Content/GameModes/GodSmith/Weapons/Spears/GsTitaniumTrident.cs:91-101 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times.
  • Duplicated block (11 lines × 6) Content/GameModes/GodSmith/Weapons/Flails/GsBallOHurt.cs:105 — Content/GameModes/GodSmith/Weapons/Flails/GsBallOHurt.cs:105-115 | Content/GameModes/GodSmith/Weapons/Flails/GsChainGuillotines.cs:127-137 | Content/GameModes/GodSmith/Weapons/Flails/GsDaoofPow.cs:120-130 | Content/GameModes/GodSmith/Weapons/Flails/GsGolemFist.cs:166-176 | Content/GameModes/GodSmith/Weapons/Flails/GsKOCannon.cs:150-160 | Content/GameModes/GodSmith/Weapons/Flails/GsSunfury.cs:75-85 — 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 6 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/GodSmith/Weapons/Flails/GsChainGuillotines.cs:125` calls `Lerp` and `Content/GameModes/GodSmith/Weapons/Flails/GsGolemFist.cs:164` does not — after which the two agree again for 3 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 × 6) Content/Items/Melee/DestroyersBlade.cs:677 — Content/Items/Melee/DestroyersBlade.cs:677-687 | Content/Items/Melee/DestroyersBladeEXs/DestroyersBeamEX.cs:160-171 | Content/Items/Melee/Flawless.cs:568-578 | Content/Items/Melee/Heartcarver.cs:956-966 | Content/Items/Melee/SpearOfLonginuses/LonginusAssets.cs:302-312 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Projectiles/EmpressAuroraVeil.cs:116-126 — before extracting anything, compare `Content/Items/Melee/DestroyersBlade.cs` and `Content/Items/Melee/DestroyersBladeEXs/DestroyersBeamEX.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DestroyersBlade.cs:677` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Melee/SpearOfLonginuses/LonginusAssets.cs:312` calls `SetValue` and `Content/Items/Melee/Heartcarver.cs:966` does not — after which the two agree again for 3 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 × 6) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:51 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:51-61 | Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainRender.cs:64-75 | Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainRender.cs:216-227 | Content/Scenarios/Kiame/Overlay/OniRainDescentRender.cs:73-83 | Content/Scenarios/Kiame/Overlay/OniRainWorldRender.cs:47-57 | Content/Scenarios/Kiame/Overlay/OniUmbrellaPuddleRender.cs:63-73 — there are 6 copies across 5 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 6 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:51` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainRender.cs:77` calls `SetSharedParams` and `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:64` 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 × 6) Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuFeiFX.cs:59 — Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuFeiFX.cs:59-69 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuHangFX.cs:60-71 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuHongFX.cs:64-75 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuLaoFX.cs:106-116 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuXiFX.cs:153-163 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuYinFX.cs:73-83 — 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 6 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuFeiFX.cs:59` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuHongFX.cs:58` calls `Clamp`, `ArchPoint`, `Vector2` and `Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuHangFX.cs:58` 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 × 6) Content/GameModes/BrutalMobs/Ambience/Mireheart/Projectiles/MireheartBeeCloudProj.cs:60 — Content/GameModes/BrutalMobs/Ambience/Mireheart/Projectiles/MireheartBeeCloudProj.cs:60-70 | Content/GameModes/BrutalMobs/Ambience/Mireheart/Projectiles/MireheartMiasmaProj.cs:89-99 | Content/GameModes/BrutalMobs/NightPack/Projectiles/NightPounceOmen.cs:56-66 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkClawCrossProj.cs:60-70 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkScytheBladeProj.cs:65-75 | Content/GameModes/BrutalMobs/Sky/Projectiles/SkyFeatherFanOmen.cs:67-77 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times.
  • Duplicated block (11 lines × 6) Content/GameModes/BrutalMobs/Ambience/Mireheart/Projectiles/MireheartGasPocketProj.cs:41 — Content/GameModes/BrutalMobs/Ambience/Mireheart/Projectiles/MireheartGasPocketProj.cs:41-51 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionInkOmen.cs:45-55 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionScoutOmen.cs:36-46 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtBoardingOmen.cs:33-43 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtBroadsideOmen.cs:62-72 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtVolleyOmen.cs:51-61 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/BrutalMobs/Ambience/Mireheart/Projectiles/MireheartGasPocketProj.cs:39` calls `SetStaticDefaults` and `Content/GameModes/BrutalMobs/Legion/Projectiles/LegionInkOmen.cs:43` does not — after which the two agree again for 4 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 × 6) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Projectiles/EmpressAuroraVeil.cs:34 — Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Projectiles/EmpressAuroraVeil.cs:34-44 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSCrownProj.cs:56-66 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSGelPoolProj.cs:29-39 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSGeyserProj.cs:48-58 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSRoyalPillarProj.cs:31-41 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSTideWaveProj.cs:76-86 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSGelPoolProj.cs:41` calls `ShouldUpdatePosition` and `Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSTideWaveProj.cs:88` 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.
D4 · Code Duplication · Duplicated block (12 lines × 4) · ×10
  • Duplicated block (12 lines × 4) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSlashRenderer.cs:316 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSlashRenderer.cs:316-327 | Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilateRenderer.cs:26-37 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleRenderer.cs:221-232 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlashRenderer.cs:343-354 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSlashRenderer.cs:328` calls `SetValue` and `Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlashRenderer.cs:355` does not — after which the two agree again for 4 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 (12 lines × 4) Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT1.cs:154 — Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT1.cs:154-165 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT3.cs:82-93 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsOdditiesFlurryHeldBase.cs:99-110 | Content/GameModes/GodSmith/Weapons/Spears/GsJoustingLances.cs:131-142 — before extracting anything, compare `Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT1.cs` and `Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT3.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 89 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT1.cs:154` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 4) Content/Items/Modifys/RBloodButcherer.cs:866 — Content/Items/Modifys/RBloodButcherer.cs:866-877 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:65-76 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:70-81 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterGlob.cs:61-72 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Modifys/RBloodButcherer.cs:866` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 4) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:398 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:398-410 | Content/Industrials/ElectricPowers/Launchers/PlayerLauncherUI.cs:356-367 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:325-337 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:398-410 — before extracting anything, compare `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs` and `Content/Industrials/ElectricPowers/Launchers/PlayerLauncherUI.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 144 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:398` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (12 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainSky.cs:109 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainSky.cs:109-123 | Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamSky.cs:69-81 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainSky.cs:90-104 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspaceSky.cs:69-80 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainSky.cs` and `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamSky.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (12 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownRender.cs:32 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownRender.cs:32-43 | Content/LegendWeapon/OnikiriLegend/OniDismembers/OniDismemberRender.cs:53-64 | Content/LegendWeapon/OnikiriLegend/OniDismembers/OniPlayerDismember.cs:420-431 | Content/LegendWeapon/OnikiriLegend/OniOmokages/OniOmokageRender.cs:82-93 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownRender.cs` and `Content/LegendWeapon/OnikiriLegend/OniDismembers/OniDismemberRender.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownRender.cs:32` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/OnikiriLegend/OniOmokages/OniOmokageRender.cs:81` calls `CompletePendingAsFallback` and `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownRender.cs:31` does not — after which the two agree again for 3 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 (12 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:116 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:116-127 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:110-121 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs:81-94 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeSkullBeamProj.cs:80-91 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs` and `Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 216 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:116` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 4) Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:292 — Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:292-304 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleCut.cs:337-348 | Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashMark.cs:232-243 | Content/LegendWeapon/OnikiriLegend/OniZanshinSlashs/OniZanshinSlash.cs:379-391 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:292` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 4) Content/NPCs/BrutalNPCs/BrutalDukeFishron/FishronGrabCutscene.cs:247 — Content/NPCs/BrutalNPCs/BrutalDukeFishron/FishronGrabCutscene.cs:247-258 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/EowDevourPlayer.cs:223-234 | Content/NPCs/BrutalNPCs/BrutalPlantera/PlanteraGrabPlayer.cs:117-128 | Content/Wraiths/Deaths/WraithRevivalDeathPlayer.cs:274-285 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (12 lines × 4) Content/Items/Melee/Flawless.cs:377 — Content/Items/Melee/Flawless.cs:377-388 | Content/Items/Melee/StormGoddessSpears/StormGoddessSpearHeld.cs:212-223 | Content/Items/Stones/Marbles/MarbleClub.cs:440-451 | Content/Items/Stones/Marbles/MarbleHuntingKnife.cs:271-282 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
D4 · Code Duplication · Duplicated block (13–14 lines × 3) · ×10
  • Duplicated block (13–14 lines × 3) Content/GameModes/BrutalMobs/Ambience/Ashreign/AshreignHeatHazeRender.cs:60 — Content/GameModes/BrutalMobs/Ambience/Ashreign/AshreignHeatHazeRender.cs:60-73 | Content/Industrials/Generator/Thermal/ThermalHeatHazeRender.cs:131-144 | Content/Scenarios/Dungeonworld/Gen/BossRooms/ProofingHallScene.cs:325-337 — before extracting anything, compare `Content/GameModes/BrutalMobs/Ambience/Ashreign/AshreignHeatHazeRender.cs` and `Content/Industrials/Generator/Thermal/ThermalHeatHazeRender.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (13–14 lines × 3) Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:441 — Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:441-453 | Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:334-346 | Content/Items/Modifys/RBloodButcherer.cs:367-380 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:441` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:333` calls `SetCompositeArmBack` and `Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:441` does not — after which the two agree again for 3 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 (13–14 lines × 3) Content/Items/Accessories/BrutalRelics/KingSlime/FallenCrownProj.cs:227 — Content/Items/Accessories/BrutalRelics/KingSlime/FallenCrownProj.cs:227-239 | Content/Items/Accessories/BrutalRelics/KingSlime/KingsVerdictWave.cs:142-154 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSCrownProj.cs:464-477 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/KingSlime/FallenCrownProj.cs:227` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (13–14 lines × 3) Content/Items/Melee/Shatterfangs/ShatterfangPRT.cs:49 — Content/Items/Melee/Shatterfangs/ShatterfangPRT.cs:49-61 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBoneParticles.cs:56-69 | Content/LegendWeapon/HalibutLegend/FishSkills/FishRockParticles.cs:141-154 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Shatterfangs/ShatterfangPRT.cs:49` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13–14 lines × 3) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetNet.cs:79 — Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetNet.cs:79-91 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownNet.cs:120-133 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetNet.cs:76-88 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetNet.cs:79` calls `ReadSingle` and `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownNet.cs:120` does not — after which the two agree again for 5 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 (13–14 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunBullet.cs:124 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunBullet.cs:124-136 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:102-115 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenCrystalShard.cs:91-104 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunBullet.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 137 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunBullet.cs:124` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13–14 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriSlash.cs:40 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriSlash.cs:40-52 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipLash.cs:53-66 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithSlash.cs:58-70 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (13–14 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:277 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:277-289 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:283-295 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:322-335 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs` as WHOLE FILES: this scan already matched 70 separate duplicated blocks between them, totalling at least 835 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:277` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (13–14 lines × 3) Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:101 — Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:101-113 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleCut.cs:103-116 | Content/LegendWeapon/OnikiriLegend/OniZanshinSlashs/OniZanshinSlash.cs:140-153 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13–14 lines × 3) Content/NPCs/BloomsandSerpents/BssHead.cs:691 — Content/NPCs/BloomsandSerpents/BssHead.cs:691-703 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/EowHeadAI.cs:549-562 | Content/NPCs/FestersandSerpents/FssHead.cs:628-640 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BloomsandSerpents/BssHead.cs:691` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Edited copy of a member (45 corresponding lines) · ×9
  • Edited copy of a member (45 corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1849 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1849-1893 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1714-1758 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (45 corresponding lines) Content/Items/Magic/Elysiums/Disciples/BaseDisciple.cs:244 — Content/Items/Magic/Elysiums/Disciples/BaseDisciple.cs:244-288 | Content/Items/Magic/Elysiums/Revelations/ApocalypseHorseman.cs:151-201 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (45 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:862 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:862-906 | Content/NPCs/SeaShrimp/Kinematics/ShrimpSkeleton.cs:236-283 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (45 corresponding lines) Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkRitualWispProj.cs:118 — Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkRitualWispProj.cs:118-162 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkScytheBladeProj.cs:124-176 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (45 corresponding lines) Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:277 — Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:277-321 | Content/LegendWeapon/OnikiriLegend/OniZanshinSlashs/OniZanshinSlash.cs:364-409 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (45 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:558 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:558-604 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:617-661 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (45 corresponding lines) Content/LegendWeapon/OnikiriLegend/UI/OniRope.cs:38 — Content/LegendWeapon/OnikiriLegend/UI/OniRope.cs:38-87 | Content/NPCs/SeaShrimp/Kinematics/ShrimpVerletStrand.cs:39-83 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (45 corresponding lines) Content/Scenarios/Helen/Gifts/HelenGiftNarrativeTracker.cs:77 — Content/Scenarios/Helen/Gifts/HelenGiftNarrativeTracker.cs:77-122 | Content/Scenarios/Shepel/Gifts/ShepelBossGiftNarrative.cs:88-132 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (45 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishBone.cs:285 — Content/LegendWeapon/HalibutLegend/FishSkills/FishBone.cs:285-333 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBone.cs:336-380 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (37 corresponding lines) · ×9
  • Edited copy of a member (37 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishAmanita.cs:415 — Content/LegendWeapon/HalibutLegend/FishSkills/FishAmanita.cs:415-451 | Content/LegendWeapon/HalibutLegend/FishSkills/FishAmanita.cs:839-877 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (37 corresponding lines) Content/NPCs/BloomsandSerpents/BssHead.cs:541 — Content/NPCs/BloomsandSerpents/BssHead.cs:541-580 | Content/NPCs/FestersandSerpents/FssHead.cs:487-523 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (37 corresponding lines) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:134 — Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:134-170 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowBurrowAmbushState.cs:121-159 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (37 corresponding lines) Content/Scenarios/Dungeonworld/Gen/Passes/GuideTrailPass.cs:57 — Content/Scenarios/Dungeonworld/Gen/Passes/GuideTrailPass.cs:57-93 | Content/Scenarios/Dungeonworld/Gen/Passes/GuideTrailPass.cs:182-225 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (37 corresponding lines) Content/Scenarios/Kiame/Gen/Passes/KiameTerrainPass.cs:19 — Content/Scenarios/Kiame/Gen/Passes/KiameTerrainPass.cs:19-55 | Content/Scenarios/Kiyume/Gen/Passes/KiyumeTerrainPass.cs:20-63 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (37 corresponding lines) Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBanish.Net.cs:96 — Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBanish.Net.cs:96-134 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.Net.cs:121-157 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (37 corresponding lines) Content/NPCs/BloomsandSerpents/States/BssPillarVaultState.cs:63 — Content/NPCs/BloomsandSerpents/States/BssPillarVaultState.cs:63-105 | Content/NPCs/BloomsandSerpents/States/BssVortexDashState.cs:65-101 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (37 corresponding lines) Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBanish.Net.cs:240 — Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBanish.Net.cs:240-291 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBossExecution.Net.cs:180-216 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (37 corresponding lines) Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomain.cs:169 — Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomain.cs:169-206 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomain.cs:210-246 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 24+ corresponding lines) · ×9
  • Edited copies of one member (3 members, 24+ corresponding lines) Content/Narrative/Presentation/Skins/StarStream/StarStreamPanelDraw.cs:144 — Content/Narrative/Presentation/Skins/StarStream/StarStreamPanelDraw.cs:144-169 | Content/Narrative/Presentation/Skins/Sulfsea/SulfseaPanelDraw.cs:58-81 | Content/Narrative/Presentation/Skins/Tzeentch/TzeentchPanelDraw.cs:57-80 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 24+ corresponding lines) Content/Items/BloomArsenal.cs:111 — Content/Items/BloomArsenal.cs:111-137 | Content/Items/Magic/BloomTomes/BloomTome.cs:120-146 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Projectiles/BrutalBeeStinger.cs:77-100 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 24+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerStrikeTelegraph.cs:44 — Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerStrikeTelegraph.cs:44-74 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronTelegraph.cs:48-71 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Projectiles/QueenBeeTelegraphLine.cs:46-69 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 24+ corresponding lines) Content/GameModes/BrutalMobs/FrostMoon/FrmMeleeNPC.cs:303 — Content/GameModes/BrutalMobs/FrostMoon/FrmMeleeNPC.cs:303-328 | Content/GameModes/BrutalMobs/FrostMoon/FrmSiegeNPC.cs:255-279 | Content/GameModes/BrutalMobs/FrostMoon/FrmSiegeNPC.cs:346-369 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 24+ corresponding lines) Content/Scenarios/OldDuke/Campsites/CampsiteLocationFinder.cs:215 — Content/Scenarios/OldDuke/Campsites/CampsiteLocationFinder.cs:215-239 | Content/Scenarios/OldDuke/Campsites/CampsiteLocationFinder.cs:316-339 | Content/Scenarios/OldDuke/Campsites/CampsiteLocationFinder.cs:410-438 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 24+ corresponding lines) Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberExecutionBoltProj.cs:166 — Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberExecutionBoltProj.cs:166-189 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberGlitchBoltProj.cs:55-78 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberRiftSlashProj.cs:58-83 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 24+ corresponding lines) Content/Items/Tools/EncyclopediaofOceanicKnowledge.cs:231 — Content/Items/Tools/EncyclopediaofOceanicKnowledge.cs:231-263 | Content/Items/Tools/TheForgottenTome.cs:192-218 | Content/Items/Tools/TheForgottenTome.cs:250-273 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 24+ corresponding lines) Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsDeadlySphereSawProj.cs:56 — Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsDeadlySphereSawProj.cs:56-81 | Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsRavenOmenProj.cs:57-80 | Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsXenoOrbitalProj.cs:63-87 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 24+ corresponding lines) Content/Scenarios/Dungeonworld/Gen/Prefabs/Prefab.cs:57 — Content/Scenarios/Dungeonworld/Gen/Prefabs/Prefab.cs:57-81 | Content/Scenarios/Kiyume/Gen/Prefabs/KiyumePrefab.cs:32-55 | Content/Scenarios/OldNet/Gen/Prefabs/OldNetPrefab.cs:32-55 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 16+ corresponding lines) · ×9
  • Edited copies of one member (4 members, 16+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:793 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:793-808 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:809-824 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:755-770 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:787-802 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 16+ corresponding lines) Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs:143 — Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs:143-159 | Content/Scenarios/Helen/Quest/OceanTrackerWidgetStyle.cs:229-244 | Content/Scenarios/OldDuke/Quest/SulfseaTrackerWidgetStyle.cs:159-179 | Content/Scenarios/SupCal/Quest/BrimstoneTrackerWidgetStyle.cs:157-176 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 16+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:646 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:646-661 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:652-668 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:608-623 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:641-656 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 16+ corresponding lines) Content/GameModes/GodSmith/Armors/Reset/GsOreArmorsHardmode.cs:272 — Content/GameModes/GodSmith/Armors/Reset/GsOreArmorsHardmode.cs:272-289 | Content/GameModes/GodSmith/Armors/Reset/GsPillarArmors.cs:293-314 | Content/GameModes/GodSmith/Armors/Reset/GsShroomiteArmor.cs:147-163 | Content/GameModes/GodSmith/Armors/Reset/GsSpiderArmor.cs:74-89 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 16+ corresponding lines) Content/Items/Melee/CosmicCalamity.cs:36 — Content/Items/Melee/CosmicCalamity.cs:36-56 | Content/Items/Melee/DawnshatterAzures/DawnshatterAzure.cs:33-48 | Content/Items/Melee/StormGoddessSpears/AncientStormGoddessSpear.cs:31-50 | Content/Items/Melee/StormGoddessSpears/StormGoddessSpear.cs:34-53 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 16+ corresponding lines) Content/Items/Ranged/BloodshotBombs/BloodshotBomb.cs:43 — Content/Items/Ranged/BloodshotBombs/BloodshotBomb.cs:43-58 | Content/Items/Summon/BloomCallers/BloomCaller.cs:18-36 | Content/Items/Summon/Deepclaws/Deepclaw.cs:17-34 | Content/Items/Summon/EyekiteStaffs/EyekiteStaff.cs:13-30 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 16+ corresponding lines) Content/Items/Accessories/BrutalRelics/Skeletron/SoulbindingArmPlayer.cs:258 — Content/Items/Accessories/BrutalRelics/Skeletron/SoulbindingArmPlayer.cs:258-276 | Content/Items/Accessories/BrutalRelics/Skeletron/SoulbindingGhostHand.cs:266-282 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:545-560 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuYinFX.cs:125-140 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 16+ corresponding lines) Content/NPCs/BloomsandSerpents/BssBody.cs:73 — Content/NPCs/BloomsandSerpents/BssBody.cs:73-89 | Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Core/BrainMotion.cs:177-192 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/EowBodyAI.cs:73-88 | Content/NPCs/FestersandSerpents/FssBody.cs:71-87 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 16+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1057 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1057-1079 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1194-1216 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:950-965 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:1019-1034 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 6+ corresponding lines) · ×9
  • Edited copies of one member (4 members, 6+ corresponding lines) Content/Scenarios/Shenyo/Gifts/ShenyoMoonLordGift.cs:26 — Content/Scenarios/Shenyo/Gifts/ShenyoMoonLordGift.cs:26-31 | Content/Scenarios/Shenyo/Gifts/ShenyoPlanteraGift.cs:26-31 | Content/Scenarios/Shenyo/Gifts/ShenyoPolterghastGift.cs:26-31 | Content/Scenarios/Shenyo/Gifts/ShenyoSkeletronGift.cs:26-31 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 6+ corresponding lines) Content/GameModes/GodSmith/Weapons/SummonWhips/Schemes/GsCoolWhip.cs:31 — Content/GameModes/GodSmith/Weapons/SummonWhips/Schemes/GsCoolWhip.cs:31-36 | Content/GameModes/GodSmith/Weapons/SummonWhips/Schemes/GsDurendal.cs:43-50 | Content/GameModes/GodSmith/Weapons/SummonWhips/Schemes/GsMorningStar.cs:42-51 | Content/GameModes/GodSmith/Weapons/SummonWhips/Schemes/GsSpinalTap.cs:31-38 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 6+ corresponding lines) Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFistProj.cs:356 — Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFistProj.cs:356-362 | Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFistProj.cs:508-513 | Content/Items/Accessories/BrutalRelics/Twins/TwinPupilShots.cs:287-294 | Content/NPCs/BloomsandSerpents/Projectiles/BssPincerSnapProj.cs:63-69 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 6+ corresponding lines) Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineTP.cs:426 — Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineTP.cs:426-432 | Content/Industrials/ElectricPowers/Crushers/CrusherTP.cs:36-41 | Content/Industrials/ElectricPowers/Incinerators/IncineratorData.cs:30-36 | Content/Industrials/ElectricPowers/Recyclers/RecyclerTP.cs:39-44 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 6+ corresponding lines) Content/HackTimes/Protocols/CompensationProtocol.cs:50 — Content/HackTimes/Protocols/CompensationProtocol.cs:50-56 | Content/HackTimes/Protocols/PayloadRewrite.cs:33-39 | Content/HackTimes/Protocols/PhaseDesync.cs:30-35 | Content/HackTimes/Protocols/ShellRequisition.cs:43-48 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 6+ corresponding lines) Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineTP.cs:434 — Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineTP.cs:434-440 | Content/Industrials/ElectricPowers/Crushers/CrusherTP.cs:43-48 | Content/Industrials/ElectricPowers/Incinerators/IncineratorData.cs:38-44 | Content/Industrials/ElectricPowers/Recyclers/RecyclerTP.cs:46-51 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 6+ corresponding lines) Content/Items/Melee/Shatterfangs/ShatterfangPRT.cs:22 — Content/Items/Melee/Shatterfangs/ShatterfangPRT.cs:22-28 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDirtParticles.cs:165-172 | Content/LegendWeapon/HalibutLegend/FishSkills/FishMudVFX.cs:138-144 | Content/PRTTypes/PRT_MarbleChip.cs:16-21 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 6+ corresponding lines) Content/Scenarios/Draedon/Defeats/ExoMechSecondDefeat.cs:36 — Content/Scenarios/Draedon/Defeats/ExoMechSecondDefeat.cs:36-41 | Content/Scenarios/Draedon/Defeats/ExoMechThirdDefeat.cs:33-38 | Content/Scenarios/Draedon/ExoMechdusaSums/ExoMechEndingDialogue.cs:59-64 | Content/Scenarios/Draedon/Quest/DeploySignaltowers/QuestCompleteScenario.cs:44-52 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 6+ corresponding lines) Content/Items/Melee/Budcrowns/Budcrown.cs:262 — Content/Items/Melee/Budcrowns/Budcrown.cs:262-267 | Content/Items/Summon/BloomCallers/BloomCallerSprout.cs:336-341 | Content/Items/Summon/Deepclaws/DeepclawLobster.cs:379-384 | Content/Items/Summon/EyekiteStaffs/EyekiteMinion.cs:408-413 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 4+ corresponding lines) · ×9
  • Edited copies of one member (3 members, 4+ corresponding lines) Content/Narrative/Presentation/Skins/Brimstone/BrimstonePanelState.cs:111 — Content/Narrative/Presentation/Skins/Brimstone/BrimstonePanelState.cs:111-114 | Content/Narrative/Presentation/Skins/Draedon/DraedonPanelDraw.cs:163-166 | Content/Narrative/Presentation/Skins/StarStream/StarStreamPanelDraw.cs:104-107 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 4+ corresponding lines) Content/Items/Melee/NeutronGlaive.cs:732 — Content/Items/Melee/NeutronGlaive.cs:732-735 | Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:883-886 | Content/Items/Modifys/RBloodButcherer.cs:820-823 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 4+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordArcRayProj.cs:136 — Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordArcRayProj.cs:136-139 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordEyeLinkProj.cs:126-132 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordScanRayProj.cs:114-120 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 4+ corresponding lines) Content/GameModes/GodSmith/Armors/Reset/GsCactusArmor.cs:65 — Content/GameModes/GodSmith/Armors/Reset/GsCactusArmor.cs:65-68 | Content/GameModes/GodSmith/Weapons/Guns/GsShotgun.cs:115-119 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsIceSickle.cs:231-235 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 4+ corresponding lines) Content/GameModes/GodSmith/Armors/Reset/GsBeetleArmors.cs:212 — Content/GameModes/GodSmith/Armors/Reset/GsBeetleArmors.cs:212-215 | Content/GameModes/GodSmith/Armors/Reset/GsNecroArmor.cs:78-81 | Content/GameModes/GodSmith/Armors/Reset/GsTurtleArmor.cs:67-70 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 4+ corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Barrel/CoralReefBarrelModule.cs:193 — Content/LegendWeapon/SHPCLegend/Modules/Barrel/CoralReefBarrelModule.cs:193-197 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/HiveBarrelModule.cs:150-154 | Content/LegendWeapon/SHPCLegend/Modules/Power/CapacitorBankModule.cs:604-607 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 4+ corresponding lines) Content/Items/Accessories/EmblemOfDread.cs:30 — Content/Items/Accessories/EmblemOfDread.cs:30-33 | Content/Items/Accessories/EyeOfSingularity.cs:26-29 | Content/Items/Melee/DawnshatterAzures/DawnshatterAzure.cs:27-31 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 4+ corresponding lines) Content/Items/Melee/Arbiters/Arbiter.cs:54 — Content/Items/Melee/Arbiters/Arbiter.cs:54-57 | Content/Items/Melee/Cloudwalking.cs:54-57 | Content/Items/Stones/Marbles/MarbleClub.cs:49-52 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 4+ corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSlashRenderer.cs:90 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSlashRenderer.cs:90-93 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepRenderer.cs:95-98 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlashRenderer.cs:92-95 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (13 lines × 4) · ×9
  • Duplicated block (13 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1026 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1026-1038 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaMinionDrownFX.cs:464-476 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaPlayerDrownFX.cs:500-512 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaScourgeFX.cs:761-773 — 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 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1026` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:394 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:394-406 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:387-399 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:437-449 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:465-477 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (13 lines × 4) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:452 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:452-464 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs:492-504 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:369-381 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:450-462 — before extracting anything, compare `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs` and `Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 226 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:452` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 4) Content/Items/Melee/DestroyersBlade.cs:102 — Content/Items/Melee/DestroyersBlade.cs:102-114 | Content/Items/Melee/DragonsScaleGreatsword.cs:118-130 | Content/Items/Melee/EnergySword.cs:129-141 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:137-149 — before extracting anything, compare `Content/Items/Melee/DestroyersBlade.cs` and `Content/Items/Melee/DragonsScaleGreatsword.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 419 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 (13 lines × 4) Content/Items/Melee/OniMachete.cs:372 — Content/Items/Melee/OniMachete.cs:372-384 | Content/LegendWeapon/HalibutLegend/FishSkills/FishTunabeardVFX.cs:167-179 | Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniKamuiFlowRenderer.cs:39-51 | Content/LegendWeapon/OnikiriLegend/OniSakuraFlights/OniSakuraFlowRenderer.cs:53-65 — before extracting anything, compare `Content/LegendWeapon/HalibutLegend/FishSkills/FishTunabeardVFX.cs` and `Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniKamuiFlowRenderer.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 112 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 4) Content/GameModes/BrutalMobs/FrostLegion/FrostLegionNPC.cs:346 — Content/GameModes/BrutalMobs/FrostLegion/FrostLegionNPC.cs:346-358 | Content/GameModes/BrutalMobs/Graveyard/GraveyardBrutalNPC.cs:279-291 | Content/GameModes/BrutalMobs/Pirates/PirateCrewNPC.cs:158-170 | Content/GameModes/BrutalMobs/PumpkinMoon/PumpkinMoonNPC.cs:808-820 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/BrutalMobs/Pirates/PirateCrewNPC.cs:154` calls `TryStart` and `Content/GameModes/BrutalMobs/PumpkinMoon/PumpkinMoonNPC.cs:807` 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 (13 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:960 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:960-972 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:1018-1030 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:921-933 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:954-966 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs` as WHOLE FILES: this scan already matched 75 separate duplicated blocks between them, totalling at least 912 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:960` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:267 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:267-279 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:1049-1061 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1280-1292 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1420-1432 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:267` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuLinFX.cs:13 — Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuLinFX.cs:13-25 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuPoFX.cs:16-28 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuWenFX.cs:15-27 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuZhaFX.cs:16-28 — 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 4 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (11 lines × 4) · ×9
  • Duplicated block (11 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:749 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:749-759 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:765-775 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:711-721 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:743-753 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs` as WHOLE FILES: this scan already matched 75 separate duplicated blocks between them, totalling at least 912 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:749` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 4) Content/GameModes/GodSmith/Weapons/Broadswords/GsBeamSword.cs:119 — Content/GameModes/GodSmith/Weapons/Broadswords/GsBeamSword.cs:119-129 | Content/GameModes/GodSmith/Weapons/Broadswords/GsChlorophyteClaymore.cs:113-123 | Content/GameModes/GodSmith/Weapons/Broadswords/GsInfluxWaver.cs:151-161 | Content/GameModes/GodSmith/Weapons/Broadswords/GsPhaseBladeShared.cs:267-277 — 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 4 call sites, so a change lands once.
  • Duplicated block (11 lines × 4) Content/GameModes/GodSmith/Weapons/Broadswords/GsChristmasTreeSword.cs:130 — Content/GameModes/GodSmith/Weapons/Broadswords/GsChristmasTreeSword.cs:130-140 | Content/GameModes/GodSmith/Weapons/Broadswords/GsEnchantedSword.cs:86-96 | Content/GameModes/GodSmith/Weapons/Broadswords/GsMeowmere.cs:273-283 | Content/GameModes/GodSmith/Weapons/Broadswords/GsPiercingStarlight.cs:273-283 — 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 4 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/GodSmith/Weapons/Broadswords/GsChristmasTreeSword.cs:126` calls `SetStaticDefaults` and `Content/GameModes/GodSmith/Weapons/Broadswords/GsPiercingStarlight.cs:271` 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) Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:198 — Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:198-209 | Content/Items/Melee/DestroyersBlade.cs:224-234 | Content/Items/Melee/DragonsScaleGreatsword.cs:232-242 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:260-270 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:198` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:197` calls `Lerp`, `SmoothStep01` and `Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:259` does not — after which the two agree again for 4 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) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:175 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:175-185 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:175-185 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:186-196 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:173-183 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs` as WHOLE FILES: this scan already matched 75 separate duplicated blocks between them, totalling at least 912 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 4) Content/Scenarios/Dungeonworld/Gen/TileBrush.cs:57 — Content/Scenarios/Dungeonworld/Gen/TileBrush.cs:57-67 | Content/Scenarios/Kiame/Gen/KiameTileBrush.cs:55-65 | Content/Scenarios/Kiyume/Gen/KiyumeTileBrush.cs:70-80 | Content/Scenarios/OldNet/Gen/OldNetTileBrush.cs:43-53 — before extracting anything, compare `Content/Scenarios/Kiame/Gen/KiameTileBrush.cs` and `Content/Scenarios/Kiyume/Gen/KiyumeTileBrush.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/Gen/TileBrush.cs:57` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Scenarios/Dungeonworld/Gen/TileBrush.cs:53` calls `Touch` and `Content/Scenarios/OldNet/Gen/OldNetTileBrush.cs:39` does not — after which the two agree again for 3 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) Content/GameModes/BrutalMobs/Legion/Projectiles/LegionVolleyArrow.cs:30 — Content/GameModes/BrutalMobs/Legion/Projectiles/LegionVolleyArrow.cs:30-40 | Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilCursedBeadProj.cs:36-46 | Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilPrismFlashProj.cs:30-40 | Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornJavelinProj.cs:36-46 — before extracting anything, compare `Content/GameModes/BrutalMobs/Legion/Projectiles/LegionVolleyArrow.cs` and `Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilCursedBeadProj.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilCursedBeadProj.cs:49` calls `CanDamage` and `Content/GameModes/BrutalMobs/Legion/Projectiles/LegionVolleyArrow.cs:42` 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) Content/Items/Ranged/BarrenBow.cs:114 — Content/Items/Ranged/BarrenBow.cs:114-124 | Content/Items/Ranged/NeutronBows/NeutronBow.cs:121-131 | Content/Items/Ranged/Thornstrings/ThornstringHeld.cs:54-64 | Content/Items/Ranged/Undertows/UndertowHeld.cs:57-67 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (11 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:203 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:203-213 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:206-216 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:219-229 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:252-262 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs` as WHOLE FILES: this scan already matched 70 separate duplicated blocks between them, totalling at least 835 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (11 lines × 5) · ×9
  • Duplicated block (11 lines × 5) Content/GameModes/GodSmith/Weapons/Broadswords/GsDD2SquireBetsySword.cs:150 — Content/GameModes/GodSmith/Weapons/Broadswords/GsDD2SquireBetsySword.cs:150-160 | Content/GameModes/GodSmith/Weapons/Broadswords/GsDD2SquireDemonSword.cs:174-184 | Content/GameModes/GodSmith/Weapons/Broadswords/GsInfluxWaver.cs:298-308 | Content/GameModes/GodSmith/Weapons/Broadswords/GsStarWrath.cs:258-268 | Content/GameModes/GodSmith/Weapons/Broadswords/GsStarfury.cs:117-127 — 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 5 call sites, so a change lands once.
  • Duplicated block (11 lines × 5) Content/GameModes/GodSmith/Weapons/Broadswords/GsPearlwoodSword.cs:135 — Content/GameModes/GodSmith/Weapons/Broadswords/GsPearlwoodSword.cs:135-145 | Content/GameModes/GodSmith/Weapons/Spears/GsDarkLance.cs:122-132 | Content/GameModes/GodSmith/Weapons/Spears/GsNorthPole.cs:165-175 | Content/GameModes/GodSmith/Weapons/Spears/GsTheRottedFork.cs:105-115 | Content/GameModes/GodSmith/Weapons/Spears/GsTrident.cs:104-114 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/GodSmith/Weapons/Spears/GsNorthPole.cs:162` calls `ToRotationVector2` and `Content/GameModes/GodSmith/Weapons/Spears/GsDarkLance.cs:120` 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 × 5) Content/Items/Melee/OniMacheteHands.cs:1343 — Content/Items/Melee/OniMacheteHands.cs:1343-1353 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCrimsonTiger.cs:794-804 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCursed.cs:458-468 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDemonicHell.cs:641-651 | Content/LegendWeapon/HalibutLegend/FishSkills/FishFallenStarVFX.cs:207-217 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/OniMacheteHands.cs:1343` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:124 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:124-134 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs:138-148 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:118-128 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeHeatRay.cs:90-101 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeSkullBeamProj.cs:88-99 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 161 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:124` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (11 lines × 5) Content/NPCs/BloomsandSerpents/BssVfx.cs:26 — Content/NPCs/BloomsandSerpents/BssVfx.cs:26-36 | Content/NPCs/FestersandSerpents/FssVfx.cs:39-49 | Content/NPCs/ScrapCommanders/Core/IScrapState.cs:148-158 | Content/NPCs/SeaShrimp/Core/ISeaShrimpState.cs:144-154 | Content/NPCs/SeaShrimp/Kinematics/ShrimpTerrain.cs:67-77 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/NPCs/SeaShrimp/Kinematics/ShrimpTerrain.cs:80` calls `WetAt`, `WetCollision`, `Vector2` and `Content/NPCs/ScrapCommanders/Core/IScrapState.cs:161` 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 × 5) Content/GameModes/BrutalMobs/Ambience/Aetherglim/Projectiles/AetherglimGravityBubbleProj.cs:46 — Content/GameModes/BrutalMobs/Ambience/Aetherglim/Projectiles/AetherglimGravityBubbleProj.cs:46-56 | Content/GameModes/BrutalMobs/Ambience/Brinefume/Projectiles/BrinefumeHazeTideProj.cs:47-57 | Content/GameModes/BrutalMobs/Ambience/Cindercrag/Projectiles/CindercragWailWaveProj.cs:39-49 | Content/GameModes/BrutalMobs/Ambience/Frostveil/Projectiles/FrostveilGaleWallProj.cs:71-81 | Content/GameModes/BrutalMobs/Ambience/Sporeshine/Projectiles/SporeshineSporeLobProj.cs:34-44 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.
  • Duplicated block (11 lines × 5) Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipBoneProj.cs:33 — Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipBoneProj.cs:33-43 | Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipDurendalProj.cs:32-42 | Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipFrostBloomProj.cs:27-37 | Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipMorningStarProj.cs:33-43 | Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipReapProj.cs:27-37 — 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 5 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipBoneProj.cs:31` calls `Clamp` and `Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipFrostBloomProj.cs:25` does not — after which the two agree again for 4 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 × 5) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Projectiles/BrainBloodShard.cs:29 — Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Projectiles/BrainBloodShard.cs:29-39 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerBolt.cs:25-35 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs:31-41 | Content/NPCs/FestersandSerpents/Projectiles/FssCascadeDrop.cs:27-37 | Content/NPCs/FestersandSerpents/Projectiles/FssIchorGlob.cs:31-41 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.
  • Duplicated block (11 lines × 5) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Projectiles/BrainMirrorImage.cs:58 — Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Projectiles/BrainMirrorImage.cs:58-68 | Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Projectiles/BrainTeleportRift.cs:30-40 | Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Projectiles/BrainVeinTelegraph.cs:27-37 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowHuskMine.cs:32-42 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowLungeOmen.cs:34-44 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.
D4 · Code Duplication · Duplicated block (10–11 lines × 4) · ×9
  • Duplicated block (10–11 lines × 4) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterTile.cs:35 — Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterTile.cs:35-44 | Content/Industrials/ElectricPowers/Crushers/CrusherTile.cs:33-42 | Content/Industrials/ElectricPowers/Incinerators/IncineratorTile.cs:29-39 | Content/Industrials/ElectricPowers/Recyclers/RecyclerTile.cs:30-39 — before extracting anything, compare `Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterTile.cs` and `Content/Industrials/ElectricPowers/Crushers/CrusherTile.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 74 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterTile.cs:35` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10–11 lines × 4) Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:351 — Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:351-360 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:377-387 | Content/Industrials/ElectricPowers/Recyclers/RecyclerUI.cs:350-359 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterUI.cs:361-370 — before extracting anything, compare `Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs` and `Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 303 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:351` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10–11 lines × 4) Content/Items/BloomArsenal.cs:192 — Content/Items/BloomArsenal.cs:192-201 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaShrimpWaterBolt.cs:98-108 | Content/NPCs/BloomsandSerpents/Projectiles/BssNeedleProj.cs:57-66 | Content/NPCs/BloomsandSerpents/Projectiles/BssSandGlob.cs:62-72 — before extracting anything, compare `Content/Items/BloomArsenal.cs` and `Content/NPCs/BloomsandSerpents/Projectiles/BssNeedleProj.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 98 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/BloomArsenal.cs:192` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (10–11 lines × 4) Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:270 — Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:270-280 | Content/Items/Melee/NeutronGlaive.cs:280-289 | Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:327-337 | Content/Items/Modifys/RBloodButcherer.cs:360-370 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:266` calls `UpdateBodyLean` and `Content/Items/Melee/NeutronGlaive.cs:276` 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 (10–11 lines × 4) Content/LegendWeapon/HalibutLegend/FishSkills/FishEaterofPlanktonVFX.cs:174 — Content/LegendWeapon/HalibutLegend/FishSkills/FishEaterofPlanktonVFX.cs:174-183 | Content/LegendWeapon/HalibutLegend/FishSkills/FishHungerVFX.cs:238-247 | Content/LegendWeapon/HalibutLegend/FishSkills/FishRockParticles.cs:170-180 | Content/LegendWeapon/HalibutLegend/FishSkills/FishRockParticles.cs:245-254 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishEaterofPlanktonVFX.cs:174` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (10–11 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1072 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1072-1081 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1409-1419 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:859-868 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1370-1379 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs` as WHOLE FILES: this scan already matched 68 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1072` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1422` calls `CurrentScanMode` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1084` does not — after which the two agree again for 4 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 (10–11 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:501 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:501-511 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:583-593 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:457-466 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:538-548 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs` as WHOLE FILES: this scan already matched 79 separate duplicated blocks between them, totalling at least 1151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (10–11 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:441 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:441-451 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:297-306 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:343-352 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:331-340 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 408 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:441` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (10–11 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuBao.cs:132 — Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuBao.cs:132-141 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuFei.cs:90-99 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuSha.cs:129-138 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuXiao.cs:76-86 — 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 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuBao.cs:132` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7 lines × 7) · ×9
  • Duplicated block (7 lines × 7) Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:265 — Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:265-271 | Content/Items/Accessories/BrutalRelics/QueenBee/SwarmVortexProj.cs:416-422 | Content/NPCs/BloomsandSerpents/Projectiles/BssDashOmen.cs:114-120 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerStrikeTelegraph.cs:103-109 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronGeyserProj.cs:148-154 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronTelegraph.cs:117-123 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Projectiles/QueenBeeTelegraphLine.cs:98-104 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronTelegraph.cs:114` calls `SetValue` and `Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:262` 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 × 7) Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuBao.cs:138 — Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuBao.cs:138-144 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuFei.cs:96-102 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuSha.cs:135-141 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuShu.cs:150-156 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuTing.cs:149-155 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuXia.cs:119-125 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuXiao.cs:83-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 7 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuBao.cs:138` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuShu.cs:147` calls `WindowPump` and `Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuBao.cs:135` 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 × 7) Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclManFlyFlaskProj.cs:163 — Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclManFlyFlaskProj.cs:163-170 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionClownBomb.cs:207-213 | Content/Items/Melee/DestroyersBladeEXs/DestroyerHeadMissile.cs:154-160 | Content/Items/Melee/DestroyersBladeEXs/DestroyerShadowBolt.cs:233-239 | Content/Items/Summon/BloomCallers/BloomCallerSprout.cs:380-386 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistSeekerStar.cs:182-188 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordBoltProj.cs:121-127 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclManFlyFlaskProj.cs:163` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (7 lines × 7) Content/Industrials/ElectricPowers/Apiaries/ApiaryTP.cs:656 — Content/Industrials/ElectricPowers/Apiaries/ApiaryTP.cs:656-662 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherTP.cs:637-643 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerTP.cs:712-718 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:798-804 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconTP.cs:332-338 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatTP.cs:617-623 | Content/Industrials/ElectricPowers/Throwers/ThrowerTP.cs:427-433 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Apiaries/ApiaryTP.cs:656` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Industrials/ElectricPowers/Throwers/ThrowerTP.cs:424` calls `Clear` and `Content/Industrials/ElectricPowers/Apiaries/ApiaryTP.cs:653` 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 × 7) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:57 — Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:57-65 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs:95-103 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainRender.cs:206-212 | Content/Scenarios/Kiame/KiameWakeResetRender.cs:93-101 | Content/Scenarios/Kiame/Overlay/OniRainDescentRender.cs:79-87 | Content/Scenarios/Kiame/Overlay/OniUmbrellaPuddleRender.cs:69-77 | Content/Scenarios/Kiame/Water/KiameWaterRender.cs:118-126 — before extracting anything, compare `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs` and `Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:54` calls `GetRenderTargets` and `Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs:92` 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 × 7) Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs:132 — Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs:132-138 | Content/LegendWeapon/KikasaLegend/TrialQuests/KikasaTrackerWidgetStyle.cs:106-112 | Content/LegendWeapon/OnikiriLegend/TrialQuests/OnikiriTrackerWidgetStyle.cs:92-98 | Content/LegendWeapon/SHPCLegend/TrialQuests/SHPCTrackerWidgetStyle.cs:122-129 | Content/Scenarios/Draedon/Quest/DraedonTrackerWidgetStyle.cs:153-160 | Content/Scenarios/OldDuke/Quest/SulfseaTrackerWidgetStyle.cs:148-154 | Content/Scenarios/SupCal/Quest/BrimstoneTrackerWidgetStyle.cs:146-152 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs:132` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 7) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1250 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1250-1256 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1429-1435 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:874-880 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:1199-1205 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1580-1586 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:1002-1008 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1577-1583 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 598 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1250` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 7) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:971 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:971-977 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:1142-1148 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1358-1364 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:969-975 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:1091-1097 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:1017-1024 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:1079-1085 — there are 7 copies across 6 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 7 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:971` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (7 lines × 7) Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolBossRoomWatcher.cs:232 — Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolBossRoomWatcher.cs:232-238 | Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolBossRoomWatcher.cs:259-265 | Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolBossRoomWatcher.cs:284-290 | Content/Scenarios/Dungeonworld/Gen/LayerTint.cs:38-44 | Content/Scenarios/Dungeonworld/Gen/LayerTint.cs:66-72 | Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Palette.cs:136-142 | Content/Scenarios/Dungeonworld/Gen/Zones/SlagVentBelt.cs:250-256 — there are 7 copies across 4 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 7 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolBossRoomWatcher.cs:232` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (7–8 lines × 3) · ×9
  • Duplicated block (7–8 lines × 3) Content/GameModes/GodSmith/Prefixes/Magic/GodSmithMythicEchoEndow.cs:152 — Content/GameModes/GodSmith/Prefixes/Magic/GodSmithMythicEchoEndow.cs:152-158 | Content/GameModes/GodSmith/Prefixes/Offense/GodSmithOverkillEndow.cs:112-119 | Content/GameModes/GodSmith/Prefixes/Ranged/GodSmithRicochetEndow.cs:112-118 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Prefixes/Magic/GodSmithMythicEchoEndow.cs:152` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7–8 lines × 3) Content/Items/Accessories/BrutalRelics/QueenBee/SwarmVortexProj.cs:376 — Content/Items/Accessories/BrutalRelics/QueenBee/SwarmVortexProj.cs:376-382 | Content/Items/Magic/Elysiums/Revelations/RevelationDomain.cs:130-137 | Content/Items/Magic/Elysiums/Serpents/SnakeConversionWave.cs:201-208 — before extracting anything, compare `Content/Items/Magic/Elysiums/Revelations/RevelationDomain.cs` and `Content/Items/Magic/Elysiums/Serpents/SnakeConversionWave.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (7–8 lines × 3) Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:190 — Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:190-196 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpJetBeam.cs:215-221 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpWaveCrest.cs:199-206 — before extracting anything, compare `Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs` and `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpJetBeam.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:190` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (7–8 lines × 3) Content/Items/Magic/Elysiums/ElysiumHeld.cs:290 — Content/Items/Magic/Elysiums/ElysiumHeld.cs:290-296 | Content/Items/Magic/Elysiums/ElysiumHeld.cs:322-328 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreezeGlobalNPC.cs:99-106 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreezeGlobalNPC.cs:99` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (7–8 lines × 3) Content/Items/Melee/NeutronGlaive.cs:599 — Content/Items/Melee/NeutronGlaive.cs:599-606 | Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:736-742 | Content/Items/Modifys/RBloodButcherer.cs:721-727 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:736` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:736` calls `Pow` and `Content/Items/Melee/NeutronGlaive.cs:599` does not — after which the two agree again for 5 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–8 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:261 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:261-268 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:280-286 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:470-476 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:261` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:286` calls `DrawUmbrella` and `Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:476` does not — after which the two agree again for 5 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–8 lines × 3) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendParticles.cs:840 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendParticles.cs:840-846 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleParticles.cs:59-65 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Rendering/FishronPRT.cs:47-54 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendParticles.cs:840` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (7–8 lines × 3) Content/LegendWeapon/SHPCLegend/Modules/Frame/MultiCellFrameModule.cs:381 — Content/LegendWeapon/SHPCLegend/Modules/Frame/MultiCellFrameModule.cs:381-387 | Content/LegendWeapon/SHPCLegend/Modules/Grip/EfficientGripModule.cs:545-551 | Content/LegendWeapon/SHPCLegend/Modules/Power/CapacitorBankModule.cs:542-549 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. 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 (7–8 lines × 3) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/PincerBindTether.cs:189 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/PincerBindTether.cs:189-196 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/TwinsTetherArc.cs:192-198 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeArcChainProj.cs:207-213 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/PincerBindTether.cs:189` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (6–7 lines × 3) · ×9
  • Duplicated block (6–7 lines × 3) Common/ShockRingDraw.cs:68 — Common/ShockRingDraw.cs:68-74 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteRingRender.cs:138-144 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistUmbraShade.cs:515-520 — before extracting anything, compare `Common/ShockRingDraw.cs` and `Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteRingRender.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (6–7 lines × 3) Content/Items/Accessories/BrutalRelics/EmpressOfLight/InterferenceBursts.cs:82 — Content/Items/Accessories/BrutalRelics/EmpressOfLight/InterferenceBursts.cs:82-88 | Content/Items/Accessories/BrutalRelics/EmpressOfLight/InterferenceBursts.cs:188-194 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Projectiles/EmpressBloomBurst.cs:79-84 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/EmpressOfLight/InterferenceBursts.cs:82` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6–7 lines × 3) Content/Items/Accessories/BrutalRelics/Twins/TwinPupilOrbiter.cs:530 — Content/Items/Accessories/BrutalRelics/Twins/TwinPupilOrbiter.cs:530-535 | Content/Items/Accessories/BrutalRelics/Twins/TwinPupilShots.cs:339-345 | Content/Items/Accessories/BrutalRelics/Twins/TwinPupilTetherBeam.cs:222-228 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/Twins/TwinPupilOrbiter.cs:530` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6–7 lines × 3) Content/Items/Magic/Elysiums/Disciples/BaseDisciple.cs:277 — Content/Items/Magic/Elysiums/Disciples/BaseDisciple.cs:277-283 | Content/NPCs/TBUGs/TBUGRiftPortalProj.cs:374-379 | Content/NPCs/Victors/VictorRiftPortalProj.cs:563-568 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. 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 (6–7 lines × 3) Content/Items/Summon/BloomCallers/BloomCallerSprout.cs:153 — Content/Items/Summon/BloomCallers/BloomCallerSprout.cs:153-159 | Content/Items/Summon/Deepclaws/DeepclawLobster.cs:172-177 | Content/Items/Summon/EyekiteStaffs/EyekiteMinion.cs:158-163 — before extracting anything, compare `Content/Items/Summon/BloomCallers/BloomCallerSprout.cs` and `Content/Items/Summon/Deepclaws/DeepclawLobster.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Summon/BloomCallers/BloomCallerSprout.cs:153` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (6–7 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:410 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:410-415 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:361-367 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:456-462 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:410` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (6–7 lines × 3) Content/NPCs/BloomsandSerpents/Core/BssStateContext.cs:303 — Content/NPCs/BloomsandSerpents/Core/BssStateContext.cs:303-308 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Core/EowStateContext.cs:106-112 | Content/NPCs/FestersandSerpents/Core/FssStateContext.cs:273-278 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BloomsandSerpents/Core/BssStateContext.cs:303` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6–7 lines × 3) Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:797 — Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:797-803 | Content/QuestLogs/Styles/ForestQuestLogStyle.cs:546-551 | Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:732-738 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:797` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6–7 lines × 3) Content/Items/Ranged/TiroFinales/FinaleMagicBolt.cs:78 — Content/Items/Ranged/TiroFinales/FinaleMagicBolt.cs:78-84 | Content/Items/Ranged/TiroFinales/FinaleMusketRound.cs:81-88 | Content/Items/Ranged/TiroFinales/TiroFinaleBlast.cs:106-111 — before extracting anything, compare `Content/Items/Ranged/TiroFinales/FinaleMagicBolt.cs` and `Content/Items/Ranged/TiroFinales/FinaleMusketRound.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 81 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Ranged/TiroFinales/FinaleMagicBolt.cs:78` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Edited copy of a member (54 corresponding lines) · ×8
  • Edited copy of a member (54 corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1793 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1793-1846 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1658-1711 — These two members are one piece of code written twice and then edited apart: 54 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (54 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaHandRig.cs:136 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaHandRig.cs:136-189 | Content/Wraiths/Projectiles/GhostHandRig.cs:140-197 — These two members are one piece of code written twice and then edited apart: 54 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (54 corresponding lines) Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilSurgeColumnProj.cs:189 — Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilSurgeColumnProj.cs:189-242 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandGeyserProj.cs:171-228 — These two members are one piece of code written twice and then edited apart: 54 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (54 corresponding lines) Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:143 — Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:143-196 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpJetBeam.cs:164-221 — These two members are one piece of code written twice and then edited apart: 54 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (54 corresponding lines) Content/Scenarios/SupCal/End/EternalBlazingNow/EbnBarsDisplay.cs:469 — Content/Scenarios/SupCal/End/EternalBlazingNow/EbnBarsDisplay.cs:469-522 | Content/Scenarios/SupCal/End/EternalBlazingNow/EbnBarsDisplay.cs:524-577 — These two members are one piece of code written twice and then edited apart: 54 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (54 corresponding lines) Content/GameModes/BrutalMobs/Legion/LegionNPC.cs:1205 — Content/GameModes/BrutalMobs/Legion/LegionNPC.cs:1205-1258 | Content/GameModes/BrutalMobs/Legion/LegionNPC.cs:1274-1327 — These two members are one piece of code written twice and then edited apart: 54 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (54 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:266 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:266-319 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:267-335 — These two members are one piece of code written twice and then edited apart: 54 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (54 corresponding lines) Content/NPCs/TBUGs/TBUG.cs:225 — Content/NPCs/TBUGs/TBUG.cs:225-281 | Content/NPCs/Victors/Victor.cs:314-367 — These two members are one piece of code written twice and then edited apart: 54 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (43 corresponding lines) · ×8
  • Edited copy of a member (43 corresponding lines) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsDeathState.cs:160 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsDeathState.cs:160-207 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/PrimeDeathState.cs:396-443 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (43 corresponding lines) Content/PRTTypes/PRT_KikasaBloodSpray.cs:128 — Content/PRTTypes/PRT_KikasaBloodSpray.cs:128-171 | Content/PRTTypes/PRT_KikasaInkSpray.cs:145-187 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (43 corresponding lines) Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordBlackHoleProj.cs:790 — Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordBlackHoleProj.cs:790-832 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordUltArms.cs:471-518 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (43 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishDemonicHell.cs:261 — Content/LegendWeapon/HalibutLegend/FishSkills/FishDemonicHell.cs:261-303 | Content/LegendWeapon/HalibutLegend/FishSkills/FishMud.cs:735-805 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (43 corresponding lines) Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordHandAI.cs:303 — Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordHandAI.cs:303-346 | Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordHandAI.cs:349-391 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (43 corresponding lines) Content/Wraiths/Abilities/CrimsonBrides/BrideHallSky.cs:139 — Content/Wraiths/Abilities/CrimsonBrides/BrideHallSky.cs:139-181 | Content/Wraiths/Abilities/GhostRains/GhostRainAmbience.cs:139-182 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (43 corresponding lines) Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:331 — Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:331-374 | Content/Items/Modifys/RTerraBlades/RTerraBladeHeld.cs:322-364 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (43 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishBat.cs:641 — Content/LegendWeapon/HalibutLegend/FishSkills/FishBat.cs:641-683 | Content/LegendWeapon/HalibutLegend/FishSkills/FishSwarm.cs:1026-1075 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (50 corresponding lines) · ×8
  • Edited copy of a member (50 corresponding lines) Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:97 — Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:97-149 | Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:62-111 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (50 corresponding lines) Content/Industrials/Generator/Biomass/BiomassGeneratorUI.cs:254 — Content/Industrials/Generator/Biomass/BiomassGeneratorUI.cs:254-303 | Content/Industrials/Generator/Thermal/ThermalGeneratorUI.cs:371-429 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (50 corresponding lines) Content/Items/Ranged/TiroFinales/FinaleMagicBolt.cs:93 — Content/Items/Ranged/TiroFinales/FinaleMagicBolt.cs:93-146 | Content/Items/Ranged/TiroFinales/FinaleMusketRound.cs:97-146 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (50 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrown.cs:260 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrown.cs:260-328 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaPlayerDrown.cs:309-358 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (50 corresponding lines) Content/Items/Melee/GeminisTribute.cs:449 — Content/Items/Melee/GeminisTribute.cs:449-514 | Content/Items/Melee/GeminisTribute.cs:695-744 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (50 corresponding lines) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerSoloRageState.cs:83 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerSoloRageState.cs:83-132 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismSoloRageState.cs:83-132 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (50 corresponding lines) Content/GameModes/BrutalMobs/Martians/MartiansNPC.cs:349 — Content/GameModes/BrutalMobs/Martians/MartiansNPC.cs:349-398 | Content/GameModes/BrutalMobs/Martians/MartiansNPC.cs:624-676 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (50 corresponding lines) Content/Industrials/ElectricPowers/Crushers/CrusherTP.cs:309 — Content/Industrials/ElectricPowers/Crushers/CrusherTP.cs:309-358 | Content/Industrials/ElectricPowers/Incinerators/IncineratorTP.cs:165-223 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (48 corresponding lines) · ×8
  • Edited copy of a member (48 corresponding lines) Content/Wraiths/Abilities/CrimsonBrides/BrideHallRenderer.cs:387 — Content/Wraiths/Abilities/CrimsonBrides/BrideHallRenderer.cs:387-437 | Content/Wraiths/Deaths/Performances/BrideSeizurePerformance.cs:362-409 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (48 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaCavitationOrb.cs:79 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaCavitationOrb.cs:79-126 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpCavitationBubble.cs:75-131 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (48 corresponding lines) Content/LegendWeapon/OnikiriLegend/OniZanshinSlashs/OniZanshinSlash.cs:625 — Content/LegendWeapon/OnikiriLegend/OniZanshinSlashs/OniZanshinSlash.cs:625-672 | Content/Scenarios/Himayo/ToriiShrines/ToriiShrineActor.cs:554-609 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (48 corresponding lines) Content/Items/Ranged/AnnihilatingUniverses/CosmicEddies.cs:125 — Content/Items/Ranged/AnnihilatingUniverses/CosmicEddies.cs:125-196 | Content/Items/Ranged/Starships/StarshipMicroGalaxy.cs:133-180 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (48 corresponding lines) Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkRootSpikeProj.cs:87 — Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkRootSpikeProj.cs:87-148 | Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilFinSurgeOmen.cs:87-134 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (48 corresponding lines) Content/Items/Accessories/BrutalRelics/Skeletron/SoulbindingGhostHand.cs:87 — Content/Items/Accessories/BrutalRelics/Skeletron/SoulbindingGhostHand.cs:87-145 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronGhostArmProj.cs:78-125 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (48 corresponding lines) Content/NPCs/ScrapCommanders/ScrapSiegeScreen.cs:55 — Content/NPCs/ScrapCommanders/ScrapSiegeScreen.cs:55-102 | Content/NPCs/SeaShrimp/Rendering/SeaShrimpAbyssScreen.cs:54-101 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (48 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishCursed.cs:25 — Content/LegendWeapon/HalibutLegend/FishSkills/FishCursed.cs:25-72 | Content/LegendWeapon/HalibutLegend/FishSkills/FishIchorn.cs:26-74 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (44 corresponding lines) · ×8
  • Edited copy of a member (44 corresponding lines) Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:80 — Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:80-133 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerIceSpikeProj.cs:77-120 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (44 corresponding lines) Content/Items/Magic/NeutronWands/NeutronPulsar.cs:459 — Content/Items/Magic/NeutronWands/NeutronPulsar.cs:459-506 | Content/Items/Magic/NeutronWands/NeutronStarquake.cs:168-211 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (44 corresponding lines) Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmAimLaneOmen.cs:128 — Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmAimLaneOmen.cs:128-171 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmStrafeLaneProj.cs:100-148 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (44 corresponding lines) Content/MainMenus/Himayo/HimayoMenuButtons.cs:139 — Content/MainMenus/Himayo/HimayoMenuButtons.cs:139-182 | Content/MainMenus/Shenyo/ShenyoMenuButtons.cs:141-184 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (44 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainDeco.cs:394 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainDeco.cs:394-456 | Content/Scenarios/Kiame/KiameAmbience.cs:126-169 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (44 corresponding lines) Content/Industrials/ElectricPowers/Crushers/CrusherTP.cs:424 — Content/Industrials/ElectricPowers/Crushers/CrusherTP.cs:424-467 | Content/Industrials/ElectricPowers/Incinerators/IncineratorTP.cs:312-355 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (44 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:497 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:497-542 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:474-517 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (44 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishHunger.cs:24 — Content/LegendWeapon/HalibutLegend/FishSkills/FishHunger.cs:24-72 | Content/LegendWeapon/HalibutLegend/FishSkills/FishPrincess.cs:28-71 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 21+ corresponding lines) · ×8
  • Edited copies of one member (3 members, 21+ corresponding lines) Content/GameModes/BrutalMobs/Pirates/PirateCrewNPC.cs:199 — Content/GameModes/BrutalMobs/Pirates/PirateCrewNPC.cs:199-221 | Content/GameModes/BrutalMobs/Pirates/PirateCrewNPC.cs:224-244 | Content/GameModes/BrutalMobs/Pirates/PirateCrewNPC.cs:247-274 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 21+ corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1718 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1718-1739 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1389-1409 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1583-1604 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 21+ corresponding lines) Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSystem.cs:150 — Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSystem.cs:150-172 | Content/Scenarios/Kiyume/Fog/KiyumeFogSystem.cs:188-210 | Content/Scenarios/Kiyume/Fog/KiyumeFogSystem.cs:214-234 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 21+ corresponding lines) Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilateRenderer.cs:22 — Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilateRenderer.cs:22-42 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleRenderer.cs:217-237 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlashRenderer.cs:339-363 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 21+ corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1203 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1203-1224 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1019-1039 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1209-1230 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 21+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:289 — Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:289-312 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowBurrowAmbushState.cs:249-269 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowIntroState.cs:188-208 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 21+ corresponding lines) Content/Scenarios/SupCal/SupCalNarrativeTicker.cs:83 — Content/Scenarios/SupCal/SupCalNarrativeTicker.cs:83-104 | Content/Scenarios/SupCal/SupCalNarrativeTicker.cs:106-126 | Content/Scenarios/SupCal/SupCalNarrativeTicker.cs:128-148 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 21+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocBlindsideCrossState.cs:60 — Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocBlindsideCrossState.cs:60-80 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocMawFrenzyState.cs:59-82 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocServantLanceState.cs:56-76 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 13+ corresponding lines) · ×8
  • Edited copies of one member (4 members, 13+ corresponding lines) Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:102 — Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:102-114 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:107-120 | Content/Industrials/ElectricPowers/Recyclers/RecyclerUI.cs:102-115 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterUI.cs:103-118 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 13+ corresponding lines) Content/Narrative/Presentation/Skins/Brimstone/BrimstoneDialogueSkin.cs:51 — Content/Narrative/Presentation/Skins/Brimstone/BrimstoneDialogueSkin.cs:51-65 | Content/Narrative/Presentation/Skins/SHPC/SHPCDialogueSkin.cs:83-111 | Content/Narrative/Presentation/Skins/Sulfsea/SulfseaDialogueSkin.cs:44-56 | Content/Narrative/Presentation/Skins/Tzeentch/TzeentchDialogueSkin.cs:49-61 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 13+ corresponding lines) Content/NPCs/BloomsandSerpents/Core/IBssState.cs:121 — Content/NPCs/BloomsandSerpents/Core/IBssState.cs:121-133 | Content/NPCs/FestersandSerpents/Core/IFssState.cs:99-111 | Content/NPCs/ScrapCommanders/Core/IScrapState.cs:121-133 | Content/NPCs/SeaShrimp/Core/ISeaShrimpState.cs:109-121 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 13+ corresponding lines) Content/NPCs/BloomsandSerpents/States/BssPillarVaultState.cs:327 — Content/NPCs/BloomsandSerpents/States/BssPillarVaultState.cs:327-339 | Content/NPCs/BloomsandSerpents/States/BssPounceState.cs:181-195 | Content/NPCs/BloomsandSerpents/States/BssSandDashState.cs:187-201 | Content/NPCs/BloomsandSerpents/States/BssVortexDashState.cs:222-237 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 13+ corresponding lines) Content/Scenarios/Kiyume/NPCs/FuneralCortegeYokai.cs:60 — Content/Scenarios/Kiyume/NPCs/FuneralCortegeYokai.cs:60-72 | Content/Scenarios/Kiyume/NPCs/FuneralCortegeYokai.cs:683-695 | Content/Scenarios/Kiyume/NPCs/ShallowHandsYokai.cs:66-80 | Content/Scenarios/Kiyume/NPCs/WellHandYokai.cs:72-89 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 13+ corresponding lines) Content/GameModes/GodSmith/Accessories/Offense/GodSmithScopeChain.cs:68 — Content/GameModes/GodSmith/Accessories/Offense/GodSmithScopeChain.cs:68-80 | Content/Items/Ranged/Starships/StarshipMicroStar.cs:18-30 | Content/Items/Ranged/Starships/StarshipPlasmaBolt.cs:20-33 | Content/Items/Ranged/Undertows/UndertowSpine.cs:35-48 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 13+ corresponding lines) Content/GameModes/GodSmith/Weapons/Shortswords/GsGladius.cs:96 — Content/GameModes/GodSmith/Weapons/Shortswords/GsGladius.cs:96-108 | Content/GameModes/GodSmith/Weapons/Spears/GsAdamantiteGlaive.cs:72-87 | Content/GameModes/GodSmith/Weapons/Spears/GsJoustingLances.cs:327-341 | Content/GameModes/GodSmith/Weapons/Spears/GsSpear.cs:81-93 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 13+ corresponding lines) Content/Items/Accessories/BrutalRelics/KingSlime/FallenCrownProj.cs:35 — Content/Items/Accessories/BrutalRelics/KingSlime/FallenCrownProj.cs:35-48 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPour.cs:147-159 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronBloodnado.cs:48-61 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuHongFX.cs:64-77 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 12+ corresponding lines) · ×8
  • Edited copies of one member (6 members, 12+ corresponding lines) Content/Narrative/Presentation/Skins/Brimstone/BrimstoneChoiceSkin.cs:119 — Content/Narrative/Presentation/Skins/Brimstone/BrimstoneChoiceSkin.cs:119-141 | Content/Narrative/Presentation/Skins/Kikasa/KikasaChoiceSkin.cs:91-108 | Content/Narrative/Presentation/Skins/Onikiri/OnikiriChoiceSkin.cs:80-97 | Content/Narrative/Presentation/Skins/StarStream/StarStreamChoiceSkin.cs:49-62 | Content/Narrative/Presentation/Skins/Sulfsea/SulfseaChoiceSkin.cs:62-73 | Content/Narrative/Presentation/Skins/Tzeentch/TzeentchChoiceSkin.cs:66-77 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 12+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:864 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:864-875 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1100-1111 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:889-900 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:909-920 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:819-830 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:858-869 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 12+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPuddle.cs:142 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPuddle.cs:142-155 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuXiFX.cs:92-105 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuXiaoFX.cs:78-91 | Content/LegendWeapon/KikasaLegend/KikasaTeleports/KikasaTeleportProj.cs:352-366 | Content/Wraiths/Deaths/SeizureGround.cs:26-38 | Content/Wraiths/Projectiles/HeadlessShadeRig.cs:141-152 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 12+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishBloodyManowarVFX.cs:62 — Content/LegendWeapon/HalibutLegend/FishSkills/FishBloodyManowarVFX.cs:62-73 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBloodyManowarVFX.cs:76-87 | Content/LegendWeapon/HalibutLegend/FishSkills/FishFrostMinnowVFX.cs:42-54 | Content/LegendWeapon/HalibutLegend/FishSkills/FishHarpyVFX.cs:20-31 | Content/LegendWeapon/HalibutLegend/FishSkills/FishJewelVFX.cs:76-88 | Content/LegendWeapon/HalibutLegend/FishSkills/FishSwarmVFX.cs:182-194 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 12+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalDeerclops/DeerclopsAI.cs:169 — Content/NPCs/BrutalNPCs/BrutalDeerclops/DeerclopsAI.cs:169-180 | Content/NPCs/BrutalNPCs/BrutalDestroyer/DestroyerHeadAI.cs:220-231 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/DukeFishronAI.cs:249-262 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/EmpressOfLightAI.cs:216-227 | Content/NPCs/BrutalNPCs/BrutalKingSlime/KingSlimeAI.cs:175-186 | Content/NPCs/BrutalNPCs/BrutalQueenBee/BrutalQueenBeeAI.cs:159-170 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 12+ corresponding lines) Content/GameModes/BrutalMobs/Eclipse/EclMothronNPC.cs:241 — Content/GameModes/BrutalMobs/Eclipse/EclMothronNPC.cs:241-252 | Content/GameModes/BrutalMobs/Eclipse/EclipseNPC.cs:170-181 | Content/GameModes/BrutalMobs/FrostMoon/FrmMeleeNPC.cs:220-232 | Content/GameModes/BrutalMobs/Meteorite/MeteoriteBrutalNPC.cs:125-137 | Content/GameModes/BrutalMobs/PumpkinMoon/PumpkinMoonNPC.cs:497-509 | Content/GameModes/BrutalMobs/PumpkinMoon/PumpkinMoonNPC.cs:701-713 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 12+ corresponding lines) Content/Items/Melee/DestroyersBlade.cs:124 — Content/Items/Melee/DestroyersBlade.cs:124-135 | Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:100-111 | Content/Items/Melee/DragonsScaleGreatsword.cs:140-151 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:159-170 | Content/Items/Stones/Marbles/MarbleClub.cs:117-128 | Content/Items/Stones/Marbles/MarbleHuntingKnife.cs:113-124 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 12+ corresponding lines) Content/GameModes/GodSmith/Weapons/SummonSentries/Projectiles/GsSentryZoneProj.cs:33 — Content/GameModes/GodSmith/Weapons/SummonSentries/Projectiles/GsSentryZoneProj.cs:33-44 | Content/LegendWeapon/HalibutLegend/FishSkills/FishScorpioSandnado.cs:181-193 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangProj.cs:50-61 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailHead.cs:60-71 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoProj.cs:59-70 | Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraRangedSlashProj.cs:33-46 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 8+ corresponding lines) · ×8
  • Edited copies of one member (5 members, 8+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishofCthuluVFX.cs:170 — Content/LegendWeapon/HalibutLegend/FishSkills/FishofCthuluVFX.cs:170-181 | Content/PRTTypes/PRT_DefFrostGlint.cs:47-56 | Content/PRTTypes/PRT_DefHealMote.cs:52-59 | Content/PRTTypes/PRT_GravityVortex.cs:67-85 | Content/PRTTypes/PRT_HeartcarverPulseRing.cs:46-54 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 8+ corresponding lines) Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2Rooms.cs:30 — Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2Rooms.cs:30-37 | Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Rooms.cs:46-54 | Content/Scenarios/Dungeonworld/Gen/Layers/L4/L4Rooms.cs:39-47 | Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Rooms.cs:41-49 | Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Rooms.cs:38-46 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 8+ corresponding lines) Content/Narrative/Presentation/Skins/Brimstone/BrimstoneChoiceSkin.cs:57 — Content/Narrative/Presentation/Skins/Brimstone/BrimstoneChoiceSkin.cs:57-71 | Content/Narrative/Presentation/Skins/SHPC/SHPCChoiceSkin.cs:29-36 | Content/Narrative/Presentation/Skins/StarStream/StarStreamChoiceSkin.cs:28-35 | Content/Narrative/Presentation/Skins/Sulfsea/SulfseaChoiceSkin.cs:33-40 | Content/Narrative/Presentation/Skins/Tzeentch/TzeentchChoiceSkin.cs:33-40 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 8+ corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Barrel/HypersonicBarrelModule.cs:182 — Content/LegendWeapon/SHPCLegend/Modules/Barrel/HypersonicBarrelModule.cs:182-189 | Content/LegendWeapon/SHPCLegend/Modules/Frame/ResonanceFrameModule.cs:653-661 | Content/LegendWeapon/SHPCLegend/Modules/Power/CapacitorBankModule.cs:613-621 | Content/LegendWeapon/SHPCLegend/Modules/Stock/AssaultStockModule.cs:134-142 | Content/LegendWeapon/SHPCLegend/Modules/Stock/AssaultStockModule.cs:252-260 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 8+ corresponding lines) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetNet.cs:54 — Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetNet.cs:54-62 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownNet.cs:58-66 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaPlayerDrownNet.cs:48-56 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetNet.cs:53-61 | Content/Scenarios/Kiyume/Fog/KiyumeTideNet.cs:22-29 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 8+ corresponding lines) Content/GameModes/BrutalMobs/Ambience/Brinefume/BrinefumeAmbience.cs:327 — Content/GameModes/BrutalMobs/Ambience/Brinefume/BrinefumeAmbience.cs:327-334 | Content/GameModes/BrutalMobs/Ambience/Mireheart/MireheartPlayer.cs:254-261 | Content/GameModes/BrutalMobs/Ambience/Rainveil/RainveilStormSystem.cs:160-167 | Content/GameModes/BrutalMobs/Ambience/Rimehollow/RimehollowDirector.cs:77-84 | Content/GameModes/BrutalMobs/Ambience/Rotmire/RotmireVentSystem.cs:141-148 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 8+ corresponding lines) Content/Industrials/ElectricPowers/Apiaries/ApiaryTP.cs:430 — Content/Industrials/ElectricPowers/Apiaries/ApiaryTP.cs:430-437 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherTP.cs:557-564 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerTP.cs:633-640 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:547-554 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatTP.cs:425-432 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 8+ corresponding lines) Content/Scenarios/Dungeonworld/Gen/Layers/L4/L4WaterWorks.cs:96 — Content/Scenarios/Dungeonworld/Gen/Layers/L4/L4WaterWorks.cs:96-103 | Content/Scenarios/Dungeonworld/Gen/ScatterEngine.cs:76-83 | Content/Scenarios/Dungeonworld/Gen/Zones/AshfallStratum.cs:160-167 | Content/Scenarios/Kiyume/Gen/KiyumeStructures.cs:66-73 | Content/Scenarios/OldNet/Gen/OldNetBuildContext.cs:126-133 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×8
  • Duplicated block (23 lines × 2) Content/GameModes/GodSmith/Weapons/Broadswords/GsMeowmere.cs:414 — Content/GameModes/GodSmith/Weapons/Broadswords/GsMeowmere.cs:414-436 | Content/GameModes/GodSmith/Weapons/Broadswords/GsMeowmere.cs:547-569 — 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 (23 lines × 2) Content/NPCs/TBUGs/TBUGRiftSpawner.cs:117 — Content/NPCs/TBUGs/TBUGRiftSpawner.cs:117-139 | Content/NPCs/Victors/VictorPortalSpawner.cs:138-160 — before extracting anything, compare `Content/NPCs/TBUGs/TBUGRiftSpawner.cs` and `Content/NPCs/Victors/VictorPortalSpawner.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 130 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/TBUGs/TBUGRiftSpawner.cs:117` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (23 lines × 2) Content/Industrials/Generator/Biomass/BiomassGeneratorUI.cs:133 — Content/Industrials/Generator/Biomass/BiomassGeneratorUI.cs:133-155 | Content/Industrials/Generator/Thermal/ThermalGeneratorUI.cs:160-182 — before extracting anything, compare `Content/Industrials/Generator/Biomass/BiomassGeneratorUI.cs` and `Content/Industrials/Generator/Thermal/ThermalGeneratorUI.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 156 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/Generator/Biomass/BiomassGeneratorUI.cs:133` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (23 lines × 2) Content/Scenarios/Dungeonworld/Gen/Passes/ValidatePass.cs:62 — Content/Scenarios/Dungeonworld/Gen/Passes/ValidatePass.cs:62-84 | Content/Scenarios/Hadalworld/Gen/Passes/HadalValidatePass.cs:54-76 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/Gen/Passes/ValidatePass.cs:62` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (23 lines × 2) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/TwinsTetherArc.cs:60 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/TwinsTetherArc.cs:60-82 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeArcChainProj.cs:70-92 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/TwinsTetherArc.cs` and `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeArcChainProj.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 146 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/TwinsTetherArc.cs:60` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (23 lines × 2) Content/Scenarios/Kiame/Overlay/OniRainDescentRender.cs:127 — Content/Scenarios/Kiame/Overlay/OniRainDescentRender.cs:127-149 | Content/Scenarios/Kiame/Overlay/OniRainWorldRender.cs:188-210 — before extracting anything, compare `Content/Scenarios/Kiame/Overlay/OniRainDescentRender.cs` and `Content/Scenarios/Kiame/Overlay/OniRainWorldRender.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 98 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Kiame/Overlay/OniRainDescentRender.cs:127` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (23 lines × 2) Content/NPCs/BrutalNPCs/BrutalGolem/Rendering/GolemScreenEffectRender.cs:74 — Content/NPCs/BrutalNPCs/BrutalGolem/Rendering/GolemScreenEffectRender.cs:74-96 | Content/Renders/PrimeScreenEffectRender.cs:97-119 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalGolem/Rendering/GolemScreenEffectRender.cs` and `Content/Renders/PrimeScreenEffectRender.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalGolem/Rendering/GolemScreenEffectRender.cs:74` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (23 lines × 2) Content/LegendWeapon/HalibutLegend/FishSkills/FishTunabeardVFX.cs:214 — Content/LegendWeapon/HalibutLegend/FishSkills/FishTunabeardVFX.cs:214-236 | Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniKamuiFlowRenderer.cs:85-107 — before extracting anything, compare `Content/LegendWeapon/HalibutLegend/FishSkills/FishTunabeardVFX.cs` and `Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniKamuiFlowRenderer.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 112 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishTunabeardVFX.cs:214` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8–10 lines × 2) · ×8
  • Duplicated block (8–10 lines × 2) Content/GameModes/BrutalMobs/Ambience/Verdant/VerdantPRT.cs:175 — Content/GameModes/BrutalMobs/Ambience/Verdant/VerdantPRT.cs:175-184 | Content/GameModes/BrutalMobs/Ambience/Verdant/VerdantPRT.cs:243-250 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8–10 lines × 2) Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawWormProj.cs:356 — Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawWormProj.cs:356-363 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/EowHeadAI.cs:392-401 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (8–10 lines × 2) Content/Items/Accessories/BrutalRelics/MoonLord/BlackFlashSigilRender.cs:168 — Content/Items/Accessories/BrutalRelics/MoonLord/BlackFlashSigilRender.cs:168-177 | Content/Items/Accessories/BrutalRelics/QueenBee/SwarmVortexRender.cs:112-119 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/MoonLord/BlackFlashSigilRender.cs:168` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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–10 lines × 2) Content/Items/Magic/FocusingGrimoire.cs:176 — Content/Items/Magic/FocusingGrimoire.cs:176-183 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/CursedFlameJet.cs:57-66 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/FocusingGrimoire.cs:176` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8–10 lines × 2) Content/LegendWeapon/HalibutLegend/FishSkills/FishDrizzle.cs:402 — Content/LegendWeapon/HalibutLegend/FishSkills/FishDrizzle.cs:402-411 | Content/LegendWeapon/HalibutLegend/FishSkills/FishSparkling.cs:284-291 — 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. 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–10 lines × 2) Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemTrapUnit.cs:392 — Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemTrapUnit.cs:392-401 | Content/Scenarios/Dungeonworld/NPCs/OverseerSlagGlob.cs:147-154 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (8–10 lines × 2) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistAmbience.cs:57 — Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistAmbience.cs:57-66 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistAmbience.cs:117-124 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistAmbience.cs:57` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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–10 lines × 2) Content/Scenarios/Shepel/CybCourses/CybCourseCompletePanel.cs:140 — Content/Scenarios/Shepel/CybCourses/CybCourseCompletePanel.cs:140-147 | Content/Scenarios/Shepel/CybCourses/CybCourseKeyBindReminderPanel.cs:180-189 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Shepel/CybCourses/CybCourseCompletePanel.cs:140` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Scenarios/Shepel/CybCourses/CybCourseKeyBindReminderPanel.cs:189` calls `Clamp` and `Content/Scenarios/Shepel/CybCourses/CybCourseCompletePanel.cs:147` does not — after which the two agree again for 5 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.
D4 · Code Duplication · Duplicated block (4–7 lines × 3) · ×8
  • Duplicated block (4–7 lines × 3) Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs:92 — Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs:92-98 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmOrnamentProj.cs:95-98 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmPresentShellProj.cs:87-93 — before extracting anything, compare `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs` and `Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmOrnamentProj.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs:92` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (4–7 lines × 3) Content/HackTimes/Scannables/BossPartScannable.cs:59 — Content/HackTimes/Scannables/BossPartScannable.cs:59-62 | Content/HackTimes/Scannables/BossPartScannable.cs:65-71 | Content/HackTimes/Scannables/NpcScannable.cs:91-97 — 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. 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 (4–7 lines × 3) Content/Items/Melee/DragonsScaleGreatsword.cs:642 — Content/Items/Melee/DragonsScaleGreatsword.cs:642-645 | Content/Items/Melee/DragonsScaleGreatsword.cs:847-853 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:996-1002 — before extracting anything, compare `Content/Items/Melee/DragonsScaleGreatsword.cs` and `Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 415 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DragonsScaleGreatsword.cs:642` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (4–7 lines × 3) Content/Items/Melee/OniMacheteHands.cs:325 — Content/Items/Melee/OniMacheteHands.cs:325-331 | Content/Items/Melee/OniMacheteHands.cs:958-961 | Content/Items/Melee/OniMacheteHands.cs:1261-1267 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/OniMacheteHands.cs:325` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (4–7 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsHail.cs:107 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsHail.cs:107-113 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Projectiles/EocBloodShot.cs:76-82 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordOrbProj.cs:174-177 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsHail.cs:107` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (4–7 lines × 3) Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiStrikes.cs:168 — Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiStrikes.cs:168-174 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiStrikes.cs:260-266 | Content/LegendWeapon/OnikiriLegend/Tutorial/OniKeikoRune.cs:187-190 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiStrikes.cs:168` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/OnikiriLegend/Tutorial/OniKeikoRune.cs:187` calls `ToRotationVector2` and `Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiStrikes.cs:260` 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 (4–7 lines × 3) Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemSolarMeteor.cs:116 — Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemSolarMeteor.cs:116-119 | Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemSunBolt.cs:80-86 | Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemSunMortar.cs:110-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 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemSolarMeteor.cs:116` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (4–7 lines × 3) Content/Narrative/Presentation/Skins/Brimstone/BrimstonePanelState.cs:246 — Content/Narrative/Presentation/Skins/Brimstone/BrimstonePanelState.cs:246-251 | Content/UIs/UIEffect/AshPRT.cs:57-60 | Content/UIs/UIEffect/EmberPRT.cs:63-69 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Narrative/Presentation/Skins/Brimstone/BrimstonePanelState.cs:246` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
X5 · Nullable reference types · Symbol treated as nullable, then dereferenced unguarded · ×8
  • Symbol treated as nullable, then dereferenced unguarded Content/EntrustManager/Styles/ChronicleManagerStyle.cs:265 — This method contradicts itself about `entry`: line 261 writes `entry?.Provider`, which says `entry` can be null, but line 265 then dereferences it directly as `entry.Key` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `entry` truly cannot be null here, the `?.` is misleading. Settle it one way — test `entry` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Content/HackTimes/HackTimeNetSync.cs:603 — This method contradicts itself about `hack`: line 585 writes `hack?.Name`, which says `hack` can be null, but line 603 then dereferences it directly as `hack.SlotIndex` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `hack` truly cannot be null here, the `?.` is misleading. Settle it one way — test `hack` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Content/HackTimes/PvP/Protocols/CyberwareOfflineHook.cs:65 — This method contradicts itself about `cyberware`: line 63 writes `cyberware?.Player`, which says `cyberware` can be null, but line 65 then dereferences it directly as `cyberware.ProfileInitialized` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `cyberware` truly cannot be null here, the `?.` is misleading. Settle it one way — test `cyberware` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Content/Items/Modifys/RecoverUnloadedItem.cs:67 — This method contradicts itself about `unloadedItem`: line 66 assigns it with `as UnloadedItem`, which hands back null rather than throwing when the value is not a `UnloadedItem`, but line 67 then dereferences it directly as `unloadedItem.ModName` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `unloadedItem` once before the first use and handle the null case, or cast with `(UnloadedItem)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuPei.cs:104 — This method contradicts itself about `umbrella`: line 99 writes `umbrella?.FlipChargeFill`, which says `umbrella` can be null, but line 104 then dereferences it directly as `umbrella.Projectile` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `umbrella` truly cannot be null here, the `?.` is misleading. Settle it one way — test `umbrella` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Content/QuestLogs/Guide/QuestBookGuidePlayer.cs:561 — This method contradicts itself about `ui`: line 551 writes `ui?.FirstVisibleEntry`, which says `ui` can be null, but line 561 then dereferences it directly as `ui.SetEntryStatus` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `ui` truly cannot be null here, the `?.` is misleading. Settle it one way — test `ui` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Content/Wraiths/Runtime/WraithNet.cs:577 — This method contradicts itself about `state`: line 588 writes `state?.LoadoutRevision`, which says `state` can be null, but line 577 then dereferences it directly as `state.TrySetSlotAuthority` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `state` truly cannot be null here, the `?.` is misleading. Settle it one way — test `state` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Content/Wraiths/Runtime/WraithNet.cs:806 — This method contradicts itself about `player`: line 805 writes `player?.selectedItem`, which says `player` can be null, but line 806 then dereferences it directly as `player.inventory` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `player` truly cannot be null here, the `?.` is misleading. Settle it one way — test `player` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
AX2 · Stateful singletons · Process-global static state · ×7
  • Process-global static state: CWRID CWRID.cs:10 — `CWRID` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_idCache; e.g. `_idCache` at line 522). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: CWRLoad CWRLoad.cs:13 — `CWRLoad` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (SepulcherSegments, StormWeaverSegments, PrimordialWyrmSegments, PerforatorLargeSegments, PerforatorMediumSegments, ArmoredDiggerSegments; e.g. `SepulcherSegments` at line 142). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: CWRMod CWRMod.cs:11 — `CWRMod` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (instance, ILoaders; e.g. `instance` at line 18). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: CWRNetWork CWRNetWork.cs:13 — `CWRNetWork` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (channels, channelByType; e.g. `channels` at line 27). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: CWRRef CWRRef.cs:22 — `CWRRef` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_has, loggedReflectionFailures, DownedBossSystemType, downedDesertScourgeProp, downedCLAMProp, downedCrabulonProp; e.g. `_has` at line 27). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: CheckedVersions CheckedVersions.cs:9 — `CheckedVersions` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (SaveVersion; e.g. `SaveVersion` at line 38). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: CWRClientConfig Common/CWRClientConfig.cs:9 — `CWRClientConfig` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (Instance; e.g. `Instance` at line 57). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
D35 · Change Coupling · Change coupling · ×7
  • Change coupling: HeadPrimeAI.cs ↔ PrimeCannonOnSpan.cs Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/HeadPrimeAI.cs:1 — `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/HeadPrimeAI.cs` and `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeCannonOnSpan.cs` change together 85% of the time (11 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `d26a6c4a` 一些更新 (at that commit the file was still `Content/Projectiles/Boss/SkeletronPrime/PrimeCannonOnSpan.cs`); `342c08d8` 调整毁灭者 (at that commit the file was still `Content/Projectiles/Boss/SkeletronPrime/PrimeCannonOnSpan.cs`); `d85f5b70` 一些更新 (at that commit the files were still `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/BrutalSkeletronPrimeAI.cs` and `Content/Projectiles/Boss/SkeletronPrime/PrimeCannonOnSpan.cs`) — run `git show` on any of them.
  • Change coupling: OniFlashMark.cs ↔ OniZanshinSlash.cs Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashMark.cs:1 — `Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashMark.cs` and `Content/LegendWeapon/OnikiriLegend/OniZanshinSlashs/OniZanshinSlash.cs` change together 80% of the time (8 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `e365f4cf` Adjust Onikiri damage scalings and stats; `ee1c9a3a` update; `0a5a7521` Tweak Onikiri damage vs segmented enemies — run `git show` on any of them.
  • Change coupling: HeadPrimeAI.cs ↔ RocketSkeleton.cs Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/HeadPrimeAI.cs:1 — `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/HeadPrimeAI.cs` and `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/RocketSkeleton.cs` change together 67% of the time (10 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `72e3812e` 初步添加EXAI (at that commit the file was still `Content/Projectiles/Boss/SkeletronPrime/RocketSkeleton.cs`); `3900204a` 一些更新 (at that commit the file was still `Content/Projectiles/Boss/SkeletronPrime/RocketSkeleton.cs`); `d85f5b70` 一些更新 (at that commit the files were still `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/BrutalSkeletronPrimeAI.cs` and `Content/Projectiles/Boss/SkeletronPrime/RocketSkeleton.cs`) — run `git show` on any of them.
  • Change coupling: CrimsonRendCleave.cs ↔ OniZanshinSlash.cs Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendCleave.cs:1 — `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendCleave.cs` and `Content/LegendWeapon/OnikiriLegend/OniZanshinSlashs/OniZanshinSlash.cs` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `ee1c9a3a` update; `60063c3b` update; `f3baf8ce` update — run `git show` on any of them.
  • Change coupling: OniAnnihilate.cs ↔ OniFlashMark.cs Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:1 — `Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs` and `Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashMark.cs` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `e365f4cf` Adjust Onikiri damage scalings and stats; `0a5a7521` Tweak Onikiri damage vs segmented enemies; `93400502` update — run `git show` on any of them.
  • Change coupling: HackPanelRenderer.cs ↔ HackRamRenderer.cs Content/HackTimes/HackPanelRenderer.cs:1 — `Content/HackTimes/HackPanelRenderer.cs` and `Content/HackTimes/HackRamRenderer.cs` change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `56c43d6c` update; `93d2a6bb` update; `272c95fd` update — run `git show` on any of them.
  • Change coupling: CrimsonRendCleave.cs ↔ OniFlashStep.cs Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendCleave.cs:1 — `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendCleave.cs` and `Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashStep.cs` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `ee1c9a3a` update; `60063c3b` update; `f3baf8ce` update — run `git show` on any of them.
D4 · Code Duplication · Edited copy of a member (51 corresponding lines) · ×7
  • Edited copy of a member (51 corresponding lines) Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMoonFlare.cs:239 — Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMoonFlare.cs:239-289 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteStarSurge.cs:153-204 — These two members are one piece of code written twice and then edited apart: 51 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (51 corresponding lines) Content/GameModes/BrutalMobs/Legion/Projectiles/LegionSurfOmen.cs:63 — Content/GameModes/BrutalMobs/Legion/Projectiles/LegionSurfOmen.cs:63-113 | Content/GameModes/BrutalMobs/Ocean/Projectiles/OceanSharkOmen.cs:82-148 — These two members are one piece of code written twice and then edited apart: 51 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (51 corresponding lines) Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:292 — Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:292-347 | Content/Items/Melee/NeutronGlaive.cs:303-353 — These two members are one piece of code written twice and then edited apart: 51 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (51 corresponding lines) Content/NPCs/BloomsandSerpents/States/BssHubState.cs:70 — Content/NPCs/BloomsandSerpents/States/BssHubState.cs:70-120 | Content/NPCs/FestersandSerpents/States/FssHubState.cs:77-129 — These two members are one piece of code written twice and then edited apart: 51 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (51 corresponding lines) Content/GameModes/BrutalMobs/FrostMoon/FrmMiniBossNPC.cs:282 — Content/GameModes/BrutalMobs/FrostMoon/FrmMiniBossNPC.cs:282-332 | Content/GameModes/BrutalMobs/FrostMoon/FrmSiegeNPC.cs:281-342 — These two members are one piece of code written twice and then edited apart: 51 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (51 corresponding lines) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetNet.cs:64 — Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetNet.cs:64-116 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetNet.cs:63-113 — These two members are one piece of code written twice and then edited apart: 51 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (51 corresponding lines) Content/LegendWeapon/KikasaLegend/UI/ServantWheel/KikasaServantWheelController.cs:167 — Content/LegendWeapon/KikasaLegend/UI/ServantWheel/KikasaServantWheelController.cs:167-217 | Content/LegendWeapon/SHPCLegend/UI/DomainWheel/SHPCDomainWheelController.cs:144-195 — These two members are one piece of code written twice and then edited apart: 51 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (47 corresponding lines) · ×7
  • Edited copy of a member (47 corresponding lines) Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs:39 — Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs:39-85 | Content/Scenarios/OldDuke/Quest/SulfseaTrackerWidgetStyle.cs:39-86 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (47 corresponding lines) Content/GameModes/BrutalMobs/Ambience/DuneStorm/Projectiles/DuneStormSandLashOmen.cs:110 — Content/GameModes/BrutalMobs/Ambience/DuneStorm/Projectiles/DuneStormSandLashOmen.cs:110-156 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesIceShatterCore.cs:104-153 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (47 corresponding lines) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerDashingState.cs:37 — Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerDashingState.cs:37-84 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronTidalDashState.cs:148-194 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (47 corresponding lines) Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:243 — Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:243-289 | Content/Items/Melee/NeutronGlaive.cs:254-300 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (47 corresponding lines) Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs:150 — Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs:150-196 | Content/Scenarios/Shenyo/ShenyoPortraitRainRenderer.cs:148-194 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (47 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutDomain.cs:100 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutDomain.cs:100-146 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumCircle.cs:100-148 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (47 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishSlime.cs:28 — Content/LegendWeapon/HalibutLegend/FishSkills/FishSlime.cs:28-86 | Content/LegendWeapon/HalibutLegend/FishSkills/FishVariegatedLard.cs:26-72 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 42+ corresponding lines) · ×7
  • Edited copies of one member (3 members, 42+ corresponding lines) Content/EntrustManager/Styles/DraedonManagerStyle.cs:302 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:302-343 | Content/EntrustManager/Styles/ForestManagerStyle.cs:307-352 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:296-341 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 42 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 42+ corresponding lines) Content/NPCs/BloomsandSerpents/BssPortrait.cs:161 — Content/NPCs/BloomsandSerpents/BssPortrait.cs:161-203 | Content/NPCs/FestersandSerpents/Rendering/FssPortrait.cs:233-274 | Content/NPCs/SeaShrimp/Rendering/SeaShrimpPortrait.cs:110-157 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 42 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 42+ corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1451 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1451-1495 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1168-1209 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1360-1404 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 42 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 42+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistPhaseSkyEffect.cs:135 — Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistPhaseSkyEffect.cs:135-186 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordEclipseSky.cs:153-194 | Content/Scenarios/Himayo/ToriiShrines/ToriiDusk.cs:175-220 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 42 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 42+ corresponding lines) Content/Items/Accessories/BrutalRelics/EyeOfCthulhu/BloodfogIrisRender.cs:20 — Content/Items/Accessories/BrutalRelics/EyeOfCthulhu/BloodfogIrisRender.cs:20-63 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Rendering/EocFogRender.cs:22-75 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistVeilRender.cs:15-56 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 42 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 42+ corresponding lines) Content/GameModes/GodSmith/Weapons/Broadswords/BroadswordSchemes.Ore.cs:222 — Content/GameModes/GodSmith/Weapons/Broadswords/BroadswordSchemes.Ore.cs:222-263 | Content/GameModes/GodSmith/Weapons/Broadswords/GsAdamantiteSword.cs:91-132 | Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:362-414 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 42 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 42+ corresponding lines) Content/Scenarios/Himayo/ToriiShrines/ToriiShrineLocationFinder.cs:205 — Content/Scenarios/Himayo/ToriiShrines/ToriiShrineLocationFinder.cs:205-246 | Content/Scenarios/Kiame/Gate/KiameGateSpawn.cs:356-397 | Content/Scenarios/Kiame/Overlay/OniUmbrellaWorldSpawn.cs:430-471 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 42 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 20+ corresponding lines) · ×7
  • Edited copies of one member (3 members, 20+ corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Frame/MirrorFrameModule.cs:30 — Content/LegendWeapon/SHPCLegend/Modules/Frame/MirrorFrameModule.cs:30-49 | Content/LegendWeapon/SHPCLegend/Modules/Frame/RecursiveFrameModule.cs:28-51 | Content/LegendWeapon/SHPCLegend/Modules/Frame/ReplicatorFrameModule.cs:28-47 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 20+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaTalismans/KikasaTalismanRegistry.cs:46 — Content/LegendWeapon/KikasaLegend/KikasaTalismans/KikasaTalismanRegistry.cs:46-74 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiRegistry.cs:51-77 | Content/MainMenus/Characters/MenuCharacter.cs:126-145 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 20+ corresponding lines) Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtFanShot.cs:75 — Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtFanShot.cs:75-96 | Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornJavelinProj.cs:84-105 | Content/LegendWeapon/HalibutLegend/FishSkills/FishotroningVFX.cs:169-188 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 20+ corresponding lines) Content/GameModes/BrutalMobs/Martians/Projectiles/MrtTeslaArcProj.cs:205 — Content/GameModes/BrutalMobs/Martians/Projectiles/MrtTeslaArcProj.cs:205-228 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/TwinsTetherArc.cs:180-204 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpBubbleArc.cs:158-177 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 20+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainHoverState.cs:94 — Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainHoverState.cs:94-129 | Content/NPCs/BrutalNPCs/BrutalPlantera/Core/PlanteraDirector.cs:124-143 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/States/WofAdvanceState.cs:126-162 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 20+ corresponding lines) Content/Industrials/ElectricPowers/HealingStations/HealStationTP.cs:112 — Content/Industrials/ElectricPowers/HealingStations/HealStationTP.cs:112-131 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconTP.cs:253-280 | Content/Industrials/ElectricPowers/ShieldGenerators/ShieldGeneratorTP.cs:195-214 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 20+ corresponding lines) Content/Industrials/ElectricPowers/Crushers/CrusherStorageProvider.cs:148 — Content/Industrials/ElectricPowers/Crushers/CrusherStorageProvider.cs:148-171 | Content/Industrials/ElectricPowers/Incinerators/IncineratorStorageProvider.cs:158-181 | Content/Industrials/Generator/Biomass/BiomassStorageProvider.cs:123-142 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 15+ corresponding lines) · ×7
  • Edited copies of one member (4 members, 15+ corresponding lines) Content/Items/Melee/DragonsScaleGreatsword.cs:66 — Content/Items/Melee/DragonsScaleGreatsword.cs:66-81 | Content/Items/Melee/NeutronGlaive.cs:90-104 | Content/Items/Melee/RebelBlade.cs:96-111 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:95-110 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 15+ corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:229 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:229-243 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:189-203 | Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashMark.cs:78-93 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:210-224 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 15+ corresponding lines) Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaRender.cs:80 — Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaRender.cs:80-94 | Content/NPCs/BrutalNPCs/BrutalGolem/Core/GolemScreenEffects.cs:109-126 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Core/MLordScreenEffects.cs:95-114 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Core/PrimeScreenEffects.cs:95-114 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 15+ corresponding lines) Content/GameModes/GodSmith/Accessories/Offense/GodSmithManaFlowerChain.cs:145 — Content/GameModes/GodSmith/Accessories/Offense/GodSmithManaFlowerChain.cs:145-159 | Content/GameModes/GodSmith/Prefixes/Offense/GodSmithOverkillEndow.cs:77-91 | Content/GameModes/GodSmith/Prefixes/Ranged/GodSmithRicochetEndow.cs:77-91 | Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawCorrosionNPC.cs:196-210 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 15+ corresponding lines) Content/Industrials/ElectricPowers/Apiaries/ApiaryStorageProvider.cs:120 — Content/Industrials/ElectricPowers/Apiaries/ApiaryStorageProvider.cs:120-134 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherStorageProvider.cs:119-133 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerStorageProvider.cs:119-133 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconStorageProvider.cs:122-136 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 15+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalGolem/GolemGrabPlayer.cs:77 — Content/NPCs/BrutalNPCs/BrutalGolem/GolemGrabPlayer.cs:77-92 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/TwinsGrabPerformancePlayer.cs:181-197 | Content/NPCs/BrutalNPCs/BrutalMoonLord/MLordGrabPlayer.cs:55-69 | Content/TimeFreezes/WorldFreezePlayer.cs:107-126 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 15+ corresponding lines) Content/Scenarios/Kiyume/NPCs/KiyumeHound.cs:700 — Content/Scenarios/Kiyume/NPCs/KiyumeHound.cs:700-714 | Content/Scenarios/Kiyume/NPCs/KiyumeWhiteHound.cs:220-234 | Content/Scenarios/Kiyume/NPCs/MinoFisherYokai.cs:230-244 | Content/Scenarios/Kiyume/NPCs/ScarecrowWatcherYokai.cs:482-496 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 9+ corresponding lines) · ×7
  • Edited copies of one member (6 members, 9+ corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendParticles.cs:836 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendParticles.cs:836-846 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleParticles.cs:55-65 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Rendering/FishronPRT.cs:43-54 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Rendering/QueenBeePRT.cs:161-170 | Content/PRTTypes/PRT_ATShard.cs:38-46 | Content/PRTTypes/PRT_CtrlWirePulse.cs:41-49 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 9+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishIchornVFX.cs:168 — Content/LegendWeapon/HalibutLegend/FishSkills/FishIchornVFX.cs:168-181 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:311-321 | Content/PRTTypes/PRT_KikasaInkBead.cs:48-58 | Content/Scenarios/Dungeonworld/NPCs/GaolFireBolt.cs:260-271 | Content/Scenarios/Dungeonworld/NPCs/OverseerSlagGlob.cs:241-249 | Content/Scenarios/Dungeonworld/NPCs/UndrownedTideWave.cs:232-241 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 9+ corresponding lines) Content/GameModes/BrutalMobs/Ambience/Mireheart/Projectiles/MireheartBeeCloudProj.cs:153 — Content/GameModes/BrutalMobs/Ambience/Mireheart/Projectiles/MireheartBeeCloudProj.cs:153-163 | Content/GameModes/BrutalMobs/Ambience/Rotmire/Projectiles/RotmireWritheProj.cs:225-235 | Content/GameModes/BrutalMobs/Ambience/Sporeshine/Projectiles/SporeshineSporeFogProj.cs:140-150 | Content/GameModes/BrutalMobs/SlimeKin/Projectiles/SlimeGelBomb.cs:139-149 | Content/Items/Melee/DestroyersBladeEXs/DestroyerBiteProj.cs:86-97 | Content/Items/Melee/Shatterfangs/ShatterfangBurstFX.cs:42-50 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 9+ corresponding lines) Content/Cyberwares/Implementation/PlowSteelClampArms/MonomolecularWire.cs:247 — Content/Cyberwares/Implementation/PlowSteelClampArms/MonomolecularWire.cs:247-255 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPour.cs:455-463 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuLongFX.cs:121-129 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowDevourState.cs:445-453 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Core/WofWallField.cs:212-220 | Content/Scenarios/OldNet/NPCs/OldNetTracerICE.cs:159-167 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 9+ corresponding lines) Content/GameModes/BrutalMobs/Eclipse/EclipseNPC.cs:158 — Content/GameModes/BrutalMobs/Eclipse/EclipseNPC.cs:158-167 | Content/GameModes/BrutalMobs/EliteMove/EliteMoveNPC.cs:134-142 | Content/GameModes/BrutalMobs/FrostMoon/FrmSiegeUtils.cs:72-80 | Content/GameModes/BrutalMobs/PumpkinMoon/PumpkinMoonNPC.cs:274-282 | Content/GameModes/BrutalMobs/SlimeKin/SlimeKinNPC.cs:314-322 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaBloodColumn.cs:145-154 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 9+ corresponding lines) Content/NPCs/BloomsandSerpents/BssVfx.cs:95 — Content/NPCs/BloomsandSerpents/BssVfx.cs:95-103 | Content/NPCs/FestersandSerpents/FssVfx.cs:138-146 | Content/NPCs/ScrapCommanders/Core/IScrapState.cs:136-144 | Content/NPCs/ScrapCommanders/ScrapVfx.cs:74-82 | Content/NPCs/SeaShrimp/Core/ISeaShrimpState.cs:132-140 | Content/Scenarios/Kiyume/NPCs/FuneralCortegeYokai.cs:1144-1152 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 9+ corresponding lines) Content/Scenarios/Dungeonworld/Gen/Infill/InfillRooms.cs:27 — Content/Scenarios/Dungeonworld/Gen/Infill/InfillRooms.cs:27-35 | Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2Rooms.cs:18-26 | Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Rooms.cs:25-33 | Content/Scenarios/Dungeonworld/Gen/Layers/L4/L4Rooms.cs:27-35 | Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Rooms.cs:19-27 | Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Rooms.cs:18-26 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 11+ corresponding lines) · ×7
  • Edited copies of one member (6 members, 11+ corresponding lines) Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineStorageProvider.cs:220 — Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineStorageProvider.cs:220-230 | Content/Industrials/ElectricPowers/Crushers/CrusherStorageProvider.cs:253-265 | Content/Industrials/ElectricPowers/Incinerators/IncineratorStorageProvider.cs:275-287 | Content/Industrials/ElectricPowers/Recyclers/RecyclerStorageProvider.cs:231-243 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterStorageProvider.cs:238-248 | Content/Industrials/Generator/Biomass/BiomassStorageProvider.cs:220-230 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 11+ corresponding lines) Content/HackTimes/Protocols/CompensationProtocol.cs:148 — Content/HackTimes/Protocols/CompensationProtocol.cs:148-158 | Content/HackTimes/Protocols/DataLeech.cs:106-116 | Content/HackTimes/Protocols/LimbSeizure.cs:142-153 | Content/HackTimes/Protocols/LiveCellTap.cs:165-175 | Content/HackTimes/Protocols/SegmentDelink.cs:151-162 | Content/HackTimes/PvP/UI/PlayerHackHud.cs:354-365 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 11+ corresponding lines) Content/GameModes/BrutalMobs/Martians/Projectiles/MrtGuardShieldProj.cs:45 — Content/GameModes/BrutalMobs/Martians/Projectiles/MrtGuardShieldProj.cs:45-55 | Content/GameModes/BrutalMobs/Martians/Projectiles/MrtOverheatMarkProj.cs:38-48 | Content/GameModes/BrutalMobs/NightPack/Projectiles/NightDiveOmen.cs:51-61 | Content/GameModes/BrutalMobs/NightPack/Projectiles/NightPounceOmen.cs:42-52 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkChargeOmen.cs:57-68 | Content/GameModes/GodSmith/Weapons/Throwing/Projectiles/GsZoneProj.cs:154-164 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 11+ corresponding lines) Content/Scenarios/OldNet/NPCs/OldNetLurkerICE.cs:235 — Content/Scenarios/OldNet/NPCs/OldNetLurkerICE.cs:235-245 | Content/Scenarios/OldNet/NPCs/OldNetPatrolICE.cs:220-232 | Content/Scenarios/OldNet/NPCs/OldNetSweepEye.cs:169-179 | Content/Scenarios/OldNet/NPCs/OldNetTaggerICE.cs:222-232 | Content/Scenarios/OldNet/NPCs/OldNetTracerICE.cs:376-386 | Content/Scenarios/OldNet/NPCs/OldNetTurretICE.cs:116-128 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 11+ corresponding lines) Content/GameModes/GodSmith/Weapons/MagicChant/GsCursedFlames.cs:162 — Content/GameModes/GodSmith/Weapons/MagicChant/GsCursedFlames.cs:162-172 | Content/GameModes/GodSmith/Weapons/MagicChant/GsNettleBurst.cs:187-197 | Content/GameModes/GodSmith/Weapons/MagicChant/GsWaspGun.cs:158-168 | Content/GameModes/GodSmith/Weapons/MagicConduit/GsLaserMachinegun.cs:89-100 | Content/GameModes/GodSmith/Weapons/MagicConduit/Projectiles/GsChargedBlasterCannonHeldProj.cs:116-126 | Content/GameModes/GodSmith/Weapons/MagicMorph/Projectiles/GsNimbusCorridorProj.cs:26-38 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 11+ corresponding lines) Content/GameModes/GodSmith/Weapons/Flails/GsFlamingMace.cs:71 — Content/GameModes/GodSmith/Weapons/Flails/GsFlamingMace.cs:71-81 | Content/GameModes/GodSmith/Weapons/Flails/GsGolemFist.cs:232-242 | Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:239-250 | Content/Items/Magic/FocusingGrimoire.cs:253-264 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowArrow.cs:32-44 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodCatch.cs:44-55 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 11+ corresponding lines) Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaRender.cs:37 — Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaRender.cs:37-47 | Content/NPCs/BrutalNPCs/BrutalGolem/Core/GolemScreenEffects.cs:37-47 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Core/MLordScreenEffects.cs:32-42 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Core/SkeletronScreenEffects.cs:34-44 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Core/PrimeScreenEffects.cs:32-42 | Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:2777-2787 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 7+ corresponding lines) · ×7
  • Edited copies of one member (5 members, 7+ corresponding lines) Content/GameModes/GodSmith/Weapons/Broadswords/GsChlorophyteClaymore.cs:76 — Content/GameModes/GodSmith/Weapons/Broadswords/GsChlorophyteClaymore.cs:76-86 | Content/GameModes/GodSmith/Weapons/Broadswords/GsDD2SquireDemonSword.cs:123-132 | Content/GameModes/GodSmith/Weapons/Broadswords/GsPhaseBladeShared.cs:240-246 | Content/GameModes/GodSmith/Weapons/Broadswords/GsSeedler.cs:71-81 | Content/GameModes/GodSmith/Weapons/Broadswords/GsSlapHand.cs:80-90 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 7+ corresponding lines) Content/Scenarios/Shepel/Gifts/ShepelMoonLordGift.cs:29 — Content/Scenarios/Shepel/Gifts/ShepelMoonLordGift.cs:29-35 | Content/Scenarios/Shepel/Gifts/ShepelPlanteraGift.cs:29-35 | Content/Scenarios/Shepel/Gifts/ShepelSlimeGodGift.cs:28-34 | Content/Scenarios/Shepel/Gifts/ShepelSupremeCalamitasGift.cs:28-34 | Content/Scenarios/Shepel/Gifts/ShepelYharonGift.cs:28-34 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 7+ corresponding lines) Content/GameModes/GodSmith/Weapons/MagicConduit/GsChargedBlasterCannon.cs:39 — Content/GameModes/GodSmith/Weapons/MagicConduit/GsChargedBlasterCannon.cs:39-46 | Content/GameModes/GodSmith/Weapons/MagicConduit/GsLastPrism.cs:49-55 | Content/GameModes/GodSmith/Weapons/MagicConduit/GsMedusaHead.cs:44-51 | Content/GameModes/GodSmith/Weapons/MagicConduit/GsShadowbeamStaff.cs:34-41 | Content/GameModes/GodSmith/Weapons/MagicConduit/GsSoulDrain.cs:41-47 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 7+ corresponding lines) Content/Items/Ranged/BarrenBow.cs:47 — Content/Items/Ranged/BarrenBow.cs:47-54 | Content/Items/Ranged/NeutronBows/NeutronBow.cs:69-76 | Content/Items/Ranged/Thornstrings/Thornstring.cs:48-55 | Content/Items/Ranged/Undertows/Undertow.cs:48-55 | Content/Projectiles/BaseHeldGun.cs:25-31 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 7+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalMoonLord/Core/MLordStateBase.cs:114 — Content/NPCs/BrutalNPCs/BrutalMoonLord/Core/MLordStateBase.cs:114-120 | Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordFreeEyeAI.cs:625-631 | Content/NPCs/BrutalNPCs/BrutalMoonLord/States/MLordMoonBiteState.cs:277-283 | Content/NPCs/BrutalNPCs/BrutalMoonLord/States/MLordPalmExecutionState.cs:290-296 | Content/NPCs/ScrapCommanders/Core/IScrapState.cs:99-106 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 7+ corresponding lines) Content/LegendWeapon/OnikiriLegend/UI/OniBrush.cs:387 — Content/LegendWeapon/OnikiriLegend/UI/OniBrush.cs:387-393 | Content/LegendWeapon/OnikiriLegend/UI/OniMeiCodexRenderer.cs:60-66 | Content/LegendWeapon/OnikiriLegend/UI/OniMeiRenderer.cs:16-22 | Content/LegendWeapon/OnikiriLegend/UI/OniRegisterRenderer.cs:898-904 | Content/QuestLogs/Core/QuestLogTheme.cs:169-175 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 7+ corresponding lines) Content/GameModes/BrutalMobs/Ambience/Stonewake/Projectiles/StonewakeGazePillarProj.cs:68 — Content/GameModes/BrutalMobs/Ambience/Stonewake/Projectiles/StonewakeGazePillarProj.cs:68-74 | Content/GameModes/BrutalMobs/Ambience/Stonewake/Projectiles/StonewakeResonanceRingProj.cs:56-62 | Content/GameModes/BrutalMobs/Ambience/Tidecall/Projectiles/TidecallRogueWaveProj.cs:87-93 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkMortarMarkerProj.cs:54-60 | Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilSurgeColumnProj.cs:68-74 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) · ×7
  • Edited copies of one member (3 members, 5+ corresponding lines) Content/GameModes/BrutalMobs/Ambience/Nyxdepth/Projectiles/NyxdepthSinkColumnProj.cs:173 — Content/GameModes/BrutalMobs/Ambience/Nyxdepth/Projectiles/NyxdepthSinkColumnProj.cs:173-177 | Content/GameModes/BrutalMobs/Ambience/Rimehollow/Projectiles/RimehollowMistPoolProj.cs:97-101 | Content/GameModes/BrutalMobs/Ambience/Sunkendune/Projectiles/SunkenduneSinkPitProj.cs:160-164 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 5+ corresponding lines) Content/LegendWeapon/OnikiriLegend/OniSakuraFlights/OniSakuraFlight.cs:471 — Content/LegendWeapon/OnikiriLegend/OniSakuraFlights/OniSakuraFlight.cs:471-475 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Rendering/WofRenderHelper.cs:54-58 | Content/Scenarios/Dungeonworld/NPCs/UndrownedVFX.cs:264-268 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 5+ corresponding lines) Content/Scenarios/OldNet/NPCs/OldNetBlackICE.cs:193 — Content/Scenarios/OldNet/NPCs/OldNetBlackICE.cs:193-198 | Content/Scenarios/OldNet/NPCs/OldNetTaggerICE.cs:216-220 | Content/Scenarios/OldNet/NPCs/OldNetTracerICE.cs:369-374 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 5+ corresponding lines) Content/GameModes/BrutalMobs/Ambience/Cindercrag/Projectiles/CindercragWailWaveProj.cs:53 — Content/GameModes/BrutalMobs/Ambience/Cindercrag/Projectiles/CindercragWailWaveProj.cs:53-58 | Content/GameModes/BrutalMobs/EliteMove/Projectiles/EMDecoyProj.cs:76-80 | Content/GameModes/GodSmith/Weapons/MagicMorph/Projectiles/GsDomainProj.cs:66-71 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 5+ corresponding lines) Content/HackTimes/Protocols/CommandLinkCut.cs:143 — Content/HackTimes/Protocols/CommandLinkCut.cs:143-147 | Content/HackTimes/Protocols/SegmentDelink.cs:182-186 | Content/HackTimes/Protocols/SwarmLink.cs:106-110 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 5+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressLance.cs:74 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressLance.cs:74-78 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressRibbon.cs:69-73 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistFallingStar.cs:52-57 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 5+ corresponding lines) Content/HackTimes/Protocols/Cyberpsychosis.cs:38 — Content/HackTimes/Protocols/Cyberpsychosis.cs:38-42 | Content/HackTimes/Protocols/MemoryWipe.cs:38-42 | Content/HackTimes/Protocols/SystemReset.cs:39-43 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (24 lines × 2) · ×7
  • Duplicated block (24 lines × 2) Content/GameModes/BrutalMobs/Martians/Projectiles/MrtWrenchProj.cs:98 — Content/GameModes/BrutalMobs/Martians/Projectiles/MrtWrenchProj.cs:98-121 | Content/GameModes/BrutalMobs/NightPack/Projectiles/NightBoneProj.cs:99-122 — before extracting anything, compare `Content/GameModes/BrutalMobs/Martians/Projectiles/MrtWrenchProj.cs` and `Content/GameModes/BrutalMobs/NightPack/Projectiles/NightBoneProj.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Martians/Projectiles/MrtWrenchProj.cs:98` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (24 lines × 2) Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberPixelDecomposeProj.cs:64 — Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberPixelDecomposeProj.cs:64-87 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberReformProj.cs:70-93 — before extracting anything, compare `Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberPixelDecomposeProj.cs` and `Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberReformProj.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 183 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberPixelDecomposeProj.cs:64` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (24 lines × 2) Content/EntrustManager/Styles/DraedonManagerStyle.cs:667 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:667-690 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:678-701 — before extracting anything, compare `Content/EntrustManager/Styles/DraedonManagerStyle.cs` and `Content/EntrustManager/Styles/HotwindManagerStyle.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 442 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/EntrustManager/Styles/DraedonManagerStyle.cs:667` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (24 lines × 2) Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineStorageProvider.cs:152 — Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineStorageProvider.cs:152-175 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterStorageProvider.cs:158-181 — before extracting anything, compare `Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineStorageProvider.cs` and `Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterStorageProvider.cs` as WHOLE FILES: this scan already matched 3 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (24 lines × 2) Content/Industrials/ElectricPowers/Collectors/CollectorArm.cs:881 — Content/Industrials/ElectricPowers/Collectors/CollectorArm.cs:881-904 | Content/Industrials/ElectricPowers/Lumberjacks/LumberjackSaw.cs:731-754 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Collectors/CollectorArm.cs:881` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (24 lines × 2) Content/Industrials/Generator/Thermal/ThermalStorageProvider.cs:135 — Content/Industrials/Generator/Thermal/ThermalStorageProvider.cs:135-158 | Content/Industrials/Generator/Thermal/ThermalStorageProvider.cs:375-398 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (24 lines × 2) Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:344 — Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:344-367 | Content/Scenarios/Kiyume/UI/KiyumeLoadingScreen.cs:350-373 — before extracting anything, compare `Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs` and `Content/Scenarios/Kiyume/UI/KiyumeLoadingScreen.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 214 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:344` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (16 lines × 3) · ×7
  • Duplicated block (16 lines × 3) Content/Industrials/Generator/Biomass/BiomassStorageProvider.cs:153 — Content/Industrials/Generator/Biomass/BiomassStorageProvider.cs:153-168 | Content/Industrials/Generator/Thermal/ThermalStorageProvider.cs:169-184 | Content/Industrials/Generator/Thermal/ThermalStorageProvider.cs:409-424 — before extracting anything, compare `Content/Industrials/Generator/Biomass/BiomassStorageProvider.cs` and `Content/Industrials/Generator/Thermal/ThermalStorageProvider.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/Generator/Biomass/BiomassStorageProvider.cs:153` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (16 lines × 3) Content/Items/Melee/NeutronGlaive.cs:612 — Content/Items/Melee/NeutronGlaive.cs:612-627 | Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:749-764 | Content/Items/Modifys/RBloodButcherer.cs:733-748 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/NeutronGlaive.cs:612` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:935 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:935-950 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1322-1337 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:935-950 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs` as WHOLE FILES: this scan already matched 48 separate duplicated blocks between them, totalling at least 508 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:935` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 3) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:429 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:429-444 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:302-317 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:391-406 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:429` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 3) Content/Items/Summon/BloomCallers/BloomCallerSprout.cs:65 — Content/Items/Summon/BloomCallers/BloomCallerSprout.cs:65-80 | Content/Items/Summon/Deepclaws/DeepclawLobster.cs:80-95 | Content/Items/Summon/EyekiteStaffs/EyekiteMinion.cs:64-79 — before extracting anything, compare `Content/Items/Summon/BloomCallers/BloomCallerSprout.cs` and `Content/Items/Summon/Deepclaws/DeepclawLobster.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (16 lines × 3) Content/Items/Magic/MelodyTheSand.cs:64 — Content/Items/Magic/MelodyTheSand.cs:64-79 | Content/Items/Magic/SandVortexOfTheDecayedSea.cs:59-74 | Content/Items/Magic/UnderTheSand.cs:77-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 3 call sites, so a change lands once.
  • Duplicated block (16 lines × 3) Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryRoom.cs:487 — Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryRoom.cs:487-502 | Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolBossRoom.cs:336-351 | Content/Scenarios/Dungeonworld/Gen/BossRooms/ProofingHallRoom.cs:515-530 — 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.
D4 · Code Duplication · Duplicated block (10 lines × 7) · ×7
  • Duplicated block (10 lines × 7) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingUI.cs:383 — Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingUI.cs:383-392 | Content/LegendWeapon/SHPCLegend/UI/SHPCCyberPanel.cs:357-366 | Content/LegendWeapon/SHPCLegend/UI/SHPCModPanel.cs:245-254 | Content/QuestLogs/QuestLogLauncher.cs:136-145 | Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:81-90 | Content/QuestLogs/Styles/ForestQuestLogStyle.cs:83-92 | Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:46-55 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingUI.cs:383` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/SHPCLegend/UI/SHPCCyberPanel.cs:353` calls `SetValue`, `Clamp` and `Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingUI.cs:379` 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 (10 lines × 7) Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs:126 — Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs:126-135 | Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:142-151 | Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgStabGlintOmen.cs:130-139 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmStrafeLaneProj.cs:114-123 | Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyRavenSwoopOmen.cs:144-153 | Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteDiveOmen.cs:129-139 | Content/GameModes/BrutalMobs/Sky/Projectiles/SkyGaleDiveOmen.cs:124-133 — before extracting anything, compare `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs` and `Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteDiveOmen.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs:126` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 7) Content/GameModes/GodSmith/Weapons/MagicCataclysm/GsBatScepter.cs:36 — Content/GameModes/GodSmith/Weapons/MagicCataclysm/GsBatScepter.cs:36-45 | Content/GameModes/GodSmith/Weapons/MagicCataclysm/GsBlizzardStaff.cs:34-43 | Content/GameModes/GodSmith/Weapons/MagicCataclysm/GsLunarFlare.cs:35-44 | Content/GameModes/GodSmith/Weapons/MagicCataclysm/GsResonanceScepter.cs:37-46 | Content/GameModes/GodSmith/Weapons/MagicCataclysm/GsSpectreStaff.cs:28-37 | Content/GameModes/GodSmith/Weapons/MagicChant/GsWaspGun.cs:33-42 | Content/GameModes/GodSmith/Weapons/MagicMorph/GsShadowFlameHexDoll.cs:29-38 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times.
  • Duplicated block (10 lines × 7) Content/Items/Magic/Elysiums/Serpents/HolySerpent.cs:387 — Content/Items/Magic/Elysiums/Serpents/HolySerpent.cs:387-396 | Content/Items/Melee/DestroyersBlade.cs:523-533 | Content/Items/Melee/DragonsScaleGreatsword.cs:546-556 | Content/Items/Melee/EnergySword.cs:562-572 | Content/Items/Melee/RebelBlade.cs:593-603 | Content/Items/Melee/StormGoddessSpears/StormGoddessSpearHeld.cs:533-543 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:528-538 — before extracting anything, compare `Content/Items/Melee/DestroyersBlade.cs` and `Content/Items/Melee/DragonsScaleGreatsword.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 419 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/Elysiums/Serpents/HolySerpent.cs:387` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `effect` to `Effect` in one and `out SpriteEffects` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (10 lines × 7) Content/NPCs/BloomsandSerpents/BssHead.cs:399 — Content/NPCs/BloomsandSerpents/BssHead.cs:399-408 | Content/NPCs/FestersandSerpents/FssHead.cs:353-362 | Content/NPCs/ScrapCommanders/ScrapCommander.cs:319-328 | Content/NPCs/SeaShrimp/SeaShrimpBoss.cs:291-300 | Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:440-449 | Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:447-456 | Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:482-491 — before extracting anything, compare `Content/NPCs/BloomsandSerpents/BssHead.cs` and `Content/NPCs/FestersandSerpents/FssHead.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 321 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 7) Content/GameModes/GodSmith/Armors/Endgame/GsApprenticeArmor.cs:126 — Content/GameModes/GodSmith/Armors/Endgame/GsApprenticeArmor.cs:126-135 | Content/GameModes/GodSmith/Armors/Endgame/GsHuntressArmor.cs:149-158 | Content/GameModes/GodSmith/Armors/Hardmode/GsChlorophyteArmor.cs:201-210 | Content/GameModes/GodSmith/Armors/Reset/GsFrostArmor.cs:83-92 | Content/GameModes/GodSmith/Armors/Reset/GsOreArmorsHardmode.cs:261-270 | Content/GameModes/GodSmith/Armors/Reset/GsOreArmorsHardmode.cs:552-561 | Content/GameModes/GodSmith/Armors/Reset/GsOreArmorsPreHardmode.cs:274-283 — there are 7 copies across 6 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 7 sites; resolving a subset leaves the remainder to drift apart. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/GameModes/GodSmith/Armors/Reset/GsOreArmorsHardmode.cs:563` calls `GetAlpha`, `Color` and `Content/GameModes/GodSmith/Armors/Endgame/GsApprenticeArmor.cs:137` 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 (10 lines × 7) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberShockwaveProj.cs:18 — Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberShockwaveProj.cs:18-27 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberFreezeWaveProj.cs:18-27 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberPixelDecomposeProj.cs:23-32 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberReformProj.cs:26-35 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/ScattershotBarrelModule.cs:314-323 | Content/LegendWeapon/SHPCLegend/Modules/Grip/HarmonyGripModule.cs:104-113 | Content/LegendWeapon/SHPCLegend/Modules/Optic/HoloOpticModule.cs:76-85 — before extracting anything, compare `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberShockwaveProj.cs` and `Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberFreezeWaveProj.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/SHPCLegend/Modules/Optic/HoloOpticModule.cs:73` calls `ToRotationVector2` and `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberShockwaveProj.cs:16` 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.
D4 · Code Duplication · Duplicated block (11–12 lines × 3) · ×7
  • Duplicated block (11–12 lines × 3) Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:547 — Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:547-558 | Content/GameModes/GodSmith/Weapons/Shortswords/GsThrustHeldBase.cs:962-972 | Content/Items/Modifys/RBloodButcherer.cs:525-536 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:547` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (11–12 lines × 3) Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordScheme.cs:34 — Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordScheme.cs:34-44 | Content/GameModes/GodSmith/Weapons/Broadswords/GsZombieArm.cs:32-43 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsOdditiesComboScheme.cs:33-43 — before extracting anything, compare `Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordScheme.cs` and `Content/GameModes/GodSmith/Weapons/MeleeOddities/GsOdditiesComboScheme.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordScheme.cs:34` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (11–12 lines × 3) Content/Items/Melee/Abyssrends/AbyssrendFX.cs:146 — Content/Items/Melee/Abyssrends/AbyssrendFX.cs:146-156 | Content/LegendWeapon/HalibutLegend/DomainSkills/RestartFish.cs:614-625 | Content/NPCs/SeaShrimp/Rendering/SeaShrimpVFX.cs:64-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/HalibutLegend/DomainSkills/RestartFish.cs:613` calls `SetValue`, `ToVector3` and `Content/Items/Melee/Abyssrends/AbyssrendFX.cs:146` 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–12 lines × 3) Content/Items/Melee/DawnshatterAzures/DawnshatterDash.cs:470 — Content/Items/Melee/DawnshatterAzures/DawnshatterDash.cs:470-480 | Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashStep.cs:1131-1141 | Content/LegendWeapon/OnikiriLegend/OniSakuraFlights/OniSakuraFlight.cs:1256-1267 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. 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 (11–12 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:554 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:554-565 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:507-518 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:463-473 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 491 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:554` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11–12 lines × 3) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistStarChartState.cs:26 — Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistStarChartState.cs:26-36 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistStarfallState.cs:43-54 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistZodiacSealState.cs:35-45 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistStarChartState.cs:26` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistZodiacSealState.cs:32` calls `SealCount` and `Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistStarChartState.cs:24` 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–12 lines × 3) Content/Scenarios/Dungeonworld/Ambience/AmbientEmitters.cs:75 — Content/Scenarios/Dungeonworld/Ambience/AmbientEmitters.cs:75-85 | Content/Scenarios/Dungeonworld/Fog/FogSuppression.cs:80-91 | Content/Scenarios/Kiyume/Fog/KiyumeFogSuppression.cs:87-98 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
D4 · Code Duplication · Duplicated block (9 lines × 7) · ×7
  • Duplicated block (9 lines × 7) Content/Items/Accessories/BrutalRelics/KingSlime/FallenCrownProj.cs:244 — Content/Items/Accessories/BrutalRelics/KingSlime/FallenCrownProj.cs:244-252 | Content/Items/Accessories/BrutalRelics/KingSlime/KingsVerdictWave.cs:159-167 | Content/Items/Ranged/Pallbearer.cs:1273-1281 | Content/LegendWeapon/HalibutLegend/FishSkills/FishAmanita.cs:694-702 | Content/LegendWeapon/HalibutLegend/FishSkills/FishHoney.cs:286-294 | Content/LegendWeapon/HalibutLegend/FishSkills/FishSlime.cs:852-860 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSCrownProj.cs:482-490 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/KingSlime/FallenCrownProj.cs:244` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 7) Content/Items/Melee/OniMachete.cs:376 — Content/Items/Melee/OniMachete.cs:376-384 | Content/LegendWeapon/HalibutLegend/FishSkills/FishTunabeardVFX.cs:171-179 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSlashRenderer.cs:320-328 | Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilateRenderer.cs:30-38 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleRenderer.cs:225-233 | Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniKamuiFlowRenderer.cs:43-51 | Content/LegendWeapon/OnikiriLegend/OniSakuraFlights/OniSakuraFlowRenderer.cs:57-65 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/OniMachete.cs:376` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilateRenderer.cs:40` calls `SetValue` and `Content/Items/Melee/OniMachete.cs:386` does not — after which the two agree again for 3 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 × 7) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:389 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:389-397 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:355-363 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:387-395 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:396-404 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:342-350 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:352-360 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:384-392 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs` as WHOLE FILES: this scan already matched 46 separate duplicated blocks between them, totalling at least 456 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:389` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (9 lines × 7) Content/Industrials/ElectricPowers/LifeWeavers/LifeWeaverTile.cs:52 — Content/Industrials/ElectricPowers/LifeWeavers/LifeWeaverTile.cs:52-60 | Content/Industrials/ElectricPowers/LifeWeavers/WGGLifeWeaver.cs:104-112 | Content/Industrials/ElectricPowers/Lumberjacks/LumberjackTile.cs:51-59 | Content/Industrials/ElectricPowers/Lumberjacks/WGGLumberjack.cs:99-107 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatTile.cs:97-105 | Content/Industrials/ElectricPowers/Sundials/ElectricSundialTile.cs:101-109 | Content/Industrials/ElectricPowers/Throwers/ThrowerTile.cs:99-107 — before extracting anything, compare `Content/Industrials/ElectricPowers/LifeWeavers/LifeWeaverTile.cs` and `Content/Industrials/ElectricPowers/LifeWeavers/WGGLifeWeaver.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 63 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/LifeWeavers/LifeWeaverTile.cs:52` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 7) Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzCrystalProj.cs:279 — Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzCrystalProj.cs:279-287 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenChandelierProj.cs:170-179 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenCrystalPrisonProj.cs:180-189 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenCrystalSpireProj.cs:160-169 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenGaleFieldProj.cs:126-135 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenRoyalChandelierProj.cs:178-187 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Rendering/QueenPrismNodeRenderer.cs:74-83 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times. 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 (9 lines × 7) Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs:102 — Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs:102-112 | Content/LegendWeapon/KikasaLegend/TrialQuests/KikasaTrackerWidgetStyle.cs:79-87 | Content/LegendWeapon/OnikiriLegend/TrialQuests/OnikiriTrackerWidgetStyle.cs:70-78 | Content/LegendWeapon/SHPCLegend/TrialQuests/SHPCTrackerWidgetStyle.cs:95-105 | Content/Scenarios/Draedon/Quest/DraedonTrackerWidgetStyle.cs:117-127 | Content/Scenarios/OldDuke/Quest/SulfseaTrackerWidgetStyle.cs:114-123 | Content/Scenarios/SupCal/Quest/BrimstoneTrackerWidgetStyle.cs:109-117 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs:102` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (9 lines × 7) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1484 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1484-1494 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1200-1208 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleCut.cs:337-347 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleRing.cs:241-251 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleScar.cs:252-262 | Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashMark.cs:232-242 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1393-1403 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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.
D4 · Code Duplication · Duplicated block (10–11 lines × 3) · ×7
  • Duplicated block (10–11 lines × 3) Content/GameModes/BrutalMobs/FrostLegion/FrostLegionNPC.cs:419 — Content/GameModes/BrutalMobs/FrostLegion/FrostLegionNPC.cs:419-429 | Content/GameModes/BrutalMobs/Graveyard/GraveyardBrutalNPC.cs:347-356 | Content/GameModes/BrutalMobs/Graveyard/GraveyardBrutalNPC.cs:499-508 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/FrostLegion/FrostLegionNPC.cs:419` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (10–11 lines × 3) Content/GameModes/GodSmith/Accessories/Offense/GodSmithEmblems.cs:255 — Content/GameModes/GodSmith/Accessories/Offense/GodSmithEmblems.cs:255-265 | Content/GameModes/GodSmith/Accessories/Offense/GodSmithManaFlowerChain.cs:231-240 | Content/GameModes/GodSmith/Accessories/Offense/GodSmithQuiverChain.cs:117-126 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Accessories/Offense/GodSmithEmblems.cs:255` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10–11 lines × 3) Content/Items/Ranged/NeutronBows/NeutronBow.cs:384 — Content/Items/Ranged/NeutronBows/NeutronBow.cs:384-393 | Content/Items/Ranged/Thornstrings/ThornstringHeld.cs:298-308 | Content/Items/Ranged/Undertows/UndertowHeld.cs:302-312 — before extracting anything, compare `Content/Items/Ranged/NeutronBows/NeutronBow.cs` and `Content/Items/Ranged/Thornstrings/ThornstringHeld.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 98 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Ranged/NeutronBows/NeutronBow.cs:384` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (10–11 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressPetal.cs:134 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressPetal.cs:134-144 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraSeed.cs:100-109 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenCrystalShard.cs:138-147 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressPetal.cs:134` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (10–11 lines × 3) Content/LegendWeapon/OnikiriLegend/UI/OniItemTooltipPanel.cs:41 — Content/LegendWeapon/OnikiriLegend/UI/OniItemTooltipPanel.cs:41-50 | Content/LegendWeapon/OnikiriLegend/UI/OniRegisterRenderer.cs:42-52 | Content/UIs/UIEffect/OniShaderPanel.cs:35-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. 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 (10–11 lines × 3) Content/NPCs/ScrapCommanders/States/ScrapSawCannonComboState.cs:106 — Content/NPCs/ScrapCommanders/States/ScrapSawCannonComboState.cs:106-115 | Content/NPCs/ScrapCommanders/States/ScrapSawLaunchState.cs:93-103 | Content/NPCs/ScrapCommanders/States/ScrapViceSnatchState.cs:80-90 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/ScrapCommanders/States/ScrapSawCannonComboState.cs:106` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (10–11 lines × 3) Content/Narrative/Presentation/Skins/StarStream/StarStreamDialogueSkin.cs:83 — Content/Narrative/Presentation/Skins/StarStream/StarStreamDialogueSkin.cs:83-92 | Content/Narrative/Presentation/Skins/Sulfsea/SulfseaDialogueSkin.cs:67-76 | Content/Narrative/Presentation/Skins/Tzeentch/TzeentchDialogueSkin.cs:72-82 — before extracting anything, compare `Content/Narrative/Presentation/Skins/Sulfsea/SulfseaDialogueSkin.cs` and `Content/Narrative/Presentation/Skins/Tzeentch/TzeentchDialogueSkin.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Narrative/Presentation/Skins/StarStream/StarStreamDialogueSkin.cs:83` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (9–11 lines × 2) · ×7
  • Duplicated block (9–11 lines × 2) Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaRender.cs:291 — Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaRender.cs:291-299 | Content/NPCs/BrutalNPCs/BrutalPlantera/Rendering/PlanteraBloomRender.cs:112-122 — before extracting anything, compare `Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaRender.cs` and `Content/NPCs/BrutalNPCs/BrutalPlantera/Rendering/PlanteraBloomRender.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaRender.cs:291` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (9–11 lines × 2) Content/Items/Melee/OniMacheteHands.cs:1100 — Content/Items/Melee/OniMacheteHands.cs:1100-1110 | Content/LegendWeapon/HalibutLegend/FishSkills/FishWyverntail.cs:393-401 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/OniMacheteHands.cs:1100` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9–11 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1016 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1016-1026 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:985-993 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs` as WHOLE FILES: this scan already matched 79 separate duplicated blocks between them, totalling at least 1151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9–11 lines × 2) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingPanel.cs:414 — Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingPanel.cs:414-424 | Content/LegendWeapon/SHPCLegend/UI/SHPCModPanel.cs:452-460 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingPanel.cs:414` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9–11 lines × 2) Content/Scenarios/OldDuke/Quest/SulfseaTrackerWidgetStyle.cs:52 — Content/Scenarios/OldDuke/Quest/SulfseaTrackerWidgetStyle.cs:52-62 | Content/Scenarios/SupCal/Quest/BrimstoneTrackerWidgetStyle.cs:55-63 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/SupCal/Quest/BrimstoneTrackerWidgetStyle.cs:55` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Scenarios/SupCal/Quest/BrimstoneTrackerWidgetStyle.cs:54` calls `DrawBorderString`, `Vector2` and `Content/Scenarios/OldDuke/Quest/SulfseaTrackerWidgetStyle.cs:52` does not — after which the two agree again for 4 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–11 lines × 2) Content/Scenarios/OldNet/NPCs/OldNetThreatField.cs:875 — Content/Scenarios/OldNet/NPCs/OldNetThreatField.cs:875-883 | Content/Scenarios/OldNet/OldNetAbsorbFX.cs:26-36 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/OldNet/NPCs/OldNetThreatField.cs:875` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9–11 lines × 2) Content/UIs/NotificationPopup/NotificationPopupSystem.cs:79 — Content/UIs/NotificationPopup/NotificationPopupSystem.cs:79-87 | Content/UIs/NotificationPopup/NotificationPopupSystem.cs:113-123 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/UIs/NotificationPopup/NotificationPopupSystem.cs:79` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (6 lines × 9) · ×7
  • Duplicated block (6 lines × 9) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:385 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:385-390 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs:422-427 | Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:420-425 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs:396-401 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:450-455 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:312-317 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconUI.cs:332-337 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterUI.cs:435-440 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:385-390 — before extracting anything, compare `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs` and `Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 188 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:385` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 9) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1284 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1284-1289 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1683-1688 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1233-1238 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1348-1353 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:1184-1189 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:1453-1458 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1712-1717 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:1157-1162 | Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:2541-2546 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs` as WHOLE FILES: this scan already matched 68 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1284` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 9) Content/Items/Melee/DestroyersBlade.cs:520 — Content/Items/Melee/DestroyersBlade.cs:520-525 | Content/Items/Melee/DragonsScaleGreatsword.cs:543-548 | Content/Items/Melee/EnergySword.cs:559-564 | Content/Items/Melee/RebelBlade.cs:590-595 | Content/Items/Melee/StormGoddessSpears/StormGoddessSpearHeld.cs:530-535 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:525-530 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:799-804 | Content/Items/Stones/Marbles/MarbleClub.cs:592-597 | Content/Items/Stones/Marbles/MarbleHuntingKnife.cs:409-414 — before extracting anything, compare `Content/Items/Melee/DestroyersBlade.cs` and `Content/Items/Melee/DragonsScaleGreatsword.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 419 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DestroyersBlade.cs:520` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 9) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1167 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1167-1172 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:927-932 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1186-1191 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:984-989 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1520-1525 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:989-994 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:888-893 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:948-953 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:921-926 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1167` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 9) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:57 — Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:57-64 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs:77-82 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs:95-102 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainRender.cs:206-211 | Content/Scenarios/Kiame/KiameWakeResetRender.cs:75-80 | Content/Scenarios/Kiame/KiameWakeResetRender.cs:93-100 | Content/Scenarios/Kiame/Overlay/OniRainDescentRender.cs:79-86 | Content/Scenarios/Kiame/Overlay/OniUmbrellaPuddleRender.cs:69-76 | Content/Scenarios/Kiame/Water/KiameWaterRender.cs:118-125 — before extracting anything, compare `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs` and `Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:54` calls `GetRenderTargets` and `Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs:92` 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 (6 lines × 9) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:481 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:481-487 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:200-206 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:402-407 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:426-431 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:533-538 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:540-545 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:467-472 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:403-408 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:471-476 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 9 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 9 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:481` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (6 lines × 9) Content/Buffs/AbyssalPressure.cs:14 — Content/Buffs/AbyssalPressure.cs:14-19 | Content/Buffs/MarblePetrify.cs:17-22 | Content/Buffs/TemporalStasis.cs:13-18 | Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawCorrosionNPC.cs:391-396 | Content/Items/Ranged/Pallbearer.cs:1324-1329 | Content/Items/Ranged/Pallbearer.cs:1348-1353 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiDebuffs.cs:21-26 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiDebuffs.cs:48-53 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiPaperEffigy.cs:360-365 — there are 9 copies across 7 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 9 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (7–9 lines × 2) · ×7
  • Duplicated block (7–9 lines × 2) Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs:375 — Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs:375-383 | Content/LegendWeapon/SHPCLegend/UI/DomainWheel/SHPCDomainWheelUI.cs:392-398 — before extracting anything, compare `Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs` and `Content/LegendWeapon/SHPCLegend/UI/DomainWheel/SHPCDomainWheelUI.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs:375` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7–9 lines × 2) Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs:147 — Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs:147-155 | Content/Scenarios/Helen/Quest/OceanTrackerWidgetStyle.cs:234-240 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs:147` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7–9 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:850 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:850-858 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:901-907 — 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. 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 (7–9 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsHail.cs:81 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsHail.cs:81-87 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressLance.cs:179-187 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsHail.cs:81` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7–9 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:365 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:365-373 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:394-400 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:365` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (7–9 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1449 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1449-1455 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreezeGlobalNPC.cs:105-113 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1449` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7–9 lines × 2) Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersUIs/OceanRaidersRenderer.cs:226 — Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersUIs/OceanRaidersRenderer.cs:226-232 | Content/Scenarios/OldDuke/OldDukeShops/OldDukeShopRenderer.cs:174-182 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersUIs/OceanRaidersRenderer.cs:226` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (6 lines × 15) · ×7
  • Duplicated block (6 lines × 15) Content/GameModes/BrutalMobs/Ambience/Ashreign/Projectiles/AshreignMagmaBeadProj.cs:160 — Content/GameModes/BrutalMobs/Ambience/Ashreign/Projectiles/AshreignMagmaBeadProj.cs:160-165 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhImpFireBolt.cs:78-83 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhScytheBolt.cs:79-84 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhShellSpike.cs:70-75 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhStingerBolt.cs:79-84 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhTridentBolt.cs:78-83 | Content/GameModes/BrutalMobs/Sky/Projectiles/SkyFeatherBolt.cs:72-77 | Content/GameModes/BrutalMobs/SlimeKin/Projectiles/SlimeGelBomb.cs:196-201 | Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadArmProj.cs:571-576 | Content/Items/Magic/AriaofTheCosmoses/AriaQSkill.cs:296-301 | Content/LegendWeapon/HalibutLegend/FishSkills/FishotroningVFX.cs:175-180 | Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Projectiles/BrainBloodShard.cs:122-127 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistSeekerStar.cs:183-188 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistStarBead.cs:174-179 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Projectiles/BrutalBeeStinger.cs:83-88 — before extracting anything, compare `Content/GameModes/BrutalMobs/Ambience/Ashreign/Projectiles/AshreignMagmaBeadProj.cs` and `Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhShellSpike.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/Ashreign/Projectiles/AshreignMagmaBeadProj.cs:160` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Projectiles/BrainBloodShard.cs:118` calls `Clamp`, `Length`, `Vector2` and `Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhImpFireBolt.cs:75` 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 (6 lines × 15) Content/GameModes/BrutalMobs/Ambience/Frostveil/FrostveilPRT.cs:62 — Content/GameModes/BrutalMobs/Ambience/Frostveil/FrostveilPRT.cs:62-68 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDoubleCodVFX.cs:143-149 | Content/LegendWeapon/HalibutLegend/FishSkills/FishIchornVFX.cs:183-189 | Content/LegendWeapon/HalibutLegend/FishSkills/FishSwarmVFX.cs:315-321 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:323-328 | Content/LegendWeapon/KikasaLegend/KikasaWisps/KikasaWispPRT.cs:57-62 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Rendering/BKSParticles.cs:63-69 | Content/PRTTypes/PRT_GhostRainYank.cs:67-72 | Content/PRTTypes/PRT_HeartcarverDroplet.cs:48-54 | Content/PRTTypes/PRT_KikasaInkBead.cs:60-65 | Content/PRTTypes/PRT_KikasaTwinsFlame.cs:71-76 | Content/Scenarios/Dungeonworld/NPCs/GaolFireBolt.cs:273-278 | Content/Scenarios/Dungeonworld/NPCs/OverseerSlagGlob.cs:251-256 | Content/Scenarios/Dungeonworld/NPCs/OverseerVfx.cs:305-310 | Content/Scenarios/Dungeonworld/NPCs/UndrownedTideWave.cs:243-248 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 15 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 15 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/Frostveil/FrostveilPRT.cs:62` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/HalibutLegend/FishSkills/FishIchornVFX.cs:192` calls `Lerp`, `Draw`, `Vector2` and `Content/LegendWeapon/HalibutLegend/FishSkills/FishDoubleCodVFX.cs:152` 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 (6 lines × 15) Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdBoltProj.cs:168 — Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdBoltProj.cs:168-173 | Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs:86-91 | Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgSnowShardProj.cs:88-93 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmNutShellProj.cs:106-111 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmOrnamentProj.cs:85-90 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmPineNeedleProj.cs:67-72 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmSnowballProj.cs:118-123 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmStrafeBulletProj.cs:68-73 | Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyMaggotBolt.cs:120-125 | Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserBoltProj.cs:114-119 | Content/GameModes/BrutalMobs/Martians/Projectiles/MrtWrenchProj.cs:172-177 | Content/Items/BloomArsenal.cs:121-126 | Content/NPCs/BloomsandSerpents/Projectiles/BssPetalProj.cs:81-86 | Content/NPCs/BloomsandSerpents/Projectiles/BssWindPetalProj.cs:100-105 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordBoltProj.cs:123-128 — before extracting anything, compare `Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdBoltProj.cs` and `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdBoltProj.cs:168` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs:82` calls `Lerp`, `Color` and `Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmNutShellProj.cs:102` does not — after which the two agree again for 3 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 (6 lines × 15) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:473 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:473-478 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs:538-543 | Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:537-542 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs:513-518 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:571-576 | Content/Industrials/ElectricPowers/Launchers/PlayerLauncherUI.cs:402-407 | Content/Industrials/ElectricPowers/MiningMachines/MiningMachineUI.cs:779-784 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:390-395 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconUI.cs:428-433 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterUI.cs:535-540 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:471-476 | Content/Industrials/ElectricPowers/Turrets/TurretControlUI.cs:384-389 | Content/Industrials/Generator/Biomass/BiomassGeneratorUI.cs:373-378 | Content/Industrials/Generator/GeneratorReadout.cs:353-358 | Content/Industrials/Generator/Thermal/ThermalGeneratorUI.cs:513-518 — before extracting anything, compare `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs` and `Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 188 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:473` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6 lines × 15) Content/Items/Accessories/ArcaneThroneOfEternity.cs:185 — Content/Items/Accessories/ArcaneThroneOfEternity.cs:185-191 | Content/Items/Accessories/ArcaneThroneOfEternity.cs:332-337 | Content/Items/Accessories/ArcaneThroneOfEternity.cs:463-468 | Content/LegendWeapon/HalibutLegend/DomainSkills/SeaDomain.cs:681-688 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutDomain.cs:322-328 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDetonationProj.cs:212-218 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberShockwaveProj.cs:99-105 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberFreezeWaveProj.cs:93-99 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberPixelDecomposeProj.cs:92-98 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberReformProj.cs:98-104 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/HeavyBarrelModule.cs:324-330 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/HypersonicBarrelModule.cs:217-223 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/ScattershotBarrelModule.cs:390-396 | Content/LegendWeapon/SHPCLegend/Modules/Power/PlasmaInjectorModule.cs:174-180 | Content/LegendWeapon/SHPCLegend/Modules/Stock/ExtenderStockModule.cs:442-448 — there are 15 copies across 13 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 15 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/ArcaneThroneOfEternity.cs:185` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberShockwaveProj.cs:110` calls `ShouldUpdatePosition` and `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDetonationProj.cs:222` 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 (6 lines × 15) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:489 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:489-494 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:466-471 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:388-393 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:445-450 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:344-349 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:337-342 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:411-416 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:405-410 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:448-453 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:518-523 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:526-531 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:454-459 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:389-394 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:407-412 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:456-461 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 15 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 15 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:489` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:476` calls `NextFloat` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:499` 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 (6 lines × 15) Content/GameModes/BrutalMobs/Ambience/Duskhall/DuskhallAmbience.cs:588 — Content/GameModes/BrutalMobs/Ambience/Duskhall/DuskhallAmbience.cs:588-593 | Content/GameModes/BrutalMobs/Ambience/Verdant/VerdantAmbientRender.cs:82-87 | Content/Items/Accessories/BrutalRelics/WallOfFlesh/GluttonousRetinaRender.cs:86-91 | Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Core/BrainMotion.cs:56-61 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Core/DeerclopsMotion.cs:195-200 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerMotionFX.cs:267-272 | Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerDespawnState.cs:462-467 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Rendering/FishronMotionFX.cs:166-171 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Rendering/EowMotionFX.cs:49-54 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Core/EocMotion.cs:248-253 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Rendering/KingSlimeGelFX.cs:47-52 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Core/CultistMotion.cs:201-206 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsDeathState.cs:255-260 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Rendering/WofMotionFX.cs:21-26 | Content/Scenarios/Dungeonworld/Ambience/DungeonworldAmbientFX.cs:267-272 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 15 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 15 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Edited copies of one member (3 members, 32+ corresponding lines) · ×6
  • Edited copies of one member (3 members, 32+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:439 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:439-478 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:388-419 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:435-470 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 32 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 32+ corresponding lines) Content/LegendWeapon/OnikiriLegend/UI/OniMeiStandDraw.cs:16 — Content/LegendWeapon/OnikiriLegend/UI/OniMeiStandDraw.cs:16-47 | Content/LegendWeapon/OnikiriLegend/UI/OniStanceBladeDraw.cs:32-66 | Content/LegendWeapon/OnikiriLegend/UI/OniVigorInkDraw.cs:32-65 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 32 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 32+ corresponding lines) Content/Industrials/ElectricPowers/MiningMachines/BaseMiningMachineTP.cs:408 — Content/Industrials/ElectricPowers/MiningMachines/BaseMiningMachineTP.cs:408-439 | Content/Industrials/ElectricPowers/WeatherControllers/WeatherControllerTile.cs:102-135 | Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersTile.cs:51-89 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 32 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 32+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:455 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:455-491 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:373-404 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:414-447 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 32 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 32+ corresponding lines) Content/NPCs/BloomsandSerpents/States/BssSandDashState.cs:91 — Content/NPCs/BloomsandSerpents/States/BssSandDashState.cs:91-122 | Content/NPCs/BloomsandSerpents/States/BssTailSweepState.cs:99-130 | Content/NPCs/FestersandSerpents/States/FssVenomSkimState.cs:86-117 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 32 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 32+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsFrostQuakeState.cs:26 — Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsFrostQuakeState.cs:26-65 | Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsSpikeCageState.cs:25-56 | Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsSpikeWaveState.cs:25-60 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 32 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 27+ corresponding lines) · ×6
  • Edited copies of one member (3 members, 27+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:163 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:163-190 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:164-193 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:146-172 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 27 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 27+ corresponding lines) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:161 — Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:161-187 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs:151-177 | Content/Scenarios/Kiame/KiameWakeResetRender.cs:147-173 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 27 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 27+ corresponding lines) Content/Scenarios/Draedon/ExoMechdusaSums/ExoMechdusaSumRender.cs:466 — Content/Scenarios/Draedon/ExoMechdusaSums/ExoMechdusaSumRender.cs:466-492 | Content/Scenarios/Draedon/ExoMechdusaSums/ExoMechdusaSumRender.cs:523-549 | Content/Scenarios/Draedon/Quest/DeploySignaltowers/DeploySignaltowerRender.cs:627-653 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 27 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 27+ corresponding lines) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterStorageProvider.cs:83 — Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterStorageProvider.cs:83-119 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerStorageProvider.cs:68-94 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatStorageProvider.cs:68-94 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 27 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 27+ corresponding lines) Content/Industrials/ElectricPowers/Throwers/ThrowerStorageProvider.cs:146 — Content/Industrials/ElectricPowers/Throwers/ThrowerStorageProvider.cs:146-175 | Content/Industrials/ElectricPowers/Throwers/ThrowerTP.cs:186-212 | Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersStorageProvider.cs:143-171 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 27 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 27+ corresponding lines) Content/NPCs/BloomsandSerpents/States/BssPillarSpikeState.cs:42 — Content/NPCs/BloomsandSerpents/States/BssPillarSpikeState.cs:42-69 | Content/NPCs/FestersandSerpents/States/FssClawQuakeState.cs:38-66 | Content/NPCs/FestersandSerpents/States/FssClawSlamState.cs:44-70 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 27 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 23+ corresponding lines) · ×6
  • Edited copies of one member (3 members, 23+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishDoubleCodVFX.cs:143 — Content/LegendWeapon/HalibutLegend/FishSkills/FishDoubleCodVFX.cs:143-165 | Content/LegendWeapon/HalibutLegend/FishSkills/FishHoneyVFX.cs:179-203 | Content/LegendWeapon/HalibutLegend/FishSkills/FishSwarmVFX.cs:315-339 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 23+ corresponding lines) Content/LegendWeapon/HalibutLegend/UI/HalibutItemTooltipPanel.cs:27 — Content/LegendWeapon/HalibutLegend/UI/HalibutItemTooltipPanel.cs:27-49 | Content/LegendWeapon/OnikiriLegend/UI/OniItemTooltipPanel.cs:28-54 | Content/LegendWeapon/SHPCLegend/UI/SHPCItemTooltipPanel.cs:30-52 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 23+ corresponding lines) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDataArcProj.cs:109 — Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDataArcProj.cs:109-131 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/MoondewBarrelModule.cs:270-292 | Content/LegendWeapon/SHPCLegend/Modules/Power/HighVoltageCoreModule.cs:227-253 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 23+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:99 — Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:99-128 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowBurrowAmbushState.cs:95-117 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowDevourState.cs:314-336 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 23+ corresponding lines) Content/GameModes/BrutalMobs/Ambience/Bloodveil/BloodveilAmbience.cs:46 — Content/GameModes/BrutalMobs/Ambience/Bloodveil/BloodveilAmbience.cs:46-68 | Content/GameModes/BrutalMobs/Ambience/Duskwatch/DuskwatchAmbience.cs:44-66 | Content/GameModes/BrutalMobs/Ambience/Rainveil/RainveilAmbience.cs:42-69 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 23+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalGolem/GolemBodyAI.cs:349 — Content/NPCs/BrutalNPCs/BrutalGolem/GolemBodyAI.cs:349-371 | Content/NPCs/BrutalNPCs/BrutalSkeletron/SkeletronHeadAI.cs:299-321 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/HeadPrimeAI.cs:652-679 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 19+ corresponding lines) · ×6
  • Edited copies of one member (4 members, 19+ corresponding lines) Content/NPCs/BloomsandSerpents/BssBody.cs:301 — Content/NPCs/BloomsandSerpents/BssBody.cs:301-324 | Content/NPCs/BloomsandSerpents/BssHead.cs:795-816 | Content/NPCs/FestersandSerpents/FssBody.cs:353-373 | Content/NPCs/FestersandSerpents/FssHead.cs:790-808 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 19+ corresponding lines) Content/Items/Melee/GeminisTribute.cs:33 — Content/Items/Melee/GeminisTribute.cs:33-52 | Content/Items/Melee/Heartcarver.cs:45-63 | Content/Items/Melee/Observer.cs:26-45 | Content/Items/Melee/SporeboundRoller.cs:29-47 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 19+ corresponding lines) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterTP.cs:602 — Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterTP.cs:602-620 | Content/Industrials/ElectricPowers/Crushers/CrusherTP.cs:469-490 | Content/Industrials/ElectricPowers/Incinerators/IncineratorTP.cs:357-379 | Content/Industrials/ElectricPowers/Recyclers/RecyclerTP.cs:504-525 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 19+ corresponding lines) Content/QuestLogs/QLNodes/IndustrialQuests.cs:28 — Content/QuestLogs/QLNodes/IndustrialQuests.cs:28-46 | Content/QuestLogs/QLNodes/IndustrialQuests.cs:57-75 | Content/QuestLogs/QLNodes/IndustrialQuests.cs:112-130 | Content/QuestLogs/QLNodes/IndustrialQuests.cs:141-159 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 19+ corresponding lines) Content/QuestLogs/QLNodes/BossQuests.cs:60 — Content/QuestLogs/QLNodes/BossQuests.cs:60-78 | Content/QuestLogs/QLNodes/BossQuests.cs:117-140 | Content/QuestLogs/QLNodes/BossQuests.cs:153-171 | Content/QuestLogs/QLNodes/BossQuests.cs:279-302 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 19+ corresponding lines) Content/QuestLogs/QLNodes/AdventurerQuests.cs:548 — Content/QuestLogs/QLNodes/AdventurerQuests.cs:548-566 | Content/QuestLogs/QLNodes/AdventurerQuests.cs:578-597 | Content/QuestLogs/QLNodes/AdventurerQuests.cs:608-626 | Content/QuestLogs/QLNodes/AdventurerQuests.cs:638-656 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 13+ corresponding lines) · ×6
  • Edited copies of one member (5 members, 13+ corresponding lines) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:89 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:89-104 | Content/Industrials/ElectricPowers/Launchers/PlayerLauncherUI.cs:93-105 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:83-95 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconUI.cs:84-97 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:91-106 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 13+ corresponding lines) Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:566 — Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:566-578 | Content/GameModes/GodSmith/Weapons/Shortswords/GsThrustHeldBase.cs:980-992 | Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:602-614 | Content/Items/Modifys/RBloodButcherer.cs:545-557 | Content/Items/Modifys/RTerraBlades/RTerraBladeHeld.cs:709-722 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 13+ corresponding lines) Content/Scenarios/Dungeonworld/Gen/LayerTint.cs:64 — Content/Scenarios/Dungeonworld/Gen/LayerTint.cs:64-79 | Content/Scenarios/Dungeonworld/Gen/Layers/L7/L7InvertedCathedral.cs:177-189 | Content/Scenarios/Dungeonworld/Gen/Layers/L7/L7Style.cs:223-235 | Content/Scenarios/Dungeonworld/Gen/Layers/L7/L7Style.cs:241-256 | Content/Scenarios/OldNet/Gen/Passes/OldNetValidatePass.cs:134-147 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 13+ corresponding lines) Content/Scenarios/Shepel/CybCourses/CybCourseCompletePanel.cs:126 — Content/Scenarios/Shepel/CybCourses/CybCourseCompletePanel.cs:126-138 | Content/Scenarios/Shepel/CybCourses/CybCourseKeyBindReminderPanel.cs:166-178 | Content/Scenarios/Shepel/CybCourses/CybTutorialLead.cs:285-297 | Content/Scenarios/Shepel/CybCourses/HackTimeTutorialLead.cs:411-423 | Content/Scenarios/Shepel/CybCourses/WheelTutorialLead.cs:266-278 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 13+ corresponding lines) Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzBeamProj.cs:57 — Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzBeamProj.cs:57-69 | Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzCrystalProj.cs:56-68 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCrimsonTiger.cs:188-202 | Content/LegendWeapon/HalibutLegend/FishSkills/FishNeonTetra.cs:117-130 | Content/LegendWeapon/HalibutLegend/FishSkills/FishPrincess.cs:150-163 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 13+ corresponding lines) Content/GameModes/BrutalMobs/FrostMoon/FrmMeleeNPC.cs:163 — Content/GameModes/BrutalMobs/FrostMoon/FrmMeleeNPC.cs:163-177 | Content/GameModes/BrutalMobs/FrostMoon/FrmMiniBossNPC.cs:123-137 | Content/GameModes/BrutalMobs/FrostMoon/FrmSiegeNPC.cs:119-133 | Content/GameModes/BrutalMobs/NightPack/NightPackNPC.cs:90-102 | Content/GameModes/BrutalMobs/Pirates/PirateCrewNPC.cs:113-127 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 17+ corresponding lines) · ×6
  • Edited copies of one member (4 members, 17+ corresponding lines) Content/UIs/UIEffect/CircuitNodePRT.cs:26 — Content/UIs/UIEffect/CircuitNodePRT.cs:26-42 | Content/UIs/UIEffect/HeroUnitPRT.cs:33-51 | Content/UIs/UIEffect/NeonMaidPRT.cs:33-50 | Content/UIs/UIEffect/StarDustPRT.cs:24-42 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 17+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsSpikeWaveState.cs:75 — Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsSpikeWaveState.cs:75-92 | Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsSpikeWaveState.cs:95-116 | Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsSpikeWaveState.cs:119-135 | Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsWhiteoutState.cs:116-134 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 17+ corresponding lines) Content/QuestLogs/Styles/Chronicle/ChronicleQuestLogStyle.cs:402 — Content/QuestLogs/Styles/Chronicle/ChronicleQuestLogStyle.cs:402-423 | Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:693-710 | Content/QuestLogs/Styles/ForestQuestLogStyle.cs:648-664 | Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:576-593 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 17+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalGolem/GolemBodyAI.cs:162 — Content/NPCs/BrutalNPCs/BrutalGolem/GolemBodyAI.cs:162-178 | Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordCoreAI.cs:154-171 | Content/NPCs/BrutalNPCs/BrutalSkeletron/SkeletronHeadAI.cs:137-153 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/HeadPrimeAI.cs:222-239 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 17+ corresponding lines) Content/Items/Ranged/NeutronBows/NeutronBow.cs:35 — Content/Items/Ranged/NeutronBows/NeutronBow.cs:35-52 | Content/Items/Ranged/NeutronGun.cs:33-49 | Content/Items/Ranged/Thornstrings/Thornstring.cs:20-39 | Content/Items/Ranged/Undertows/Undertow.cs:20-39 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 17+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuLin.cs:75 — Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuLin.cs:75-91 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuSha.cs:55-78 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuShu.cs:72-88 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuYu.cs:65-81 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 15+ corresponding lines) · ×6
  • Edited copies of one member (5 members, 15+ corresponding lines) Content/Scenarios/Shepel/Dialogues/Situational/ShepelDungeonDialogue.cs:42 — Content/Scenarios/Shepel/Dialogues/Situational/ShepelDungeonDialogue.cs:42-57 | Content/Scenarios/Shepel/Dialogues/Situational/ShepelFirstNightDialogue.cs:44-58 | Content/Scenarios/Shepel/Dialogues/Situational/ShepelJungleDialogue.cs:42-57 | Content/Scenarios/Shepel/Dialogues/Situational/ShepelOceanDialogue.cs:42-57 | Content/Scenarios/Shepel/Dialogues/Situational/ShepelUnderworldDialogue.cs:42-57 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 15+ corresponding lines) Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFistProj.cs:144 — Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFistProj.cs:144-158 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:696-713 | Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallMeltFX.cs:394-411 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/PrimeViceExecutionState.cs:153-167 | Content/Scenarios/Kiame/KasaOnis/KasaOniActor.cs:887-904 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 15+ corresponding lines) Content/QuestLogs/QLNodes/OmigaQuests.cs:244 — Content/QuestLogs/QLNodes/OmigaQuests.cs:244-258 | Content/QuestLogs/QLNodes/OmigaQuests.cs:272-286 | Content/QuestLogs/QLNodes/OmigaQuests.cs:300-314 | Content/QuestLogs/QLNodes/OmigaQuests.cs:328-342 | Content/QuestLogs/QLNodes/OmigaQuests.cs:356-370 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 15+ corresponding lines) Content/QuestLogs/QLNodes/OmigaQuests.cs:40 — Content/QuestLogs/QLNodes/OmigaQuests.cs:40-54 | Content/QuestLogs/QLNodes/OmigaQuests.cs:68-82 | Content/QuestLogs/QLNodes/OmigaQuests.cs:96-110 | Content/QuestLogs/QLNodes/OmigaQuests.cs:124-138 | Content/QuestLogs/QLNodes/OmigaQuests.cs:152-166 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 15+ corresponding lines) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:134 — Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:134-150 | Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:117-131 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:123-137 | Content/Industrials/ElectricPowers/Recyclers/RecyclerUI.cs:118-132 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterUI.cs:121-135 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 15+ corresponding lines) Content/GameModes/GodSmith/Weapons/Broadswords/GsIceBlade.cs:43 — Content/GameModes/GodSmith/Weapons/Broadswords/GsIceBlade.cs:43-57 | Content/GameModes/GodSmith/Weapons/Broadswords/GsLightsBane.cs:46-60 | Content/GameModes/GodSmith/Weapons/Broadswords/GsMandibleBlade.cs:55-73 | Content/GameModes/GodSmith/Weapons/Broadswords/GsPurpleClubberfish.cs:53-71 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsIceSickle.cs:57-72 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 10+ corresponding lines) · ×6
  • Edited copies of one member (5 members, 10+ corresponding lines) Content/Industrials/ElectricPowers/WireInterfaces/WireInterfaceTile.cs:19 — Content/Industrials/ElectricPowers/WireInterfaces/WireInterfaceTile.cs:19-31 | Content/Industrials/MaterialFlow/Fluids/FluidPipeline.cs:44-56 | Content/Industrials/MaterialFlow/ItemPipelines/ItemPipeline.cs:39-48 | Content/Industrials/MaterialFlow/Pipelines/CreativeUEPipeline.cs:45-54 | Content/Industrials/MaterialFlow/Pipelines/UEPipeline.cs:56-65 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 10+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishCatVFX.cs:56 — Content/LegendWeapon/HalibutLegend/FishSkills/FishCatVFX.cs:56-65 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDoubleCodVFX.cs:90-99 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Core/EocMotion.cs:202-211 | Content/Scenarios/Kiyume/NPCs/FuneralCortegeYokai.cs:1154-1165 | Content/Scenarios/Kiyume/NPCs/LanternGuideYokai.cs:426-437 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 10+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:120 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:120-130 | Content/LegendWeapon/KikasaLegend/KikasaTeleports/KikasaTeleportProj.cs:115-125 | Content/Wraiths/Projectiles/GhostRainProj.cs:66-76 | Content/Wraiths/Projectiles/LanternBoyProj.cs:81-91 | Content/Wraiths/Runtime/WraithNet.cs:913-922 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 10+ corresponding lines) Content/HackTimes/Protocols/TileConscript.cs:143 — Content/HackTimes/Protocols/TileConscript.cs:143-154 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:76-85 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaMiniBloodSlime.cs:66-75 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs:89-98 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:175-185 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 10+ corresponding lines) Content/GameModes/GodSmith/Weapons/Guns/GsBoomstick.cs:127 — Content/GameModes/GodSmith/Weapons/Guns/GsBoomstick.cs:127-137 | Content/GameModes/GodSmith/Weapons/Guns/GsFlareGun.cs:132-142 | Content/GameModes/GodSmith/Weapons/Guns/GsHarpoon.cs:150-160 | Content/GameModes/GodSmith/Weapons/Guns/GunsEarlyShared.cs:486-496 | Content/Items/Ranged/CrystalDimming.cs:432-441 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 10+ corresponding lines) Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs:352 — Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs:352-361 | Content/Industrials/ElectricPowers/Launchers/PlayerLauncherUI.cs:262-272 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconUI.cs:283-292 | Content/Industrials/ElectricPowers/Sensors/SensorUI.cs:259-268 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:292-302 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 8+ corresponding lines) · ×6
  • Edited copies of one member (6 members, 8+ corresponding lines) Content/Scenarios/Helen/Gifts/AquaticScourgeGift.cs:31 — Content/Scenarios/Helen/Gifts/AquaticScourgeGift.cs:31-38 | Content/Scenarios/Helen/Gifts/EyeOfCthulhuGift.cs:31-38 | Content/Scenarios/Helen/Gifts/MoonLordGift.cs:31-38 | Content/Scenarios/Helen/Gifts/PlaguebringerGift.cs:31-38 | Content/Scenarios/Helen/Gifts/PlanteraGift.cs:31-38 | Content/Scenarios/Helen/Gifts/YharonGift.cs:31-38 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 8+ corresponding lines) Content/GameModes/BrutalMobs/Ambience/Astralveil/Projectiles/AstralveilSpearMarkProj.cs:165 — Content/GameModes/BrutalMobs/Ambience/Astralveil/Projectiles/AstralveilSpearMarkProj.cs:165-174 | Content/GameModes/BrutalMobs/Ambience/Brinefume/Projectiles/BrinefumeBoilZoneProj.cs:152-159 | Content/GameModes/GodSmith/Weapons/MagicCataclysm/Projectiles/GsOrogenyDirector.cs:68-76 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:173-184 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpGeyserSpout.cs:121-129 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpWaveCrest.cs:127-135 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 8+ corresponding lines) Content/Scenarios/Dungeonworld/NPCs/ProofSealCharm.cs:36 — Content/Scenarios/Dungeonworld/NPCs/ProofSealCharm.cs:36-43 | Content/Scenarios/Dungeonworld/NPCs/ProofSealCharm.cs:46-54 | Content/Scenarios/Dungeonworld/NPCs/RustedGaolIrons.cs:83-90 | Content/Scenarios/Dungeonworld/NPCs/RustedGaolIrons.cs:93-101 | Content/Scenarios/Dungeonworld/NPCs/UndrownedShackleCharm.cs:41-48 | Content/Scenarios/Dungeonworld/NPCs/UndrownedShackleCharm.cs:51-59 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 8+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Core/BrainMotion.cs:46 — Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Core/BrainMotion.cs:46-53 | Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerDespawnState.cs:452-459 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Core/TwinsMotion.cs:106-113 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsDeathState.cs:245-252 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Core/QueenBeeMotion.cs:65-72 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Core/QueenMotion.cs:123-130 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 8+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainFrenzyChaseState.cs:99 — Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainFrenzyChaseState.cs:99-106 | Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainHeartAttackState.cs:214-221 | Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainMirrorFeintState.cs:184-191 | Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainMirrorMazeState.cs:193-200 | Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainMirrorStrikeState.cs:92-99 | Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainOrbitCageState.cs:183-190 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 8+ corresponding lines) Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordScheme.cs:61 — Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordScheme.cs:61-68 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsOdditiesComboScheme.cs:52-59 | Content/GameModes/GodSmith/Weapons/Shortswords/GsThrustHeldBase.cs:62-70 | Content/GameModes/GodSmith/Weapons/_Exemplars/GsIronBroadsword.cs:51-58 | Content/Items/Modifys/RBloodButcherer.cs:69-76 | Content/Items/Modifys/RTerraBlades/RTerraBlade.cs:73-80 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (26 lines × 2) · ×6
  • Duplicated block (26 lines × 2) Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:749 — Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:749-774 | Content/Items/Melee/WeaverGrievanceses/WGManifestationActor.cs:641-666 — before extracting anything, compare `Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs` and `Content/Items/Melee/WeaverGrievanceses/WGManifestationActor.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 237 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:749` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (26 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownRender.cs:17 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownRender.cs:17-42 | Content/LegendWeapon/OnikiriLegend/OniDismembers/OniDismemberRender.cs:38-63 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownRender.cs` and `Content/LegendWeapon/OnikiriLegend/OniDismembers/OniDismemberRender.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownRender.cs:17` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (26 lines × 2) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs:43 — Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs:43-68 | Content/NPCs/FestersandSerpents/Projectiles/FssIchorGlob.cs:43-68 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs` and `Content/NPCs/FestersandSerpents/Projectiles/FssIchorGlob.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 149 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs:43` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (26 lines × 2) Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSim.cs:142 — Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSim.cs:142-167 | Content/Scenarios/Kiyume/Fog/KiyumeFogSim.cs:212-237 — before extracting anything, compare `Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSim.cs` and `Content/Scenarios/Kiyume/Fog/KiyumeFogSim.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 174 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (26 lines × 2) Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:83 — Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:83-108 | Content/Scenarios/Kiyume/UI/KiyumeLoadingScreen.cs:89-114 — before extracting anything, compare `Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs` and `Content/Scenarios/Kiyume/UI/KiyumeLoadingScreen.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 214 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (26 lines × 2) Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:590 — Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:590-615 | Content/Scenarios/Kiyume/UI/KiyumeLoadingScreen.cs:530-555 — before extracting anything, compare `Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs` and `Content/Scenarios/Kiyume/UI/KiyumeLoadingScreen.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 214 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:590` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (22–23 lines × 2) · ×6
  • Duplicated block (22–23 lines × 2) Content/GameModes/GodSmith/Armors/Hardmode/GsForbiddenArmor.cs:46 — Content/GameModes/GodSmith/Armors/Hardmode/GsForbiddenArmor.cs:46-68 | Content/GameModes/GodSmith/Armors/Hardmode/GsSpookyWoodArmor.cs:46-67 — before extracting anything, compare `Content/GameModes/GodSmith/Armors/Hardmode/GsForbiddenArmor.cs` and `Content/GameModes/GodSmith/Armors/Hardmode/GsSpookyWoodArmor.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Armors/Hardmode/GsForbiddenArmor.cs:46` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22–23 lines × 2) Content/GameModes/GodSmith/Armors/Reset/GsCrimsonArmor.cs:70 — Content/GameModes/GodSmith/Armors/Reset/GsCrimsonArmor.cs:70-92 | Content/GameModes/GodSmith/Armors/Reset/GsOreArmorsHardmode.cs:332-353 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Armors/Reset/GsCrimsonArmor.cs:70` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/GodSmith/Armors/Reset/GsOreArmorsHardmode.cs:328` calls `GetAlpha`, `Color` and `Content/GameModes/GodSmith/Armors/Reset/GsCrimsonArmor.cs:66` does not — after which the two agree again for 3 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 (22–23 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:92 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:92-114 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterGlob.cs:95-116 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterGlob.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 117 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:92` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:116` calls `SplashBurst`, `SpawnMist` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterGlob.cs:118` 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 (22–23 lines × 2) Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:173 — Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:173-195 | Content/Scenarios/Kiyume/UI/KiyumeLoadingScreen.cs:184-205 — before extracting anything, compare `Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs` and `Content/Scenarios/Kiyume/UI/KiyumeLoadingScreen.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 214 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:173` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:172` calls `Clamp`, `Lerp` and `Content/Scenarios/Kiyume/UI/KiyumeLoadingScreen.cs:184` does not — after which the two agree again for 4 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 (22–23 lines × 2) Content/Scenarios/Shepel/CybCourses/HackTimeTutorialLead.cs:457 — Content/Scenarios/Shepel/CybCourses/HackTimeTutorialLead.cs:457-478 | Content/Scenarios/Shepel/CybCourses/WheelTutorialLead.cs:300-322 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Shepel/CybCourses/HackTimeTutorialLead.cs:457` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22–23 lines × 2) Content/Wraiths/Projectiles/GhostHandProj.cs:661 — Content/Wraiths/Projectiles/GhostHandProj.cs:661-683 | Content/Wraiths/Projectiles/GhostHandProj.cs:716-737 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Wraiths/Projectiles/GhostHandProj.cs:661` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (18 lines × 3) · ×6
  • Duplicated block (18 lines × 3) Content/Industrials/Generator/Biomass/BiomassStorageProvider.cs:177 — Content/Industrials/Generator/Biomass/BiomassStorageProvider.cs:177-194 | Content/Industrials/Generator/Thermal/ThermalStorageProvider.cs:193-210 | Content/Industrials/Generator/Thermal/ThermalStorageProvider.cs:433-450 — before extracting anything, compare `Content/Industrials/Generator/Biomass/BiomassStorageProvider.cs` and `Content/Industrials/Generator/Thermal/ThermalStorageProvider.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/Generator/Biomass/BiomassStorageProvider.cs:177` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (18 lines × 3) Content/PRTTypes/PRT_BanishGlitch.cs:113 — Content/PRTTypes/PRT_BanishGlitch.cs:113-130 | Content/PRTTypes/PRT_CyberConverge.cs:94-111 | Content/PRTTypes/PRT_CyberSquare.cs:55-72 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/PRTTypes/PRT_BanishGlitch.cs:113` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (18 lines × 3) Content/EntrustManager/Styles/DraedonManagerStyle.cs:553 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:553-570 | Content/EntrustManager/Styles/ForestManagerStyle.cs:562-579 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:551-568 — before extracting anything, compare `Content/EntrustManager/Styles/DraedonManagerStyle.cs` and `Content/EntrustManager/Styles/ForestManagerStyle.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 334 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/EntrustManager/Styles/DraedonManagerStyle.cs:553` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 3) Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:301 — Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:301-318 | Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:207-224 | Content/Items/Modifys/RBloodButcherer.cs:246-263 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:301` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 3) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:163 — Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:163-180 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs:153-170 | Content/Scenarios/Kiame/KiameWakeResetRender.cs:149-166 — before extracting anything, compare `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs` and `Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:163` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:138 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:138-155 | Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs:208-225 | Content/Scenarios/Kiame/Overlay/OniRainWorldRender.cs:144-161 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs` and `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 192 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (14–15 lines × 3) · ×6
  • Duplicated block (14–15 lines × 3) Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:459 — Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:459-472 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:492-506 | Content/Industrials/ElectricPowers/Recyclers/RecyclerUI.cs:420-433 — before extracting anything, compare `Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs` and `Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 303 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:459` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14–15 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:983 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:983-996 | Content/LegendWeapon/KikasaLegend/KikasaVaults/KikasaLakeFX.cs:577-591 | Content/LegendWeapon/KikasaLegend/KikasaVaults/KikasaLakeFX.cs:612-625 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:983` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14–15 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:316 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:316-330 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:400-413 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:318-331 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs` as WHOLE FILES: this scan already matched 48 separate duplicated blocks between them, totalling at least 508 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:316` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (14–15 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:941 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:941-955 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1253-1266 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:822-835 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:941` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14–15 lines × 3) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:326 — Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:326-339 | Content/LegendWeapon/SHPCLegend/UI/SHPCModPanel.cs:382-396 | Content/LegendWeapon/SHPCLegend/UI/SHPCModuleSelectPanel.cs:343-357 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:326` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (14–15 lines × 3) Content/Items/Magic/Elysiums/Revelations/CelestialMeteor.cs:161 — Content/Items/Magic/Elysiums/Revelations/CelestialMeteor.cs:161-175 | Content/Items/Magic/Elysiums/Revelations/RevelationDomain.cs:126-139 | Content/Items/Magic/Elysiums/Serpents/SnakeConversionWave.cs:196-210 — before extracting anything, compare `Content/Items/Magic/Elysiums/Revelations/RevelationDomain.cs` and `Content/Items/Magic/Elysiums/Serpents/SnakeConversionWave.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/Elysiums/Revelations/CelestialMeteor.cs:161` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Magic/Elysiums/Revelations/CelestialMeteor.cs:161` calls `End` and `Content/Items/Magic/Elysiums/Serpents/SnakeConversionWave.cs:196` 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.
D4 · Code Duplication · Duplicated block (13–15 lines × 2) · ×6
  • Duplicated block (13–15 lines × 2) Content/HackTimes/HackEffectNPC.cs:191 — Content/HackTimes/HackEffectNPC.cs:191-203 | Content/LegendWeapon/SHPCLegend/Cyberspaces/SHPCNPCEffects.cs:619-633 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (13–15 lines × 2) Content/LegendWeapon/HalibutLegend/DomainSkills/RestartFish.cs:455 — Content/LegendWeapon/HalibutLegend/DomainSkills/RestartFish.cs:455-467 | Content/LegendWeapon/HalibutLegend/DomainSkills/Superposition.cs:485-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 (13–15 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaCavitationOrb.cs:62 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaCavitationOrb.cs:62-74 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpCavitationBubble.cs:56-70 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (13–15 lines × 2) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:104 — Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:104-118 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowBurrowAmbushState.cs:97-109 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs` and `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowBurrowAmbushState.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 70 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:104` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `context` to `DestroyerStateContext` in one and `EowStateContext` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (13–15 lines × 2) Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocFeintDashState.cs:159 — Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocFeintDashState.cs:159-173 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocMawDragState.cs:230-242 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocFeintDashState.cs:159` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (13–15 lines × 2) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsCombinedAttackState.cs:214 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsCombinedAttackState.cs:214-228 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsCrossDashState.cs:157-169 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsCombinedAttackState.cs:214` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11–13 lines × 2) · ×6
  • Duplicated block (11–13 lines × 2) Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT1.cs:298 — Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT1.cs:298-310 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT3.cs:182-192 — before extracting anything, compare `Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT1.cs` and `Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT3.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 89 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT1.cs:298` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (11–13 lines × 2) Content/Industrials/Generator/Biomass/BiomassGeneratorUI.cs:258 — Content/Industrials/Generator/Biomass/BiomassGeneratorUI.cs:258-268 | Content/Industrials/Generator/Thermal/ThermalGeneratorUI.cs:375-387 — before extracting anything, compare `Content/Industrials/Generator/Biomass/BiomassGeneratorUI.cs` and `Content/Industrials/Generator/Thermal/ThermalGeneratorUI.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 156 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/Generator/Biomass/BiomassGeneratorUI.cs:258` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11–13 lines × 2) Content/Items/Accessories/BrutalRelics/EyeOfCthulhu/BloodfogVeilProj.cs:251 — Content/Items/Accessories/BrutalRelics/EyeOfCthulhu/BloodfogVeilProj.cs:251-263 | Content/Items/Accessories/BrutalRelics/EyeOfCthulhu/BloodfogVeilProj.cs:399-409 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/EyeOfCthulhu/BloodfogVeilProj.cs:251` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11–13 lines × 2) Content/Items/Accessories/BrutalRelics/Twins/PRT_TwinPupilSpark.cs:51 — Content/Items/Accessories/BrutalRelics/Twins/PRT_TwinPupilSpark.cs:51-61 | Content/PRTTypes/PRT_TwinsSpark.cs:49-61 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/Twins/PRT_TwinPupilSpark.cs:51` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11–13 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:101 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:101-113 | Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs:120-130 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs` and `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 192 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs:120` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11–13 lines × 2) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/HeadPrimeAI.cs:771 — Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/HeadPrimeAI.cs:771-783 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/PrimeViceAI.cs:66-76 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/HeadPrimeAI.cs:771` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (11–12 lines × 4) · ×6
  • Duplicated block (11–12 lines × 4) Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:307 — Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:307-317 | Content/Items/Melee/NeutronGlaive.cs:309-319 | Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:264-274 | Content/Items/Modifys/RBloodButcherer.cs:299-310 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:307` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11–12 lines × 4) Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs:45 — Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs:45-56 | Content/LegendWeapon/SHPCLegend/TrialQuests/SHPCTrackerWidgetStyle.cs:49-59 | Content/Scenarios/Draedon/Quest/DraedonTrackerWidgetStyle.cs:48-58 | Content/Scenarios/OldDuke/Quest/SulfseaTrackerWidgetStyle.cs:45-56 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (11–12 lines × 4) Content/LegendWeapon/HalibutLegend/UI/HalibutItemTooltipPanel.cs:30 — Content/LegendWeapon/HalibutLegend/UI/HalibutItemTooltipPanel.cs:30-41 | Content/LegendWeapon/KikasaLegend/UI/KikasaItemTooltipPanel.cs:39-49 | Content/LegendWeapon/OnikiriLegend/UI/OniItemTooltipPanel.cs:31-41 | Content/LegendWeapon/SHPCLegend/UI/SHPCItemTooltipPanel.cs:33-44 — before extracting anything, compare `Content/LegendWeapon/HalibutLegend/UI/HalibutItemTooltipPanel.cs` and `Content/LegendWeapon/KikasaLegend/UI/KikasaItemTooltipPanel.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/UI/HalibutItemTooltipPanel.cs:30` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (11–12 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainRender.cs:86 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainRender.cs:86-97 | Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainRender.cs:242-253 | Content/Scenarios/Kiame/Overlay/OniUmbrellaPuddleRender.cs:83-93 | Content/Scenarios/Kiame/Water/KiameWaterRender.cs:134-144 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainRender.cs:86` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainRender.cs:240` calls `FillUniforms` and `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainRender.cs:84` does not — after which the two agree again for 3 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–12 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:928 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:928-938 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:985-996 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:889-899 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:922-932 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs` as WHOLE FILES: this scan already matched 75 separate duplicated blocks between them, totalling at least 912 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:928` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (11–12 lines × 4) Content/Scenarios/Dungeonworld/Gen/TileBrush.cs:29 — Content/Scenarios/Dungeonworld/Gen/TileBrush.cs:29-40 | Content/Scenarios/Kiame/Gen/KiameTileBrush.cs:18-28 | Content/Scenarios/Kiyume/Gen/KiyumeTileBrush.cs:18-28 | Content/Scenarios/OldNet/Gen/OldNetTileBrush.cs:18-28 — before extracting anything, compare `Content/Scenarios/Kiame/Gen/KiameTileBrush.cs` and `Content/Scenarios/Kiyume/Gen/KiyumeTileBrush.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/Gen/TileBrush.cs:29` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10 lines × 8) · ×6
  • Duplicated block (10 lines × 8) Content/Industrials/ElectricPowers/Apiaries/ApiaryStorageProvider.cs:182 — Content/Industrials/ElectricPowers/Apiaries/ApiaryStorageProvider.cs:182-191 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherStorageProvider.cs:181-190 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerStorageProvider.cs:181-190 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerStorageProvider.cs:121-130 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatStorageProvider.cs:121-130 | Content/Industrials/ElectricPowers/Throwers/ThrowerStorageProvider.cs:187-196 | Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersStorageProvider.cs:183-192 | Content/Scenarios/OldDuke/OldDuchests/OldDuchestStorageProvider.cs:169-178 — before extracting anything, compare `Content/Industrials/ElectricPowers/Apiaries/ApiaryStorageProvider.cs` and `Content/Industrials/ElectricPowers/AutoFishers/AutoFisherStorageProvider.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Apiaries/ApiaryStorageProvider.cs:182` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 8) Content/NPCs/BloomsandSerpents/BssHead.cs:722 — Content/NPCs/BloomsandSerpents/BssHead.cs:722-731 | Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/BrainOfCthulhuAI.cs:382-391 | Content/NPCs/BrutalNPCs/BrutalDestroyer/DestroyerHeadAI.cs:175-184 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/EowHeadAI.cs:572-581 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/EyeOfCthulhuAI.cs:267-276 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/CultistBossAI.cs:263-272 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/QueenSlimeAI.cs:221-230 | Content/NPCs/FestersandSerpents/FssHead.cs:712-721 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 8 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 8 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/BrutalNPCs/BrutalLunaticCultist/CultistBossAI.cs:258` calls `Update` and `Content/NPCs/BloomsandSerpents/BssHead.cs:717` 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 (10 lines × 8) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:433 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:433-442 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:402-411 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:458-467 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:434-443 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:420-429 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:394-403 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:390-399 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:436-445 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs` as WHOLE FILES: this scan already matched 55 separate duplicated blocks between them, totalling at least 611 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:433` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (10 lines × 8) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1477 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1477-1488 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1194-1203 | Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:281-292 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleCut.cs:330-341 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleRing.cs:234-245 | Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashMark.cs:225-236 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1386-1397 | Content/LegendWeapon/OnikiriLegend/OniZanshinSlashs/OniZanshinSlash.cs:368-379 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1477` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashMark.cs:223` calls `Cos`, `ApplySlashPenetration` and `Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleCut.cs:329` 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 (10 lines × 8) Content/GameModes/BrutalMobs/EliteMove/Projectiles/EMParryStanceProj.cs:24 — Content/GameModes/BrutalMobs/EliteMove/Projectiles/EMParryStanceProj.cs:24-33 | Content/GameModes/BrutalMobs/EliteMove/Projectiles/EMPhaseAnchorProj.cs:28-37 | Content/GameModes/BrutalMobs/EvilBiome/Projectiles/SiphonPounceOmen.cs:30-39 | Content/GameModes/BrutalMobs/Martians/Projectiles/MrtSaucerScanProj.cs:40-49 | Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemTelegraph.cs:24-33 | Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraSnareVine.cs:31-40 | Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraTelegraphLine.cs:22-31 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeTelegraphLine.cs:32-41 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemTelegraph.cs` and `Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraTelegraphLine.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 8) Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs:32 — Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs:32-41 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmPresentShellProj.cs:30-39 | Content/NPCs/BloomsandSerpents/Projectiles/BssDashOmen.cs:37-46 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerCoilRingProj.cs:28-37 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerHeatWakeProj.cs:28-37 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerStrikeTelegraph.cs:31-40 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronTelegraph.cs:35-44 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Projectiles/QueenBeeTelegraphLine.cs:33-42 — before extracting anything, compare `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs` and `Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmPresentShellProj.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/NPCs/BloomsandSerpents/Projectiles/BssDashOmen.cs:48` calls `ShouldUpdatePosition` and `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs:43` 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.
D4 · Code Duplication · Duplicated block (10 lines × 6) · ×6
  • Duplicated block (10 lines × 6) Content/Industrials/ElectricPowers/HealingStations/HealStationTile.cs:93 — Content/Industrials/ElectricPowers/HealingStations/HealStationTile.cs:93-102 | Content/Industrials/ElectricPowers/ShieldGenerators/ShieldGeneratorTile.cs:93-102 | Content/Industrials/ElectricPowers/Suppressors/PacifierTowerTile.cs:93-102 | Content/Industrials/ElectricPowers/Turrets/CryoTurrets/CryoTurretTile.cs:93-102 | Content/Industrials/ElectricPowers/Turrets/FlameTurrets/FlameTurretTile.cs:93-102 | Content/Industrials/ElectricPowers/Turrets/LaserTurrets/LaserTurretTile.cs:93-102 — before extracting anything, compare `Content/Industrials/ElectricPowers/HealingStations/HealStationTile.cs` and `Content/Industrials/ElectricPowers/ShieldGenerators/ShieldGeneratorTile.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/HealingStations/HealStationTile.cs:93` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 6) Content/Items/Melee/DestroyersBlade.cs:126 — Content/Items/Melee/DestroyersBlade.cs:126-135 | Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:102-111 | Content/Items/Melee/DragonsScaleGreatsword.cs:142-151 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:161-170 | Content/Items/Stones/Marbles/MarbleClub.cs:119-128 | Content/Items/Stones/Marbles/MarbleHuntingKnife.cs:115-124 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DestroyersBlade.cs:126` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 6) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:866 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:866-875 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1042-1051 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:796-805 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:726-735 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:774-783 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:664-673 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs` as WHOLE FILES: this scan already matched 66 separate duplicated blocks between them, totalling at least 737 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:866` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 6) Content/Scenarios/OldNet/Tiles/OldNetAccessTerminalTile.cs:125 — Content/Scenarios/OldNet/Tiles/OldNetAccessTerminalTile.cs:125-134 | Content/Scenarios/OldNet/Tiles/OldNetDataNodeTile.cs:101-110 | Content/Scenarios/OldNet/Tiles/OldNetEncryptedNodeTile.cs:121-130 | Content/Scenarios/OldNet/Tiles/OldNetEventNodeTile.cs:94-103 | Content/Scenarios/OldNet/Tiles/OldNetLogoutTerminalTile.cs:78-87 | Content/Scenarios/OldNet/Tiles/OldNetRelayTile.cs:88-97 — 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 6 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/OldNet/Tiles/OldNetAccessTerminalTile.cs:125` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Scenarios/OldNet/Tiles/OldNetAccessTerminalTile.cs:124` calls `ArmedBoost01` and `Content/Scenarios/OldNet/Tiles/OldNetLogoutTerminalTile.cs:77` does not — after which the two agree again for 4 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 (10 lines × 6) Content/LegendWeapon/OnikiriLegend/OniDismembers/OniPlayerDismember.cs:354 — Content/LegendWeapon/OnikiriLegend/OniDismembers/OniPlayerDismember.cs:354-365 | Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Core/BrainMindSeizePlayer.cs:58-67 | Content/NPCs/BrutalNPCs/BrutalDeerclops/DeerclopsGrabPlayer.cs:96-106 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/EmpressGrabCutscene.cs:102-111 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Core/KingSlimeEngulfPlayer.cs:175-184 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/QueenSlimePerformancePlayer.cs:208-217 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times.
  • Duplicated block (10 lines × 6) Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmIceShardProj.cs:76 — Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmIceShardProj.cs:76-85 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesIceShardProj.cs:77-86 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandPelletProj.cs:84-93 | Content/Items/BloomArsenal.cs:201-210 | Content/Items/Ranged/Thornstrings/ThornstringArrow.cs:103-112 | Content/NPCs/BloomsandSerpents/Projectiles/BssNeedleProj.cs:66-75 — before extracting anything, compare `Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmIceShardProj.cs` and `Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesIceShardProj.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmIceShardProj.cs:76` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (5 lines × 9) · ×6
  • Duplicated block (5 lines × 9) Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclNailheadNailProj.cs:92 — Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclNailheadNailProj.cs:92-96 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmNutShellProj.cs:105-109 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmOrnamentProj.cs:84-88 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmPineNeedleProj.cs:66-70 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmPresentShellProj.cs:80-84 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteStarSurge.cs:280-284 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Projectiles/EocBloodShot.cs:96-100 | Content/NPCs/FestersandSerpents/Projectiles/FssMortarShard.cs:65-69 | Content/NPCs/FestersandSerpents/Projectiles/FssMortarShell.cs:126-130 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 9 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 9 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclNailheadNailProj.cs:92` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 9) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:383 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:383-387 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:389-393 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:355-359 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:387-391 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:396-400 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:342-346 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:352-356 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:351-355 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:384-388 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:383` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 9) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:434 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:434-438 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:403-407 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:459-463 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:435-439 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:421-425 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:395-399 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:391-395 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:437-441 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistIceShard.cs:150-154 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs` as WHOLE FILES: this scan already matched 55 separate duplicated blocks between them, totalling at least 611 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:434` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (5 lines × 9) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:803 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:803-807 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:884-888 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1059-1063 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:799-803 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeMortar.cs:203-207 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:442-446 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1150-1154 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:966-970 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1216-1220 — there are 9 copies across 8 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 9 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:803` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 9) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:804 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:804-808 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1060-1064 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:800-804 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:428-432 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:535-539 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:542-546 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:469-473 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1151-1155 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:967-971 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs` as WHOLE FILES: this scan already matched 48 separate duplicated blocks between them, totalling at least 508 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:804` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (5 lines × 9) Content/GameModes/GodSmith/Weapons/Broadswords/GsBreakerBlade.cs:126 — Content/GameModes/GodSmith/Weapons/Broadswords/GsBreakerBlade.cs:126-130 | Content/GameModes/GodSmith/Weapons/Broadswords/GsFetidBaghnakhs.cs:176-180 | Content/GameModes/GodSmith/Weapons/Broadswords/GsHamBat.cs:134-138 | Content/GameModes/GodSmith/Weapons/Broadswords/GsMeowmere.cs:593-597 | Content/GameModes/GodSmith/Weapons/Broadswords/GsMythrilSword.cs:148-152 | Content/GameModes/GodSmith/Weapons/Broadswords/GsPhaseBladeShared.cs:325-329 | Content/GameModes/GodSmith/Weapons/Broadswords/GsPiercingStarlight.cs:330-334 | Content/GameModes/GodSmith/Weapons/Broadswords/GsSlapHand.cs:130-134 | Content/GameModes/GodSmith/Weapons/Broadswords/GsStarWrath.cs:455-459 — 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 9 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (8 lines × 7) · ×6
  • Duplicated block (8 lines × 7) Content/GameModes/GodSmith/Weapons/MagicChant/GsCursedFlames.cs:162 — Content/GameModes/GodSmith/Weapons/MagicChant/GsCursedFlames.cs:162-169 | Content/GameModes/GodSmith/Weapons/MagicChant/GsCursedFlames.cs:235-242 | Content/GameModes/GodSmith/Weapons/MagicChant/GsGoldenShower.cs:204-211 | Content/GameModes/GodSmith/Weapons/MagicChant/GsNettleBurst.cs:122-129 | Content/GameModes/GodSmith/Weapons/MagicChant/GsNettleBurst.cs:187-194 | Content/GameModes/GodSmith/Weapons/MagicChant/GsWaspGun.cs:158-165 | Content/GameModes/GodSmith/Weapons/MagicConduit/Projectiles/GsChargedBlasterCannonHeldProj.cs:116-123 — there are 7 copies across 5 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 7 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/MagicChant/GsCursedFlames.cs:162` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 7) Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:338 — Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:338-345 | Content/Items/Melee/DestroyersBlade.cs:354-361 | Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:480-487 | Content/Items/Melee/DragonsScaleGreatsword.cs:367-374 | Content/Items/Melee/EnergySword.cs:382-389 | Content/Items/Melee/RebelBlade.cs:404-411 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:366-373 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:338` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 7) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:452 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:452-459 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:701-708 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:450-457 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:742-749 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:427-434 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:415-422 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:529-536 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs` as WHOLE FILES: this scan already matched 46 separate duplicated blocks between them, totalling at least 456 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 7) Content/Items/Accessories/BrutalRelics/KingSlime/FallenCrownProj.cs:242 — Content/Items/Accessories/BrutalRelics/KingSlime/FallenCrownProj.cs:242-250 | Content/Items/Accessories/BrutalRelics/KingSlime/KingsVerdictWave.cs:157-165 | Content/Items/Ranged/Pallbearer.cs:1271-1279 | Content/LegendWeapon/HalibutLegend/FishSkills/FishAmanita.cs:692-700 | Content/LegendWeapon/HalibutLegend/FishSkills/FishHoney.cs:284-292 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Projectiles/EmpressAuroraVeil.cs:145-152 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSCrownProj.cs:480-488 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times.
  • Duplicated block (8 lines × 7) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:467 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:467-474 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:716-723 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:465-472 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:757-764 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:521-528 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:440-447 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:430-437 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs` as WHOLE FILES: this scan already matched 46 separate duplicated blocks between them, totalling at least 456 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 × 7) Content/Scenarios/OldNet/Tiles/OldNetBreakerTile.cs:70 — Content/Scenarios/OldNet/Tiles/OldNetBreakerTile.cs:70-77 | Content/Scenarios/OldNet/Tiles/OldNetCacheTile.cs:97-104 | Content/Scenarios/OldNet/Tiles/OldNetCipherVaultTile.cs:105-112 | Content/Scenarios/OldNet/Tiles/OldNetColdNodeTile.cs:101-108 | Content/Scenarios/OldNet/Tiles/OldNetEscrowTile.cs:129-136 | Content/Scenarios/OldNet/Tiles/OldNetLedgerDockTile.cs:84-91 | Content/Scenarios/OldNet/Tiles/OldNetSentryMineTile.cs:98-105 — before extracting anything, compare `Content/Scenarios/OldNet/Tiles/OldNetBreakerTile.cs` and `Content/Scenarios/OldNet/Tiles/OldNetSentryMineTile.cs` as WHOLE FILES: this scan already matched 5 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.
D4 · Code Duplication · Duplicated block (6 lines × 8) · ×6
  • Duplicated block (6 lines × 8) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:548 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:548-553 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumCircle.cs:243-248 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoProj.cs:163-168 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistThunderOrb.cs:177-182 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaMiniBloodSlime.cs:195-200 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeBloodBee.cs:122-127 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenGelMine.cs:263-268 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshLeech.cs:128-133 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 8 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 8 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:548` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaMiniBloodSlime.cs:192` calls `FindTarget` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshLeech.cs:125` 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 (6 lines × 8) Content/Industrials/ElectricPowers/LifeWeavers/LifeWeaverTile.cs:55 — Content/Industrials/ElectricPowers/LifeWeavers/LifeWeaverTile.cs:55-60 | Content/Industrials/ElectricPowers/LifeWeavers/WGGLifeWeaver.cs:107-112 | Content/Industrials/ElectricPowers/Lumberjacks/LumberjackTile.cs:54-59 | Content/Industrials/ElectricPowers/Lumberjacks/WGGLumberjack.cs:102-107 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatTile.cs:100-105 | Content/Industrials/ElectricPowers/Sundials/ElectricSundialTile.cs:104-109 | Content/Industrials/ElectricPowers/Throwers/ThrowerTile.cs:102-107 | Content/Tiles/FoodStallChair.cs:93-98 — before extracting anything, compare `Content/Industrials/ElectricPowers/LifeWeavers/LifeWeaverTile.cs` and `Content/Industrials/ElectricPowers/LifeWeavers/WGGLifeWeaver.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 63 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 (6 lines × 8) Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFistProj.cs:392 — Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFistProj.cs:392-397 | Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFistProj.cs:551-556 | Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadCommandRender.cs:187-192 | Content/Items/Accessories/BrutalRelics/Twins/TwinPupilOrbiter.cs:529-534 | Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemSunCore.cs:303-308 | Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemTelegraph.cs:113-118 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Rendering/SkeletronRenderHelper.cs:508-513 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/HeadPrimeAI.cs:813-818 — there are 8 copies across 7 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 8 sites; resolving a subset leaves the remainder to drift apart.
  • Duplicated block (6 lines × 8) Content/Items/Accessories/Proverbs.cs:250 — Content/Items/Accessories/Proverbs.cs:250-259 | Content/Items/Magic/Pandemoniums/PandemoniumBlastWave.cs:85-94 | Content/Items/Magic/Pandemoniums/PandemoniumChannel.cs:831-840 | Content/Items/Magic/Pandemoniums/PandemoniumCircle.cs:328-337 | Content/Items/Magic/Pandemoniums/PandemoniumRSkill.cs:462-471 | Content/Items/Ranged/Starships/StarshipPlanet.cs:191-198 | Content/Items/Tools/EncyclopediaofOceanicKnowledge.cs:472-477 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumCircle.cs:352-358 — before extracting anything, compare `Content/Items/Accessories/Proverbs.cs` and `Content/Items/Magic/Pandemoniums/PandemoniumBlastWave.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/Proverbs.cs:250` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6 lines × 8) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:308 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:308-313 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:627-632 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:979-984 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:589-594 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:940-945 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:303-308 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:622-627 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:973-978 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs` as WHOLE FILES: this scan already matched 78 separate duplicated blocks between them, totalling at least 968 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:308` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 8) Content/Scenarios/Shepel/Dialogues/Reactive/Bosses/ShepelBrimstoneElementalDialogue.cs:21 — Content/Scenarios/Shepel/Dialogues/Reactive/Bosses/ShepelBrimstoneElementalDialogue.cs:21-26 | Content/Scenarios/Shepel/Dialogues/Reactive/Bosses/ShepelDesertScourgeDialogue.cs:21-26 | Content/Scenarios/Shepel/Dialogues/Reactive/Bosses/ShepelEyeOfCthulhuDialogue.cs:22-27 | Content/Scenarios/Shepel/Dialogues/Reactive/Bosses/ShepelPlaguebringerDialogue.cs:21-26 | Content/Scenarios/Shepel/Dialogues/Reactive/Bosses/ShepelSkeletronDialogue.cs:22-27 | Content/Scenarios/Shepel/Dialogues/Reactive/Bosses/ShepelSkeletronPrimeDialogue.cs:22-27 | Content/Scenarios/Shepel/Dialogues/Reactive/Bosses/ShepelSlimeGodDialogue.cs:21-26 | Content/Scenarios/Shepel/Dialogues/Reactive/Bosses/ShepelYharonDialogue.cs:21-26 — 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 8 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (6 lines × 10) · ×6
  • Duplicated block (6 lines × 10) Content/Items/Accessories/BrutalRelics/MoonLord/BlackFlashSigilRender.cs:143 — Content/Items/Accessories/BrutalRelics/MoonLord/BlackFlashSigilRender.cs:143-148 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSShockwaveProj.cs:73-79 | Content/Scenarios/Kiyume/NPCs/FacelessOneYokai.cs:495-501 | Content/Scenarios/Kiyume/NPCs/FuneralCortegeYokai.cs:1208-1214 | Content/Scenarios/Kiyume/NPCs/KiyumeHound.cs:1052-1058 | Content/Scenarios/Kiyume/NPCs/KiyumeWhiteHound.cs:475-481 | Content/Scenarios/Kiyume/NPCs/LanternGuideYokai.cs:593-599 | Content/Scenarios/Kiyume/NPCs/RidgeWalkerYokai.cs:594-602 | Content/Scenarios/Kiyume/NPCs/ShallowHandsYokai.cs:395-403 | Content/Scenarios/Kiyume/NPCs/WellHandYokai.cs:407-415 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 10 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 10 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/MoonLord/BlackFlashSigilRender.cs:143` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6 lines × 10) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1072 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1072-1077 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:866-871 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1102-1107 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:891-896 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1409-1414 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:911-916 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:821-826 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:859-864 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:860-865 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1370-1375 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1072` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6 lines × 10) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1318 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1318-1323 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:982-987 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1337-1342 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:1040-1045 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1701-1706 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:1046-1051 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:943-948 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:1069-1074 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:976-981 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1747-1752 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1318` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (6 lines × 10) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:742 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:742-748 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:756-762 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:673-678 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:535-540 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:723-728 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:692-698 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:849-855 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:966-971 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:943-948 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:943-949 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 598 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:742` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (6 lines × 10) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:362 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:362-367 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:468-474 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:363-368 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:439-445 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:431-437 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:546-552 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:552-557 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:479-484 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:416-422 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:484-490 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs` as WHOLE FILES: this scan already matched 48 separate duplicated blocks between them, totalling at least 508 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:362` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:475` calls `PlaySound` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:368` 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 (6 lines × 10) Content/Items/Accessories/BrutalRelics/Deerclops/WhiteoutVeilRender.cs:90 — Content/Items/Accessories/BrutalRelics/Deerclops/WhiteoutVeilRender.cs:90-95 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Rendering/DeerclopsVeilRender.cs:89-94 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Rendering/EocFogRender.cs:127-132 | Content/NPCs/BrutalNPCs/BrutalGolem/Rendering/GolemScreenEffectRender.cs:141-146 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistVeilRender.cs:77-82 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordScreenRender.cs:111-116 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Rendering/SkeletronScreenRender.cs:100-105 | Content/Renders/PrimeScreenEffectRender.cs:149-154 | Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:3027-3032 | Content/Scenarios/Dungeonworld/NPCs/Elites/LampeaterWispRendering.cs:244-249 — before extracting anything, compare `Content/Items/Accessories/BrutalRelics/Deerclops/WhiteoutVeilRender.cs` and `Content/NPCs/BrutalNPCs/BrutalDeerclops/Rendering/DeerclopsVeilRender.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×6
  • Swallowed exception (caught, then discarded) Content/Cyberwares/CyberwarePlayer.cs:369 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterRecipeId.cs:145 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:336 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:885 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) Content/LegendWeapon/LegendData.cs:272 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) Content/LegendWeapon/OnikiriLegend/OniBladeProfile.cs:64 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
D4 · Code Duplication · Edited copy of a member (49 corresponding lines) · ×5
  • Edited copy of a member (49 corresponding lines) Content/GameModes/BrutalMobs/Martians/Projectiles/MrtWrenchProj.cs:139 — Content/GameModes/BrutalMobs/Martians/Projectiles/MrtWrenchProj.cs:139-187 | Content/GameModes/BrutalMobs/NightPack/Projectiles/NightBoneProj.cs:140-188 — These two members are one piece of code written twice and then edited apart: 49 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (49 corresponding lines) Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmIcingPatchProj.cs:104 — Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmIcingPatchProj.cs:104-156 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesIceSlickZone.cs:138-186 — These two members are one piece of code written twice and then edited apart: 49 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (49 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:176 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:176-224 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs:184-243 — These two members are one piece of code written twice and then edited apart: 49 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (49 corresponding lines) Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs:521 — Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs:521-577 | Content/Scenarios/Shenyo/ShenyoPortraitRainRenderer.cs:512-560 — These two members are one piece of code written twice and then edited apart: 49 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (49 corresponding lines) Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:241 — Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:241-300 | Content/Scenarios/Kiame/Overlay/OniRainExitTransition.cs:198-246 — These two members are one piece of code written twice and then edited apart: 49 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (41 corresponding lines) · ×5
  • Edited copy of a member (41 corresponding lines) Content/Items/Ranged/CrystalDimming.cs:381 — Content/Items/Ranged/CrystalDimming.cs:381-421 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenCrystalSpireProj.cs:122-171 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (41 corresponding lines) Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerSeizeHandProj.cs:247 — Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerSeizeHandProj.cs:247-287 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerShadowHandProj.cs:152-195 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (41 corresponding lines) Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Content.cs:509 — Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Content.cs:509-555 | Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Content.cs:345-385 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (41 corresponding lines) Content/NPCs/BloomsandSerpents/Projectiles/BssBreachOmen.cs:36 — Content/NPCs/BloomsandSerpents/Projectiles/BssBreachOmen.cs:36-76 | Content/NPCs/FestersandSerpents/Projectiles/FssBreachOmen.cs:31-79 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (41 corresponding lines) Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:659 — Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:659-702 | Content/Items/Modifys/RTerraBlades/RTerraBladeHeld.cs:871-911 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 36+ corresponding lines) · ×5
  • Edited copies of one member (3 members, 36+ corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Barrel/HiveBarrelModule.cs:158 — Content/LegendWeapon/SHPCLegend/Modules/Barrel/HiveBarrelModule.cs:158-193 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/ObsidianBarrelModule.cs:236-276 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/ScattershotBarrelModule.cs:234-270 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 36 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 36+ corresponding lines) Content/Items/Melee/DawnshatterAzures/DawnshatterDash.cs:452 — Content/Items/Melee/DawnshatterAzures/DawnshatterDash.cs:452-488 | Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashStep.cs:1114-1149 | Content/LegendWeapon/OnikiriLegend/OniSakuraFlights/OniSakuraFlight.cs:1235-1275 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 36 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 36+ corresponding lines) Content/Scenarios/OldNet/Tiles/OldNetAccessTerminalTile.cs:117 — Content/Scenarios/OldNet/Tiles/OldNetAccessTerminalTile.cs:117-152 | Content/Scenarios/OldNet/Tiles/OldNetLogoutTerminalTile.cs:71-120 | Content/Scenarios/OldNet/Tiles/OldNetRelayTile.cs:81-125 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 36 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 36+ corresponding lines) Content/Scenarios/Kiyume/Ambience/KiyumeCrowFlight.cs:286 — Content/Scenarios/Kiyume/Ambience/KiyumeCrowFlight.cs:286-321 | Content/Scenarios/Kiyume/Ambience/KiyumeCrowRoost.cs:437-476 | Content/Scenarios/Kiyume/Fog/KiyumeHoundShade.cs:136-171 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 36 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 36+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomain.cs:112 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomain.cs:112-155 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomain.cs:92-133 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Cyberspace.cs:102-137 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 36 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 26+ corresponding lines) · ×5
  • Edited copies of one member (3 members, 26+ corresponding lines) Content/Narrative/Presentation/Skins/Sulfsea/SulfseaPanelDraw.cs:29 — Content/Narrative/Presentation/Skins/Sulfsea/SulfseaPanelDraw.cs:29-56 | Content/Narrative/Presentation/Skins/Tzeentch/TzeentchPanelDraw.cs:29-54 | Content/Scenarios/SupCal/End/EternalBlazingNow/Enchants/EnchantUI.cs:400-433 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 26 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 26+ corresponding lines) Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs:75 — Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs:75-102 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmNutShellProj.cs:96-123 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmOrnamentProj.cs:75-100 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 26 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 26+ corresponding lines) Content/Industrials/ElectricPowers/Apiaries/ApiaryTP.cs:636 — Content/Industrials/ElectricPowers/Apiaries/ApiaryTP.cs:636-662 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherTP.cs:618-643 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerTP.cs:692-718 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 26 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 26+ corresponding lines) Content/NPCs/BloomsandSerpents/BssHead.cs:682 — Content/NPCs/BloomsandSerpents/BssHead.cs:682-707 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/EowHeadAI.cs:541-568 | Content/NPCs/FestersandSerpents/FssHead.cs:619-644 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 26 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 26+ corresponding lines) Content/HackTimes/HackTimeNPCDraw.cs:13 — Content/HackTimes/HackTimeNPCDraw.cs:13-38 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreezeGlobalNPC.cs:17-47 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreezeGlobalProj.cs:14-43 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 26 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 19+ corresponding lines) · ×5
  • Edited copies of one member (5 members, 19+ corresponding lines) Content/Items/Summon/AzureDragonRage.cs:92 — Content/Items/Summon/AzureDragonRage.cs:92-110 | Content/Items/Summon/BleedingScourge.cs:75-93 | Content/Items/Summon/ElementWhip.cs:82-100 | Content/Items/Summon/GhostFireWhip.cs:88-106 | Content/Items/Summon/WhiplashGalactica.cs:97-115 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 19+ corresponding lines) Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:315 — Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:315-333 | Content/Items/Melee/Abyssrends/AbyssrendUndercurrent.cs:136-158 | Content/Items/Ranged/Undertows/UndertowSpine.cs:174-194 | Content/Items/Summon/Deepclaws/DeepclawLobster.cs:465-486 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpWaterBolt.cs:103-122 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 19+ corresponding lines) Content/GameModes/GodSmith/Prefixes/Accessory/GodSmithMenaceEndow.cs:42 — Content/GameModes/GodSmith/Prefixes/Accessory/GodSmithMenaceEndow.cs:42-61 | Content/GameModes/GodSmith/Prefixes/Magic/GodSmithOverloadEndow.cs:46-64 | Content/GameModes/GodSmith/Prefixes/Offense/GodSmithCritMarkEndow.cs:44-63 | Content/GameModes/GodSmith/Prefixes/Offense/GodSmithShockwaveEndow.cs:47-67 | Content/GameModes/GodSmith/Prefixes/Speed/GodSmithComboEndow.cs:49-67 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 19+ corresponding lines) Content/QuestLogs/QLNodes/AdventurerQuests.cs:60 — Content/QuestLogs/QLNodes/AdventurerQuests.cs:60-78 | Content/QuestLogs/QLNodes/AdventurerQuests.cs:127-145 | Content/QuestLogs/QLNodes/AdventurerQuests.cs:157-175 | Content/QuestLogs/QLNodes/AdventurerQuests.cs:224-242 | Content/QuestLogs/QLNodes/AdventurerQuests.cs:706-724 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 19+ corresponding lines) Content/QuestLogs/QLNodes/AdventurerQuests.cs:291 — Content/QuestLogs/QLNodes/AdventurerQuests.cs:291-309 | Content/QuestLogs/QLNodes/AdventurerQuests.cs:403-421 | Content/QuestLogs/QLNodes/AdventurerQuests.cs:434-452 | Content/QuestLogs/QLNodes/AdventurerQuests.cs:875-893 | Content/QuestLogs/QLNodes/AdventurerQuests.cs:949-967 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 14+ corresponding lines) · ×5
  • Edited copies of one member (5 members, 14+ corresponding lines) Content/HackTimes/Protocols/MachineShortCircuit.cs:74 — Content/HackTimes/Protocols/MachineShortCircuit.cs:74-90 | Content/HackTimes/Protocols/TileDetonate.cs:145-162 | Content/HackTimes/Protocols/TurretCircuitOverload.cs:36-49 | Content/HackTimes/Protocols/TurretShortCircuit.cs:36-49 | Content/HackTimes/Protocols/VirusBroadcast.cs:41-55 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 14+ corresponding lines) Content/Items/Magic/SandVortexOfTheDecayedSea.cs:430 — Content/Items/Magic/SandVortexOfTheDecayedSea.cs:430-445 | Content/Items/Melee/BudPiercers/BudPiercer.cs:113-128 | Content/Items/Melee/RebelBlade.cs:768-781 | Content/Items/Ranged/RaiderGun.cs:464-477 | Content/Items/Tools/FungalFeed.cs:115-128 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 14+ corresponding lines) Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachine.cs:14 — Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachine.cs:14-29 | Content/Industrials/ElectricPowers/FluidInjectors/FluidInjector.cs:14-29 | Content/Industrials/ElectricPowers/FluidPumps/FluidPump.cs:14-29 | Content/Industrials/ElectricPowers/WireInterfaces/WireInterface.cs:33-47 | Content/Industrials/MaterialFlow/Fluids/LargeFluidTank.cs:17-30 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 14+ corresponding lines) Content/LegendWeapon/OnikiriLegend/OniDismembers/OniSeverReplicationSystem.cs:235 — Content/LegendWeapon/OnikiriLegend/OniDismembers/OniSeverReplicationSystem.cs:235-249 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBanish.Net.cs:463-477 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBossExecution.Net.cs:292-306 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.Net.cs:808-822 | Content/TimeFreezes/TimeControlReplicationSystem.cs:340-353 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 14+ corresponding lines) Content/Items/Melee/GeminisTribute.cs:156 — Content/Items/Melee/GeminisTribute.cs:156-169 | Content/Items/Melee/GeminisTribute.cs:528-541 | Content/Items/Melee/Heartcarver.cs:574-587 | Content/Items/Melee/Heartcarver.cs:1177-1191 | Content/Items/Ranged/NeutronBows/NeutronArrow.cs:11-24 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 10+ corresponding lines) · ×5
  • Edited copies of one member (6 members, 10+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemEyeRay.cs:179 — Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemEyeRay.cs:179-189 | Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemGrabRay.cs:180-190 | Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemTrapUnit.cs:656-666 | Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraSnareVine.cs:46-55 | Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraTelegraphLine.cs:40-51 | Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraVineLattice.cs:53-64 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 10+ corresponding lines) Content/Items/Magic/Elysiums/Disciples/John.cs:20 — Content/Items/Magic/Elysiums/Disciples/John.cs:20-30 | Content/Items/Magic/Elysiums/Disciples/Matthew.cs:23-33 | Content/Items/Magic/Elysiums/Disciples/Philip.cs:44-57 | Content/Items/Magic/Elysiums/Disciples/Thaddaeus.cs:27-40 | Content/Items/Magic/Elysiums/Disciples/Thomas.cs:21-33 | Content/Items/Magic/Elysiums/Disciples/Zealot.cs:20-29 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 10+ corresponding lines) Content/HackTimes/Protocols/TileConscript.cs:442 — Content/HackTimes/Protocols/TileConscript.cs:442-453 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:63-73 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:741-751 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs:76-86 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1177-1186 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshEyeLaser.cs:66-76 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 10+ corresponding lines) Content/Scenarios/Dungeonworld/Dungeonworld.cs:88 — Content/Scenarios/Dungeonworld/Dungeonworld.cs:88-97 | Content/Scenarios/Hadalworld/Hadalworld.cs:61-70 | Content/Scenarios/Kiame/KiameWorld.cs:57-66 | Content/Scenarios/Kiyume/KiyumeWorld.cs:57-66 | Content/Scenarios/OldNet/OldNetWorld.cs:58-67 | Content/Scenarios/Shepel/CybCourses/CybCourse.cs:34-43 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 10+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuBao.cs:161 — Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuBao.cs:161-170 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuHang.cs:106-115 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuHong.cs:67-76 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuShu.cs:174-183 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuTing.cs:172-181 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuZi.cs:131-142 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 5+ corresponding lines) · ×5
  • Edited copies of one member (4 members, 5+ corresponding lines) Content/NPCs/BloomsandSerpents/BssHead.cs:410 — Content/NPCs/BloomsandSerpents/BssHead.cs:410-414 | Content/NPCs/FestersandSerpents/FssHead.cs:364-368 | Content/NPCs/ScrapCommanders/ScrapCommander.cs:330-334 | Content/NPCs/SeaShrimp/SeaShrimpBoss.cs:302-306 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 5+ corresponding lines) Content/GameModes/GodSmith/Weapons/Guns/GunsHardShared.cs:467 — Content/GameModes/GodSmith/Weapons/Guns/GunsHardShared.cs:467-471 | Content/Items/Melee/StormGoddessSpears/StormGoddessSpearHeld.cs:372-379 | Content/LegendWeapon/HalibutLegend/UI/HalibutTheme.cs:108-115 | Content/Scenarios/Draedon/ExoMechdusaSums/ExoMechdusaSumRender.cs:560-567 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 5+ corresponding lines) Content/Items/Accessories/ElementMuzzleBrake.cs:26 — Content/Items/Accessories/ElementMuzzleBrake.cs:26-30 | Content/Items/Accessories/EyeOfSingularity.cs:67-71 | Content/Items/Accessories/PrecisionMuzzleBrake.cs:27-31 | Content/Items/Accessories/SimpleMuzzleBrake.cs:26-30 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 5+ corresponding lines) Content/HackTimes/Protocols/DataLeech.cs:54 — Content/HackTimes/Protocols/DataLeech.cs:54-58 | Content/HackTimes/Protocols/FirmwareRollback.cs:57-62 | Content/HackTimes/Protocols/PhaseDesync.cs:48-52 | Content/HackTimes/Protocols/SwarmLink.cs:39-43 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 5+ corresponding lines) Content/Items/Materials/SoulofFrightEX.cs:11 — Content/Items/Materials/SoulofFrightEX.cs:11-16 | Content/Items/Materials/SoulofMightEX.cs:11-16 | Content/Items/Materials/SoulofSightEX.cs:11-16 | Content/Items/Melee/NeutronScythe.cs:29-33 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (3 corresponding lines) · ×5
  • Edited copy of a member (3 corresponding lines) Content/Scenarios/Kiyume/NPCs/FuneralCortegeYokai.cs:1249 — Content/Scenarios/Kiyume/NPCs/FuneralCortegeYokai.cs:1249-1251 | Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterTile.cs:296-298 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:898 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:898-900 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:898-900 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) Content/LegendWeapon/HalibutLegend/DomainSkills/Superposition.cs:553 — Content/LegendWeapon/HalibutLegend/DomainSkills/Superposition.cs:553-555 | Content/LegendWeapon/HalibutLegend/DomainSkills/YourLevelIsTooLow.cs:420-422 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) Content/GameModes/BrutalMobs/Ambience/DuneStorm/DuneStorm.cs:76 — Content/GameModes/BrutalMobs/Ambience/DuneStorm/DuneStorm.cs:76-78 | Content/GameModes/BrutalMobs/Sandveil/SandveilBrutalNPC.cs:257-259 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBanish.cs:623 — Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBanish.cs:623-625 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.cs:744-748 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 4+ corresponding lines) · ×5
  • Edited copies of one member (4 members, 4+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Core/EmpressMotion.cs:95 — Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Core/EmpressMotion.cs:95-98 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Core/EocMotion.cs:42-45 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Core/CultistMotion.cs:108-111 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Core/TwinsMotion.cs:30-33 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 4+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:663 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:663-666 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:670-673 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:625-628 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:658-661 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 4+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Core/EocMotion.cs:66 — Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Core/EocMotion.cs:66-69 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Core/CultistMotion.cs:114-117 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Core/TwinsMotion.cs:62-65 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Core/QueenBeeMotion.cs:59-62 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 4+ corresponding lines) Content/Items/Ranged/BarrenBow.cs:302 — Content/Items/Ranged/BarrenBow.cs:302-305 | Content/Items/Ranged/NeutronBows/NeutronBow.cs:338-341 | Content/Items/Ranged/Thornstrings/ThornstringHeld.cs:256-259 | Content/Items/Ranged/Undertows/UndertowHeld.cs:262-265 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 4+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalDestroyer/Core/IDestroyerState.cs:94 — Content/NPCs/BrutalNPCs/BrutalDestroyer/Core/IDestroyerState.cs:94-97 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Core/TwinsMotion.cs:48-52 | Content/NPCs/BrutalNPCs/BrutalPlantera/Core/IPlanteraState.cs:144-147 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Core/ISkeletronHandState.cs:113-116 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (27 lines × 2) · ×5
  • Duplicated block (27 lines × 2) Content/NPCs/TBUGs/TBUG.cs:53 — Content/NPCs/TBUGs/TBUG.cs:53-79 | Content/NPCs/Victors/Victor.cs:60-86 — before extracting anything, compare `Content/NPCs/TBUGs/TBUG.cs` and `Content/NPCs/Victors/Victor.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 117 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/TBUGs/TBUG.cs:53` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (27 lines × 2) Content/MainMenus/Himayo/HimayoMenuButtons.cs:222 — Content/MainMenus/Himayo/HimayoMenuButtons.cs:222-248 | Content/MainMenus/Shenyo/ShenyoMenuButtons.cs:224-250 — before extracting anything, compare `Content/MainMenus/Himayo/HimayoMenuButtons.cs` and `Content/MainMenus/Shenyo/ShenyoMenuButtons.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 174 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/MainMenus/Himayo/HimayoMenuButtons.cs:222` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (27 lines × 2) Content/LegendWeapon/HalibutLegend/FishSkills/FishTunabeardVFX.cs:312 — Content/LegendWeapon/HalibutLegend/FishSkills/FishTunabeardVFX.cs:312-338 | Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniKamuiFlowRenderer.cs:216-242 — before extracting anything, compare `Content/LegendWeapon/HalibutLegend/FishSkills/FishTunabeardVFX.cs` and `Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniKamuiFlowRenderer.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 112 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (27 lines × 2) Content/NPCs/ScrapCommanders/States/ScrapSawLaunchState.cs:161 — Content/NPCs/ScrapCommanders/States/ScrapSawLaunchState.cs:161-187 | Content/NPCs/ScrapCommanders/States/ScrapViceSnatchState.cs:156-182 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/ScrapCommanders/States/ScrapSawLaunchState.cs:161` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (27 lines × 2) Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs:155 — Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs:155-181 | Content/Industrials/ElectricPowers/Lumberjacks/WGGLumberjack.cs:160-187 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (21 lines × 3) · ×5
  • Duplicated block (21 lines × 3) Content/Items/Melee/OniMacheteHands.cs:1310 — Content/Items/Melee/OniMacheteHands.cs:1310-1330 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCursed.cs:425-445 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDemonicHell.cs:608-628 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/OniMacheteHands.cs:1310` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (21 lines × 3) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/MachineEffect.cs:111 — Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/MachineEffect.cs:111-131 | Content/Scenarios/Draedon/Tzeentch/TzeentchEffect.cs:57-77 | Content/Scenarios/OldDuke/OldDukeEffect.cs:69-89 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/MachineEffect.cs` and `Content/Scenarios/Draedon/Tzeentch/TzeentchEffect.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Scenarios/OldDuke/OldDukeEffect.cs:90` calls `SetValue` and `Content/Scenarios/Draedon/Tzeentch/TzeentchEffect.cs:78` does not — after which the two agree again for 3 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 (21 lines × 3) Content/Scenarios/OldNet/Tiles/OldNetAccessTerminalTile.cs:117 — Content/Scenarios/OldNet/Tiles/OldNetAccessTerminalTile.cs:117-137 | Content/Scenarios/OldNet/Tiles/OldNetLogoutTerminalTile.cs:71-91 | Content/Scenarios/OldNet/Tiles/OldNetRelayTile.cs:81-101 — before extracting anything, compare `Content/Scenarios/OldNet/Tiles/OldNetAccessTerminalTile.cs` and `Content/Scenarios/OldNet/Tiles/OldNetLogoutTerminalTile.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 52 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/OldNet/Tiles/OldNetAccessTerminalTile.cs:117` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 3) Content/Items/Melee/Abyssrends/AbyssrendBurst.cs:47 — Content/Items/Melee/Abyssrends/AbyssrendBurst.cs:47-67 | Content/Items/Ranged/Undertows/UndertowSpine.cs:251-271 | Content/Items/Summon/Deepclaws/DeepclawLobster.cs:543-563 — before extracting anything, compare `Content/Items/Melee/Abyssrends/AbyssrendBurst.cs` and `Content/Items/Ranged/Undertows/UndertowSpine.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Abyssrends/AbyssrendBurst.cs:47` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 3) Content/EntrustManager/Styles/DraedonManagerStyle.cs:734 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:734-754 | Content/EntrustManager/Styles/ForestManagerStyle.cs:739-759 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:734-754 — before extracting anything, compare `Content/EntrustManager/Styles/DraedonManagerStyle.cs` and `Content/EntrustManager/Styles/ForestManagerStyle.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 334 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/EntrustManager/Styles/DraedonManagerStyle.cs:734` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (21–22 lines × 2) · ×5
  • Duplicated block (21–22 lines × 2) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterTile.cs:109 — Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterTile.cs:109-129 | Content/Industrials/ElectricPowers/Crushers/CrusherTile.cs:107-128 — before extracting anything, compare `Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterTile.cs` and `Content/Industrials/ElectricPowers/Crushers/CrusherTile.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 74 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (21–22 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaMinionDrownFX.cs:270 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaMinionDrownFX.cs:270-290 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaPlayerDrownFX.cs:328-349 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaMinionDrownFX.cs:270` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (21–22 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:272 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:272-293 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:251-271 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs` as WHOLE FILES: this scan already matched 79 separate duplicated blocks between them, totalling at least 1151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:272` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (21–22 lines × 2) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:420 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:420-441 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:294-314 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:420` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21–22 lines × 2) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:769 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:769-789 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:953-974 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` and `Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 850 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:769` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (20–21 lines × 2) · ×5
  • Duplicated block (20–21 lines × 2) Content/EntrustManager/BaseQuestAcceptUI.cs:335 — Content/EntrustManager/BaseQuestAcceptUI.cs:335-354 | Content/UIs/OverhaulSettings/OverhaulSettingsUI.cs:441-461 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/EntrustManager/BaseQuestAcceptUI.cs:335` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20–21 lines × 2) Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:508 — Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:508-528 | Content/Industrials/Modifys/ChargingStationUI.cs:355-374 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (20–21 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:394 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:394-414 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:358-377 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs` as WHOLE FILES: this scan already matched 79 separate duplicated blocks between them, totalling at least 1151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:394` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20–21 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:316 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:316-336 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:318-337 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs` as WHOLE FILES: this scan already matched 70 separate duplicated blocks between them, totalling at least 835 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:316` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20–21 lines × 2) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/Arms/PrimeSawStates.cs:24 — Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/Arms/PrimeSawStates.cs:24-44 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/Arms/PrimeViceStates.cs:27-46 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/Arms/PrimeSawStates.cs:24` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (17 lines × 3) · ×5
  • Duplicated block (17 lines × 3) Content/Structures/DatIO/JunkmanBase.cs:21 — Content/Structures/DatIO/JunkmanBase.cs:21-37 | Content/Structures/DatIO/RocketHut.cs:19-35 | Content/Structures/DatIO/SylvanOutpost.cs:20-36 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Structures/DatIO/JunkmanBase.cs:21` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 3) Content/Items/Summon/BloomCallers/BloomCallerSprout.cs:132 — Content/Items/Summon/BloomCallers/BloomCallerSprout.cs:132-148 | Content/Items/Summon/Deepclaws/DeepclawLobster.cs:151-167 | Content/Items/Summon/EyekiteStaffs/EyekiteMinion.cs:137-153 — before extracting anything, compare `Content/Items/Summon/BloomCallers/BloomCallerSprout.cs` and `Content/Items/Summon/Deepclaws/DeepclawLobster.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (17 lines × 3) Content/Scenarios/Draedon/DraedonEffect.cs:140 — Content/Scenarios/Draedon/DraedonEffect.cs:140-156 | Content/Scenarios/Draedon/Tzeentch/TzeentchEffect.cs:106-122 | Content/Scenarios/OldDuke/OldDukeEffect.cs:133-149 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (17 lines × 3) Content/Scenarios/Himayo/ToriiShrines/ToriiShrineLocationFinder.cs:175 — Content/Scenarios/Himayo/ToriiShrines/ToriiShrineLocationFinder.cs:175-191 | Content/Scenarios/Kiame/Gate/KiameGateSpawn.cs:331-347 | Content/Scenarios/Kiame/Overlay/OniUmbrellaWorldSpawn.cs:400-416 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Himayo/ToriiShrines/ToriiShrineLocationFinder.cs:175` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 3) Content/Scenarios/OldNet/Tiles/OldNetDataNodeTile.cs:95 — Content/Scenarios/OldNet/Tiles/OldNetDataNodeTile.cs:95-111 | Content/Scenarios/OldNet/Tiles/OldNetEncryptedNodeTile.cs:115-131 | Content/Scenarios/OldNet/Tiles/OldNetEventNodeTile.cs:88-104 — before extracting anything, compare `Content/Scenarios/OldNet/Tiles/OldNetDataNodeTile.cs` and `Content/Scenarios/OldNet/Tiles/OldNetEncryptedNodeTile.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 84 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Scenarios/OldNet/Tiles/OldNetDataNodeTile.cs:92` calls `Sin` and `Content/Scenarios/OldNet/Tiles/OldNetEventNodeTile.cs:86` 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.
D4 · Code Duplication · Duplicated block (16–18 lines × 2) · ×5
  • Duplicated block (16–18 lines × 2) Content/Cyberwares/UIs/CyberwareUI.cs:306 — Content/Cyberwares/UIs/CyberwareUI.cs:306-323 | Content/NPCs/Victors/UIs/VictorClinicUI.cs:209-224 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Cyberwares/UIs/CyberwareUI.cs:306` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (16–18 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrown.cs:373 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrown.cs:373-390 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaScourge.cs:225-240 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrown.cs:373` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16–18 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutDomain.cs:100 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutDomain.cs:100-117 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumCircle.cs:100-115 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutDomain.cs:100` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (16–18 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuLaoFX.cs:139 — Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuLaoFX.cs:139-154 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuXiFX.cs:186-203 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuLaoFX.cs:139` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16–18 lines × 2) Content/Scenarios/Kiyume/NPCs/KiyumeHoundDirector.cs:245 — Content/Scenarios/Kiyume/NPCs/KiyumeHoundDirector.cs:245-262 | Content/Scenarios/Kiyume/NPCs/KiyumeWhiteHound.cs:389-404 — 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.
D4 · Code Duplication · Duplicated block (14–16 lines × 2) · ×5
  • Duplicated block (14–16 lines × 2) Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT1.cs:239 — Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT1.cs:239-254 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT3.cs:153-166 — before extracting anything, compare `Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT1.cs` and `Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT3.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 89 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT1.cs:239` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (14–16 lines × 2) Content/Industrials/ElectricPowers/FluidPumps/FluidPumpTP.cs:87 — Content/Industrials/ElectricPowers/FluidPumps/FluidPumpTP.cs:87-102 | Content/Industrials/ElectricPowers/FluidPumps/FluidPumpTP.cs:190-203 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/FluidPumps/FluidPumpTP.cs:87` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (14–16 lines × 2) Content/Industrials/ElectricPowers/Lumberjacks/LumberjackSaw.cs:154 — Content/Industrials/ElectricPowers/Lumberjacks/LumberjackSaw.cs:154-169 | Content/Industrials/ElectricPowers/Lumberjacks/WGGLumberjack.cs:763-776 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (14–16 lines × 2) Content/LegendWeapon/HalibutLegend/FishSkills/FishSlime.cs:726 — Content/LegendWeapon/HalibutLegend/FishSkills/FishSlime.cs:726-741 | Content/LegendWeapon/HalibutLegend/FishSkills/FishVariegatedLard.cs:393-406 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishSlime.cs:726` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14–16 lines × 2) Content/LegendWeapon/OnikiriLegend/UI/OniBrush.cs:47 — Content/LegendWeapon/OnikiriLegend/UI/OniBrush.cs:47-60 | Content/LegendWeapon/OnikiriLegend/UI/OniBrush.cs:83-98 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/UI/OniBrush.cs:47` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (14–15 lines × 2) · ×5
  • Duplicated block (14–15 lines × 2) Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:248 — Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:248-262 | Content/Industrials/Modifys/ChargingStationUI.cs:194-207 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:248` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14–15 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:181 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:181-195 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs:188-201 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 161 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:181` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (14–15 lines × 2) Content/NPCs/BrutalNPCs/BrutalDestroyer/DestroyerBodyAI.cs:269 — Content/NPCs/BrutalNPCs/BrutalDestroyer/DestroyerBodyAI.cs:269-283 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/EowBodyAI.cs:229-242 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/BrutalNPCs/BrutalDestroyer/DestroyerBodyAI.cs:266` calls `ClockFrame` and `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/EowBodyAI.cs:227` does not — after which the two agree again for 4 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–15 lines × 2) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerSoloRageState.cs:118 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerSoloRageState.cs:118-132 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismSoloRageState.cs:119-132 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerSoloRageState.cs:118` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (14–15 lines × 2) Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordBlackHoleProj.cs:812 — Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordBlackHoleProj.cs:812-825 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordUltArms.cs:497-511 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordBlackHoleProj.cs:812` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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.
D4 · Code Duplication · Duplicated block (11 lines × 9) · ×5
  • Duplicated block (11 lines × 9) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:208 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:208-218 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs:230-240 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs:216-226 | Content/Industrials/ElectricPowers/Launchers/PlayerLauncherUI.cs:189-199 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:187-197 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconUI.cs:189-199 | Content/Industrials/ElectricPowers/Sensors/SensorUI.cs:171-181 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:205-215 | Content/Industrials/ElectricPowers/TeleportStations/TeleportStationUI.cs:254-264 — before extracting anything, compare `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs` and `Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 188 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:208` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 9) Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsRallyFieldProj.cs:34 — Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsRallyFieldProj.cs:34-44 | Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsSanguineArcProj.cs:20-30 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkGeyser.cs:124-134 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuJiFX.cs:117-128 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuNiFX.cs:122-132 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuPeiFX.cs:91-101 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuPiFX.cs:54-65 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuPoFX.cs:215-225 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuShuangFX.cs:127-137 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 9 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 9 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsRallyFieldProj.cs:34` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuJiFX.cs:115` calls `Clamp` and `Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkGeyser.cs:122` 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 × 9) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:743 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:743-754 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:757-768 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:674-684 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:536-546 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:724-734 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:693-704 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:850-861 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:659-670 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:944-955 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 598 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:743` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 9) Content/GameModes/BrutalMobs/Ambience/Ashreign/Projectiles/AshreignAshStormProj.cs:44 — Content/GameModes/BrutalMobs/Ambience/Ashreign/Projectiles/AshreignAshStormProj.cs:44-54 | Content/GameModes/BrutalMobs/Ambience/Brinefume/Projectiles/BrinefumeBoilZoneProj.cs:50-60 | Content/GameModes/BrutalMobs/Ambience/Cindercrag/Projectiles/CindercragVentProj.cs:100-110 | Content/GameModes/BrutalMobs/Ambience/Rainveil/Projectiles/RainveilThunderboltProj.cs:54-64 | Content/GameModes/BrutalMobs/Ambience/Rotmire/Projectiles/RotmireVentProj.cs:73-83 | Content/GameModes/BrutalMobs/Ambience/Starfall/Projectiles/StarfallAfterburstProj.cs:78-88 | Content/GameModes/BrutalMobs/Ambience/Stratos/Projectiles/StratosFallingStarProj.cs:76-86 | Content/GameModes/BrutalMobs/Ambience/Verdant/Projectiles/VerdantMireFogProj.cs:63-73 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhVineLash.cs:68-78 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 9 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 9 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/GameModes/BrutalMobs/Ambience/Rainveil/Projectiles/RainveilThunderboltProj.cs:69` calls `CanDamage` and `Content/GameModes/BrutalMobs/Ambience/Brinefume/Projectiles/BrinefumeBoilZoneProj.cs:64` 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 × 9) Content/GameModes/BrutalMobs/Ambience/Ashreign/Projectiles/AshreignMagmaBeadProj.cs:39 — Content/GameModes/BrutalMobs/Ambience/Ashreign/Projectiles/AshreignMagmaBeadProj.cs:39-49 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhShellSpike.cs:26-36 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhStingerBolt.cs:30-40 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhTridentBolt.cs:29-39 | Content/GameModes/BrutalMobs/Sky/Projectiles/SkyFeatherBolt.cs:27-37 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Projectiles/BrutalBeeStinger.cs:30-40 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Projectiles/HoneyGlobProj.cs:19-29 | Content/Scenarios/OldNet/NPCs/OldNetTurretICE.cs:213-223 | Content/Scenarios/OldNet/NPCs/OldNetWardenICE.cs:1064-1074 — before extracting anything, compare `Content/GameModes/BrutalMobs/Ambience/Ashreign/Projectiles/AshreignMagmaBeadProj.cs` and `Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhShellSpike.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/GameModes/BrutalMobs/Sky/Projectiles/SkyFeatherBolt.cs:40` calls `CanDamage` and `Content/GameModes/BrutalMobs/Ambience/Ashreign/Projectiles/AshreignMagmaBeadProj.cs:51` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (7 lines × 8) · ×5
  • Duplicated block (7 lines × 8) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:837 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:837-843 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:828-834 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:711-717 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:646-652 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1048-1054 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:952-958 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:941-947 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:981-987 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 8 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 8 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:837` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 8) Content/GameModes/BrutalMobs/Ambience/Fleshfen/FleshfenPRT_BloodDrop.cs:122 — Content/GameModes/BrutalMobs/Ambience/Fleshfen/FleshfenPRT_BloodDrop.cs:122-130 | Content/LegendWeapon/HalibutLegend/FishSkills/FishHoneyVFX.cs:186-194 | Content/LegendWeapon/HalibutLegend/FishSkills/FishMudVFX.cs:111-119 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendParticles.cs:485-491 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Rendering/BKSParticles.cs:170-176 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Rendering/QueenBeePRT.cs:71-78 | Content/PRTTypes/PRT_GhostRainDrop.cs:177-185 | Content/PRTTypes/PRT_TurnkeyDrip.cs:82-89 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 8 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 8 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/Fleshfen/FleshfenPRT_BloodDrop.cs:122` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendParticles.cs:492` calls `Draw`, `Vector2` and `Content/NPCs/BrutalNPCs/BrutalKingSlime/Rendering/BKSParticles.cs:177` does not — after which the two agree again for 3 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 × 8) Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineStorageProvider.cs:220 — Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineStorageProvider.cs:220-226 | Content/Industrials/ElectricPowers/Crushers/CrusherStorageProvider.cs:253-261 | Content/Industrials/ElectricPowers/Incinerators/IncineratorStorageProvider.cs:275-283 | Content/Industrials/ElectricPowers/Recyclers/RecyclerStorageProvider.cs:231-239 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterStorageProvider.cs:238-244 | Content/Industrials/Generator/Biomass/BiomassStorageProvider.cs:220-227 | Content/Industrials/Generator/Thermal/ThermalStorageProvider.cs:236-243 | Content/Industrials/Generator/Thermal/ThermalStorageProvider.cs:476-483 — before extracting anything, compare `Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineStorageProvider.cs` and `Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterStorageProvider.cs` as WHOLE FILES: this scan already matched 3 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineStorageProvider.cs:220` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (7 lines × 8) Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:190 — Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:190-196 | Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzCrystalProj.cs:262-268 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerFrostPulseProj.cs:137-143 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerIceSpikeProj.cs:173-179 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenChandelierProj.cs:146-152 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenCrystalPrisonProj.cs:164-170 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenRoyalChandelierProj.cs:155-161 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Rendering/QueenPrismNodeRenderer.cs:58-64 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 8 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 8 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/NPCs/BrutalNPCs/BrutalQueenSlime/Rendering/QueenPrismNodeRenderer.cs:68` calls `SetValue` and `Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:200` 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 × 8) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1179 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1179-1186 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:939-945 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:997-1003 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1532-1540 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:1002-1008 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:900-906 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:960-967 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:933-939 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1179` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (10–12 lines × 2) · ×5
  • Duplicated block (10–12 lines × 2) Content/Cyberwares/Implementation/Sandevistans/SandevistanHUD.cs:259 — Content/Cyberwares/Implementation/Sandevistans/SandevistanHUD.cs:259-270 | Content/Cyberwares/Implementation/Sandevistans/SandevistanHUD.cs:285-294 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Cyberwares/Implementation/Sandevistans/SandevistanHUD.cs:259` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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 (10–12 lines × 2) Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFin.cs:334 — Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFin.cs:334-343 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Rendering/FishronStormSky.cs:226-237 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (10–12 lines × 2) Content/Items/Melee/Abyssrends/AbyssrendUndercurrent.cs:107 — Content/Items/Melee/Abyssrends/AbyssrendUndercurrent.cs:107-118 | Content/Items/Melee/TideReapers/TideReaperWave.cs:73-82 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Melee/Abyssrends/AbyssrendUndercurrent.cs:105` calls `FindTarget` and `Content/Items/Melee/TideReapers/TideReaperWave.cs:72` 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 (10–12 lines × 2) Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberExecutionBoltProj.cs:405 — Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberExecutionBoltProj.cs:405-416 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberGlitchBoltProj.cs:146-155 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberExecutionBoltProj.cs:416` calls `SetValue`, `Clamp`, `DrawTrail` and `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberGlitchBoltProj.cs:155` 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 (10–12 lines × 2) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspacePlayer.cs:506 — Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspacePlayer.cs:506-517 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspacePlayer.cs:782-791 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspacePlayer.cs:506` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11 lines × 8) · ×5
  • Duplicated block (11 lines × 8) Content/Items/Accessories/BrutalRelics/Deerclops/WhiteoutVeilRender.cs:59 — Content/Items/Accessories/BrutalRelics/Deerclops/WhiteoutVeilRender.cs:59-69 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonImpactFX.cs:207-217 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Rendering/DeerclopsVeilRender.cs:58-68 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Rendering/FishronGrabVeil.cs:86-96 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Rendering/EmpressScreenRender.cs:93-103 | Content/NPCs/BrutalNPCs/BrutalGolem/Rendering/GolemScreenEffectRender.cs:51-61 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordScreenRender.cs:80-90 | Content/Renders/PrimeScreenEffectRender.cs:53-63 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 8 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 8 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/Deerclops/WhiteoutVeilRender.cs:59` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 8) Content/Items/Melee/DestroyersBlade.cs:524 — Content/Items/Melee/DestroyersBlade.cs:524-534 | Content/Items/Melee/DragonsScaleGreatsword.cs:547-557 | Content/Items/Melee/EnergySword.cs:563-573 | Content/Items/Melee/RebelBlade.cs:594-604 | Content/Items/Melee/StormGoddessSpears/StormGoddessSpearHeld.cs:534-544 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:529-539 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Rendering/KingSlimeGelFX.cs:235-246 | Content/NPCs/BrutalNPCs/BrutalPlantera/Rendering/PlanteraVineRenderer.cs:136-146 — before extracting anything, compare `Content/Items/Melee/DestroyersBlade.cs` and `Content/Items/Melee/DragonsScaleGreatsword.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 419 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DestroyersBlade.cs:524` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `effect` to `out SpriteEffects` in one and `Effect` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (11 lines × 8) Content/Items/Melee/DestroyersBlade.cs:521 — Content/Items/Melee/DestroyersBlade.cs:521-531 | Content/Items/Melee/DragonsScaleGreatsword.cs:544-554 | Content/Items/Melee/EnergySword.cs:560-570 | Content/Items/Melee/RebelBlade.cs:591-601 | Content/Items/Melee/StormGoddessSpears/StormGoddessSpearHeld.cs:531-541 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:526-536 | Content/Items/Stones/Marbles/MarbleClub.cs:593-603 | Content/Items/Stones/Marbles/MarbleHuntingKnife.cs:410-420 — before extracting anything, compare `Content/Items/Melee/DestroyersBlade.cs` and `Content/Items/Melee/DragonsScaleGreatsword.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 419 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DestroyersBlade.cs:521` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 8) Content/GameModes/BrutalMobs/Ambience/DuneStorm/Projectiles/DuneStormSandLashOmen.cs:38 — Content/GameModes/BrutalMobs/Ambience/DuneStorm/Projectiles/DuneStormSandLashOmen.cs:38-48 | Content/GameModes/BrutalMobs/Ambience/Sporeshine/Projectiles/SporeshineCapSwellProj.cs:49-59 | Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdCastOmen.cs:107-117 | Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdHammerConeOmen.cs:70-80 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmYetiConeOmen.cs:71-81 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionSurfOmen.cs:46-56 | Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomVineWhipOmen.cs:51-61 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandConeTelegraph.cs:97-107 — before extracting anything, compare `Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdHammerConeOmen.cs` and `Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmYetiConeOmen.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdCastOmen.cs:120` calls `CanDamage` and `Content/GameModes/BrutalMobs/Ambience/DuneStorm/Projectiles/DuneStormSandLashOmen.cs:50` 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 × 8) Content/GameModes/BrutalMobs/Ocean/Projectiles/OceanPulseRing.cs:97 — Content/GameModes/BrutalMobs/Ocean/Projectiles/OceanPulseRing.cs:97-107 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtBoardHookProj.cs:60-70 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtRicochetShot.cs:71-81 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronBoneShard.cs:19-29 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronBoneSpike.cs:30-40 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronCursedSkull.cs:30-40 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronGhostArmProj.cs:52-62 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronOrbitSkull.cs:44-54 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronCursedSkull.cs` and `Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronOrbitSkull.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 55 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtBoardHookProj.cs:72` calls `ShouldUpdatePosition`, `CanDamage` and `Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronBoneShard.cs:31` 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.
D4 · Code Duplication · Duplicated block (9 lines × 6) · ×5
  • Duplicated block (9 lines × 6) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1190 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1190-1198 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1270-1278 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:840-848 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:1012-1020 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:971-979 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1410-1418 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs` as WHOLE FILES: this scan already matched 40 separate duplicated blocks between them, totalling at least 467 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1190` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 6) Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaRender.cs:81 — Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaRender.cs:81-89 | Content/NPCs/BrutalNPCs/BrutalGolem/Core/GolemScreenEffects.cs:110-118 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Core/MLordScreenEffects.cs:96-104 | Content/NPCs/BrutalNPCs/BrutalPlantera/Core/PlanteraScreenFX.cs:103-111 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Core/SkeletronScreenEffects.cs:122-130 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Core/PrimeScreenEffects.cs:96-104 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalGolem/Core/GolemScreenEffects.cs` and `Content/NPCs/BrutalNPCs/BrutalMoonLord/Core/MLordScreenEffects.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaRender.cs:80` calls `Update` and `Content/NPCs/BrutalNPCs/BrutalPlantera/Core/PlanteraScreenFX.cs:102` 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 × 6) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistIceShard.cs:93 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistIceShard.cs:93-101 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsHail.cs:73-81 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraSeed.cs:67-75 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeBloodBee.cs:96-104 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeStinger.cs:142-150 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronBloodSkull.cs:103-111 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistIceShard.cs:93` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (9 lines × 6) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Projectiles/EmpressRepelRing.cs:29 — Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Projectiles/EmpressRepelRing.cs:29-37 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/PincerBindTether.cs:44-52 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordConstellationProj.cs:28-36 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenCrystalPrisonProj.cs:35-43 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenRoyalChandelierProj.cs:53-61 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofRotEyeBudProj.cs:39-47 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times.
  • Duplicated block (9 lines × 6) Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2EscapeTunnel.cs:420 — Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2EscapeTunnel.cs:420-428 | Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Palette.cs:155-163 | Content/Scenarios/Dungeonworld/Gen/Layers/L4/L4Palette.cs:129-137 | Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Palette.cs:167-175 | Content/Scenarios/Dungeonworld/Gen/Layers/L7/L7Style.cs:163-171 | Content/Scenarios/Kiyume/Gen/KiyumeTileBrush.cs:160-168 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (8–10 lines × 3) · ×5
  • Duplicated block (8–10 lines × 3) Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtBannerMark.cs:91 — Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtBannerMark.cs:91-100 | Content/GameModes/BrutalMobs/Sandveil/SandveilBrutalNPC.cs:314-321 | Content/GameModes/BrutalMobs/Wastes/WastesBrutalNPC.cs:260-267 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtBannerMark.cs:91` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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–10 lines × 3) Content/GameModes/GodSmith/Weapons/Shortswords/GsThrustHeldBase.cs:961 — Content/GameModes/GodSmith/Weapons/Shortswords/GsThrustHeldBase.cs:961-968 | Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:580-588 | Content/Items/Modifys/RBloodButcherer.cs:523-532 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (8–10 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:111 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:111-118 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:183-192 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:250-258 — 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, `Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:108` calls `Inflate` and `Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:180` 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–10 lines × 3) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:105 — Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:105-114 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowBurrowAmbushState.cs:99-106 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowDevourState.cs:316-324 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs` and `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowBurrowAmbushState.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 70 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note first that the copies are not typed on the same thing: the declarations holding them bind `context` to `DestroyerStateContext` in one and `EowStateContext` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (8–10 lines × 3) Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:201 — Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:201-208 | Content/Scenarios/Kiame/Overlay/OniRainExitTransition.cs:158-165 | Content/Scenarios/Kiame/Overlay/OniRainWorldTransition.cs:218-227 — before extracting anything, compare `Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs` and `Content/Scenarios/Kiame/Overlay/OniRainExitTransition.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 186 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:201` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8–9 lines × 4) · ×5
  • Duplicated block (8–9 lines × 4) Content/GameModes/BrutalMobs/Ambience/Tidecall/Projectiles/TidecallRogueWaveProj.cs:361 — Content/GameModes/BrutalMobs/Ambience/Tidecall/Projectiles/TidecallRogueWaveProj.cs:361-369 | Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:178-185 | Content/Scenarios/Dungeonworld/NPCs/UndrownedDepthMine.cs:202-209 | Content/Scenarios/Dungeonworld/NPCs/UndrownedTideWave.cs:156-164 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/NPCs/UndrownedDepthMine.cs:202` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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–9 lines × 4) Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:882 — Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:882-889 | Content/Items/Melee/NeutronGlaive.cs:563-571 | Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:697-705 | Content/Items/Modifys/RBloodButcherer.cs:682-690 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:882` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:697` calls `Color` and `Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:882` 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–9 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:856 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:856-864 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:868-876 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:830-837 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:841-848 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs` as WHOLE FILES: this scan already matched 79 separate duplicated blocks between them, totalling at least 1151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:856` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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–9 lines × 4) Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSShockwaveProj.cs:96 — Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSShockwaveProj.cs:96-103 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpLeapVortex.cs:146-154 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpMiniVortex.cs:145-153 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpVortexWall.cs:147-155 — before extracting anything, compare `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpLeapVortex.cs` and `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpMiniVortex.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 99 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSShockwaveProj.cs:96` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (8–9 lines × 4) Content/Scenarios/OldNet/Gen/Zones/Z1/Z1Rooms.cs:16 — Content/Scenarios/OldNet/Gen/Zones/Z1/Z1Rooms.cs:16-24 | Content/Scenarios/OldNet/Gen/Zones/Z2/Z2Rooms.cs:19-26 | Content/Scenarios/OldNet/Gen/Zones/Z3/Z3Rooms.cs:19-26 | Content/Scenarios/OldNet/Gen/Zones/Z3/Z3Rooms.cs:215-222 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/OldNet/Gen/Zones/Z1/Z1Rooms.cs:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (6–8 lines × 2) · ×5
  • Duplicated block (6–8 lines × 2) Content/HackTimes/HackRamRenderer.cs:457 — Content/HackTimes/HackRamRenderer.cs:457-464 | Content/HackTimes/HackRamRenderer.cs:470-475 — 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 (6–8 lines × 2) Content/Items/Magic/Everdeeps/EverdeepVFX.cs:50 — Content/Items/Magic/Everdeeps/EverdeepVFX.cs:50-55 | Content/LegendWeapon/HalibutLegend/OceanCurrentParticles.cs:100-107 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/Everdeeps/EverdeepVFX.cs:50` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6–8 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainDeco.cs:379 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainDeco.cs:379-386 | Content/LegendWeapon/KikasaLegend/KikasaWisps/KikasaWispFX.cs:192-197 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainDeco.cs:376` calls `Lerp`, `Vector3` and `Content/LegendWeapon/KikasaLegend/KikasaWisps/KikasaWispFX.cs:189` 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 (6–8 lines × 2) Content/NPCs/SeaShrimp/Projectiles/SeaShrimpLeapVortex.cs:101 — Content/NPCs/SeaShrimp/Projectiles/SeaShrimpLeapVortex.cs:101-108 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpMiniVortex.cs:83-88 — before extracting anything, compare `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpLeapVortex.cs` and `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpMiniVortex.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 99 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6–8 lines × 2) Content/Scenarios/Kiyume/Fog/KiyumeFogSystem.cs:293 — Content/Scenarios/Kiyume/Fog/KiyumeFogSystem.cs:293-300 | Content/Scenarios/Kiyume/Fog/KiyumeGroundFogRender.cs:150-155 — 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. 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.
D4 · Code Duplication · Duplicated block (5 lines × 15) · ×5
  • Duplicated block (5 lines × 15) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1189 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1189-1193 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:947-951 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1210-1214 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:1005-1009 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1543-1547 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1127-1131 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1269-1273 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:1012-1016 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:839-843 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:1081-1085 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:1011-1015 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:908-912 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:970-974 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:941-945 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1409-1413 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1189` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 15) Content/GameModes/BrutalMobs/Ambience/Frostveil/FrostveilPRT.cs:63 — Content/GameModes/BrutalMobs/Ambience/Frostveil/FrostveilPRT.cs:63-69 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDoubleCodVFX.cs:144-149 | Content/LegendWeapon/HalibutLegend/FishSkills/FishIchornVFX.cs:184-189 | Content/LegendWeapon/HalibutLegend/FishSkills/FishScorpioPRT.cs:71-76 | Content/LegendWeapon/HalibutLegend/FishSkills/FishSwarmVFX.cs:316-321 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:324-328 | Content/LegendWeapon/KikasaLegend/KikasaWisps/KikasaWispPRT.cs:58-62 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Rendering/BKSParticles.cs:64-69 | Content/PRTTypes/PRT_GhostRainYank.cs:68-73 | Content/PRTTypes/PRT_HeartcarverDroplet.cs:49-54 | Content/PRTTypes/PRT_KikasaInkBead.cs:61-65 | Content/PRTTypes/PRT_KikasaTwinsFlame.cs:72-76 | Content/Scenarios/Dungeonworld/NPCs/GaolFireBolt.cs:274-278 | Content/Scenarios/Dungeonworld/NPCs/OverseerSlagGlob.cs:252-256 | Content/Scenarios/Dungeonworld/NPCs/UndrownedTideWave.cs:244-248 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 15 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 15 times. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/HalibutLegend/FishSkills/FishIchornVFX.cs:192` calls `Lerp`, `Draw`, `Vector2` and `Content/LegendWeapon/HalibutLegend/FishSkills/FishDoubleCodVFX.cs:152` 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 (5 lines × 15) Content/Items/Magic/AriaofTheCosmoses/AccretionDisk.cs:388 — Content/Items/Magic/AriaofTheCosmoses/AccretionDisk.cs:388-392 | Content/Items/Magic/NeutronWands/NeutronPulsar.cs:364-368 | Content/Items/Melee/SpearOfLonginuses/LonginusThrow.cs:141-145 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDemonicHell.cs:492-498 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:451-456 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:403-407 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:409-413 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:351-357 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:360-365 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:421-427 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:430-436 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:1583-1587 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:447-452 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:455-460 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Core/MLordLocomotion.cs:846-850 — there are 15 copies across 10 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 15 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/AriaofTheCosmoses/AccretionDisk.cs:388` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (5 lines × 15) Content/Scenarios/OldNet/Tiles/OldNetAccessTerminalTile.cs:132 — Content/Scenarios/OldNet/Tiles/OldNetAccessTerminalTile.cs:132-136 | Content/Scenarios/OldNet/Tiles/OldNetBreakerTile.cs:72-76 | Content/Scenarios/OldNet/Tiles/OldNetCacheTile.cs:99-103 | Content/Scenarios/OldNet/Tiles/OldNetCipherVaultTile.cs:107-111 | Content/Scenarios/OldNet/Tiles/OldNetColdNodeTile.cs:103-107 | Content/Scenarios/OldNet/Tiles/OldNetDataNodeTile.cs:108-112 | Content/Scenarios/OldNet/Tiles/OldNetEchoNodeTile.cs:108-112 | Content/Scenarios/OldNet/Tiles/OldNetEncryptedNodeTile.cs:128-132 | Content/Scenarios/OldNet/Tiles/OldNetEscrowTile.cs:131-135 | Content/Scenarios/OldNet/Tiles/OldNetEventNodeTile.cs:101-105 | Content/Scenarios/OldNet/Tiles/OldNetLedgerDockTile.cs:86-90 | Content/Scenarios/OldNet/Tiles/OldNetLogoutTerminalTile.cs:85-89 | Content/Scenarios/OldNet/Tiles/OldNetRelayTile.cs:95-99 | Content/Scenarios/OldNet/Tiles/OldNetSentryMineTile.cs:100-104 | Content/Scenarios/OldNet/Tiles/OldNetTripwireTile.cs:92-96 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/OldNet/Tiles/OldNetAccessTerminalTile.cs:132` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (5 lines × 15) Content/Items/Melee/OniMachete.cs:325 — Content/Items/Melee/OniMachete.cs:325-329 | Content/Items/Melee/Shatterfangs/ShatterfangRepairHeld.cs:262-266 | Content/Items/Ranged/PallbearerAssets.cs:199-203 | Content/Items/Ranged/TiroFinales/TiroFinaleHeld.cs:724-728 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCrimsonTiger.cs:206-210 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDrizzle.cs:36-40 | Content/LegendWeapon/HalibutLegend/FishSkills/FishFrostMinnowVFX.cs:188-192 | Content/LegendWeapon/HalibutLegend/FishSkills/FishHarpy.cs:844-848 | Content/LegendWeapon/HalibutLegend/FishSkills/FishHungerVFX.cs:28-32 | Content/LegendWeapon/HalibutLegend/FishSkills/FishNeonTetraVFX.cs:38-42 | Content/LegendWeapon/HalibutLegend/FishSkills/FishPengVFX.cs:187-191 | Content/LegendWeapon/HalibutLegend/FishSkills/FishPrincessVFX.cs:211-215 | Content/LegendWeapon/HalibutLegend/FishSkills/FishofCthuluVFX.cs:105-109 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSlashRenderer.cs:98-102 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleRenderer.cs:121-125 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 15 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 15 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/OniMachete.cs:325` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleRenderer.cs:116` calls `EaseOutCubic`, `Pow`, `Clamp` and `Content/Items/Melee/OniMachete.cs:321` 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.
D4 · Code Duplication · Duplicated block (4–6 lines × 3) · ×5
  • Duplicated block (4–6 lines × 3) Content/GameModes/BrutalMobs/Ambience/Lumindepth/LumindepthAmbientRender.cs:97 — Content/GameModes/BrutalMobs/Ambience/Lumindepth/LumindepthAmbientRender.cs:97-100 | Content/GameModes/BrutalMobs/Ambience/Mireheart/MireheartAmbience.cs:289-294 | Content/GameModes/BrutalMobs/Ambience/Rimehollow/RimehollowRender.cs:80-85 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/Lumindepth/LumindepthAmbientRender.cs:97` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (4–6 lines × 3) Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:605 — Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:605-610 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:614-619 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:628-631 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:605` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:626` calls `NextFloat`, `Configure` and `Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:605` 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 (4–6 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:905 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:905-908 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:927-932 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:1604-1609 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:927` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (4–6 lines × 3) Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronGeyserProj.cs:78 — Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronGeyserProj.cs:78-83 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronIntroState.cs:83-88 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronTsunamiSweepState.cs:105-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronGeyserProj.cs:78` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronGeyserProj.cs:78` calls `NextFloat` and `Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronTsunamiSweepState.cs:105` 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 (4–6 lines × 3) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:2581 — Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:2581-2584 | Content/Scenarios/Kiyume/NPCs/MinoFisherYokai.cs:296-301 | Content/Scenarios/Kiyume/NPCs/RidgeWalkerYokai.cs:498-503 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:2581` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (4–5 lines × 4) · ×5
  • Duplicated block (4–5 lines × 4) Content/GameModes/BrutalMobs/Ambience/Cindercrag/CindercragGlowRender.cs:110 — Content/GameModes/BrutalMobs/Ambience/Cindercrag/CindercragGlowRender.cs:110-114 | Content/GameModes/BrutalMobs/Ambience/Mireheart/MireheartAmbience.cs:175-179 | Content/GameModes/BrutalMobs/Ambience/Stonewake/StonewakeFX.cs:125-129 | Content/GameModes/BrutalMobs/Ambience/Sunkendune/SunkenduneAmbience.cs:91-94 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/Cindercrag/CindercragGlowRender.cs:110` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (4–5 lines × 4) Content/Items/Magic/DragonsWord.cs:170 — Content/Items/Magic/DragonsWord.cs:170-173 | Content/Items/Magic/DragonsWord.cs:264-268 | Content/Items/Magic/DragonsWord.cs:550-553 | Content/Items/Magic/DragonsWord.cs:620-624 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/DragonsWord.cs:170` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Magic/DragonsWord.cs:263` calls `Configure` and `Content/Items/Magic/DragonsWord.cs:549` does not — after which the two agree again for 3 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 (4–5 lines × 4) Content/NPCs/ScrapCommanders/States/ScrapAllOutCommandState.cs:91 — Content/NPCs/ScrapCommanders/States/ScrapAllOutCommandState.cs:91-95 | Content/NPCs/ScrapCommanders/States/ScrapDeathState.cs:203-206 | Content/NPCs/ScrapCommanders/States/ScrapLaserMatrixState.cs:130-135 | Content/NPCs/ScrapCommanders/States/ScrapLegionState.cs:94-97 — 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 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/ScrapCommanders/States/ScrapAllOutCommandState.cs:91` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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 (4–5 lines × 4) Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:817 — Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:817-820 | Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:860-865 | Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:886-889 | Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:1192-1196 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:817` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (4–5 lines × 4) Content/Scenarios/Himayo/Gifts/HimayoCalamitasCloneGift.cs:26 — Content/Scenarios/Himayo/Gifts/HimayoCalamitasCloneGift.cs:26-29 | Content/Scenarios/Himayo/Gifts/HimayoDevourerOfGodsGift.cs:26-29 | Content/Scenarios/Himayo/Gifts/HimayoMoonLordGift.cs:27-31 | Content/Scenarios/Himayo/Gifts/HimayoWallOfFleshGift.cs:27-31 — 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 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Himayo/Gifts/HimayoCalamitasCloneGift.cs:26` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
IC1 · Incompleteness & stubs · Both branches open with the same statements · ×5
  • Both branches open with the same statements — the condition does not decide them Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainHoverState.cs:96 — The first 2 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
  • Both branches open with the same statements — the condition does not decide them Content/NPCs/BrutalNPCs/BrutalQueenBee/BrutalQueenBeeAI.cs:473 — The first 1 statement of the `if` and of the `else` are identical, so it runs on both paths regardless of the condition. Lift it above the `if` — leaving it duplicated inside makes the branches read as though they handled this differently.
  • Both branches open with the same statements — the condition does not decide them Content/NPCs/FestersandSerpents/States/FssMoltGrowthState.cs:90 — The first 2 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
  • Both branches open with the same statements — the condition does not decide them Content/NPCs/Modifys/ModifyTruffle.cs:44 — The first 2 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
  • Both branches open with the same statements — the condition does not decide them Content/Structures/DatIO/JunkmanBase.cs:86 — The first 2 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
D4 · Code Duplication · Near-duplicate member family (5 members, 18 shared lines) · ×4
  • Near-duplicate member family (5 members, 18 shared lines) Content/Industrials/ElectricPowers/LifeWeavers/LifeWeaverTile.cs:47 — Content/Industrials/ElectricPowers/LifeWeavers/LifeWeaverTile.cs:47-72 | Content/Industrials/ElectricPowers/LifeWeavers/WGGLifeWeaver.cs:99-124 | Content/Industrials/ElectricPowers/Lumberjacks/LumberjackTile.cs:46-71 | Content/Industrials/ElectricPowers/Lumberjacks/WGGLumberjack.cs:94-119 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatTile.cs:92-125 — These 5 members are variants of one another: a block of 18 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 5 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 5 times.
  • Near-duplicate member family (5 members, 18 shared lines) Content/Items/Melee/NeutronGlaive.cs:1252 — Content/Items/Melee/NeutronGlaive.cs:1252-1277 | Content/Items/Melee/NeutronGlaive.cs:1317-1356 | Content/Items/Melee/NeutronScythe.cs:322-348 | Content/Items/Ranged/NeutronBows/EXNeutronExplosionRanged.cs:29-54 | Content/Items/Ranged/NeutronBows/NeutronExplosionRanged.cs:28-53 — These 5 members are variants of one another: a block of 18 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 5 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 5 times.
  • Near-duplicate member family (5 members, 18 shared lines) Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordRayRender.cs:17 — Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordRayRender.cs:17-66 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenGaleFieldProj.cs:97-137 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenPrismBeamProj.cs:262-307 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofRetinaScanBeam.cs:206-257 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofRotBeamProj.cs:137-187 — These 5 members are variants of one another: a block of 18 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 5 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 5 times.
  • Near-duplicate member family (5 members, 18 shared lines) Content/UIs/UIEffect/BrimstoneShaderPanel.cs:19 — Content/UIs/UIEffect/BrimstoneShaderPanel.cs:19-45 | Content/UIs/UIEffect/CyberShaderPanel.cs:18-43 | Content/UIs/UIEffect/SeaShaderPanel.cs:19-45 | Content/UIs/UIEffect/SulfseaShaderPanel.cs:19-45 | Content/UIs/UIEffect/TzeentchShaderPanel.cs:19-45 — These 5 members are variants of one another: a block of 18 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 5 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 5 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 19 shared lines) · ×4
  • Near-duplicate member family (4 members, 19 shared lines) Content/Industrials/Generator/Biomass/BiomassGenerator.cs:117 — Content/Industrials/Generator/Biomass/BiomassGenerator.cs:117-144 | Content/Industrials/Generator/Thermal/ThermalGenerator.cs:84-110 | Content/Industrials/Generator/Thermal/ThermalGeneratorMK2.cs:84-110 | Content/Scenarios/Draedon/Quest/DeploySignaltowers/CQETConstructor.cs:97-122 — These 4 members are variants of one another: a block of 19 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 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 4 times.
  • Near-duplicate member family (4 members, 19 shared lines) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainRender.cs:40 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainRender.cs:40-97 | Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainRender.cs:207-253 | Content/Scenarios/Kiame/Overlay/OniUmbrellaPuddleRender.cs:27-93 | Content/Scenarios/Kiame/Water/KiameWaterRender.cs:58-144 — These 4 members are variants of one another: a block of 19 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 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 4 times.
  • Near-duplicate member family (4 members, 19 shared lines) Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamGroundField.cs:90 — Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamGroundField.cs:90-124 | Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSim.cs:99-139 | Content/Scenarios/Kiyume/Fog/KiyumeFogSim.cs:169-209 | Content/Scenarios/Kiyume/Fog/KiyumeGroundField.cs:105-139 — These 4 members are variants of one another: a block of 19 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 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 4 times.
  • Near-duplicate member family (4 members, 19 shared lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:64 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:64-120 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:69-119 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterGlob.cs:60-120 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenCrystalShard.cs:57-108 — These 4 members are variants of one another: a block of 19 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 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 4 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 12 shared lines) · ×4
  • Near-duplicate member family (4 members, 12 shared lines) Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:133 — Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:133-181 | Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgStabGlintOmen.cs:121-157 | Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyGhostNameThread.cs:145-186 | Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyRavenSwoopOmen.cs:135-171 — These 4 members are variants of one another: a block of 12 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 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 4 times.
  • Near-duplicate member family (4 members, 12 shared lines) Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawWormProj.cs:555 — Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawWormProj.cs:555-597 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowBreachOmen.cs:71-111 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowDevourOmen.cs:97-153 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowGeyserProj.cs:180-205 — These 4 members are variants of one another: a block of 12 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 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 4 times.
  • Near-duplicate member family (4 members, 12 shared lines) Content/Narrative/MusicToast.cs:350 — Content/Narrative/MusicToast.cs:350-376 | Content/Narrative/MusicToast.cs:407-434 | Content/Narrative/MusicToast.cs:489-510 | Content/Narrative/MusicToast.cs:522-543 — These 4 members are variants of one another: a block of 12 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 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 4 times.
  • Near-duplicate member family (4 members, 12 shared lines) Content/Scenarios/SupCal/End/EternalBlazingNow/EbnEffect.cs:327 — Content/Scenarios/SupCal/End/EternalBlazingNow/EbnEffect.cs:327-343 | Content/Scenarios/SupCal/End/EternalBlazingNow/EbnEffect.cs:345-369 | Content/Scenarios/SupCal/SupCalEffect.cs:151-170 | Content/Scenarios/SupCal/SupCalEffect.cs:172-191 — These 4 members are variants of one another: a block of 12 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 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 4 times.
D4 · Code Duplication · Near-duplicate member family (3 members, 9 shared lines) · ×4
  • Near-duplicate member family (3 members, 9 shared lines) Content/Cyberwares/UIs/CyberBodyRenderer.cs:514 — Content/Cyberwares/UIs/CyberBodyRenderer.cs:514-572 | Content/Cyberwares/UIs/CyberBodyRenderer.cs:575-619 | Content/Cyberwares/UIs/CyberBodyRenderer.cs:622-670 — These 3 members are variants of one another: a block of 9 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 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 3 times.
  • Near-duplicate member family (3 members, 9 shared lines) Content/Items/Stones/Granites/GraniteEffects.cs:52 — Content/Items/Stones/Granites/GraniteEffects.cs:52-69 | Content/Items/Stones/Granites/GraniteFlower.cs:355-377 | Content/Items/Stones/Granites/GraniteTome.cs:363-399 — These 3 members are variants of one another: a block of 9 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 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 3 times.
  • Near-duplicate member family (3 members, 9 shared lines) Content/Narrative/Presentation/Skins/Brimstone/BrimstoneDialogueSkin.cs:34 — Content/Narrative/Presentation/Skins/Brimstone/BrimstoneDialogueSkin.cs:34-49 | Content/Narrative/Presentation/Skins/Sea/SeaDialogueSkin.cs:31-47 | Content/Narrative/Presentation/Skins/StarStream/StarStreamDialogueSkin.cs:34-52 — These 3 members are variants of one another: a block of 9 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 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 3 times.
  • Near-duplicate member family (3 members, 9 shared lines) Content/Scenarios/OldNet/Tiles/OldNetBreakerTile.cs:69 — Content/Scenarios/OldNet/Tiles/OldNetBreakerTile.cs:69-123 | Content/Scenarios/OldNet/Tiles/OldNetEventNodeTile.cs:86-136 | Content/Scenarios/OldNet/Tiles/OldNetSentryMineTile.cs:97-177 — These 3 members are variants of one another: a block of 9 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 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 3 times.
D4 · Code Duplication · Edited copy of a member (57 corresponding lines) · ×4
  • Edited copy of a member (57 corresponding lines) Content/Items/Melee/DestroyersBlade.cs:643 — Content/Items/Melee/DestroyersBlade.cs:643-699 | Content/Items/Melee/DestroyersBladeEXs/DestroyersBeamEX.cs:127-183 — These two members are one piece of code written twice and then edited apart: 57 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (57 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:722 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:722-785 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:725-781 — These two members are one piece of code written twice and then edited apart: 57 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (57 corresponding lines) Content/Cyberwares/UIs/CyberwareUI.cs:136 — Content/Cyberwares/UIs/CyberwareUI.cs:136-200 | Content/NPCs/Victors/UIs/VictorClinicUI.cs:117-173 — These two members are one piece of code written twice and then edited apart: 57 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (57 corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishBunny.cs:23 — Content/LegendWeapon/HalibutLegend/FishSkills/FishBunny.cs:23-82 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCat.cs:23-79 — These two members are one piece of code written twice and then edited apart: 57 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (56 corresponding lines) · ×4
  • Edited copy of a member (56 corresponding lines) Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs:69 — Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs:69-146 | Content/LegendWeapon/SHPCLegend/UI/DomainWheel/SHPCDomainWheelUI.cs:91-146 — These two members are one piece of code written twice and then edited apart: 56 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (56 corresponding lines) Content/Scenarios/Dungeonworld/NPCs/OverseerDormantRig.cs:114 — Content/Scenarios/Dungeonworld/NPCs/OverseerDormantRig.cs:114-169 | Content/Scenarios/Dungeonworld/NPCs/UndrownedThrone.cs:120-175 — These two members are one piece of code written twice and then edited apart: 56 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (56 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:518 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:518-579 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:717-772 — These two members are one piece of code written twice and then edited apart: 56 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (56 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:825 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:825-893 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:579-634 — These two members are one piece of code written twice and then edited apart: 56 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 33+ corresponding lines) · ×4
  • Edited copies of one member (3 members, 33+ corresponding lines) Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolRoomSealTile.cs:51 — Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolRoomSealTile.cs:51-90 | Content/Scenarios/OldNet/Tiles/OldNetBulkheadTile.cs:39-71 | Content/Scenarios/OldNet/Tiles/OldNetSealGateTile.cs:46-91 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 33 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 33+ corresponding lines) Content/GameModes/BrutalMobs/Ambience/DuneStorm/DuneStormRender.cs:228 — Content/GameModes/BrutalMobs/Ambience/DuneStorm/DuneStormRender.cs:228-263 | Content/GameModes/BrutalMobs/Ambience/Starfall/StarfallAmbientRender.cs:238-273 | Content/Scenarios/Dungeonworld/Ambience/DungeonworldAmbientRender.cs:198-230 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 33 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 33+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:504 — Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:504-536 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:770-802 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:804-836 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 33 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 33+ corresponding lines) Content/EntrustManager/Styles/DraedonManagerStyle.cs:51 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:51-86 | Content/EntrustManager/Styles/ForestManagerStyle.cs:51-86 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:50-82 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 33 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 30+ corresponding lines) · ×4
  • Edited copies of one member (3 members, 30+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1143 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1143-1172 | Content/LegendWeapon/KikasaLegend/KikasaVaults/KikasaLakeFX.cs:667-701 | Content/LegendWeapon/KikasaLegend/KikasaVaults/KikasaVaultRenderer.cs:106-138 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 30 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 30+ corresponding lines) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingUI.cs:363 — Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingUI.cs:363-392 | Content/LegendWeapon/SHPCLegend/UI/SHPCCyberPanel.cs:329-366 | Content/LegendWeapon/SHPCLegend/UI/SHPCModPanel.cs:221-254 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 30 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 30+ corresponding lines) Content/HackTimes/Targets/BossPartTargetType.cs:67 — Content/HackTimes/Targets/BossPartTargetType.cs:67-101 | Content/HackTimes/Targets/SignalTowerTargetType.cs:13-42 | Content/HackTimes/Targets/TurretTargetType.cs:13-42 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 30 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 30+ corresponding lines) Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteRingRender.cs:19 — Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteRingRender.cs:19-48 | Content/Items/Accessories/BrutalRelics/Skeletron/SoulbindingArmRender.cs:119-151 | Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadCommandRender.cs:33-67 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 30 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 22+ corresponding lines) · ×4
  • Edited copies of one member (3 members, 22+ corresponding lines) Content/NPCs/ScrapCommanders/ScrapCommander.cs:615 — Content/NPCs/ScrapCommanders/ScrapCommander.cs:615-642 | Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:2562-2587 | Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:1185-1206 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 22+ corresponding lines) Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:783 — Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:783-808 | Content/QuestLogs/Styles/ForestQuestLogStyle.cs:533-554 | Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:720-742 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 22+ corresponding lines) Content/Scenarios/Himayo/ToriiShrines/ToriiShrine.cs:64 — Content/Scenarios/Himayo/ToriiShrines/ToriiShrine.cs:64-87 | Content/Scenarios/Kiame/Gate/KiameGateSpawn.cs:61-82 | Content/Scenarios/Kiame/Overlay/OniUmbrellaWorldSpawn.cs:60-82 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 22+ corresponding lines) Content/Scenarios/Dungeonworld/Ambience/DungeonworldAmbientFX.cs:292 — Content/Scenarios/Dungeonworld/Ambience/DungeonworldAmbientFX.cs:292-314 | Content/Scenarios/Dungeonworld/Ambience/DungeonworldSnuff.cs:156-178 | Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSystem.cs:111-132 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 21+ corresponding lines) · ×4
  • Edited copies of one member (4 members, 21+ corresponding lines) Content/LegendWeapon/HalibutLegend/UI/HalibutItemTooltipPanel.cs:73 — Content/LegendWeapon/HalibutLegend/UI/HalibutItemTooltipPanel.cs:73-93 | Content/LegendWeapon/KikasaLegend/UI/KikasaItemTooltipPanel.cs:88-109 | Content/LegendWeapon/OnikiriLegend/UI/OniItemTooltipPanel.cs:71-96 | Content/LegendWeapon/SHPCLegend/UI/SHPCItemTooltipPanel.cs:74-98 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 21+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:941 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:941-963 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:822-846 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1164-1188 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:981-1001 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 21+ corresponding lines) Content/Industrials/ElectricPowers/Apiaries/ApiaryTP.cs:219 — Content/Industrials/ElectricPowers/Apiaries/ApiaryTP.cs:219-242 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherTP.cs:246-269 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerTP.cs:243-263 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatTP.cs:198-219 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 21+ corresponding lines) Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:784 — Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:784-804 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconTP.cs:318-338 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatTP.cs:603-623 | Content/Industrials/ElectricPowers/Throwers/ThrowerTP.cs:413-433 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 16+ corresponding lines) · ×4
  • Edited copies of one member (5 members, 16+ corresponding lines) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:220 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:220-237 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs:242-262 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs:228-246 | Content/Industrials/ElectricPowers/Sensors/SensorUI.cs:183-198 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:217-233 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 16+ corresponding lines) Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:956 — Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:956-971 | Content/Items/Melee/NeutronGlaive.cs:631-646 | Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:769-784 | Content/Items/Modifys/RBloodButcherer.cs:753-768 | Content/Items/Modifys/RTerraBlades/RTerraBladeHeld.cs:914-929 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 16+ corresponding lines) Content/GameModes/GodSmith/Weapons/SummonMinions/Schemes/GsDeadlySphereStaff.cs:48 — Content/GameModes/GodSmith/Weapons/SummonMinions/Schemes/GsDeadlySphereStaff.cs:48-68 | Content/GameModes/GodSmith/Weapons/SummonMinions/Schemes/GsEmpressBlade.cs:43-58 | Content/GameModes/GodSmith/Weapons/SummonMinions/Schemes/GsRavenStaff.cs:48-63 | Content/GameModes/GodSmith/Weapons/SummonMinions/Schemes/GsStormTigerStaff.cs:45-63 | Content/GameModes/GodSmith/Weapons/SummonMinions/Schemes/GsXenoStaff.cs:49-67 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 16+ corresponding lines) Content/QuestLogs/QLNodes/BossQuests.cs:406 — Content/QuestLogs/QLNodes/BossQuests.cs:406-421 | Content/QuestLogs/QLNodes/BossQuests.cs:434-449 | Content/QuestLogs/QLNodes/BossQuests.cs:494-509 | Content/QuestLogs/QLNodes/CalamityHuntQuests.cs:43-60 | Content/QuestLogs/QLNodes/CalamityHuntQuests.cs:147-163 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 14+ corresponding lines) · ×4
  • Edited copies of one member (6 members, 14+ corresponding lines) Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:529 — Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:529-543 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:563-577 | Content/Industrials/ElectricPowers/Turrets/TurretControlUI.cs:377-390 | Content/Industrials/Generator/Biomass/BiomassGeneratorUI.cs:366-379 | Content/Industrials/Generator/GeneratorReadout.cs:346-359 | Content/Industrials/Generator/Thermal/ThermalGeneratorUI.cs:505-519 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 14+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsBloodSpike.cs:169 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsBloodSpike.cs:169-182 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:1462-1478 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:390-403 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonVesselWhip.cs:260-274 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraVine.cs:237-251 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:1166-1179 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 14+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:130 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:130-144 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:151-165 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:141-155 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:164-178 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:134-147 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:181-195 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 14+ corresponding lines) Content/LegendWeapon/HalibutLegend/UI/HalibutHudLead.cs:416 — Content/LegendWeapon/HalibutLegend/UI/HalibutHudLead.cs:416-436 | Content/LegendWeapon/KikasaLegend/UI/KikasaHudLead.cs:531-547 | Content/QuestLogs/Guide/QuestBookGuideLead.cs:203-219 | Content/Scenarios/OldNet/UI/OldNetCipherPanel.cs:436-449 | Content/Scenarios/OldNet/UI/OldNetDebriefPanel.cs:396-409 | Content/Scenarios/OldNet/UI/OldNetGuideLead.cs:176-192 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 14+ corresponding lines) · ×4
  • Edited copies of one member (4 members, 14+ corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1566 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1566-1579 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1269-1284 | Content/LegendWeapon/OnikiriLegend/OniBladePose.cs:263-277 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1468-1482 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 14+ corresponding lines) Content/GameModes/GodSmith/Prefixes/Ranged/GodSmithBallisticEndow.cs:46 — Content/GameModes/GodSmith/Prefixes/Ranged/GodSmithBallisticEndow.cs:46-59 | Content/GameModes/GodSmith/Prefixes/Ranged/GodSmithPhantomVolleyEndow.cs:38-54 | Content/GameModes/GodSmith/Prefixes/Rescue/GodSmithHiddenEdgeEndow.cs:51-64 | Content/GameModes/GodSmith/Prefixes/Speed/GodSmithAfterimageEndow.cs:48-62 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 14+ corresponding lines) Content/Items/Melee/DawnshatterAzures/DawnshatterSpike.cs:52 — Content/Items/Melee/DawnshatterAzures/DawnshatterSpike.cs:52-65 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBellWave.cs:45-58 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiInkThread.cs:124-137 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiThunderColumn.cs:46-59 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 14+ corresponding lines) Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconStorageProvider.cs:60 — Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconStorageProvider.cs:60-73 | Content/Industrials/ElectricPowers/Throwers/ThrowerStorageProvider.cs:61-79 | Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersStorageProvider.cs:61-77 | Content/Scenarios/OldDuke/OldDuchests/OldDuchestStorageProvider.cs:62-78 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 6+ corresponding lines) · ×4
  • Edited copies of one member (6 members, 6+ corresponding lines) Content/Cyberwares/Implementation/Sandevistans/SandevistanHUD.cs:519 — Content/Cyberwares/Implementation/Sandevistans/SandevistanHUD.cs:519-525 | Content/Cyberwares/UIs/CyberwareTheme.cs:76-82 | Content/HackTimes/HackRamRenderer.cs:558-564 | Content/Items/Magic/Pandemoniums/PandemoniumChannel.cs:885-890 | Content/Items/Magic/Pandemoniums/PandemoniumCircle.cs:366-372 | Content/Items/Magic/Pandemoniums/PandemoniumRSkill.cs:517-523 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 6+ corresponding lines) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterTile.cs:55 — Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterTile.cs:55-60 | Content/Industrials/ElectricPowers/Crushers/CrusherTile.cs:53-58 | Content/Industrials/ElectricPowers/Incinerators/IncineratorTile.cs:65-70 | Content/Industrials/ElectricPowers/Recyclers/RecyclerTile.cs:50-55 | Content/Industrials/MaterialFlow/ItemPipelines/ItemPipeline.cs:67-72 | Content/LegendWeapon/SHPCLegend/MoldProcessingTables/MoldProcessingTableTile.cs:51-56 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 6+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/PrimeFuryStates.cs:15 — Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/PrimeFuryStates.cs:15-20 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/States/WofDespawnState.cs:18-23 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/States/WofEyeScanState.cs:26-31 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/States/WofFleshSpikeState.cs:24-29 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/States/WofLeechWaveState.cs:36-42 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/States/WofMawVortexState.cs:27-32 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 6+ corresponding lines) Content/Industrials/ElectricPowers/HealingStations/HealStationTile.cs:67 — Content/Industrials/ElectricPowers/HealingStations/HealStationTile.cs:67-72 | Content/Industrials/ElectricPowers/ShieldGenerators/ShieldGeneratorTile.cs:67-72 | Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:161-166 | Content/Industrials/ElectricPowers/Turrets/CryoTurrets/CryoTurretTile.cs:67-72 | Content/Industrials/ElectricPowers/Turrets/FlameTurrets/FlameTurretTile.cs:67-72 | Content/Industrials/ElectricPowers/Turrets/LaserTurrets/LaserTurretTile.cs:67-72 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 7+ corresponding lines) · ×4
  • Edited copies of one member (6 members, 7+ corresponding lines) Content/Scenarios/OldDuke/CampsiteChatDialogue.cs:218 — Content/Scenarios/OldDuke/CampsiteChatDialogue.cs:218-225 | Content/Scenarios/OldDuke/CampsiteChatDialogue.cs:227-233 | Content/Scenarios/OldDuke/CampsiteChatDialogue.cs:253-260 | Content/Scenarios/OldDuke/CampsiteChatDialogue.cs:262-269 | Content/Scenarios/OldDuke/CampsiteChatDialogue.cs:295-302 | Content/Scenarios/OldDuke/CampsiteChatDialogue.cs:304-312 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 7+ corresponding lines) Content/GameModes/BrutalMobs/Ambience/Stratos/Projectiles/StratosFallingStarProj.cs:240 — Content/GameModes/BrutalMobs/Ambience/Stratos/Projectiles/StratosFallingStarProj.cs:240-248 | Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclManFlyFlaskProj.cs:129-137 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmMortarBlastProj.cs:108-117 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionClownBomb.cs:67-75 | Content/GameModes/BrutalMobs/Ocean/Projectiles/OceanPulseRing.cs:115-123 | Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraSporeCloud.cs:61-67 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 7+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishHoney.cs:201 — Content/LegendWeapon/HalibutLegend/FishSkills/FishHoney.cs:201-207 | Content/LegendWeapon/HalibutLegend/FishSkills/FishObsidian.cs:83-89 | Content/LegendWeapon/HalibutLegend/FishSkills/FishPrincess.cs:73-79 | Content/LegendWeapon/HalibutLegend/FishSkills/FishSlime.cs:88-94 | Content/LegendWeapon/HalibutLegend/FishSkills/FishVariegatedLard.cs:74-80 | Content/LegendWeapon/HalibutLegend/FishSkills/Fishotroning.cs:99-105 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 7+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenAerialBalletState.cs:39 — Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenAerialBalletState.cs:39-45 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenChandelierFallState.cs:31-38 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenCrystalDiveStompState.cs:30-38 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenSkySpikeCascadeState.cs:42-49 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenSpikeRingState.cs:41-48 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenWingGaleWaltzState.cs:33-40 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (28–29 lines × 2) · ×4
  • Duplicated block (28–29 lines × 2) Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:323 — Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:323-350 | Content/Items/Modifys/RBloodButcherer.cs:356-384 — before extracting anything, compare `Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs` and `Content/Items/Modifys/RBloodButcherer.cs` as WHOLE FILES: this scan already matched 36 separate duplicated blocks between them, totalling at least 458 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (28–29 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:869 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:869-896 | Content/NPCs/SeaShrimp/Kinematics/ShrimpSkeleton.cs:244-272 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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 (28–29 lines × 2) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1066 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1066-1094 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:829-856 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1066` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (28–29 lines × 2) Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSim.cs:196 — Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSim.cs:196-223 | Content/Scenarios/Kiyume/Fog/KiyumeFogSim.cs:284-312 — before extracting anything, compare `Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSim.cs` and `Content/Scenarios/Kiyume/Fog/KiyumeFogSim.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 174 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSim.cs:196` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (28 lines × 2) · ×4
  • Duplicated block (28 lines × 2) Content/Scenarios/Helen/Gifts/HelenGiftNarrativeTracker.cs:95 — Content/Scenarios/Helen/Gifts/HelenGiftNarrativeTracker.cs:95-122 | Content/Scenarios/Shepel/Gifts/ShepelBossGiftNarrative.cs:105-132 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Helen/Gifts/HelenGiftNarrativeTracker.cs:95` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (28 lines × 2) Content/Items/Melee/Arbiters/ArbiterManifestationSystem.cs:131 — Content/Items/Melee/Arbiters/ArbiterManifestationSystem.cs:131-158 | Content/Items/Melee/WeaverGrievanceses/WGManifestationSystem.cs:130-157 — before extracting anything, compare `Content/Items/Melee/Arbiters/ArbiterManifestationSystem.cs` and `Content/Items/Melee/WeaverGrievanceses/WGManifestationSystem.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (28 lines × 2) Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:277 — Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:277-304 | Content/LegendWeapon/OnikiriLegend/OniZanshinSlashs/OniZanshinSlash.cs:364-391 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:277` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (28 lines × 2) Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenBallroomStepState.cs:70 — Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenBallroomStepState.cs:70-97 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenSpikeRondoState.cs:79-106 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenBallroomStepState.cs:70` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (18–20 lines × 2) · ×4
  • Duplicated block (18–20 lines × 2) Content/Industrials/ElectricPowers/Collectors/CollectorArm.cs:569 — Content/Industrials/ElectricPowers/Collectors/CollectorArm.cs:569-588 | Content/Industrials/ElectricPowers/Collectors/CollectorArm.cs:616-633 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Collectors/CollectorArm.cs:569` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (18–20 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:942 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:942-961 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:942-959 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs` as WHOLE FILES: this scan already matched 70 separate duplicated blocks between them, totalling at least 835 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:942` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18–20 lines × 2) Content/LegendWeapon/OnikiriLegend/Tutorial/OnikiriTutorialPlayer.cs:153 — Content/LegendWeapon/OnikiriLegend/Tutorial/OnikiriTutorialPlayer.cs:153-170 | Content/TimeFreezes/WorldFreezePlayer.cs:84-103 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/Tutorial/OnikiriTutorialPlayer.cs:153` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18–20 lines × 2) Content/NPCs/BloomsandSerpents/States/BssCoilOrbitState.cs:198 — Content/NPCs/BloomsandSerpents/States/BssCoilOrbitState.cs:198-215 | Content/NPCs/BloomsandSerpents/States/BssTailSweepState.cs:253-272 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BloomsandSerpents/States/BssCoilOrbitState.cs:198` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (17–18 lines × 3) · ×4
  • Duplicated block (17–18 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:117 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:117-133 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:111-127 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeSkullBeamProj.cs:81-98 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs` and `Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 216 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:117` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17–18 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:127 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:127-143 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs:141-158 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:121-137 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 161 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:127` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17–18 lines × 3) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1203 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1203-1220 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1019-1035 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1209-1226 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1203` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (17–18 lines × 3) Content/Scenarios/Kiyume/NPCs/KiyumeHound.cs:1046 — Content/Scenarios/Kiyume/NPCs/KiyumeHound.cs:1046-1062 | Content/Scenarios/Kiyume/NPCs/KiyumeWhiteHound.cs:469-485 | Content/Scenarios/Kiyume/NPCs/RidgeWalkerYokai.cs:589-606 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Kiyume/NPCs/KiyumeHound.cs:1046` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (14 lines × 4) · ×4
  • Duplicated block (14 lines × 4) Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:338 — Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:338-351 | Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:384-397 | Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:430-443 | Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:476-489 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:338` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 4) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:396 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:396-409 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:323-336 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconUI.cs:358-371 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:396-409 — before extracting anything, compare `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs` and `Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 270 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (14 lines × 4) Content/Items/Magic/Pandemoniums/PandemoniumRainDrop.cs:97 — Content/Items/Magic/Pandemoniums/PandemoniumRainDrop.cs:97-110 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:506-520 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:772-786 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:806-820 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/Pandemoniums/PandemoniumRainDrop.cs:97` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:549 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:549-562 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:555-568 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:512-525 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:545-558 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs` as WHOLE FILES: this scan already matched 75 separate duplicated blocks between them, totalling at least 912 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (16–17 lines × 3) · ×4
  • Duplicated block (16–17 lines × 3) Content/Items/Melee/NeutronGlaive.cs:545 — Content/Items/Melee/NeutronGlaive.cs:545-560 | Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:676-692 | Content/Items/Modifys/RBloodButcherer.cs:664-679 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/NeutronGlaive.cs:545` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Modifys/RBloodButcherer.cs:659` calls `DrawBladeSet` and `Content/Items/Melee/NeutronGlaive.cs:540` 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 (16–17 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:953 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:953-969 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1340-1356 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:952-967 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs` as WHOLE FILES: this scan already matched 48 separate duplicated blocks between them, totalling at least 508 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:953` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16–17 lines × 3) Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordFreeEyeAI.cs:105 — Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordFreeEyeAI.cs:105-120 | Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordHandAI.cs:65-81 | Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordHeadAI.cs:41-56 — 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 (16–17 lines × 3) Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:590 — Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:590-606 | Content/QuestLogs/Styles/ForestQuestLogStyle.cs:500-515 | Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:505-521 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:590` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (15–17 lines × 2) · ×4
  • Duplicated block (15–17 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:76 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:76-90 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:83-99 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs` as WHOLE FILES: this scan already matched 66 separate duplicated blocks between them, totalling at least 737 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:78` calls `Sign` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:71` does not — after which the two agree again for 4 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 (15–17 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:604 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:604-620 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:784-798 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:604` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15–17 lines × 2) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/TwinsTetherArc.cs:190 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/TwinsTetherArc.cs:190-204 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeArcChainProj.cs:203-219 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/TwinsTetherArc.cs` and `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeArcChainProj.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 146 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/TwinsTetherArc.cs:190` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (15–17 lines × 2) Content/NPCs/BrutalNPCs/BrutalSkeletron/States/SkeletronBoneMaelstromState.cs:121 — Content/NPCs/BrutalNPCs/BrutalSkeletron/States/SkeletronBoneMaelstromState.cs:121-135 | Content/NPCs/BrutalNPCs/BrutalSkeletron/States/SkeletronPhaseTransitionState.cs:90-106 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalSkeletron/States/SkeletronBoneMaelstromState.cs:121` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (13 lines × 5) · ×4
  • Duplicated block (13 lines × 5) Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:110 — Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:110-122 | Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:147-159 | Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:184-196 | Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:261-273 | Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:482-494 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:110` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 5) Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:221 — Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:221-233 | Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:301-313 | Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:344-356 | Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:390-402 | Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:436-448 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:221` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 5) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:175 — Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:175-187 | Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:196-208 | Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs:265-277 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs:165-177 | Content/Scenarios/Kiame/KiameWakeResetRender.cs:161-173 — before extracting anything, compare `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs` and `Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:175` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:403 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:403-415 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:401-413 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:356-368 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:366-378 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:398-410 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs` as WHOLE FILES: this scan already matched 75 separate duplicated blocks between them, totalling at least 912 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:403` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11–14 lines × 2) · ×4
  • Duplicated block (11–14 lines × 2) Common/ShockRingDraw.cs:79 — Common/ShockRingDraw.cs:79-92 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteRingRender.cs:148-158 — before extracting anything, compare `Common/ShockRingDraw.cs` and `Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteRingRender.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Common/ShockRingDraw.cs:79` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (11–14 lines × 2) Content/LegendWeapon/HalibutLegend/FishSkills/FishBunny.cs:254 — Content/LegendWeapon/HalibutLegend/FishSkills/FishBunny.cs:254-267 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCat.cs:218-228 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishBunny.cs:254` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11–14 lines × 2) Content/LegendWeapon/HalibutLegend/FishSkills/FishPrincessVFX.cs:148 — Content/LegendWeapon/HalibutLegend/FishSkills/FishPrincessVFX.cs:148-158 | Content/LegendWeapon/HalibutLegend/FishSkills/FishPrismite.cs:388-401 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishPrincessVFX.cs:148` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11–14 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamSystem.cs:88 — Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamSystem.cs:88-101 | Content/Scenarios/Kiyume/KiyumeAmbienceFX.cs:36-46 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamSystem.cs:88` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamSystem.cs:84` calls `Rebuild` and `Content/Scenarios/Kiyume/KiyumeAmbienceFX.cs:35` 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.
D4 · Code Duplication · Duplicated block (12–13 lines × 4) · ×4
  • Duplicated block (12–13 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:726 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:726-738 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:837-849 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:939-951 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:728-739 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:939` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12–13 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:927 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:927-939 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1061-1072 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:967-978 | Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallProj.cs:795-807 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:927` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12–13 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:247 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:247-259 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:315-327 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:278-289 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:337-348 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:247` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (12–13 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:425 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:425-437 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:532-544 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:539-550 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:466-477 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:425` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (11–13 lines × 3) · ×4
  • Duplicated block (11–13 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:353 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:353-365 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:355-366 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:408-418 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs` as WHOLE FILES: this scan already matched 70 separate duplicated blocks between them, totalling at least 835 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:369` calls `PlaySound` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:368` does not — after which the two agree again for 3 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–13 lines × 3) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1849 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1849-1861 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1510-1520 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1714-1726 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1849` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (11–13 lines × 3) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerCoilCrushState.cs:312 — Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerCoilCrushState.cs:312-322 | Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerCoilLockState.cs:213-223 | Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerEncircleState.cs:130-142 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerCoilCrushState.cs:312` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11–13 lines × 3) Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemTelegraph.cs:71 — Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemTelegraph.cs:71-81 | Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraTelegraphLine.cs:63-75 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeTelegraphLine.cs:81-93 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemTelegraph.cs` and `Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraTelegraphLine.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemTelegraph.cs:71` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (9–11 lines × 4) · ×4
  • Duplicated block (9–11 lines × 4) Content/GameModes/BrutalMobs/Ambience/Ashreign/Projectiles/AshreignMagmaBeadProj.cs:51 — Content/GameModes/BrutalMobs/Ambience/Ashreign/Projectiles/AshreignMagmaBeadProj.cs:51-61 | Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgSnowShardProj.cs:48-56 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmIceShardProj.cs:43-51 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandPelletProj.cs:51-60 — before extracting anything, compare `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgSnowShardProj.cs` and `Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmIceShardProj.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/Ashreign/Projectiles/AshreignMagmaBeadProj.cs:51` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgSnowShardProj.cs:46` calls `CanDamage` and `Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmIceShardProj.cs:41` does not — after which the two agree again for 3 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–11 lines × 4) Content/Items/Ranged/BarrenBow.cs:470 — Content/Items/Ranged/BarrenBow.cs:470-480 | Content/Items/Ranged/NeutronBows/NeutronBow.cs:455-465 | Content/Items/Tools/EncyclopediaofOceanicKnowledge.cs:469-477 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumCircle.cs:349-358 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Ranged/BarrenBow.cs:470` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (9–11 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:544 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:544-554 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:411-420 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:491-499 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:430-440 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart. 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 (9–11 lines × 4) Content/LegendWeapon/OnikiriLegend/UI/OniLedgerSwapFX.cs:128 — Content/LegendWeapon/OnikiriLegend/UI/OniLedgerSwapFX.cs:128-136 | Content/LegendWeapon/OnikiriLegend/UI/OniMeiStandDraw.cs:36-46 | Content/LegendWeapon/OnikiriLegend/UI/OniSigilBoardDraw.cs:59-67 | Content/LegendWeapon/OnikiriLegend/UI/OniVigorInkDraw.cs:54-64 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/UI/OniLedgerSwapFX.cs` and `Content/LegendWeapon/OnikiriLegend/UI/OniVigorInkDraw.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 44 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.
D4 · Code Duplication · Duplicated block (8–10 lines × 9) · ×4
  • Duplicated block (8–10 lines × 9) Content/Items/Accessories/ArcaneThroneOfEternity.cs:329 — Content/Items/Accessories/ArcaneThroneOfEternity.cs:329-336 | Content/Items/Accessories/ArcaneThroneOfEternity.cs:460-467 | Content/LegendWeapon/HalibutLegend/DomainSkills/SeaDomain.cs:678-687 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutDomain.cs:320-327 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDetonationProj.cs:209-217 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberPixelDecomposeProj.cs:89-97 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberReformProj.cs:95-103 | Content/LegendWeapon/SHPCLegend/Modules/Frame/ResonanceFrameModule.cs:700-707 | Content/LegendWeapon/SHPCLegend/Modules/Power/PlasmaInjectorModule.cs:171-179 — there are 9 copies across 8 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 9 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/ArcaneThroneOfEternity.cs:329` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8–10 lines × 9) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainSky.cs:181 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainSky.cs:181-189 | Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamSky.cs:99-107 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainSky.cs:138-146 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspaceSky.cs:100-107 | Content/Scenarios/Hadalworld/Ambience/HadalSky.cs:145-152 | Content/Scenarios/Kiame/Backgrounds/KiameSky.cs:141-149 | Content/Scenarios/Kiame/Overlay/OniRainWorldSky.cs:144-153 | Content/Scenarios/Kiyume/Backgrounds/KiyumeSky.cs:118-125 | Content/Scenarios/OldNet/Backgrounds/OldNetSky.cs:140-147 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainSky.cs` and `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamSky.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (8–10 lines × 9) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:526 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:526-533 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:544-553 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:550-559 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:519-526 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:497-504 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:507-516 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:481-488 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:540-549 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:502-509 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:544` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8–10 lines × 9) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1069 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1069-1077 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:864-871 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1100-1107 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:889-896 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1405-1414 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:909-916 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:819-826 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:856-864 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:858-865 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1069` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (9–10 lines × 5) · ×4
  • Duplicated block (9–10 lines × 5) Content/Items/BloomArsenal.cs:194 — Content/Items/BloomArsenal.cs:194-202 | Content/LegendWeapon/HalibutLegend/FishSkills/FishotroningVFX.cs:171-180 | Content/NPCs/BloomsandSerpents/Projectiles/BssNeedleProj.cs:59-67 | Content/NPCs/BloomsandSerpents/Projectiles/BssSandGlob.cs:64-73 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Projectiles/BrutalBeeStinger.cs:79-88 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/BloomArsenal.cs:194` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (9–10 lines × 5) Content/Items/Melee/OniMacheteHands.cs:1333 — Content/Items/Melee/OniMacheteHands.cs:1333-1341 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCrimsonTiger.cs:784-792 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCursed.cs:448-456 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDemonicHell.cs:631-639 | Content/LegendWeapon/HalibutLegend/FishSkills/FishWyverntail.cs:380-389 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/OniMacheteHands.cs:1333` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (9–10 lines × 5) Content/Items/Modifys/RBloodButcherer.cs:931 — Content/Items/Modifys/RBloodButcherer.cs:931-940 | Content/LegendWeapon/HalibutLegend/FishSkills/FishIchornVFX.cs:103-112 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:163-171 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:154-163 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemMagmaBall.cs:268-277 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Modifys/RBloodButcherer.cs:931` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9–10 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1177 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1177-1186 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1319-1328 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:1061-1069 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:1129-1137 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1460-1469 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 598 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1177` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (4–9 lines × 3) · ×4
  • Duplicated block (4–9 lines × 3) Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:155 — Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:155-163 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmStrafeLaneProj.cs:141-144 | Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyRavenSwoopOmen.cs:157-165 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:155` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (4–9 lines × 3) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:228 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:228-236 | Content/Industrials/ElectricPowers/Launchers/PlayerLauncherUI.cs:209-212 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:224-232 — before extracting anything, compare `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs` and `Content/Industrials/ElectricPowers/Launchers/PlayerLauncherUI.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 144 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (4–9 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsBloodSpike.cs:184 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsBloodSpike.cs:184-192 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:831-834 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonVesselWhip.cs:393-401 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsBloodSpike.cs:184` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (4–9 lines × 3) Content/NPCs/SeaShrimp/Projectiles/SeaShrimpLeapVortex.cs:157 — Content/NPCs/SeaShrimp/Projectiles/SeaShrimpLeapVortex.cs:157-165 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpMiniVortex.cs:120-123 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpVortexWall.cs:158-166 — before extracting anything, compare `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpLeapVortex.cs` and `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpMiniVortex.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 99 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpLeapVortex.cs:157` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpLeapVortex.cs:165` calls `Vector2` and `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpMiniVortex.cs:123` 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.
D4 · Code Duplication · Duplicated block (8 lines × 8) · ×4
  • Duplicated block (8 lines × 8) Content/Cyberwares/Implementation/Sandevistans/SandevistanRender.cs:46 — Content/Cyberwares/Implementation/Sandevistans/SandevistanRender.cs:46-55 | Content/HackTimes/HackTimeRender.cs:85-94 | Content/HackTimes/HackTimeTileCyberPass.cs:105-113 | Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:54-61 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainRender.cs:47-58 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainRender.cs:173-183 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspaceRender.cs:127-135 | Content/Scenarios/OldNet/Renders/OldNetGradeRender.cs:45-53 — before extracting anything, compare `Content/Cyberwares/Implementation/Sandevistans/SandevistanRender.cs` and `Content/HackTimes/HackTimeRender.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Cyberwares/Implementation/Sandevistans/SandevistanRender.cs:46` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/HackTimes/HackTimeTileCyberPass.cs:101` calls `EnsureRT` and `Content/Cyberwares/Implementation/Sandevistans/SandevistanRender.cs:43` 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 × 8) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:54 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:54-61 | Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainRender.cs:67-75 | Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainRender.cs:219-227 | Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs:59-66 | Content/Scenarios/Kiame/Overlay/OniRainDescentRender.cs:76-83 | Content/Scenarios/Kiame/Overlay/OniRainWorldRender.cs:50-57 | Content/Scenarios/Kiame/Overlay/OniUmbrellaPuddleRender.cs:66-73 | Content/Scenarios/Kiame/Water/KiameWaterRender.cs:115-122 — there are 8 copies across 7 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 8 sites; resolving a subset leaves the remainder to drift apart. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainRender.cs:77` calls `SetSharedParams` and `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:64` 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 × 8) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1495 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1495-1503 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:1206-1213 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1524-1532 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1367-1375 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1430-1438 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1491-1499 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1615-1623 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1380-1388 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 8 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 8 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1495` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 8) Content/Scenarios/OldNet/NPCs/OldNetBlackICE.cs:223 — Content/Scenarios/OldNet/NPCs/OldNetBlackICE.cs:223-230 | Content/Scenarios/OldNet/NPCs/OldNetLurkerICE.cs:262-269 | Content/Scenarios/OldNet/NPCs/OldNetPatrolICE.cs:248-255 | Content/Scenarios/OldNet/NPCs/OldNetSweepEye.cs:195-202 | Content/Scenarios/OldNet/NPCs/OldNetTaggerICE.cs:259-266 | Content/Scenarios/OldNet/NPCs/OldNetTracerICE.cs:403-410 | Content/Scenarios/OldNet/NPCs/OldNetTurretICE.cs:144-151 | Content/Scenarios/OldNet/NPCs/OldNetWardenICE.cs:898-905 — 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 8 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/OldNet/NPCs/OldNetBlackICE.cs:223` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Scenarios/OldNet/NPCs/OldNetPatrolICE.cs:256` calls `Sin` and `Content/Scenarios/OldNet/NPCs/OldNetSweepEye.cs:204` 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.
D4 · Code Duplication · Duplicated block (5 lines × 10) · ×4
  • Duplicated block (5 lines × 10) Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:321 — Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:321-325 | Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzBeamProj.cs:270-274 | Content/Items/Magic/AriaofTheCosmoses/GammaRayBeam.cs:199-203 | Content/Items/Magic/CommandersStaff.cs:352-356 | Content/Items/Melee/Heartcarver.cs:510-514 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:276-280 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:225-229 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordRayRender.cs:43-47 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenGaleFieldProj.cs:116-120 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenPrismBeamProj.cs:285-289 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 10 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 10 times.
  • Duplicated block (5 lines × 10) Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamHound.cs:1017 — Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamHound.cs:1017-1021 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:838-842 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1262-1266 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonOrb.cs:145-149 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeBloodBee.cs:168-172 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1198-1202 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeStinger.cs:220-224 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronBloodSkull.cs:172-176 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1456-1460 | Content/Scenarios/Dungeonworld/NPCs/GaolFireBolt.cs:205-209 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 10 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 10 times.
  • Duplicated block (5 lines × 10) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:383 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:383-387 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:389-393 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:355-359 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:387-391 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:396-400 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:342-346 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:352-356 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:351-355 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:384-388 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:403-407 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:383` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 10) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailHead.cs:184 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailHead.cs:184-189 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipLash.cs:119-123 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:360-364 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:753-757 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1012-1016 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:361-365 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronBubble.cs:122-126 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:738-742 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:413-417 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:616-620 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 10 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 10 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailHead.cs:184` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:369` calls `PlaySound` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:368` 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.
D4 · Code Duplication · Duplicated block (3–6 lines × 3) · ×4
  • Duplicated block (3–6 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:686 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:686-691 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1034-1039 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs:262-264 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:686` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (3–6 lines × 3) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:322 — Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:322-327 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Rendering/EowMotionFX.cs:74-80 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowGeyserRakeState.cs:125-127 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:322` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (3–6 lines × 3) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:328 — Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:328-330 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Rendering/EowMotionFX.cs:75-81 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Rendering/EowMotionFX.cs:82-87 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:328` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Rendering/EowMotionFX.cs:82` calls `Vector2`, `NextFloat` and `Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:328` does not — after which the two agree again for 5 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 (3–6 lines × 3) Content/Narrative/Presentation/Skins/Brimstone/BrimstoneDialogueSkin.cs:42 — Content/Narrative/Presentation/Skins/Brimstone/BrimstoneDialogueSkin.cs:42-47 | Content/Narrative/Presentation/Skins/Sea/SeaDialogueSkin.cs:39-44 | Content/Narrative/Presentation/Skins/StarStream/StarStreamDialogueSkin.cs:42-44 — before extracting anything, compare `Content/Narrative/Presentation/Skins/Brimstone/BrimstoneDialogueSkin.cs` and `Content/Narrative/Presentation/Skins/Sea/SeaDialogueSkin.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Narrative/Presentation/Skins/Brimstone/BrimstoneDialogueSkin.cs:41` calls `Draw`, `Rectangle` and `Content/Narrative/Presentation/Skins/StarStream/StarStreamDialogueSkin.cs:42` does not — after which the two agree again for 4 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.
D4 · Code Duplication · Near-duplicate member family (6 members, 14 shared lines) · ×3
  • Near-duplicate member family (6 members, 14 shared lines) Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs:118 — Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs:118-164 | Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteDiveOmen.cs:102-159 | Content/GameModes/BrutalMobs/NightPack/Projectiles/NightDiveOmen.cs:128-187 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkChargeOmen.cs:139-184 | Content/GameModes/BrutalMobs/Sky/Projectiles/SkyGaleDiveOmen.cs:115-153 | Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornDiveLane.cs:114-170 — These 6 members are variants of one another: a block of 14 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 6 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 6 times.
  • Near-duplicate member family (6 members, 14 shared lines) Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:296 — Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:296-341 | Content/Items/Magic/AriaofTheCosmoses/GammaRayBeam.cs:171-225 | Content/Items/Magic/CommandersStaff.cs:328-371 | Content/Items/Melee/Heartcarver.cs:486-529 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:259-295 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:207-244 — These 6 members are variants of one another: a block of 14 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 6 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 6 times.
  • Near-duplicate member family (6 members, 14 shared lines) Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawWormProj.cs:555 — Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawWormProj.cs:555-597 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidPool.cs:92-119 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowBreachOmen.cs:71-111 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowGeyserProj.cs:180-205 | Content/NPCs/FestersandSerpents/Projectiles/FssGeyserColumn.cs:184-209 | Content/NPCs/FestersandSerpents/Projectiles/FssIchorPool.cs:210-239 — These 6 members are variants of one another: a block of 14 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 6 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 6 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 16 shared lines) · ×3
  • Near-duplicate member family (4 members, 16 shared lines) Content/Items/Summon/AzureDragonRage.cs:112 — Content/Items/Summon/AzureDragonRage.cs:112-147 | Content/Items/Summon/BleedingScourge.cs:95-131 | Content/Items/Summon/ElementWhip.cs:102-164 | Content/Items/Summon/GhostFireWhip.cs:108-157 — These 4 members are variants of one another: a block of 16 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 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 4 times.
  • Near-duplicate member family (4 members, 16 shared lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:530 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:530-589 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:385-452 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:379-419 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:457-510 — These 4 members are variants of one another: a block of 16 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 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 4 times.
  • Near-duplicate member family (4 members, 16 shared lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistIceShard.cs:57 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistIceShard.cs:57-114 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsHail.cs:53-104 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeStinger.cs:88-163 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronBloodSkull.cs:65-124 — These 4 members are variants of one another: a block of 16 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 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 4 times.
D4 · Code Duplication · Near-duplicate member pair (37 shared lines) · ×3
  • Near-duplicate member pair (37 shared lines) Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:442 — Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:442-506 | Content/Industrials/Modifys/ChargingStationUI.cs:294-353 — These two members are variants of one another: 37 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 (37 shared lines) Content/Items/Magic/AriaofTheCosmoses/AccretionDisk.cs:431 — Content/Items/Magic/AriaofTheCosmoses/AccretionDisk.cs:431-493 | Content/Items/Magic/AriaofTheCosmoses/FlattenedAccretionDisk.cs:172-239 — These two members are variants of one another: 37 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 (37 shared lines) Content/LegendWeapon/KikasaLegend/UI/KikasaHudTooltip.cs:38 — Content/LegendWeapon/KikasaLegend/UI/KikasaHudTooltip.cs:38-114 | Content/LegendWeapon/OnikiriLegend/UI/OniHudTooltipOverlay.cs:34-107 — These two members are variants of one another: 37 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 · Near-duplicate member pair (32 shared lines) · ×3
  • Near-duplicate member pair (32 shared lines) Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:520 — Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:520-571 | Content/Items/Modifys/RBloodButcherer.cs:459-514 — These two members are variants of one another: 32 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 (32 shared lines) Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemEyeRay.cs:128 — Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemEyeRay.cs:128-175 | Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemGrabRay.cs:129-176 — These two members are variants of one another: 32 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 (32 shared lines) Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordEyeLinkProj.cs:49 — Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordEyeLinkProj.cs:49-110 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordScanRayProj.cs:46-101 — These two members are variants of one another: 32 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 · Edited copy of a member (63 corresponding lines) · ×3
  • Edited copy of a member (63 corresponding lines) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:317 — Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:317-382 | Content/LegendWeapon/SHPCLegend/UI/SHPCModuleSelectPanel.cs:333-395 — These two members are one piece of code written twice and then edited apart: 63 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (63 corresponding lines) Content/MainMenus/Himayo/HimayoMenuButtons.cs:186 — Content/MainMenus/Himayo/HimayoMenuButtons.cs:186-248 | Content/MainMenus/Shenyo/ShenyoMenuButtons.cs:188-250 — These two members are one piece of code written twice and then edited apart: 63 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (63 corresponding lines) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:221 — Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:221-283 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowBurrowAmbushState.cs:182-245 — These two members are one piece of code written twice and then edited apart: 63 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (59 corresponding lines) · ×3
  • Edited copy of a member (59 corresponding lines) Content/NPCs/BrutalNPCs/BrutalSkeletron/Rendering/SkeletronScreenRender.cs:17 — Content/NPCs/BrutalNPCs/BrutalSkeletron/Rendering/SkeletronScreenRender.cs:17-79 | Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:2950-3008 — These two members are one piece of code written twice and then edited apart: 59 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (59 corresponding lines) Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerMotionFX.cs:31 — Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerMotionFX.cs:31-89 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Rendering/EocRenderHelper.cs:129-206 — These two members are one piece of code written twice and then edited apart: 59 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (59 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallRenderer.cs:80 — Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallRenderer.cs:80-140 | Content/Scenarios/Kiame/Overlay/OniRainWorldUmbrella.cs:387-445 — These two members are one piece of code written twice and then edited apart: 59 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (67 corresponding lines) · ×3
  • Edited copy of a member (67 corresponding lines) Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Preview.cs:17 — Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Preview.cs:17-83 | Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Preview.cs:17-91 — These two members are one piece of code written twice and then edited apart: 67 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (67 corresponding lines) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistArcaneNovaState.cs:35 — Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistArcaneNovaState.cs:35-102 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistCometVolleyState.cs:39-105 — These two members are one piece of code written twice and then edited apart: 67 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (67 corresponding lines) Content/Items/Melee/Arbiters/ArbiterManifestationSystem.cs:266 — Content/Items/Melee/Arbiters/ArbiterManifestationSystem.cs:266-332 | Content/Items/Melee/WeaverGrievanceses/WGManifestationSystem.cs:258-324 — These two members are one piece of code written twice and then edited apart: 67 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 45+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 45+ corresponding lines) Content/NPCs/SeaShrimp/Projectiles/SeaShrimpLeapVortex.cs:110 — Content/NPCs/SeaShrimp/Projectiles/SeaShrimpLeapVortex.cs:110-154 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpMiniVortex.cs:102-153 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpVortexWall.cs:110-155 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 45 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 45+ corresponding lines) Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGallerySiting.cs:25 — Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGallerySiting.cs:25-76 | Content/Scenarios/Dungeonworld/Gen/BossRooms/ProofingHallSiting.cs:23-67 | Content/Scenarios/Dungeonworld/Gen/GaolBossRoomSiting.cs:31-79 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 45 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 45+ corresponding lines) Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserMarkLine.cs:121 — Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserMarkLine.cs:121-168 | Content/GameModes/BrutalMobs/NightPack/Projectiles/NightDiveOmen.cs:79-126 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkChargeOmen.cs:93-137 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 45 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (52 corresponding lines) · ×3
  • Edited copy of a member (52 corresponding lines) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowApexFrenzyState.cs:341 — Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowApexFrenzyState.cs:341-392 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowSplitPincerState.cs:426-494 — These two members are one piece of code written twice and then edited apart: 52 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (52 corresponding lines) Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.cs:345 — Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.cs:345-396 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.cs:427-479 — These two members are one piece of code written twice and then edited apart: 52 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (52 corresponding lines) Content/Scenarios/Dungeonworld/UI/DungeonworldTransitionGate.cs:61 — Content/Scenarios/Dungeonworld/UI/DungeonworldTransitionGate.cs:61-112 | Content/Scenarios/Hadalworld/UI/HadalworldTransitionGate.cs:60-111 — These two members are one piece of code written twice and then edited apart: 52 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 34+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 34+ corresponding lines) Content/Items/Melee/SpearOfLonginuses/LonginusAssets.cs:199 — Content/Items/Melee/SpearOfLonginuses/LonginusAssets.cs:199-243 | Content/Items/Melee/SpearOfLonginuses/LonginusAssets.cs:249-284 | Content/Items/Melee/SpearOfLonginuses/LonginusAssets.cs:362-395 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 34 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 34+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:581 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:581-614 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:842-883 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:913-948 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 34 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 34+ corresponding lines) Content/Industrials/ElectricPowers/Crushers/CrusherTP.cs:360 — Content/Industrials/ElectricPowers/Crushers/CrusherTP.cs:360-396 | Content/Industrials/ElectricPowers/Incinerators/IncineratorTP.cs:248-284 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterTP.cs:565-598 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 34 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 29+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 29+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishEaterofPlanktonVFX.cs:174 — Content/LegendWeapon/HalibutLegend/FishSkills/FishEaterofPlanktonVFX.cs:174-207 | Content/LegendWeapon/HalibutLegend/FishSkills/FishHungerVFX.cs:238-270 | Content/LegendWeapon/HalibutLegend/FishSkills/FishRockParticles.cs:170-198 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 29 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 29+ corresponding lines) Content/Items/Magic/Elysiums/ElysiumHeld.cs:270 — Content/Items/Magic/Elysiums/ElysiumHeld.cs:270-298 | Content/Items/Magic/Elysiums/ElysiumHeld.cs:301-330 | Content/Items/Magic/Elysiums/UI/ElysiumRoseWindow.cs:210-243 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 29 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 29+ corresponding lines) Content/NPCs/BloomsandSerpents/BssHead.cs:636 — Content/NPCs/BloomsandSerpents/BssHead.cs:636-664 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/EowHeadAI.cs:503-536 | Content/NPCs/FestersandSerpents/FssHead.cs:577-605 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 29 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 31+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 31+ corresponding lines) Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyMaggotBurstCore.cs:53 — Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyMaggotBurstCore.cs:53-83 | Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomSporeBurstCore.cs:67-98 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesIceShatterCore.cs:54-85 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 31 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 31+ corresponding lines) Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdHammerConeOmen.cs:86 — Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdHammerConeOmen.cs:86-120 | Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomSporeMistTelegraph.cs:87-126 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandConeTelegraph.cs:111-141 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 31 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 31+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishBone.cs:26 — Content/LegendWeapon/HalibutLegend/FishSkills/FishBone.cs:26-61 | Content/LegendWeapon/HalibutLegend/FishSkills/FishHarpy.cs:24-59 | Content/LegendWeapon/HalibutLegend/FishSkills/FishObsidian.cs:27-57 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 31 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 28+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 28+ corresponding lines) Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberExecutionBoltProj.cs:385 — Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberExecutionBoltProj.cs:385-419 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberGlitchBoltProj.cs:129-156 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberRiftSlashProj.cs:131-161 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 28 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 28+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerFocusedBeamState.cs:49 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerFocusedBeamState.cs:49-76 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerLaserMatrixState.cs:58-88 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismFlameStormState.cs:57-87 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 28 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 28+ corresponding lines) Content/GameModes/BrutalMobs/FrostMoon/FrmMeleeNPC.cs:234 — Content/GameModes/BrutalMobs/FrostMoon/FrmMeleeNPC.cs:234-266 | Content/GameModes/BrutalMobs/FrostMoon/FrmSiegeNPC.cs:168-195 | Content/GameModes/BrutalMobs/Mushroom/MushroomBrutalNPC.cs:244-274 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 28 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 23+ corresponding lines) · ×3
  • Edited copies of one member (4 members, 23+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:751 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:751-776 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:825-849 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1000-1024 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:625-647 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 23+ corresponding lines) Content/Items/Modifys/RBloodButcherer.cs:900 — Content/Items/Modifys/RBloodButcherer.cs:900-923 | Content/LegendWeapon/HalibutLegend/FishSkills/FishIchorn.cs:261-283 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunBullet.cs:144-168 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenCrystalShard.cs:112-135 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 23+ corresponding lines) Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:540 — Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:540-564 | Content/GameModes/GodSmith/Weapons/Broadswords/GsMandibleBlade.cs:83-105 | Content/GameModes/GodSmith/Weapons/Shortswords/GsThrustHeldBase.cs:955-978 | Content/Items/Melee/Abyssrends/AbyssrendClampHeld.cs:456-478 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 20+ corresponding lines) · ×3
  • Edited copies of one member (5 members, 20+ corresponding lines) Content/LegendWeapon/HalibutLegend/DomainSkills/FishTeleport.cs:136 — Content/LegendWeapon/HalibutLegend/DomainSkills/FishTeleport.cs:136-156 | Content/LegendWeapon/HalibutLegend/DomainSkills/RestartFish.cs:170-190 | Content/LegendWeapon/HalibutLegend/DomainSkills/SeaDomain.cs:924-943 | Content/LegendWeapon/HalibutLegend/DomainSkills/Superposition.cs:132-167 | Content/LegendWeapon/HalibutLegend/DomainSkills/YourLevelIsTooLow.cs:737-758 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 20+ corresponding lines) Content/GameModes/BrutalMobs/Ambience/Fleshfen/FleshfenPRT_BloodDrop.cs:112 — Content/GameModes/BrutalMobs/Ambience/Fleshfen/FleshfenPRT_BloodDrop.cs:112-134 | Content/LegendWeapon/HalibutLegend/FishSkills/FishMudVFX.cs:103-123 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Rendering/QueenBeePRT.cs:63-82 | Content/PRTTypes/PRT_SewageGlob.cs:109-132 | Content/PRTTypes/PRT_TurnkeyDrip.cs:74-94 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 20+ corresponding lines) Content/Items/Melee/Arbiters/Arbiter.cs:24 — Content/Items/Melee/Arbiters/Arbiter.cs:24-46 | Content/Items/Melee/Cloudwalking.cs:25-46 | Content/Items/Melee/DragonsScaleGreatsword.cs:33-52 | Content/Items/Melee/EnergySword.cs:29-51 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:32-53 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 18+ corresponding lines) · ×3
  • Edited copies of one member (4 members, 18+ corresponding lines) Content/GameModes/BrutalMobs/EvilBiome/Projectiles/VileLanceProj.cs:48 — Content/GameModes/BrutalMobs/EvilBiome/Projectiles/VileLanceProj.cs:48-69 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionVolleyArrow.cs:42-64 | Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteMoltenGlob.cs:56-73 | Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornJavelinProj.cs:51-70 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 18+ corresponding lines) Content/Items/Magic/SandVortexOfTheDecayedSea.cs:20 — Content/Items/Magic/SandVortexOfTheDecayedSea.cs:20-38 | Content/Items/Ranged/HyperionBarrage.cs:71-88 | Content/Items/Ranged/RaiderGun.cs:86-104 | Content/Items/Ranged/Starships/Starship.cs:14-33 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 18+ corresponding lines) Content/Items/Melee/BudPiercers/BudPiercer.cs:23 — Content/Items/Melee/BudPiercers/BudPiercer.cs:23-40 | Content/Items/Melee/SandDagger.cs:20-37 | Content/Items/Melee/SeasonalKunai.cs:20-39 | Content/Items/Melee/WraithKunai.cs:24-43 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 24+ corresponding lines) · ×3
  • Edited copies of one member (4 members, 24+ corresponding lines) Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:102 — Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:102-125 | Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:139-162 | Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:176-199 | Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:213-236 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 24+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishDirt.cs:454 — Content/LegendWeapon/HalibutLegend/FishSkills/FishDirt.cs:454-482 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDirt.cs:484-510 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDirt.cs:512-536 | Content/LegendWeapon/HalibutLegend/FishSkills/FishHoney.cs:643-666 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 24+ corresponding lines) Content/QuestLogs/QLNodes/AdventurerQuests.cs:15 — Content/QuestLogs/QLNodes/AdventurerQuests.cs:15-41 | Content/QuestLogs/QLNodes/AdventurerQuests.cs:352-375 | Content/QuestLogs/QLNodes/AdventurerQuests.cs:506-529 | Content/QuestLogs/QLNodes/AdventurerQuests.cs:1020-1046 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 16+ corresponding lines) · ×3
  • Edited copies of one member (6 members, 16+ corresponding lines) Content/GameModes/GodSmith/Weapons/Broadswords/BroadswordSchemes.Wood.cs:44 — Content/GameModes/GodSmith/Weapons/Broadswords/BroadswordSchemes.Wood.cs:44-60 | Content/GameModes/GodSmith/Weapons/Broadswords/BroadswordSchemes.Wood.cs:441-457 | Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordScheme.cs:32-48 | Content/GameModes/GodSmith/Weapons/Broadswords/GsDD2SquireDemonSword.cs:46-65 | Content/GameModes/GodSmith/Weapons/Broadswords/GsZombieArm.cs:31-46 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsOdditiesComboScheme.cs:31-47 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 16+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuBao.cs:132 — Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuBao.cs:132-147 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuFei.cs:90-105 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuSha.cs:129-144 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuTing.cs:139-158 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuXia.cs:113-128 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuXiao.cs:76-93 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 16+ corresponding lines) Content/Scenarios/OldNet/NPCs/OldNetLurkerICE.cs:52 — Content/Scenarios/OldNet/NPCs/OldNetLurkerICE.cs:52-68 | Content/Scenarios/OldNet/NPCs/OldNetPatrolICE.cs:48-64 | Content/Scenarios/OldNet/NPCs/OldNetSweepEye.cs:48-63 | Content/Scenarios/OldNet/NPCs/OldNetTracerICE.cs:58-74 | Content/Scenarios/OldNet/NPCs/OldNetTurretICE.cs:37-52 | Content/Scenarios/OldNet/NPCs/OldNetWardenICE.cs:129-144 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 17+ corresponding lines) · ×3
  • Edited copies of one member (6 members, 17+ corresponding lines) Content/Scenarios/Dungeonworld/Gen/Layers/L1/L1Style.cs:172 — Content/Scenarios/Dungeonworld/Gen/Layers/L1/L1Style.cs:172-189 | Content/Scenarios/Dungeonworld/Gen/Layers/L1/L1Style.cs:192-211 | Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Palette.cs:178-195 | Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Palette.cs:202-218 | Content/Scenarios/Dungeonworld/Gen/Layers/L7/L7Style.cs:259-276 | Content/Scenarios/Dungeonworld/Gen/Layers/L7/L7Style.cs:322-341 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 17+ corresponding lines) Content/Items/Magic/BloomTomes/BloomTome.cs:25 — Content/Items/Magic/BloomTomes/BloomTome.cs:25-41 | Content/Items/Magic/Everdeeps/Everdeep.cs:21-38 | Content/Items/Magic/Eyetooths/Eyetooth.cs:28-45 | Content/Items/Magic/WheezingWyrms/WheezingWyrm.cs:19-36 | Content/Items/Ranged/SneezingWyrms/SneezingWyrm.cs:20-37 | Content/Items/Ranged/TiroFinales/TiroFinale.cs:21-39 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 17+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalDeerclops/DeerclopsPerformancePlayer.cs:28 — Content/NPCs/BrutalNPCs/BrutalDeerclops/DeerclopsPerformancePlayer.cs:28-45 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/FishronDeathCutscene.cs:40-57 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/EmpressDeathCutscene.cs:59-76 | Content/NPCs/BrutalNPCs/BrutalGolem/GolemDeathPerformancePlayer.cs:13-30 | Content/NPCs/BrutalNPCs/BrutalMoonLord/MLordPerformancePlayer.cs:12-28 | Content/NPCs/BrutalNPCs/BrutalSkeletron/SkeletronPerformancePlayer.cs:13-30 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 11+ corresponding lines) · ×3
  • Edited copies of one member (7 members, 11+ corresponding lines) Content/Scenarios/OldNet/NPCs/OldNetLurkerICE.cs:247 — Content/Scenarios/OldNet/NPCs/OldNetLurkerICE.cs:247-257 | Content/Scenarios/OldNet/NPCs/OldNetPatrolICE.cs:234-244 | Content/Scenarios/OldNet/NPCs/OldNetSweepEye.cs:181-191 | Content/Scenarios/OldNet/NPCs/OldNetTaggerICE.cs:234-244 | Content/Scenarios/OldNet/NPCs/OldNetTracerICE.cs:388-398 | Content/Scenarios/OldNet/NPCs/OldNetTurretICE.cs:130-140 | Content/Scenarios/OldNet/NPCs/OldNetWardenICE.cs:874-886 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
  • Edited copies of one member (7 members, 11+ corresponding lines) Content/LegendWeapon/OnikiriLegend/OniDismembers/OniPlayerDismember.cs:353 — Content/LegendWeapon/OnikiriLegend/OniDismembers/OniPlayerDismember.cs:353-366 | Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Core/BrainMindSeizePlayer.cs:57-69 | Content/NPCs/BrutalNPCs/BrutalDeerclops/DeerclopsGrabPlayer.cs:95-107 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/EmpressGrabCutscene.cs:101-112 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/EocGrabPerformancePlayer.cs:180-190 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Core/KingSlimeEngulfPlayer.cs:174-185 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/QueenSlimePerformancePlayer.cs:207-218 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
  • Edited copies of one member (7 members, 11+ corresponding lines) Content/NPCs/ScrapCommanders/Projectiles/ScrapSweepBeam.cs:52 — Content/NPCs/ScrapCommanders/Projectiles/ScrapSweepBeam.cs:52-62 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpLeapVortex.cs:49-59 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpVortexWall.cs:46-58 | Content/Scenarios/Dungeonworld/Machines/L6MachineStrike.cs:47-57 | Content/Scenarios/Dungeonworld/NPCs/OverseerDartBolt.cs:31-44 | Content/Scenarios/Dungeonworld/NPCs/UndrownedDepthMine.cs:36-46 | Content/Scenarios/Dungeonworld/NPCs/UndrownedTideWave.cs:43-53 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 6+ corresponding lines) · ×3
  • Edited copies of one member (5 members, 6+ corresponding lines) Content/Scenarios/Himayo/Gifts/HimayoDestroyerGift.cs:26 — Content/Scenarios/Himayo/Gifts/HimayoDestroyerGift.cs:26-31 | Content/Scenarios/Himayo/Gifts/HimayoMoonLordGift.cs:26-31 | Content/Scenarios/Himayo/Gifts/HimayoProvidenceGift.cs:26-31 | Content/Scenarios/Himayo/Gifts/HimayoSlimeGodGift.cs:26-31 | Content/Scenarios/Himayo/Gifts/HimayoWallOfFleshGift.cs:26-31 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 6+ corresponding lines) Content/Items/Accessories/BrutalRelics/Deerclops/WhiteoutBurstProj.cs:79 — Content/Items/Accessories/BrutalRelics/Deerclops/WhiteoutBurstProj.cs:79-84 | Content/Items/Magic/Elysiums/Disciples/Matthew.cs:101-108 | Content/Items/Magic/Elysiums/ElysiumThunder.cs:87-94 | Content/Items/Magic/Elysiums/Revelations/CelestialMeteor.cs:106-116 | Content/Items/Magic/Elysiums/Revelations/RevelationSealJudgment.cs:196-204 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 6+ corresponding lines) Content/Items/Accessories/ArcaneThroneOfEternity.cs:27 — Content/Items/Accessories/ArcaneThroneOfEternity.cs:27-33 | Content/Items/Accessories/GodslayerScabbard.cs:23-29 | Content/Items/Accessories/JusticeUnveileds/JusticeUnveiled.cs:19-24 | Content/Items/Accessories/Proverbs.cs:27-33 | Content/Items/Accessories/SimpleMuzzleBrake.cs:12-17 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 15+ corresponding lines) · ×3
  • Edited copies of one member (8 members, 15+ corresponding lines) Content/Cyberwares/Implementation/CstmVisualEyes/CstmVisualEye.cs:33 — Content/Cyberwares/Implementation/CstmVisualEyes/CstmVisualEye.cs:33-47 | Content/Cyberwares/Implementation/OmniElectricFoots/OmniElectricFoot.cs:62-76 | Content/Cyberwares/Implementation/PlowSteelClampArms/PlowSteelClampArm.cs:56-70 | Content/Cyberwares/Implementation/PrimePlasamas/PrimePlasama.cs:33-47 | Content/Cyberwares/Implementation/SCCA32CRPs/SCCA32CRP.cs:49-63 | Content/Cyberwares/Implementation/Sandevistans/Sandevistan.cs:52-70 | Content/Cyberwares/Implementation/SelfHackCrystals/SelfHackCrystal.cs:42-56 | Content/Cyberwares/Implementation/SelfHealingSkelents/SelfHealingSkelent.cs:36-50 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
  • Edited copies of one member (8 members, 15+ corresponding lines) Content/GameModes/GodSmith/Armors/Reset/GsResetArmorScheme.cs:158 — Content/GameModes/GodSmith/Armors/Reset/GsResetArmorScheme.cs:158-172 | Content/GameModes/GodSmith/Weapons/Bows/GsHuntMarkNPC.cs:57-71 | Content/GameModes/GodSmith/Weapons/Broadswords/GsTheHorsemansBlade.cs:285-299 | Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsStardustCellMoteProj.cs:68-82 | Content/GameModes/GodSmith/Weapons/SummonMinions/Schemes/GsPirateStaff.cs:86-100 | Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipThornProj.cs:105-119 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMirrorPhantom.cs:172-186 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteRing.cs:303-317 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
  • Edited copies of one member (8 members, 15+ corresponding lines) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:107 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:107-121 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs:120-134 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs:115-129 | Content/Industrials/ElectricPowers/Launchers/PlayerLauncherUI.cs:108-122 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:98-112 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconUI.cs:100-114 | Content/Industrials/ElectricPowers/Sensors/SensorUI.cs:72-86 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:109-123 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 4+ corresponding lines) · ×3
  • Edited copies of one member (6 members, 4+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainPlayer.cs:1681 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainPlayer.cs:1681-1684 | Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamDirector.cs:225-228 | Content/MainMenus/Overs/AckTheme.cs:57-60 | Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:348-351 | Content/Scenarios/Kiame/Overlay/OniRainExitTransition.cs:306-309 | Content/Scenarios/Kiame/Overlay/OniRainWorldTransition.cs:456-459 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 4+ corresponding lines) Content/Scenarios/Dungeonworld/DungeonworldGuard.cs:37 — Content/Scenarios/Dungeonworld/DungeonworldGuard.cs:37-40 | Content/Scenarios/Hadalworld/HadalworldGuard.cs:37-40 | Content/Scenarios/Kiame/KiameGuard.cs:37-40 | Content/Scenarios/Kiyume/KiyumeGuard.cs:37-40 | Content/Scenarios/OldNet/OldNetGuard.cs:37-40 | Content/Scenarios/Shepel/CybCourses/CybCourseWorldGuard.cs:45-48 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 4+ corresponding lines) Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:257 — Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:257-260 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT2.cs:370-373 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsScourgeoftheCorruptor.cs:222-225 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsSolarEruption.cs:342-345 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsVampireKnives.cs:318-321 | Content/GameModes/GodSmith/Weapons/Shortswords/GsThrustHeldBase.cs:841-844 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 4+ corresponding lines) · ×3
  • Edited copies of one member (5 members, 4+ corresponding lines) Content/HackTimes/CircuitNodes/SentryTurretActor.cs:532 — Content/HackTimes/CircuitNodes/SentryTurretActor.cs:532-535 | Content/HackTimes/CircuitNodes/SignalTowerActor.cs:343-346 | Content/HackTimes/Scannables/ContainerScannable.cs:193-198 | Content/HackTimes/Scannables/SelfRigScannable.cs:181-187 | Content/HackTimes/Scannables/WorldScannable.cs:86-91 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 4+ corresponding lines) Content/Narrative/Presentation/Skins/Brimstone/BrimstonePopupSkin.cs:32 — Content/Narrative/Presentation/Skins/Brimstone/BrimstonePopupSkin.cs:32-38 | Content/Narrative/Presentation/Skins/Kikasa/KikasaPopupSkin.cs:19-22 | Content/Narrative/Presentation/Skins/Onikiri/OnikiriPopupSkin.cs:18-21 | Content/Narrative/Presentation/Skins/Sea/SeaPopupSkin.cs:17-20 | Content/Narrative/Presentation/Skins/Tzeentch/TzeentchPopupSkin.cs:18-21 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 4+ corresponding lines) Content/Items/Accessories/BrutalRelics/Twins/TwinPupilOrbiter.cs:363 — Content/Items/Accessories/BrutalRelics/Twins/TwinPupilOrbiter.cs:363-366 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetHourglass.cs:451-454 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1437-1440 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiSenjuArm.cs:295-298 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Rendering/SkeletronRenderHelper.cs:70-73 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (33 lines × 2) · ×3
  • Duplicated block (33 lines × 2) Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs:320 — Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs:320-352 | Content/Scenarios/Shenyo/ShenyoPortraitRainRenderer.cs:314-346 — before extracting anything, compare `Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs` and `Content/Scenarios/Shenyo/ShenyoPortraitRainRenderer.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 211 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs:320` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (33 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:726 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:726-758 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:662-694 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs` as WHOLE FILES: this scan already matched 68 separate duplicated blocks between them, totalling at least 933 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:726` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (33 lines × 2) Content/LegendWeapon/KikasaLegend/UI/ServantWheel/KikasaServantWheelController.cs:167 — Content/LegendWeapon/KikasaLegend/UI/ServantWheel/KikasaServantWheelController.cs:167-199 | Content/LegendWeapon/SHPCLegend/UI/DomainWheel/SHPCDomainWheelController.cs:144-176 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/UI/ServantWheel/KikasaServantWheelController.cs` and `Content/LegendWeapon/SHPCLegend/UI/DomainWheel/SHPCDomainWheelController.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 92 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/UI/ServantWheel/KikasaServantWheelController.cs:167` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (29 lines × 3) · ×3
  • Duplicated block (29 lines × 3) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:738 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:738-766 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:541-569 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:691-719 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:738` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (29 lines × 3) Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:508 — Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:508-536 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:774-802 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:808-836 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:508` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (29 lines × 3) Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:481 — Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:481-509 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:515-543 | Content/Industrials/ElectricPowers/Recyclers/RecyclerUI.cs:442-470 — before extracting anything, compare `Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs` and `Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 303 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:481` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (31 lines × 2) · ×3
  • Duplicated block (31 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamGroundField.cs:94 — Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamGroundField.cs:94-124 | Content/Scenarios/Kiyume/Fog/KiyumeGroundField.cs:109-139 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamGroundField.cs` and `Content/Scenarios/Kiyume/Fog/KiyumeGroundField.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamGroundField.cs:94` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (31 lines × 2) Content/NPCs/TBUGs/TBUG.cs:302 — Content/NPCs/TBUGs/TBUG.cs:302-332 | Content/NPCs/Victors/Victor.cs:131-161 — before extracting anything, compare `Content/NPCs/TBUGs/TBUG.cs` and `Content/NPCs/Victors/Victor.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 117 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (31 lines × 2) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismDashingState.cs:58 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismDashingState.cs:58-88 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismPhase2DashingState.cs:66-96 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismDashingState.cs` and `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismPhase2DashingState.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 45 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismDashingState.cs:58` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (25–26 lines × 2) · ×3
  • Duplicated block (25–26 lines × 2) Content/LegendWeapon/SHPCLegend/Modules/Optic/PrecisionOpticModule.cs:228 — Content/LegendWeapon/SHPCLegend/Modules/Optic/PrecisionOpticModule.cs:228-253 | Content/LegendWeapon/SHPCLegend/Modules/Optic/SniperOpticModule.cs:608-632 — before extracting anything, compare `Content/LegendWeapon/SHPCLegend/Modules/Optic/PrecisionOpticModule.cs` and `Content/LegendWeapon/SHPCLegend/Modules/Optic/SniperOpticModule.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 131 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/Modules/Optic/PrecisionOpticModule.cs:228` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/SHPCLegend/Modules/Optic/SniperOpticModule.cs:607` calls `SetValue` and `Content/LegendWeapon/SHPCLegend/Modules/Optic/PrecisionOpticModule.cs:228` does not — after which the two agree again for 3 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 (25–26 lines × 2) Content/NPCs/BloomsandSerpents/BssHead.cs:757 — Content/NPCs/BloomsandSerpents/BssHead.cs:757-782 | Content/NPCs/FestersandSerpents/FssHead.cs:747-771 — before extracting anything, compare `Content/NPCs/BloomsandSerpents/BssHead.cs` and `Content/NPCs/FestersandSerpents/FssHead.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 321 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BloomsandSerpents/BssHead.cs:757` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (25–26 lines × 2) Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerStrikeTelegraph.cs:93 — Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerStrikeTelegraph.cs:93-117 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Projectiles/QueenBeeTelegraphLine.cs:87-112 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerStrikeTelegraph.cs` and `Content/NPCs/BrutalNPCs/BrutalQueenBee/Projectiles/QueenBeeTelegraphLine.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 128 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (24–25 lines × 2) · ×3
  • Duplicated block (24–25 lines × 2) Content/Industrials/Generator/WindGriven/WGGMK2Wilderness.cs:99 — Content/Industrials/Generator/WindGriven/WGGMK2Wilderness.cs:99-123 | Content/Industrials/Generator/WindGriven/WGGWilderness.cs:97-120 — before extracting anything, compare `Content/Industrials/Generator/WindGriven/WGGMK2Wilderness.cs` and `Content/Industrials/Generator/WindGriven/WGGWilderness.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 69 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/Generator/WindGriven/WGGMK2Wilderness.cs:99` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (24–25 lines × 2) Content/PRTTypes/PRT_KikasaBloodSpray.cs:141 — Content/PRTTypes/PRT_KikasaBloodSpray.cs:141-165 | Content/PRTTypes/PRT_KikasaInkSpray.cs:158-181 — before extracting anything, compare `Content/PRTTypes/PRT_KikasaBloodSpray.cs` and `Content/PRTTypes/PRT_KikasaInkSpray.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 70 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/PRTTypes/PRT_KikasaBloodSpray.cs:141` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (24–25 lines × 2) Content/Structures/DatIO/JunkmanBase.cs:86 — Content/Structures/DatIO/JunkmanBase.cs:86-109 | Content/Structures/DatIO/JunkmanBase.cs:110-134 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Structures/DatIO/JunkmanBase.cs:110` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (23–24 lines × 2) · ×3
  • Duplicated block (23–24 lines × 2) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/TwinsTetherArc.cs:87 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/TwinsTetherArc.cs:87-110 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeArcChainProj.cs:97-119 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/TwinsTetherArc.cs` and `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeArcChainProj.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 146 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/TwinsTetherArc.cs:87` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (23–24 lines × 2) Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordAnnihilationRayProj.cs:213 — Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordAnnihilationRayProj.cs:213-235 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordArcRayProj.cs:85-108 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordAnnihilationRayProj.cs` and `Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordArcRayProj.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 64 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordAnnihilationRayProj.cs:213` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (23–24 lines × 2) Content/Narrative/Common/BaseRecipeDisplayUI.cs:381 — Content/Narrative/Common/BaseRecipeDisplayUI.cs:381-403 | Content/Narrative/Common/BaseRecipeDisplayUI.cs:445-468 — 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. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Narrative/Common/BaseRecipeDisplayUI.cs:468` calls `Sin` and `Content/Narrative/Common/BaseRecipeDisplayUI.cs:403` does not — after which the two agree again for 4 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.
D4 · Code Duplication · Duplicated block (21–23 lines × 2) · ×3
  • Duplicated block (21–23 lines × 2) Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs:178 — Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs:178-198 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronSharkTornadoProj.cs:292-314 — before extracting anything, compare `Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs` and `Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronSharkTornadoProj.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 181 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs:178` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21–23 lines × 2) Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:336 — Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:336-356 | Content/LegendWeapon/OnikiriLegend/OniZanshinSlashs/OniZanshinSlash.cs:423-445 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:336` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21–23 lines × 2) Content/Scenarios/Hadalworld/Ambience/HadalSky.cs:75 — Content/Scenarios/Hadalworld/Ambience/HadalSky.cs:75-97 | Content/Scenarios/OldNet/Backgrounds/OldNetSky.cs:75-95 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Hadalworld/Ambience/HadalSky.cs:75` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (20–23 lines × 2) · ×3
  • Duplicated block (20–23 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:755 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:755-777 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:800-819 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:755` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20–23 lines × 2) Content/NPCs/BloomsandSerpents/BssHead.cs:558 — Content/NPCs/BloomsandSerpents/BssHead.cs:558-580 | Content/NPCs/FestersandSerpents/FssHead.cs:504-523 — before extracting anything, compare `Content/NPCs/BloomsandSerpents/BssHead.cs` and `Content/NPCs/FestersandSerpents/FssHead.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 321 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BloomsandSerpents/BssHead.cs:558` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20–23 lines × 2) Content/NPCs/BrutalNPCs/BrutalGolem/States/GolemHeadDetachState.cs:30 — Content/NPCs/BrutalNPCs/BrutalGolem/States/GolemHeadDetachState.cs:30-49 | Content/NPCs/BrutalNPCs/BrutalGolem/States/GolemSolarOverdriveState.cs:32-54 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalGolem/States/GolemHeadDetachState.cs:30` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (21–22 lines × 3) · ×3
  • Duplicated block (21–22 lines × 3) Content/GameModes/GodSmith/Weapons/Flamethrowers/FlamethrowersShared.cs:100 — Content/GameModes/GodSmith/Weapons/Flamethrowers/FlamethrowersShared.cs:100-121 | Content/GameModes/GodSmith/Weapons/Guns/GsMinishark.cs:218-238 | Content/GameModes/GodSmith/Weapons/Guns/GsPhoenixBlaster.cs:194-214 — before extracting anything, compare `Content/GameModes/GodSmith/Weapons/Guns/GsMinishark.cs` and `Content/GameModes/GodSmith/Weapons/Guns/GsPhoenixBlaster.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 74 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/Flamethrowers/FlamethrowersShared.cs:100` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/GodSmith/Weapons/Flamethrowers/FlamethrowersShared.cs:99` calls `Max` and `Content/GameModes/GodSmith/Weapons/Guns/GsPhoenixBlaster.cs:193` does not — after which the two agree again for 4 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 (21–22 lines × 3) Content/NPCs/BrutalNPCs/BrutalDestroyer/DestroyerHeadAI.cs:279 — Content/NPCs/BrutalNPCs/BrutalDestroyer/DestroyerHeadAI.cs:279-300 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/DukeFishronAI.cs:296-317 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/EowHeadAI.cs:504-524 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/NPCs/BrutalNPCs/BrutalDukeFishron/DukeFishronAI.cs:318` calls `SpawnMist` and `Content/NPCs/BrutalNPCs/BrutalDestroyer/DestroyerHeadAI.cs:301` does not — after which the two agree again for 3 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 (21–22 lines × 3) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/PincerBindTether.cs:92 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/PincerBindTether.cs:92-112 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/TwinsTetherArc.cs:76-97 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeArcChainProj.cs:86-107 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/PincerBindTether.cs:92` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (20–22 lines × 2) · ×3
  • Duplicated block (20–22 lines × 2) Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs:70 — Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs:70-91 | Content/LegendWeapon/SHPCLegend/UI/DomainWheel/SHPCDomainWheelUI.cs:92-111 — before extracting anything, compare `Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs` and `Content/LegendWeapon/SHPCLegend/UI/DomainWheel/SHPCDomainWheelUI.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs:70` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (20–22 lines × 2) Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:294 — Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:294-313 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpWaterBolt.cs:80-101 — before extracting anything, compare `Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs` and `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpWaterBolt.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 116 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:290` calls `OnHitNPC`, `AddBuff` and `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpWaterBolt.cs:77` 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 (20–22 lines × 2) Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:335 — Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:335-354 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpWaterBolt.cs:124-145 — before extracting anything, compare `Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs` and `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpWaterBolt.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 116 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (15 lines × 4) · ×3
  • Duplicated block (15 lines × 4) Content/Items/Melee/DestroyersBlade.cs:262 — Content/Items/Melee/DestroyersBlade.cs:262-276 | Content/Items/Melee/DragonsScaleGreatsword.cs:275-289 | Content/Items/Melee/EnergySword.cs:286-300 | Content/Items/Melee/RebelBlade.cs:307-321 — before extracting anything, compare `Content/Items/Melee/DestroyersBlade.cs` and `Content/Items/Melee/DragonsScaleGreatsword.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 419 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DestroyersBlade.cs:262` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:90 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:90-104 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:90-104 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:101-115 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:88-102 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs` as WHOLE FILES: this scan already matched 75 separate duplicated blocks between them, totalling at least 912 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (15 lines × 4) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/BrainOfCthulhuAI.cs:315 — Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/BrainOfCthulhuAI.cs:315-330 | Content/NPCs/BrutalNPCs/BrutalDestroyer/DestroyerHeadAI.cs:279-294 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/DukeFishronAI.cs:296-311 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/EowHeadAI.cs:504-518 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/BrainOfCthulhuAI.cs:315` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (16 lines × 4) · ×3
  • Duplicated block (16 lines × 4) Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:298 — Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:298-313 | Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:341-356 | Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:387-402 | Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:433-448 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:298` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 4) Content/Items/Melee/DestroyersBlade.cs:163 — Content/Items/Melee/DestroyersBlade.cs:163-178 | Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:164-179 | Content/Items/Melee/DragonsScaleGreatsword.cs:179-194 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:198-213 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DestroyersBlade.cs:163` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 4) Content/Items/Melee/OniMacheteHands.cs:1338 — Content/Items/Melee/OniMacheteHands.cs:1338-1353 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCrimsonTiger.cs:789-804 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCursed.cs:453-468 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDemonicHell.cs:636-651 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/OniMacheteHands.cs:1338` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (17–19 lines × 2) · ×3
  • Duplicated block (17–19 lines × 2) Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs:395 — Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs:395-413 | Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs:678-694 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs:395` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17–19 lines × 2) Content/NPCs/BrutalNPCs/BrutalKingSlime/Rendering/KingSlimeEngulfRender.cs:62 — Content/NPCs/BrutalNPCs/BrutalKingSlime/Rendering/KingSlimeEngulfRender.cs:62-78 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Rendering/KingSlimeRenderer.cs:71-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 both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalKingSlime/Rendering/KingSlimeEngulfRender.cs:62` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (17–19 lines × 2) Content/Scenarios/Kiame/Backgrounds/KiameSky.cs:131 — Content/Scenarios/Kiame/Backgrounds/KiameSky.cs:131-147 | Content/Scenarios/Kiame/Overlay/OniRainWorldSky.cs:133-151 — before extracting anything, compare `Content/Scenarios/Kiame/Backgrounds/KiameSky.cs` and `Content/Scenarios/Kiame/Overlay/OniRainWorldSky.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Kiame/Backgrounds/KiameSky.cs:131` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Scenarios/Kiame/Overlay/OniRainWorldSky.cs:132` calls `SetValue` and `Content/Scenarios/Kiame/Backgrounds/KiameSky.cs:130` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (17–18 lines × 2) · ×3
  • Duplicated block (17–18 lines × 2) Content/GameModes/BrutalMobs/Ambience/Sporeshine/SporeshineAmbience.cs:259 — Content/GameModes/BrutalMobs/Ambience/Sporeshine/SporeshineAmbience.cs:259-275 | Content/GameModes/BrutalMobs/Ambience/Sporeshine/SporeshinePlayer.cs:173-190 — 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 (17–18 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:919 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:919-936 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1053-1069 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:919` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17–18 lines × 2) Content/Scenarios/Kiyume/NPCs/KiyumeHound.cs:1017 — Content/Scenarios/Kiyume/NPCs/KiyumeHound.cs:1017-1034 | Content/Scenarios/Kiyume/NPCs/KiyumeWhiteHound.cs:443-459 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Kiyume/NPCs/KiyumeHound.cs:1017` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (14–18 lines × 2) · ×3
  • Duplicated block (14–18 lines × 2) Content/Industrials/ElectricPowers/MiningMachines/MiningMachineUI.cs:225 — Content/Industrials/ElectricPowers/MiningMachines/MiningMachineUI.cs:225-242 | Content/Industrials/ElectricPowers/Turrets/TurretControlUI.cs:153-166 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/MiningMachines/MiningMachineUI.cs:225` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (14–18 lines × 2) Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainRender.cs:47 — Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainRender.cs:47-64 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainRender.cs:173-186 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainRender.cs:47` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (14–18 lines × 2) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingUI.cs:315 — Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingUI.cs:315-328 | Content/LegendWeapon/SHPCLegend/UI/SHPCModPanel.cs:545-562 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingUI.cs:315` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (15 lines × 5) · ×3
  • Duplicated block (15 lines × 5) Content/Items/Melee/DestroyersBlade.cs:354 — Content/Items/Melee/DestroyersBlade.cs:354-368 | Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:480-494 | Content/Items/Melee/DragonsScaleGreatsword.cs:367-381 | Content/Items/Melee/EnergySword.cs:382-396 | Content/Items/Melee/RebelBlade.cs:404-418 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DestroyersBlade.cs:354` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 5) Content/Items/Ranged/Dicoria.cs:25 — Content/Items/Ranged/Dicoria.cs:25-39 | Content/Items/Ranged/HyperionBarrage.cs:27-41 | Content/Items/Ranged/HyperionBarrage.cs:71-85 | Content/Items/Ranged/RaiderGun.cs:22-36 | Content/Items/Ranged/RaiderGun.cs:86-100 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Ranged/Dicoria.cs:25` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Ranged/Dicoria.cs:42` calls `CWR` and `Content/Items/Ranged/HyperionBarrage.cs:88` 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 (15 lines × 5) Content/Scenarios/Dungeonworld/DungeonworldGuard.cs:53 — Content/Scenarios/Dungeonworld/DungeonworldGuard.cs:53-67 | Content/Scenarios/Hadalworld/HadalworldGuard.cs:53-67 | Content/Scenarios/Kiame/KiameGuard.cs:53-67 | Content/Scenarios/Kiyume/KiyumeGuard.cs:53-67 | Content/Scenarios/OldNet/OldNetGuard.cs:53-67 — before extracting anything, compare `Content/Scenarios/Dungeonworld/DungeonworldGuard.cs` and `Content/Scenarios/Hadalworld/HadalworldGuard.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (13–15 lines × 3) · ×3
  • Duplicated block (13–15 lines × 3) Content/Industrials/ElectricPowers/Collectors/CollectorUI.cs:545 — Content/Industrials/ElectricPowers/Collectors/CollectorUI.cs:545-557 | Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:488-502 | Content/Industrials/Modifys/ChargingStationUI.cs:332-345 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (13–15 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:182 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:182-195 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeBloodBee.cs:51-63 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeStinger.cs:60-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (13–15 lines × 3) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerDespawnState.cs:92 — Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerDespawnState.cs:92-106 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsDeathState.cs:68-82 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/PrimeDeathState.cs:124-136 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerDespawnState.cs` and `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsDeathState.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 111 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerDespawnState.cs:92` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `context` to `DestroyerStateContext` in one and `TwinsStateContext` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (12 lines × 7) · ×3
  • Duplicated block (12 lines × 7) Content/UIs/UIEffect/BrimstoneShaderPanel.cs:34 — Content/UIs/UIEffect/BrimstoneShaderPanel.cs:34-45 | Content/UIs/UIEffect/CyberShaderPanel.cs:32-43 | Content/UIs/UIEffect/KikasaShaderPanel.cs:41-52 | Content/UIs/UIEffect/OniShaderPanel.cs:40-51 | Content/UIs/UIEffect/SeaShaderPanel.cs:34-45 | Content/UIs/UIEffect/SulfseaShaderPanel.cs:34-45 | Content/UIs/UIEffect/TzeentchShaderPanel.cs:34-45 — before extracting anything, compare `Content/UIs/UIEffect/BrimstoneShaderPanel.cs` and `Content/UIs/UIEffect/SeaShaderPanel.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/UIs/UIEffect/BrimstoneShaderPanel.cs:34` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/UIs/UIEffect/BrimstoneShaderPanel.cs:32` calls `SetValue` and `Content/UIs/UIEffect/CyberShaderPanel.cs:30` does not — after which the two agree again for 4 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 (12 lines × 7) Content/GameModes/GodSmith/Prefixes/Accessory/GodSmithMenaceEndow.cs:84 — Content/GameModes/GodSmith/Prefixes/Accessory/GodSmithMenaceEndow.cs:84-95 | Content/GameModes/GodSmith/Prefixes/Magic/GodSmithOverloadEndow.cs:72-83 | Content/GameModes/GodSmith/Prefixes/Offense/GodSmithCritMarkEndow.cs:93-104 | Content/GameModes/GodSmith/Prefixes/Offense/GodSmithExecutionEndow.cs:75-86 | Content/GameModes/GodSmith/Prefixes/Offense/GodSmithShockwaveEndow.cs:80-91 | Content/GameModes/GodSmith/Prefixes/Rescue/GodSmithDesperationEndow.cs:84-95 | Content/GameModes/GodSmith/Prefixes/Speed/GodSmithComboEndow.cs:104-115 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/GameModes/GodSmith/Prefixes/Accessory/GodSmithMenaceEndow.cs:97` calls `OnHitNPC`, `SuppressNow` and `Content/GameModes/GodSmith/Prefixes/Magic/GodSmithOverloadEndow.cs:85` does not — after which the two agree again for 3 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 (12 lines × 7) Content/LegendWeapon/HalibutLegend/FishSkills/FishAmanita.cs:666 — Content/LegendWeapon/HalibutLegend/FishSkills/FishAmanita.cs:666-677 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBloodyManowar.cs:437-448 | Content/LegendWeapon/HalibutLegend/FishSkills/FishHoney.cs:253-266 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBellWave.cs:194-205 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiMirrorStand.cs:221-232 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiSandGarden.cs:203-214 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiSenjuArm.cs:207-218 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishAmanita.cs:666` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/HalibutLegend/FishSkills/FishHoney.cs:268` calls `SetValue` and `Content/LegendWeapon/HalibutLegend/FishSkills/FishAmanita.cs:679` 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.
D4 · Code Duplication · Duplicated block (12 lines × 6) · ×3
  • Duplicated block (12 lines × 6) Content/Items/Melee/DestroyersBlade.cs:508 — Content/Items/Melee/DestroyersBlade.cs:508-519 | Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:719-730 | Content/Items/Melee/DragonsScaleGreatsword.cs:531-542 | Content/Items/Melee/EnergySword.cs:547-558 | Content/Items/Melee/RebelBlade.cs:578-589 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:513-524 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DestroyersBlade.cs:508` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 6) Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBellWave.cs:192 — Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBellWave.cs:192-203 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiInkThread.cs:436-447 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiMirrorStand.cs:219-230 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiSandGarden.cs:201-212 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiSenjuArm.cs:205-216 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiThunderColumn.cs:193-204 — 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 6 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiMirrorStand.cs:234` calls `SetValue` and `Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBellWave.cs:207` 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 (12 lines × 6) Content/Items/Melee/DestroyersBlade.cs:523 — Content/Items/Melee/DestroyersBlade.cs:523-534 | Content/Items/Melee/DragonsScaleGreatsword.cs:546-557 | Content/Items/Melee/EnergySword.cs:562-573 | Content/Items/Melee/RebelBlade.cs:593-604 | Content/Items/Melee/StormGoddessSpears/StormGoddessSpearHeld.cs:533-544 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:528-539 — before extracting anything, compare `Content/Items/Melee/DestroyersBlade.cs` and `Content/Items/Melee/DragonsScaleGreatsword.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 419 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DestroyersBlade.cs:523` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13 lines × 6) · ×3
  • Duplicated block (13 lines × 6) Content/LegendWeapon/HalibutLegend/FishSkills/FishAmanita.cs:666 — Content/LegendWeapon/HalibutLegend/FishSkills/FishAmanita.cs:666-678 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBloodyManowar.cs:437-449 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBellWave.cs:194-206 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiMirrorStand.cs:221-233 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiSandGarden.cs:203-215 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiSenjuArm.cs:207-219 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishAmanita.cs:666` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiMirrorStand.cs:234` calls `SetValue` and `Content/LegendWeapon/HalibutLegend/FishSkills/FishAmanita.cs:679` does not — after which the two agree again for 3 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 (13 lines × 6) Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:907 — Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:907-919 | Content/Items/Melee/DivineSourceBlades/DivineSourceWaveProjectile.cs:337-349 | Content/Items/Melee/NeutronGlaive.cs:587-599 | Content/Items/Melee/NeutronGlaive.cs:1024-1036 | Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:721-733 | Content/Items/Modifys/RBloodButcherer.cs:706-718 — there are 6 copies across 5 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 6 sites; resolving a subset leaves the remainder to drift apart. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:736` calls `Pow` and `Content/Items/Melee/NeutronGlaive.cs:601` does not — after which the two agree again for 4 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 (13 lines × 6) Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:942 — Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:942-954 | Content/Items/Melee/DivineSourceBlades/DivineSourceWaveProjectile.cs:400-412 | Content/Items/Melee/NeutronGlaive.cs:617-629 | Content/Items/Melee/NeutronGlaive.cs:1083-1095 | Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:754-766 | Content/Items/Modifys/RBloodButcherer.cs:738-750 — there are 6 copies across 5 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 6 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:942` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13–14 lines × 4) · ×3
  • Duplicated block (13–14 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:122 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:122-134 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:116-128 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeHeatRay.cs:88-101 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeSkullBeamProj.cs:86-99 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs` and `Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 216 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:122` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13–14 lines × 4) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:229 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:229-241 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:189-201 | Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashMark.cs:78-91 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:210-222 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:229` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (13–14 lines × 4) Content/NPCs/BloomsandSerpents/Projectiles/BssDashOmen.cs:50 — Content/NPCs/BloomsandSerpents/Projectiles/BssDashOmen.cs:50-62 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerStrikeTelegraph.cs:44-57 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronTelegraph.cs:48-61 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Projectiles/QueenBeeTelegraphLine.cs:46-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BloomsandSerpents/Projectiles/BssDashOmen.cs:50` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12–14 lines × 2) · ×3
  • Duplicated block (12–14 lines × 2) Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs:205 — Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs:205-218 | Content/LegendWeapon/SHPCLegend/UI/DomainWheel/SHPCDomainWheelUI.cs:194-205 — before extracting anything, compare `Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs` and `Content/LegendWeapon/SHPCLegend/UI/DomainWheel/SHPCDomainWheelUI.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs:205` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (12–14 lines × 2) Content/Items/Melee/Arbiters/ArbiterManifestationRenderer.cs:35 — Content/Items/Melee/Arbiters/ArbiterManifestationRenderer.cs:35-48 | Content/Items/Melee/WeaverGrievanceses/WGMaterializationRenderer.cs:39-50 — before extracting anything, compare `Content/Items/Melee/Arbiters/ArbiterManifestationRenderer.cs` and `Content/Items/Melee/WeaverGrievanceses/WGMaterializationRenderer.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Arbiters/ArbiterManifestationRenderer.cs:35` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (12–14 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:493 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:493-506 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:458-469 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:493` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (12–13 lines × 3) · ×3
  • Duplicated block (12–13 lines × 3) Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFist.cs:622 — Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFist.cs:622-633 | Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainNet.cs:65-77 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainNet.cs:51-63 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFist.cs:622` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (12–13 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:700 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:700-711 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:907-919 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:703-714 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs` as WHOLE FILES: this scan already matched 48 separate duplicated blocks between them, totalling at least 508 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:700` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12–13 lines × 3) Content/LegendWeapon/SHPCLegend/Modules/Barrel/HiveBarrelModule.cs:163 — Content/LegendWeapon/SHPCLegend/Modules/Barrel/HiveBarrelModule.cs:163-174 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/ObsidianBarrelModule.cs:241-253 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/ScattershotBarrelModule.cs:239-250 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/SHPCLegend/Modules/Barrel/ObsidianBarrelModule.cs:256` calls `Lerp` and `Content/LegendWeapon/SHPCLegend/Modules/Barrel/HiveBarrelModule.cs:176` 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.
D4 · Code Duplication · Duplicated block (11 lines × 7) · ×3
  • Duplicated block (11 lines × 7) Content/GameModes/BrutalMobs/Ambience/Astralveil/AstralveilSpearDirector.cs:194 — Content/GameModes/BrutalMobs/Ambience/Astralveil/AstralveilSpearDirector.cs:194-204 | Content/GameModes/BrutalMobs/Ambience/Frostveil/FrostveilGaleScheduler.cs:119-129 | Content/GameModes/BrutalMobs/Ambience/Prismglade/PrismgladeAmbience.cs:222-232 | Content/GameModes/BrutalMobs/DungeonDeep/DungeonDeepNPC.cs:281-291 | Content/GameModes/BrutalMobs/FrostLegion/FrostLegionNPC.cs:270-280 | Content/GameModes/BrutalMobs/Sandveil/SandveilBrutalNPC.cs:243-253 | Content/GameModes/BrutalMobs/Wastes/WastesBrutalNPC.cs:186-196 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/Astralveil/AstralveilSpearDirector.cs:194` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11 lines × 7) Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipBoneProj.cs:126 — Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipBoneProj.cs:126-136 | Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipFirecrackerChainProj.cs:28-38 | Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipLeatherCrackProj.cs:24-34 | Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipMorningStarProj.cs:147-157 | Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipPrismSlashProj.cs:36-46 | Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipReapProj.cs:99-109 | Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipThornProj.cs:24-34 — 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 7 call sites, so a change lands once.
  • Duplicated block (11 lines × 7) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:549 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:549-559 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumCircle.cs:244-254 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoProj.cs:164-174 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistThunderOrb.cs:178-188 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaMiniBloodSlime.cs:196-206 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeBloodBee.cs:123-133 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshLeech.cs:129-139 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:549` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (12 lines × 5) · ×3
  • Duplicated block (12 lines × 5) Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdCastOmen.cs:231 — Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdCastOmen.cs:231-242 | Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdHammerConeOmen.cs:140-151 | Content/GameModes/BrutalMobs/EvilBiome/Projectiles/MummyWrapOmen.cs:99-110 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmYetiConeOmen.cs:155-166 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandConeTelegraph.cs:162-173 — before extracting anything, compare `Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdHammerConeOmen.cs` and `Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmYetiConeOmen.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/GameModes/BrutalMobs/EvilBiome/Projectiles/MummyWrapOmen.cs:113` calls `Size`, `ToRotationVector2` and `Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdCastOmen.cs:244` 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 (12 lines × 5) Content/Items/Magic/Pandemoniums/PandemoniumFirePillar.cs:152 — Content/Items/Magic/Pandemoniums/PandemoniumFirePillar.cs:152-164 | Content/Items/Magic/Pandemoniums/PandemoniumRainDrop.cs:97-108 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:506-517 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:772-783 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:806-817 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Magic/Pandemoniums/PandemoniumFirePillar.cs:148` calls `AddBuff`, `OnKill` and `Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:770` 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 (12 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1110 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1110-1125 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1141-1152 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1451-1466 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:945-956 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:894-909 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs` as WHOLE FILES: this scan already matched 55 separate duplicated blocks between them, totalling at least 611 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1107` calls `BladeDrawRot` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1446` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (11–12 lines × 5) · ×3
  • Duplicated block (11–12 lines × 5) Content/GameModes/GodSmith/Weapons/Flamethrowers/FlamethrowersShared.cs:58 — Content/GameModes/GodSmith/Weapons/Flamethrowers/FlamethrowersShared.cs:58-68 | Content/GameModes/GodSmith/Weapons/Guns/GsGunPoseShared.cs:111-122 | Content/GameModes/GodSmith/Weapons/Guns/GsMinishark.cs:152-162 | Content/GameModes/GodSmith/Weapons/Guns/GsPhoenixBlaster.cs:140-150 | Content/GameModes/GodSmith/Weapons/Specials/GsChainGun.cs:72-82 — before extracting anything, compare `Content/GameModes/GodSmith/Weapons/Guns/GsMinishark.cs` and `Content/GameModes/GodSmith/Weapons/Guns/GsPhoenixBlaster.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 74 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–12 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:650 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:650-661 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:774-785 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:862-873 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:656-666 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:672-682 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:650` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:684` calls `Lerp` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:664` 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–12 lines × 5) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDetonationProj.cs:155 — Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDetonationProj.cs:155-165 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberShockwaveProj.cs:57-67 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberFreezeWaveProj.cs:46-56 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberPixelDecomposeProj.cs:42-53 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberReformProj.cs:45-56 — before extracting anything, compare `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDetonationProj.cs` and `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberShockwaveProj.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 82 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberShockwaveProj.cs:68` calls `Clamp`, `Lerp` and `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDetonationProj.cs:167` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (9–11 lines × 3) · ×3
  • Duplicated block (9–11 lines × 3) Content/HackTimes/Protocols/DelayFuse.cs:51 — Content/HackTimes/Protocols/DelayFuse.cs:51-60 | Content/HackTimes/Protocols/ProjectileFreeze.cs:25-35 | Content/HackTimes/Protocols/ProjectileTithe.cs:87-95 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/HackTimes/Protocols/DelayFuse.cs:51` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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 (9–11 lines × 3) Content/LegendWeapon/OnikiriLegend/OniDismembers/OniSeverReplicationSystem.cs:200 — Content/LegendWeapon/OnikiriLegend/OniDismembers/OniSeverReplicationSystem.cs:200-208 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBanish.Net.cs:433-443 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.Net.cs:1149-1159 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9–11 lines × 3) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsCombinedAttackState.cs:218 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsCombinedAttackState.cs:218-228 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsCrossDashState.cs:161-169 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsPincerGrabState.cs:364-372 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsCombinedAttackState.cs:218` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (3–9 lines × 3) · ×3
  • Duplicated block (3–9 lines × 3) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:302 — Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:302-310 | Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingPanel.cs:485-493 | Content/LegendWeapon/SHPCLegend/UI/SHPCModuleSelectPanel.cs:272-274 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:302` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (3–9 lines × 3) Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsEyeGrabState.cs:168 — Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsEyeGrabState.cs:168-170 | Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsGazeRoarState.cs:78-86 | Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsPhaseRoarState.cs:59-67 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsGazeRoarState.cs:78` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (3–9 lines × 3) Content/Scenarios/Dungeonworld/NPCs/Elites/BoneStitcher.cs:221 — Content/Scenarios/Dungeonworld/NPCs/Elites/BoneStitcher.cs:221-223 | Content/Scenarios/Dungeonworld/NPCs/Elites/BoneStitcher.cs:235-243 | Content/Scenarios/Dungeonworld/NPCs/Elites/BoneStitcher.cs:460-468 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/NPCs/Elites/BoneStitcher.cs:221` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (7 lines × 10) · ×3
  • Duplicated block (7 lines × 10) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:984 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:984-990 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:893-899 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:702-708 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:956-962 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1166-1172 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:968-974 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:777-783 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:741-747 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1082-1088 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:1151-1157 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs` as WHOLE FILES: this scan already matched 43 separate duplicated blocks between them, totalling at least 492 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1161` calls `SmoothStep01` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:963` does not — after which the two agree again for 3 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 × 10) Content/Items/Accessories/ArcaneThroneOfEternity.cs:328 — Content/Items/Accessories/ArcaneThroneOfEternity.cs:328-334 | Content/Items/Accessories/ArcaneThroneOfEternity.cs:459-465 | Content/LegendWeapon/HalibutLegend/DomainSkills/SeaDomain.cs:676-685 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutDomain.cs:318-325 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDetonationProj.cs:208-215 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Restart/CyberRestartProj.cs:215-222 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberPixelDecomposeProj.cs:88-95 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberReformProj.cs:94-101 | Content/LegendWeapon/SHPCLegend/Modules/Frame/ResonanceFrameModule.cs:699-705 | Content/LegendWeapon/SHPCLegend/Modules/Power/PlasmaInjectorModule.cs:170-177 — there are 10 copies across 9 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 10 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/DomainSkills/SeaDomain.cs:676` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (7 lines × 10) Content/Items/Accessories/BrutalRelics/MoonLord/BlackFlashSigilRender.cs:142 — Content/Items/Accessories/BrutalRelics/MoonLord/BlackFlashSigilRender.cs:142-148 | Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryRender.cs:221-229 | Content/Scenarios/Kiyume/NPCs/FacelessOneYokai.cs:494-501 | Content/Scenarios/Kiyume/NPCs/FuneralCortegeYokai.cs:1207-1214 | Content/Scenarios/Kiyume/NPCs/KiyumeHound.cs:1051-1058 | Content/Scenarios/Kiyume/NPCs/KiyumeWhiteHound.cs:474-481 | Content/Scenarios/Kiyume/NPCs/LanternGuideYokai.cs:592-599 | Content/Scenarios/Kiyume/NPCs/RidgeWalkerYokai.cs:594-602 | Content/Scenarios/Kiyume/NPCs/ShallowHandsYokai.cs:395-403 | Content/Scenarios/Kiyume/NPCs/WellHandYokai.cs:407-415 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 10 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 10 times. 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.
D4 · Code Duplication · Duplicated block (7–8 lines × 6) · ×3
  • Duplicated block (7–8 lines × 6) Content/GameModes/BrutalMobs/Legion/Projectiles/LegionInkOmen.cs:72 — Content/GameModes/BrutalMobs/Legion/Projectiles/LegionInkOmen.cs:72-79 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionScoutOmen.cs:58-64 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionSurfOmen.cs:65-71 | Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomSporeMistTelegraph.cs:99-105 | Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomVineWhipOmen.cs:75-81 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandConeTelegraph.cs:116-122 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Legion/Projectiles/LegionInkOmen.cs:72` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomVineWhipOmen.cs:71` calls `PlaySound` and `Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandConeTelegraph.cs:112` 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–8 lines × 6) Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamHound.cs:962 — Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamHound.cs:962-968 | Content/Scenarios/Kiyume/NPCs/FacelessOneYokai.cs:499-505 | Content/Scenarios/Kiyume/NPCs/KiyumeHound.cs:1056-1062 | Content/Scenarios/Kiyume/NPCs/KiyumeWhiteHound.cs:479-485 | Content/Scenarios/Kiyume/NPCs/LanternGuideYokai.cs:597-603 | Content/Scenarios/Kiyume/NPCs/RidgeWalkerYokai.cs:599-606 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times.
  • Duplicated block (7–8 lines × 6) Content/Scenarios/OldNet/Gen/Zones/Z1/Z1Rooms.cs:13 — Content/Scenarios/OldNet/Gen/Zones/Z1/Z1Rooms.cs:13-20 | Content/Scenarios/OldNet/Gen/Zones/Z2/Z2Rooms.cs:16-22 | Content/Scenarios/OldNet/Gen/Zones/Z2/Z2Rooms.cs:65-71 | Content/Scenarios/OldNet/Gen/Zones/Z2/Z2Rooms.cs:155-161 | Content/Scenarios/OldNet/Gen/Zones/Z3/Z3Rooms.cs:16-22 | Content/Scenarios/OldNet/Gen/Zones/Z3/Z3Rooms.cs:212-218 — there are 6 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 6 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/OldNet/Gen/Zones/Z1/Z1Rooms.cs:13` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (6–8 lines × 3) · ×3
  • Duplicated block (6–8 lines × 3) Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaBurst.cs:340 — Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaBurst.cs:340-345 | Content/Items/Melee/GeminisTribute.cs:506-513 | Content/Items/Melee/GeminisTribute.cs:736-743 — 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 (6–8 lines × 3) Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadArcProj.cs:217 — Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadArcProj.cs:217-224 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:940-945 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeArcChainProj.cs:242-249 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadArcProj.cs:217` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6–8 lines × 3) Content/Scenarios/Dungeonworld/NPCs/OverseerSlagGlob.cs:259 — Content/Scenarios/Dungeonworld/NPCs/OverseerSlagGlob.cs:259-264 | Content/Scenarios/Dungeonworld/NPCs/OverseerVfx.cs:310-317 | Content/Scenarios/Dungeonworld/NPCs/UndrownedTideWave.cs:252-258 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/NPCs/OverseerSlagGlob.cs:259` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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.
D4 · Code Duplication · Duplicated block (6–7 lines × 4) · ×3
  • Duplicated block (6–7 lines × 4) Content/Items/Stones/Granites/GraniteEffects.cs:58 — Content/Items/Stones/Granites/GraniteEffects.cs:58-63 | Content/Items/Stones/Granites/GraniteFlower.cs:366-371 | Content/Items/Stones/Granites/GraniteThrowingKnife.cs:135-141 | Content/Items/Stones/Granites/GraniteTome.cs:371-376 — 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 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Stones/Granites/GraniteEffects.cs:58` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6–7 lines × 4) Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniKamuiFlowRenderer.cs:51 — Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniKamuiFlowRenderer.cs:51-56 | Content/LegendWeapon/OnikiriLegend/UI/OniItemTooltipPanel.cs:40-46 | Content/LegendWeapon/OnikiriLegend/UI/OniRegisterRenderer.cs:41-47 | Content/UIs/UIEffect/OniShaderPanel.cs:34-40 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. 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 (6–7 lines × 4) Content/NPCs/BrutalNPCs/BrutalDukeFishron/Rendering/FishronMotionFX.cs:86 — Content/NPCs/BrutalNPCs/BrutalDukeFishron/Rendering/FishronMotionFX.cs:86-91 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Core/EocMotion.cs:84-89 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Core/TwinsMotion.cs:91-97 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Core/QueenBeeMotion.cs:82-87 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalDukeFishron/Rendering/FishronMotionFX.cs:86` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (6 lines × 11) · ×3
  • Duplicated block (6 lines × 11) Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMoonFlare.cs:277 — Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMoonFlare.cs:277-282 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteStarSurge.cs:191-196 | Content/Items/Accessories/BrutalRelics/WallOfFlesh/GluttonousRetinaRender.cs:102-108 | Content/Items/Accessories/BrutalRelics/WallOfFlesh/GluttonousTongueProj.cs:431-436 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistCoronaLance.cs:131-136 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistGazeBeam.cs:279-284 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistGazeBeam.cs:341-346 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistPlanetProj.cs:853-858 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistUmbraShade.cs:509-514 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistZodiacRing.cs:180-185 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordOrbProj.cs:298-303 — there are 11 copies across 10 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 11 sites; resolving a subset leaves the remainder to drift apart.
  • Duplicated block (6 lines × 11) Content/Items/Accessories/BrutalRelics/MoonLord/BlackFlashSigilRender.cs:142 — Content/Items/Accessories/BrutalRelics/MoonLord/BlackFlashSigilRender.cs:142-148 | Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryRender.cs:221-229 | Content/Scenarios/Dungeonworld/NPCs/Elites/LampeaterWisp.cs:576-581 | Content/Scenarios/Kiyume/NPCs/FacelessOneYokai.cs:494-501 | Content/Scenarios/Kiyume/NPCs/FuneralCortegeYokai.cs:1207-1214 | Content/Scenarios/Kiyume/NPCs/KiyumeHound.cs:1051-1058 | Content/Scenarios/Kiyume/NPCs/KiyumeWhiteHound.cs:474-481 | Content/Scenarios/Kiyume/NPCs/LanternGuideYokai.cs:592-599 | Content/Scenarios/Kiyume/NPCs/RidgeWalkerYokai.cs:594-602 | Content/Scenarios/Kiyume/NPCs/ShallowHandsYokai.cs:395-403 | Content/Scenarios/Kiyume/NPCs/WellHandYokai.cs:407-415 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 11 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 11 times. 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 (6 lines × 11) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:1483 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:1483-1488 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:1164-1169 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1385-1390 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1452-1457 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1509-1514 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaMiniBloodSlime.cs:227-233 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1571-1576 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1634-1639 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1664-1669 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1398-1403 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1733-1738 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 11 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 11 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:1483` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1382` calls `OnKill` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaMiniBloodSlime.cs:226` 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.
D4 · Code Duplication · Duplicated block (5 lines × 11) · ×3
  • Duplicated block (5 lines × 11) Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs:216 — Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs:216-221 | Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawWormProj.cs:592-596 | Content/Items/Magic/Everdeeps/EverdeepMaelstrom.cs:340-345 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronSharkTornadoProj.cs:333-338 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronTsunamiWallProj.cs:186-191 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidPool.cs:113-118 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowBreachOmen.cs:94-98 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowDevourOmen.cs:128-132 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowGeyserProj.cs:200-204 | Content/NPCs/FestersandSerpents/Projectiles/FssGeyserColumn.cs:204-208 | Content/NPCs/FestersandSerpents/Projectiles/FssIchorPool.cs:233-238 — before extracting anything, compare `Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs` and `Content/Items/Magic/Everdeeps/EverdeepMaelstrom.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 11) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:380 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:380-384 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:352-356 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:393-397 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:383-387 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:373-377 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:316-320 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:347-351 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:389-393 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:339-343 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:460-464 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:400-404 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs` as WHOLE FILES: this scan already matched 55 separate duplicated blocks between them, totalling at least 611 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:380` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:469` calls `UpdateVesselRaise` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:392` 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 (5 lines × 11) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeSlash.cs:88 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeSlash.cs:88-92 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:165-169 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressPetal.cs:146-150 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:425-429 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:937-941 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:532-536 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:539-543 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeLaserBolt.cs:97-101 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeMortar.cs:227-231 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:466-470 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:402-406 — there are 11 copies across 10 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 11 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeSlash.cs:88` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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.
D4 · Code Duplication · Duplicated block (3–5 lines × 5) · ×3
  • Duplicated block (3–5 lines × 5) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismDashingState.cs:59 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismDashingState.cs:59-63 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismPhase2DashingState.cs:67-71 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismShadowDashState.cs:153-157 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismSoloRageState.cs:206-210 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismSoloRageState.cs:397-399 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismDashingState.cs` and `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismPhase2DashingState.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 45 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismDashingState.cs:59` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismDashingState.cs:59` calls `SafeNormalize`, `NextVector2Circular` and `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismSoloRageState.cs:397` 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 (3–5 lines × 5) Content/Industrials/ElectricPowers/GridSwitches/GridSwitchTP.cs:281 — Content/Industrials/ElectricPowers/GridSwitches/GridSwitchTP.cs:281-285 | Content/Industrials/ElectricPowers/GridSwitches/GridSwitchTP.cs:306-308 | Content/Industrials/ElectricPowers/Sensors/SensorTP.cs:390-394 | Content/Industrials/ElectricPowers/Sensors/SensorTP.cs:399-403 | Content/Industrials/ElectricPowers/WireInterfaces/WireInterfaceTP.cs:315-319 — 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 (3–5 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaMinionDrownFX.cs:152 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaMinionDrownFX.cs:152-154 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaPlayerDrownFX.cs:290-294 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaPlayerDrownFX.cs:300-304 | Content/NPCs/ScrapCommanders/Projectiles/ScrapJunkPile.cs:80-82 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpVoltBubble.cs:206-208 — there are 5 copies across 4 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaMinionDrownFX.cs:152` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (3–5 lines × 3) · ×3
  • Duplicated block (3–5 lines × 3) Content/Industrials/ElectricPowers/GridSwitches/GridSwitchTP.cs:301 — Content/Industrials/ElectricPowers/GridSwitches/GridSwitchTP.cs:301-305 | Content/Industrials/ElectricPowers/WireInterfaces/WireInterfaceTP.cs:329-333 | Content/Industrials/ElectricPowers/WireInterfaces/WireInterfaceTP.cs:334-336 — 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. 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 (3–5 lines × 3) Content/NPCs/ScrapCommanders/Projectiles/ScrapSweepBeam.cs:165 — Content/NPCs/ScrapCommanders/Projectiles/ScrapSweepBeam.cs:165-169 | Content/NPCs/ScrapCommanders/States/ScrapLaserSweepState.cs:215-219 | Content/NPCs/ScrapCommanders/States/ScrapSawLaunchState.cs:132-134 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/ScrapCommanders/Projectiles/ScrapSweepBeam.cs:165` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (3–5 lines × 3) Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:840 — Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:840-844 | Content/QuestLogs/Styles/ForestQuestLogStyle.cs:591-593 | Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:654-659 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:840` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
IC1 · Incompleteness & stubs · Both branches are identical · ×3
  • Both branches are identical — the condition decides nothing Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerPrecisionSniperState.cs:22 — Both arms of `Context.IsAsuraMode ? … : …` are `2`, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
  • Both branches are identical — the condition decides nothing Content/PRTTypes/PRT_CampfireSteam.cs:39 — Both arms of `isEnhanced ? … : …` are `Color.Yellow`, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
  • Both branches are identical — the condition decides nothing Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3MazeBlock.cs:137 — Both arms of `plan.Forbidden ? … : …` are `12`, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
X5 · Nullable reference types · Null guard scopes only part of the work it protects · ×3
  • Null guard scopes only part of the work it protects Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs:241 — This method contradicts itself about `player`: line 224 tests it for null before doing anything with it — the author's own statement that null is an input this code expects — but that `if` scopes only the block beneath it, and line 241 then dereferences `player` as `player.GetModPlayer` AFTER the block has closed, where the guard no longer applies. A null `player` skips the guarded body and reaches that line anyway, throwing NullReferenceException on exactly the input the guard was written for. If the dereference belongs to the guarded work, move it inside the block; if `player` truly cannot be null by then, the guard above is misleading and should go.
  • Null guard scopes only part of the work it protects Content/Items/Melee/WeaverGrievanceses/WGManifestationNet.cs:242 — This method contradicts itself about `player`: line 225 tests it for null before doing anything with it — the author's own statement that null is an input this code expects — but that `if` scopes only the block beneath it, and line 242 then dereferences `player` as `player.GetModPlayer` AFTER the block has closed, where the guard no longer applies. A null `player` skips the guarded body and reaches that line anyway, throwing NullReferenceException on exactly the input the guard was written for. If the dereference belongs to the guarded work, move it inside the block; if `player` truly cannot be null by then, the guard above is misleading and should go.
  • Null guard scopes only part of the work it protects Content/LegendWeapon/OnikiriLegend/OniOmokages/OniOmokageRender.cs:267 — This method contradicts itself about `fx`: line 238 tests it for null before doing anything with it — the author's own statement that null is an input this code expects — but that `if` scopes only the block beneath it, and line 267 then dereferences `fx` as `fx.CurrentTechnique` AFTER the block has closed, where the guard no longer applies. A null `fx` skips the guarded body and reaches that line anyway, throwing NullReferenceException on exactly the input the guard was written for. If the dereference belongs to the guarded work, move it inside the block; if `fx` truly cannot be null by then, the guard above is misleading and should go.
D35 · Change Coupling · Change-coupling hub · ×2
  • Change-coupling hub: CrimsonRendSlash.cs → CrimsonRendCleave.cs, OniAnnihilate.cs, OniFinaleCut.cs, OniFlashMark.cs Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs — `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` changes together with 4 other files — `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendCleave.cs`, `Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs`, `Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleCut.cs`, `Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashMark.cs` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
  • Change-coupling hub: OniFinaleCut.cs → OniAnnihilate.cs, OniFlashMark.cs, OniZanshinSlash.cs Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleCut.cs — `Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleCut.cs` changes together with 3 other files — `Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs`, `Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashMark.cs`, `Content/LegendWeapon/OnikiriLegend/OniZanshinSlashs/OniZanshinSlash.cs` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
D4 · Code Duplication · Near-duplicate member family (15 members, 11 shared lines) · ×2
  • Near-duplicate member family (15 members, 11 shared lines) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:331 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:331-350 | Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:386-405 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs:363-382 | Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:329-348 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs:347-366 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:355-374 | Content/Industrials/ElectricPowers/Launchers/PlayerLauncherUI.cs:274-293 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:270-289 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconUI.cs:294-313 | Content/Industrials/ElectricPowers/Recyclers/RecyclerUI.cs:328-347 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterUI.cs:339-358 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:304-323 | Content/Industrials/ElectricPowers/TeleportStations/TeleportStationUI.cs:369-395 | Content/Industrials/Generator/Biomass/BiomassGeneratorUI.cs:233-251 | Content/Industrials/Generator/Thermal/ThermalGeneratorUI.cs:344-368 — These 15 members are variants of one another: a block of 11 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them 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.
  • Near-duplicate member family (15 members, 11 shared lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:489 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:489-526 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:466-504 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:388-424 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:445-477 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:344-381 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:337-375 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:411-448 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:405-440 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:448-490 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:518-555 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:526-560 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:454-487 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:389-425 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:407-453 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:456-493 — These 15 members are variants of one another: a block of 11 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them 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 · Near-duplicate member family (7 members, 18 shared lines) · ×2
  • Near-duplicate member family (7 members, 18 shared lines) Content/Industrials/Generator/Hydroelectrics/Hydroelectric.cs:71 — Content/Industrials/Generator/Hydroelectrics/Hydroelectric.cs:71-90 | Content/Industrials/Generator/Hydroelectrics/HydroelectricMK2.cs:61-80 | Content/Industrials/Generator/Thermal/ThermalGeneratorMK2.cs:55-75 | Content/Industrials/Generator/WindGriven/WGGMK2Wilderness.cs:44-65 | Content/Industrials/Generator/WindGriven/WGGWilderness.cs:44-63 | Content/Industrials/Generator/WindGriven/WindGrivenGenerator.cs:80-99 | Content/Industrials/Generator/WindGriven/WindGrivenGeneratorMk2.cs:81-103 — These 7 members are variants of one another: a block of 18 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 7 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 7 times.
  • Near-duplicate member family (7 members, 18 shared lines) Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:164 — Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:164-214 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerFrostPulseProj.cs:118-161 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerIceSpikeProj.cs:146-197 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenChandelierProj.cs:134-181 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenCrystalPrisonProj.cs:136-191 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenRoyalChandelierProj.cs:143-189 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Rendering/QueenPrismNodeRenderer.cs:53-85 — These 7 members are variants of one another: a block of 18 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 7 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 7 times.
D4 · Code Duplication · Near-duplicate member family (6 members, 32 shared lines) · ×2
  • Near-duplicate member family (6 members, 32 shared lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1219 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1219-1289 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1573-1688 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1156-1238 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1298-1353 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:1108-1189 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1606-1717 — These 6 members are variants of one another: a block of 32 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 6 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 6 times.
  • Near-duplicate member family (6 members, 32 shared lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:338 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:338-421 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:328-407 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:274-347 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:247-323 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:305-383 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:344-423 — These 6 members are variants of one another: a block of 32 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 6 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 6 times.
D4 · Code Duplication · Near-duplicate member family (6 members, 16 shared lines) · ×2
  • Near-duplicate member family (6 members, 16 shared lines) Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:296 — Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:296-341 | Content/Items/Magic/CommandersStaff.cs:328-371 | Content/Items/Melee/Heartcarver.cs:486-529 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:259-295 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs:312-347 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:207-244 — These 6 members are variants of one another: a block of 16 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 6 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 6 times.
  • Near-duplicate member family (6 members, 16 shared lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:451 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:451-494 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:700-747 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:449-492 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:741-790 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:426-471 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:414-457 — These 6 members are variants of one another: a block of 16 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 6 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 6 times.
D4 · Code Duplication · Near-duplicate member family (5 members, 20 shared lines) · ×2
  • Near-duplicate member family (5 members, 20 shared lines) Content/Cyberwares/Implementation/Sandevistans/SandevistanRender.cs:16 — Content/Cyberwares/Implementation/Sandevistans/SandevistanRender.cs:16-87 | Content/HackTimes/HackTimeRender.cs:74-117 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainRender.cs:24-81 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspaceRender.cs:106-188 | Content/Scenarios/OldNet/Renders/OldNetGradeRender.cs:21-94 — These 5 members are variants of one another: a block of 20 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 5 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 5 times.
  • Near-duplicate member family (5 members, 20 shared lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:265 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:265-303 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:1047-1086 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1278-1315 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1328-1415 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1414-1455 — These 5 members are variants of one another: a block of 20 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 5 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 5 times.
D4 · Code Duplication · Near-duplicate member family (5 members, 16 shared lines) · ×2
  • Near-duplicate member family (5 members, 16 shared lines) Content/Industrials/ElectricPowers/ElectricMinRocket.cs:239 — Content/Industrials/ElectricPowers/ElectricMinRocket.cs:239-259 | Content/Industrials/ElectricPowers/MiningMachines/MiningMachine.cs:58-78 | Content/Industrials/ElectricPowers/MiningMachines/MiningMachineMk2.cs:58-78 | Content/Industrials/ElectricPowers/Recyclers/RecyclerTile.cs:19-39 | Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersTile.cs:20-38 — These 5 members are variants of one another: a block of 16 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 5 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 5 times.
  • Near-duplicate member family (5 members, 16 shared lines) Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzCrystalProj.cs:246 — Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzCrystalProj.cs:246-291 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenChandelierProj.cs:134-181 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenCrystalPrisonProj.cs:136-191 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenRoyalChandelierProj.cs:143-189 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Rendering/QueenPrismNodeRenderer.cs:53-85 — These 5 members are variants of one another: a block of 16 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 5 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 5 times.
D4 · Code Duplication · Near-duplicate member family (5 members, 15 shared lines) · ×2
  • Near-duplicate member family (5 members, 15 shared lines) Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhImpFireBolt.cs:72 — Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhImpFireBolt.cs:72-94 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhScytheBolt.cs:73-95 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhStingerBolt.cs:73-96 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhTridentBolt.cs:72-94 | Content/GameModes/BrutalMobs/Sky/Projectiles/SkyFeatherBolt.cs:66-89 — These 5 members are variants of one another: a block of 15 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 5 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 5 times.
  • Near-duplicate member family (5 members, 15 shared lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:265 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:265-303 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:1047-1086 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1278-1315 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1414-1455 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1555-1604 — These 5 members are variants of one another: a block of 15 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 5 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 5 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 22 shared lines) · ×2
  • Near-duplicate member family (4 members, 22 shared lines) Content/Items/Melee/OniMacheteHands.cs:1303 — Content/Items/Melee/OniMacheteHands.cs:1303-1367 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCrimsonTiger.cs:758-819 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDemonicHell.cs:601-666 | Content/LegendWeapon/HalibutLegend/FishSkills/FishFallenStarVFX.cs:168-231 — These 4 members are variants of one another: a block of 22 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 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 4 times.
  • Near-duplicate member family (4 members, 22 shared lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:87 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:87-173 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:81-165 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeHeatRay.cs:59-117 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeSkullBeamProj.cs:50-128 — These 4 members are variants of one another: a block of 22 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 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 4 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 21 shared lines) · ×2
  • Near-duplicate member family (4 members, 21 shared lines) Content/Items/Melee/OniMacheteHands.cs:1303 — Content/Items/Melee/OniMacheteHands.cs:1303-1367 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCrimsonTiger.cs:758-819 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDemonicHell.cs:601-666 | Content/LegendWeapon/HalibutLegend/FishSkills/FishWyverntail.cs:364-418 — These 4 members are variants of one another: a block of 21 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 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 4 times.
  • Near-duplicate member family (4 members, 21 shared lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:87 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:87-173 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:81-165 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs:47-126 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeSkullBeamProj.cs:50-128 — These 4 members are variants of one another: a block of 21 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 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 4 times.
D4 · Code Duplication · Near-duplicate member family (3 members, 35 shared lines) · ×2
  • Near-duplicate member family (3 members, 35 shared lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:808 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:808-1015 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:609-814 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:764-1002 — These 3 members are variants of one another: a block of 35 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 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 3 times.
  • Near-duplicate member family (3 members, 35 shared lines) Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:175 — Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:175-239 | Content/Scenarios/Kiame/Overlay/OniRainExitTransition.cs:132-196 | Content/Scenarios/Kiame/Overlay/OniRainWorldTransition.cs:210-297 — These 3 members are variants of one another: a block of 35 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 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 3 times.
D4 · Code Duplication · Near-duplicate member family (3 members, 21 shared lines) · ×2
  • Near-duplicate member family (3 members, 21 shared lines) Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdHammerConeOmen.cs:137 — Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdHammerConeOmen.cs:137-187 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmYetiConeOmen.cs:152-201 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandConeTelegraph.cs:159-204 — These 3 members are variants of one another: a block of 21 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 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 3 times.
  • Near-duplicate member family (3 members, 21 shared lines) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs:118 — Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs:118-144 | Content/NPCs/FestersandSerpents/Projectiles/FssCascadeDrop.cs:72-115 | Content/NPCs/FestersandSerpents/Projectiles/FssIchorGlob.cs:116-142 — These 3 members are variants of one another: a block of 21 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 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 3 times.
D4 · Code Duplication · Near-duplicate member pair (55 shared lines) · ×2
  • Near-duplicate member pair (55 shared lines) Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:313 — Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:313-379 | Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:251-315 — These two members are variants of one another: 55 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 (55 shared lines) Content/Items/Melee/Arbiters/ArbiterManifestationRenderer.cs:35 — Content/Items/Melee/Arbiters/ArbiterManifestationRenderer.cs:35-125 | Content/Items/Melee/WeaverGrievanceses/WGMaterializationRenderer.cs:39-110 — These two members are variants of one another: 55 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 · Near-duplicate member pair (43 shared lines) · ×2
  • Near-duplicate member pair (43 shared lines) Content/Scenarios/Hadalworld/Ambience/HadalSky.cs:75 — Content/Scenarios/Hadalworld/Ambience/HadalSky.cs:75-176 | Content/Scenarios/OldNet/Backgrounds/OldNetSky.cs:75-220 — These two members are variants of one another: 43 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 (43 shared lines) Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:202 — Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:202-311 | Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:130-249 — These two members are variants of one another: 43 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 · Near-duplicate member pair (33 shared lines) · ×2
  • Near-duplicate member pair (33 shared lines) Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaRender.cs:228 — Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaRender.cs:228-277 | Content/NPCs/BrutalNPCs/BrutalPlantera/Rendering/PlanteraBloomRender.cs:50-100 — These two members are variants of one another: 33 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 (33 shared lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeSlash.cs:169 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeSlash.cs:169-225 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithSlash.cs:181-261 — These two members are variants of one another: 33 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 · Near-duplicate member pair (31 shared lines) · ×2
  • Near-duplicate member pair (31 shared lines) Content/Scenarios/Kiyume/Ambience/KiyumeCrowFlight.cs:323 — Content/Scenarios/Kiyume/Ambience/KiyumeCrowFlight.cs:323-369 | Content/Scenarios/Kiyume/Ambience/KiyumeCrowRoost.cs:478-523 — These two members are variants of one another: 31 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 (31 shared lines) Content/Cyberwares/UIs/CyberwareUI.cs:270 — Content/Cyberwares/UIs/CyberwareUI.cs:270-336 | Content/NPCs/Victors/UIs/VictorClinicUI.cs:175-233 — These two members are variants of one another: 31 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 · Near-duplicate member pair (28 shared lines) · ×2
  • Near-duplicate member pair (28 shared lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:149 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:149-189 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemMagmaBall.cs:263-312 — These two members are variants of one another: 28 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 (28 shared lines) Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniKamuiFlowRenderer.cs:70 — Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniKamuiFlowRenderer.cs:70-148 | Content/LegendWeapon/OnikiriLegend/OniSakuraFlights/OniSakuraFlowRenderer.cs:85-159 — These two members are variants of one another: 28 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 · Edited copy of a member (83 corresponding lines) · ×2
  • Edited copy of a member (83 corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:422 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:422-504 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:548-647 — These two members are one piece of code written twice and then edited apart: 83 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (83 corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:612 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:612-701 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:422-504 — These two members are one piece of code written twice and then edited apart: 83 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (89 corresponding lines) · ×2
  • Edited copy of a member (89 corresponding lines) Content/Industrials/ElectricPowers/TreeRegrowths/TreeBlueprint.cs:158 — Content/Industrials/ElectricPowers/TreeRegrowths/TreeBlueprint.cs:158-268 | Content/Industrials/ElectricPowers/TreeRegrowths/TreeBlueprint.cs:271-359 — These two members are one piece of code written twice and then edited apart: 89 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (89 corresponding lines) Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenBallroomStepState.cs:51 — Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenBallroomStepState.cs:51-139 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenSpikeRondoState.cs:55-147 — These two members are one piece of code written twice and then edited apart: 89 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 55+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 55+ corresponding lines) Content/Scenarios/Kiyume/NPCs/FacelessOneYokai.cs:470 — Content/Scenarios/Kiyume/NPCs/FacelessOneYokai.cs:470-524 | Content/Scenarios/Kiyume/NPCs/FuneralCortegeYokai.cs:1181-1240 | Content/Scenarios/Kiyume/NPCs/LanternGuideYokai.cs:563-622 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 55 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 55+ corresponding lines) Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:457 — Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:457-511 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:490-545 | Content/Industrials/ElectricPowers/Recyclers/RecyclerUI.cs:418-472 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 55 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (64 corresponding lines) · ×2
  • Edited copy of a member (64 corresponding lines) Content/Scenarios/Dungeonworld/NPCs/Elites/LanternWardenRender.cs:34 — Content/Scenarios/Dungeonworld/NPCs/Elites/LanternWardenRender.cs:34-97 | Content/Scenarios/Dungeonworld/NPCs/Elites/TurnkeyRendering.cs:32-102 — These two members are one piece of code written twice and then edited apart: 64 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (64 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:255 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:255-327 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:259-322 — These two members are one piece of code written twice and then edited apart: 64 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (66 corresponding lines) · ×2
  • Edited copy of a member (66 corresponding lines) Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilSurgeColumnProj.cs:93 — Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilSurgeColumnProj.cs:93-167 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandGeyserProj.cs:83-148 — These two members are one piece of code written twice and then edited apart: 66 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (66 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:839 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:839-911 | Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:979-1044 — These two members are one piece of code written twice and then edited apart: 66 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 63+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 63+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/PincerBindTether.cs:65 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/PincerBindTether.cs:65-127 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/TwinsTetherArc.cs:50-113 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeArcChainProj.cs:58-122 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 63 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 63+ corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:704 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:704-766 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:507-569 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:650-719 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 63 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 50+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 50+ corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1497 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1497-1549 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1211-1260 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1406-1458 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 50 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 50+ corresponding lines) Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBellWave.cs:187 — Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBellWave.cs:187-236 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBellWave.cs:258-313 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiSandGarden.cs:196-246 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 50 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 38+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 38+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:298 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:298-340 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs:369-406 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:247-291 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 38 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 38+ corresponding lines) Content/LegendWeapon/OnikiriLegend/TrialQuests/OnikiriTrackerWidgetStyle.cs:28 — Content/LegendWeapon/OnikiriLegend/TrialQuests/OnikiriTrackerWidgetStyle.cs:28-67 | Content/LegendWeapon/SHPCLegend/TrialQuests/SHPCTrackerWidgetStyle.cs:41-78 | Content/Scenarios/Draedon/Quest/DraedonTrackerWidgetStyle.cs:40-88 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 38 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (79 corresponding lines) · ×2
  • Edited copy of a member (79 corresponding lines) Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryWatcher.cs:115 — Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryWatcher.cs:115-193 | Content/Scenarios/Dungeonworld/Gen/BossRooms/ProofingHallWatcher.cs:85-166 — These two members are one piece of code written twice and then edited apart: 79 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (79 corresponding lines) Content/Scenarios/Shepel/CybCourses/HackTimeTutorialLead.cs:228 — Content/Scenarios/Shepel/CybCourses/HackTimeTutorialLead.cs:228-309 | Content/Scenarios/Shepel/CybCourses/WheelTutorialLead.cs:156-234 — These two members are one piece of code written twice and then edited apart: 79 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (58 corresponding lines) · ×2
  • Edited copy of a member (58 corresponding lines) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismDashingState.cs:42 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismDashingState.cs:42-99 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismPhase2DashingState.cs:45-111 — These two members are one piece of code written twice and then edited apart: 58 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (58 corresponding lines) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:22 — Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetRender.cs:22-80 | Content/Scenarios/Kiame/Overlay/OniRainDescentRender.cs:48-105 — These two members are one piece of code written twice and then edited apart: 58 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 37+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 37+ corresponding lines) Content/Items/Tools/EncyclopediaofOceanicKnowledge.cs:446 — Content/Items/Tools/EncyclopediaofOceanicKnowledge.cs:446-482 | Content/LegendWeapon/HalibutLegend/DomainSkills/SeaDomain.cs:635-689 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutDomain.cs:287-329 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 37 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 37+ corresponding lines) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1641 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1641-1679 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1310-1347 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1507-1543 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 37 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 41+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 41+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:373 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:373-415 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:535-583 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:375-415 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 41 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 41+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsCrossDashState.cs:53 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsCrossDashState.cs:53-101 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsScissorRayState.cs:57-97 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsTetherSweepState.cs:58-99 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 41 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 36+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 36+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:788 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:788-824 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:869-905 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1044-1080 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:784-819 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 36 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 36+ corresponding lines) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:240 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:240-275 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs:265-307 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs:249-291 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconUI.cs:218-264 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 36 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 42+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 42+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:459 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:459-508 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:544-593 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:497-542 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:453-494 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 42 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 42+ corresponding lines) Content/NPCs/BloomsandSerpents/BssHead.cs:590 — Content/NPCs/BloomsandSerpents/BssHead.cs:590-633 | Content/NPCs/BrutalNPCs/BrutalDestroyer/DestroyerHeadAI.cs:234-275 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/EowHeadAI.cs:383-426 | Content/NPCs/FestersandSerpents/FssHead.cs:531-574 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 42 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 23+ corresponding lines) · ×2
  • Edited copies of one member (5 members, 23+ corresponding lines) Content/Items/Modifys/RBloodButcherer.cs:1019 — Content/Items/Modifys/RBloodButcherer.cs:1019-1044 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunBullet.cs:262-288 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:245-270 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemEyeSpit.cs:107-129 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemMagmaBall.cs:316-347 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 23+ corresponding lines) Content/QuestLogs/QLNodes/CalamityMaterialQuests.cs:175 — Content/QuestLogs/QLNodes/CalamityMaterialQuests.cs:175-197 | Content/QuestLogs/QLNodes/CalamityMaterialQuests.cs:209-231 | Content/QuestLogs/QLNodes/CalamityMaterialQuests.cs:243-269 | Content/QuestLogs/QLNodes/CalamityMaterialQuests.cs:281-303 | Content/QuestLogs/QLNodes/CalamityMaterialQuests.cs:317-342 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 34+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 34+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:497 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:497-530 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:495-536 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:460-493 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:493-526 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 34 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 34+ corresponding lines) Content/Industrials/ElectricPowers/Apiaries/ApiaryStorageProvider.cs:136 — Content/Industrials/ElectricPowers/Apiaries/ApiaryStorageProvider.cs:136-169 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherStorageProvider.cs:135-168 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerStorageProvider.cs:135-168 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconStorageProvider.cs:138-171 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 34 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 28+ corresponding lines) · ×2
  • Edited copies of one member (6 members, 28+ corresponding lines) Content/EntrustManager/Styles/DraedonManagerStyle.cs:103 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:103-130 | Content/EntrustManager/Styles/ForestManagerStyle.cs:102-129 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:98-125 | Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:64-94 | Content/QuestLogs/Styles/ForestQuestLogStyle.cs:67-96 | Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:30-59 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 28 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 28+ corresponding lines) Content/Items/Melee/DestroyersBlade.cs:163 — Content/Items/Melee/DestroyersBlade.cs:163-197 | Content/Items/Melee/DragonsScaleGreatsword.cs:179-206 | Content/Items/Melee/EnergySword.cs:193-220 | Content/Items/Melee/RebelBlade.cs:217-247 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:198-229 | Content/Items/Stones/Marbles/MarbleHuntingKnife.cs:140-169 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 28 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 21+ corresponding lines) · ×2
  • Edited copies of one member (5 members, 21+ corresponding lines) Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgSnowShardProj.cs:77 — Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgSnowShardProj.cs:77-100 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmIceShardProj.cs:65-85 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmSnowballProj.cs:107-130 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesIceShardProj.cs:66-86 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandPelletProj.cs:73-93 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 21+ corresponding lines) Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2Scatter.cs:82 — Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2Scatter.cs:82-102 | Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Scatter.cs:189-209 | Content/Scenarios/Dungeonworld/Gen/Layers/L4/L4Scatter.cs:135-156 | Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Scatter.cs:148-169 | Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Scatter.cs:128-148 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 26+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 26+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishDirtParticles.cs:113 — Content/LegendWeapon/HalibutLegend/FishSkills/FishDirtParticles.cs:113-138 | Content/LegendWeapon/HalibutLegend/FishSkills/FishEaterofPlanktonVFX.cs:139-172 | Content/LegendWeapon/HalibutLegend/FishSkills/FishHungerVFX.cs:203-236 | Content/PRTTypes/PRT_GraniteShard.cs:52-78 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 26 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 26+ corresponding lines) Content/GameModes/BrutalMobs/FrostLegion/FrostLegionNPC.cs:345 — Content/GameModes/BrutalMobs/FrostLegion/FrostLegionNPC.cs:345-370 | Content/GameModes/BrutalMobs/FrostMoon/FrmMeleeNPC.cs:268-297 | Content/GameModes/BrutalMobs/FrostMoon/FrmSiegeNPC.cs:197-223 | Content/GameModes/BrutalMobs/Graveyard/GraveyardBrutalNPC.cs:278-303 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 26 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 24+ corresponding lines) · ×2
  • Edited copies of one member (5 members, 24+ corresponding lines) Content/GameModes/BrutalMobs/FrostLegion/FrostLegionNPC.cs:406 — Content/GameModes/BrutalMobs/FrostLegion/FrostLegionNPC.cs:406-432 | Content/GameModes/BrutalMobs/FrostLegion/FrostLegionNPC.cs:551-575 | Content/GameModes/BrutalMobs/Graveyard/GraveyardBrutalNPC.cs:334-359 | Content/GameModes/BrutalMobs/Graveyard/GraveyardBrutalNPC.cs:488-511 | Content/GameModes/BrutalMobs/Sky/SkyBrutalNPC.cs:316-340 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 24+ corresponding lines) Content/QuestLogs/QLNodes/AdventurerQuests.cs:92 — Content/QuestLogs/QLNodes/AdventurerQuests.cs:92-115 | Content/QuestLogs/QLNodes/AdventurerQuests.cs:189-212 | Content/QuestLogs/QLNodes/AdventurerQuests.cs:256-279 | Content/QuestLogs/QLNodes/AdventurerQuests.cs:670-693 | Content/QuestLogs/QLNodes/AdventurerQuests.cs:839-862 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 18+ corresponding lines) · ×2
  • Edited copies of one member (5 members, 18+ corresponding lines) Content/Items/Ranged/NeutronBows/NeutronBow.cs:254 — Content/Items/Ranged/NeutronBows/NeutronBow.cs:254-271 | Content/Items/Ranged/NeutronBows/NeutronBow.cs:274-294 | Content/Items/Ranged/Thornstrings/ThornstringHeld.cs:192-212 | Content/Items/Ranged/Undertows/UndertowHeld.cs:177-195 | Content/Items/Ranged/Undertows/UndertowHeld.cs:198-218 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 18+ corresponding lines) Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryRoom.cs:423 — Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryRoom.cs:423-440 | Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2EscapeTunnel.cs:387-406 | Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2Palette.cs:65-84 | Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Palette.cs:72-91 | Content/Scenarios/Dungeonworld/Gen/Layers/L7/L7Style.cs:67-92 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 16+ corresponding lines) · ×2
  • Edited copies of one member (8 members, 16+ corresponding lines) Content/Industrials/ElectricPowers/MiningMachines/MiningMachineMk2.cs:27 — Content/Industrials/ElectricPowers/MiningMachines/MiningMachineMk2.cs:27-42 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuter.cs:14-29 | Content/Industrials/Generator/Hydroelectrics/Hydroelectric.cs:25-40 | Content/Industrials/Generator/Hydroelectrics/HydroelectricMK2.cs:24-39 | Content/Industrials/Generator/SolarPanels/SolarPanelMK2.cs:23-38 | Content/Industrials/Generator/Thermal/ThermalGeneratorMK2.cs:20-35 | Content/Industrials/Generator/WindGriven/WindGrivenGeneratorMk2.cs:31-46 | Content/Industrials/MaterialFlow/Batterys/CapacitorMatrix.cs:29-44 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
  • Edited copies of one member (8 members, 16+ corresponding lines) Content/QuestLogs/QLNodes/IndustrialExpansionQuests.cs:153 — Content/QuestLogs/QLNodes/IndustrialExpansionQuests.cs:153-169 | Content/QuestLogs/QLNodes/IndustrialExpansionQuests.cs:239-256 | Content/QuestLogs/QLNodes/IndustrialExpansionQuests.cs:409-424 | Content/QuestLogs/QLNodes/IndustrialExpansionQuests.cs:435-451 | Content/QuestLogs/QLNodes/IndustrialExpansionQuests.cs:462-477 | Content/QuestLogs/QLNodes/IndustrialExpansionQuests.cs:569-584 | Content/QuestLogs/QLNodes/IndustrialExpansionQuests.cs:595-611 | Content/QuestLogs/QLNodes/IndustrialExpansionQuests.cs:622-637 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 16+ corresponding lines) · ×2
  • Edited copies of one member (7 members, 16+ corresponding lines) Content/Items/Stones/Granites/GraniteFlower.cs:22 — Content/Items/Stones/Granites/GraniteFlower.cs:22-38 | Content/Items/Stones/Granites/GraniteThrowingKnife.cs:20-35 | Content/Items/Stones/Granites/GraniteTome.cs:22-39 | Content/Items/Stones/Marbles/MarbleClub.cs:25-43 | Content/Items/Stones/Marbles/MarbleDisc.cs:20-35 | Content/Items/Stones/Marbles/MarbleHuntingKnife.cs:24-42 | Content/Items/Stones/Marbles/MarblePebble.cs:19-34 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
  • Edited copies of one member (7 members, 16+ corresponding lines) Content/QuestLogs/QLNodes/BossQuests.cs:551 — Content/QuestLogs/QLNodes/BossQuests.cs:551-566 | Content/QuestLogs/QLNodes/CalamityHuntQuests.cs:176-192 | Content/QuestLogs/QLNodes/CalamityHuntQuests.cs:205-221 | Content/QuestLogs/QLNodes/CalamityHuntQuests.cs:234-250 | Content/QuestLogs/QLNodes/CalamityHuntQuests.cs:263-279 | Content/QuestLogs/QLNodes/VanillaSideQuests.cs:41-58 | Content/QuestLogs/QLNodes/VanillaSideQuests.cs:69-86 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 12+ corresponding lines) · ×2
  • Edited copies of one member (7 members, 12+ corresponding lines) Content/LegendWeapon/HalibutLegend/UI/HalibutUIParticles.cs:76 — Content/LegendWeapon/HalibutLegend/UI/HalibutUIParticles.cs:76-87 | Content/LegendWeapon/OnikiriLegend/UI/OniUIParticles.cs:66-79 | Content/LegendWeapon/OnikiriLegend/UI/OniUIParticles.cs:82-93 | Content/LegendWeapon/OnikiriLegend/UI/OniUIParticles.cs:116-127 | Content/LegendWeapon/OnikiriLegend/UI/OniUIParticles.cs:130-142 | Content/LegendWeapon/OnikiriLegend/UI/OniUIParticles.cs:145-158 | Content/LegendWeapon/OnikiriLegend/UI/OniUIParticles.cs:161-172 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
  • Edited copies of one member (7 members, 12+ corresponding lines) Content/Industrials/ElectricPowers/Apiaries/ApiaryTile.cs:78 — Content/Industrials/ElectricPowers/Apiaries/ApiaryTile.cs:78-89 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherTile.cs:78-89 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerTile.cs:78-89 | Content/Industrials/ElectricPowers/Launchers/PlayerLauncherTile.cs:88-99 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTile.cs:78-89 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconTile.cs:79-90 | Content/Industrials/ElectricPowers/TeleportStations/TeleportStationTile.cs:86-97 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 18+ corresponding lines) · ×2
  • Edited copies of one member (7 members, 18+ corresponding lines) Content/NPCs/BloomsandSerpents/BssHead.cs:170 — Content/NPCs/BloomsandSerpents/BssHead.cs:170-191 | Content/NPCs/FestersandSerpents/FssHead.cs:154-174 | Content/NPCs/ScrapCommanders/ScrapCommander.cs:136-153 | Content/NPCs/SeaShrimp/SeaShrimpBoss.cs:63-80 | Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:257-274 | Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:231-249 | Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:277-295 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
  • Edited copies of one member (7 members, 18+ corresponding lines) Content/QuestLogs/QLNodes/CalamityMaterialQuests.cs:365 — Content/QuestLogs/QLNodes/CalamityMaterialQuests.cs:365-382 | Content/QuestLogs/QLNodes/IndustrialQuests.cs:228-248 | Content/QuestLogs/QLNodes/IndustrialQuests.cs:259-276 | Content/QuestLogs/QLNodes/IndustrialQuests.cs:287-304 | Content/QuestLogs/QLNodes/IndustrialQuests.cs:315-335 | Content/QuestLogs/QLNodes/IndustrialQuests.cs:346-366 | Content/QuestLogs/QLNodes/IndustrialQuests.cs:377-397 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 15+ corresponding lines) · ×2
  • Edited copies of one member (7 members, 15+ corresponding lines) Content/GameModes/BrutalMobs/Ambience/Rainveil/Projectiles/RainveilThunderboltProj.cs:180 — Content/GameModes/BrutalMobs/Ambience/Rainveil/Projectiles/RainveilThunderboltProj.cs:180-194 | Content/GameModes/BrutalMobs/Ambience/Rotmire/Projectiles/RotmireVentProj.cs:170-187 | Content/GameModes/BrutalMobs/Ambience/Starfall/Projectiles/StarfallAfterburstProj.cs:191-209 | Content/GameModes/BrutalMobs/Ambience/Stonewake/Projectiles/StonewakeGazePillarProj.cs:176-193 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkRootSpikeProj.cs:151-168 | Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilSurgeColumnProj.cs:170-187 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandGeyserProj.cs:151-169 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
  • Edited copies of one member (7 members, 15+ corresponding lines) Content/GameModes/BrutalMobs/Ambience/Astralveil/AstralveilSpearDirector.cs:190 — Content/GameModes/BrutalMobs/Ambience/Astralveil/AstralveilSpearDirector.cs:190-204 | Content/GameModes/BrutalMobs/Ambience/Frostveil/FrostveilGaleScheduler.cs:115-129 | Content/GameModes/BrutalMobs/Ambience/Prismglade/PrismgladeAmbience.cs:218-232 | Content/GameModes/BrutalMobs/FrostLegion/FrostLegionNPC.cs:266-280 | Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomVineWhipProj.cs:127-141 | Content/GameModes/BrutalMobs/Sandveil/SandveilBrutalNPC.cs:239-253 | Content/GameModes/BrutalMobs/Wastes/WastesBrutalNPC.cs:182-196 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 6+ corresponding lines) · ×2
  • Edited copies of one member (7 members, 6+ corresponding lines) Content/Scenarios/Shenyo/Gifts/ShenyoCultistGift.cs:26 — Content/Scenarios/Shenyo/Gifts/ShenyoCultistGift.cs:26-31 | Content/Scenarios/Shenyo/Gifts/ShenyoDukeFishronGift.cs:26-31 | Content/Scenarios/Shenyo/Gifts/ShenyoExoAndSCalGift.cs:26-31 | Content/Scenarios/Shenyo/Gifts/ShenyoGolemGift.cs:26-31 | Content/Scenarios/Shenyo/Gifts/ShenyoMechsGift.cs:26-31 | Content/Scenarios/Shenyo/Gifts/ShenyoQueenSlimeGift.cs:26-31 | Content/Scenarios/Shenyo/Gifts/ShenyoWallOfFleshGift.cs:26-31 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
  • Edited copies of one member (7 members, 6+ corresponding lines) Content/HackTimes/PvP/Protocols/ChannelScramble.cs:91 — Content/HackTimes/PvP/Protocols/ChannelScramble.cs:91-96 | Content/HackTimes/PvP/Protocols/ChannelScrambleChatHook.cs:211-216 | Content/HackTimes/PvP/Protocols/GaugePollution.cs:170-175 | Content/HackTimes/PvP/Protocols/MapBlackoutRenderer.cs:122-127 | Content/NPCs/TBUGs/TBUGRiftPortalProj.cs:385-390 | Content/PRTTypes/PRT_BanishGlitch.cs:106-111 | Content/PRTTypes/PRT_TBUGGlitch.cs:101-106 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 8+ corresponding lines) · ×2
  • Edited copies of one member (7 members, 8+ corresponding lines) Content/PRTTypes/PRT_DragonsWordCut.cs:45 — Content/PRTTypes/PRT_DragonsWordCut.cs:45-53 | Content/PRTTypes/PRT_HeavenfallStar.cs:36-46 | Content/PRTTypes/PRT_Line.cs:43-50 | Content/PRTTypes/PRT_Line_FormPlayer.cs:37-44 | Content/PRTTypes/PRT_LonginusStar.cs:57-66 | Content/PRTTypes/PRT_Spark.cs:47-57 | Content/PRTTypes/PRT_SparkAlpha.cs:43-53 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
  • Edited copies of one member (7 members, 8+ corresponding lines) Content/GameModes/GodSmith/Weapons/Guns/GsXenopopper.cs:90 — Content/GameModes/GodSmith/Weapons/Guns/GsXenopopper.cs:90-98 | Content/GameModes/GodSmith/Weapons/MagicMorph/Projectiles/GsRiftProj.cs:23-32 | Content/GameModes/GodSmith/Weapons/Throwing/Projectiles/GsZoneProj.cs:38-47 | Content/Items/Accessories/BrutalRelics/EyeOfCthulhu/BloodfogVeilProj.cs:122-132 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMirrorPhantom.cs:34-42 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteStarSurge.cs:32-40 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteVeilRift.cs:27-34 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 9+ corresponding lines) · ×2
  • Edited copies of one member (7 members, 9+ corresponding lines) Content/Cyberwares/Implementation/OmniElectricFoots/OmniElectricFootHUD.cs:282 — Content/Cyberwares/Implementation/OmniElectricFoots/OmniElectricFootHUD.cs:282-290 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaHandRig.cs:277-286 | Content/LegendWeapon/OnikiriLegend/OniOmokages/OniOmokageRender.cs:669-679 | Content/LegendWeapon/SHPCLegend/Modules/Stock/BraceStockModule.cs:416-424 | Content/LegendWeapon/SHPCLegend/UI/SHPCRenderer.cs:39-47 | Content/Scenarios/Draedon/PQCDs/DraedonCallUI.cs:358-367 | Content/UIs/UIEffect/SvgPathPen.cs:162-170 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
  • Edited copies of one member (7 members, 9+ corresponding lines) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:2000 — Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:2000-2008 | Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:1208-1216 | Content/Scenarios/Dungeonworld/NPCs/GaolDormantSkull.cs:211-219 | Content/Scenarios/Dungeonworld/NPCs/OverseerDormantRig.cs:300-308 | Content/Scenarios/Dungeonworld/NPCs/OverseerPressStrike.cs:194-202 | Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:1724-1732 | Content/Scenarios/Dungeonworld/NPCs/UndrownedThrone.cs:296-304 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 7+ corresponding lines) · ×2
  • Edited copies of one member (7 members, 7+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Core/BrainMotion.cs:25 — Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Core/BrainMotion.cs:25-31 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Core/EmpressMotion.cs:49-55 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Core/EocMotion.cs:33-39 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Core/CultistMotion.cs:99-105 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Core/TwinsMotion.cs:21-27 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Core/QueenBeeMotion.cs:24-30 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Core/QueenMotion.cs:59-65 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
  • Edited copies of one member (7 members, 7+ corresponding lines) Content/Items/Melee/Shatterfangs/ShatterfangFX.cs:70 — Content/Items/Melee/Shatterfangs/ShatterfangFX.cs:70-76 | Content/Items/Ranged/PallbearerAssets.cs:45-51 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBloodyManowarVFX.cs:38-44 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCursedVFX.cs:33-39 | Content/LegendWeapon/HalibutLegend/FishSkills/FishFallenStarVFX.cs:40-46 | Content/LegendWeapon/HalibutLegend/FishSkills/FishJewelVFX.cs:67-73 | Content/LegendWeapon/HalibutLegend/FishSkills/FishPrismiteVFX.cs:59-65 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 1+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 1+ corresponding lines) Content/Industrials/MaterialFlow/Fluids/FluidPipeline.cs:106 — Content/Industrials/MaterialFlow/Fluids/FluidPipeline.cs:106-106 | Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs:75-75 | Content/Industrials/MaterialFlow/Pipelines/UEPipeline.cs:116-116 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 1+ corresponding lines) Content/LegendWeapon/OnikiriLegend/UI/OniMeiCodexRenderer.cs:629 — Content/LegendWeapon/OnikiriLegend/UI/OniMeiCodexRenderer.cs:629-629 | Content/Scenarios/Dungeonworld/Gen/Layers/L1/L1Content.cs:249-249 | Content/Scenarios/Dungeonworld/Gen/Passes/LayerPlanPass.cs:105-105 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (50 lines × 2) · ×2
  • Duplicated block (50 lines × 2) Content/MainMenus/Himayo/HimayoMenuButtons.cs:61 — Content/MainMenus/Himayo/HimayoMenuButtons.cs:61-110 | Content/MainMenus/Shenyo/ShenyoMenuButtons.cs:63-112 — before extracting anything, compare `Content/MainMenus/Himayo/HimayoMenuButtons.cs` and `Content/MainMenus/Shenyo/ShenyoMenuButtons.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 174 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (50 lines × 2) Content/Scenarios/Himayo/ToriiShrines/ToriiShrineLocationFinder.cs:149 — Content/Scenarios/Himayo/ToriiShrines/ToriiShrineLocationFinder.cs:149-198 | Content/Scenarios/Kiame/Overlay/OniUmbrellaWorldSpawn.cs:374-423 — before extracting anything, compare `Content/Scenarios/Himayo/ToriiShrines/ToriiShrineLocationFinder.cs` and `Content/Scenarios/Kiame/Overlay/OniUmbrellaWorldSpawn.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 117 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (40 lines × 2) · ×2
  • Duplicated block (40 lines × 2) Content/Scenarios/Kiame/Backgrounds/KiameSky.cs:90 — Content/Scenarios/Kiame/Backgrounds/KiameSky.cs:90-129 | Content/Scenarios/Kiame/Overlay/OniRainWorldSky.cs:92-131 — before extracting anything, compare `Content/Scenarios/Kiame/Backgrounds/KiameSky.cs` and `Content/Scenarios/Kiame/Overlay/OniRainWorldSky.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Kiame/Backgrounds/KiameSky.cs:90` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (40 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:195 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:195-234 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterGlob.cs:171-210 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterGlob.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 117 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:195` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (39 lines × 2) · ×2
  • Duplicated block (39 lines × 2) Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:639 — Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:639-677 | Content/Items/Melee/WeaverGrievanceses/WGManifestationActor.cs:534-572 — before extracting anything, compare `Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs` and `Content/Items/Melee/WeaverGrievanceses/WGManifestationActor.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 237 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (39 lines × 2) Content/Scenarios/Himayo/Gifts/HimayoGiftNarrativeTracker.cs:180 — Content/Scenarios/Himayo/Gifts/HimayoGiftNarrativeTracker.cs:180-219 | Content/Scenarios/Shenyo/Gifts/ShenyoGiftNarrativeTracker.cs:173-211 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (36–37 lines × 2) · ×2
  • Duplicated block (36–37 lines × 2) Content/Items/Summon/AzureDragonRage.cs:112 — Content/Items/Summon/AzureDragonRage.cs:112-147 | Content/Items/Summon/BleedingScourge.cs:95-131 — before extracting anything, compare `Content/Items/Summon/AzureDragonRage.cs` and `Content/Items/Summon/BleedingScourge.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 93 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (36–37 lines × 2) Content/NPCs/BloomsandSerpents/BssPortrait.cs:161 — Content/NPCs/BloomsandSerpents/BssPortrait.cs:161-197 | Content/NPCs/FestersandSerpents/Rendering/FssPortrait.cs:233-268 — before extracting anything, compare `Content/NPCs/BloomsandSerpents/BssPortrait.cs` and `Content/NPCs/FestersandSerpents/Rendering/FssPortrait.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 108 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BloomsandSerpents/BssPortrait.cs:161` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (36 lines × 2) · ×2
  • Duplicated block (36 lines × 2) Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSim.cs:104 — Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSim.cs:104-139 | Content/Scenarios/Kiyume/Fog/KiyumeFogSim.cs:174-209 — before extracting anything, compare `Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSim.cs` and `Content/Scenarios/Kiyume/Fog/KiyumeFogSim.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 174 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSim.cs:104` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (36 lines × 2) Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:551 — Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:551-586 | Content/Scenarios/Kiyume/UI/KiyumeLoadingScreen.cs:491-526 — before extracting anything, compare `Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs` and `Content/Scenarios/Kiyume/UI/KiyumeLoadingScreen.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 214 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Scenarios/Kiyume/UI/KiyumeLoadingScreen.cs:486` calls `CenterRect` and `Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:547` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (32–33 lines × 3) · ×2
  • Duplicated block (32–33 lines × 3) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:772 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:772-804 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:572-603 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:725-757 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `action` to `ActiveSlash` in one and `ActiveRift` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:809` calls `DecaySmears` and `Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:765` 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 (32–33 lines × 3) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1452 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1452-1484 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1169-1200 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1361-1393 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1452` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (30 lines × 2) · ×2
  • Duplicated block (30 lines × 2) Content/Items/Melee/Arbiters/ArbiterManifestationRenderer.cs:93 — Content/Items/Melee/Arbiters/ArbiterManifestationRenderer.cs:93-122 | Content/Items/Melee/WeaverGrievanceses/WGMaterializationRenderer.cs:78-107 — before extracting anything, compare `Content/Items/Melee/Arbiters/ArbiterManifestationRenderer.cs` and `Content/Items/Melee/WeaverGrievanceses/WGMaterializationRenderer.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Arbiters/ArbiterManifestationRenderer.cs:93` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (30 lines × 2) Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs:393 — Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs:393-422 | Content/Scenarios/Shenyo/ShenyoPortraitRainRenderer.cs:389-418 — before extracting anything, compare `Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs` and `Content/Scenarios/Shenyo/ShenyoPortraitRainRenderer.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 211 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs:393` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (30–31 lines × 2) · ×2
  • Duplicated block (30–31 lines × 2) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:286 — Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:286-315 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaReset.cs:309-339 — before extracting anything, compare `Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs` and `Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaReset.cs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (30–31 lines × 2) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberShockwaveProj.cs:75 — Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberShockwaveProj.cs:75-104 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberFreezeWaveProj.cs:68-98 — before extracting anything, compare `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberShockwaveProj.cs` and `Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberFreezeWaveProj.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberShockwaveProj.cs:75` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (29 lines × 2) · ×2
  • Duplicated block (29 lines × 2) Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:508 — Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:508-536 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:808-836 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:508` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (29 lines × 2) Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:319 — Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:319-347 | Content/Items/Melee/NeutronGlaive.cs:325-353 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:319` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Melee/NeutronGlaive.cs:323` calls `Sin` and `Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:318` 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.
D4 · Code Duplication · Duplicated block (26 lines × 3) · ×2
  • Duplicated block (26 lines × 3) Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:51 — Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:51-76 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:53-78 | Content/Industrials/ElectricPowers/Recyclers/RecyclerUI.cs:50-75 — before extracting anything, compare `Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs` and `Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 303 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (26 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaMinionDrownFX.cs:484 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaMinionDrownFX.cs:484-509 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaPlayerDrownFX.cs:520-545 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaScourgeFX.cs:781-806 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaMinionDrownFX.cs:484` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (30 lines × 3) · ×2
  • Duplicated block (30 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:688 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:688-717 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:650-679 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:683-712 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs` as WHOLE FILES: this scan already matched 78 separate duplicated blocks between them, totalling at least 968 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:688` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:718` calls `Min` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:713` does not — after which the two agree again for 4 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 (30 lines × 3) Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:107 — Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:107-136 | Content/Scenarios/Kiame/Overlay/OniRainExitTransition.cs:70-99 | Content/Scenarios/Kiame/Overlay/OniRainWorldTransition.cs:102-131 — before extracting anything, compare `Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs` and `Content/Scenarios/Kiame/Overlay/OniRainExitTransition.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 186 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.
D4 · Code Duplication · Duplicated block (28–30 lines × 2) · ×2
  • Duplicated block (28–30 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:563 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:563-590 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:622-651 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs` as WHOLE FILES: this scan already matched 66 separate duplicated blocks between them, totalling at least 737 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:563` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (28–30 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:373 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:373-402 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:375-402 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs` as WHOLE FILES: this scan already matched 70 separate duplicated blocks between them, totalling at least 835 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:373` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (26–28 lines × 2) · ×2
  • Duplicated block (26–28 lines × 2) Content/Cyberwares/Skills/CyberwareSkillRadialController.cs:288 — Content/Cyberwares/Skills/CyberwareSkillRadialController.cs:288-315 | Content/LegendWeapon/HalibutLegend/UI/SkillWheel/HalibutWheelController.cs:142-167 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Cyberwares/Skills/CyberwareSkillRadialController.cs:288` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (26–28 lines × 2) Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs:174 — Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs:174-201 | Content/LegendWeapon/SHPCLegend/UI/DomainWheel/SHPCDomainWheelUI.cs:165-190 — before extracting anything, compare `Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs` and `Content/LegendWeapon/SHPCLegend/UI/DomainWheel/SHPCDomainWheelUI.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs:174` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs:174` calls `ResolveAnchor` and `Content/LegendWeapon/SHPCLegend/UI/DomainWheel/SHPCDomainWheelUI.cs:165` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (27–28 lines × 2) · ×2
  • Duplicated block (27–28 lines × 2) Content/Items/Accessories/EmblemOfDread.cs:140 — Content/Items/Accessories/EmblemOfDread.cs:140-166 | Content/Items/Accessories/EyeOfSingularity.cs:96-123 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/EmblemOfDread.cs:140` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (27–28 lines × 2) Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:211 — Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:211-237 | Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:140-167 — before extracting anything, compare `Content/QuestLogs/Styles/DraedonQuestLogStyle.cs` and `Content/QuestLogs/Styles/HotwindQuestLogStyle.cs` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 377 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.
D4 · Code Duplication · Duplicated block (26–27 lines × 2) · ×2
  • Duplicated block (26–27 lines × 2) Content/Items/Accessories/BrutalRelics/KingSlime/FallenCrownProj.cs:227 — Content/Items/Accessories/BrutalRelics/KingSlime/FallenCrownProj.cs:227-252 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSCrownProj.cs:464-490 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/KingSlime/FallenCrownProj.cs:227` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (26–27 lines × 2) Content/Items/Melee/DivineSourceBlades/DivineSourceWaveProjectile.cs:227 — Content/Items/Melee/DivineSourceBlades/DivineSourceWaveProjectile.cs:227-252 | Content/Items/Melee/NeutronGlaive.cs:922-948 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (25 lines × 3) · ×2
  • Duplicated block (25 lines × 3) Content/EntrustManager/Styles/DraedonManagerStyle.cs:106 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:106-130 | Content/EntrustManager/Styles/ForestManagerStyle.cs:105-129 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:101-125 — before extracting anything, compare `Content/EntrustManager/Styles/DraedonManagerStyle.cs` and `Content/EntrustManager/Styles/ForestManagerStyle.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 334 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/EntrustManager/Styles/DraedonManagerStyle.cs:106` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (25 lines × 3) Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:70 — Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:70-94 | Content/QuestLogs/Styles/ForestQuestLogStyle.cs:72-96 | Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:35-59 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:70` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (24 lines × 5) · ×2
  • Duplicated block (24 lines × 5) Content/Scenarios/Dungeonworld/DungeonworldGuard.cs:78 — Content/Scenarios/Dungeonworld/DungeonworldGuard.cs:78-101 | Content/Scenarios/Hadalworld/HadalworldGuard.cs:78-101 | Content/Scenarios/Kiame/KiameGuard.cs:78-101 | Content/Scenarios/Kiyume/KiyumeGuard.cs:78-101 | Content/Scenarios/OldNet/OldNetGuard.cs:78-101 — before extracting anything, compare `Content/Scenarios/Dungeonworld/DungeonworldGuard.cs` and `Content/Scenarios/Hadalworld/HadalworldGuard.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/DungeonworldGuard.cs:78` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (24 lines × 5) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:161 — Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:161-184 | Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:142-165 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:148-171 | Content/Industrials/ElectricPowers/Recyclers/RecyclerUI.cs:143-166 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterUI.cs:146-169 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:185` calls `RebuildCandidates` and `Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterUI.cs:170` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (24–25 lines × 3) · ×2
  • Duplicated block (24–25 lines × 3) Content/Items/Accessories/Proverbs.cs:243 — Content/Items/Accessories/Proverbs.cs:243-267 | Content/Items/Magic/Pandemoniums/PandemoniumCircle.cs:322-345 | Content/Items/Magic/Pandemoniums/PandemoniumRSkill.cs:455-479 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/Proverbs.cs:243` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (24–25 lines × 3) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1793 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1793-1817 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1462-1485 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1658-1682 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1793` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (4–24 lines × 3) · ×2
  • Duplicated block (4–24 lines × 3) Content/Items/Melee/Arbiters/Arbiter.cs:931 — Content/Items/Melee/Arbiters/Arbiter.cs:931-952 | Content/Items/Melee/Arbiters/Arbiter.cs:959-962 | Content/Items/Melee/Arbiters/Arbiter.cs:973-996 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Arbiters/Arbiter.cs:931` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (4–24 lines × 3) Content/Items/Melee/CommandersChainsaw.cs:111 — Content/Items/Melee/CommandersChainsaw.cs:111-134 | Content/Items/Melee/CommandersChainsaw.cs:175-178 | Content/Items/Melee/CommandersChainsaw.cs:208-231 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/CommandersChainsaw.cs:175` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (19–22 lines × 2) · ×2
  • Duplicated block (19–22 lines × 2) Content/Cyberwares/Implementation/Sandevistans/SandevistanRender.cs:37 — Content/Cyberwares/Implementation/Sandevistans/SandevistanRender.cs:37-58 | Content/Scenarios/OldNet/Renders/OldNetGradeRender.cs:38-56 — before extracting anything, compare `Content/Cyberwares/Implementation/Sandevistans/SandevistanRender.cs` and `Content/Scenarios/OldNet/Renders/OldNetGradeRender.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Cyberwares/Implementation/Sandevistans/SandevistanRender.cs:37` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (19–22 lines × 2) Content/Items/Melee/StormGoddessSpears/StormLightning.cs:275 — Content/Items/Melee/StormGoddessSpears/StormLightning.cs:275-296 | Content/Projectiles/Lightning.cs:180-198 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (20 lines × 3) · ×2
  • Duplicated block (20 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:531 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:531-550 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:735-754 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:420-439 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs` as WHOLE FILES: this scan already matched 48 separate duplicated blocks between them, totalling at least 508 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:531` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 3) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1771 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1771-1790 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1440-1459 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1636-1655 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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.
D4 · Code Duplication · Duplicated block (18–21 lines × 2) · ×2
  • Duplicated block (18–21 lines × 2) Content/LegendWeapon/HalibutLegend/DomainSkills/SeaDomain.cs:669 — Content/LegendWeapon/HalibutLegend/DomainSkills/SeaDomain.cs:669-689 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutDomain.cs:312-329 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/DomainSkills/SeaDomain.cs:669` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18–21 lines × 2) Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraFrenzyPounceState.cs:132 — Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraFrenzyPounceState.cs:132-149 | Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraGrapplePounceState.cs:140-160 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraFrenzyPounceState.cs` and `Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraGrapplePounceState.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 70 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraFrenzyPounceState.cs:132` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraGrapplePounceState.cs:163` calls `PlaySound` and `Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraFrenzyPounceState.cs:150` 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.
D4 · Code Duplication · Duplicated block (19–21 lines × 2) · ×2
  • Duplicated block (19–21 lines × 2) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:325 — Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:325-343 | Content/LegendWeapon/SHPCLegend/UI/SHPCModuleSelectPanel.cs:342-362 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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 (19–21 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:322 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:322-340 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:289-309 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:322` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (17 lines × 5) · ×2
  • Duplicated block (17 lines × 5) Content/Items/Melee/DestroyersBlade.cs:170 — Content/Items/Melee/DestroyersBlade.cs:170-186 | Content/Items/Melee/DragonsScaleGreatsword.cs:186-202 | Content/Items/Melee/EnergySword.cs:200-216 | Content/Items/Melee/RebelBlade.cs:227-243 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:205-221 — before extracting anything, compare `Content/Items/Melee/DestroyersBlade.cs` and `Content/Items/Melee/DragonsScaleGreatsword.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 419 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DestroyersBlade.cs:170` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 5) Content/Items/Summon/AzureDragonRage.cs:93 — Content/Items/Summon/AzureDragonRage.cs:93-109 | Content/Items/Summon/BleedingScourge.cs:76-92 | Content/Items/Summon/ElementWhip.cs:83-99 | Content/Items/Summon/GhostFireWhip.cs:89-105 | Content/Items/Summon/WhiplashGalactica.cs:98-114 — before extracting anything, compare `Content/Items/Summon/AzureDragonRage.cs` and `Content/Items/Summon/BleedingScourge.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 93 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.
D4 · Code Duplication · Duplicated block (19–20 lines × 5) · ×2
  • Duplicated block (19–20 lines × 5) Content/Items/Melee/DestroyersBlade.cs:444 — Content/Items/Melee/DestroyersBlade.cs:444-463 | Content/Items/Melee/DragonsScaleGreatsword.cs:470-489 | Content/Items/Melee/EnergySword.cs:481-499 | Content/Items/Melee/RebelBlade.cs:507-526 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:452-471 — before extracting anything, compare `Content/Items/Melee/DestroyersBlade.cs` and `Content/Items/Melee/DragonsScaleGreatsword.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 419 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DestroyersBlade.cs:444` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Melee/DragonsScaleGreatsword.cs:468` calls `OnHitPlayer`, `AddBuff` and `Content/Items/Melee/DestroyersBlade.cs:442` 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 (19–20 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:503 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:503-521 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:509-527 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:903-922 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:467-485 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:499-517 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs` as WHOLE FILES: this scan already matched 75 separate duplicated blocks between them, totalling at least 912 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:503` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (18 lines × 4) · ×2
  • Duplicated block (18 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:940 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:940-957 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:998-1015 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:901-918 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:934-951 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs` as WHOLE FILES: this scan already matched 75 separate duplicated blocks between them, totalling at least 912 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:940` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:788 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:788-805 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:869-886 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1044-1061 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:784-801 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:788` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (19–20 lines × 3) · ×2
  • Duplicated block (19–20 lines × 3) Content/LegendWeapon/HalibutLegend/UI/SkillWheel/HalibutWheelController.cs:94 — Content/LegendWeapon/HalibutLegend/UI/SkillWheel/HalibutWheelController.cs:94-112 | Content/LegendWeapon/KikasaLegend/UI/ServantWheel/KikasaServantWheelController.cs:114-133 | Content/LegendWeapon/SHPCLegend/UI/DomainWheel/SHPCDomainWheelController.cs:98-117 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/UI/ServantWheel/KikasaServantWheelController.cs` and `Content/LegendWeapon/SHPCLegend/UI/DomainWheel/SHPCDomainWheelController.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 92 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (19–20 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownRender.cs:22 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownRender.cs:22-41 | Content/LegendWeapon/OnikiriLegend/OniDismembers/OniDismemberRender.cs:43-62 | Content/Scenarios/Kiame/Overlay/OniUmbrellaPuddleRender.cs:53-71 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownRender.cs` and `Content/LegendWeapon/OnikiriLegend/OniDismembers/OniDismemberRender.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownRender.cs:45` calls `RunCaptures` and `Content/Scenarios/Kiame/Overlay/OniUmbrellaPuddleRender.cs:76` 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.
D4 · Code Duplication · Duplicated block (18–19 lines × 4) · ×2
  • Duplicated block (18–19 lines × 4) Content/Items/Ranged/BarrenBow.cs:183 — Content/Items/Ranged/BarrenBow.cs:183-201 | Content/Items/Ranged/NeutronBows/NeutronBow.cs:306-323 | Content/Items/Ranged/Thornstrings/ThornstringHeld.cs:224-241 | Content/Items/Ranged/Undertows/UndertowHeld.cs:230-247 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (18–19 lines × 4) Content/NPCs/BrutalNPCs/BrutalDestroyer/DestroyerHeadAI.cs:279 — Content/NPCs/BrutalNPCs/BrutalDestroyer/DestroyerHeadAI.cs:279-297 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/DukeFishronAI.cs:296-314 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/EowHeadAI.cs:504-521 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/EyeOfCthulhuAI.cs:235-253 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/NPCs/BrutalNPCs/BrutalDukeFishron/DukeFishronAI.cs:318` calls `SpawnMist` and `Content/NPCs/BrutalNPCs/BrutalDestroyer/DestroyerHeadAI.cs:301` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (18–19 lines × 3) · ×2
  • Duplicated block (18–19 lines × 3) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:977 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:977-995 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:775-792 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:959-977 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:977` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18–19 lines × 3) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs:193 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs:193-211 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeHeatRay.cs:179-196 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeSkullBeamProj.cs:190-207 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs` and `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeHeatRay.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs:193` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (16–19 lines × 2) · ×2
  • Duplicated block (16–19 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:723 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:723-741 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaMinionDrownFX.cs:301-316 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:723` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `show` to `DrownShow` in one and `WaveShow` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:742` calls `ShakeViewer` and `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaMinionDrownFX.cs:317` does not — after which the two agree again for 4 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 (16–19 lines × 2) Content/NPCs/BrutalNPCs/BrutalDestroyer/DestroyerBodyAI.cs:593 — Content/NPCs/BrutalNPCs/BrutalDestroyer/DestroyerBodyAI.cs:593-611 | Content/NPCs/BrutalNPCs/BrutalDestroyer/DestroyerTailAI.cs:27-42 — 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.
D4 · Code Duplication · Duplicated block (16–17 lines × 5) · ×2
  • Duplicated block (16–17 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:423 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:423-438 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:421-436 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:386-401 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:418-433 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:501-517 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs` as WHOLE FILES: this scan already matched 75 separate duplicated blocks between them, totalling at least 912 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:519` calls `AngleLerp`, `Clamp` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:440` 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 (16–17 lines × 5) Content/Scenarios/Kiyume/NPCs/KiyumeHound.cs:1046 — Content/Scenarios/Kiyume/NPCs/KiyumeHound.cs:1046-1061 | Content/Scenarios/Kiyume/NPCs/KiyumeWhiteHound.cs:469-484 | Content/Scenarios/Kiyume/NPCs/RidgeWalkerYokai.cs:589-605 | Content/Scenarios/Kiyume/NPCs/ShallowHandsYokai.cs:390-405 | Content/Scenarios/Kiyume/NPCs/WellHandYokai.cs:402-417 — 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 5 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Kiyume/NPCs/KiyumeHound.cs:1046` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Scenarios/Kiyume/NPCs/ShallowHandsYokai.cs:408` calls `SetValue` and `Content/Scenarios/Kiyume/NPCs/WellHandYokai.cs:420` 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.
D4 · Code Duplication · Duplicated block (16–17 lines × 4) · ×2
  • Duplicated block (16–17 lines × 4) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterStorageProvider.cs:140 — Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterStorageProvider.cs:140-155 | Content/Industrials/ElectricPowers/Crushers/CrusherStorageProvider.cs:206-221 | Content/Industrials/ElectricPowers/Incinerators/IncineratorStorageProvider.cs:222-238 | Content/Industrials/ElectricPowers/Recyclers/RecyclerStorageProvider.cs:184-199 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (16–17 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:808 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:808-824 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:889-905 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1064-1080 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:804-819 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:808` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (15–16 lines × 4) · ×2
  • Duplicated block (15–16 lines × 4) Content/Items/Modifys/RBloodButcherer.cs:926 — Content/Items/Modifys/RBloodButcherer.cs:926-941 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:158-172 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:149-164 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemMagmaBall.cs:263-278 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Modifys/RBloodButcherer.cs:926` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (15–16 lines × 4) Content/NPCs/BloomsandSerpents/BssHead.cs:287 — Content/NPCs/BloomsandSerpents/BssHead.cs:287-301 | Content/NPCs/FestersandSerpents/FssHead.cs:246-260 | Content/NPCs/ScrapCommanders/ScrapCommander.cs:218-232 | Content/NPCs/SeaShrimp/SeaShrimpBoss.cs:178-193 — before extracting anything, compare `Content/NPCs/BloomsandSerpents/BssHead.cs` and `Content/NPCs/FestersandSerpents/FssHead.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 321 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BloomsandSerpents/BssHead.cs:287` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/BloomsandSerpents/BssHead.cs:283` calls `TakeSway` and `Content/NPCs/ScrapCommanders/ScrapCommander.cs:216` 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.
D4 · Code Duplication · Duplicated block (14–15 lines × 4) · ×2
  • Duplicated block (14–15 lines × 4) Content/Items/Magic/Pandemoniums/PandemoniumFirePillar.cs:82 — Content/Items/Magic/Pandemoniums/PandemoniumFirePillar.cs:82-95 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:516-530 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:782-796 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:816-830 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/Pandemoniums/PandemoniumFirePillar.cs:82` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14–15 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:651 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:651-665 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:775-789 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:863-877 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:657-670 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:651` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12–15 lines × 2) · ×2
  • Duplicated block (12–15 lines × 2) Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:138 — Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:138-152 | Content/Industrials/Modifys/ChargingStationUI.cs:114-125 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (12–15 lines × 2) Content/Items/Stones/Granites/GraniteThrowingKnife.cs:170 — Content/Items/Stones/Granites/GraniteThrowingKnife.cs:170-181 | Content/Items/Stones/Marbles/MarbleDisc.cs:237-251 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (8–15 lines × 2) · ×2
  • Duplicated block (8–15 lines × 2) Content/Items/Melee/OniMacheteHands.cs:1202 — Content/Items/Melee/OniMacheteHands.cs:1202-1209 | Content/LegendWeapon/HalibutLegend/FishSkills/Fishotroning.cs:996-1010 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/OniMacheteHands.cs:1202` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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–15 lines × 2) Content/Narrative/Presentation/Skins/Brimstone/BrimstonePopupSkin.cs:84 — Content/Narrative/Presentation/Skins/Brimstone/BrimstonePopupSkin.cs:84-98 | Content/Narrative/Presentation/Skins/Sea/SeaPopupSkin.cs:43-50 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Narrative/Presentation/Skins/Brimstone/BrimstonePopupSkin.cs:84` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13–14 lines × 8) · ×2
  • Duplicated block (13–14 lines × 8) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:466 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:466-478 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs:531-543 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs:506-518 | Content/Industrials/ElectricPowers/Launchers/PlayerLauncherUI.cs:395-407 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:383-395 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconUI.cs:421-433 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterUI.cs:527-540 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:464-476 — before extracting anything, compare `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs` and `Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 188 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:466` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (13–14 lines × 8) Content/Scenarios/Kiyume/NPCs/FacelessOneYokai.cs:490 — Content/Scenarios/Kiyume/NPCs/FacelessOneYokai.cs:490-502 | Content/Scenarios/Kiyume/NPCs/FuneralCortegeYokai.cs:1203-1215 | Content/Scenarios/Kiyume/NPCs/KiyumeHound.cs:1047-1059 | Content/Scenarios/Kiyume/NPCs/KiyumeWhiteHound.cs:470-482 | Content/Scenarios/Kiyume/NPCs/LanternGuideYokai.cs:588-600 | Content/Scenarios/Kiyume/NPCs/RidgeWalkerYokai.cs:590-603 | Content/Scenarios/Kiyume/NPCs/ShallowHandsYokai.cs:391-404 | Content/Scenarios/Kiyume/NPCs/WellHandYokai.cs:403-416 — 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 8 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Kiyume/NPCs/FacelessOneYokai.cs:490` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12–14 lines × 3) · ×2
  • Duplicated block (12–14 lines × 3) Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs:87 — Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs:87-98 | Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteDiveOmen.cs:76-89 | Content/GameModes/BrutalMobs/Sky/Projectiles/SkyGaleDiveOmen.cs:89-102 — before extracting anything, compare `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs` and `Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteDiveOmen.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs:87` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (12–14 lines × 3) Content/Items/Melee/OniMacheteHands.cs:843 — Content/Items/Melee/OniMacheteHands.cs:843-854 | Content/LegendWeapon/HalibutLegend/FishSkills/Fishotroning.cs:819-832 | Content/Wraiths/Projectiles/GhostHandProj.cs:744-755 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
D4 · Code Duplication · Duplicated block (11–13 lines × 4) · ×2
  • Duplicated block (11–13 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownRender.cs:49 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownRender.cs:49-61 | Content/LegendWeapon/OnikiriLegend/OniDismembers/OniDismemberRender.cs:85-97 | Content/LegendWeapon/OnikiriLegend/OniDismembers/OniPlayerDismember.cs:446-456 | Content/LegendWeapon/OnikiriLegend/OniOmokages/OniOmokageRender.cs:132-144 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownRender.cs` and `Content/LegendWeapon/OnikiriLegend/OniDismembers/OniDismemberRender.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownRender.cs:49` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/OnikiriLegend/OniDismembers/OniPlayerDismember.cs:441` calls `CaptureSnapshot` and `Content/LegendWeapon/OnikiriLegend/OniDismembers/OniDismemberRender.cs:80` 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–13 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:433 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:433-444 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:402-412 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:458-470 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:390-400 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs` as WHOLE FILES: this scan already matched 55 separate duplicated blocks between them, totalling at least 611 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:433` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (10–13 lines × 3) · ×2
  • Duplicated block (10–13 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:717 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:717-729 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaMinionDrownFX.cs:297-306 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaPlayerDrownFX.cs:356-366 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:717` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10–13 lines × 3) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Projectiles/BrainTeleportRift.cs:115 — Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Projectiles/BrainTeleportRift.cs:115-127 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordBlackHoleProj.cs:802-811 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordUltArms.cs:486-496 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Projectiles/BrainTeleportRift.cs:115` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (7–13 lines × 2) · ×2
  • Duplicated block (7–13 lines × 2) Content/LegendWeapon/HalibutLegend/FishSkills/FishCatVFX.cs:74 — Content/LegendWeapon/HalibutLegend/FishSkills/FishCatVFX.cs:74-80 | Content/LegendWeapon/HalibutLegend/FishSkills/Fishotroning.cs:1040-1052 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishCatVFX.cs:74` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (7–13 lines × 2) Content/Narrative/Presentation/Skins/SHPC/SHPCDialogueSkin.cs:99 — Content/Narrative/Presentation/Skins/SHPC/SHPCDialogueSkin.cs:99-111 | Content/Narrative/Presentation/Skins/Sea/SeaDialogueSkin.cs:57-63 — before extracting anything, compare `Content/Narrative/Presentation/Skins/SHPC/SHPCDialogueSkin.cs` and `Content/Narrative/Presentation/Skins/Sea/SeaDialogueSkin.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Narrative/Presentation/Skins/SHPC/SHPCDialogueSkin.cs:99` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11 lines × 17) · ×2
  • Duplicated block (11 lines × 17) Content/GameModes/BrutalMobs/DungeonDeep/DungeonDeepNPC.cs:226 — Content/GameModes/BrutalMobs/DungeonDeep/DungeonDeepNPC.cs:226-236 | Content/GameModes/BrutalMobs/Eclipse/EclMothronNPC.cs:430-440 | Content/GameModes/BrutalMobs/Eclipse/EclipseNPC.cs:142-152 | Content/GameModes/BrutalMobs/FrostLegion/FrostLegionNPC.cs:221-231 | Content/GameModes/BrutalMobs/FrostMoon/FrmMeleeNPC.cs:181-191 | Content/GameModes/BrutalMobs/FrostMoon/FrmSiegeNPC.cs:137-147 | Content/GameModes/BrutalMobs/Graveyard/GraveyardBrutalNPC.cs:149-159 | Content/GameModes/BrutalMobs/Martians/MartiansNPC.cs:198-208 | Content/GameModes/BrutalMobs/Meteorite/MeteoriteBrutalNPC.cs:92-102 | Content/GameModes/BrutalMobs/NightPack/NightPackNPC.cs:106-116 | Content/GameModes/BrutalMobs/Ocean/OceanBrutalNPC.cs:238-248 | Content/GameModes/BrutalMobs/Pirates/PirateCrewNPC.cs:131-141 | Content/GameModes/BrutalMobs/PumpkinMoon/PumpkinMoonNPC.cs:237-247 | Content/GameModes/BrutalMobs/Sandveil/SandveilBrutalNPC.cs:194-204 | Content/GameModes/BrutalMobs/Sky/SkyBrutalNPC.cs:100-110 | Content/GameModes/BrutalMobs/Stoneborn/StonebornBrutalNPC.cs:181-191 | Content/GameModes/BrutalMobs/Temple/TempleBrutalNPC.cs:211-221 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 17 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 17 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/BrutalMobs/FrostMoon/FrmMeleeNPC.cs:176` calls `Next` and `Content/GameModes/BrutalMobs/Eclipse/EclipseNPC.cs:136` 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 × 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:469 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:469-480 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:430-440 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:435-445 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:428-438 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:495-506 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:468-479 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:454-465 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:425-435 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:405-415 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:393-403 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:425-436 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:425-435 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:470-481 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:546-558 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:480-490 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:593-604 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:487-498 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:469` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:468` calls `RebuildBlades` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:545` 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.
D4 · Code Duplication · Duplicated block (10–12 lines × 6) · ×2
  • Duplicated block (10–12 lines × 6) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainSky.cs:176 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainSky.cs:176-187 | Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamSky.cs:94-105 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainSky.cs:133-144 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspaceSky.cs:95-105 | Content/Scenarios/Kiyume/Backgrounds/KiyumeSky.cs:113-123 | Content/Scenarios/OldNet/Backgrounds/OldNetSky.cs:136-145 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainSky.cs` and `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamSky.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainSky.cs:176` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainSky.cs:174` calls `FillWaveUniforms`, `FillTideUniforms` and `Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainSky.cs:133` 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 (10–12 lines × 6) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunBullet.cs:112 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunBullet.cs:112-121 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsHail.cs:77-86 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:88-98 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:90-99 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterGlob.cs:91-101 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenCrystalShard.cs:76-87 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunBullet.cs:112` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (10–12 lines × 3) · ×2
  • Duplicated block (10–12 lines × 3) Content/GameModes/BrutalMobs/NightPack/Projectiles/NightDiveOmen.cs:79 — Content/GameModes/BrutalMobs/NightPack/Projectiles/NightDiveOmen.cs:79-90 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkChargeOmen.cs:93-102 | Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornDiveLane.cs:62-72 — before extracting anything, compare `Content/GameModes/BrutalMobs/NightPack/Projectiles/NightDiveOmen.cs` and `Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkChargeOmen.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/NightPack/Projectiles/NightDiveOmen.cs:79` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornDiveLane.cs:58` calls `CanDamage` and `Content/GameModes/BrutalMobs/NightPack/Projectiles/NightDiveOmen.cs:75` does not — after which the two agree again for 3 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 (10–12 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:291 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:291-300 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:337-346 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:402-413 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs` as WHOLE FILES: this scan already matched 47 separate duplicated blocks between them, totalling at least 491 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:291` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:333` calls `AngleLerp` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:287` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (9–12 lines × 2) · ×2
  • Duplicated block (9–12 lines × 2) Content/GameModes/BrutalMobs/Ambience/Tidecall/Projectiles/TidecallRogueWaveProj.cs:367 — Content/GameModes/BrutalMobs/Ambience/Tidecall/Projectiles/TidecallRogueWaveProj.cs:367-375 | Content/Scenarios/Dungeonworld/NPCs/UndrownedTideWave.cs:162-173 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (9–12 lines × 2) Content/Wraiths/Projectiles/GhostHandProj.cs:692 — Content/Wraiths/Projectiles/GhostHandProj.cs:692-700 | Content/Wraiths/Projectiles/GhostHandProj.cs:717-728 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Wraiths/Projectiles/GhostHandProj.cs:692` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Wraiths/Projectiles/GhostHandProj.cs:715` calls `NextVector2Unit`, `NextFloat`, `NextVector2Circular` and `Content/Wraiths/Projectiles/GhostHandProj.cs:692` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (8–11 lines × 2) · ×2
  • Duplicated block (8–11 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:797 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:797-804 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:925-935 — 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–11 lines × 2) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/HeadPrimeAI.cs:616 — Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/HeadPrimeAI.cs:616-623 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/HeadPrimeAI.cs:624-634 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/HeadPrimeAI.cs:616` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (10 lines × 22) · ×2
  • Duplicated block (10 lines × 22) Content/GameModes/GodSmith/Weapons/Broadswords/GsAdamantiteSword.cs:200 — Content/GameModes/GodSmith/Weapons/Broadswords/GsAdamantiteSword.cs:200-209 | Content/GameModes/GodSmith/Weapons/Broadswords/GsBloodButcherer.cs:158-167 | Content/GameModes/GodSmith/Weapons/Broadswords/GsBreakerBlade.cs:137-146 | Content/GameModes/GodSmith/Weapons/Broadswords/GsCobaltSword.cs:171-180 | Content/GameModes/GodSmith/Weapons/Broadswords/GsFetidBaghnakhs.cs:187-196 | Content/GameModes/GodSmith/Weapons/Broadswords/GsHamBat.cs:141-150 | Content/GameModes/GodSmith/Weapons/Broadswords/GsMeowmere.cs:459-468 | Content/GameModes/GodSmith/Weapons/Broadswords/GsMeowmere.cs:600-609 | Content/GameModes/GodSmith/Weapons/Broadswords/GsMythrilSword.cs:155-164 | Content/GameModes/GodSmith/Weapons/Broadswords/GsPhaseBladeShared.cs:332-341 | Content/GameModes/GodSmith/Weapons/Broadswords/GsPiercingStarlight.cs:337-346 | Content/GameModes/GodSmith/Weapons/Broadswords/GsSlapHand.cs:137-146 | Content/GameModes/GodSmith/Weapons/Broadswords/GsStarWrath.cs:462-471 | Content/GameModes/GodSmith/Weapons/Broadswords/GsTheHorsemansBlade.cs:168-178 | Content/GameModes/GodSmith/Weapons/Broadswords/GsTitaniumSword.cs:125-134 | Content/GameModes/GodSmith/Weapons/Flails/GsTheMeatball.cs:82-91 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:606-615 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsSolarEruption.cs:415-424 | Content/GameModes/GodSmith/Weapons/Shortswords/GsPlatinumShortsword.cs:83-92 | Content/GameModes/GodSmith/Weapons/Spears/GsJoustingLances.cs:467-476 | Content/Items/Melee/DestroyersBladeEXs/DestroyerBiteProj.cs:70-79 | Content/Items/Melee/NeutronGlaive.cs:795-805 — there are 22 copies across 21 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 22 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/Broadswords/GsAdamantiteSword.cs:200` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (10 lines × 22) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:240 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:240-250 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:197-206 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:217-226 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:197-206 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:247-257 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:243-253 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:252-262 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:174-183 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:181-190 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:224-233 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:208-217 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:208-217 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:215-225 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:195-204 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:253-263 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:261-271 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:202-212 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:169-180 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:164-175 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:221-231 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:241-251 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:202-212 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (10 lines × 19) · ×2
  • Duplicated block (10 lines × 19) Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:228 — Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:228-237 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT2.cs:125-134 | Content/Items/Melee/Abyssrends/AbyssrendClampHeld.cs:74-83 | Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:109-118 | Content/Items/Melee/CosmicCalamity.cs:141-150 | Content/Items/Melee/DawnshatterAzures/DawnshatterHeld.cs:122-131 | Content/Items/Melee/DestroyersBlade.cs:124-133 | Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:100-109 | Content/Items/Melee/DragonsScaleGreatsword.cs:140-149 | Content/Items/Melee/EnergySword.cs:152-161 | Content/Items/Melee/NeutronGlaive.cs:197-206 | Content/Items/Melee/RebelBlade.cs:176-185 | Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:115-124 | Content/Items/Melee/StormGoddessSpears/StormGoddessSpearHeld.cs:67-76 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:159-168 | Content/Items/Modifys/RBloodButcherer.cs:183-192 | Content/Items/Modifys/RTerraBlades/RTerraBladeHeld.cs:149-159 | Content/Items/Stones/Marbles/MarbleClub.cs:117-126 | Content/Items/Stones/Marbles/MarbleHuntingKnife.cs:113-122 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 19 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 19 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:228` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:224` calls `Clamp` and `Content/Items/Melee/NeutronGlaive.cs:195` 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 (10 lines × 19) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Projectiles/EmpressLance.cs:61 — Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Projectiles/EmpressLance.cs:61-70 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Projectiles/EmpressWhipCrack.cs:51-60 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs:36-45 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/TwinsTetherArc.cs:39-48 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordBoltProj.cs:41-50 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordEyeLinkProj.cs:38-47 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordOrbProj.cs:54-63 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordScanRayProj.cs:35-44 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenChandelierProj.cs:49-58 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenCrystalSpikeProj.cs:56-65 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenCrystalSpireProj.cs:35-44 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenGelPearlProj.cs:26-35 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenPrismBeamProj.cs:65-74 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeArcChainProj.cs:47-56 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeHeatRay.cs:48-57 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofGrabTongueProj.cs:47-56 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofRetinaScanBeam.cs:43-52 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofRotBeamProj.cs:39-48 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofTongueLashProj.cs:43-52 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs` and `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeHeatRay.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeHeatRay.cs:42` calls `HostValid`, `UpdateAnchor` and `Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordEyeLinkProj.cs:34` 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.
D4 · Code Duplication · Duplicated block (10 lines × 17) · ×2
  • Duplicated block (10 lines × 17) Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:191 — Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:191-200 | Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:319-328 | Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzBeamProj.cs:268-278 | Content/Items/Magic/CommandersStaff.cs:350-359 | Content/Items/Magic/NeutronWands/NeutronPulsar.cs:417-426 | Content/Items/Melee/Heartcarver.cs:508-517 | Content/Items/Melee/SpearOfLonginuses/LonginusAssets.cs:148-157 | Content/Items/Melee/SpearOfLonginuses/LonginusAssets.cs:219-228 | Content/Items/Melee/SpearOfLonginuses/LonginusAssets.cs:264-273 | Content/Items/Melee/SpearOfLonginuses/LonginusAssets.cs:374-383 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:274-283 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerFrostPulseProj.cs:138-147 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerIceSpikeProj.cs:174-183 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:223-232 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordRayRender.cs:41-50 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenGaleFieldProj.cs:114-123 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenPrismBeamProj.cs:283-292 — there are 17 copies across 14 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 17 sites; resolving a subset leaves the remainder to drift apart. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Magic/CommandersStaff.cs:359` calls `SetValue` and `Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:200` does not — after which the two agree again for 3 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 (10 lines × 17) Content/GameModes/GodSmith/Armors/Reset/GsPillarArmors.cs:282 — Content/GameModes/GodSmith/Armors/Reset/GsPillarArmors.cs:282-291 | Content/GameModes/GodSmith/Armors/Reset/GsTikiArmor.cs:57-66 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistFireOrb.cs:51-62 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistIceShard.cs:44-55 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:51-62 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressLance.cs:80-89 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressPetal.cs:54-65 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:56-67 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterGlob.cs:48-58 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemEyeSpit.cs:36-47 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemMagmaBall.cs:57-68 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonOrb.cs:42-51 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonOrb.cs:187-198 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraSeed.cs:36-47 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenCrystalShard.cs:44-55 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronBloodSkull.cs:52-63 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuWenFX.cs:166-175 — there are 17 copies across 16 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 17 sites; resolving a subset leaves the remainder to drift apart. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemEyeSpit.cs:29` calls `CoolTint`, `Clamp` and `Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuWenFX.cs:164` 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.
D4 · Code Duplication · Duplicated block (8 lines × 17) · ×2
  • Duplicated block (8 lines × 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:469 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:469-476 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:430-437 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:435-442 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:428-435 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:495-502 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:468-475 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:454-461 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:425-432 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:405-412 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:393-400 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:425-432 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:425-432 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:470-477 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:480-487 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:503-510 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:509-516 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:487-494 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:469` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:514` calls `FindTarget` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:480` 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 × 17) Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs:112 — Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs:112-119 | Content/Industrials/ElectricPowers/Incinerators/IncineratorTile.cs:104-111 | Content/Industrials/ElectricPowers/LifeWeavers/LifeWeaverTile.cs:65-72 | Content/Industrials/ElectricPowers/LifeWeavers/WGGLifeWeaver.cs:117-124 | Content/Industrials/ElectricPowers/Lumberjacks/LumberjackTile.cs:64-71 | Content/Industrials/ElectricPowers/Lumberjacks/WGGLumberjack.cs:112-119 | Content/Industrials/ElectricPowers/MiningMachines/BaseMiningMachineTP.cs:432-439 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatTile.cs:118-125 | Content/Industrials/ElectricPowers/Spectrometers/Spectrometer.cs:108-115 | Content/Industrials/ElectricPowers/WeatherControllers/WeatherControllerTile.cs:128-135 | Content/Industrials/Generator/Biomass/BiomassGenerator.cs:137-144 | Content/Industrials/Generator/Thermal/ThermalGenerator.cs:103-110 | Content/Industrials/Generator/Thermal/ThermalGeneratorMK2.cs:103-110 | Content/Items/Placeable/HoChaMeditatorItem.cs:81-88 | Content/Items/Placeable/StarflowPlatedBlock.cs:80-87 | Content/Scenarios/Draedon/Quest/DeploySignaltowers/CQETConstructor.cs:115-122 | Content/Tiles/NeutronStarIngotTile.cs:49-57 — before extracting anything, compare `Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs` and `Content/Industrials/ElectricPowers/Incinerators/IncineratorTile.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs:112` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (7 lines × 16) · ×2
  • Duplicated block (7 lines × 16) Content/GameModes/BrutalMobs/EliteMove/Projectiles/EMScatterBoltProj.cs:87 — Content/GameModes/BrutalMobs/EliteMove/Projectiles/EMScatterBoltProj.cs:87-93 | Content/GameModes/BrutalMobs/EvilBiome/Projectiles/VileLanceProj.cs:93-99 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhImpFireBolt.cs:75-81 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhScytheBolt.cs:76-82 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhShellSpike.cs:67-73 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhStingerBolt.cs:76-82 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhTridentBolt.cs:75-81 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionInkGlob.cs:83-89 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionScoutBolt.cs:82-88 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionVolleyArrow.cs:86-92 | Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteMoltenGlob.cs:142-148 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtBroadsideBall.cs:92-98 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtFanShot.cs:78-84 | Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilCursedBeadProj.cs:73-79 | Content/GameModes/BrutalMobs/Sky/Projectiles/SkyFeatherBolt.cs:69-75 | Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornJavelinProj.cs:87-93 — before extracting anything, compare `Content/GameModes/BrutalMobs/EliteMove/Projectiles/EMScatterBoltProj.cs` and `Content/GameModes/BrutalMobs/EvilBiome/Projectiles/VileLanceProj.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/EliteMove/Projectiles/EMScatterBoltProj.cs:87` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 16) Content/Items/Melee/DestroyersBlade.cs:541 — Content/Items/Melee/DestroyersBlade.cs:541-547 | Content/Items/Melee/DestroyersBlade.cs:693-699 | Content/Items/Melee/DestroyersBladeEXs/DestroyersBeamEX.cs:177-183 | Content/Items/Melee/DragonsScaleGreatsword.cs:562-568 | Content/Items/Melee/EnergySword.cs:578-584 | Content/Items/Melee/Heartcarver.cs:970-976 | Content/Items/Melee/OniMacheteHands.cs:1120-1126 | Content/Items/Melee/OniMacheteHands.cs:1361-1367 | Content/Items/Melee/RebelBlade.cs:609-615 | Content/Items/Melee/StormGoddessSpears/StormGoddessSpearHeld.cs:549-555 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:544-550 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCrimsonTiger.cs:813-819 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDemonicHell.cs:660-666 | Content/LegendWeapon/HalibutLegend/FishSkills/FishEaterofPlankton.cs:420-426 | Content/LegendWeapon/HalibutLegend/FishSkills/FishFallenStarVFX.cs:225-231 | Content/LegendWeapon/HalibutLegend/FishSkills/FishWyverntail.cs:412-418 — before extracting anything, compare `Content/Items/Melee/DestroyersBlade.cs` and `Content/Items/Melee/DestroyersBladeEXs/DestroyersBeamEX.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DestroyersBlade.cs:541` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Melee/DestroyersBlade.cs:701` calls `PostDraw`, `AddLight`, `ToVector3` and `Content/Items/Melee/EnergySword.cs:585` 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.
D4 · Code Duplication · Duplicated block (9–10 lines × 14) · ×2
  • Duplicated block (9–10 lines × 14) Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:321 — Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:321-329 | Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzBeamProj.cs:270-279 | Content/Items/Magic/CommandersStaff.cs:352-360 | Content/Items/Magic/NeutronWands/NeutronPulsar.cs:419-427 | Content/Items/Melee/DestroyersBlade.cs:680-688 | Content/Items/Melee/DestroyersBladeEXs/DestroyersBeamEX.cs:163-172 | Content/Items/Melee/Heartcarver.cs:510-518 | Content/Items/Melee/Heartcarver.cs:959-967 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:276-284 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:225-233 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Projectiles/EmpressAuroraVeil.cs:119-127 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordRayRender.cs:43-51 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenGaleFieldProj.cs:116-124 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenPrismBeamProj.cs:285-293 — there are 14 copies across 13 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 14 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzBeamProj.cs:270` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:331` calls `SetValue` and `Content/Items/Melee/Heartcarver.cs:968` does not — after which the two agree again for 3 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–10 lines × 14) Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawWormProj.cs:582 — Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawWormProj.cs:582-590 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerMotionFX.cs:111-120 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs:127-135 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidPool.cs:102-110 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowBreachOmen.cs:83-91 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowGeyserProj.cs:158-166 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowGeyserProj.cs:190-198 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowLungeOmen.cs:177-185 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Projectiles/HoneyPuddleZone.cs:131-139 | Content/NPCs/FestersandSerpents/Projectiles/FssCascadeDrop.cs:86-94 | Content/NPCs/FestersandSerpents/Projectiles/FssGeyserColumn.cs:162-170 | Content/NPCs/FestersandSerpents/Projectiles/FssGeyserColumn.cs:194-202 | Content/NPCs/FestersandSerpents/Projectiles/FssIchorGlob.cs:125-133 | Content/NPCs/FestersandSerpents/Projectiles/FssIchorPool.cs:222-230 — there are 14 copies across 12 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 14 sites; resolving a subset leaves the remainder to drift apart. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowGeyserProj.cs:156` calls `SetValue` and `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs:125` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (10 lines × 12) · ×2
  • Duplicated block (10 lines × 12) Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzCrystalProj.cs:263 — Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzCrystalProj.cs:263-273 | Content/Items/Melee/DragonsScaleGreatsword.cs:674-683 | Content/Items/Melee/DragonsScaleGreatsword.cs:884-893 | Content/Items/Melee/HeartcarverHeart.cs:248-257 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:1036-1045 | Content/Items/Ranged/UniversalFrost.cs:393-402 | Content/LegendWeapon/HalibutLegend/FishSkills/FishVariegatedLard.cs:694-703 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs:326-335 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Rendering/KingSlimeGelFX.cs:186-196 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenCrystalPrisonProj.cs:165-174 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Rendering/QueenPrismNodeRenderer.cs:59-68 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofRotBeamProj.cs:160-170 — there are 12 copies across 11 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 12 sites; resolving a subset leaves the remainder to drift apart. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Ranged/UniversalFrost.cs:403` calls `SetValue` and `Content/Items/Melee/DragonsScaleGreatsword.cs:684` 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 (10 lines × 12) Content/LegendWeapon/SHPCLegend/Modules/Barrel/RapidBarrelModule.cs:436 — Content/LegendWeapon/SHPCLegend/Modules/Barrel/RapidBarrelModule.cs:436-445 | Content/LegendWeapon/SHPCLegend/Modules/Frame/MultiCellFrameModule.cs:127-136 | Content/LegendWeapon/SHPCLegend/Modules/Frame/ResonanceFrameModule.cs:393-402 | Content/LegendWeapon/SHPCLegend/Modules/Frame/VolatileFrameModule.cs:471-480 | Content/LegendWeapon/SHPCLegend/Modules/Grip/EfficientGripModule.cs:322-331 | Content/LegendWeapon/SHPCLegend/Modules/Optic/AdaptiveOpticModule.cs:114-123 | Content/LegendWeapon/SHPCLegend/Modules/Optic/SniperOpticModule.cs:270-279 | Content/LegendWeapon/SHPCLegend/Modules/Stock/AssaultStockModule.cs:60-69 | Content/LegendWeapon/SHPCLegend/Modules/Stock/BraceStockModule.cs:231-240 | Content/LegendWeapon/SHPCLegend/Modules/Stock/ErgonomicStockModule.cs:348-357 | Content/LegendWeapon/SHPCLegend/Modules/Stock/SteadyStockModule.cs:493-502 | Content/LegendWeapon/SHPCLegend/Modules/Stock/StormStockModule.cs:91-100 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 12 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 12 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/SHPCLegend/Modules/Frame/VolatileFrameModule.cs:469` calls `PulseGlitch`, `Max` and `Content/LegendWeapon/SHPCLegend/Modules/Grip/EfficientGripModule.cs:320` 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.
D4 · Code Duplication · Duplicated block (9–10 lines × 4) · ×2
  • Duplicated block (9–10 lines × 4) Content/Items/Melee/DestroyersBlade.cs:478 — Content/Items/Melee/DestroyersBlade.cs:478-487 | Content/Items/Melee/DragonsScaleGreatsword.cs:504-512 | Content/Items/Melee/EnergySword.cs:515-523 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:486-494 — before extracting anything, compare `Content/Items/Melee/DestroyersBlade.cs` and `Content/Items/Melee/DragonsScaleGreatsword.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 419 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DestroyersBlade.cs:478` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9–10 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamGroundField.cs:90 — Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamGroundField.cs:90-98 | Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSim.cs:99-108 | Content/Scenarios/Kiyume/Fog/KiyumeFogSim.cs:169-178 | Content/Scenarios/Kiyume/Fog/KiyumeGroundField.cs:105-113 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamGroundField.cs` and `Content/Scenarios/Kiyume/Fog/KiyumeGroundField.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamGroundField.cs:90` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (4–10 lines × 3) · ×2
  • Duplicated block (4–10 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:1129 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:1129-1138 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1468-1471 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1480-1488 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:1129` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1489` calls `SetValue` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:1139` does not — after which the two agree again for 4 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 (4–10 lines × 3) Content/Scenarios/OldNet/Tiles/OldNetBreakerTile.cs:97 — Content/Scenarios/OldNet/Tiles/OldNetBreakerTile.cs:97-106 | Content/Scenarios/OldNet/Tiles/OldNetEventNodeTile.cs:119-122 | Content/Scenarios/OldNet/Tiles/OldNetSentryMineTile.cs:129-137 — before extracting anything, compare `Content/Scenarios/OldNet/Tiles/OldNetBreakerTile.cs` and `Content/Scenarios/OldNet/Tiles/OldNetSentryMineTile.cs` as WHOLE FILES: this scan already matched 5 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/OldNet/Tiles/OldNetBreakerTile.cs:97` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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.
D4 · Code Duplication · Duplicated block (9 lines × 18) · ×2
  • Duplicated block (9 lines × 18) Content/GameModes/BrutalMobs/EliteMove/Projectiles/EMScatterBoltProj.cs:87 — Content/GameModes/BrutalMobs/EliteMove/Projectiles/EMScatterBoltProj.cs:87-95 | Content/GameModes/BrutalMobs/EvilBiome/Projectiles/VileLanceProj.cs:93-101 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhImpFireBolt.cs:75-83 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhScytheBolt.cs:76-84 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhShellSpike.cs:67-75 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhStingerBolt.cs:76-84 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhTridentBolt.cs:75-83 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionInkGlob.cs:83-91 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionScoutBolt.cs:82-90 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionVolleyArrow.cs:86-94 | Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteMoltenGlob.cs:142-150 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtBroadsideBall.cs:92-100 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtFanShot.cs:78-86 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkEmberSeedProj.cs:93-101 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkMortarShellProj.cs:95-103 | Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilCursedBeadProj.cs:73-81 | Content/GameModes/BrutalMobs/Sky/Projectiles/SkyFeatherBolt.cs:69-77 | Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornJavelinProj.cs:87-95 — before extracting anything, compare `Content/GameModes/BrutalMobs/EliteMove/Projectiles/EMScatterBoltProj.cs` and `Content/GameModes/BrutalMobs/EvilBiome/Projectiles/VileLanceProj.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/EliteMove/Projectiles/EMScatterBoltProj.cs:87` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (9 lines × 18) Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:332 — Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:332-340 | Content/Items/Magic/AriaofTheCosmoses/GammaRayBeam.cs:215-224 | Content/Items/Magic/CommandersStaff.cs:362-370 | Content/Items/Melee/DragonsScaleGreatsword.cs:685-693 | Content/Items/Melee/DragonsScaleGreatsword.cs:896-904 | Content/Items/Melee/Heartcarver.cs:520-528 | Content/Items/Melee/HeartcarverHeart.cs:261-269 | Content/Items/Melee/OniMacheteHands.cs:1507-1515 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:1048-1056 | Content/Items/Ranged/CrystalDimming.cs:412-420 | Content/Items/Ranged/UniversalFrost.cs:404-412 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDemonicHell.cs:294-302 | Content/LegendWeapon/HalibutLegend/FishSkills/FishFrostMinnowVFX.cs:355-364 | Content/LegendWeapon/HalibutLegend/FishSkills/FishRock.cs:773-781 | Content/LegendWeapon/HalibutLegend/FishSkills/FishVariegatedLard.cs:711-719 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:286-294 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs:338-346 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:235-243 — there are 18 copies across 17 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 18 sites; resolving a subset leaves the remainder to drift apart. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:331` calls `SetValue` and `Content/Items/Melee/OniMacheteHands.cs:1506` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (9 lines × 10) · ×2
  • Duplicated block (9 lines × 10) Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:319 — Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:319-327 | Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzBeamProj.cs:268-277 | Content/Items/Magic/CommandersStaff.cs:350-358 | Content/Items/Melee/Heartcarver.cs:508-516 | Content/Items/Ranged/HyperionBarrage.cs:154-162 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:274-282 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:223-231 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordRayRender.cs:41-49 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenGaleFieldProj.cs:114-122 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenPrismBeamProj.cs:283-291 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 10 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 10 times. 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 (9 lines × 10) Content/GameModes/GodSmith/Weapons/Broadswords/BroadswordSchemes.Wood.cs:685 — Content/GameModes/GodSmith/Weapons/Broadswords/BroadswordSchemes.Wood.cs:685-693 | Content/GameModes/GodSmith/Weapons/Broadswords/BroadswordSchemes.Wood.cs:770-778 | Content/GameModes/GodSmith/Weapons/Broadswords/GsBladetongue.cs:122-130 | Content/GameModes/GodSmith/Weapons/Broadswords/GsChlorophyteClaymore.cs:177-185 | Content/GameModes/GodSmith/Weapons/Broadswords/GsFrostbrand.cs:128-136 | Content/GameModes/GodSmith/Weapons/Broadswords/GsIceBlade.cs:89-97 | Content/GameModes/GodSmith/Weapons/Broadswords/GsSeedler.cs:104-112 | Content/GameModes/GodSmith/Weapons/Broadswords/GsSeedler.cs:184-192 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsVampireKnives.cs:354-362 | Content/GameModes/GodSmith/Weapons/Spears/GsNorthPole.cs:390-398 — there are 10 copies across 8 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 10 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (8–9 lines × 7) · ×2
  • Duplicated block (8–9 lines × 7) Content/Items/Melee/CursedflameBloodfists/CursedflameFistProj.cs:184 — Content/Items/Melee/CursedflameBloodfists/CursedflameFistProj.cs:184-191 | Content/Items/Melee/StormGoddessSpears/AncientStormGoddessSpear.cs:312-320 | Content/Items/Melee/StormGoddessSpears/AncientStormGoddessSpear.cs:477-485 | Content/Items/Ranged/NeutronBows/EXNeutronArrow.cs:75-82 | Content/Items/Summon/WhiplashGalactica.cs:231-238 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerLaser.cs:120-127 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/DeadLaser.cs:78-85 — before extracting anything, compare `Content/Items/Melee/StormGoddessSpears/AncientStormGoddessSpear.cs` and `Content/Items/Ranged/NeutronBows/EXNeutronArrow.cs` 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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–9 lines × 7) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1092 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1092-1100 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:886-893 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1122-1129 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:911-918 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:931-938 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:879-887 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:880-887 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1107` calls `BladeDrawRot` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:899` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (7–9 lines × 3) · ×2
  • Duplicated block (7–9 lines × 3) Content/GameModes/BrutalMobs/Ambience/Tidecall/Projectiles/TidecallRogueWaveProj.cs:364 — Content/GameModes/BrutalMobs/Ambience/Tidecall/Projectiles/TidecallRogueWaveProj.cs:364-370 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistUmbraShade.cs:511-517 | Content/Scenarios/Dungeonworld/NPCs/UndrownedTideWave.cs:159-167 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/Tidecall/Projectiles/TidecallRogueWaveProj.cs:364` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (7–9 lines × 3) Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSystem.cs:164 — Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSystem.cs:164-172 | Content/Scenarios/Kiyume/Fog/KiyumeFogSystem.cs:202-210 | Content/Scenarios/Kiyume/Fog/KiyumeFogSystem.cs:228-234 — before extracting anything, compare `Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSystem.cs` and `Content/Scenarios/Kiyume/Fog/KiyumeFogSystem.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSystem.cs:164` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (6–9 lines × 2) · ×2
  • Duplicated block (6–9 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeSlash.cs:124 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeSlash.cs:124-132 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterGlob.cs:135-140 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeSlash.cs:124` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (6–9 lines × 2) Content/NPCs/BloomsandSerpents/BssClawRig.cs:328 — Content/NPCs/BloomsandSerpents/BssClawRig.cs:328-333 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordArmIK.cs:210-218 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordArmIK.cs:219` calls `Min` and `Content/NPCs/BloomsandSerpents/BssClawRig.cs:334` 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.
D4 · Code Duplication · Duplicated block (7 lines × 30) · ×2
  • Duplicated block (7 lines × 30) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1155 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1155-1161 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:915-921 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1174-1180 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:972-978 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1508-1514 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1096-1102 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1237-1243 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:982-988 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:808-814 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:1051-1057 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:977-983 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:876-882 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:936-942 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:909-915 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1377-1383 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:928-934 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:266-272 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1267-1273 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:1048-1054 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:1107-1113 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1315-1321 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:928-934 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1279-1285 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1329-1335 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1443-1449 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1364-1370 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1222-1228 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:1400-1406 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1532-1538 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1556-1562 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1339` calls `Clamp` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:274` 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 × 30) Content/Industrials/ElectricPowers/Apiaries/ApiaryTile.cs:20 — Content/Industrials/ElectricPowers/Apiaries/ApiaryTile.cs:20-26 | Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterTile.cs:26-32 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherTile.cs:20-26 | Content/Industrials/ElectricPowers/Collectors/Collector.cs:66-72 | Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs:47-53 | Content/Industrials/ElectricPowers/Crushers/CrusherTile.cs:24-30 | Content/Industrials/ElectricPowers/ElectricMinRocket.cs:239-246 | Content/Industrials/ElectricPowers/GridSwitches/GridSwitchTile.cs:19-25 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerTile.cs:20-26 | Content/Industrials/ElectricPowers/Incinerators/IncineratorTile.cs:18-24 | Content/Industrials/ElectricPowers/Launchers/PlayerLauncherTile.cs:20-26 | Content/Industrials/ElectricPowers/LifeWeavers/LifeWeaverTile.cs:17-23 | Content/Industrials/ElectricPowers/LifeWeavers/WGGLifeWeaver.cs:52-58 | Content/Industrials/ElectricPowers/Lumberjacks/LumberjackTile.cs:16-22 | Content/Industrials/ElectricPowers/Lumberjacks/WGGLumberjack.cs:47-53 | Content/Industrials/ElectricPowers/MiningMachines/MiningMachine.cs:58-65 | Content/Industrials/ElectricPowers/MiningMachines/MiningMachineMk2.cs:58-65 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTile.cs:20-26 | Content/Industrials/ElectricPowers/Recyclers/RecyclerTile.cs:19-25 | Content/Industrials/ElectricPowers/Sensors/SensorTile.cs:21-27 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatTile.cs:21-27 | Content/Industrials/ElectricPowers/Spectrometers/Spectrometer.cs:53-59 | Content/Industrials/ElectricPowers/Sundials/ElectricSundialTile.cs:25-31 | Content/Industrials/ElectricPowers/Throwers/ThrowerTile.cs:25-31 | Content/Industrials/MaterialFlow/LaserEnergyTrans.cs:64-70 | Content/Scenarios/Draedon/Quest/DeploySignaltowers/CQETConstructor.cs:64-70 | Content/Scenarios/OldDuke/MermanRod.cs:49-55 | Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersTile.cs:20-26 | Content/Scenarios/OldDuke/OldDuchests/OldDuchest.cs:55-61 | OtherMods/Coralite/Arcanes/ArcaneTransformer.cs:40-46 — before extracting anything, compare `Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterTile.cs` and `Content/Industrials/ElectricPowers/Crushers/CrusherTile.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 74 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Apiaries/ApiaryTile.cs:20` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Industrials/ElectricPowers/Sundials/ElectricSundialTile.cs:22` calls `VaultLoaden` and `Content/Industrials/ElectricPowers/Apiaries/ApiaryTile.cs:18` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (8 lines × 23) · ×2
  • Duplicated block (8 lines × 23) Content/GameModes/BrutalMobs/EliteMove/Projectiles/EMScatterBoltProj.cs:87 — Content/GameModes/BrutalMobs/EliteMove/Projectiles/EMScatterBoltProj.cs:87-95 | Content/GameModes/BrutalMobs/EvilBiome/Projectiles/VileLanceProj.cs:93-101 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhImpFireBolt.cs:75-83 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhScytheBolt.cs:76-84 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhShellSpike.cs:67-75 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhStingerBolt.cs:76-84 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhTridentBolt.cs:75-83 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionInkGlob.cs:83-91 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionScoutBolt.cs:82-90 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionVolleyArrow.cs:86-94 | Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteMoltenGlob.cs:142-150 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtBroadsideBall.cs:92-100 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtFanShot.cs:78-86 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkEmberSeedProj.cs:93-101 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkMortarShellProj.cs:95-103 | Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilCursedBeadProj.cs:73-81 | Content/GameModes/BrutalMobs/Sky/Projectiles/SkyFeatherBolt.cs:69-77 | Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornJavelinProj.cs:87-95 | Content/Items/BloomArsenal.cs:195-202 | Content/LegendWeapon/HalibutLegend/FishSkills/FishotroningVFX.cs:172-180 | Content/NPCs/BloomsandSerpents/Projectiles/BssNeedleProj.cs:60-67 | Content/NPCs/BloomsandSerpents/Projectiles/BssSandGlob.cs:65-73 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Projectiles/BrutalBeeStinger.cs:80-88 — before extracting anything, compare `Content/GameModes/BrutalMobs/EliteMove/Projectiles/EMScatterBoltProj.cs` and `Content/GameModes/BrutalMobs/EvilBiome/Projectiles/VileLanceProj.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/EliteMove/Projectiles/EMScatterBoltProj.cs:87` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 × 23) Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:193 — Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:193-200 | Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:321-328 | Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzBeamProj.cs:270-278 | Content/Items/Magic/CommandersStaff.cs:352-359 | Content/Items/Magic/NeutronWands/NeutronPulsar.cs:419-426 | Content/Items/Melee/DestroyersBlade.cs:680-687 | Content/Items/Melee/DestroyersBladeEXs/DestroyersBeamEX.cs:163-171 | Content/Items/Melee/Flawless.cs:571-578 | Content/Items/Melee/Heartcarver.cs:510-517 | Content/Items/Melee/Heartcarver.cs:959-966 | Content/Items/Melee/SpearOfLonginuses/LonginusAssets.cs:150-157 | Content/Items/Melee/SpearOfLonginuses/LonginusAssets.cs:221-228 | Content/Items/Melee/SpearOfLonginuses/LonginusAssets.cs:266-273 | Content/Items/Melee/SpearOfLonginuses/LonginusAssets.cs:305-312 | Content/Items/Melee/SpearOfLonginuses/LonginusAssets.cs:376-383 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:276-283 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerFrostPulseProj.cs:140-147 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerIceSpikeProj.cs:176-183 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:225-232 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Projectiles/EmpressAuroraVeil.cs:119-126 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordRayRender.cs:43-50 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenGaleFieldProj.cs:116-123 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenPrismBeamProj.cs:285-292 — there are 23 copies across 18 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 23 sites; resolving a subset leaves the remainder to drift apart. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Magic/CommandersStaff.cs:359` calls `SetValue` and `Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:200` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (8 lines × 16) · ×2
  • Duplicated block (8 lines × 16) Content/GameModes/BrutalMobs/Ambience/Tidecall/Projectiles/TidecallRogueWaveProj.cs:359 — Content/GameModes/BrutalMobs/Ambience/Tidecall/Projectiles/TidecallRogueWaveProj.cs:359-367 | Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs:202-210 | Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTsunamiProj.cs:281-289 | Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:176-183 | Content/Items/Magic/Everdeeps/EverdeepMaelstrom.cs:327-334 | Content/Items/Magic/Everdeeps/EverdeepRing.cs:354-362 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronSharkTornadoProj.cs:318-327 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronTsunamiWallProj.cs:170-179 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpGeyserSpout.cs:183-190 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpJetBeam.cs:200-207 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpLeapVortex.cs:135-142 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpMiniVortex.cs:134-141 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpVortexWall.cs:136-143 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpWaveCrest.cs:173-180 | Content/Scenarios/Dungeonworld/NPCs/UndrownedDepthMine.cs:200-207 | Content/Scenarios/Dungeonworld/NPCs/UndrownedTideWave.cs:154-162 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 16 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 16 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTsunamiProj.cs:281` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/BrutalMobs/Ambience/Tidecall/Projectiles/TidecallRogueWaveProj.cs:357` calls `SetValue` and `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpGeyserSpout.cs:183` 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 × 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:548 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:548-556 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:475-483 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:554-562 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:560-568 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:839-847 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:513-521 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:593-601 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:421-428 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:499-506 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:468-476 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:548-556 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:511-519 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:544-552 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:559-567 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:687-694 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:805-812 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs` as WHOLE FILES: this scan already matched 46 separate duplicated blocks between them, totalling at least 456 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:548` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (8 lines × 12) · ×2
  • Duplicated block (8 lines × 12) Content/GameModes/BrutalMobs/Ambience/Bloodveil/BloodveilAmbience.cs:186 — Content/GameModes/BrutalMobs/Ambience/Bloodveil/BloodveilAmbience.cs:186-193 | Content/GameModes/BrutalMobs/Ambience/Brinefume/BrinefumeAmbience.cs:102-109 | Content/GameModes/BrutalMobs/Ambience/DuneStorm/DuneStormAmbience.cs:148-155 | Content/GameModes/BrutalMobs/Ambience/Duskwatch/DuskwatchAmbience.cs:164-171 | Content/GameModes/BrutalMobs/Ambience/Rainveil/RainveilAmbience.cs:117-124 | Content/GameModes/BrutalMobs/Ambience/Woodsong/WoodsongAmbience.cs:831-838 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspaceSystem.cs:64-73 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Rendering/EmpressDaySky.cs:106-113 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordEclipseSky.cs:93-100 | Content/Scenarios/Himayo/ToriiShrines/ToriiDusk.cs:117-124 | Content/Wraiths/Abilities/CrimsonBrides/BrideHallSky.cs:87-94 | Content/Wraiths/Abilities/GhostRains/GhostRainAmbience.cs:77-84 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 12 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 12 times.
  • Duplicated block (8 lines × 12) Content/LegendWeapon/HalibutLegend/FishSkills/FishAmanita.cs:481 — Content/LegendWeapon/HalibutLegend/FishSkills/FishAmanita.cs:481-488 | Content/LegendWeapon/HalibutLegend/FishSkills/FishAmanita.cs:733-740 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBloodyManowar.cs:791-798 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBone.cs:160-167 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDemonicHell.cs:335-342 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDrizzle.cs:704-711 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDynamite.cs:341-348 | Content/LegendWeapon/HalibutLegend/FishSkills/FishEaterofPlankton.cs:106-113 | Content/LegendWeapon/HalibutLegend/FishSkills/FishScorpio.cs:153-160 | Content/LegendWeapon/HalibutLegend/FishSkills/FishScorpioSandnado.cs:195-202 | Content/LegendWeapon/HalibutLegend/FishSkills/FishSlime.cs:211-218 | Content/LegendWeapon/HalibutLegend/FishSkills/FishSparkling.cs:422-429 — there are 12 copies across 11 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 12 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (7 lines × 9) · ×2
  • Duplicated block (7 lines × 9) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:216 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:216-222 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:174-180 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:194-200 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:174-180 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:223-229 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:185-191 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:185-191 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:191-197 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:172-178 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:216` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 9) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:1482 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:1482-1488 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1384-1390 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1451-1457 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1508-1514 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1570-1576 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1633-1639 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1663-1669 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1397-1403 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1732-1738 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 9 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 9 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:1482` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:1477` calls `PlaySound` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1379` 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.
D4 · Code Duplication · Duplicated block (7–8 lines × 4) · ×2
  • Duplicated block (7–8 lines × 4) Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:393 — Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:393-399 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:421-428 | Content/Industrials/ElectricPowers/Recyclers/RecyclerUI.cs:399-405 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterUI.cs:405-411 — before extracting anything, compare `Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs` and `Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 303 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:393` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7–8 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:284 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:284-290 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:1068-1075 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1299-1306 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1353-1360 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:284` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (4–8 lines × 3) · ×2
  • Duplicated block (4–8 lines × 3) Content/LegendWeapon/HalibutLegend/FishSkills/FishIchornVFX.cs:194 — Content/LegendWeapon/HalibutLegend/FishSkills/FishIchornVFX.cs:194-201 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:333-340 | Content/PRTTypes/PRT_KikasaQueenSlimeFacet.cs:78-81 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishIchornVFX.cs:194` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (4–8 lines × 3) Content/LegendWeapon/HalibutLegend/FishSkills/FishVariegatedLard.cs:316 — Content/LegendWeapon/HalibutLegend/FishSkills/FishVariegatedLard.cs:316-319 | Content/LegendWeapon/HalibutLegend/FishSkills/FishVariegatedLard.cs:553-560 | Content/LegendWeapon/HalibutLegend/FishSkills/FishVariegatedLard.cs:590-597 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishVariegatedLard.cs:316` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (7 lines × 12) · ×2
  • Duplicated block (7 lines × 12) Content/GameModes/BrutalMobs/Ambience/Ashreign/Projectiles/AshreignMagmaBeadProj.cs:160 — Content/GameModes/BrutalMobs/Ambience/Ashreign/Projectiles/AshreignMagmaBeadProj.cs:160-166 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhImpFireBolt.cs:78-84 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhScytheBolt.cs:79-85 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhShellSpike.cs:70-76 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhStingerBolt.cs:79-85 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhTridentBolt.cs:78-84 | Content/GameModes/BrutalMobs/Sky/Projectiles/SkyFeatherBolt.cs:72-78 | Content/GameModes/BrutalMobs/SlimeKin/Projectiles/SlimeGelBomb.cs:196-202 | Content/Items/Magic/AriaofTheCosmoses/AriaQSkill.cs:296-302 | Content/LegendWeapon/HalibutLegend/FishSkills/FishotroningVFX.cs:175-181 | Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Projectiles/BrainBloodShard.cs:122-128 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Projectiles/BrutalBeeStinger.cs:83-89 — before extracting anything, compare `Content/GameModes/BrutalMobs/Ambience/Ashreign/Projectiles/AshreignMagmaBeadProj.cs` and `Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhShellSpike.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/Ashreign/Projectiles/AshreignMagmaBeadProj.cs:160` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Projectiles/BrainBloodShard.cs:118` calls `Clamp`, `Length`, `Vector2` and `Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhImpFireBolt.cs:75` 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 × 12) Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:318 — Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:318-324 | Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzBeamProj.cs:267-273 | Content/Items/Magic/CommandersStaff.cs:349-355 | Content/Items/Melee/Heartcarver.cs:507-513 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:273-279 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs:325-331 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:222-228 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordRayRender.cs:40-46 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenGaleFieldProj.cs:113-119 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenPrismBeamProj.cs:282-288 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofRetinaScanBeam.cs:229-236 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofRotBeamProj.cs:159-166 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 12 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 12 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofRetinaScanBeam.cs:239` calls `Pow`, `Abs` and `Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:327` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (6–7 lines × 9) · ×2
  • Duplicated block (6–7 lines × 9) Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdBoltProj.cs:168 — Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdBoltProj.cs:168-174 | Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs:86-91 | Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgSnowShardProj.cs:88-93 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmSnowballProj.cs:118-123 | Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyMaggotBolt.cs:120-125 | Content/GameModes/BrutalMobs/Martians/Projectiles/MrtWrenchProj.cs:172-178 | Content/Items/BloomArsenal.cs:121-126 | Content/NPCs/BloomsandSerpents/Projectiles/BssPetalProj.cs:81-86 | Content/NPCs/BloomsandSerpents/Projectiles/BssWindPetalProj.cs:100-105 — before extracting anything, compare `Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdBoltProj.cs` and `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs:86` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6–7 lines × 9) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:488 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:488-494 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:408-414 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:367-373 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:432-438 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:539-545 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:546-551 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:473-478 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:409-415 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:477-483 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 9 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 9 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:488` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (5–7 lines × 2) · ×2
  • Duplicated block (5–7 lines × 2) Content/GameModes/GodSmith/Weapons/Broadswords/GsStarWrath.cs:373 — Content/GameModes/GodSmith/Weapons/Broadswords/GsStarWrath.cs:373-379 | Content/Items/Magic/Elysiums/Revelations/CelestialMeteor.cs:96-100 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/Broadswords/GsStarWrath.cs:373` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (5–7 lines × 2) Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadCommandCore.cs:399 — Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadCommandCore.cs:399-403 | Content/Items/Accessories/GodslayerScabbard.cs:272-278 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadCommandCore.cs:399` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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.
D4 · Code Duplication · Duplicated block (6 lines × 23) · ×2
  • Duplicated block (6 lines × 23) Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs:111 — Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs:111-116 | Content/Industrials/ElectricPowers/HealingStations/HealStationTile.cs:118-123 | Content/Industrials/ElectricPowers/Incinerators/IncineratorTile.cs:103-108 | Content/Industrials/ElectricPowers/LifeWeavers/LifeWeaverTile.cs:64-69 | Content/Industrials/ElectricPowers/LifeWeavers/WGGLifeWeaver.cs:116-121 | Content/Industrials/ElectricPowers/Lumberjacks/LumberjackTile.cs:63-68 | Content/Industrials/ElectricPowers/Lumberjacks/WGGLumberjack.cs:111-116 | Content/Industrials/ElectricPowers/MiningMachines/BaseMiningMachineTP.cs:431-436 | Content/Industrials/ElectricPowers/ShieldGenerators/ShieldGeneratorTile.cs:118-123 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatTile.cs:117-122 | Content/Industrials/ElectricPowers/Spectrometers/Spectrometer.cs:107-112 | Content/Industrials/ElectricPowers/Suppressors/PacifierTowerTile.cs:118-123 | Content/Industrials/ElectricPowers/Turrets/CryoTurrets/CryoTurretTile.cs:118-123 | Content/Industrials/ElectricPowers/Turrets/FlameTurrets/FlameTurretTile.cs:118-123 | Content/Industrials/ElectricPowers/Turrets/LaserTurrets/LaserTurretTile.cs:118-123 | Content/Industrials/ElectricPowers/WeatherControllers/WeatherControllerTile.cs:127-132 | Content/Industrials/Generator/Biomass/BiomassGenerator.cs:136-141 | Content/Industrials/Generator/Thermal/ThermalGenerator.cs:102-107 | Content/Industrials/Generator/Thermal/ThermalGeneratorMK2.cs:102-107 | Content/Items/Placeable/HoChaMeditatorItem.cs:80-85 | Content/Items/Placeable/StarflowPlatedBlock.cs:79-84 | Content/Scenarios/Draedon/Quest/DeploySignaltowers/CQETConstructor.cs:114-119 | Content/Tiles/NeutronStarIngotTile.cs:48-53 — before extracting anything, compare `Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs` and `Content/Industrials/ElectricPowers/Incinerators/IncineratorTile.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs:111` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Industrials/ElectricPowers/HealingStations/HealStationTile.cs:124` calls `Draw`, `Rectangle` and `Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs:117` does not — after which the two agree again for 3 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 (6 lines × 23) Content/Items/Accessories/ArcaneThroneOfEternity.cs:176 — Content/Items/Accessories/ArcaneThroneOfEternity.cs:176-182 | Content/Items/Accessories/ArcaneThroneOfEternity.cs:323-329 | Content/Items/Accessories/ArcaneThroneOfEternity.cs:454-460 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDetonationProj.cs:203-209 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberShockwaveProj.cs:89-95 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberFreezeWaveProj.cs:82-88 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Restart/CyberRestartProj.cs:210-216 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberPixelDecomposeProj.cs:83-89 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberReformProj.cs:89-95 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/HeavyBarrelModule.cs:315-321 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/HypersonicBarrelModule.cs:208-214 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/RapidBarrelModule.cs:656-662 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/ScattershotBarrelModule.cs:381-387 | Content/LegendWeapon/SHPCLegend/Modules/Frame/ResonanceFrameModule.cs:693-700 | Content/LegendWeapon/SHPCLegend/Modules/Optic/HoloOpticModule.cs:193-199 | Content/LegendWeapon/SHPCLegend/Modules/Optic/PrecisionOpticModule.cs:236-242 | Content/LegendWeapon/SHPCLegend/Modules/Optic/SniperOpticModule.cs:402-408 | Content/LegendWeapon/SHPCLegend/Modules/Optic/SniperOpticModule.cs:615-621 | Content/LegendWeapon/SHPCLegend/Modules/Power/PlasmaInjectorModule.cs:165-171 | Content/LegendWeapon/SHPCLegend/Modules/Stock/BraceStockModule.cs:487-493 | Content/LegendWeapon/SHPCLegend/Modules/Stock/ExtenderStockModule.cs:433-439 | Content/NPCs/TBUGs/TBUGRiftPortalProj.cs:366-371 | Content/NPCs/Victors/VictorRiftPortalProj.cs:555-560 — before extracting anything, compare `Content/Items/Accessories/ArcaneThroneOfEternity.cs` and `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDetonationProj.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 112 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (5–6 lines × 3) · ×2
  • Duplicated block (5–6 lines × 3) Content/Items/Magic/UnderTheSand.cs:309 — Content/Items/Magic/UnderTheSand.cs:309-314 | Content/Items/Ranged/RaiderGun.cs:471-475 | Content/Items/Tools/FungalFeed.cs:122-126 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/UnderTheSand.cs:309` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (5–6 lines × 3) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:2564 — Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:2564-2569 | Content/Scenarios/Kiyume/NPCs/ShallowHandsYokai.cs:294-298 | Content/Scenarios/Kiyume/NPCs/WellHandYokai.cs:349-354 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:2564` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:2569` calls `Vector2`, `NextFloat` and `Content/Scenarios/Kiyume/NPCs/ShallowHandsYokai.cs:298` 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.
D4 · Code Duplication · Duplicated block (4–6 lines × 4) · ×2
  • Duplicated block (4–6 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:439 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:439-444 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:495-498 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:409-414 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:348-354 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:439` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:439` calls `Vector2`, `NextFloat` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:495` 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 (4–6 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:957 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:957-962 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1516-1519 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1680-1685 | Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:2510-2515 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:957` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (3–6 lines × 4) · ×2
  • Duplicated block (3–6 lines × 4) Content/Items/Melee/DestroyersBladeEXs/DestroyerBiteProj.cs:294 — Content/Items/Melee/DestroyersBladeEXs/DestroyerBiteProj.cs:294-296 | Content/Items/Melee/DestroyersBladeEXs/DestroyerHeadMissile.cs:134-139 | Content/Items/Melee/DestroyersBladeEXs/DestroyerShadowBolt.cs:165-170 | Content/Items/Melee/DestroyersBladeEXs/DestroyersBeamEX.cs:98-101 — 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 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DestroyersBladeEXs/DestroyerHeadMissile.cs:134` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Melee/DestroyersBladeEXs/DestroyerHeadMissile.cs:139` calls `NextVector2Circular`, `NextBool`, `Color` and `Content/Items/Melee/DestroyersBladeEXs/DestroyerBiteProj.cs:296` 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 (3–6 lines × 4) Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:546 — Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:546-552 | Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:1038-1040 | Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:1121-1123 | Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:1137-1142 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:546` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:1123` calls `NextFloat`, `Configure`, `Next` and `Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:1142` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (4–5 lines × 5) · ×2
  • Duplicated block (4–5 lines × 5) Content/Narrative/Presentation/Skins/Brimstone/BrimstoneDialogueSkin.cs:34 — Content/Narrative/Presentation/Skins/Brimstone/BrimstoneDialogueSkin.cs:34-38 | Content/Narrative/Presentation/Skins/Sea/SeaDialogueSkin.cs:31-35 | Content/Narrative/Presentation/Skins/StarStream/StarStreamDialogueSkin.cs:34-39 | Content/Narrative/Presentation/Skins/Sulfsea/SulfseaDialogueSkin.cs:33-37 | Content/Narrative/Presentation/Skins/Tzeentch/TzeentchDialogueSkin.cs:38-41 — before extracting anything, compare `Content/Narrative/Presentation/Skins/Brimstone/BrimstoneDialogueSkin.cs` and `Content/Narrative/Presentation/Skins/Sea/SeaDialogueSkin.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Narrative/Presentation/Skins/Brimstone/BrimstoneDialogueSkin.cs:34` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (4–5 lines × 5) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:567 — Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:567-572 | Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:1571-1575 | Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:2583-2586 | Content/Scenarios/Kiyume/NPCs/WellHandYokai.cs:252-255 | Content/Scenarios/Kiyume/NPCs/WellHandYokai.cs:277-280 — there are 5 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 5 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:567` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Scenarios/Kiyume/NPCs/WellHandYokai.cs:257` calls `SetHandState`, `Vector2` and `Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:2587` 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.
D4 · Code Duplication · Duplicated block (3–5 lines × 4) · ×2
  • Duplicated block (3–5 lines × 4) Content/Industrials/MaterialFlow/Fluids/FluidVFX.cs:46 — Content/Industrials/MaterialFlow/Fluids/FluidVFX.cs:46-50 | Content/Industrials/MaterialFlow/Fluids/FluidVFX.cs:51-55 | Content/Industrials/MaterialFlow/Fluids/FluidVFX.cs:56-60 | Content/Industrials/MaterialFlow/Fluids/FluidVFX.cs:61-63 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/MaterialFlow/Fluids/FluidVFX.cs:46` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Industrials/MaterialFlow/Fluids/FluidVFX.cs:61` calls `Color` and `Content/Industrials/MaterialFlow/Fluids/FluidVFX.cs:63` does not — after which the two agree again for 3 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 (3–5 lines × 4) Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:640 — Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:640-644 | Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:681-685 | Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:565-567 | Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:697-699 — before extracting anything, compare `Content/QuestLogs/Styles/DraedonQuestLogStyle.cs` and `Content/QuestLogs/Styles/HotwindQuestLogStyle.cs` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 377 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. 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.
D4 · Code Duplication · Duplicated block (3–5 lines × 6) · ×2
  • Duplicated block (3–5 lines × 6) Content/Narrative/MusicToast.cs:371 — Content/Narrative/MusicToast.cs:371-373 | Content/Narrative/MusicToast.cs:429-431 | Content/Narrative/MusicToast.cs:505-507 | Content/Narrative/MusicToast.cs:538-540 | Content/Narrative/MusicToast.cs:565-569 | Content/Narrative/MusicToast.cs:642-646 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Narrative/MusicToast.cs:565` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Narrative/MusicToast.cs:425` calls `DrawDigitalGrid` and `Content/Narrative/MusicToast.cs:367` 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 (3–5 lines × 6) Content/LegendWeapon/HalibutLegend/FishSkills/FishObsidian.cs:361 — Content/LegendWeapon/HalibutLegend/FishSkills/FishObsidian.cs:361-364 | Content/LegendWeapon/HalibutLegend/FishSkills/Fishotroning.cs:1143-1145 | Content/Scenarios/Kiyume/NPCs/FacelessOneYokai.cs:359-363 | Content/Scenarios/Kiyume/NPCs/FuneralCortegeYokai.cs:1160-1163 | Content/Scenarios/Kiyume/NPCs/LanternGuideYokai.cs:430-434 | Content/Wraiths/Deaths/Performances/ShadeSeizurePerformance.cs:303-306 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/Fishotroning.cs:1143` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Scenarios/Kiyume/NPCs/FacelessOneYokai.cs:363` calls `Color`, `NextFloat` and `Content/Scenarios/Kiyume/NPCs/FuneralCortegeYokai.cs:1163` does not — after which the two agree again for 3 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.
D1 · Cyclomatic Complexity · CultistPlanetProj.AI (cyclomatic 97) · ×1
  • CultistPlanetProj.AI (cyclomatic 97) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistPlanetProj.cs:126 — CultistPlanetProj.AI has cyclomatic complexity 97 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaInkPour.AI (cyclomatic 77) · ×1
  • KikasaInkPour.AI (cyclomatic 77) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPour.cs:161 — KikasaInkPour.AI has cyclomatic complexity 77 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BssHubState.PickAttack (cyclomatic 75) · ×1
  • BssHubState.PickAttack (cyclomatic 75) Content/NPCs/BloomsandSerpents/States/BssHubState.cs:140 — BssHubState.PickAttack has cyclomatic complexity 75 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniSeverStrike.AcceptAuthoritySnapshot (cyclomatic 73) · ×1
  • OniSeverStrike.AcceptAuthoritySnapshot (cyclomatic 73) Content/LegendWeapon/OnikiriLegend/OniDismembers/OniSeverStrike.cs:936 — OniSeverStrike.AcceptAuthoritySnapshot has cyclomatic complexity 73 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ValidatePass.ApplyPass (cyclomatic 73) · ×1
  • ValidatePass.ApplyPass (cyclomatic 73) Content/Scenarios/Dungeonworld/Gen/Passes/ValidatePass.cs:21 — ValidatePass.ApplyPass has cyclomatic complexity 73 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SHPCUI.Update (cyclomatic 69) · ×1
  • SHPCUI.Update (cyclomatic 69) Content/LegendWeapon/SHPCLegend/UI/SHPCUI.cs:472 — SHPCUI.Update has cyclomatic complexity 69 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · HalibutPlayer.PostUpdate (cyclomatic 63) · ×1
  • HalibutPlayer.PostUpdate (cyclomatic 63) Content/LegendWeapon/HalibutLegend/HalibutPlayer.cs:351 — HalibutPlayer.PostUpdate has cyclomatic complexity 63 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaGunServant.UpdateGuns (cyclomatic 62) · ×1
  • KikasaGunServant.UpdateGuns (cyclomatic 62) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1040 — KikasaGunServant.UpdateGuns has cyclomatic complexity 62 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniMeiUI.UpdateInteraction (cyclomatic 61) · ×1
  • OniMeiUI.UpdateInteraction (cyclomatic 61) Content/LegendWeapon/OnikiriLegend/UI/OniMeiUI.cs:619 — OniMeiUI.UpdateInteraction has cyclomatic complexity 61 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaServantPlayer.LoadData (cyclomatic 60) · ×1
  • KikasaServantPlayer.LoadData (cyclomatic 60) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaServantPlayer.cs:579 — KikasaServantPlayer.LoadData has cyclomatic complexity 60 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OnikiriPlayer.PostUpdate (cyclomatic 60) · ×1
  • OnikiriPlayer.PostUpdate (cyclomatic 60) Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs:531 — OnikiriPlayer.PostUpdate has cyclomatic complexity 60 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · HadalValidatePass.ApplyPass (cyclomatic 59) · ×1
  • HadalValidatePass.ApplyPass (cyclomatic 59) Content/Scenarios/Hadalworld/Gen/Passes/HadalValidatePass.cs:17 — HadalValidatePass.ApplyPass has cyclomatic complexity 59 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaPanoramaUI.DrawHoverTipPanel (cyclomatic 58) · ×1
  • KikasaPanoramaUI.DrawHoverTipPanel (cyclomatic 58) Content/LegendWeapon/KikasaLegend/UI/Panorama/KikasaPanoramaUI.cs:2064 — KikasaPanoramaUI.DrawHoverTipPanel has cyclomatic complexity 58 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FssHubState.PickAttack (cyclomatic 53) · ×1
  • FssHubState.PickAttack (cyclomatic 53) Content/NPCs/FestersandSerpents/States/FssHubState.cs:140 — FssHubState.PickAttack has cyclomatic complexity 53 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · LegendTooltipPanel.Draw (cyclomatic 52) · ×1
  • LegendTooltipPanel.Draw (cyclomatic 52) Content/LegendWeapon/LegendTooltipLayout.cs:290 — LegendTooltipPanel.Draw 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.
D1 · Cyclomatic Complexity · RibbonDefinition.Validate (cyclomatic 52) · ×1
  • RibbonDefinition.Validate (cyclomatic 52) Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/Geometry/RibbonMesh.cs:94 — RibbonDefinition.Validate 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.
D1 · Cyclomatic Complexity · CultistConjunctionState.UpdateRelease (cyclomatic 52) · ×1
  • CultistConjunctionState.UpdateRelease (cyclomatic 52) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistConjunctionState.cs:149 — CultistConjunctionState.UpdateRelease 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.
D1 · Cyclomatic Complexity · AtlasSkillSea.Update (cyclomatic 50) · ×1
  • AtlasSkillSea.Update (cyclomatic 50) Content/LegendWeapon/HalibutLegend/UI/Atlas/AtlasSkillSea.cs:204 — AtlasSkillSea.Update has cyclomatic complexity 50 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaInkDrop.AI (cyclomatic 50) · ×1
  • KikasaInkDrop.AI (cyclomatic 50) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:197 — KikasaInkDrop.AI has cyclomatic complexity 50 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaQueenBeeServant.UpdateRake (cyclomatic 49) · ×1
  • KikasaQueenBeeServant.UpdateRake (cyclomatic 49) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:517 — KikasaQueenBeeServant.UpdateRake has cyclomatic complexity 49 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FishronVortexGrabState.OnUpdate (cyclomatic 49) · ×1
  • FishronVortexGrabState.OnUpdate (cyclomatic 49) Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronVortexGrabStates.cs:313 — FishronVortexGrabState.OnUpdate has cyclomatic complexity 49 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CultistUmbraShade.AI (cyclomatic 49) · ×1
  • CultistUmbraShade.AI (cyclomatic 49) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistUmbraShade.cs:278 — CultistUmbraShade.AI has cyclomatic complexity 49 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MLordLocomotion.Update (cyclomatic 49) · ×1
  • MLordLocomotion.Update (cyclomatic 49) Content/NPCs/BrutalNPCs/BrutalMoonLord/Core/MLordLocomotion.cs:260 — MLordLocomotion.Update has cyclomatic complexity 49 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DeepGaolWraith.UpdateCuffs (cyclomatic 48) · ×1
  • DeepGaolWraith.UpdateCuffs (cyclomatic 48) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:1642 — DeepGaolWraith.UpdateCuffs has cyclomatic complexity 48 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · HadalTerrainCarver.CarvePlain (cyclomatic 48) · ×1
  • HadalTerrainCarver.CarvePlain (cyclomatic 48) Content/Scenarios/Hadalworld/Gen/Core/HadalTerrainCarver.cs:204 — HadalTerrainCarver.CarvePlain has cyclomatic complexity 48 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OverhaulSettingsUI.Update (cyclomatic 48) · ×1
  • OverhaulSettingsUI.Update (cyclomatic 48) Content/UIs/OverhaulSettings/OverhaulSettingsUI.cs:175 — OverhaulSettingsUI.Update has cyclomatic complexity 48 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · TreeBlueprint.GenerateCommon (cyclomatic 47) · ×1
  • TreeBlueprint.GenerateCommon (cyclomatic 47) Content/Industrials/ElectricPowers/TreeRegrowths/TreeBlueprint.cs:158 — TreeBlueprint.GenerateCommon has cyclomatic complexity 47 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ScrapLaserSweepState.OnUpdate (cyclomatic 47) · ×1
  • ScrapLaserSweepState.OnUpdate (cyclomatic 47) Content/NPCs/ScrapCommanders/States/ScrapLaserSweepState.cs:44 — ScrapLaserSweepState.OnUpdate has cyclomatic complexity 47 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ScrapIntroState.OnUpdate (cyclomatic 46) · ×1
  • ScrapIntroState.OnUpdate (cyclomatic 46) Content/NPCs/ScrapCommanders/States/ScrapIntroState.cs:56 — ScrapIntroState.OnUpdate has cyclomatic complexity 46 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · AshfallStratum.BuildChute (cyclomatic 46) · ×1
  • AshfallStratum.BuildChute (cyclomatic 46) Content/Scenarios/Dungeonworld/Gen/Zones/AshfallStratum.cs:314 — AshfallStratum.BuildChute has cyclomatic complexity 46 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · IndustrializationGen.SpawnWindGrivenGenerator (cyclomatic 46) · ×1
  • IndustrializationGen.SpawnWindGrivenGenerator (cyclomatic 46) Content/Structures/IndustrializationGen.cs:210 — IndustrializationGen.SpawnWindGrivenGenerator has cyclomatic complexity 46 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · AutoFisherUI.Update (cyclomatic 45) · ×1
  • AutoFisherUI.Update (cyclomatic 45) Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs:136 — AutoFisherUI.Update has cyclomatic complexity 45 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CrimsonSweepSlash.UpdateBladePose (cyclomatic 45) · ×1
  • CrimsonSweepSlash.UpdateBladePose (cyclomatic 45) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:609 — CrimsonSweepSlash.UpdateBladePose has cyclomatic complexity 45 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · HackNetworkTarget.TryCapture (cyclomatic 44) · ×1
  • HackNetworkTarget.TryCapture (cyclomatic 44) Content/HackTimes/HackTimeNetSync.cs:212 — HackNetworkTarget.TryCapture has cyclomatic complexity 44 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ScorpionSentry.AI (cyclomatic 44) · ×1
  • ScorpionSentry.AI (cyclomatic 44) Content/LegendWeapon/HalibutLegend/FishSkills/FishScorpio.cs:174 — ScorpionSentry.AI has cyclomatic complexity 44 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KiyumeVillage.BuildInterior (cyclomatic 44) · ×1
  • KiyumeVillage.BuildInterior (cyclomatic 44) Content/Scenarios/Kiyume/Gen/KiyumeVillage.cs:276 — KiyumeVillage.BuildInterior has cyclomatic complexity 44 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · PrismgladeJudgmentProj.AI (cyclomatic 43) · ×1
  • PrismgladeJudgmentProj.AI (cyclomatic 43) Content/GameModes/BrutalMobs/Ambience/Prismglade/Projectiles/PrismgladeJudgmentProj.cs:99 — PrismgladeJudgmentProj.AI has cyclomatic complexity 43 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniSigilUI.UpdateInteraction (cyclomatic 43) · ×1
  • OniSigilUI.UpdateInteraction (cyclomatic 43) Content/LegendWeapon/OnikiriLegend/UI/OniSigilUI.cs:339 — OniSigilUI.UpdateInteraction has cyclomatic complexity 43 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · L3MazeBlock.Build (cyclomatic 43) · ×1
  • L3MazeBlock.Build (cyclomatic 43) Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3MazeBlock.cs:101 — L3MazeBlock.Build has cyclomatic complexity 43 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CrusherUI.Update (cyclomatic 42) · ×1
  • CrusherUI.Update (cyclomatic 42) Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:133 — CrusherUI.Update has cyclomatic complexity 42 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · IncineratorUI.Update (cyclomatic 42) · ×1
  • IncineratorUI.Update (cyclomatic 42) Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:139 — IncineratorUI.Update has cyclomatic complexity 42 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · RecyclerUI.Update (cyclomatic 42) · ×1
  • RecyclerUI.Update (cyclomatic 42) Content/Industrials/ElectricPowers/Recyclers/RecyclerUI.cs:134 — RecyclerUI.Update has cyclomatic complexity 42 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaPanoramaUI.Update (cyclomatic 42) · ×1
  • KikasaPanoramaUI.Update (cyclomatic 42) Content/LegendWeapon/KikasaLegend/UI/Panorama/KikasaPanoramaUI.cs:369 — KikasaPanoramaUI.Update has cyclomatic complexity 42 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DrownedCulverts.BuildBelt (cyclomatic 42) · ×1
  • DrownedCulverts.BuildBelt (cyclomatic 42) Content/Scenarios/Dungeonworld/Gen/Zones/DrownedCulverts.cs:91 — DrownedCulverts.BuildBelt has cyclomatic complexity 42 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · Undrowned.UpdateDeath (cyclomatic 42) · ×1
  • Undrowned.UpdateDeath (cyclomatic 42) Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:1555 — Undrowned.UpdateDeath has cyclomatic complexity 42 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · AutoCrafterUI.Update (cyclomatic 41) · ×1
  • AutoCrafterUI.Update (cyclomatic 41) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:152 — AutoCrafterUI.Update has cyclomatic complexity 41 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ShimmerTransmuterUI.Update (cyclomatic 41) · ×1
  • ShimmerTransmuterUI.Update (cyclomatic 41) Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterUI.cs:137 — ShimmerTransmuterUI.Update has cyclomatic complexity 41 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaSkeletronServant.UpdateHands (cyclomatic 41) · ×1
  • KikasaSkeletronServant.UpdateHands (cyclomatic 41) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1050 — KikasaSkeletronServant.UpdateHands has cyclomatic complexity 41 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SkeletronPalmSnatchState.AuthorityUpdate (cyclomatic 41) · ×1
  • SkeletronPalmSnatchState.AuthorityUpdate (cyclomatic 41) Content/NPCs/BrutalNPCs/BrutalSkeletron/States/SkeletronPalmSnatchState.cs:141 — SkeletronPalmSnatchState.AuthorityUpdate has cyclomatic complexity 41 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · LanternBoyProj.TryApplyAuthorityImpact (cyclomatic 41) · ×1
  • LanternBoyProj.TryApplyAuthorityImpact (cyclomatic 41) Content/Wraiths/Projectiles/LanternBoyProj.cs:248 — LanternBoyProj.TryApplyAuthorityImpact has cyclomatic complexity 41 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaBowServant.UpdateBows (cyclomatic 40) · ×1
  • KikasaBowServant.UpdateBows (cyclomatic 40) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:864 — KikasaBowServant.UpdateBows has cyclomatic complexity 40 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FishronMaelstromState.OnUpdate (cyclomatic 40) · ×1
  • FishronMaelstromState.OnUpdate (cyclomatic 40) Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronMaelstromState.cs:72 — FishronMaelstromState.OnUpdate has cyclomatic complexity 40 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CultistEclipseDragon.AI (cyclomatic 40) · ×1
  • CultistEclipseDragon.AI (cyclomatic 40) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistEclipseDragon.cs:80 — CultistEclipseDragon.AI has cyclomatic complexity 40 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · TheHungryAI.UpdateTetherMode (cyclomatic 40) · ×1
  • TheHungryAI.UpdateTetherMode (cyclomatic 40) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/TheHungryAI.cs:94 — TheHungryAI.UpdateTetherMode has cyclomatic complexity 40 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KiyumeHound.UpdatePresentation (cyclomatic 40) · ×1
  • KiyumeHound.UpdatePresentation (cyclomatic 40) Content/Scenarios/Kiyume/NPCs/KiyumeHound.cs:826 — KiyumeHound.UpdatePresentation has cyclomatic complexity 40 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OldNetICEDirector.PostUpdateNPCs (cyclomatic 40) · ×1
  • OldNetICEDirector.PostUpdateNPCs (cyclomatic 40) Content/Scenarios/OldNet/NPCs/OldNetICEDirector.cs:147 — OldNetICEDirector.PostUpdateNPCs has cyclomatic complexity 40 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SensorUI.Update (cyclomatic 39) · ×1
  • SensorUI.Update (cyclomatic 39) Content/Industrials/ElectricPowers/Sensors/SensorUI.cs:88 — SensorUI.Update has cyclomatic complexity 39 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaQueenSlimeServant.UpdateDive (cyclomatic 39) · ×1
  • KikasaQueenSlimeServant.UpdateDive (cyclomatic 39) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:636 — KikasaQueenSlimeServant.UpdateDive has cyclomatic complexity 39 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CrimsonRendSlash.UpdateBladePose (cyclomatic 39) · ×1
  • CrimsonRendSlash.UpdateBladePose (cyclomatic 39) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:808 — CrimsonRendSlash.UpdateBladePose has cyclomatic complexity 39 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SteadyStockModule.OnPlayerUpdate (cyclomatic 39) · ×1
  • SteadyStockModule.OnPlayerUpdate (cyclomatic 39) Content/LegendWeapon/SHPCLegend/Modules/Stock/SteadyStockModule.cs:116 — SteadyStockModule.OnPlayerUpdate has cyclomatic complexity 39 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · HadalDecorPass.ApplyPass (cyclomatic 39) · ×1
  • HadalDecorPass.ApplyPass (cyclomatic 39) Content/Scenarios/Hadalworld/Gen/Passes/HadalDecorPass.cs:16 — HadalDecorPass.ApplyPass has cyclomatic complexity 39 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ApiaryUI.Update (cyclomatic 38) · ×1
  • ApiaryUI.Update (cyclomatic 38) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:123 — ApiaryUI.Update has cyclomatic complexity 38 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CollectorUI.Update (cyclomatic 38) · ×1
  • CollectorUI.Update (cyclomatic 38) Content/Industrials/ElectricPowers/Collectors/CollectorUI.cs:188 — CollectorUI.Update has cyclomatic complexity 38 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · HerbFarmerUI.Update (cyclomatic 38) · ×1
  • HerbFarmerUI.Update (cyclomatic 38) Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs:131 — HerbFarmerUI.Update has cyclomatic complexity 38 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaRainRender.DrawBloodBodies (cyclomatic 38) · ×1
  • KikasaRainRender.DrawBloodBodies (cyclomatic 38) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:102 — KikasaRainRender.DrawBloodBodies has cyclomatic complexity 38 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SHPCNPCEffects.PreAI (cyclomatic 38) · ×1
  • SHPCNPCEffects.PreAI (cyclomatic 38) Content/LegendWeapon/SHPCLegend/Cyberspaces/SHPCNPCEffects.cs:432 — SHPCNPCEffects.PreAI has cyclomatic complexity 38 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EowSplitPincerState.UpdatePincer (cyclomatic 38) · ×1
  • EowSplitPincerState.UpdatePincer (cyclomatic 38) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowSplitPincerState.cs:207 — EowSplitPincerState.UpdatePincer has cyclomatic complexity 38 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · L4Content.TryBuild (cyclomatic 38) · ×1
  • L4Content.TryBuild (cyclomatic 38) Content/Scenarios/Dungeonworld/Gen/Layers/L4/L4Content.cs:248 — L4Content.TryBuild has cyclomatic complexity 38 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaBladeServant.UpdateBlades (cyclomatic 37) · ×1
  • KikasaBladeServant.UpdateBlades (cyclomatic 37) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:787 — KikasaBladeServant.UpdateBlades has cyclomatic complexity 37 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaKingSlimeServant.UpdateDissolve (cyclomatic 37) · ×1
  • KikasaKingSlimeServant.UpdateDissolve (cyclomatic 37) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:904 — KikasaKingSlimeServant.UpdateDissolve has cyclomatic complexity 37 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DeerclopsEyeGrabState.DriveBossPresentation (cyclomatic 37) · ×1
  • DeerclopsEyeGrabState.DriveBossPresentation (cyclomatic 37) Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsEyeGrabState.cs:119 — DeerclopsEyeGrabState.DriveBossPresentation has cyclomatic complexity 37 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SeaShrimpHubState.PickAttack (cyclomatic 37) · ×1
  • SeaShrimpHubState.PickAttack (cyclomatic 37) Content/NPCs/SeaShrimp/States/SeaShrimpHubState.cs:86 — SeaShrimpHubState.PickAttack has cyclomatic complexity 37 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DrownedTurnkey.UpdateBurst (cyclomatic 37) · ×1
  • DrownedTurnkey.UpdateBurst (cyclomatic 37) Content/Scenarios/Dungeonworld/NPCs/Elites/DrownedTurnkey.cs:454 — DrownedTurnkey.UpdateBurst has cyclomatic complexity 37 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CWRRef.BulkRestoreCalamityFlagsOr (cyclomatic 36) · ×1
  • CWRRef.BulkRestoreCalamityFlagsOr (cyclomatic 36) CWRRef.cs:1017 — CWRRef.BulkRestoreCalamityFlagsOr 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.
D1 · Cyclomatic Complexity · DraedonManagerStyle.DrawQuestEntry (cyclomatic 36) · ×1
  • DraedonManagerStyle.DrawQuestEntry (cyclomatic 36) Content/EntrustManager/Styles/DraedonManagerStyle.cs:405 — DraedonManagerStyle.DrawQuestEntry 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.
D1 · Cyclomatic Complexity · ForestManagerStyle.DrawQuestEntry (cyclomatic 36) · ×1
  • ForestManagerStyle.DrawQuestEntry (cyclomatic 36) Content/EntrustManager/Styles/ForestManagerStyle.cs:414 — ForestManagerStyle.DrawQuestEntry 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.
D1 · Cyclomatic Complexity · HotwindManagerStyle.DrawQuestEntry (cyclomatic 36) · ×1
  • HotwindManagerStyle.DrawQuestEntry (cyclomatic 36) Content/EntrustManager/Styles/HotwindManagerStyle.cs:403 — HotwindManagerStyle.DrawQuestEntry 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.
D1 · Cyclomatic Complexity · HackStatusDisplay.Draw (cyclomatic 36) · ×1
  • HackStatusDisplay.Draw (cyclomatic 36) Content/HackTimes/HackStatusDisplay.cs:37 — HackStatusDisplay.Draw 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.
D1 · Cyclomatic Complexity · HackTimeNetSync.ValidateAuthorityRequest (cyclomatic 36) · ×1
  • HackTimeNetSync.ValidateAuthorityRequest (cyclomatic 36) Content/HackTimes/HackTimeNetSync.cs:671 — HackTimeNetSync.ValidateAuthorityRequest 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.
D1 · Cyclomatic Complexity · KikasaOnikiriServant.UpdateBlade (cyclomatic 36) · ×1
  • KikasaOnikiriServant.UpdateBlade (cyclomatic 36) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:805 — KikasaOnikiriServant.UpdateBlade 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.
D1 · Cyclomatic Complexity · KikasaPrimeServant.UpdateDart (cyclomatic 36) · ×1
  • KikasaPrimeServant.UpdateDart (cyclomatic 36) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:555 — KikasaPrimeServant.UpdateDart 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.
D1 · Cyclomatic Complexity · OniSlash.UpdateBladePose (cyclomatic 36) · ×1
  • OniSlash.UpdateBladePose (cyclomatic 36) Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:764 — OniSlash.UpdateBladePose 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.
D1 · Cyclomatic Complexity · OniMeiCodexUI.UpdateInteraction (cyclomatic 36) · ×1
  • OniMeiCodexUI.UpdateInteraction (cyclomatic 36) Content/LegendWeapon/OnikiriLegend/UI/OniMeiCodexUI.cs:340 — OniMeiCodexUI.UpdateInteraction 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.
D1 · Cyclomatic Complexity · DraedonQuestLogStyle.DrawDetailContent (cyclomatic 36) · ×1
  • DraedonQuestLogStyle.DrawDetailContent (cyclomatic 36) Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:398 — DraedonQuestLogStyle.DrawDetailContent 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.
D1 · Cyclomatic Complexity · L3Content.PlaceDeckRooms (cyclomatic 36) · ×1
  • L3Content.PlaceDeckRooms (cyclomatic 36) Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Content.cs:277 — L3Content.PlaceDeckRooms 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.
D1 · Cyclomatic Complexity · Undrowned.UpdateAnchorThrow (cyclomatic 36) · ×1
  • Undrowned.UpdateAnchorThrow (cyclomatic 36) Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:820 — Undrowned.UpdateAnchorThrow 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.
D1 · Cyclomatic Complexity · BlessingWheelUI.Update (cyclomatic 35) · ×1
  • BlessingWheelUI.Update (cyclomatic 35) Content/GameModes/Blessings/UI/BlessingWheelUI.cs:125 — BlessingWheelUI.Update has cyclomatic complexity 35 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SlimeVatUI.Update (cyclomatic 35) · ×1
  • SlimeVatUI.Update (cyclomatic 35) Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:125 — SlimeVatUI.Update has cyclomatic complexity 35 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaGolemServant.UpdateSlam (cyclomatic 35) · ×1
  • KikasaGolemServant.UpdateSlam (cyclomatic 35) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:516 — KikasaGolemServant.UpdateSlam has cyclomatic complexity 35 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaHudLead.DrawOverlay (cyclomatic 35) · ×1
  • KikasaHudLead.DrawOverlay (cyclomatic 35) Content/LegendWeapon/KikasaLegend/UI/KikasaHudLead.cs:549 — KikasaHudLead.DrawOverlay has cyclomatic complexity 35 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CrimsonSweepSlash.UpdateCombo (cyclomatic 35) · ×1
  • CrimsonSweepSlash.UpdateCombo (cyclomatic 35) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:422 — CrimsonSweepSlash.UpdateCombo has cyclomatic complexity 35 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniSlash.UpdateCombo (cyclomatic 35) · ×1
  • OniSlash.UpdateCombo (cyclomatic 35) Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:548 — OniSlash.UpdateCombo has cyclomatic complexity 35 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniDomainEye.Update (cyclomatic 35) · ×1
  • OniDomainEye.Update (cyclomatic 35) Content/LegendWeapon/OnikiriLegend/UI/OniDomainEye.cs:71 — OniDomainEye.Update has cyclomatic complexity 35 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ErgonomicStockModule.OnPlayerUpdate (cyclomatic 35) · ×1
  • ErgonomicStockModule.OnPlayerUpdate (cyclomatic 35) Content/LegendWeapon/SHPCLegend/Modules/Stock/ErgonomicStockModule.cs:215 — ErgonomicStockModule.OnPlayerUpdate has cyclomatic complexity 35 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DeepGaolWraith.UpdateEmerge (cyclomatic 35) · ×1
  • DeepGaolWraith.UpdateEmerge (cyclomatic 35) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:484 — DeepGaolWraith.UpdateEmerge has cyclomatic complexity 35 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SandevistanPlayer.ApplySnapshot (cyclomatic 34) · ×1
  • SandevistanPlayer.ApplySnapshot (cyclomatic 34) Content/Cyberwares/Implementation/Sandevistans/SandevistanPlayer.cs:234 — SandevistanPlayer.ApplySnapshot has cyclomatic complexity 34 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EclStrikeOmen.AI (cyclomatic 34) · ×1
  • EclStrikeOmen.AI (cyclomatic 34) Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclStrikeOmen.cs:73 — EclStrikeOmen.AI has cyclomatic complexity 34 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · TreeBlueprint.GenerateWithSettings (cyclomatic 34) · ×1
  • TreeBlueprint.GenerateWithSettings (cyclomatic 34) Content/Industrials/ElectricPowers/TreeRegrowths/TreeBlueprint.cs:271 — TreeBlueprint.GenerateWithSettings has cyclomatic complexity 34 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ThermalGeneratorUI.UpdateElement (cyclomatic 34) · ×1
  • ThermalGeneratorUI.UpdateElement (cyclomatic 34) Content/Industrials/Generator/Thermal/ThermalGeneratorUI.cs:118 — ThermalGeneratorUI.UpdateElement has cyclomatic complexity 34 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaDeerclopsServant.UpdateEmerge (cyclomatic 34) · ×1
  • KikasaDeerclopsServant.UpdateEmerge (cyclomatic 34) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:319 — KikasaDeerclopsServant.UpdateEmerge has cyclomatic complexity 34 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaPlanteraServant.UpdateEmerge (cyclomatic 34) · ×1
  • KikasaPlanteraServant.UpdateEmerge (cyclomatic 34) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:399 — KikasaPlanteraServant.UpdateEmerge has cyclomatic complexity 34 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaTwinsServant.UpdateScissor (cyclomatic 34) · ×1
  • KikasaTwinsServant.UpdateScissor (cyclomatic 34) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:527 — KikasaTwinsServant.UpdateScissor has cyclomatic complexity 34 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CrimsonRendSlash.UpdateCombo (cyclomatic 34) · ×1
  • CrimsonRendSlash.UpdateCombo (cyclomatic 34) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:612 — CrimsonRendSlash.UpdateCombo has cyclomatic complexity 34 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OnikiriPlayer.TryDash (cyclomatic 34) · ×1
  • OnikiriPlayer.TryDash (cyclomatic 34) Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs:940 — OnikiriPlayer.TryDash has cyclomatic complexity 34 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SakuraKiriRenderer.Draw (cyclomatic 34) · ×1
  • SakuraKiriRenderer.Draw (cyclomatic 34) Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraKiriRenderer.cs:111 — SakuraKiriRenderer.Draw has cyclomatic complexity 34 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniMeiUI.LogicUpdate (cyclomatic 34) · ×1
  • OniMeiUI.LogicUpdate (cyclomatic 34) Content/LegendWeapon/OnikiriLegend/UI/OniMeiUI.cs:345 — OniMeiUI.LogicUpdate has cyclomatic complexity 34 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CyberChargeOrbProj.AI_Charging (cyclomatic 34) · ×1
  • CyberChargeOrbProj.AI_Charging (cyclomatic 34) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberChargeOrbProj.cs:212 — CyberChargeOrbProj.AI_Charging has cyclomatic complexity 34 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SHPCBraceRigProj.AI (cyclomatic 34) · ×1
  • SHPCBraceRigProj.AI (cyclomatic 34) Content/LegendWeapon/SHPCLegend/Modules/Stock/BraceStockModule.cs:242 — SHPCBraceRigProj.AI has cyclomatic complexity 34 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · Undrowned.UpdateFloodRite (cyclomatic 34) · ×1
  • Undrowned.UpdateFloodRite (cyclomatic 34) Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:1414 — Undrowned.UpdateFloodRite has cyclomatic complexity 34 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · HeadlessShadeProj.TryApplyAuthorityImpact (cyclomatic 34) · ×1
  • HeadlessShadeProj.TryApplyAuthorityImpact (cyclomatic 34) Content/Wraiths/Projectiles/HeadlessShadeProj.cs:550 — HeadlessShadeProj.TryApplyAuthorityImpact has cyclomatic complexity 34 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CyberSlotRenderer.DrawConnectors (cyclomatic 33) · ×1
  • CyberSlotRenderer.DrawConnectors (cyclomatic 33) Content/Cyberwares/UIs/CyberSlotRenderer.cs:256 — CyberSlotRenderer.DrawConnectors 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.
D1 · Cyclomatic Complexity · HackNetworkTarget.TryResolve (cyclomatic 33) · ×1
  • HackNetworkTarget.TryResolve (cyclomatic 33) Content/HackTimes/HackTimeNetSync.cs:133 — HackNetworkTarget.TryResolve 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.
D1 · Cyclomatic Complexity · PlayerLauncherUI.Update (cyclomatic 33) · ×1
  • PlayerLauncherUI.Update (cyclomatic 33) Content/Industrials/ElectricPowers/Launchers/PlayerLauncherUI.cs:124 — PlayerLauncherUI.Update 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.
D1 · Cyclomatic Complexity · BiomassGeneratorUI.UpdateElement (cyclomatic 33) · ×1
  • BiomassGeneratorUI.UpdateElement (cyclomatic 33) Content/Industrials/Generator/Biomass/BiomassGeneratorUI.cs:90 — BiomassGeneratorUI.UpdateElement 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.
D1 · Cyclomatic Complexity · DivineSourceBladeHeld.HandlePhaseEvents (cyclomatic 33) · ×1
  • DivineSourceBladeHeld.HandlePhaseEvents (cyclomatic 33) Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:436 — DivineSourceBladeHeld.HandlePhaseEvents 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.
D1 · Cyclomatic Complexity · HalibutSave.LoadData (cyclomatic 33) · ×1
  • HalibutSave.LoadData (cyclomatic 33) Content/LegendWeapon/HalibutLegend/HalibutSave.cs:387 — HalibutSave.LoadData 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.
D1 · Cyclomatic Complexity · AtlasDomainEyes.Update (cyclomatic 33) · ×1
  • AtlasDomainEyes.Update (cyclomatic 33) Content/LegendWeapon/HalibutLegend/UI/Atlas/AtlasDomainEyes.cs:71 — AtlasDomainEyes.Update 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.
D1 · Cyclomatic Complexity · KikasaSpearServant.UpdateSpears (cyclomatic 33) · ×1
  • KikasaSpearServant.UpdateSpears (cyclomatic 33) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:662 — KikasaSpearServant.UpdateSpears 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.
D1 · Cyclomatic Complexity · KikasaBrainServant.DrawGlow (cyclomatic 33) · ×1
  • KikasaBrainServant.DrawGlow (cyclomatic 33) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1380 — KikasaBrainServant.DrawGlow 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.
D1 · Cyclomatic Complexity · KikasaPlanteraServant.UpdatePounce (cyclomatic 33) · ×1
  • KikasaPlanteraServant.UpdatePounce (cyclomatic 33) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:887 — KikasaPlanteraServant.UpdatePounce 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.
D1 · Cyclomatic Complexity · KikasaPrimeServant.UpdateArms (cyclomatic 33) · ×1
  • KikasaPrimeServant.UpdateArms (cyclomatic 33) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:982 — KikasaPrimeServant.UpdateArms 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.
D1 · Cyclomatic Complexity · BssIntroState.OnUpdate (cyclomatic 33) · ×1
  • BssIntroState.OnUpdate (cyclomatic 33) Content/NPCs/BloomsandSerpents/States/BssIntroState.cs:69 — BssIntroState.OnUpdate 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.
D1 · Cyclomatic Complexity · FishronSharkronStrafeState.OnUpdate (cyclomatic 33) · ×1
  • FishronSharkronStrafeState.OnUpdate (cyclomatic 33) Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronSharkronStrafeState.cs:55 — FishronSharkronStrafeState.OnUpdate 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.
D1 · Cyclomatic Complexity · CrabulonCommandController.HandleInput (cyclomatic 33) · ×1
  • CrabulonCommandController.HandleInput (cyclomatic 33) Content/NPCs/Modifys/Crabulons/CrabulonUIs/CrabulonCommandUI.cs:137 — CrabulonCommandController.HandleInput 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.
D1 · Cyclomatic Complexity · DeepGaolWraith.UpdateAmbush (cyclomatic 33) · ×1
  • DeepGaolWraith.UpdateAmbush (cyclomatic 33) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:1332 — DeepGaolWraith.UpdateAmbush 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.
D1 · Cyclomatic Complexity · Undrowned.UpdateEmerge (cyclomatic 33) · ×1
  • Undrowned.UpdateEmerge (cyclomatic 33) Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:551 — Undrowned.UpdateEmerge 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.
D1 · Cyclomatic Complexity · BaseQuestAcceptUI.Update (cyclomatic 32) · ×1
  • BaseQuestAcceptUI.Update (cyclomatic 32) Content/EntrustManager/BaseQuestAcceptUI.cs:111 — BaseQuestAcceptUI.Update 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.
D1 · Cyclomatic Complexity · MushroomFarmerUI.Update (cyclomatic 32) · ×1
  • MushroomFarmerUI.Update (cyclomatic 32) Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:114 — MushroomFarmerUI.Update 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.
D1 · Cyclomatic Complexity · PotionBeaconUI.Update (cyclomatic 32) · ×1
  • PotionBeaconUI.Update (cyclomatic 32) Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconUI.cs:116 — PotionBeaconUI.Update 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.
D1 · Cyclomatic Complexity · OniHandMinion.AI (cyclomatic 32) · ×1
  • OniHandMinion.AI (cyclomatic 32) Content/Items/Melee/OniMacheteHands.cs:210 — OniHandMinion.AI 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.
D1 · Cyclomatic Complexity · AtlasSkillSea.DrawDock (cyclomatic 32) · ×1
  • AtlasSkillSea.DrawDock (cyclomatic 32) Content/LegendWeapon/HalibutLegend/UI/Atlas/AtlasSkillSea.cs:833 — AtlasSkillSea.DrawDock 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.
D1 · Cyclomatic Complexity · KikasaDrownFX.UpdateShow (cyclomatic 32) · ×1
  • KikasaDrownFX.UpdateShow (cyclomatic 32) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:428 — KikasaDrownFX.UpdateShow 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.
D1 · Cyclomatic Complexity · KikasaHud.DrawTooltipOverlay (cyclomatic 32) · ×1
  • KikasaHud.DrawTooltipOverlay (cyclomatic 32) Content/LegendWeapon/KikasaLegend/UI/KikasaHud.cs:786 — KikasaHud.DrawTooltipOverlay 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.
D1 · Cyclomatic Complexity · OnikiriTutorialRenderer.BuildAndDrawButtons (cyclomatic 32) · ×1
  • OnikiriTutorialRenderer.BuildAndDrawButtons (cyclomatic 32) Content/LegendWeapon/OnikiriLegend/Tutorial/OnikiriTutorialRenderer.cs:376 — OnikiriTutorialRenderer.BuildAndDrawButtons 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.
D1 · Cyclomatic Complexity · GolemTrapUnit.UpdateActive (cyclomatic 32) · ×1
  • GolemTrapUnit.UpdateActive (cyclomatic 32) Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemTrapUnit.cs:175 — GolemTrapUnit.UpdateActive 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.
D1 · Cyclomatic Complexity · GolemIntroState.OnUpdate (cyclomatic 32) · ×1
  • GolemIntroState.OnUpdate (cyclomatic 32) Content/NPCs/BrutalNPCs/BrutalGolem/States/GolemIntroState.cs:26 — GolemIntroState.OnUpdate 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.
D1 · Cyclomatic Complexity · GaolBossRoom.Place (cyclomatic 32) · ×1
  • GaolBossRoom.Place (cyclomatic 32) Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolBossRoom.cs:114 — GaolBossRoom.Place 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.
D1 · Cyclomatic Complexity · CybTutorialLead.UpdateUI (cyclomatic 32) · ×1
  • CybTutorialLead.UpdateUI (cyclomatic 32) Content/Scenarios/Shepel/CybCourses/CybTutorialLead.cs:126 — CybTutorialLead.UpdateUI 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.
D1 · Cyclomatic Complexity · IndustrializationGen.SpawnWGGCollectorTile (cyclomatic 32) · ×1
  • IndustrializationGen.SpawnWGGCollectorTile (cyclomatic 32) Content/Structures/IndustrializationGen.cs:72 — IndustrializationGen.SpawnWGGCollectorTile 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.
D1 · Cyclomatic Complexity · StationSnapshot.Scan (cyclomatic 31) · ×1
  • StationSnapshot.Scan (cyclomatic 31) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterRecipeId.cs:156 — StationSnapshot.Scan 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.
D1 · Cyclomatic Complexity · SolarCoreFistPlayer.PreUpdateMovement (cyclomatic 31) · ×1
  • SolarCoreFistPlayer.PreUpdateMovement (cyclomatic 31) Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFist.cs:202 — SolarCoreFistPlayer.PreUpdateMovement 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.
D1 · Cyclomatic Complexity · KikasaDeerclopsServant.UpdateFollow (cyclomatic 31) · ×1
  • KikasaDeerclopsServant.UpdateFollow (cyclomatic 31) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:508 — KikasaDeerclopsServant.UpdateFollow 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.
D1 · Cyclomatic Complexity · KikasaDestroyerServant.UpdateJet (cyclomatic 31) · ×1
  • KikasaDestroyerServant.UpdateJet (cyclomatic 31) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:529 — KikasaDestroyerServant.UpdateJet 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.
D1 · Cyclomatic Complexity · KikasaMoonLordServant.UpdateMoonRay (cyclomatic 31) · ×1
  • KikasaMoonLordServant.UpdateMoonRay (cyclomatic 31) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:769 — KikasaMoonLordServant.UpdateMoonRay 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.
D1 · Cyclomatic Complexity · KikasaTwinsServant.UpdateEyes (cyclomatic 31) · ×1
  • KikasaTwinsServant.UpdateEyes (cyclomatic 31) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:989 — KikasaTwinsServant.UpdateEyes 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.
D1 · Cyclomatic Complexity · PRT_CrimsonBloodStain.TryEnterStuck (cyclomatic 31) · ×1
  • PRT_CrimsonBloodStain.TryEnterStuck (cyclomatic 31) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendParticles.cs:269 — PRT_CrimsonBloodStain.TryEnterStuck 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.
D1 · Cyclomatic Complexity · OniDomainDeco.Draw (cyclomatic 31) · ×1
  • OniDomainDeco.Draw (cyclomatic 31) Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainDeco.cs:440 — OniDomainDeco.Draw 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.
D1 · Cyclomatic Complexity · OniTalismanHud.LogicUpdate (cyclomatic 31) · ×1
  • OniTalismanHud.LogicUpdate (cyclomatic 31) Content/LegendWeapon/OnikiriLegend/UI/OniTalismanHud.cs:232 — OniTalismanHud.LogicUpdate 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.
D1 · Cyclomatic Complexity · TwinsRenderHelper.DrawChargeEffect (cyclomatic 31) · ×1
  • TwinsRenderHelper.DrawChargeEffect (cyclomatic 31) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Rendering/TwinsRenderHelper.cs:14 — TwinsRenderHelper.DrawChargeEffect 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.
D1 · Cyclomatic Complexity · RetinazerSoloRageState.ExecuteLaserMatrix (cyclomatic 31) · ×1
  • RetinazerSoloRageState.ExecuteLaserMatrix (cyclomatic 31) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerSoloRageState.cs:401 — RetinazerSoloRageState.ExecuteLaserMatrix 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.
D1 · Cyclomatic Complexity · ScrapDeathState.OnUpdate (cyclomatic 31) · ×1
  • ScrapDeathState.OnUpdate (cyclomatic 31) Content/NPCs/ScrapCommanders/States/ScrapDeathState.cs:50 — ScrapDeathState.OnUpdate 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.
D1 · Cyclomatic Complexity · ForestQuestLogStyle.DrawDetailContent (cyclomatic 31) · ×1
  • ForestQuestLogStyle.DrawDetailContent (cyclomatic 31) Content/QuestLogs/Styles/ForestQuestLogStyle.cs:339 — ForestQuestLogStyle.DrawDetailContent 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.
D1 · Cyclomatic Complexity · HotwindQuestLogStyle.DrawDetailContent (cyclomatic 31) · ×1
  • HotwindQuestLogStyle.DrawDetailContent (cyclomatic 31) Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:334 — HotwindQuestLogStyle.DrawDetailContent 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.
D1 · Cyclomatic Complexity · L5Leviathan.BuildCavity (cyclomatic 31) · ×1
  • L5Leviathan.BuildCavity (cyclomatic 31) Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Leviathan.cs:311 — L5Leviathan.BuildCavity 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.
D1 · Cyclomatic Complexity · L6Content.PlaceAndBuildNode (cyclomatic 31) · ×1
  • L6Content.PlaceAndBuildNode (cyclomatic 31) Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Content.cs:223 — L6Content.PlaceAndBuildNode 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.
D1 · Cyclomatic Complexity · Z3Giant.BuildGiantAt (cyclomatic 31) · ×1
  • Z3Giant.BuildGiantAt (cyclomatic 31) Content/Scenarios/OldNet/Gen/Zones/Z3/Z3Giant.cs:59 — Z3Giant.BuildGiantAt 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.
D1 · Cyclomatic Complexity · FrostveilScreenFrostRender.EndCaptureDraw (cyclomatic 30) · ×1
  • FrostveilScreenFrostRender.EndCaptureDraw (cyclomatic 30) Content/GameModes/BrutalMobs/Ambience/Frostveil/FrostveilScreenFrostRender.cs:37 — FrostveilScreenFrostRender.EndCaptureDraw 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.
D1 · Cyclomatic Complexity · HollowdeepAmbience.InPureCave (cyclomatic 30) · ×1
  • HollowdeepAmbience.InPureCave (cyclomatic 30) Content/GameModes/BrutalMobs/Ambience/Hollowdeep/HollowdeepAmbience.cs:106 — HollowdeepAmbience.InPureCave 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.
D1 · Cyclomatic Complexity · GsChainGunHeld.AI (cyclomatic 30) · ×1
  • GsChainGunHeld.AI (cyclomatic 30) Content/GameModes/GodSmith/Weapons/Specials/GsChainGun.cs:86 — GsChainGunHeld.AI 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.
D1 · Cyclomatic Complexity · AutoCrafterTP.UpdateVisualFX (cyclomatic 30) · ×1
  • AutoCrafterTP.UpdateVisualFX (cyclomatic 30) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterTP.cs:328 — AutoCrafterTP.UpdateVisualFX 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.
D1 · Cyclomatic Complexity · AtlasDomainEyes.Draw (cyclomatic 30) · ×1
  • AtlasDomainEyes.Draw (cyclomatic 30) Content/LegendWeapon/HalibutLegend/UI/Atlas/AtlasDomainEyes.cs:202 — AtlasDomainEyes.Draw 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.
D1 · Cyclomatic Complexity · AtlasSkillSea.HandleMouseInput (cyclomatic 30) · ×1
  • AtlasSkillSea.HandleMouseInput (cyclomatic 30) Content/LegendWeapon/HalibutLegend/UI/Atlas/AtlasSkillSea.cs:351 — AtlasSkillSea.HandleMouseInput 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.
D1 · Cyclomatic Complexity · KikasaKingSlimeServant.UpdateSlam (cyclomatic 30) · ×1
  • KikasaKingSlimeServant.UpdateSlam (cyclomatic 30) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:604 — KikasaKingSlimeServant.UpdateSlam 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.
D1 · Cyclomatic Complexity · KikasaQueenSlimeServant.UpdateEmerge (cyclomatic 30) · ×1
  • KikasaQueenSlimeServant.UpdateEmerge (cyclomatic 30) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:281 — KikasaQueenSlimeServant.UpdateEmerge 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.
D1 · Cyclomatic Complexity · KikasaSkeletronServant.UpdateSpin (cyclomatic 30) · ×1
  • KikasaSkeletronServant.UpdateSpin (cyclomatic 30) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:715 — KikasaSkeletronServant.UpdateSpin 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.
D1 · Cyclomatic Complexity · SHPCRecycleCellRingProj.AI (cyclomatic 30) · ×1
  • SHPCRecycleCellRingProj.AI (cyclomatic 30) Content/LegendWeapon/SHPCLegend/Modules/Grip/EfficientGripModule.cs:362 — SHPCRecycleCellRingProj.AI 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.
D1 · Cyclomatic Complexity · HadalTerrainModel.Flood (cyclomatic 30) · ×1
  • HadalTerrainModel.Flood (cyclomatic 30) Content/Scenarios/Hadalworld/Gen/Core/HadalTerrainModel.cs:80 — HadalTerrainModel.Flood 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.
D1 · Cyclomatic Complexity · StratosFallingStarProj.AI (cyclomatic 29) · ×1
  • StratosFallingStarProj.AI (cyclomatic 29) Content/GameModes/BrutalMobs/Ambience/Stratos/Projectiles/StratosFallingStarProj.cs:99 — StratosFallingStarProj.AI 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.
D1 · Cyclomatic Complexity · SunkenduneSandfallProj.AI (cyclomatic 29) · ×1
  • SunkenduneSandfallProj.AI (cyclomatic 29) Content/GameModes/BrutalMobs/Ambience/Sunkendune/Projectiles/SunkenduneSandfallProj.cs:94 — SunkenduneSandfallProj.AI 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.
D1 · Cyclomatic Complexity · NightPackNPC.TryStart (cyclomatic 29) · ×1
  • NightPackNPC.TryStart (cyclomatic 29) Content/GameModes/BrutalMobs/NightPack/NightPackNPC.cs:166 — NightPackNPC.TryStart 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.
D1 · Cyclomatic Complexity · PlayerScannable.BuildScanData (cyclomatic 29) · ×1
  • PlayerScannable.BuildScanData (cyclomatic 29) Content/HackTimes/Scannables/PlayerScannable.cs:58 — PlayerScannable.BuildScanData 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.
D1 · Cyclomatic Complexity · CrusherTP.UpdateVisualFX (cyclomatic 29) · ×1
  • CrusherTP.UpdateVisualFX (cyclomatic 29) Content/Industrials/ElectricPowers/Crushers/CrusherTP.cs:196 — CrusherTP.UpdateVisualFX 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.
D1 · Cyclomatic Complexity · GeneratorReadoutUI.UpdateElement (cyclomatic 29) · ×1
  • GeneratorReadoutUI.UpdateElement (cyclomatic 29) Content/Industrials/Generator/GeneratorReadout.cs:124 — GeneratorReadoutUI.UpdateElement 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.
D1 · Cyclomatic Complexity · SolarCoreFistPlayer.UpdateVisualEnvelopes (cyclomatic 29) · ×1
  • SolarCoreFistPlayer.UpdateVisualEnvelopes (cyclomatic 29) Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFist.cs:368 — SolarCoreFistPlayer.UpdateVisualEnvelopes 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.
D1 · Cyclomatic Complexity · ShatterfangHeld.HandlePhaseEvents (cyclomatic 29) · ×1
  • ShatterfangHeld.HandlePhaseEvents (cyclomatic 29) Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:372 — ShatterfangHeld.HandlePhaseEvents 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.
D1 · Cyclomatic Complexity · HungryCompanionProjectile.AI (cyclomatic 29) · ×1
  • HungryCompanionProjectile.AI (cyclomatic 29) Content/LegendWeapon/HalibutLegend/FishSkills/FishHunger.cs:186 — HungryCompanionProjectile.AI 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.
D1 · Cyclomatic Complexity · KikasaFlailServant.UpdateHands (cyclomatic 29) · ×1
  • KikasaFlailServant.UpdateHands (cyclomatic 29) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:690 — KikasaFlailServant.UpdateHands 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.
D1 · Cyclomatic Complexity · KikasaKingSlimeServant.UpdateEmerge (cyclomatic 29) · ×1
  • KikasaKingSlimeServant.UpdateEmerge (cyclomatic 29) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:299 — KikasaKingSlimeServant.UpdateEmerge 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.
D1 · Cyclomatic Complexity · KikasaMoonVesselWhip.AI (cyclomatic 29) · ×1
  • KikasaMoonVesselWhip.AI (cyclomatic 29) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonVesselWhip.cs:73 — KikasaMoonVesselWhip.AI 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.
D1 · Cyclomatic Complexity · KikasaSkeletronServant.UpdateEmerge (cyclomatic 29) · ×1
  • KikasaSkeletronServant.UpdateEmerge (cyclomatic 29) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:331 — KikasaSkeletronServant.UpdateEmerge 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.
D1 · Cyclomatic Complexity · KikasaHud.Update (cyclomatic 29) · ×1
  • KikasaHud.Update (cyclomatic 29) Content/LegendWeapon/KikasaLegend/UI/KikasaHud.cs:264 — KikasaHud.Update 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.
D1 · Cyclomatic Complexity · CyberspacePlayer.Update (cyclomatic 29) · ×1
  • CyberspacePlayer.Update (cyclomatic 29) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspacePlayer.cs:437 — CyberspacePlayer.Update 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.
D1 · Cyclomatic Complexity · RapidBarrelModule.OnPlayerUpdate (cyclomatic 29) · ×1
  • RapidBarrelModule.OnPlayerUpdate (cyclomatic 29) Content/LegendWeapon/SHPCLegend/Modules/Barrel/RapidBarrelModule.cs:127 — RapidBarrelModule.OnPlayerUpdate 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.
D1 · Cyclomatic Complexity · BssBody.DrawSegment (cyclomatic 29) · ×1
  • BssBody.DrawSegment (cyclomatic 29) Content/NPCs/BloomsandSerpents/BssBody.cs:333 — BssBody.DrawSegment 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.
D1 · Cyclomatic Complexity · BssBurrowLungeState.OnUpdate (cyclomatic 29) · ×1
  • BssBurrowLungeState.OnUpdate (cyclomatic 29) Content/NPCs/BloomsandSerpents/States/BssBurrowLungeState.cs:53 — BssBurrowLungeState.OnUpdate 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.
D1 · Cyclomatic Complexity · DeerclopsSeizeHuntState.OnUpdate (cyclomatic 29) · ×1
  • DeerclopsSeizeHuntState.OnUpdate (cyclomatic 29) Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsSeizeHuntState.cs:71 — DeerclopsSeizeHuntState.OnUpdate 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.
D1 · Cyclomatic Complexity · ProbeAI.AI (cyclomatic 29) · ×1
  • ProbeAI.AI (cyclomatic 29) Content/NPCs/BrutalNPCs/BrutalDestroyer/ProbeAI.cs:30 — ProbeAI.AI 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.
D1 · Cyclomatic Complexity · FssMoltGrowthState.OnUpdate (cyclomatic 29) · ×1
  • FssMoltGrowthState.OnUpdate (cyclomatic 29) Content/NPCs/FestersandSerpents/States/FssMoltGrowthState.cs:47 — FssMoltGrowthState.OnUpdate 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.
D1 · Cyclomatic Complexity · ScrapCommander.DrawGlowLayer (cyclomatic 29) · ×1
  • ScrapCommander.DrawGlowLayer (cyclomatic 29) Content/NPCs/ScrapCommanders/ScrapCommander.cs:819 — ScrapCommander.DrawGlowLayer 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.
D1 · Cyclomatic Complexity · SeaShrimpBubbleCannonState.OnUpdate (cyclomatic 29) · ×1
  • SeaShrimpBubbleCannonState.OnUpdate (cyclomatic 29) Content/NPCs/SeaShrimp/States/SeaShrimpBubbleCannonState.cs:37 — SeaShrimpBubbleCannonState.OnUpdate 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.
D1 · Cyclomatic Complexity · TBUGShopUI.Update (cyclomatic 29) · ×1
  • TBUGShopUI.Update (cyclomatic 29) Content/NPCs/TBUGs/UIs/TBUGShopUI.cs:220 — TBUGShopUI.Update 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.
D1 · Cyclomatic Complexity · VictorDialogue.CollectContext (cyclomatic 29) · ×1
  • VictorDialogue.CollectContext (cyclomatic 29) Content/NPCs/Victors/VictorDialogue.cs:218 — VictorDialogue.CollectContext 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.
D1 · Cyclomatic Complexity · VictorRiftPortalProj.SpawnAmbientParticles (cyclomatic 29) · ×1
  • VictorRiftPortalProj.SpawnAmbientParticles (cyclomatic 29) Content/NPCs/Victors/VictorRiftPortalProj.cs:239 — VictorRiftPortalProj.SpawnAmbientParticles 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.
D1 · Cyclomatic Complexity · Undrowned.UpdateBreach (cyclomatic 29) · ×1
  • Undrowned.UpdateBreach (cyclomatic 29) Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:1161 — Undrowned.UpdateBreach 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.
D1 · Cyclomatic Complexity · KiyumeGroundField.Scan (cyclomatic 29) · ×1
  • KiyumeGroundField.Scan (cyclomatic 29) Content/Scenarios/Kiyume/Fog/KiyumeGroundField.cs:143 — KiyumeGroundField.Scan 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.
D1 · Cyclomatic Complexity · SettingsCategory.Update (cyclomatic 29) · ×1
  • SettingsCategory.Update (cyclomatic 29) Content/UIs/OverhaulSettings/SettingsCategory.cs:104 — SettingsCategory.Update 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.
D1 · Cyclomatic Complexity · RotmireWritheProj.AI (cyclomatic 28) · ×1
  • RotmireWritheProj.AI (cyclomatic 28) Content/GameModes/BrutalMobs/Ambience/Rotmire/Projectiles/RotmireWritheProj.cs:89 — RotmireWritheProj.AI 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.
D1 · Cyclomatic Complexity · DdCastOmen.AI (cyclomatic 28) · ×1
  • DdCastOmen.AI (cyclomatic 28) Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdCastOmen.cs:124 — DdCastOmen.AI 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.
D1 · Cyclomatic Complexity · HackPanelRenderer.DrawRowForeground (cyclomatic 28) · ×1
  • HackPanelRenderer.DrawRowForeground (cyclomatic 28) Content/HackTimes/HackPanelRenderer.cs:659 — HackPanelRenderer.DrawRowForeground 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.
D1 · Cyclomatic Complexity · SolarCoreFistRender.EndEntityDraw (cyclomatic 28) · ×1
  • SolarCoreFistRender.EndEntityDraw (cyclomatic 28) Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFistRender.cs:24 — SolarCoreFistRender.EndEntityDraw 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.
D1 · Cyclomatic Complexity · ArbiterManifestationSystem.EnsureSingleActor (cyclomatic 28) · ×1
  • ArbiterManifestationSystem.EnsureSingleActor (cyclomatic 28) Content/Items/Melee/Arbiters/ArbiterManifestationSystem.cs:266 — ArbiterManifestationSystem.EnsureSingleActor 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.
D1 · Cyclomatic Complexity · WGManifestationSystem.EnsureSingleActor (cyclomatic 28) · ×1
  • WGManifestationSystem.EnsureSingleActor (cyclomatic 28) Content/Items/Melee/WeaverGrievanceses/WGManifestationSystem.cs:258 — WGManifestationSystem.EnsureSingleActor 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.
D1 · Cyclomatic Complexity · DirtFishFollower.ConvergingAI (cyclomatic 28) · ×1
  • DirtFishFollower.ConvergingAI (cyclomatic 28) Content/LegendWeapon/HalibutLegend/FishSkills/FishDirt.cs:365 — DirtFishFollower.ConvergingAI 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.
D1 · Cyclomatic Complexity · KikasaDreamHound.AI (cyclomatic 28) · ×1
  • KikasaDreamHound.AI (cyclomatic 28) Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamHound.cs:185 — KikasaDreamHound.AI 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.
D1 · Cyclomatic Complexity · KikasaDrownNet.Receive (cyclomatic 28) · ×1
  • KikasaDrownNet.Receive (cyclomatic 28) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownNet.cs:105 — KikasaDrownNet.Receive 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.
D1 · Cyclomatic Complexity · KikasaRainUmbrella.AI (cyclomatic 28) · ×1
  • KikasaRainUmbrella.AI (cyclomatic 28) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:327 — KikasaRainUmbrella.AI 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.
D1 · Cyclomatic Complexity · KikasaRainUmbrella.TickVolleyBeat (cyclomatic 28) · ×1
  • KikasaRainUmbrella.TickVolleyBeat (cyclomatic 28) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:624 — KikasaRainUmbrella.TickVolleyBeat 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.
D1 · Cyclomatic Complexity · KikasaGunServant.UpdateEmerge (cyclomatic 28) · ×1
  • KikasaGunServant.UpdateEmerge (cyclomatic 28) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:336 — KikasaGunServant.UpdateEmerge 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.
D1 · Cyclomatic Complexity · KikasaEaterServant.UpdateRiftRam (cyclomatic 28) · ×1
  • KikasaEaterServant.UpdateRiftRam (cyclomatic 28) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:587 — KikasaEaterServant.UpdateRiftRam 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.
D1 · Cyclomatic Complexity · KikasaFesterSerpentServant.UpdateCystSweep (cyclomatic 28) · ×1
  • KikasaFesterSerpentServant.UpdateCystSweep (cyclomatic 28) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:514 — KikasaFesterSerpentServant.UpdateCystSweep 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.
D1 · Cyclomatic Complexity · KikasaMoonLordServant.UpdateDissolve (cyclomatic 28) · ×1
  • KikasaMoonLordServant.UpdateDissolve (cyclomatic 28) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:902 — KikasaMoonLordServant.UpdateDissolve 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.
D1 · Cyclomatic Complexity · KikasaServantPlayer.SaveData (cyclomatic 28) · ×1
  • KikasaServantPlayer.SaveData (cyclomatic 28) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaServantPlayer.cs:489 — KikasaServantPlayer.SaveData 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.
D1 · Cyclomatic Complexity · KikasaLakeFX.UpdateSink (cyclomatic 28) · ×1
  • KikasaLakeFX.UpdateSink (cyclomatic 28) Content/LegendWeapon/KikasaLegend/KikasaVaults/KikasaLakeFX.cs:278 — KikasaLakeFX.UpdateSink 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.
D1 · Cyclomatic Complexity · OniDomainDeco.UpdatePetals (cyclomatic 28) · ×1
  • OniDomainDeco.UpdatePetals (cyclomatic 28) Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainDeco.cs:210 — OniDomainDeco.UpdatePetals 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.
D1 · Cyclomatic Complexity · OnikiriPlayer.ModifyHurt (cyclomatic 28) · ×1
  • OnikiriPlayer.ModifyHurt (cyclomatic 28) Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs:2512 — OnikiriPlayer.ModifyHurt 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.
D1 · Cyclomatic Complexity · SakuraWeaponAnimation.Validate (cyclomatic 28) · ×1
  • SakuraWeaponAnimation.Validate (cyclomatic 28) Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraWeaponAnimation.cs:139 — SakuraWeaponAnimation.Validate 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.
D1 · Cyclomatic Complexity · OniRegisterUI.UpdateInteraction (cyclomatic 28) · ×1
  • OniRegisterUI.UpdateInteraction (cyclomatic 28) Content/LegendWeapon/OnikiriLegend/UI/OniRegisterUI.cs:353 — OniRegisterUI.UpdateInteraction 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.
D1 · Cyclomatic Complexity · CyberDomainFreeze.CollectFreezeTargets (cyclomatic 28) · ×1
  • CyberDomainFreeze.CollectFreezeTargets (cyclomatic 28) Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.cs:209 — CyberDomainFreeze.CollectFreezeTargets 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.
D1 · Cyclomatic Complexity · CyberDomainFreeze.ApplyFreezeBatch (cyclomatic 28) · ×1
  • CyberDomainFreeze.ApplyFreezeBatch (cyclomatic 28) Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.cs:275 — CyberDomainFreeze.ApplyFreezeBatch 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.
D1 · Cyclomatic Complexity · BssSandSpitState.OnUpdate (cyclomatic 28) · ×1
  • BssSandSpitState.OnUpdate (cyclomatic 28) Content/NPCs/BloomsandSerpents/States/BssSandSpitState.cs:41 — BssSandSpitState.OnUpdate 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.
D1 · Cyclomatic Complexity · FishronVortexSnareState.OnUpdate (cyclomatic 28) · ×1
  • FishronVortexSnareState.OnUpdate (cyclomatic 28) Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronVortexGrabStates.cs:121 — FishronVortexSnareState.OnUpdate 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.
D1 · Cyclomatic Complexity · GolemMeteorLeapState.OnUpdate (cyclomatic 28) · ×1
  • GolemMeteorLeapState.OnUpdate (cyclomatic 28) Content/NPCs/BrutalNPCs/BrutalGolem/States/GolemMeteorLeapState.cs:37 — GolemMeteorLeapState.OnUpdate 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.
D1 · Cyclomatic Complexity · MLordTidalPalmsState.DriveSlamServer (cyclomatic 28) · ×1
  • MLordTidalPalmsState.DriveSlamServer (cyclomatic 28) Content/NPCs/BrutalNPCs/BrutalMoonLord/States/MLordTidalPalmsState.cs:161 — MLordTidalPalmsState.DriveSlamServer 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.
D1 · Cyclomatic Complexity · BrutalQueenBeeAI.UpdateHoneyMark (cyclomatic 28) · ×1
  • BrutalQueenBeeAI.UpdateHoneyMark (cyclomatic 28) Content/NPCs/BrutalNPCs/BrutalQueenBee/BrutalQueenBeeAI.cs:283 — BrutalQueenBeeAI.UpdateHoneyMark 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.
D1 · Cyclomatic Complexity · QBSwarmLiftState.OnUpdate (cyclomatic 28) · ×1
  • QBSwarmLiftState.OnUpdate (cyclomatic 28) Content/NPCs/BrutalNPCs/BrutalQueenBee/States/QBSwarmLiftState.cs:124 — QBSwarmLiftState.OnUpdate 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.
D1 · Cyclomatic Complexity · QueenCrystalPrisonWaltzState.UpdateWaltz (cyclomatic 28) · ×1
  • QueenCrystalPrisonWaltzState.UpdateWaltz (cyclomatic 28) Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenCrystalPrisonWaltzState.cs:324 — QueenCrystalPrisonWaltzState.UpdateWaltz 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.
D1 · Cyclomatic Complexity · ScrapSweepBeam.AI (cyclomatic 28) · ×1
  • ScrapSweepBeam.AI (cyclomatic 28) Content/NPCs/ScrapCommanders/Projectiles/ScrapSweepBeam.cs:121 — ScrapSweepBeam.AI 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.
D1 · Cyclomatic Complexity · FloodGalleryRoom.ApplyWeathering (cyclomatic 28) · ×1
  • FloodGalleryRoom.ApplyWeathering (cyclomatic 28) Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryRoom.cs:272 — FloodGalleryRoom.ApplyWeathering 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.
D1 · Cyclomatic Complexity · BoneStitcher.UpdateScavenge (cyclomatic 28) · ×1
  • BoneStitcher.UpdateScavenge (cyclomatic 28) Content/Scenarios/Dungeonworld/NPCs/Elites/BoneStitcher.cs:247 — BoneStitcher.UpdateScavenge 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.
D1 · Cyclomatic Complexity · FoundryOverseer.PreDraw (cyclomatic 28) · ×1
  • FoundryOverseer.PreDraw (cyclomatic 28) Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:1244 — FoundryOverseer.PreDraw 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.
D1 · Cyclomatic Complexity · HackTimeTutorialLead.UpdateUI (cyclomatic 28) · ×1
  • HackTimeTutorialLead.UpdateUI (cyclomatic 28) Content/Scenarios/Shepel/CybCourses/HackTimeTutorialLead.cs:228 — HackTimeTutorialLead.UpdateUI 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.
D1 · Cyclomatic Complexity · SvgPathPen.Flatten (cyclomatic 28) · ×1
  • SvgPathPen.Flatten (cyclomatic 28) Content/UIs/UIEffect/SvgPathPen.cs:185 — SvgPathPen.Flatten 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.
D1 · Cyclomatic Complexity · GhostHandProj.UpdateVisuals (cyclomatic 28) · ×1
  • GhostHandProj.UpdateVisuals (cyclomatic 28) Content/Wraiths/Projectiles/GhostHandProj.cs:766 — GhostHandProj.UpdateVisuals 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.
D1 · Cyclomatic Complexity · CyberSlotRenderer.DrawSlots (cyclomatic 27) · ×1
  • CyberSlotRenderer.DrawSlots (cyclomatic 27) Content/Cyberwares/UIs/CyberSlotRenderer.cs:143 — CyberSlotRenderer.DrawSlots has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · StonewakeResonanceRingProj.AI (cyclomatic 27) · ×1
  • StonewakeResonanceRingProj.AI (cyclomatic 27) Content/GameModes/BrutalMobs/Ambience/Stonewake/Projectiles/StonewakeResonanceRingProj.cs:84 — StonewakeResonanceRingProj.AI has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SunkenduneSinkPitProj.AI (cyclomatic 27) · ×1
  • SunkenduneSinkPitProj.AI (cyclomatic 27) Content/GameModes/BrutalMobs/Ambience/Sunkendune/Projectiles/SunkenduneSinkPitProj.cs:67 — SunkenduneSinkPitProj.AI has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · HackEffectTracker.ApplyReplicatedEffect (cyclomatic 27) · ×1
  • HackEffectTracker.ApplyReplicatedEffect (cyclomatic 27) Content/HackTimes/HackEffectTracker.cs:246 — HackEffectTracker.ApplyReplicatedEffect has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ApiaryTP.UpdateMachine (cyclomatic 27) · ×1
  • ApiaryTP.UpdateMachine (cyclomatic 27) Content/Industrials/ElectricPowers/Apiaries/ApiaryTP.cs:299 — ApiaryTP.UpdateMachine has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FishEnvironment.Capture (cyclomatic 27) · ×1
  • FishEnvironment.Capture (cyclomatic 27) Content/Industrials/ElectricPowers/AutoFishers/AutoFisherLootTable.cs:46 — FishEnvironment.Capture has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · TeleportStationUI.Update (cyclomatic 27) · ×1
  • TeleportStationUI.Update (cyclomatic 27) Content/Industrials/ElectricPowers/TeleportStations/TeleportStationUI.cs:186 — TeleportStationUI.Update has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ChargingStationUI.Update (cyclomatic 27) · ×1
  • ChargingStationUI.Update (cyclomatic 27) Content/Industrials/Modifys/ChargingStationUI.cs:108 — ChargingStationUI.Update has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FallenKingsCrownPlayer.PostUpdate (cyclomatic 27) · ×1
  • FallenKingsCrownPlayer.PostUpdate (cyclomatic 27) Content/Items/Accessories/BrutalRelics/KingSlime/FallenKingsCrownPlayer.cs:77 — FallenKingsCrownPlayer.PostUpdate has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SwarmVortexProj.AI (cyclomatic 27) · ×1
  • SwarmVortexProj.AI (cyclomatic 27) Content/Items/Accessories/BrutalRelics/QueenBee/SwarmVortexProj.cs:73 — SwarmVortexProj.AI has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SeaDomainProj.AI (cyclomatic 27) · ×1
  • SeaDomainProj.AI (cyclomatic 27) Content/LegendWeapon/HalibutLegend/DomainSkills/SeaDomain.cs:177 — SeaDomainProj.AI has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · AtlasFishStudyPanel.Update (cyclomatic 27) · ×1
  • AtlasFishStudyPanel.Update (cyclomatic 27) Content/LegendWeapon/HalibutLegend/UI/Atlas/AtlasFishStudyPanel.cs:124 — AtlasFishStudyPanel.Update has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · HalibutAtlas.Update (cyclomatic 27) · ×1
  • HalibutAtlas.Update (cyclomatic 27) Content/LegendWeapon/HalibutLegend/UI/Atlas/HalibutAtlas.cs:186 — HalibutAtlas.Update has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaMinionDrownFX.UpdateShow (cyclomatic 27) · ×1
  • KikasaMinionDrownFX.UpdateShow (cyclomatic 27) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaMinionDrownFX.cs:235 — KikasaMinionDrownFX.UpdateShow has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaBoomerangServant.UpdateHands (cyclomatic 27) · ×1
  • KikasaBoomerangServant.UpdateHands (cyclomatic 27) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:671 — KikasaBoomerangServant.UpdateHands has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaBowServant.UpdateEmerge (cyclomatic 27) · ×1
  • KikasaBowServant.UpdateEmerge (cyclomatic 27) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:300 — KikasaBowServant.UpdateEmerge has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaDeerclopsServant.UpdateRoar (cyclomatic 27) · ×1
  • KikasaDeerclopsServant.UpdateRoar (cyclomatic 27) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:765 — KikasaDeerclopsServant.UpdateRoar has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaDeerclopsServant.DrawGlow (cyclomatic 27) · ×1
  • KikasaDeerclopsServant.DrawGlow (cyclomatic 27) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:1356 — KikasaDeerclopsServant.DrawGlow has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaDestroyerServant.UpdateEmerge (cyclomatic 27) · ×1
  • KikasaDestroyerServant.UpdateEmerge (cyclomatic 27) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:289 — KikasaDestroyerServant.UpdateEmerge has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaMoonLordServant.DrawVesselLayer (cyclomatic 27) · ×1
  • KikasaMoonLordServant.DrawVesselLayer (cyclomatic 27) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1187 — KikasaMoonLordServant.DrawVesselLayer has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · RibbonMeshBuilder.Build (cyclomatic 27) · ×1
  • RibbonMeshBuilder.Build (cyclomatic 27) Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/Geometry/RibbonMesh.cs:144 — RibbonMeshBuilder.Build has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CyberTraceBeamProj.AI (cyclomatic 27) · ×1
  • CyberTraceBeamProj.AI (cyclomatic 27) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberTraceBeamProj.cs:181 — CyberTraceBeamProj.AI has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SHPCSandCurtainProj.AI (cyclomatic 27) · ×1
  • SHPCSandCurtainProj.AI (cyclomatic 27) Content/LegendWeapon/SHPCLegend/Modules/Barrel/SandstormBarrelModule.cs:75 — SHPCSandCurtainProj.AI has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SHPCPlayer.LoadData (cyclomatic 27) · ×1
  • SHPCPlayer.LoadData (cyclomatic 27) Content/LegendWeapon/SHPCLegend/SHPCPlayer.cs:287 — SHPCPlayer.LoadData has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BrainLanceWavesState.OnUpdate (cyclomatic 27) · ×1
  • BrainLanceWavesState.OnUpdate (cyclomatic 27) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainLanceWavesState.cs:47 — BrainLanceWavesState.OnUpdate has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FishronIntroState.OnUpdate (cyclomatic 27) · ×1
  • FishronIntroState.OnUpdate (cyclomatic 27) Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronIntroState.cs:44 — FishronIntroState.OnUpdate has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CultistOrreryRingProj.AI (cyclomatic 27) · ×1
  • CultistOrreryRingProj.AI (cyclomatic 27) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistOrreryRingProj.cs:65 — CultistOrreryRingProj.AI has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · QueenCrystalCathedralState.OnUpdate (cyclomatic 27) · ×1
  • QueenCrystalCathedralState.OnUpdate (cyclomatic 27) Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenCrystalCathedralState.cs:56 — QueenCrystalCathedralState.OnUpdate has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ScrapCommander.AI (cyclomatic 27) · ×1
  • ScrapCommander.AI (cyclomatic 27) Content/NPCs/ScrapCommanders/ScrapCommander.cs:207 — ScrapCommander.AI has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · TBUGDialogue.CollectContext (cyclomatic 27) · ×1
  • TBUGDialogue.CollectContext (cyclomatic 27) Content/NPCs/TBUGs/TBUGDialogue.cs:218 — TBUGDialogue.CollectContext has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ProofingHallWatcher.PostUpdateNPCs (cyclomatic 27) · ×1
  • ProofingHallWatcher.PostUpdateNPCs (cyclomatic 27) Content/Scenarios/Dungeonworld/Gen/BossRooms/ProofingHallWatcher.cs:85 — ProofingHallWatcher.PostUpdateNPCs has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DeepGaolWraith.DrawGlowLayer (cyclomatic 27) · ×1
  • DeepGaolWraith.DrawGlowLayer (cyclomatic 27) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:2438 — DeepGaolWraith.DrawGlowLayer has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FoundryOverseer.UpdateDeath (cyclomatic 27) · ×1
  • FoundryOverseer.UpdateDeath (cyclomatic 27) Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:1069 — FoundryOverseer.UpdateDeath has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · WheelTutorialLead.UpdateUI (cyclomatic 27) · ×1
  • WheelTutorialLead.UpdateUI (cyclomatic 27) Content/Scenarios/Shepel/CybCourses/WheelTutorialLead.cs:156 — WheelTutorialLead.UpdateUI has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SylvanOutpost.IsValidGroundLevel (cyclomatic 27) · ×1
  • SylvanOutpost.IsValidGroundLevel (cyclomatic 27) Content/Structures/DatIO/SylvanOutpost.cs:238 — SylvanOutpost.IsValidGroundLevel has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MireheartBeeCloudProj.AI (cyclomatic 26) · ×1
  • MireheartBeeCloudProj.AI (cyclomatic 26) Content/GameModes/BrutalMobs/Ambience/Mireheart/Projectiles/MireheartBeeCloudProj.cs:74 — MireheartBeeCloudProj.AI has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DdMarksmanOmen.AI (cyclomatic 26) · ×1
  • DdMarksmanOmen.AI (cyclomatic 26) Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdMarksmanOmen.cs:81 — DdMarksmanOmen.AI has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FlgMortarRingOmen.AI (cyclomatic 26) · ×1
  • FlgMortarRingOmen.AI (cyclomatic 26) Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarRingOmen.cs:71 — FlgMortarRingOmen.AI has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · LegionClownBomb.AI (cyclomatic 26) · ×1
  • LegionClownBomb.AI (cyclomatic 26) Content/GameModes/BrutalMobs/Legion/Projectiles/LegionClownBomb.cs:77 — LegionClownBomb.AI has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · PrtBoardHookProj.AI (cyclomatic 26) · ×1
  • PrtBoardHookProj.AI (cyclomatic 26) Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtBoardHookProj.cs:77 — PrtBoardHookProj.AI has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · GsMinisharkHeld.AI (cyclomatic 26) · ×1
  • GsMinisharkHeld.AI (cyclomatic 26) Content/GameModes/GodSmith/Weapons/Guns/GsMinishark.cs:166 — GsMinisharkHeld.AI has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · HackEffectTracker.ApplyAuthorityEffect (cyclomatic 26) · ×1
  • HackEffectTracker.ApplyAuthorityEffect (cyclomatic 26) Content/HackTimes/HackEffectTracker.cs:157 — HackEffectTracker.ApplyAuthorityEffect has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · RecyclerTP.UpdateVisualFX (cyclomatic 26) · ×1
  • RecyclerTP.UpdateVisualFX (cyclomatic 26) Content/Industrials/ElectricPowers/Recyclers/RecyclerTP.cs:198 — RecyclerTP.UpdateVisualFX has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ThrowerUI.Update (cyclomatic 26) · ×1
  • ThrowerUI.Update (cyclomatic 26) Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:132 — ThrowerUI.Update has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · GodslayerScabbardPlayer.PreUpdateMovement (cyclomatic 26) · ×1
  • GodslayerScabbardPlayer.PreUpdateMovement (cyclomatic 26) Content/Items/Accessories/GodslayerScabbard.cs:71 — GodslayerScabbardPlayer.PreUpdateMovement has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · PallbearerBoomerang.AI (cyclomatic 26) · ×1
  • PallbearerBoomerang.AI (cyclomatic 26) Content/Items/Ranged/Pallbearer.cs:592 — PallbearerBoomerang.AI has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FallingPenguin.PreDraw (cyclomatic 26) · ×1
  • FallingPenguin.PreDraw (cyclomatic 26) Content/LegendWeapon/HalibutLegend/FishSkills/FishPeng.cs:513 — FallingPenguin.PreDraw has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaDreamGroundField.Scan (cyclomatic 26) · ×1
  • KikasaDreamGroundField.Scan (cyclomatic 26) Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamGroundField.cs:128 — KikasaDreamGroundField.Scan has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaDreamHound.UpdateSprint (cyclomatic 26) · ×1
  • KikasaDreamHound.UpdateSprint (cyclomatic 26) Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamHound.cs:526 — KikasaDreamHound.UpdateSprint has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaPlayerDrownFX.UpdateShow (cyclomatic 26) · ×1
  • KikasaPlayerDrownFX.UpdateShow (cyclomatic 26) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaPlayerDrownFX.cs:230 — KikasaPlayerDrownFX.UpdateShow has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaBladeServant.UpdateEmerge (cyclomatic 26) · ×1
  • KikasaBladeServant.UpdateEmerge (cyclomatic 26) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:325 — KikasaBladeServant.UpdateEmerge has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaBoomerangServant.UpdateEmerge (cyclomatic 26) · ×1
  • KikasaBoomerangServant.UpdateEmerge (cyclomatic 26) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:324 — KikasaBoomerangServant.UpdateEmerge has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaFlailServant.UpdateEmerge (cyclomatic 26) · ×1
  • KikasaFlailServant.UpdateEmerge (cyclomatic 26) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:321 — KikasaFlailServant.UpdateEmerge has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaHalibutServant.UpdateGun (cyclomatic 26) · ×1
  • KikasaHalibutServant.UpdateGun (cyclomatic 26) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:794 — KikasaHalibutServant.UpdateGun has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaSHPCServant.UpdateGun (cyclomatic 26) · ×1
  • KikasaSHPCServant.UpdateGun (cyclomatic 26) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:772 — KikasaSHPCServant.UpdateGun has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaThrowServant.UpdateEmerge (cyclomatic 26) · ×1
  • KikasaThrowServant.UpdateEmerge (cyclomatic 26) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:287 — KikasaThrowServant.UpdateEmerge has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaYoyoServant.UpdateEmerge (cyclomatic 26) · ×1
  • KikasaYoyoServant.UpdateEmerge (cyclomatic 26) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:319 — KikasaYoyoServant.UpdateEmerge has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaYoyoServant.UpdateHands (cyclomatic 26) · ×1
  • KikasaYoyoServant.UpdateHands (cyclomatic 26) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:666 — KikasaYoyoServant.UpdateHands has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaBloomSerpentServant.UpdateDashRam (cyclomatic 26) · ×1
  • KikasaBloomSerpentServant.UpdateDashRam (cyclomatic 26) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:419 — KikasaBloomSerpentServant.UpdateDashRam has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaBrainServant.UpdateMirages (cyclomatic 26) · ×1
  • KikasaBrainServant.UpdateMirages (cyclomatic 26) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:957 — KikasaBrainServant.UpdateMirages has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaPlanteraVine.AI (cyclomatic 26) · ×1
  • KikasaPlanteraVine.AI (cyclomatic 26) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraVine.cs:98 — KikasaPlanteraVine.AI has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaPrimeServant.UpdateEmerge (cyclomatic 26) · ×1
  • KikasaPrimeServant.UpdateEmerge (cyclomatic 26) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:342 — KikasaPrimeServant.UpdateEmerge has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaTwinsServant.UpdateCord (cyclomatic 26) · ×1
  • KikasaTwinsServant.UpdateCord (cyclomatic 26) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1223 — KikasaTwinsServant.UpdateCord has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaLakeFX.UpdateRaise (cyclomatic 26) · ×1
  • KikasaLakeFX.UpdateRaise (cyclomatic 26) Content/LegendWeapon/KikasaLegend/KikasaVaults/KikasaLakeFX.cs:398 — KikasaLakeFX.UpdateRaise has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaWispFX.Update (cyclomatic 26) · ×1
  • KikasaWispFX.Update (cyclomatic 26) Content/LegendWeapon/KikasaLegend/KikasaWisps/KikasaWispFX.cs:63 — KikasaWispFX.Update has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniSeverStrike.ValidateRequest (cyclomatic 26) · ×1
  • OniSeverStrike.ValidateRequest (cyclomatic 26) Content/LegendWeapon/OnikiriLegend/OniDismembers/OniSeverStrike.cs:572 — OniSeverStrike.ValidateRequest has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SHPCModuleItem.BuildStatLines (cyclomatic 26) · ×1
  • SHPCModuleItem.BuildStatLines (cyclomatic 26) Content/LegendWeapon/SHPCLegend/Modules/SHPCModuleItem.cs:92 — SHPCModuleItem.BuildStatLines has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BrainOrbitCageState.OnUpdate (cyclomatic 26) · ×1
  • BrainOrbitCageState.OnUpdate (cyclomatic 26) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainOrbitCageState.cs:64 — BrainOrbitCageState.OnUpdate has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DeerclopsDeathState.OnUpdate (cyclomatic 26) · ×1
  • DeerclopsDeathState.OnUpdate (cyclomatic 26) Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsDeathState.cs:47 — DeerclopsDeathState.OnUpdate has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MLordArmIK.SolveInner (cyclomatic 26) · ×1
  • MLordArmIK.SolveInner (cyclomatic 26) Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordArmIK.cs:114 — MLordArmIK.SolveInner has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · QueenBallroomStepState.OnUpdate (cyclomatic 26) · ×1
  • QueenBallroomStepState.OnUpdate (cyclomatic 26) Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenBallroomStepState.cs:51 — QueenBallroomStepState.OnUpdate has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FssDeathState.OnUpdate (cyclomatic 26) · ×1
  • FssDeathState.OnUpdate (cyclomatic 26) Content/NPCs/FestersandSerpents/States/FssDeathState.cs:44 — FssDeathState.OnUpdate has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SeaShrimpVortexWallState.OnUpdate (cyclomatic 26) · ×1
  • SeaShrimpVortexWallState.OnUpdate (cyclomatic 26) Content/NPCs/SeaShrimp/States/SeaShrimpVortexWallState.cs:39 — SeaShrimpVortexWallState.OnUpdate has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DeepGaolWraith.UpdateFlail (cyclomatic 26) · ×1
  • DeepGaolWraith.UpdateFlail (cyclomatic 26) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:1104 — DeepGaolWraith.UpdateFlail has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OldNetCipherPanel.UpdateUI (cyclomatic 26) · ×1
  • OldNetCipherPanel.UpdateUI (cyclomatic 26) Content/Scenarios/OldNet/UI/OldNetCipherPanel.cs:155 — OldNetCipherPanel.UpdateUI has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SubworldDrawBlackFix.DrawBlackFullRange (cyclomatic 26) · ×1
  • SubworldDrawBlackFix.DrawBlackFullRange (cyclomatic 26) Content/Scenarios/SubworldDrawBlackFix.cs:68 — SubworldDrawBlackFix.DrawBlackFullRange has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · IndustrialSkyIslandGen.BuildIslandBody (cyclomatic 26) · ×1
  • IndustrialSkyIslandGen.BuildIslandBody (cyclomatic 26) Content/Structures/IndustrialSkyIslandGen.cs:123 — IndustrialSkyIslandGen.BuildIslandBody has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · GhostHandProj.GrippingBehavior (cyclomatic 26) · ×1
  • GhostHandProj.GrippingBehavior (cyclomatic 26) Content/Wraiths/Projectiles/GhostHandProj.cs:448 — GhostHandProj.GrippingBehavior has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · QuestLogsAPI.TryRegisterNode (cyclomatic 25) · ×1
  • QuestLogsAPI.TryRegisterNode (cyclomatic 25) API/QuestLogsAPI.cs:28 — QuestLogsAPI.TryRegisterNode has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EclipseNPC.TryStart (cyclomatic 25) · ×1
  • EclipseNPC.TryStart (cyclomatic 25) Content/GameModes/BrutalMobs/Eclipse/EclipseNPC.cs:230 — EclipseNPC.TryStart has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · WastesIceSlickZone.AI (cyclomatic 25) · ×1
  • WastesIceSlickZone.AI (cyclomatic 25) Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesIceSlickZone.cs:58 — WastesIceSlickZone.AI has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · GsZoneProj.AI (cyclomatic 25) · ×1
  • GsZoneProj.AI (cyclomatic 25) Content/GameModes/GodSmith/Weapons/Throwing/Projectiles/GsZoneProj.cs:61 — GsZoneProj.AI has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · AutoFisherLootTable.RollCrate (cyclomatic 25) · ×1
  • AutoFisherLootTable.RollCrate (cyclomatic 25) Content/Industrials/ElectricPowers/AutoFishers/AutoFisherLootTable.cs:163 — AutoFisherLootTable.RollCrate has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MushroomFarmerTP.TryHarvest (cyclomatic 25) · ×1
  • MushroomFarmerTP.TryHarvest (cyclomatic 25) Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:406 — MushroomFarmerTP.TryHarvest has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · GeneratorReadoutUI.Draw (cyclomatic 25) · ×1
  • GeneratorReadoutUI.Draw (cyclomatic 25) Content/Industrials/Generator/GeneratorReadout.cs:255 — GeneratorReadoutUI.Draw has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SeaDomainProj.UpdateDomainEffects (cyclomatic 25) · ×1
  • SeaDomainProj.UpdateDomainEffects (cyclomatic 25) Content/LegendWeapon/HalibutLegend/DomainSkills/SeaDomain.cs:328 — SeaDomainProj.UpdateDomainEffects has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · UnicornFishDashProj.PreDraw (cyclomatic 25) · ×1
  • UnicornFishDashProj.PreDraw (cyclomatic 25) Content/LegendWeapon/HalibutLegend/FishSkills/FishUnicorn.cs:369 — UnicornFishDashProj.PreDraw has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaSpearServant.UpdateEmerge (cyclomatic 25) · ×1
  • KikasaSpearServant.UpdateEmerge (cyclomatic 25) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:287 — KikasaSpearServant.UpdateEmerge has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaThrowServant.UpdateHands (cyclomatic 25) · ×1
  • KikasaThrowServant.UpdateHands (cyclomatic 25) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:633 — KikasaThrowServant.UpdateHands has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaWhipServant.UpdateEmerge (cyclomatic 25) · ×1
  • KikasaWhipServant.UpdateEmerge (cyclomatic 25) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:295 — KikasaWhipServant.UpdateEmerge has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaZenithServant.DrawGlow (cyclomatic 25) · ×1
  • KikasaZenithServant.DrawGlow (cyclomatic 25) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1438 — KikasaZenithServant.DrawGlow has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaEaterServant.UpdateSpitVolley (cyclomatic 25) · ×1
  • KikasaEaterServant.UpdateSpitVolley (cyclomatic 25) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:734 — KikasaEaterServant.UpdateSpitVolley has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaEmpressLance.AI (cyclomatic 25) · ×1
  • KikasaEmpressLance.AI (cyclomatic 25) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressLance.cs:105 — KikasaEmpressLance.AI has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaPlanteraServant.AI (cyclomatic 25) · ×1
  • KikasaPlanteraServant.AI (cyclomatic 25) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:233 — KikasaPlanteraServant.AI has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaQueenBeeServant.UpdateEmerge (cyclomatic 25) · ×1
  • KikasaQueenBeeServant.UpdateEmerge (cyclomatic 25) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:278 — KikasaQueenBeeServant.UpdateEmerge has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaSkeletronServant.DrawGlow (cyclomatic 25) · ×1
  • KikasaSkeletronServant.DrawGlow (cyclomatic 25) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1603 — KikasaSkeletronServant.DrawGlow has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaTwinsServant.UpdateEmerge (cyclomatic 25) · ×1
  • KikasaTwinsServant.UpdateEmerge (cyclomatic 25) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:337 — KikasaTwinsServant.UpdateEmerge has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniHangingSwitch.Update (cyclomatic 25) · ×1
  • OniHangingSwitch.Update (cyclomatic 25) Content/LegendWeapon/OnikiriLegend/UI/OniHangingSwitch.cs:65 — OniHangingSwitch.Update has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MoldProcessingUI.Update (cyclomatic 25) · ×1
  • MoldProcessingUI.Update (cyclomatic 25) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingUI.cs:122 — MoldProcessingUI.Update has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CharacterDockUI.UpdateInteraction (cyclomatic 25) · ×1
  • CharacterDockUI.UpdateInteraction (cyclomatic 25) Content/MainMenus/Characters/CharacterDockUI.cs:329 — CharacterDockUI.UpdateInteraction has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BssCoilOrbitState.OnUpdate (cyclomatic 25) · ×1
  • BssCoilOrbitState.OnUpdate (cyclomatic 25) Content/NPCs/BloomsandSerpents/States/BssCoilOrbitState.cs:61 — BssCoilOrbitState.OnUpdate has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BrainHeartAttackState.OnUpdate (cyclomatic 25) · ×1
  • BrainHeartAttackState.OnUpdate (cyclomatic 25) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainHeartAttackState.cs:64 — BrainHeartAttackState.OnUpdate has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · GolemFistGrabState.OnUpdate (cyclomatic 25) · ×1
  • GolemFistGrabState.OnUpdate (cyclomatic 25) Content/NPCs/BrutalNPCs/BrutalGolem/States/Fists/GolemFistGrabState.cs:74 — GolemFistGrabState.OnUpdate has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KingSlimePursuitBurrowState.OnUpdate (cyclomatic 25) · ×1
  • KingSlimePursuitBurrowState.OnUpdate (cyclomatic 25) Content/NPCs/BrutalNPCs/BrutalKingSlime/States/KingSlimePursuitBurrowState.cs:40 — KingSlimePursuitBurrowState.OnUpdate has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CultistPlanetProj.PreDraw (cyclomatic 25) · ×1
  • CultistPlanetProj.PreDraw (cyclomatic 25) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistPlanetProj.cs:798 — CultistPlanetProj.PreDraw has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CultistStarChart.PreDraw (cyclomatic 25) · ×1
  • CultistStarChart.PreDraw (cyclomatic 25) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistStarChart.cs:192 — CultistStarChart.PreDraw has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CultistEclipseState.OnUpdate (cyclomatic 25) · ×1
  • CultistEclipseState.OnUpdate (cyclomatic 25) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistEclipseState.cs:39 — CultistEclipseState.OnUpdate has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · TwinsPincerGrabState.OnBeatChanged (cyclomatic 25) · ×1
  • TwinsPincerGrabState.OnBeatChanged (cyclomatic 25) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsPincerGrabState.cs:477 — TwinsPincerGrabState.OnBeatChanged has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MoonLordCoreAI.EvaluateGlobalTransitions (cyclomatic 25) · ×1
  • MoonLordCoreAI.EvaluateGlobalTransitions (cyclomatic 25) Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordCoreAI.cs:185 — MoonLordCoreAI.EvaluateGlobalTransitions has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MoonLordFreeEyeAI.UpdateStarArray (cyclomatic 25) · ×1
  • MoonLordFreeEyeAI.UpdateStarArray (cyclomatic 25) Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordFreeEyeAI.cs:464 — MoonLordFreeEyeAI.UpdateStarArray has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · PlanteraVineLattice.AI (cyclomatic 25) · ×1
  • PlanteraVineLattice.AI (cyclomatic 25) Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraVineLattice.cs:66 — PlanteraVineLattice.AI has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FssIntroState.OnUpdate (cyclomatic 25) · ×1
  • FssIntroState.OnUpdate (cyclomatic 25) Content/NPCs/FestersandSerpents/States/FssIntroState.cs:60 — FssIntroState.OnUpdate has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SeaShrimpDeathState.OnUpdate (cyclomatic 25) · ×1
  • SeaShrimpDeathState.OnUpdate (cyclomatic 25) Content/NPCs/SeaShrimp/States/SeaShrimpDeathState.cs:41 — SeaShrimpDeathState.OnUpdate has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FloodGalleryWatcher.PostUpdateNPCs (cyclomatic 25) · ×1
  • FloodGalleryWatcher.PostUpdateNPCs (cyclomatic 25) Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryWatcher.cs:115 — FloodGalleryWatcher.PostUpdateNPCs has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · L3Content.TryBuildNode (cyclomatic 25) · ×1
  • L3Content.TryBuildNode (cyclomatic 25) Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Content.cs:361 — L3Content.TryBuildNode has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · L6Traps.RollMotif (cyclomatic 25) · ×1
  • L6Traps.RollMotif (cyclomatic 25) Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Traps.cs:59 — L6Traps.RollMotif has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · LampeaterWisp.UpdatePounce (cyclomatic 25) · ×1
  • LampeaterWisp.UpdatePounce (cyclomatic 25) Content/Scenarios/Dungeonworld/NPCs/Elites/LampeaterWisp.cs:229 — LampeaterWisp.UpdatePounce has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FoundryOverseer.AI (cyclomatic 25) · ×1
  • FoundryOverseer.AI (cyclomatic 25) Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:372 — FoundryOverseer.AI has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OverseerPressStrike.AI (cyclomatic 25) · ×1
  • OverseerPressStrike.AI (cyclomatic 25) Content/Scenarios/Dungeonworld/NPCs/OverseerPressStrike.cs:75 — OverseerPressStrike.AI has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · UndrownedAnchor.AI (cyclomatic 25) · ×1
  • UndrownedAnchor.AI (cyclomatic 25) Content/Scenarios/Dungeonworld/NPCs/UndrownedAnchor.cs:53 — UndrownedAnchor.AI has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · HadalTerrainPlanner.BuildDeepStructures (cyclomatic 25) · ×1
  • HadalTerrainPlanner.BuildDeepStructures (cyclomatic 25) Content/Scenarios/Hadalworld/Gen/Core/HadalTerrainPlan.cs:520 — HadalTerrainPlanner.BuildDeepStructures has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KiyumeFogSystem.ApplyPassUniforms (cyclomatic 25) · ×1
  • KiyumeFogSystem.ApplyPassUniforms (cyclomatic 25) Content/Scenarios/Kiyume/Fog/KiyumeFogSystem.cs:256 — KiyumeFogSystem.ApplyPassUniforms has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · WorldGenSettingsCategory.HandleClick (cyclomatic 25) · ×1
  • WorldGenSettingsCategory.HandleClick (cyclomatic 25) Content/UIs/OverhaulSettings/WorldGenSettingsCategory.cs:310 — WorldGenSettingsCategory.HandleClick has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MireheartAmbience.PostUpdateEverything (cyclomatic 24) · ×1
  • MireheartAmbience.PostUpdateEverything (cyclomatic 24) Content/GameModes/BrutalMobs/Ambience/Mireheart/MireheartAmbience.cs:100 — MireheartAmbience.PostUpdateEverything has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · VerdantPlayer.PostUpdate (cyclomatic 24) · ×1
  • VerdantPlayer.PostUpdate (cyclomatic 24) Content/GameModes/BrutalMobs/Ambience/Verdant/VerdantPlayer.cs:44 — VerdantPlayer.PostUpdate has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DungeonDeepNPC.TickBoneLee (cyclomatic 24) · ×1
  • DungeonDeepNPC.TickBoneLee (cyclomatic 24) Content/GameModes/BrutalMobs/DungeonDeep/DungeonDeepNPC.Melee.cs:268 — DungeonDeepNPC.TickBoneLee has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EliteMoveNPC.ServerLeap (cyclomatic 24) · ×1
  • EliteMoveNPC.ServerLeap (cyclomatic 24) Content/GameModes/BrutalMobs/EliteMove/EliteMoveNPC.cs:320 — EliteMoveNPC.ServerLeap has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MartiansNPC.ArcStep (cyclomatic 24) · ×1
  • MartiansNPC.ArcStep (cyclomatic 24) Content/GameModes/BrutalMobs/Martians/MartiansNPC.cs:242 — MartiansNPC.ArcStep has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · PmkClawCrossProj.AI (cyclomatic 24) · ×1
  • PmkClawCrossProj.AI (cyclomatic 24) Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkClawCrossProj.cs:74 — PmkClawCrossProj.AI has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · StonebornGazeOmen.AI (cyclomatic 24) · ×1
  • StonebornGazeOmen.AI (cyclomatic 24) Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornGazeOmen.cs:79 — StonebornGazeOmen.AI has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ProbeMatrixPlayer.UpdateSquad (cyclomatic 24) · ×1
  • ProbeMatrixPlayer.UpdateSquad (cyclomatic 24) Content/Items/Accessories/BrutalRelics/Destroyer/ProbeMatrixCore.cs:181 — ProbeMatrixPlayer.UpdateSquad has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · RefractionWaltzPlayer.ReconcileLinks (cyclomatic 24) · ×1
  • RefractionWaltzPlayer.ReconcileLinks (cyclomatic 24) Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltz.cs:262 — RefractionWaltzPlayer.ReconcileLinks has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ArbiterManifestationRenderer.Draw (cyclomatic 24) · ×1
  • ArbiterManifestationRenderer.Draw (cyclomatic 24) Content/Items/Melee/Arbiters/ArbiterManifestationRenderer.cs:27 — ArbiterManifestationRenderer.Draw has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · HalibutReset.UpdateShow (cyclomatic 24) · ×1
  • HalibutReset.UpdateShow (cyclomatic 24) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:460 — HalibutReset.UpdateShow has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaInkGeyser.AI (cyclomatic 24) · ×1
  • KikasaInkGeyser.AI (cyclomatic 24) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkGeyser.cs:138 — KikasaInkGeyser.AI has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaReset.UpdateShow (cyclomatic 24) · ×1
  • KikasaReset.UpdateShow (cyclomatic 24) Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaReset.cs:448 — KikasaReset.UpdateShow has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaBrainServant.UpdateEmerge (cyclomatic 24) · ×1
  • KikasaBrainServant.UpdateEmerge (cyclomatic 24) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:397 — KikasaBrainServant.UpdateEmerge has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaBrainServant.UpdateDissolve (cyclomatic 24) · ×1
  • KikasaBrainServant.UpdateDissolve (cyclomatic 24) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:790 — KikasaBrainServant.UpdateDissolve has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaCultistServant.UpdateRuneRite (cyclomatic 24) · ×1
  • KikasaCultistServant.UpdateRuneRite (cyclomatic 24) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:532 — KikasaCultistServant.UpdateRuneRite has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaGolemMagmaBall.AI (cyclomatic 24) · ×1
  • KikasaGolemMagmaBall.AI (cyclomatic 24) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemMagmaBall.cs:82 — KikasaGolemMagmaBall.AI has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OnikiriTutorialRenderer.UpdateInput (cyclomatic 24) · ×1
  • OnikiriTutorialRenderer.UpdateInput (cyclomatic 24) Content/LegendWeapon/OnikiriLegend/Tutorial/OnikiriTutorialRenderer.cs:79 — OnikiriTutorialRenderer.UpdateInput has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniSigilRenderer.DrawNode (cyclomatic 24) · ×1
  • OniSigilRenderer.DrawNode (cyclomatic 24) Content/LegendWeapon/OnikiriLegend/UI/OniSigilRenderer.cs:144 — OniSigilRenderer.DrawNode has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EmpressLacewing.AI (cyclomatic 24) · ×1
  • EmpressLacewing.AI (cyclomatic 24) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Projectiles/EmpressLacewing.cs:70 — EmpressLacewing.AI has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EmpressFinaleState.Swarm (cyclomatic 24) · ×1
  • EmpressFinaleState.Swarm (cyclomatic 24) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/States/EmpressFinaleState.cs:171 — EmpressFinaleState.Swarm has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EmpressPhaseTransitionState.OnUpdate (cyclomatic 24) · ×1
  • EmpressPhaseTransitionState.OnUpdate (cyclomatic 24) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/States/EmpressPhaseTransitionState.cs:34 — EmpressPhaseTransitionState.OnUpdate has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BKSTideWaveProj.AI (cyclomatic 24) · ×1
  • BKSTideWaveProj.AI (cyclomatic 24) Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSTideWaveProj.cs:88 — BKSTideWaveProj.AI has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · QueenSpikeRondoState.OnUpdate (cyclomatic 24) · ×1
  • QueenSpikeRondoState.OnUpdate (cyclomatic 24) Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenSpikeRondoState.cs:55 — QueenSpikeRondoState.OnUpdate has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SkeletronBoneMaelstromState.UpdateBeats (cyclomatic 24) · ×1
  • SkeletronBoneMaelstromState.UpdateBeats (cyclomatic 24) Content/NPCs/BrutalNPCs/BrutalSkeletron/States/SkeletronBoneMaelstromState.cs:71 — SkeletronBoneMaelstromState.UpdateBeats has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · PrimeViceExecutionState.ChoreographShooter (cyclomatic 24) · ×1
  • PrimeViceExecutionState.ChoreographShooter (cyclomatic 24) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/PrimeViceExecutionState.cs:492 — PrimeViceExecutionState.ChoreographShooter has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FssHead.AI (cyclomatic 24) · ×1
  • FssHead.AI (cyclomatic 24) Content/NPCs/FestersandSerpents/FssHead.cs:231 — FssHead.AI has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ScrapFusedFrenzyState.OnUpdate (cyclomatic 24) · ×1
  • ScrapFusedFrenzyState.OnUpdate (cyclomatic 24) Content/NPCs/ScrapCommanders/States/ScrapFusedFrenzyState.cs:39 — ScrapFusedFrenzyState.OnUpdate has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaPanelState.Update (cyclomatic 24) · ×1
  • KikasaPanelState.Update (cyclomatic 24) Content/Narrative/Presentation/Skins/Kikasa/KikasaPanelState.cs:48 — KikasaPanelState.Update has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DungeonworldSnuff.Advance (cyclomatic 24) · ×1
  • DungeonworldSnuff.Advance (cyclomatic 24) Content/Scenarios/Dungeonworld/Ambience/DungeonworldSnuff.cs:257 — DungeonworldSnuff.Advance has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SlagVentBelt.TryBuildCavern (cyclomatic 24) · ×1
  • SlagVentBelt.TryBuildCavern (cyclomatic 24) Content/Scenarios/Dungeonworld/Gen/Zones/SlagVentBelt.cs:127 — SlagVentBelt.TryBuildCavern has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DeepGaolWraith.UpdateDeath (cyclomatic 24) · ×1
  • DeepGaolWraith.UpdateDeath (cyclomatic 24) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:1498 — DeepGaolWraith.UpdateDeath has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OldNetThreatField.SeedTripwires (cyclomatic 24) · ×1
  • OldNetThreatField.SeedTripwires (cyclomatic 24) Content/Scenarios/OldNet/NPCs/OldNetThreatField.cs:669 — OldNetThreatField.SeedTripwires has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ChestInteraction.UpdateSlotInteraction (cyclomatic 24) · ×1
  • ChestInteraction.UpdateSlotInteraction (cyclomatic 24) Content/UIs/StorageUIs/ChestInteraction.cs:51 — ChestInteraction.UpdateSlotInteraction has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · HeadlessShadeProj.UpdateVisuals (cyclomatic 24) · ×1
  • HeadlessShadeProj.UpdateVisuals (cyclomatic 24) Content/Wraiths/Projectiles/HeadlessShadeProj.cs:756 — HeadlessShadeProj.UpdateVisuals has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MusicDirector.Arbitrate (cyclomatic 23) · ×1
  • MusicDirector.Arbitrate (cyclomatic 23) Common/MusicDirector.cs:120 — MusicDirector.Arbitrate 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.
D1 · Cyclomatic Complexity · QuestManagerUI.HandleMouseInput (cyclomatic 23) · ×1
  • QuestManagerUI.HandleMouseInput (cyclomatic 23) Content/EntrustManager/EntrustManagerUI.cs:416 — QuestManagerUI.HandleMouseInput 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.
D1 · Cyclomatic Complexity · EntrustTrackerWidget.Update (cyclomatic 23) · ×1
  • EntrustTrackerWidget.Update (cyclomatic 23) Content/EntrustManager/EntrustTrackerWidget.cs:113 — EntrustTrackerWidget.Update 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.
D1 · Cyclomatic Complexity · MournfogGrudgeRingProj.AI (cyclomatic 23) · ×1
  • MournfogGrudgeRingProj.AI (cyclomatic 23) Content/GameModes/BrutalMobs/Ambience/Mournfog/Projectiles/MournfogGrudgeRingProj.cs:95 — MournfogGrudgeRingProj.AI 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.
D1 · Cyclomatic Complexity · SporeshineRender.UpdateBySystem (cyclomatic 23) · ×1
  • SporeshineRender.UpdateBySystem (cyclomatic 23) Content/GameModes/BrutalMobs/Ambience/Sporeshine/SporeshineRender.cs:73 — SporeshineRender.UpdateBySystem 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.
D1 · Cyclomatic Complexity · VerdantAmbientRender.EndEntityDraw (cyclomatic 23) · ×1
  • VerdantAmbientRender.EndEntityDraw (cyclomatic 23) Content/GameModes/BrutalMobs/Ambience/Verdant/VerdantAmbientRender.cs:30 — VerdantAmbientRender.EndEntityDraw 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.
D1 · Cyclomatic Complexity · VerdantMireScheduler.TryFindMireAnchor (cyclomatic 23) · ×1
  • VerdantMireScheduler.TryFindMireAnchor (cyclomatic 23) Content/GameModes/BrutalMobs/Ambience/Verdant/VerdantMireScheduler.cs:79 — VerdantMireScheduler.TryFindMireAnchor 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.
D1 · Cyclomatic Complexity · EliteMoveNPC.ServerParry (cyclomatic 23) · ×1
  • EliteMoveNPC.ServerParry (cyclomatic 23) Content/GameModes/BrutalMobs/EliteMove/EliteMoveNPC.cs:242 — EliteMoveNPC.ServerParry 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.
D1 · Cyclomatic Complexity · FrmPoseTelegraphProj.AI (cyclomatic 23) · ×1
  • FrmPoseTelegraphProj.AI (cyclomatic 23) Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmPoseTelegraphProj.cs:72 — FrmPoseTelegraphProj.AI 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.
D1 · Cyclomatic Complexity · SandveilSurgeColumnProj.AI (cyclomatic 23) · ×1
  • SandveilSurgeColumnProj.AI (cyclomatic 23) Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilSurgeColumnProj.cs:93 — SandveilSurgeColumnProj.AI 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.
D1 · Cyclomatic Complexity · GsYoyoScheme.GsProjPostAI (cyclomatic 23) · ×1
  • GsYoyoScheme.GsProjPostAI (cyclomatic 23) Content/GameModes/GodSmith/Weapons/Yoyos/GsYoyoScheme.cs:78 — GsYoyoScheme.GsProjPostAI 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.
D1 · Cyclomatic Complexity · HackTimeNetSync.TryReadTarget (cyclomatic 23) · ×1
  • HackTimeNetSync.TryReadTarget (cyclomatic 23) Content/HackTimes/HackTimeNetSync.cs:1342 — HackTimeNetSync.TryReadTarget 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.
D1 · Cyclomatic Complexity · AutoCrafterTP.ConsumeIngredients (cyclomatic 23) · ×1
  • AutoCrafterTP.ConsumeIngredients (cyclomatic 23) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterTP.cs:436 — AutoCrafterTP.ConsumeIngredients 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.
D1 · Cyclomatic Complexity · AutoCrafterTile.DrawHologram (cyclomatic 23) · ×1
  • AutoCrafterTile.DrawHologram (cyclomatic 23) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterTile.cs:174 — AutoCrafterTile.DrawHologram 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.
D1 · Cyclomatic Complexity · AutoFisherTP.ScanWater (cyclomatic 23) · ×1
  • AutoFisherTP.ScanWater (cyclomatic 23) Content/Industrials/ElectricPowers/AutoFishers/AutoFisherTP.cs:282 — AutoFisherTP.ScanWater 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.
D1 · Cyclomatic Complexity · FluidInjectorTP.UpdateVisualFx (cyclomatic 23) · ×1
  • FluidInjectorTP.UpdateVisualFx (cyclomatic 23) Content/Industrials/ElectricPowers/FluidInjectors/FluidInjectorTP.cs:158 — FluidInjectorTP.UpdateVisualFx 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.
D1 · Cyclomatic Complexity · PotionBeaconTP.UpdateMachine (cyclomatic 23) · ×1
  • PotionBeaconTP.UpdateMachine (cyclomatic 23) Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconTP.cs:167 — PotionBeaconTP.UpdateMachine 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.
D1 · Cyclomatic Complexity · RiteMirrorPhantom.TryResolveWeaponShot (cyclomatic 23) · ×1
  • RiteMirrorPhantom.TryResolveWeaponShot (cyclomatic 23) Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMirrorPhantom.cs:114 — RiteMirrorPhantom.TryResolveWeaponShot 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.
D1 · Cyclomatic Complexity · BlackFlashSigilRender.DrawTimeSenseGhosts (cyclomatic 23) · ×1
  • BlackFlashSigilRender.DrawTimeSenseGhosts (cyclomatic 23) Content/Items/Accessories/BrutalRelics/MoonLord/BlackFlashSigilRender.cs:43 — BlackFlashSigilRender.DrawTimeSenseGhosts 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.
D1 · Cyclomatic Complexity · SoulbindingArmRender.EndEntityDraw (cyclomatic 23) · ×1
  • SoulbindingArmRender.EndEntityDraw (cyclomatic 23) Content/Items/Accessories/BrutalRelics/Skeletron/SoulbindingArmRender.cs:260 — SoulbindingArmRender.EndEntityDraw 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.
D1 · Cyclomatic Complexity · ElysiumGuidanceGlobalProj.PostAI (cyclomatic 23) · ×1
  • ElysiumGuidanceGlobalProj.PostAI (cyclomatic 23) Content/Items/Magic/Elysiums/Disciples/Philip.cs:74 — ElysiumGuidanceGlobalProj.PostAI 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.
D1 · Cyclomatic Complexity · BonefishOrbit.AI (cyclomatic 23) · ×1
  • BonefishOrbit.AI (cyclomatic 23) Content/LegendWeapon/HalibutLegend/FishSkills/FishBone.cs:169 — BonefishOrbit.AI 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.
D1 · Cyclomatic Complexity · KikasaDomainPlayer.HandleMutateKey (cyclomatic 23) · ×1
  • KikasaDomainPlayer.HandleMutateKey (cyclomatic 23) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainPlayer.cs:378 — KikasaDomainPlayer.HandleMutateKey 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.
D1 · Cyclomatic Complexity · KikasaDreamProjectileBan.IsSwallowed (cyclomatic 23) · ×1
  • KikasaDreamProjectileBan.IsSwallowed (cyclomatic 23) Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamProjectileBan.cs:73 — KikasaDreamProjectileBan.IsSwallowed 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.
D1 · Cyclomatic Complexity · KikasaDrown.StartAuthoritative (cyclomatic 23) · ×1
  • KikasaDrown.StartAuthoritative (cyclomatic 23) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrown.cs:402 — KikasaDrown.StartAuthoritative 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.
D1 · Cyclomatic Complexity · KikasaGunServant.DrawGlow (cyclomatic 23) · ×1
  • KikasaGunServant.DrawGlow (cyclomatic 23) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1573 — KikasaGunServant.DrawGlow 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.
D1 · Cyclomatic Complexity · KikasaDestroyerServant.UpdateDiveRam (cyclomatic 23) · ×1
  • KikasaDestroyerServant.UpdateDiveRam (cyclomatic 23) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:666 — KikasaDestroyerServant.UpdateDiveRam 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.
D1 · Cyclomatic Complexity · KikasaEmpressServant.UpdateEmerge (cyclomatic 23) · ×1
  • KikasaEmpressServant.UpdateEmerge (cyclomatic 23) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:245 — KikasaEmpressServant.UpdateEmerge 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.
D1 · Cyclomatic Complexity · KikasaEmpressServant.DrawGlow (cyclomatic 23) · ×1
  • KikasaEmpressServant.DrawGlow (cyclomatic 23) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:1036 — KikasaEmpressServant.DrawGlow 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.
D1 · Cyclomatic Complexity · KikasaFishronServant.UpdatePorpoise (cyclomatic 23) · ×1
  • KikasaFishronServant.UpdatePorpoise (cyclomatic 23) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:529 — KikasaFishronServant.UpdatePorpoise 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.
D1 · Cyclomatic Complexity · KikasaPrimeServant.AI (cyclomatic 23) · ×1
  • KikasaPrimeServant.AI (cyclomatic 23) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:255 — KikasaPrimeServant.AI 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.
D1 · Cyclomatic Complexity · KikasaPrimeServant.DrawGlowLayer (cyclomatic 23) · ×1
  • KikasaPrimeServant.DrawGlowLayer (cyclomatic 23) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1536 — KikasaPrimeServant.DrawGlowLayer 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.
D1 · Cyclomatic Complexity · KikasaQueenSlimeServant.UpdateDissolve (cyclomatic 23) · ×1
  • KikasaQueenSlimeServant.UpdateDissolve (cyclomatic 23) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:879 — KikasaQueenSlimeServant.UpdateDissolve 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.
D1 · Cyclomatic Complexity · KikasaTwinsFlameBreath.AI (cyclomatic 23) · ×1
  • KikasaTwinsFlameBreath.AI (cyclomatic 23) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsFlameBreath.cs:52 — KikasaTwinsFlameBreath.AI 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.
D1 · Cyclomatic Complexity · CrimsonRendCleave.AI (cyclomatic 23) · ×1
  • CrimsonRendCleave.AI (cyclomatic 23) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendCleave.cs:232 — CrimsonRendCleave.AI 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.
D1 · Cyclomatic Complexity · OnikiriPlayer.TryPetalPruneOnKill (cyclomatic 23) · ×1
  • OnikiriPlayer.TryPetalPruneOnKill (cyclomatic 23) Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs:2175 — OnikiriPlayer.TryPetalPruneOnKill 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.
D1 · Cyclomatic Complexity · SHPCSniperLockLineProj.AI (cyclomatic 23) · ×1
  • SHPCSniperLockLineProj.AI (cyclomatic 23) Content/LegendWeapon/SHPCLegend/Modules/Optic/SniperOpticModule.cs:281 — SHPCSniperLockLineProj.AI 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.
D1 · Cyclomatic Complexity · SHPCErgoEchoProj.AI (cyclomatic 23) · ×1
  • SHPCErgoEchoProj.AI (cyclomatic 23) Content/LegendWeapon/SHPCLegend/Modules/Stock/ErgonomicStockModule.cs:369 — SHPCErgoEchoProj.AI 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.
D1 · Cyclomatic Complexity · HimayoMenuButtons.Tick (cyclomatic 23) · ×1
  • HimayoMenuButtons.Tick (cyclomatic 23) Content/MainMenus/Himayo/HimayoMenuButtons.cs:61 — HimayoMenuButtons.Tick 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.
D1 · Cyclomatic Complexity · ShenyoMenuButtons.Tick (cyclomatic 23) · ×1
  • ShenyoMenuButtons.Tick (cyclomatic 23) Content/MainMenus/Shenyo/ShenyoMenuButtons.cs:63 — ShenyoMenuButtons.Tick 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.
D1 · Cyclomatic Complexity · BssDeathState.OnUpdate (cyclomatic 23) · ×1
  • BssDeathState.OnUpdate (cyclomatic 23) Content/NPCs/BloomsandSerpents/States/BssDeathState.cs:36 — BssDeathState.OnUpdate 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.
D1 · Cyclomatic Complexity · BssStormTransitionState.OnUpdate (cyclomatic 23) · ×1
  • BssStormTransitionState.OnUpdate (cyclomatic 23) Content/NPCs/BloomsandSerpents/States/BssStormTransitionState.cs:37 — BssStormTransitionState.OnUpdate 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.
D1 · Cyclomatic Complexity · DeerclopsGazeRoarState.OnUpdate (cyclomatic 23) · ×1
  • DeerclopsGazeRoarState.OnUpdate (cyclomatic 23) Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsGazeRoarState.cs:35 — DeerclopsGazeRoarState.OnUpdate 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.
D1 · Cyclomatic Complexity · EowBossBar.ModifyInfo (cyclomatic 23) · ×1
  • EowBossBar.ModifyInfo (cyclomatic 23) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/EowBossBar.cs:27 — EowBossBar.ModifyInfo 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.
D1 · Cyclomatic Complexity · KingSlimeEngulfState.OnUpdate (cyclomatic 23) · ×1
  • KingSlimeEngulfState.OnUpdate (cyclomatic 23) Content/NPCs/BrutalNPCs/BrutalKingSlime/States/KingSlimeEngulfState.cs:94 — KingSlimeEngulfState.OnUpdate 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.
D1 · Cyclomatic Complexity · KingSlimeGelMortarState.OnUpdate (cyclomatic 23) · ×1
  • KingSlimeGelMortarState.OnUpdate (cyclomatic 23) Content/NPCs/BrutalNPCs/BrutalKingSlime/States/KingSlimeGelMortarState.cs:46 — KingSlimeGelMortarState.OnUpdate 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.
D1 · Cyclomatic Complexity · KingSlimePhaseShiftState.OnUpdate (cyclomatic 23) · ×1
  • KingSlimePhaseShiftState.OnUpdate (cyclomatic 23) Content/NPCs/BrutalNPCs/BrutalKingSlime/States/KingSlimePhaseShiftState.cs:35 — KingSlimePhaseShiftState.OnUpdate 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.
D1 · Cyclomatic Complexity · PincerBindTether.AI (cyclomatic 23) · ×1
  • PincerBindTether.AI (cyclomatic 23) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/PincerBindTether.cs:65 — PincerBindTether.AI 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.
D1 · Cyclomatic Complexity · MoonLordHandAI.UpdateAlive (cyclomatic 23) · ×1
  • MoonLordHandAI.UpdateAlive (cyclomatic 23) Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordHandAI.cs:117 — MoonLordHandAI.UpdateAlive 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.
D1 · Cyclomatic Complexity · SkeletronIntroState.UpdateBeats (cyclomatic 23) · ×1
  • SkeletronIntroState.UpdateBeats (cyclomatic 23) Content/NPCs/BrutalNPCs/BrutalSkeletron/States/SkeletronIntroState.cs:69 — SkeletronIntroState.UpdateBeats 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.
D1 · Cyclomatic Complexity · PrimeArcChainProj.AI (cyclomatic 23) · ×1
  • PrimeArcChainProj.AI (cyclomatic 23) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeArcChainProj.cs:58 — PrimeArcChainProj.AI 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.
D1 · Cyclomatic Complexity · ScrapHubState.OnUpdate (cyclomatic 23) · ×1
  • ScrapHubState.OnUpdate (cyclomatic 23) Content/NPCs/ScrapCommanders/States/ScrapHubState.cs:24 — ScrapHubState.OnUpdate 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.
D1 · Cyclomatic Complexity · ScrapSawLaunchState.OnUpdate (cyclomatic 23) · ×1
  • ScrapSawLaunchState.OnUpdate (cyclomatic 23) Content/NPCs/ScrapCommanders/States/ScrapSawLaunchState.cs:36 — ScrapSawLaunchState.OnUpdate 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.
D1 · Cyclomatic Complexity · SeaShrimpAbyssJetState.OnUpdate (cyclomatic 23) · ×1
  • SeaShrimpAbyssJetState.OnUpdate (cyclomatic 23) Content/NPCs/SeaShrimp/States/SeaShrimpAbyssJetState.cs:38 — SeaShrimpAbyssJetState.OnUpdate 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.
D1 · Cyclomatic Complexity · GaolBossRoomWatcher.PostUpdateNPCs (cyclomatic 23) · ×1
  • GaolBossRoomWatcher.PostUpdateNPCs (cyclomatic 23) Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolBossRoomWatcher.cs:97 — GaolBossRoomWatcher.PostUpdateNPCs 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.
D1 · Cyclomatic Complexity · L2EscapeTunnel.Carve (cyclomatic 23) · ×1
  • L2EscapeTunnel.Carve (cyclomatic 23) Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2EscapeTunnel.cs:223 — L2EscapeTunnel.Carve 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.
D1 · Cyclomatic Complexity · L3BookTower.Build (cyclomatic 23) · ×1
  • L3BookTower.Build (cyclomatic 23) Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3BookTower.cs:53 — L3BookTower.Build 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.
D1 · Cyclomatic Complexity · L3Rooms.BuildVault (cyclomatic 23) · ×1
  • L3Rooms.BuildVault (cyclomatic 23) Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Rooms.cs:337 — L3Rooms.BuildVault 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.
D1 · Cyclomatic Complexity · L6Content.PlanAndBuild (cyclomatic 23) · ×1
  • L6Content.PlanAndBuild (cyclomatic 23) Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Content.cs:43 — L6Content.PlanAndBuild 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.
D1 · Cyclomatic Complexity · DeepGaolWraith.UpdateFollow (cyclomatic 23) · ×1
  • DeepGaolWraith.UpdateFollow (cyclomatic 23) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:750 — DeepGaolWraith.UpdateFollow 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.
D1 · Cyclomatic Complexity · Undrowned.PickNextAttack (cyclomatic 23) · ×1
  • Undrowned.PickNextAttack (cyclomatic 23) Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:736 — Undrowned.PickNextAttack 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.
D1 · Cyclomatic Complexity · UndrownedVFX.DrawAndAdvance (cyclomatic 23) · ×1
  • UndrownedVFX.DrawAndAdvance (cyclomatic 23) Content/Scenarios/Dungeonworld/NPCs/UndrownedVFX.cs:186 — UndrownedVFX.DrawAndAdvance 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.
D1 · Cyclomatic Complexity · KiyumeLampEvents.UpdateFall (cyclomatic 23) · ×1
  • KiyumeLampEvents.UpdateFall (cyclomatic 23) Content/Scenarios/Kiyume/Ambience/KiyumeLampEvents.cs:126 — KiyumeLampEvents.UpdateFall 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.
D1 · Cyclomatic Complexity · KiyumeHoundDirector.TrySpawnAt (cyclomatic 23) · ×1
  • KiyumeHoundDirector.TrySpawnAt (cyclomatic 23) Content/Scenarios/Kiyume/NPCs/KiyumeHoundDirector.cs:235 — KiyumeHoundDirector.TrySpawnAt 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.
D1 · Cyclomatic Complexity · OldDuchestTP.Update (cyclomatic 23) · ×1
  • OldDuchestTP.Update (cyclomatic 23) Content/Scenarios/OldDuke/OldDuchests/OldDuchestTP.cs:132 — OldDuchestTP.Update 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.
D1 · Cyclomatic Complexity · EbnBarsDisplay.DrawMana (cyclomatic 23) · ×1
  • EbnBarsDisplay.DrawMana (cyclomatic 23) Content/Scenarios/SupCal/End/EternalBlazingNow/EbnBarsDisplay.cs:324 — EbnBarsDisplay.DrawMana 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.
D1 · Cyclomatic Complexity · AetherglimPlayer.UpdateDeepPull (cyclomatic 22) · ×1
  • AetherglimPlayer.UpdateDeepPull (cyclomatic 22) Content/GameModes/BrutalMobs/Ambience/Aetherglim/AetherglimPlayer.cs:139 — AetherglimPlayer.UpdateDeepPull has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · NyxdepthGaze.Update (cyclomatic 22) · ×1
  • NyxdepthGaze.Update (cyclomatic 22) Content/GameModes/BrutalMobs/Ambience/Nyxdepth/NyxdepthGaze.cs:54 — NyxdepthGaze.Update has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · WoodsongBrambleProj.AI (cyclomatic 22) · ×1
  • WoodsongBrambleProj.AI (cyclomatic 22) Content/GameModes/BrutalMobs/Ambience/Woodsong/WoodsongBramble.cs:215 — WoodsongBrambleProj.AI has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FrmOrnamentRowOmen.AI (cyclomatic 22) · ×1
  • FrmOrnamentRowOmen.AI (cyclomatic 22) Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmOrnamentRowOmen.cs:75 — FrmOrnamentRowOmen.AI has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · GyGhostNameThread.AI (cyclomatic 22) · ×1
  • GyGhostNameThread.AI (cyclomatic 22) Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyGhostNameThread.cs:72 — GyGhostNameThread.AI has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MrtLaserMarkLine.PreDraw (cyclomatic 22) · ×1
  • MrtLaserMarkLine.PreDraw (cyclomatic 22) Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserMarkLine.cs:170 — MrtLaserMarkLine.PreDraw has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · StonebornBrutalNPC.TickTelegraph (cyclomatic 22) · ×1
  • StonebornBrutalNPC.TickTelegraph (cyclomatic 22) Content/GameModes/BrutalMobs/Stoneborn/StonebornBrutalNPC.cs:398 — StonebornBrutalNPC.TickTelegraph has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · WastesElementRing.AI (cyclomatic 22) · ×1
  • WastesElementRing.AI (cyclomatic 22) Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesElementRing.cs:51 — WastesElementRing.AI has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · WastesSandGeyserProj.AI (cyclomatic 22) · ×1
  • WastesSandGeyserProj.AI (cyclomatic 22) Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandGeyserProj.cs:83 — WastesSandGeyserProj.AI has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · AutoCrafterUI.DrawRecipeList (cyclomatic 22) · ×1
  • AutoCrafterUI.DrawRecipeList (cyclomatic 22) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:433 — AutoCrafterUI.DrawRecipeList has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ProcessingChainVFX.OreChipColors (cyclomatic 22) · ×1
  • ProcessingChainVFX.OreChipColors (cyclomatic 22) Content/Industrials/ElectricPowers/Crushers/ProcessingChainVFX.cs:76 — ProcessingChainVFX.OreChipColors has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ShieldGeneratorTP.UpdateDomeVisual (cyclomatic 22) · ×1
  • ShieldGeneratorTP.UpdateDomeVisual (cyclomatic 22) Content/Industrials/ElectricPowers/ShieldGenerators/ShieldGeneratorTP.cs:120 — ShieldGeneratorTP.UpdateDomeVisual has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SlimeVatTP.UpdateMachine (cyclomatic 22) · ×1
  • SlimeVatTP.UpdateMachine (cyclomatic 22) Content/Industrials/ElectricPowers/SlimeVats/SlimeVatTP.cs:314 — SlimeVatTP.UpdateMachine has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · WingsOfInterferencePlayer.PostUpdate (cyclomatic 22) · ×1
  • WingsOfInterferencePlayer.PostUpdate (cyclomatic 22) Content/Items/Accessories/BrutalRelics/EmpressOfLight/WingsOfInterference.cs:304 — WingsOfInterferencePlayer.PostUpdate has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EverdeepRing.AI (cyclomatic 22) · ×1
  • EverdeepRing.AI (cyclomatic 22) Content/Items/Magic/Everdeeps/EverdeepRing.cs:88 — EverdeepRing.AI has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DawnshatterHeld.ConsumeWindows (cyclomatic 22) · ×1
  • DawnshatterHeld.ConsumeWindows (cyclomatic 22) Content/Items/Melee/DawnshatterAzures/DawnshatterHeld.cs:571 — DawnshatterHeld.ConsumeWindows has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ShatterfangHeld.InitStage (cyclomatic 22) · ×1
  • ShatterfangHeld.InitStage (cyclomatic 22) Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:133 — ShatterfangHeld.InitStage has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · WGMaterializationRenderer.Draw (cyclomatic 22) · ×1
  • WGMaterializationRenderer.Draw (cyclomatic 22) Content/Items/Melee/WeaverGrievanceses/WGMaterializationRenderer.cs:31 — WGMaterializationRenderer.Draw has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · TiroFinaleRenderer.DrawHeldLayer (cyclomatic 22) · ×1
  • TiroFinaleRenderer.DrawHeldLayer (cyclomatic 22) Content/Items/Ranged/TiroFinales/TiroFinaleRenderer.cs:41 — TiroFinaleRenderer.DrawHeldLayer has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FishingFly.AI (cyclomatic 22) · ×1
  • FishingFly.AI (cyclomatic 22) Content/LegendWeapon/HalibutLegend/FishSkills/FishSwarm.cs:510 — FishingFly.AI has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FishingFly.PreDraw (cyclomatic 22) · ×1
  • FishingFly.PreDraw (cyclomatic 22) Content/LegendWeapon/HalibutLegend/FishSkills/FishSwarm.cs:1106 — FishingFly.PreDraw has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaDreamHound.UpdateFrame (cyclomatic 22) · ×1
  • KikasaDreamHound.UpdateFrame (cyclomatic 22) Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamHound.cs:814 — KikasaDreamHound.UpdateFrame has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaRainRender.DrawInkBodies (cyclomatic 22) · ×1
  • KikasaRainRender.DrawInkBodies (cyclomatic 22) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:177 — KikasaRainRender.DrawInkBodies has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaRainUmbrella.FireDrop (cyclomatic 22) · ×1
  • KikasaRainUmbrella.FireDrop (cyclomatic 22) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:1366 — KikasaRainUmbrella.FireDrop has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaGunBullet.AI (cyclomatic 22) · ×1
  • KikasaGunBullet.AI (cyclomatic 22) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunBullet.cs:76 — KikasaGunBullet.AI has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaRodServant.UpdateFish (cyclomatic 22) · ×1
  • KikasaRodServant.UpdateFish (cyclomatic 22) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:371 — KikasaRodServant.UpdateFish has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaZenithServant.UpdateBlade (cyclomatic 22) · ×1
  • KikasaZenithServant.UpdateBlade (cyclomatic 22) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:971 — KikasaZenithServant.UpdateBlade has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaBrainServant.DrawBloodForms (cyclomatic 22) · ×1
  • KikasaBrainServant.DrawBloodForms (cyclomatic 22) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1265 — KikasaBrainServant.DrawBloodForms has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaCultistServant.AI (cyclomatic 22) · ×1
  • KikasaCultistServant.AI (cyclomatic 22) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:216 — KikasaCultistServant.AI has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaFishronServant.UpdateEmerge (cyclomatic 22) · ×1
  • KikasaFishronServant.UpdateEmerge (cyclomatic 22) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:327 — KikasaFishronServant.UpdateEmerge has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaGolemServant.AI (cyclomatic 22) · ×1
  • KikasaGolemServant.AI (cyclomatic 22) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:235 — KikasaGolemServant.AI has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaGolemServant.UpdateEmerge (cyclomatic 22) · ×1
  • KikasaGolemServant.UpdateEmerge (cyclomatic 22) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:315 — KikasaGolemServant.UpdateEmerge has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaGolemServant.UpdateDissolve (cyclomatic 22) · ×1
  • KikasaGolemServant.UpdateDissolve (cyclomatic 22) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:876 — KikasaGolemServant.UpdateDissolve has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaKingSlimeServant.UpdateFollow (cyclomatic 22) · ×1
  • KikasaKingSlimeServant.UpdateFollow (cyclomatic 22) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:502 — KikasaKingSlimeServant.UpdateFollow has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaPlanteraServant.UpdateDissolve (cyclomatic 22) · ×1
  • KikasaPlanteraServant.UpdateDissolve (cyclomatic 22) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1016 — KikasaPlanteraServant.UpdateDissolve has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaTwinsServant.UpdateDissolve (cyclomatic 22) · ×1
  • KikasaTwinsServant.UpdateDissolve (cyclomatic 22) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:879 — KikasaTwinsServant.UpdateDissolve has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaTwinsServant.DrawGlow (cyclomatic 22) · ×1
  • KikasaTwinsServant.DrawGlow (cyclomatic 22) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1606 — KikasaTwinsServant.DrawGlow has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaWallOfFleshServant.UpdateEmerge (cyclomatic 22) · ×1
  • KikasaWallOfFleshServant.UpdateEmerge (cyclomatic 22) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:292 — KikasaWallOfFleshServant.UpdateEmerge has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · PRT_CrimsonSteelSpark.TryRicochet (cyclomatic 22) · ×1
  • PRT_CrimsonSteelSpark.TryRicochet (cyclomatic 22) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendParticles.cs:625 — PRT_CrimsonSteelSpark.TryRicochet has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniOmokage.UpdateReimprint (cyclomatic 22) · ×1
  • OniOmokage.UpdateReimprint (cyclomatic 22) Content/LegendWeapon/OnikiriLegend/OniOmokages/OniOmokage.cs:784 — OniOmokage.UpdateReimprint has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniSlash.UpdateBeatEvents (cyclomatic 22) · ×1
  • OniSlash.UpdateBeatEvents (cyclomatic 22) Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1026 — OniSlash.UpdateBeatEvents has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniMeiRite.Update (cyclomatic 22) · ×1
  • OniMeiRite.Update (cyclomatic 22) Content/LegendWeapon/OnikiriLegend/UI/OniMeiRite.cs:107 — OniMeiRite.Update has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniMeiUI.Draw (cyclomatic 22) · ×1
  • OniMeiUI.Draw (cyclomatic 22) Content/LegendWeapon/OnikiriLegend/UI/OniMeiUI.cs:1122 — OniMeiUI.Draw has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CyberspaceActionNet.ExecuteDomainAction (cyclomatic 22) · ×1
  • CyberspaceActionNet.ExecuteDomainAction (cyclomatic 22) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspaceActionNet.cs:192 — CyberspaceActionNet.ExecuteDomainAction has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SHPCMultiCellMatrixProj.AI (cyclomatic 22) · ×1
  • SHPCMultiCellMatrixProj.AI (cyclomatic 22) Content/LegendWeapon/SHPCLegend/Modules/Frame/MultiCellFrameModule.cs:163 — SHPCMultiCellMatrixProj.AI has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BssHead.AI (cyclomatic 22) · ×1
  • BssHead.AI (cyclomatic 22) Content/NPCs/BloomsandSerpents/BssHead.cs:272 — BssHead.AI has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BssLegRig.UpdateWalk (cyclomatic 22) · ×1
  • BssLegRig.UpdateWalk (cyclomatic 22) Content/NPCs/BloomsandSerpents/BssLegRig.cs:405 — BssLegRig.UpdateWalk has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BssSkyWeaveState.OnUpdate (cyclomatic 22) · ×1
  • BssSkyWeaveState.OnUpdate (cyclomatic 22) Content/NPCs/BloomsandSerpents/States/BssSkyWeaveState.cs:45 — BssSkyWeaveState.OnUpdate has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BrainMirrorFeintState.OnUpdate (cyclomatic 22) · ×1
  • BrainMirrorFeintState.OnUpdate (cyclomatic 22) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainMirrorFeintState.cs:45 — BrainMirrorFeintState.OnUpdate has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DeerclopsWhiteoutState.OnUpdate (cyclomatic 22) · ×1
  • DeerclopsWhiteoutState.OnUpdate (cyclomatic 22) Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsWhiteoutState.cs:34 — DeerclopsWhiteoutState.OnUpdate has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DestroyerProbeMatrixState.ExecuteFirePhase (cyclomatic 22) · ×1
  • DestroyerProbeMatrixState.ExecuteFirePhase (cyclomatic 22) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerProbeMatrixState.cs:173 — DestroyerProbeMatrixState.ExecuteFirePhase has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FishronTsunamiSweepState.OnUpdate (cyclomatic 22) · ×1
  • FishronTsunamiSweepState.OnUpdate (cyclomatic 22) Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronTsunamiSweepState.cs:52 — FishronTsunamiSweepState.OnUpdate has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EmpressDashGrabState.DashUpdate (cyclomatic 22) · ×1
  • EmpressDashGrabState.DashUpdate (cyclomatic 22) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/States/EmpressDashGrabState.cs:147 — EmpressDashGrabState.DashUpdate has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EmpressLacewingState.OnUpdate (cyclomatic 22) · ×1
  • EmpressLacewingState.OnUpdate (cyclomatic 22) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/States/EmpressLacewingState.cs:37 — EmpressLacewingState.OnUpdate has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EocMawDragState.OnUpdate (cyclomatic 22) · ×1
  • EocMawDragState.OnUpdate (cyclomatic 22) Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocMawDragState.cs:110 — EocMawDragState.OnUpdate has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · GolemFistPunchState.OnUpdate (cyclomatic 22) · ×1
  • GolemFistPunchState.OnUpdate (cyclomatic 22) Content/NPCs/BrutalNPCs/BrutalGolem/States/Fists/GolemFistStates.cs:126 — GolemFistPunchState.OnUpdate has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · WofTongueGrabState.OnUpdate (cyclomatic 22) · ×1
  • WofTongueGrabState.OnUpdate (cyclomatic 22) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/States/WofTongueGrabState.cs:119 — WofTongueGrabState.OnUpdate has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SeaShrimpSkyLeapState.OnUpdate (cyclomatic 22) · ×1
  • SeaShrimpSkyLeapState.OnUpdate (cyclomatic 22) Content/NPCs/SeaShrimp/States/SeaShrimpSkyLeapState.cs:40 — SeaShrimpSkyLeapState.OnUpdate has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · AmbientEmitters.EmitAir (cyclomatic 22) · ×1
  • AmbientEmitters.EmitAir (cyclomatic 22) Content/Scenarios/Dungeonworld/Ambience/AmbientEmitters.cs:262 — AmbientEmitters.EmitAir has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DrownedTurnkey.UpdateVisualEnvelopes (cyclomatic 22) · ×1
  • DrownedTurnkey.UpdateVisualEnvelopes (cyclomatic 22) Content/Scenarios/Dungeonworld/NPCs/Elites/DrownedTurnkey.cs:275 — DrownedTurnkey.UpdateVisualEnvelopes has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · Undrowned.AI (cyclomatic 22) · ×1
  • Undrowned.AI (cyclomatic 22) Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:402 — Undrowned.AI has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · UndrownedThrone.UpdateRite (cyclomatic 22) · ×1
  • UndrownedThrone.UpdateRite (cyclomatic 22) Content/Scenarios/Dungeonworld/NPCs/UndrownedThrone.cs:179 — UndrownedThrone.UpdateRite has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OldDukeCampsiteGenerationService.PlaceOldChest (cyclomatic 22) · ×1
  • OldDukeCampsiteGenerationService.PlaceOldChest (cyclomatic 22) Content/Scenarios/OldDuke/Campsites/OldDukeCampsiteGenerationService.cs:136 — OldDukeCampsiteGenerationService.PlaceOldChest has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OldNetThreatField.ScanWindow (cyclomatic 22) · ×1
  • OldNetThreatField.ScanWindow (cyclomatic 22) Content/Scenarios/OldNet/NPCs/OldNetThreatField.cs:192 — OldNetThreatField.ScanWindow has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BrideHallRenderer.OnRiteTick (cyclomatic 22) · ×1
  • BrideHallRenderer.OnRiteTick (cyclomatic 22) Content/Wraiths/Abilities/CrimsonBrides/BrideHallRenderer.cs:79 — BrideHallRenderer.OnRiteTick has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · WraithPlayer.LoadData (cyclomatic 22) · ×1
  • WraithPlayer.LoadData (cyclomatic 22) Content/Wraiths/Runtime/WraithPlayer.cs:546 — WraithPlayer.LoadData has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · AstralveilSpearMarkProj.PreDraw (cyclomatic 21) · ×1
  • AstralveilSpearMarkProj.PreDraw (cyclomatic 21) Content/GameModes/BrutalMobs/Ambience/Astralveil/Projectiles/AstralveilSpearMarkProj.cs:176 — AstralveilSpearMarkProj.PreDraw has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DuskhallGazeRender.EndEntityDraw (cyclomatic 21) · ×1
  • DuskhallGazeRender.EndEntityDraw (cyclomatic 21) Content/GameModes/BrutalMobs/Ambience/Duskhall/DuskhallGazeRender.cs:35 — DuskhallGazeRender.EndEntityDraw has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FleshfenHazeRender.UpdateBySystem (cyclomatic 21) · ×1
  • FleshfenHazeRender.UpdateBySystem (cyclomatic 21) Content/GameModes/BrutalMobs/Ambience/Fleshfen/FleshfenHazeRender.cs:52 — FleshfenHazeRender.UpdateBySystem has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FrostveilGaleWallProj.ApplyToLocalPlayer (cyclomatic 21) · ×1
  • FrostveilGaleWallProj.ApplyToLocalPlayer (cyclomatic 21) Content/GameModes/BrutalMobs/Ambience/Frostveil/Projectiles/FrostveilGaleWallProj.cs:189 — FrostveilGaleWallProj.ApplyToLocalPlayer has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · NyxdepthSinkColumnProj.AI (cyclomatic 21) · ×1
  • NyxdepthSinkColumnProj.AI (cyclomatic 21) Content/GameModes/BrutalMobs/Ambience/Nyxdepth/Projectiles/NyxdepthSinkColumnProj.cs:54 — NyxdepthSinkColumnProj.AI has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EclMothronDiveOmen.AI (cyclomatic 21) · ×1
  • EclMothronDiveOmen.AI (cyclomatic 21) Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs:62 — EclMothronDiveOmen.AI has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FlgAimLineOmen.AI (cyclomatic 21) · ×1
  • FlgAimLineOmen.AI (cyclomatic 21) Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:67 — FlgAimLineOmen.AI has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FrmMeleeNPC.GingerActive (cyclomatic 21) · ×1
  • FrmMeleeNPC.GingerActive (cyclomatic 21) Content/GameModes/BrutalMobs/FrostMoon/FrmMeleeNPC.cs:417 — FrmMeleeNPC.GingerActive has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FrmYetiConeOmen.AI (cyclomatic 21) · ×1
  • FrmYetiConeOmen.AI (cyclomatic 21) Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmYetiConeOmen.cs:88 — FrmYetiConeOmen.AI has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · LegionPoseOmen.AI (cyclomatic 21) · ×1
  • LegionPoseOmen.AI (cyclomatic 21) Content/GameModes/BrutalMobs/Legion/Projectiles/LegionPoseOmen.cs:72 — LegionPoseOmen.AI has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MrtTeslaArcProj.AI (cyclomatic 21) · ×1
  • MrtTeslaArcProj.AI (cyclomatic 21) Content/GameModes/BrutalMobs/Martians/Projectiles/MrtTeslaArcProj.cs:79 — MrtTeslaArcProj.AI has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OceanBrutalNPC.TickStrike (cyclomatic 21) · ×1
  • OceanBrutalNPC.TickStrike (cyclomatic 21) Content/GameModes/BrutalMobs/Ocean/OceanBrutalNPC.cs:633 — OceanBrutalNPC.TickStrike has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · GsPhoenixBlasterHeld.AI (cyclomatic 21) · ×1
  • GsPhoenixBlasterHeld.AI (cyclomatic 21) Content/GameModes/GodSmith/Weapons/Guns/GsPhoenixBlaster.cs:154 — GsPhoenixBlasterHeld.AI has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · GameModeTabUI.Update (cyclomatic 21) · ×1
  • GameModeTabUI.Update (cyclomatic 21) Content/GameModes/UI/GameModeTabUI.cs:99 — GameModeTabUI.Update has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · PlayerHackLinkRender.DrawSerpentine (cyclomatic 21) · ×1
  • PlayerHackLinkRender.DrawSerpentine (cyclomatic 21) Content/HackTimes/PvP/UI/PlayerHackLinkRender.cs:284 — PlayerHackLinkRender.DrawSerpentine has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · WaterScannable.CountNearbyBiomeTiles (cyclomatic 21) · ×1
  • WaterScannable.CountNearbyBiomeTiles (cyclomatic 21) Content/HackTimes/Scannables/WaterScannable.cs:161 — WaterScannable.CountNearbyBiomeTiles has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · HerbFarmerTP.ScanWorkArea (cyclomatic 21) · ×1
  • HerbFarmerTP.ScanWorkArea (cyclomatic 21) Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerTP.cs:273 — HerbFarmerTP.ScanWorkArea has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ItemPipelineTP.LoadData (cyclomatic 21) · ×1
  • ItemPipelineTP.LoadData (cyclomatic 21) Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs:921 — ItemPipelineTP.LoadData has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ArcaneEternityGlobalProj.OnSpawn (cyclomatic 21) · ×1
  • ArcaneEternityGlobalProj.OnSpawn (cyclomatic 21) Content/Items/Accessories/ArcaneThroneOfEternity.cs:812 — ArcaneEternityGlobalProj.OnSpawn has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MawWormProj.AI (cyclomatic 21) · ×1
  • MawWormProj.AI (cyclomatic 21) Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawWormProj.cs:103 — MawWormProj.AI has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BloomNovaBulbPlayer.TryLash (cyclomatic 21) · ×1
  • BloomNovaBulbPlayer.TryLash (cyclomatic 21) Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaBulb.cs:218 — BloomNovaBulbPlayer.TryLash has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · RefractionWaltzBeamProj.AI (cyclomatic 21) · ×1
  • RefractionWaltzBeamProj.AI (cyclomatic 21) Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzBeamProj.cs:93 — RefractionWaltzBeamProj.AI has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ElysiumRoseWindow.UpdateInteraction (cyclomatic 21) · ×1
  • ElysiumRoseWindow.UpdateInteraction (cyclomatic 21) Content/Items/Magic/Elysiums/UI/ElysiumRoseWindow.cs:125 — ElysiumRoseWindow.UpdateInteraction has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · PandemoniumChannel.AI (cyclomatic 21) · ×1
  • PandemoniumChannel.AI (cyclomatic 21) Content/Items/Magic/Pandemoniums/PandemoniumChannel.cs:123 — PandemoniumChannel.AI has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DestroyersBladeEXHeld.FireShots (cyclomatic 21) · ×1
  • DestroyersBladeEXHeld.FireShots (cyclomatic 21) Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:497 — DestroyersBladeEXHeld.FireShots has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DivineSourceBladeHeld.HandleParticles (cyclomatic 21) · ×1
  • DivineSourceBladeHeld.HandleParticles (cyclomatic 21) Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:633 — DivineSourceBladeHeld.HandleParticles has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CloudRide.UpdateCloudFishParticles (cyclomatic 21) · ×1
  • CloudRide.UpdateCloudFishParticles (cyclomatic 21) Content/LegendWeapon/HalibutLegend/FishSkills/FishCloud.cs:191 — CloudRide.UpdateCloudFishParticles has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DrizzleFishHolder.AI (cyclomatic 21) · ×1
  • DrizzleFishHolder.AI (cyclomatic 21) Content/LegendWeapon/HalibutLegend/FishSkills/FishDrizzle.cs:380 — DrizzleFishHolder.AI has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaDomainPlayer.UpdateLocal (cyclomatic 21) · ×1
  • KikasaDomainPlayer.UpdateLocal (cyclomatic 21) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainPlayer.cs:950 — KikasaDomainPlayer.UpdateLocal has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaLakeSurface.ApplyStanding (cyclomatic 21) · ×1
  • KikasaLakeSurface.ApplyStanding (cyclomatic 21) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaLakeSurface.cs:40 — KikasaLakeSurface.ApplyStanding has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaDrown.UpdateHoverOmen (cyclomatic 21) · ×1
  • KikasaDrown.UpdateHoverOmen (cyclomatic 21) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrown.cs:260 — KikasaDrown.UpdateHoverOmen has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaPlayerDrown.UpdateHoverOmen (cyclomatic 21) · ×1
  • KikasaPlayerDrown.UpdateHoverOmen (cyclomatic 21) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaPlayerDrown.cs:309 — KikasaPlayerDrown.UpdateHoverOmen has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaRainRender.EndEntityDraw (cyclomatic 21) · ×1
  • KikasaRainRender.EndEntityDraw (cyclomatic 21) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:30 — KikasaRainRender.EndEntityDraw has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaRainUmbrella.UpdatePour (cyclomatic 21) · ×1
  • KikasaRainUmbrella.UpdatePour (cyclomatic 21) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:1006 — KikasaRainUmbrella.UpdatePour has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaDeerclopsServant.UpdateDissolve (cyclomatic 21) · ×1
  • KikasaDeerclopsServant.UpdateDissolve (cyclomatic 21) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:877 — KikasaDeerclopsServant.UpdateDissolve has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaDeerclopsServant.GetPoseFrame (cyclomatic 21) · ×1
  • KikasaDeerclopsServant.GetPoseFrame (cyclomatic 21) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:1025 — KikasaDeerclopsServant.GetPoseFrame has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaEmpressServant.GetArmFrames (cyclomatic 21) · ×1
  • KikasaEmpressServant.GetArmFrames (cyclomatic 21) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:848 — KikasaEmpressServant.GetArmFrames has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaEyeServant.UpdateDash (cyclomatic 21) · ×1
  • KikasaEyeServant.UpdateDash (cyclomatic 21) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:423 — KikasaEyeServant.UpdateDash has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaFesterSerpentServant.UpdateIchorVolley (cyclomatic 21) · ×1
  • KikasaFesterSerpentServant.UpdateIchorVolley (cyclomatic 21) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:419 — KikasaFesterSerpentServant.UpdateIchorVolley has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaFishronServant.UpdateBubbleRing (cyclomatic 21) · ×1
  • KikasaFishronServant.UpdateBubbleRing (cyclomatic 21) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:755 — KikasaFishronServant.UpdateBubbleRing has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaGolemServant.UpdateMagma (cyclomatic 21) · ×1
  • KikasaGolemServant.UpdateMagma (cyclomatic 21) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:712 — KikasaGolemServant.UpdateMagma has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaPlanteraServant.UpdateRelocate (cyclomatic 21) · ×1
  • KikasaPlanteraServant.UpdateRelocate (cyclomatic 21) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:649 — KikasaPlanteraServant.UpdateRelocate has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaPlanteraServant.DrawGlow (cyclomatic 21) · ×1
  • KikasaPlanteraServant.DrawGlow (cyclomatic 21) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1519 — KikasaPlanteraServant.DrawGlow has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaPrimeServant.UpdateLaser (cyclomatic 21) · ×1
  • KikasaPrimeServant.UpdateLaser (cyclomatic 21) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:782 — KikasaPrimeServant.UpdateLaser has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaPrimeServant.UpdateDissolve (cyclomatic 21) · ×1
  • KikasaPrimeServant.UpdateDissolve (cyclomatic 21) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:886 — KikasaPrimeServant.UpdateDissolve has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaSeaShrimpServant.UpdateEmerge (cyclomatic 21) · ×1
  • KikasaSeaShrimpServant.UpdateEmerge (cyclomatic 21) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:322 — KikasaSeaShrimpServant.UpdateEmerge has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaSkeletronServant.UpdateSlam (cyclomatic 21) · ×1
  • KikasaSkeletronServant.UpdateSlam (cyclomatic 21) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:546 — KikasaSkeletronServant.UpdateSlam has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaWisp.Update (cyclomatic 21) · ×1
  • KikasaWisp.Update (cyclomatic 21) Content/LegendWeapon/KikasaLegend/KikasaWisps/KikasaWisp.cs:66 — KikasaWisp.Update has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaHudLead.PollFallbackKey (cyclomatic 21) · ×1
  • KikasaHudLead.PollFallbackKey (cyclomatic 21) Content/LegendWeapon/KikasaLegend/UI/KikasaHudLeadInput.cs:80 — KikasaHudLead.PollFallbackKey has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniMeiPaperEffigy.PreDraw (cyclomatic 21) · ×1
  • OniMeiPaperEffigy.PreDraw (cyclomatic 21) Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiPaperEffigy.cs:258 — OniMeiPaperEffigy.PreDraw has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniDomainPlayer.UpdateOpening (cyclomatic 21) · ×1
  • OniDomainPlayer.UpdateOpening (cyclomatic 21) Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainPlayer.cs:431 — OniDomainPlayer.UpdateOpening has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CyberBanish.ValidateAuthoritativeRequest (cyclomatic 21) · ×1
  • CyberBanish.ValidateAuthoritativeRequest (cyclomatic 21) Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBanish.cs:176 — CyberBanish.ValidateAuthoritativeRequest has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SHPCMossPatchProj.AI (cyclomatic 21) · ×1
  • SHPCMossPatchProj.AI (cyclomatic 21) Content/LegendWeapon/SHPCLegend/Modules/Barrel/MossboundBarrelModule.cs:140 — SHPCMossPatchProj.AI has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SHPCRedlineGaugeProj.AI (cyclomatic 21) · ×1
  • SHPCRedlineGaugeProj.AI (cyclomatic 21) Content/LegendWeapon/SHPCLegend/Modules/Barrel/RapidBarrelModule.cs:447 — SHPCRedlineGaugeProj.AI has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SHPCStormFieldProj.AI (cyclomatic 21) · ×1
  • SHPCStormFieldProj.AI (cyclomatic 21) Content/LegendWeapon/SHPCLegend/Modules/Stock/StormStockModule.cs:102 — SHPCStormFieldProj.AI has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SHPCOverride.On_Shoot (cyclomatic 21) · ×1
  • SHPCOverride.On_Shoot (cyclomatic 21) Content/LegendWeapon/SHPCLegend/SHPCOverride.cs:180 — SHPCOverride.On_Shoot has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BrainFrenzyChaseState.OnUpdate (cyclomatic 21) · ×1
  • BrainFrenzyChaseState.OnUpdate (cyclomatic 21) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainFrenzyChaseState.cs:38 — BrainFrenzyChaseState.OnUpdate has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DeerclopsIntroState.OnUpdate (cyclomatic 21) · ×1
  • DeerclopsIntroState.OnUpdate (cyclomatic 21) Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsIntroState.cs:28 — DeerclopsIntroState.OnUpdate has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EowBurrowAmbushState.UpdateErupt (cyclomatic 21) · ×1
  • EowBurrowAmbushState.UpdateErupt (cyclomatic 21) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowBurrowAmbushState.cs:182 — EowBurrowAmbushState.UpdateErupt has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · GolemRenderHelper.DrawFistThruster (cyclomatic 21) · ×1
  • GolemRenderHelper.DrawFistThruster (cyclomatic 21) Content/NPCs/BrutalNPCs/BrutalGolem/Rendering/GolemRenderHelper.cs:200 — GolemRenderHelper.DrawFistThruster has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KingSlimeMassEjectState.OnUpdate (cyclomatic 21) · ×1
  • KingSlimeMassEjectState.OnUpdate (cyclomatic 21) Content/NPCs/BrutalNPCs/BrutalKingSlime/States/KingSlimeMassEjectState.cs:51 — KingSlimeMassEjectState.OnUpdate has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · TwinsTetherArc.AI (cyclomatic 21) · ×1
  • TwinsTetherArc.AI (cyclomatic 21) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/TwinsTetherArc.cs:50 — TwinsTetherArc.AI has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · TwinsPincerGrabState.UpdateGrabBeats (cyclomatic 21) · ×1
  • TwinsPincerGrabState.UpdateGrabBeats (cyclomatic 21) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsPincerGrabState.cs:580 — TwinsPincerGrabState.UpdateGrabBeats has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · QBIntroState.OnUpdate (cyclomatic 21) · ×1
  • QBIntroState.OnUpdate (cyclomatic 21) Content/NPCs/BrutalNPCs/BrutalQueenBee/States/QBIntroState.cs:40 — QBIntroState.OnUpdate has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · QueenPrismBeamProj.AI (cyclomatic 21) · ×1
  • QueenPrismBeamProj.AI (cyclomatic 21) Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenPrismBeamProj.cs:147 — QueenPrismBeamProj.AI has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · QueenRoyalChandelierProj.AI (cyclomatic 21) · ×1
  • QueenRoyalChandelierProj.AI (cyclomatic 21) Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenRoyalChandelierProj.cs:63 — QueenRoyalChandelierProj.AI has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · QueenCrystalDiveStompState.OnUpdate (cyclomatic 21) · ×1
  • QueenCrystalDiveStompState.OnUpdate (cyclomatic 21) Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenCrystalDiveStompState.cs:40 — QueenCrystalDiveStompState.OnUpdate has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · QueenDeathState.OnUpdate (cyclomatic 21) · ×1
  • QueenDeathState.OnUpdate (cyclomatic 21) Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenDespawnState.cs:112 — QueenDeathState.OnUpdate has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · PrimeArmStateBase.AnchoredFollow (cyclomatic 21) · ×1
  • PrimeArmStateBase.AnchoredFollow (cyclomatic 21) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Core/IPrimeArmState.cs:126 — PrimeArmStateBase.AnchoredFollow has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · HeadPrimeAI.TryBeginViceExecution (cyclomatic 21) · ×1
  • HeadPrimeAI.TryBeginViceExecution (cyclomatic 21) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/HeadPrimeAI.cs:522 — HeadPrimeAI.TryBeginViceExecution has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · WofRetinaScanBeam.AI (cyclomatic 21) · ×1
  • WofRetinaScanBeam.AI (cyclomatic 21) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofRetinaScanBeam.cs:104 — WofRetinaScanBeam.AI has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · WofAdvanceState.PickNextAttack (cyclomatic 21) · ×1
  • WofAdvanceState.PickNextAttack (cyclomatic 21) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/States/WofAdvanceState.cs:82 — WofAdvanceState.PickNextAttack has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · WallOfFleshAI.Draw (cyclomatic 21) · ×1
  • WallOfFleshAI.Draw (cyclomatic 21) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/WallOfFleshAI.cs:501 — WallOfFleshAI.Draw has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FssLegRig.UpdateWalk (cyclomatic 21) · ×1
  • FssLegRig.UpdateWalk (cyclomatic 21) Content/NPCs/FestersandSerpents/FssLegRig.cs:232 — FssLegRig.UpdateWalk has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ScrapHubState.PickAttack (cyclomatic 21) · ×1
  • ScrapHubState.PickAttack (cyclomatic 21) Content/NPCs/ScrapCommanders/States/ScrapHubState.cs:131 — ScrapHubState.PickAttack has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ScrapPhaseTransitionState.OnUpdate (cyclomatic 21) · ×1
  • ScrapPhaseTransitionState.OnUpdate (cyclomatic 21) Content/NPCs/ScrapCommanders/States/ScrapPhaseTransitionState.cs:34 — ScrapPhaseTransitionState.OnUpdate has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SeaShrimpBubbleBatState.OnUpdate (cyclomatic 21) · ×1
  • SeaShrimpBubbleBatState.OnUpdate (cyclomatic 21) Content/NPCs/SeaShrimp/States/SeaShrimpBubbleBatState.cs:37 — SeaShrimpBubbleBatState.OnUpdate has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · QuestBookGuidePlayer.OnStepEnter (cyclomatic 21) · ×1
  • QuestBookGuidePlayer.OnStepEnter (cyclomatic 21) Content/QuestLogs/Guide/QuestBookGuidePlayer.cs:367 — QuestBookGuidePlayer.OnStepEnter has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · L6Colossus.BuildInterior (cyclomatic 21) · ×1
  • L6Colossus.BuildInterior (cyclomatic 21) Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Colossus.cs:253 — L6Colossus.BuildInterior has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · TurnkeyWaterlineRender.EndEntityDraw (cyclomatic 21) · ×1
  • TurnkeyWaterlineRender.EndEntityDraw (cyclomatic 21) Content/Scenarios/Dungeonworld/NPCs/Elites/TurnkeyRendering.cs:32 — TurnkeyWaterlineRender.EndEntityDraw has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · Undrowned.PreDraw (cyclomatic 21) · ×1
  • Undrowned.PreDraw (cyclomatic 21) Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:1786 — Undrowned.PreDraw has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · HadalTerrainCarver.ApplyBioSpots (cyclomatic 21) · ×1
  • HadalTerrainCarver.ApplyBioSpots (cyclomatic 21) Content/Scenarios/Hadalworld/Gen/Core/HadalTerrainCarver.cs:474 — HadalTerrainCarver.ApplyBioSpots has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KiyumeDirector.TryClaimScare (cyclomatic 21) · ×1
  • KiyumeDirector.TryClaimScare (cyclomatic 21) Content/Scenarios/Kiyume/Ambience/KiyumeDirector.cs:79 — KiyumeDirector.TryClaimScare has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OldNetLurkerICE.PreDraw (cyclomatic 21) · ×1
  • OldNetLurkerICE.PreDraw (cyclomatic 21) Content/Scenarios/OldNet/NPCs/OldNetLurkerICE.cs:262 — OldNetLurkerICE.PreDraw has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OldNetTracerICE.PreDraw (cyclomatic 21) · ×1
  • OldNetTracerICE.PreDraw (cyclomatic 21) Content/Scenarios/OldNet/NPCs/OldNetTracerICE.cs:403 — OldNetTracerICE.PreDraw has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OldNetWardenICE.UpdateRain (cyclomatic 21) · ×1
  • OldNetWardenICE.UpdateRain (cyclomatic 21) Content/Scenarios/OldNet/NPCs/OldNetWardenICE.cs:452 — OldNetWardenICE.UpdateRain has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OldNetTripwireTile.SpecialDraw (cyclomatic 21) · ×1
  • OldNetTripwireTile.SpecialDraw (cyclomatic 21) Content/Scenarios/OldNet/Tiles/OldNetTripwireTile.cs:89 — OldNetTripwireTile.SpecialDraw has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · WorldGenSettingsCategory.DrawRowExtra (cyclomatic 21) · ×1
  • WorldGenSettingsCategory.DrawRowExtra (cyclomatic 21) Content/UIs/OverhaulSettings/WorldGenSettingsCategory.cs:411 — WorldGenSettingsCategory.DrawRowExtra has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SvgPathPen.Stroke (cyclomatic 21) · ×1
  • SvgPathPen.Stroke (cyclomatic 21) Content/UIs/UIEffect/SvgPathPen.cs:74 — SvgPathPen.Stroke has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CyberwareGuideLead.DrawOverlay (cyclomatic 20) · ×1
  • CyberwareGuideLead.DrawOverlay (cyclomatic 20) Content/Cyberwares/Tutorial/CyberwareGuideLead.cs:274 — CyberwareGuideLead.DrawOverlay has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CindercragAmbience.UpdateAuthority (cyclomatic 20) · ×1
  • CindercragAmbience.UpdateAuthority (cyclomatic 20) Content/GameModes/BrutalMobs/Ambience/Cindercrag/CindercragAmbience.cs:208 — CindercragAmbience.UpdateAuthority has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CindercragGlowRender.TrySampleCeiling (cyclomatic 20) · ×1
  • CindercragGlowRender.TrySampleCeiling (cyclomatic 20) Content/GameModes/BrutalMobs/Ambience/Cindercrag/CindercragGlowRender.cs:163 — CindercragGlowRender.TrySampleCeiling has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · LumindepthAmbientRender.UpdateDapples (cyclomatic 20) · ×1
  • LumindepthAmbientRender.UpdateDapples (cyclomatic 20) Content/GameModes/BrutalMobs/Ambience/Lumindepth/LumindepthAmbientRender.cs:82 — LumindepthAmbientRender.UpdateDapples has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · RotmireVentProj.AI (cyclomatic 20) · ×1
  • RotmireVentProj.AI (cyclomatic 20) Content/GameModes/BrutalMobs/Ambience/Rotmire/Projectiles/RotmireVentProj.cs:87 — RotmireVentProj.AI has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · StonewakeGazePillarProj.AI (cyclomatic 20) · ×1
  • StonewakeGazePillarProj.AI (cyclomatic 20) Content/GameModes/BrutalMobs/Ambience/Stonewake/Projectiles/StonewakeGazePillarProj.cs:93 — StonewakeGazePillarProj.AI has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · PRT_WoodsongRaven.PerchAI (cyclomatic 20) · ×1
  • PRT_WoodsongRaven.PerchAI (cyclomatic 20) Content/GameModes/BrutalMobs/Ambience/Woodsong/PRT_WoodsongRaven.cs:164 — PRT_WoodsongRaven.PerchAI has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · WoodsongAmbience.UpdateThreatWarning (cyclomatic 20) · ×1
  • WoodsongAmbience.UpdateThreatWarning (cyclomatic 20) Content/GameModes/BrutalMobs/Ambience/Woodsong/WoodsongAmbience.cs:548 — WoodsongAmbience.UpdateThreatWarning has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case 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: WoodsongAmbience.LocalInPureForest (cyclomatic 27) 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.
D1 · Cyclomatic Complexity · LegionNPC.ThiefStep (cyclomatic 20) · ×1
  • LegionNPC.ThiefStep (cyclomatic 20) Content/GameModes/BrutalMobs/Legion/LegionNPC.cs:815 — LegionNPC.ThiefStep has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MrtGuardShieldProj.AI (cyclomatic 20) · ×1
  • MrtGuardShieldProj.AI (cyclomatic 20) Content/GameModes/BrutalMobs/Martians/Projectiles/MrtGuardShieldProj.cs:70 — MrtGuardShieldProj.AI has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · PrtRicochetShot.AI (cyclomatic 20) · ×1
  • PrtRicochetShot.AI (cyclomatic 20) Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtRicochetShot.cs:89 — PrtRicochetShot.AI has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · PmkRootSpikeProj.AI (cyclomatic 20) · ×1
  • PmkRootSpikeProj.AI (cyclomatic 20) Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkRootSpikeProj.cs:87 — PmkRootSpikeProj.AI has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · PumpkinMoonNPC.TryStartEmberMove (cyclomatic 20) · ×1
  • PumpkinMoonNPC.TryStartEmberMove (cyclomatic 20) Content/GameModes/BrutalMobs/PumpkinMoon/PumpkinMoonNPC.cs:420 — PumpkinMoonNPC.TryStartEmberMove has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SandveilVortexArrayOmen.AI (cyclomatic 20) · ×1
  • SandveilVortexArrayOmen.AI (cyclomatic 20) Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilVortexArrayOmen.cs:135 — SandveilVortexArrayOmen.AI has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SkyFeatherFanOmen.AI (cyclomatic 20) · ×1
  • SkyFeatherFanOmen.AI (cyclomatic 20) Content/GameModes/BrutalMobs/Sky/Projectiles/SkyFeatherFanOmen.cs:88 — SkyFeatherFanOmen.AI has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · HackPanelRenderer.DrawConnectorTree (cyclomatic 20) · ×1
  • HackPanelRenderer.DrawConnectorTree (cyclomatic 20) Content/HackTimes/HackPanelRenderer.cs:963 — HackPanelRenderer.DrawConnectorTree has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SelfRigScannable.BuildScanData (cyclomatic 20) · ×1
  • SelfRigScannable.BuildScanData (cyclomatic 20) Content/HackTimes/Scannables/SelfRigScannable.cs:51 — SelfRigScannable.BuildScanData has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · AutoFisherLootTable.RollFish (cyclomatic 20) · ×1
  • AutoFisherLootTable.RollFish (cyclomatic 20) Content/Industrials/ElectricPowers/AutoFishers/AutoFisherLootTable.cs:208 — AutoFisherLootTable.RollFish has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CollectorTP.DrawStorageLinks (cyclomatic 20) · ×1
  • CollectorTP.DrawStorageLinks (cyclomatic 20) Content/Industrials/ElectricPowers/Collectors/CollectorTP.cs:540 — CollectorTP.DrawStorageLinks has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FluidInjectorTP.UpdateMachine (cyclomatic 20) · ×1
  • FluidInjectorTP.UpdateMachine (cyclomatic 20) Content/Industrials/ElectricPowers/FluidInjectors/FluidInjectorTP.cs:73 — FluidInjectorTP.UpdateMachine has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MushroomFarmerTP.UpdateMachine (cyclomatic 20) · ×1
  • MushroomFarmerTP.UpdateMachine (cyclomatic 20) Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:265 — MushroomFarmerTP.UpdateMachine has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ShimmerTransmuterTP.TryPlaceOutputs (cyclomatic 20) · ×1
  • ShimmerTransmuterTP.TryPlaceOutputs (cyclomatic 20) Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterTP.cs:318 — ShimmerTransmuterTP.TryPlaceOutputs has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CryoTurretTP.UpdateCryoField (cyclomatic 20) · ×1
  • CryoTurretTP.UpdateCryoField (cyclomatic 20) Content/Industrials/ElectricPowers/Turrets/CryoTurrets/CryoTurretTP.cs:125 — CryoTurretTP.UpdateCryoField has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ThermalHeatHazeRender.CollectSources (cyclomatic 20) · ×1
  • ThermalHeatHazeRender.CollectSources (cyclomatic 20) Content/Industrials/Generator/Thermal/ThermalHeatHazeRender.cs:30 — ThermalHeatHazeRender.CollectSources has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · WingsOfInterferencePlayer.DetectIntersections (cyclomatic 20) · ×1
  • WingsOfInterferencePlayer.DetectIntersections (cyclomatic 20) Content/Items/Accessories/BrutalRelics/EmpressOfLight/WingsOfInterference.cs:518 — WingsOfInterferencePlayer.DetectIntersections has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · RiteMoonFlare.AI (cyclomatic 20) · ×1
  • RiteMoonFlare.AI (cyclomatic 20) Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMoonFlare.cs:107 — RiteMoonFlare.AI has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · RiteRingPlayer.DetectVeilStep (cyclomatic 20) · ×1
  • RiteRingPlayer.DetectVeilStep (cyclomatic 20) Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteRing.cs:327 — RiteRingPlayer.DetectVeilStep has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · StarshipHeld.AI (cyclomatic 20) · ×1
  • StarshipHeld.AI (cyclomatic 20) Content/Items/Ranged/Starships/StarshipHeld.cs:84 — StarshipHeld.AI has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FishVoodooPlayer.OnSet (cyclomatic 20) · ×1
  • FishVoodooPlayer.OnSet (cyclomatic 20) Content/LegendWeapon/HalibutLegend/FishSkills/FishVoodoo.cs:37 — FishVoodooPlayer.OnSet has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FishVoodooRitual.AI (cyclomatic 20) · ×1
  • FishVoodooRitual.AI (cyclomatic 20) Content/LegendWeapon/HalibutLegend/FishSkills/FishVoodooRitual.cs:149 — FishVoodooRitual.AI has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaDomainPlayer.UpdateFlipping (cyclomatic 20) · ×1
  • KikasaDomainPlayer.UpdateFlipping (cyclomatic 20) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainPlayer.cs:1154 — KikasaDomainPlayer.UpdateFlipping has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaInkDrop.UpdatePlunge (cyclomatic 20) · ×1
  • KikasaInkDrop.UpdatePlunge (cyclomatic 20) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:445 — KikasaInkDrop.UpdatePlunge has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaArmsQuickSink.TryQuickSink (cyclomatic 20) · ×1
  • KikasaArmsQuickSink.TryQuickSink (cyclomatic 20) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaArmsQuickSink.cs:23 — KikasaArmsQuickSink.TryQuickSink has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaGunServant.AI (cyclomatic 20) · ×1
  • KikasaGunServant.AI (cyclomatic 20) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:261 — KikasaGunServant.AI has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaHalibutDomain.UpdateVisuals (cyclomatic 20) · ×1
  • KikasaHalibutDomain.UpdateVisuals (cyclomatic 20) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutDomain.cs:206 — KikasaHalibutDomain.UpdateVisuals has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaPandemoniumServant.UpdateBook (cyclomatic 20) · ×1
  • KikasaPandemoniumServant.UpdateBook (cyclomatic 20) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:724 — KikasaPandemoniumServant.UpdateBook has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaRodServant.PullCatch (cyclomatic 20) · ×1
  • KikasaRodServant.PullCatch (cyclomatic 20) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:453 — KikasaRodServant.PullCatch has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaWhipServant.UpdateWhips (cyclomatic 20) · ×1
  • KikasaWhipServant.UpdateWhips (cyclomatic 20) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:646 — KikasaWhipServant.UpdateWhips has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaBrainClot.AI (cyclomatic 20) · ×1
  • KikasaBrainClot.AI (cyclomatic 20) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:80 — KikasaBrainClot.AI has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaDeerclopsHail.AI (cyclomatic 20) · ×1
  • KikasaDeerclopsHail.AI (cyclomatic 20) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsHail.cs:53 — KikasaDeerclopsHail.AI has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaEaterServant.DrawRifts (cyclomatic 20) · ×1
  • KikasaEaterServant.DrawRifts (cyclomatic 20) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1377 — KikasaEaterServant.DrawRifts has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaEyeServant.UpdateEmerge (cyclomatic 20) · ×1
  • KikasaEyeServant.UpdateEmerge (cyclomatic 20) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:247 — KikasaEyeServant.UpdateEmerge has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaGolemServant.DrawGlow (cyclomatic 20) · ×1
  • KikasaGolemServant.DrawGlow (cyclomatic 20) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1336 — KikasaGolemServant.DrawGlow has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaMoonLordServant.AI (cyclomatic 20) · ×1
  • KikasaMoonLordServant.AI (cyclomatic 20) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:233 — KikasaMoonLordServant.AI has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaMoonLordServant.UpdateEmerge (cyclomatic 20) · ×1
  • KikasaMoonLordServant.UpdateEmerge (cyclomatic 20) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:410 — KikasaMoonLordServant.UpdateEmerge has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaMoonLordServant.DrawGlow (cyclomatic 20) · ×1
  • KikasaMoonLordServant.DrawGlow (cyclomatic 20) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1459 — KikasaMoonLordServant.DrawGlow has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaQueenBeeStinger.AI (cyclomatic 20) · ×1
  • KikasaQueenBeeStinger.AI (cyclomatic 20) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeStinger.cs:88 — KikasaQueenBeeStinger.AI has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaWallOfFleshServant.DrawWallBody (cyclomatic 20) · ×1
  • KikasaWallOfFleshServant.DrawWallBody (cyclomatic 20) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:948 — KikasaWallOfFleshServant.DrawWallBody has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaTeleportProj.EruptBeat (cyclomatic 20) · ×1
  • KikasaTeleportProj.EruptBeat (cyclomatic 20) Content/LegendWeapon/KikasaLegend/KikasaTeleports/KikasaTeleportProj.cs:269 — KikasaTeleportProj.EruptBeat has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniSeverStrike.UpdatePose (cyclomatic 20) · ×1
  • OniSeverStrike.UpdatePose (cyclomatic 20) Content/LegendWeapon/OnikiriLegend/OniDismembers/OniSeverStrike.cs:1259 — OniSeverStrike.UpdatePose has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniMeiUI.ResolveTag (cyclomatic 20) · ×1
  • OniMeiUI.ResolveTag (cyclomatic 20) Content/LegendWeapon/OnikiriLegend/UI/OniMeiUI.cs:1008 — OniMeiUI.ResolveTag has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EfficientGripModule.ConsumeZeroLossShot (cyclomatic 20) · ×1
  • EfficientGripModule.ConsumeZeroLossShot (cyclomatic 20) Content/LegendWeapon/SHPCLegend/Modules/Grip/EfficientGripModule.cs:196 — EfficientGripModule.ConsumeZeroLossShot has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MoldCodexPanel.Draw (cyclomatic 20) · ×1
  • MoldCodexPanel.Draw (cyclomatic 20) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:101 — MoldCodexPanel.Draw has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BrainBloodPulseState.OnUpdate (cyclomatic 20) · ×1
  • BrainBloodPulseState.OnUpdate (cyclomatic 20) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainBloodPulseState.cs:44 — BrainBloodPulseState.OnUpdate has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BrainIntroState.OnUpdate (cyclomatic 20) · ×1
  • BrainIntroState.OnUpdate (cyclomatic 20) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainIntroState.cs:43 — BrainIntroState.OnUpdate has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BrainMirrorStrikeState.OnUpdate (cyclomatic 20) · ×1
  • BrainMirrorStrikeState.OnUpdate (cyclomatic 20) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainMirrorStrikeState.cs:101 — BrainMirrorStrikeState.OnUpdate has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DestroyerEncircleState.OnUpdate (cyclomatic 20) · ×1
  • DestroyerEncircleState.OnUpdate (cyclomatic 20) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerEncircleState.cs:37 — DestroyerEncircleState.OnUpdate has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EmpressScreenRender.EndCaptureDraw (cyclomatic 20) · ×1
  • EmpressScreenRender.EndCaptureDraw (cyclomatic 20) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Rendering/EmpressScreenRender.cs:15 — EmpressScreenRender.EndCaptureDraw has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EmpressMoonShadowState.OnUpdate (cyclomatic 20) · ×1
  • EmpressMoonShadowState.OnUpdate (cyclomatic 20) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/States/EmpressMoonShadowState.cs:43 — EmpressMoonShadowState.OnUpdate has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KingSlimeTowerCollapseState.OnUpdate (cyclomatic 20) · ×1
  • KingSlimeTowerCollapseState.OnUpdate (cyclomatic 20) Content/NPCs/BrutalNPCs/BrutalKingSlime/States/KingSlimeTowerCollapseState.cs:48 — KingSlimeTowerCollapseState.OnUpdate has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CultistSeekerStar.AI (cyclomatic 20) · ×1
  • CultistSeekerStar.AI (cyclomatic 20) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistSeekerStar.cs:65 — CultistSeekerStar.AI has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CultistStarBead.AI (cyclomatic 20) · ×1
  • CultistStarBead.AI (cyclomatic 20) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistStarBead.cs:64 — CultistStarBead.AI has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CultistPlanetHurlState.OnUpdate (cyclomatic 20) · ×1
  • CultistPlanetHurlState.OnUpdate (cyclomatic 20) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistPlanetHurlState.cs:56 — CultistPlanetHurlState.OnUpdate has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · TwinsCombinedAttackState.ExecuteBurstPhase (cyclomatic 20) · ×1
  • TwinsCombinedAttackState.ExecuteBurstPhase (cyclomatic 20) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsCombinedAttackState.cs:240 — TwinsCombinedAttackState.ExecuteBurstPhase has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MoonLordHandAI.ApplyIdleEyeCue (cyclomatic 20) · ×1
  • MoonLordHandAI.ApplyIdleEyeCue (cyclomatic 20) Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordHandAI.cs:199 — MoonLordHandAI.ApplyIdleEyeCue has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MLordAnnihilationRayProj.AI (cyclomatic 20) · ×1
  • MLordAnnihilationRayProj.AI (cyclomatic 20) Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordAnnihilationRayProj.cs:173 — MLordAnnihilationRayProj.AI has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BrutalBeeAI.FormationBeeAI (cyclomatic 20) · ×1
  • BrutalBeeAI.FormationBeeAI (cyclomatic 20) Content/NPCs/BrutalNPCs/BrutalQueenBee/BrutalBeeAI.cs:45 — BrutalBeeAI.FormationBeeAI has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · QueenPrismVolleyState.OnUpdate (cyclomatic 20) · ×1
  • QueenPrismVolleyState.OnUpdate (cyclomatic 20) Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenPrismVolleyState.cs:37 — QueenPrismVolleyState.OnUpdate has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · QueenWingGaleWaltzState.OnUpdate (cyclomatic 20) · ×1
  • QueenWingGaleWaltzState.OnUpdate (cyclomatic 20) Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenWingGaleWaltzState.cs:42 — QueenWingGaleWaltzState.OnUpdate has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SkeletronHeadAI.EvaluateGlobalTransitions (cyclomatic 20) · ×1
  • SkeletronHeadAI.EvaluateGlobalTransitions (cyclomatic 20) Content/NPCs/BrutalNPCs/BrutalSkeletron/SkeletronHeadAI.cs:175 — SkeletronHeadAI.EvaluateGlobalTransitions has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · HandCrushState.OnUpdate (cyclomatic 20) · ×1
  • HandCrushState.OnUpdate (cyclomatic 20) Content/NPCs/BrutalNPCs/BrutalSkeletron/States/Hands/SkeletronHandStates.cs:204 — HandCrushState.OnUpdate has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · HandClapState.OnUpdate (cyclomatic 20) · ×1
  • HandClapState.OnUpdate (cyclomatic 20) Content/NPCs/BrutalNPCs/BrutalSkeletron/States/Hands/SkeletronHandStates.cs:418 — HandClapState.OnUpdate has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SkeletronSkullRainTeleportState.UpdateRound (cyclomatic 20) · ×1
  • SkeletronSkullRainTeleportState.UpdateRound (cyclomatic 20) Content/NPCs/BrutalNPCs/BrutalSkeletron/States/SkeletronSkullRainTeleportState.cs:63 — SkeletronSkullRainTeleportState.UpdateRound has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · WofWallField.ComputeScanTargets (cyclomatic 20) · ×1
  • WofWallField.ComputeScanTargets (cyclomatic 20) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Core/WofWallField.cs:87 — WofWallField.ComputeScanTargets has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · WofRotEyeBudProj.AI (cyclomatic 20) · ×1
  • WofRotEyeBudProj.AI (cyclomatic 20) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofRotEyeBudProj.cs:61 — WofRotEyeBudProj.AI has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · WallOfFleshAI.UpdateAdvance (cyclomatic 20) · ×1
  • WallOfFleshAI.UpdateAdvance (cyclomatic 20) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/WallOfFleshAI.cs:287 — WallOfFleshAI.UpdateAdvance has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ScrapHeadSwingState.OnUpdate (cyclomatic 20) · ×1
  • ScrapHeadSwingState.OnUpdate (cyclomatic 20) Content/NPCs/ScrapCommanders/States/ScrapHeadSwingState.cs:33 — ScrapHeadSwingState.OnUpdate has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SeaShrimpTailFlipStrikeState.OnUpdate (cyclomatic 20) · ×1
  • SeaShrimpTailFlipStrikeState.OnUpdate (cyclomatic 20) Content/NPCs/SeaShrimp/States/SeaShrimpTailFlipStrikeState.cs:32 — SeaShrimpTailFlipStrikeState.OnUpdate has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · VictorClinicPanel.UpdateInteraction (cyclomatic 20) · ×1
  • VictorClinicPanel.UpdateInteraction (cyclomatic 20) Content/NPCs/Victors/UIs/VictorClinicPanel.cs:182 — VictorClinicPanel.UpdateInteraction has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MusicToast.DrawContent (cyclomatic 20) · ×1
  • MusicToast.DrawContent (cyclomatic 20) Content/Narrative/MusicToast.cs:689 — MusicToast.DrawContent has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · PlayerDeath.ExecuteScapeGhostAuthority (cyclomatic 20) · ×1
  • PlayerDeath.ExecuteScapeGhostAuthority (cyclomatic 20) Content/Players/PlayerDeath.cs:186 — PlayerDeath.ExecuteScapeGhostAuthority has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · L3Content.PlanAndBuild (cyclomatic 20) · ×1
  • L3Content.PlanAndBuild (cyclomatic 20) Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Content.cs:80 — L3Content.PlanAndBuild has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · RestitchedBones.DrawAssembly (cyclomatic 20) · ×1
  • RestitchedBones.DrawAssembly (cyclomatic 20) Content/Scenarios/Dungeonworld/NPCs/Elites/BoneStitcher.cs:991 — RestitchedBones.DrawAssembly has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FoundryOverseer.UpdatePendulum (cyclomatic 20) · ×1
  • FoundryOverseer.UpdatePendulum (cyclomatic 20) Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:916 — FoundryOverseer.UpdatePendulum has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OverseerDormantRig.UpdateRite (cyclomatic 20) · ×1
  • OverseerDormantRig.UpdateRite (cyclomatic 20) Content/Scenarios/Dungeonworld/NPCs/OverseerDormantRig.cs:173 — OverseerDormantRig.UpdateRite has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · HadalTerrainCarver.BaseFill (cyclomatic 20) · ×1
  • HadalTerrainCarver.BaseFill (cyclomatic 20) Content/Scenarios/Hadalworld/Gen/Core/HadalTerrainCarver.cs:39 — HadalTerrainCarver.BaseFill has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FishoilQuestScenario.Tick (cyclomatic 20) · ×1
  • FishoilQuestScenario.Tick (cyclomatic 20) Content/Scenarios/Helen/Quest/FishoilQuest/FishoilQuestScenario.cs:74 — FishoilQuestScenario.Tick has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KiameRuins.TryBuildHut (cyclomatic 20) · ×1
  • KiameRuins.TryBuildHut (cyclomatic 20) Content/Scenarios/Kiame/Gen/KiameRuins.cs:60 — KiameRuins.TryBuildHut has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniRainWorldTransition.AdvanceEnvelopes (cyclomatic 20) · ×1
  • OniRainWorldTransition.AdvanceEnvelopes (cyclomatic 20) Content/Scenarios/Kiame/Overlay/OniRainWorldTransition.cs:133 — OniRainWorldTransition.AdvanceEnvelopes has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KiameWaterRender.EndCaptureDraw (cyclomatic 20) · ×1
  • KiameWaterRender.EndCaptureDraw (cyclomatic 20) Content/Scenarios/Kiame/Water/KiameWaterRender.cs:58 — KiameWaterRender.EndCaptureDraw has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KiyumeHound.SampleSenses (cyclomatic 20) · ×1
  • KiyumeHound.SampleSenses (cyclomatic 20) Content/Scenarios/Kiyume/NPCs/KiyumeHound.cs:213 — KiyumeHound.SampleSenses has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OldNetSky.Draw (cyclomatic 20) · ×1
  • OldNetSky.Draw (cyclomatic 20) Content/Scenarios/OldNet/Backgrounds/OldNetSky.cs:75 — OldNetSky.Draw has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OldNetThreatField.TickBulkheads (cyclomatic 20) · ×1
  • OldNetThreatField.TickBulkheads (cyclomatic 20) Content/Scenarios/OldNet/NPCs/OldNetThreatField.cs:457 — OldNetThreatField.TickBulkheads has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EbnBarsDisplay.PreDrawResources (cyclomatic 20) · ×1
  • EbnBarsDisplay.PreDrawResources (cyclomatic 20) Content/Scenarios/SupCal/End/EternalBlazingNow/EbnBarsDisplay.cs:89 — EbnBarsDisplay.PreDrawResources has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SylvanOutpost.BlendEdge (cyclomatic 20) · ×1
  • SylvanOutpost.BlendEdge (cyclomatic 20) Content/Structures/DatIO/SylvanOutpost.cs:532 — SylvanOutpost.BlendEdge has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · QuestLogsAPI.ApplyLayout (cyclomatic 19) · ×1
  • QuestLogsAPI.ApplyLayout (cyclomatic 19) API/QuestLogsAPI.cs:193 — QuestLogsAPI.ApplyLayout has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CWRRef.ApplyEnchantmentToItem (cyclomatic 19) · ×1
  • CWRRef.ApplyEnchantmentToItem (cyclomatic 19) CWRRef.cs:1340 — CWRRef.ApplyEnchantmentToItem has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CWRProjectile.OnSpawn (cyclomatic 19) · ×1
  • CWRProjectile.OnSpawn (cyclomatic 19) Content/CWRProjectile.cs:48 — CWRProjectile.OnSpawn has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CyberwareNet.SendSurgeryRequest (cyclomatic 19) · ×1
  • CyberwareNet.SendSurgeryRequest (cyclomatic 19) Content/Cyberwares/CyberwareNet.cs:101 — CyberwareNet.SendSurgeryRequest has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CyberwareNet.ExecuteSurgery (cyclomatic 19) · ×1
  • CyberwareNet.ExecuteSurgery (cyclomatic 19) Content/Cyberwares/CyberwareNet.cs:531 — CyberwareNet.ExecuteSurgery has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · AstralveilSpearMarkProj.AI (cyclomatic 19) · ×1
  • AstralveilSpearMarkProj.AI (cyclomatic 19) Content/GameModes/BrutalMobs/Ambience/Astralveil/Projectiles/AstralveilSpearMarkProj.cs:71 — AstralveilSpearMarkProj.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BrinefumeAmbientRender.UpdateBySystem (cyclomatic 19) · ×1
  • BrinefumeAmbientRender.UpdateBySystem (cyclomatic 19) Content/GameModes/BrutalMobs/Ambience/Brinefume/BrinefumeAmbientRender.cs:48 — BrinefumeAmbientRender.UpdateBySystem has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BrinefumeBoilZoneProj.AI (cyclomatic 19) · ×1
  • BrinefumeBoilZoneProj.AI (cyclomatic 19) Content/GameModes/BrutalMobs/Ambience/Brinefume/Projectiles/BrinefumeBoilZoneProj.cs:64 — BrinefumeBoilZoneProj.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CindercragVentProj.AI (cyclomatic 19) · ×1
  • CindercragVentProj.AI (cyclomatic 19) Content/GameModes/BrutalMobs/Ambience/Cindercrag/Projectiles/CindercragVentProj.cs:114 — CindercragVentProj.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DuneStormSandLashOmen.AI (cyclomatic 19) · ×1
  • DuneStormSandLashOmen.AI (cyclomatic 19) Content/GameModes/BrutalMobs/Ambience/DuneStorm/Projectiles/DuneStormSandLashOmen.cs:52 — DuneStormSandLashOmen.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FrostveilAmbience.UpdateAurora (cyclomatic 19) · ×1
  • FrostveilAmbience.UpdateAurora (cyclomatic 19) Content/GameModes/BrutalMobs/Ambience/Frostveil/FrostveilAmbience.cs:279 — FrostveilAmbience.UpdateAurora has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · HollowdeepPlayer.PostUpdate (cyclomatic 19) · ×1
  • HollowdeepPlayer.PostUpdate (cyclomatic 19) Content/GameModes/BrutalMobs/Ambience/Hollowdeep/HollowdeepPlayer.cs:52 — HollowdeepPlayer.PostUpdate has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · RimehollowIcicleProj.TriggerScan (cyclomatic 19) · ×1
  • RimehollowIcicleProj.TriggerScan (cyclomatic 19) Content/GameModes/BrutalMobs/Ambience/Rimehollow/Projectiles/RimehollowIcicleProj.cs:305 — RimehollowIcicleProj.TriggerScan has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · RotmireWritheProj.PreDraw (cyclomatic 19) · ×1
  • RotmireWritheProj.PreDraw (cyclomatic 19) Content/GameModes/BrutalMobs/Ambience/Rotmire/Projectiles/RotmireWritheProj.cs:237 — RotmireWritheProj.PreDraw has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SporeshineCapSwellProj.AI (cyclomatic 19) · ×1
  • SporeshineCapSwellProj.AI (cyclomatic 19) Content/GameModes/BrutalMobs/Ambience/Sporeshine/Projectiles/SporeshineCapSwellProj.cs:63 — SporeshineCapSwellProj.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FlgStabGlintOmen.AI (cyclomatic 19) · ×1
  • FlgStabGlintOmen.AI (cyclomatic 19) Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgStabGlintOmen.cs:62 — FlgStabGlintOmen.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FrmMiniBossNPC.RamActive (cyclomatic 19) · ×1
  • FrmMiniBossNPC.RamActive (cyclomatic 19) Content/GameModes/BrutalMobs/FrostMoon/FrmMiniBossNPC.cs:378 — FrmMiniBossNPC.RamActive has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · TempleDiveOmen.AI (cyclomatic 19) · ×1
  • TempleDiveOmen.AI (cyclomatic 19) Content/GameModes/BrutalMobs/Temple/Projectiles/TempleDiveOmen.cs:73 — TempleDiveOmen.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · GsChargeBowHeld.WatchTierCues (cyclomatic 19) · ×1
  • GsChargeBowHeld.WatchTierCues (cyclomatic 19) Content/GameModes/GodSmith/Weapons/Bows/GsChargeBowHeld.cs:240 — GsChargeBowHeld.WatchTierCues has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · GsThunderSpearHeld.OnHitTarget (cyclomatic 19) · ×1
  • GsThunderSpearHeld.OnHitTarget (cyclomatic 19) Content/GameModes/GodSmith/Weapons/Spears/GsThunderSpear.cs:67 — GsThunderSpearHeld.OnHitTarget has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · GsHornetStaff.UpdateDive (cyclomatic 19) · ×1
  • GsHornetStaff.UpdateDive (cyclomatic 19) Content/GameModes/GodSmith/Weapons/SummonMinions/Schemes/GsHornetStaff.cs:98 — GsHornetStaff.UpdateDive has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · HackEffectTracker.UpdateAuthorityList (cyclomatic 19) · ×1
  • HackEffectTracker.UpdateAuthorityList (cyclomatic 19) Content/HackTimes/HackEffectTracker.cs:368 — HackEffectTracker.UpdateAuthorityList has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · HackTimeNetSync.TryRequestQueue (cyclomatic 19) · ×1
  • HackTimeNetSync.TryRequestQueue (cyclomatic 19) Content/HackTimes/HackTimeNetSync.cs:373 — HackTimeNetSync.TryRequestQueue has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case 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: HackTimeNetSync.TryCreateEffectRecord (cyclomatic 21) 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.
D1 · Cyclomatic Complexity · StressInvert.TickCollisionDamage (cyclomatic 19) · ×1
  • StressInvert.TickCollisionDamage (cyclomatic 19) Content/HackTimes/Protocols/StressInvert.cs:151 — StressInvert.TickCollisionDamage has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · PlayerHackNet.HandleDefenderApply (cyclomatic 19) · ×1
  • PlayerHackNet.HandleDefenderApply (cyclomatic 19) Content/HackTimes/PvP/PlayerHackNet.cs:1005 — PlayerHackNet.HandleDefenderApply has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · AutoCrafterUI.DrawStatusRow (cyclomatic 19) · ×1
  • AutoCrafterUI.DrawStatusRow (cyclomatic 19) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:551 — AutoCrafterUI.DrawStatusRow has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FluidPourDraw.PreDrawEverything (cyclomatic 19) · ×1
  • FluidPourDraw.PreDrawEverything (cyclomatic 19) Content/Industrials/ElectricPowers/FluidInjectors/FluidInjectorTP.cs:314 — FluidPourDraw.PreDrawEverything has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MirrorheartRender.DrawBeforePlayers (cyclomatic 19) · ×1
  • MirrorheartRender.DrawBeforePlayers (cyclomatic 19) Content/Items/Accessories/BrutalRelics/BrainOfCthulhu/MirrorheartRender.cs:30 — MirrorheartRender.DrawBeforePlayers has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BloodfogVeilProj.SimulateElements (cyclomatic 19) · ×1
  • BloodfogVeilProj.SimulateElements (cyclomatic 19) Content/Items/Accessories/BrutalRelics/EyeOfCthulhu/BloodfogVeilProj.cs:534 — BloodfogVeilProj.SimulateElements has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SoulbindingGhostHand.AI (cyclomatic 19) · ×1
  • SoulbindingGhostHand.AI (cyclomatic 19) Content/Items/Accessories/BrutalRelics/Skeletron/SoulbindingGhostHand.cs:87 — SoulbindingGhostHand.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · GluttonousRetinaRender.EndEntityDraw (cyclomatic 19) · ×1
  • GluttonousRetinaRender.EndEntityDraw (cyclomatic 19) Content/Items/Accessories/BrutalRelics/WallOfFlesh/GluttonousRetinaRender.cs:42 — GluttonousRetinaRender.EndEntityDraw has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · JusticeUnveiledCross.AI (cyclomatic 19) · ×1
  • JusticeUnveiledCross.AI (cyclomatic 19) Content/Items/Accessories/JusticeUnveileds/JusticeUnveiledCross.cs:38 — JusticeUnveiledCross.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · JusticeUnveiledExplode.AI (cyclomatic 19) · ×1
  • JusticeUnveiledExplode.AI (cyclomatic 19) Content/Items/Accessories/JusticeUnveileds/JusticeUnveiledExplode.cs:41 — JusticeUnveiledExplode.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · PandemoniumFireball.AI (cyclomatic 19) · ×1
  • PandemoniumFireball.AI (cyclomatic 19) Content/Items/Magic/Pandemoniums/PandemoniumFireball.cs:35 — PandemoniumFireball.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · PandemoniumScythe.AI (cyclomatic 19) · ×1
  • PandemoniumScythe.AI (cyclomatic 19) Content/Items/Magic/Pandemoniums/PandemoniumScythe.cs:46 — PandemoniumScythe.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DivineSourceChargeBarLayer.Draw (cyclomatic 19) · ×1
  • DivineSourceChargeBarLayer.Draw (cyclomatic 19) Content/Items/Melee/DivineSourceBlades/DivineSourcePlayer.cs:158 — DivineSourceChargeBarLayer.Draw has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniMachetePlayer.PostUpdateMiscEffects (cyclomatic 19) · ×1
  • OniMachetePlayer.PostUpdateMiscEffects (cyclomatic 19) Content/Items/Melee/OniMachete.cs:217 — OniMachetePlayer.PostUpdateMiscEffects has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ShatterfangHeld.DrawBladeSet (cyclomatic 19) · ×1
  • ShatterfangHeld.DrawBladeSet (cyclomatic 19) Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:787 — ShatterfangHeld.DrawBladeSet has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CosmicEddies.AI (cyclomatic 19) · ×1
  • CosmicEddies.AI (cyclomatic 19) Content/Items/Ranged/AnnihilatingUniverses/CosmicEddies.cs:33 — CosmicEddies.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · HyperionCruiseMissile.OnKill (cyclomatic 19) · ×1
  • HyperionCruiseMissile.OnKill (cyclomatic 19) Content/Items/Ranged/HyperionBarrage.cs:552 — HyperionCruiseMissile.OnKill has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · UndertowSpine.AI (cyclomatic 19) · ×1
  • UndertowSpine.AI (cyclomatic 19) Content/Items/Ranged/Undertows/UndertowSpine.cs:56 — UndertowSpine.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MarbleHuntingKnifeHeld.AI (cyclomatic 19) · ×1
  • MarbleHuntingKnifeHeld.AI (cyclomatic 19) Content/Items/Stones/Marbles/MarbleHuntingKnife.cs:171 — MarbleHuntingKnifeHeld.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · HalibutRenderer.DrawCursorPanel (cyclomatic 19) · ×1
  • HalibutRenderer.DrawCursorPanel (cyclomatic 19) Content/LegendWeapon/HalibutLegend/UI/HalibutRenderer.cs:549 — HalibutRenderer.DrawCursorPanel has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaLakeHighlight.CaptureMask (cyclomatic 19) · ×1
  • KikasaLakeHighlight.CaptureMask (cyclomatic 19) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaLakeHighlight.cs:183 — KikasaLakeHighlight.CaptureMask has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaDreamPullRender.EndCaptureDraw (cyclomatic 19) · ×1
  • KikasaDreamPullRender.EndCaptureDraw (cyclomatic 19) Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs:23 — KikasaDreamPullRender.EndCaptureDraw has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaBowServant.AI (cyclomatic 19) · ×1
  • KikasaBowServant.AI (cyclomatic 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:230 — KikasaBowServant.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaBowServant.FireArrow (cyclomatic 19) · ×1
  • KikasaBowServant.FireArrow (cyclomatic 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:558 — KikasaBowServant.FireArrow has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaHalibutServant.AI (cyclomatic 19) · ×1
  • KikasaHalibutServant.AI (cyclomatic 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:257 — KikasaHalibutServant.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaHalibutServant.UpdateDomainCast (cyclomatic 19) · ×1
  • KikasaHalibutServant.UpdateDomainCast (cyclomatic 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:638 — KikasaHalibutServant.UpdateDomainCast has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaPandemoniumServant.AI (cyclomatic 19) · ×1
  • KikasaPandemoniumServant.AI (cyclomatic 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:185 — KikasaPandemoniumServant.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaSHPCServant.AI (cyclomatic 19) · ×1
  • KikasaSHPCServant.AI (cyclomatic 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:237 — KikasaSHPCServant.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaZenithServant.AI (cyclomatic 19) · ×1
  • KikasaZenithServant.AI (cyclomatic 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:267 — KikasaZenithServant.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaZenithServant.UpdateStorm (cyclomatic 19) · ×1
  • KikasaZenithServant.UpdateStorm (cyclomatic 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:538 — KikasaZenithServant.UpdateStorm has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaBrainServant.AI (cyclomatic 19) · ×1
  • KikasaBrainServant.AI (cyclomatic 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:275 — KikasaBrainServant.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaCultistServant.UpdateEmerge (cyclomatic 19) · ×1
  • KikasaCultistServant.UpdateEmerge (cyclomatic 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:291 — KikasaCultistServant.UpdateEmerge has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaDeerclopsServant.UpdateStomp (cyclomatic 19) · ×1
  • KikasaDeerclopsServant.UpdateStomp (cyclomatic 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:671 — KikasaDeerclopsServant.UpdateStomp has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaEaterServant.AI (cyclomatic 19) · ×1
  • KikasaEaterServant.AI (cyclomatic 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:282 — KikasaEaterServant.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaEmpressServant.DrawLayeredBody (cyclomatic 19) · ×1
  • KikasaEmpressServant.DrawLayeredBody (cyclomatic 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:927 — KikasaEmpressServant.DrawLayeredBody has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaPlanteraServant.SyncLatchesQuietly (cyclomatic 19) · ×1
  • KikasaPlanteraServant.SyncLatchesQuietly (cyclomatic 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:331 — KikasaPlanteraServant.SyncLatchesQuietly has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaPlanteraServant.UpdateHookPoses (cyclomatic 19) · ×1
  • KikasaPlanteraServant.UpdateHookPoses (cyclomatic 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1088 — KikasaPlanteraServant.UpdateHookPoses has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaQueenGelMine.PreDraw (cyclomatic 19) · ×1
  • KikasaQueenGelMine.PreDraw (cyclomatic 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenGelMine.cs:334 — KikasaQueenGelMine.PreDraw has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaQueenSlimeServant.DrawShaderPieces (cyclomatic 19) · ×1
  • KikasaQueenSlimeServant.DrawShaderPieces (cyclomatic 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:1399 — KikasaQueenSlimeServant.DrawShaderPieces has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaSeaShrimpServant.UpdatePunch (cyclomatic 19) · ×1
  • KikasaSeaShrimpServant.UpdatePunch (cyclomatic 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:481 — KikasaSeaShrimpServant.UpdatePunch has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaSeaShrimpServant.UpdateTailVolley (cyclomatic 19) · ×1
  • KikasaSeaShrimpServant.UpdateTailVolley (cyclomatic 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:568 — KikasaSeaShrimpServant.UpdateTailVolley has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaSkeletronServant.AI (cyclomatic 19) · ×1
  • KikasaSkeletronServant.AI (cyclomatic 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:259 — KikasaSkeletronServant.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaWallOfFleshServant.AI (cyclomatic 19) · ×1
  • KikasaWallOfFleshServant.AI (cyclomatic 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:216 — KikasaWallOfFleshServant.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FuLongFX.RunWash (cyclomatic 19) · ×1
  • FuLongFX.RunWash (cyclomatic 19) Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuLongFX.cs:49 — FuLongFX.RunWash has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaThrallProj.AI (cyclomatic 19) · ×1
  • KikasaThrallProj.AI (cyclomatic 19) Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallProj.cs:227 — KikasaThrallProj.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaPanoramaUI.ResolveHover (cyclomatic 19) · ×1
  • KikasaPanoramaUI.ResolveHover (cyclomatic 19) Content/LegendWeapon/KikasaLegend/UI/Panorama/KikasaPanoramaUI.cs:642 — KikasaPanoramaUI.ResolveHover has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniMeiDeedProgress.Load (cyclomatic 19) · ×1
  • OniMeiDeedProgress.Load (cyclomatic 19) Content/LegendWeapon/OnikiriLegend/Inscriptions/Deeds/OniMeiDeedProgress.cs:104 — OniMeiDeedProgress.Load has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniSeverStrike.UpdateAuthority (cyclomatic 19) · ×1
  • OniSeverStrike.UpdateAuthority (cyclomatic 19) Content/LegendWeapon/OnikiriLegend/OniDismembers/OniSeverStrike.cs:649 — OniSeverStrike.UpdateAuthority has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniDomainPlayer.UpdateFlipping (cyclomatic 19) · ×1
  • OniDomainPlayer.UpdateFlipping (cyclomatic 19) Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainPlayer.cs:546 — OniDomainPlayer.UpdateFlipping has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniOmokageRender.CapturePending (cyclomatic 19) · ×1
  • OniOmokageRender.CapturePending (cyclomatic 19) Content/LegendWeapon/OnikiriLegend/OniOmokages/OniOmokageRender.cs:61 — OniOmokageRender.CapturePending has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SakuraKiriPlayerProj.AI (cyclomatic 19) · ×1
  • SakuraKiriPlayerProj.AI (cyclomatic 19) Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraKiriPlayerProj.cs:390 — SakuraKiriPlayerProj.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CyberDomainFreeze.BroadcastApply (cyclomatic 19) · ×1
  • CyberDomainFreeze.BroadcastApply (cyclomatic 19) Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.Net.cs:229 — CyberDomainFreeze.BroadcastApply has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CyberDomainFreeze.WriteSnapshot (cyclomatic 19) · ×1
  • CyberDomainFreeze.WriteSnapshot (cyclomatic 19) Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.Net.cs:829 — CyberDomainFreeze.WriteSnapshot has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CyberDomainFreeze.ReadSnapshot (cyclomatic 19) · ×1
  • CyberDomainFreeze.ReadSnapshot (cyclomatic 19) Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.Net.cs:882 — CyberDomainFreeze.ReadSnapshot has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SHPCRedlineGaugeProj.DrawPrimitives (cyclomatic 19) · ×1
  • SHPCRedlineGaugeProj.DrawPrimitives (cyclomatic 19) Content/LegendWeapon/SHPCLegend/Modules/Barrel/RapidBarrelModule.cs:555 — SHPCRedlineGaugeProj.DrawPrimitives has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MoldCodexPanel.DrawCell (cyclomatic 19) · ×1
  • MoldCodexPanel.DrawCell (cyclomatic 19) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:217 — MoldCodexPanel.DrawCell has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SHPCModPanel.DrawEquippedTooltip (cyclomatic 19) · ×1
  • SHPCModPanel.DrawEquippedTooltip (cyclomatic 19) Content/LegendWeapon/SHPCLegend/UI/SHPCModPanel.cs:372 — SHPCModPanel.DrawEquippedTooltip has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SHPCModuleSelectPanel.Draw (cyclomatic 19) · ×1
  • SHPCModuleSelectPanel.Draw (cyclomatic 19) Content/LegendWeapon/SHPCLegend/UI/SHPCModuleSelectPanel.cs:145 — SHPCModuleSelectPanel.Draw has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BssDustDevilProj.AI (cyclomatic 19) · ×1
  • BssDustDevilProj.AI (cyclomatic 19) Content/NPCs/BloomsandSerpents/Projectiles/BssDustDevilProj.cs:60 — BssDustDevilProj.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BssNeedleRippleState.OnUpdate (cyclomatic 19) · ×1
  • BssNeedleRippleState.OnUpdate (cyclomatic 19) Content/NPCs/BloomsandSerpents/States/BssNeedleRippleState.cs:46 — BssNeedleRippleState.OnUpdate has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BrainHoverState.OnUpdate (cyclomatic 19) · ×1
  • BrainHoverState.OnUpdate (cyclomatic 19) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainHoverState.cs:38 — BrainHoverState.OnUpdate has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BrainMindSeizeState.OnUpdate (cyclomatic 19) · ×1
  • BrainMindSeizeState.OnUpdate (cyclomatic 19) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainMindSeizeState.cs:166 — BrainMindSeizeState.OnUpdate has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BrainMindSeizeState.UpdateComboPresentation (cyclomatic 19) · ×1
  • BrainMindSeizeState.UpdateComboPresentation (cyclomatic 19) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainMindSeizeState.cs:408 — BrainMindSeizeState.UpdateComboPresentation has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BrainMirrorMazeState.OnUpdate (cyclomatic 19) · ×1
  • BrainMirrorMazeState.OnUpdate (cyclomatic 19) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainMirrorMazeState.cs:67 — BrainMirrorMazeState.OnUpdate has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DestroyerBurrowAmbushState.UpdateErupt (cyclomatic 19) · ×1
  • DestroyerBurrowAmbushState.UpdateErupt (cyclomatic 19) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:221 — DestroyerBurrowAmbushState.UpdateErupt has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FishronTidalDashCooldownState.OnUpdate (cyclomatic 19) · ×1
  • FishronTidalDashCooldownState.OnUpdate (cyclomatic 19) Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronTidalDashState.cs:229 — FishronTidalDashCooldownState.OnUpdate has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EowBodyAI.AI (cyclomatic 19) · ×1
  • EowBodyAI.AI (cyclomatic 19) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/EowBodyAI.cs:97 — EowBodyAI.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EowDevourState.OnUpdate (cyclomatic 19) · ×1
  • EowDevourState.OnUpdate (cyclomatic 19) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowDevourState.cs:143 — EowDevourState.OnUpdate has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EmpressTrackBeam.AI (cyclomatic 19) · ×1
  • EmpressTrackBeam.AI (cyclomatic 19) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Projectiles/EmpressTrackBeam.cs:87 — EmpressTrackBeam.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EmpressTrackBeam.MarkerUpdate (cyclomatic 19) · ×1
  • EmpressTrackBeam.MarkerUpdate (cyclomatic 19) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Projectiles/EmpressTrackBeam.cs:140 — EmpressTrackBeam.MarkerUpdate has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EmpressAscensionState.OnUpdate (cyclomatic 19) · ×1
  • EmpressAscensionState.OnUpdate (cyclomatic 19) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/States/EmpressAscensionState.cs:51 — EmpressAscensionState.OnUpdate has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · GolemDeathState.UpdateCollapse (cyclomatic 19) · ×1
  • GolemDeathState.UpdateCollapse (cyclomatic 19) Content/NPCs/BrutalNPCs/BrutalGolem/States/GolemDeathState.cs:290 — GolemDeathState.UpdateCollapse has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · GolemHookSwingState.OnUpdate (cyclomatic 19) · ×1
  • GolemHookSwingState.OnUpdate (cyclomatic 19) Content/NPCs/BrutalNPCs/BrutalGolem/States/GolemHookSwingState.cs:26 — GolemHookSwingState.OnUpdate has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · GolemStompComboState.OnUpdate (cyclomatic 19) · ×1
  • GolemStompComboState.OnUpdate (cyclomatic 19) Content/NPCs/BrutalNPCs/BrutalGolem/States/GolemStompComboState.cs:34 — GolemStompComboState.OnUpdate has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CultistPlanetProj.EmitVolley (cyclomatic 19) · ×1
  • CultistPlanetProj.EmitVolley (cyclomatic 19) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistPlanetProj.cs:526 — CultistPlanetProj.EmitVolley has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · RetinazerDeathRay.AI (cyclomatic 19) · ×1
  • RetinazerDeathRay.AI (cyclomatic 19) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs:47 — RetinazerDeathRay.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · TwinsPincerGrabState.OnUpdate (cyclomatic 19) · ×1
  • TwinsPincerGrabState.OnUpdate (cyclomatic 19) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsPincerGrabState.cs:168 — TwinsPincerGrabState.OnUpdate has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MoonLordHeadAI.UpdateAlive (cyclomatic 19) · ×1
  • MoonLordHeadAI.UpdateAlive (cyclomatic 19) Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordHeadAI.cs:82 — MoonLordHeadAI.UpdateAlive has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MLordBlackHoleProj.UpdateCollapse (cyclomatic 19) · ×1
  • MLordBlackHoleProj.UpdateCollapse (cyclomatic 19) Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordBlackHoleProj.cs:324 — MLordBlackHoleProj.UpdateCollapse has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MLordCrescentCloseState.OnUpdate (cyclomatic 19) · ×1
  • MLordCrescentCloseState.OnUpdate (cyclomatic 19) Content/NPCs/BrutalNPCs/BrutalMoonLord/States/MLordCrescentCloseState.cs:148 — MLordCrescentCloseState.OnUpdate has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · PlanteraSporeSowState.OnUpdate (cyclomatic 19) · ×1
  • PlanteraSporeSowState.OnUpdate (cyclomatic 19) Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraSporeSowState.cs:29 — PlanteraSporeSowState.OnUpdate has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · QBSwarmArrowState.OnUpdate (cyclomatic 19) · ×1
  • QBSwarmArrowState.OnUpdate (cyclomatic 19) Content/NPCs/BrutalNPCs/BrutalQueenBee/States/QBSwarmArrowState.cs:35 — QBSwarmArrowState.OnUpdate has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · QueenCrystalPrisonWaltzState.UpdateSummon (cyclomatic 19) · ×1
  • QueenCrystalPrisonWaltzState.UpdateSummon (cyclomatic 19) Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenCrystalPrisonWaltzState.cs:220 — QueenCrystalPrisonWaltzState.UpdateSummon has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · QueenGelSplitSummonState.OnUpdate (cyclomatic 19) · ×1
  • QueenGelSplitSummonState.OnUpdate (cyclomatic 19) Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenGelSplitSummonState.cs:61 — QueenGelSplitSummonState.OnUpdate has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SkeletronPhaseTransitionState.UpdateBeats (cyclomatic 19) · ×1
  • SkeletronPhaseTransitionState.UpdateBeats (cyclomatic 19) Content/NPCs/BrutalNPCs/BrutalSkeletron/States/SkeletronPhaseTransitionState.cs:50 — SkeletronPhaseTransitionState.UpdateBeats has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · PrimeViceExecutionState.PlayBeatEffects (cyclomatic 19) · ×1
  • PrimeViceExecutionState.PlayBeatEffects (cyclomatic 19) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/PrimeViceExecutionState.cs:273 — PrimeViceExecutionState.PlayBeatEffects has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · NPCTalkUIBase.DrawTextBlock (cyclomatic 19) · ×1
  • NPCTalkUIBase.DrawTextBlock (cyclomatic 19) Content/NPCs/CommonUIs/NPCTalkUIBase.cs:240 — NPCTalkUIBase.DrawTextBlock has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FssIchorPool.AI (cyclomatic 19) · ×1
  • FssIchorPool.AI (cyclomatic 19) Content/NPCs/FestersandSerpents/Projectiles/FssIchorPool.cs:110 — FssIchorPool.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FssPortraitActor.DrawWorm (cyclomatic 19) · ×1
  • FssPortraitActor.DrawWorm (cyclomatic 19) Content/NPCs/FestersandSerpents/Rendering/FssPortrait.cs:135 — FssPortraitActor.DrawWorm has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FssCoilCascadeState.OnUpdate (cyclomatic 19) · ×1
  • FssCoilCascadeState.OnUpdate (cyclomatic 19) Content/NPCs/FestersandSerpents/States/FssCoilCascadeState.cs:55 — FssCoilCascadeState.OnUpdate has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FssFieldDetonateState.OnUpdate (cyclomatic 19) · ×1
  • FssFieldDetonateState.OnUpdate (cyclomatic 19) Content/NPCs/FestersandSerpents/States/FssFieldDetonateState.cs:60 — FssFieldDetonateState.OnUpdate has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CrabulonClusterRenderer.DrawWorldCluster (cyclomatic 19) · ×1
  • CrabulonClusterRenderer.DrawWorldCluster (cyclomatic 19) Content/NPCs/Modifys/Crabulons/CrabulonUIs/CrabulonCommandUI.cs:452 — CrabulonClusterRenderer.DrawWorldCluster has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ScrapSawCannonComboState.OnUpdate (cyclomatic 19) · ×1
  • ScrapSawCannonComboState.OnUpdate (cyclomatic 19) Content/NPCs/ScrapCommanders/States/ScrapSawCannonComboState.cs:36 — ScrapSawCannonComboState.OnUpdate has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SeaShrimpIntroState.OnUpdate (cyclomatic 19) · ×1
  • SeaShrimpIntroState.OnUpdate (cyclomatic 19) Content/NPCs/SeaShrimp/States/SeaShrimpIntroState.cs:44 — SeaShrimpIntroState.OnUpdate has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · QuestBookGuidePlayer.PerformStepForPlayer (cyclomatic 19) · ×1
  • QuestBookGuidePlayer.PerformStepForPlayer (cyclomatic 19) Content/QuestLogs/Guide/QuestBookGuidePlayer.cs:512 — QuestBookGuidePlayer.PerformStepForPlayer has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · QuestBookGuideTargets.Resolve (cyclomatic 19) · ×1
  • QuestBookGuideTargets.Resolve (cyclomatic 19) Content/QuestLogs/Guide/QuestBookGuideTargets.cs:13 — QuestBookGuideTargets.Resolve has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DraedonShopRenderer.DrawRecord (cyclomatic 19) · ×1
  • DraedonShopRenderer.DrawRecord (cyclomatic 19) Content/Scenarios/Draedon/PQCDs/DraedonShops/DraedonShopRenderer.cs:54 — DraedonShopRenderer.DrawRecord has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · L2EscapeTunnel.Plan (cyclomatic 19) · ×1
  • L2EscapeTunnel.Plan (cyclomatic 19) Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2EscapeTunnel.cs:111 — L2EscapeTunnel.Plan has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · Prefab.CollectSockets (cyclomatic 19) · ×1
  • Prefab.CollectSockets (cyclomatic 19) Content/Scenarios/Dungeonworld/Gen/Prefabs/Prefab.cs:84 — Prefab.CollectSockets has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DeepGaolWraith.AI (cyclomatic 19) · ×1
  • DeepGaolWraith.AI (cyclomatic 19) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:369 — DeepGaolWraith.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DeepGaolWraith.UpdateEmergeFromSkull (cyclomatic 19) · ×1
  • DeepGaolWraith.UpdateEmergeFromSkull (cyclomatic 19) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:640 — DeepGaolWraith.UpdateEmergeFromSkull has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · LanternWardenRender.DrawNPCsOverTiles (cyclomatic 19) · ×1
  • LanternWardenRender.DrawNPCsOverTiles (cyclomatic 19) Content/Scenarios/Dungeonworld/NPCs/Elites/LanternWardenRender.cs:33 — LanternWardenRender.DrawNPCsOverTiles has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · HadalTerrainPlanner.BuildCaveField (cyclomatic 19) · ×1
  • HadalTerrainPlanner.BuildCaveField (cyclomatic 19) Content/Scenarios/Hadalworld/Gen/Core/HadalTerrainPlan.cs:433 — HadalTerrainPlanner.BuildCaveField has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OldNetBlackICE.AI (cyclomatic 19) · ×1
  • OldNetBlackICE.AI (cyclomatic 19) Content/Scenarios/OldNet/NPCs/OldNetBlackICE.cs:78 — OldNetBlackICE.AI has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OldNetICEDirector.SeedLurkers (cyclomatic 19) · ×1
  • OldNetICEDirector.SeedLurkers (cyclomatic 19) Content/Scenarios/OldNet/NPCs/OldNetICEDirector.cs:572 — OldNetICEDirector.SeedLurkers has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OldNetDeco.Update (cyclomatic 19) · ×1
  • OldNetDeco.Update (cyclomatic 19) Content/Scenarios/OldNet/OldNetDeco.cs:18 — OldNetDeco.Update has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OldNetPlayer.PostUpdate (cyclomatic 19) · ×1
  • OldNetPlayer.PostUpdate (cyclomatic 19) Content/Scenarios/OldNet/OldNetPlayer.cs:557 — OldNetPlayer.PostUpdate has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EbnBarsDisplay.DrawLife (cyclomatic 19) · ×1
  • EbnBarsDisplay.DrawLife (cyclomatic 19) Content/Scenarios/SupCal/End/EternalBlazingNow/EbnBarsDisplay.cs:181 — EbnBarsDisplay.DrawLife has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SylvanOutpost.RepairFoundation (cyclomatic 19) · ×1
  • SylvanOutpost.RepairFoundation (cyclomatic 19) Content/Structures/DatIO/SylvanOutpost.cs:457 — SylvanOutpost.RepairFoundation has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · GhostHandAbility.Update (cyclomatic 19) · ×1
  • GhostHandAbility.Update (cyclomatic 19) Content/Wraiths/Abilities/GhostHandAbility.cs:100 — GhostHandAbility.Update has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · LanternBoyProj.PublishComboBeat (cyclomatic 19) · ×1
  • LanternBoyProj.PublishComboBeat (cyclomatic 19) Content/Wraiths/Projectiles/LanternBoyProj.cs:207 — LanternBoyProj.PublishComboBeat has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · WraithPlayer.UpdateAuthority (cyclomatic 19) · ×1
  • WraithPlayer.UpdateAuthority (cyclomatic 19) Content/Wraiths/Runtime/WraithPlayer.cs:385 — WraithPlayer.UpdateAuthority has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EntrustAPI.TryRegister (cyclomatic 18) · ×1
  • EntrustAPI.TryRegister (cyclomatic 18) API/EntrustAPI.cs:58 — EntrustAPI.TryRegister has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CWRID.Get (cyclomatic 18) · ×1
  • CWRID.Get (cyclomatic 18) CWRID.cs:465 — CWRID.Get has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CWRCrafted.AddResultContent (cyclomatic 18) · ×1
  • CWRCrafted.AddResultContent (cyclomatic 18) Content/CWRCrafted.cs:41 — CWRCrafted.AddResultContent has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CWRNpc.OnKill (cyclomatic 18) · ×1
  • CWRNpc.OnKill (cyclomatic 18) Content/CWRNpc.cs:124 — CWRNpc.OnKill has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CyberBodyRenderer.DrawPrimaryCurves (cyclomatic 18) · ×1
  • CyberBodyRenderer.DrawPrimaryCurves (cyclomatic 18) Content/Cyberwares/UIs/CyberBodyRenderer.cs:460 — CyberBodyRenderer.DrawPrimaryCurves has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CyberTooltipRenderer.DrawTooltip (cyclomatic 18) · ×1
  • CyberTooltipRenderer.DrawTooltip (cyclomatic 18) Content/Cyberwares/UIs/CyberTooltipRenderer.cs:20 — CyberTooltipRenderer.DrawTooltip has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · AshreignPlayer.LocalStormTick (cyclomatic 18) · ×1
  • AshreignPlayer.LocalStormTick (cyclomatic 18) Content/GameModes/BrutalMobs/Ambience/Ashreign/AshreignPlayer.cs:78 — AshreignPlayer.LocalStormTick has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CindercragGlowRender.EndEntityDraw (cyclomatic 18) · ×1
  • CindercragGlowRender.EndEntityDraw (cyclomatic 18) Content/GameModes/BrutalMobs/Ambience/Cindercrag/CindercragGlowRender.cs:267 — CindercragGlowRender.EndEntityDraw has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DuneStormRender.UpdateStreaks (cyclomatic 18) · ×1
  • DuneStormRender.UpdateStreaks (cyclomatic 18) Content/GameModes/BrutalMobs/Ambience/DuneStorm/DuneStormRender.cs:71 — DuneStormRender.UpdateStreaks has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · RimehollowRender.UpdateBySystem (cyclomatic 18) · ×1
  • RimehollowRender.UpdateBySystem (cyclomatic 18) Content/GameModes/BrutalMobs/Ambience/Rimehollow/RimehollowRender.cs:56 — RimehollowRender.UpdateBySystem has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SilkcryptWebPatchProj.AI (cyclomatic 18) · ×1
  • SilkcryptWebPatchProj.AI (cyclomatic 18) Content/GameModes/BrutalMobs/Ambience/Silkcrypt/Projectiles/SilkcryptWebPatchProj.cs:62 — SilkcryptWebPatchProj.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · StratosFallingStarProj.PreDraw (cyclomatic 18) · ×1
  • StratosFallingStarProj.PreDraw (cyclomatic 18) Content/GameModes/BrutalMobs/Ambience/Stratos/Projectiles/StratosFallingStarProj.cs:250 — StratosFallingStarProj.PreDraw has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · WoodsongAmbience.FindWispTarget (cyclomatic 18) · ×1
  • WoodsongAmbience.FindWispTarget (cyclomatic 18) Content/GameModes/BrutalMobs/Ambience/Woodsong/WoodsongAmbience.cs:645 — WoodsongAmbience.FindWispTarget has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case 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: WoodsongAmbience.LocalInPureForest (cyclomatic 27) 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.
D1 · Cyclomatic Complexity · DdChargeOmen.AI (cyclomatic 18) · ×1
  • DdChargeOmen.AI (cyclomatic 18) Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdChargeOmen.cs:150 — DdChargeOmen.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FrmAimLaneOmen.AI (cyclomatic 18) · ×1
  • FrmAimLaneOmen.AI (cyclomatic 18) Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmAimLaneOmen.cs:83 — FrmAimLaneOmen.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FrmFlockoBurstOmen.AI (cyclomatic 18) · ×1
  • FrmFlockoBurstOmen.AI (cyclomatic 18) Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmFlockoBurstOmen.cs:75 — FrmFlockoBurstOmen.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · GyRavenSwoopOmen.AI (cyclomatic 18) · ×1
  • GyRavenSwoopOmen.AI (cyclomatic 18) Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyRavenSwoopOmen.cs:77 — GyRavenSwoopOmen.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MeteoriteDiveOmen.AI (cyclomatic 18) · ×1
  • MeteoriteDiveOmen.AI (cyclomatic 18) Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteDiveOmen.cs:62 — MeteoriteDiveOmen.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OceanSharkOmen.AI (cyclomatic 18) · ×1
  • OceanSharkOmen.AI (cyclomatic 18) Content/GameModes/BrutalMobs/Ocean/Projectiles/OceanSharkOmen.cs:82 — OceanSharkOmen.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · PmkEmberProj.AI (cyclomatic 18) · ×1
  • PmkEmberProj.AI (cyclomatic 18) Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkEmberProj.cs:66 — PmkEmberProj.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · PumpkinMoonNPC.TryStartCharge (cyclomatic 18) · ×1
  • PumpkinMoonNPC.TryStartCharge (cyclomatic 18) Content/GameModes/BrutalMobs/PumpkinMoon/PumpkinMoonNPC.cs:654 — PumpkinMoonNPC.TryStartCharge has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SkyGaleDiveOmen.AI (cyclomatic 18) · ×1
  • SkyGaleDiveOmen.AI (cyclomatic 18) Content/GameModes/BrutalMobs/Sky/Projectiles/SkyGaleDiveOmen.cs:75 — SkyGaleDiveOmen.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SlimeGooPatch.AI (cyclomatic 18) · ×1
  • SlimeGooPatch.AI (cyclomatic 18) Content/GameModes/BrutalMobs/SlimeKin/Projectiles/SlimeGooPatch.cs:73 — SlimeGooPatch.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · GodSmithHelmetNestItem.PostDrawTooltip (cyclomatic 18) · ×1
  • GodSmithHelmetNestItem.PostDrawTooltip (cyclomatic 18) Content/GameModes/GodSmith/Framework/GodSmithHelmetNestItem.cs:193 — GodSmithHelmetNestItem.PostDrawTooltip has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · GsHarpoonSpearProj.AI (cyclomatic 18) · ×1
  • GsHarpoonSpearProj.AI (cyclomatic 18) Content/GameModes/GodSmith/Weapons/Guns/GsHarpoon.cs:165 — GsHarpoonSpearProj.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · GsNimbusCorridorProj.AI (cyclomatic 18) · ×1
  • GsNimbusCorridorProj.AI (cyclomatic 18) Content/GameModes/GodSmith/Weapons/MagicMorph/Projectiles/GsNimbusCorridorProj.cs:73 — GsNimbusCorridorProj.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · GsSpikyBall.GsThrowOnHit (cyclomatic 18) · ×1
  • GsSpikyBall.GsThrowOnHit (cyclomatic 18) Content/GameModes/GodSmith/Weapons/Throwing/ThrowingSchemes.BonesSpears.cs:183 — GsSpikyBall.GsThrowOnHit has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · HackQueueRenderer.DrawThread (cyclomatic 18) · ×1
  • HackQueueRenderer.DrawThread (cyclomatic 18) Content/HackTimes/HackQueueRenderer.cs:392 — HackQueueRenderer.DrawThread has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ProjectileTithe.UpdateVisualWatch (cyclomatic 18) · ×1
  • ProjectileTithe.UpdateVisualWatch (cyclomatic 18) Content/HackTimes/Protocols/ProjectileTithe.cs:256 — ProjectileTithe.UpdateVisualWatch has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FluidPumpTP.UpdateMachine (cyclomatic 18) · ×1
  • FluidPumpTP.UpdateMachine (cyclomatic 18) Content/Industrials/ElectricPowers/FluidPumps/FluidPumpTP.cs:58 — FluidPumpTP.UpdateMachine has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MushroomFarmerTP.ScanWorkArea (cyclomatic 18) · ×1
  • MushroomFarmerTP.ScanWorkArea (cyclomatic 18) Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:189 — MushroomFarmerTP.ScanWorkArea has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MushroomFarmerTP.TryPlant (cyclomatic 18) · ×1
  • MushroomFarmerTP.TryPlant (cyclomatic 18) Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:332 — MushroomFarmerTP.TryPlant has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MushroomFarmerTP.VisualScanField (cyclomatic 18) · ×1
  • MushroomFarmerTP.VisualScanField (cyclomatic 18) Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:683 — MushroomFarmerTP.VisualScanField has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SensorTP.UpdateEyeEnvelope (cyclomatic 18) · ×1
  • SensorTP.UpdateEyeEnvelope (cyclomatic 18) Content/Industrials/ElectricPowers/Sensors/SensorTP.cs:292 — SensorTP.UpdateEyeEnvelope has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SensorUI.DrawParamColumn (cyclomatic 18) · ×1
  • SensorUI.DrawParamColumn (cyclomatic 18) Content/Industrials/ElectricPowers/Sensors/SensorUI.cs:322 — SensorUI.DrawParamColumn has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ThermalGeneratorTP.GeneratorUpdate (cyclomatic 18) · ×1
  • ThermalGeneratorTP.GeneratorUpdate (cyclomatic 18) Content/Industrials/Generator/Thermal/ThermalGenerator.cs:206 — ThermalGeneratorTP.GeneratorUpdate has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ItemPipelineNetwork.Rebuild (cyclomatic 18) · ×1
  • ItemPipelineNetwork.Rebuild (cyclomatic 18) Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineNetwork.cs:93 — ItemPipelineNetwork.Rebuild has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MirrorheartPlayer.TickTimers (cyclomatic 18) · ×1
  • MirrorheartPlayer.TickTimers (cyclomatic 18) Content/Items/Accessories/BrutalRelics/BrainOfCthulhu/MirrorheartParadox.cs:120 — MirrorheartPlayer.TickTimers has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MirrorheartPlayer.FirePendingEchoes (cyclomatic 18) · ×1
  • MirrorheartPlayer.FirePendingEchoes (cyclomatic 18) Content/Items/Accessories/BrutalRelics/BrainOfCthulhu/MirrorheartParadox.cs:282 — MirrorheartPlayer.FirePendingEchoes has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · WingsOfInterferencePlayer.TryRegisterTrail (cyclomatic 18) · ×1
  • WingsOfInterferencePlayer.TryRegisterTrail (cyclomatic 18) Content/Items/Accessories/BrutalRelics/EmpressOfLight/WingsOfInterference.cs:458 — WingsOfInterferencePlayer.TryRegisterTrail has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BloodfogIrisPlayer.TryStartDash (cyclomatic 18) · ×1
  • BloodfogIrisPlayer.TryStartDash (cyclomatic 18) Content/Items/Accessories/BrutalRelics/EyeOfCthulhu/BloodfogIris.cs:207 — BloodfogIrisPlayer.TryStartDash has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · RiteStarCore.AI (cyclomatic 18) · ×1
  • RiteStarCore.AI (cyclomatic 18) Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteStarSurge.cs:58 — RiteStarCore.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BlackFlashSigilPlayer.PreUpdateMovement (cyclomatic 18) · ×1
  • BlackFlashSigilPlayer.PreUpdateMovement (cyclomatic 18) Content/Items/Accessories/BrutalRelics/MoonLord/BlackFlashSigil.cs:149 — BlackFlashSigilPlayer.PreUpdateMovement has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SwarmVortexProj.UpdateSoundAndParticles (cyclomatic 18) · ×1
  • SwarmVortexProj.UpdateSoundAndParticles (cyclomatic 18) Content/Items/Accessories/BrutalRelics/QueenBee/SwarmVortexProj.cs:226 — SwarmVortexProj.UpdateSoundAndParticles has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · AccretionDisk.EmitParticles (cyclomatic 18) · ×1
  • AccretionDisk.EmitParticles (cyclomatic 18) Content/Items/Magic/AriaofTheCosmoses/AccretionDisk.cs:260 — AccretionDisk.EmitParticles has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DestroyersBladeHeldBase.AI (cyclomatic 18) · ×1
  • DestroyersBladeHeldBase.AI (cyclomatic 18) Content/Items/Melee/DestroyersBlade.cs:199 — DestroyersBladeHeldBase.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DivineSourceBoltProjectile.AI (cyclomatic 18) · ×1
  • DivineSourceBoltProjectile.AI (cyclomatic 18) Content/Items/Melee/DivineSourceBlades/DivineSourceBoltProjectile.cs:62 — DivineSourceBoltProjectile.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · HeartcarverHeld.AI (cyclomatic 18) · ×1
  • HeartcarverHeld.AI (cyclomatic 18) Content/Items/Melee/Heartcarver.cs:212 — HeartcarverHeld.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniHandMinion.WindupBehavior (cyclomatic 18) · ×1
  • OniHandMinion.WindupBehavior (cyclomatic 18) Content/Items/Melee/OniMacheteHands.cs:472 — OniHandMinion.WindupBehavior has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · PallbearerCoffinSeal.AI (cyclomatic 18) · ×1
  • PallbearerCoffinSeal.AI (cyclomatic 18) Content/Items/Ranged/Pallbearer.cs:1077 — PallbearerCoffinSeal.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ThornstringHeld.UpdateRightCharge (cyclomatic 18) · ×1
  • ThornstringHeld.UpdateRightCharge (cyclomatic 18) Content/Items/Ranged/Thornstrings/ThornstringHeld.cs:115 — ThornstringHeld.UpdateRightCharge has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · UndertowHeld.UpdateRightCharge (cyclomatic 18) · ×1
  • UndertowHeld.UpdateRightCharge (cyclomatic 18) Content/Items/Ranged/Undertows/UndertowHeld.cs:118 — UndertowHeld.UpdateRightCharge has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CrimsonTigerFishMinion.AI (cyclomatic 18) · ×1
  • CrimsonTigerFishMinion.AI (cyclomatic 18) Content/LegendWeapon/HalibutLegend/FishSkills/FishCrimsonTiger.cs:212 — CrimsonTigerFishMinion.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DynamiteExplosionEffect.SpawnTimedSmoke (cyclomatic 18) · ×1
  • DynamiteExplosionEffect.SpawnTimedSmoke (cyclomatic 18) Content/LegendWeapon/HalibutLegend/FishSkills/FishDynamite.cs:553 — DynamiteExplosionEffect.SpawnTimedSmoke has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · HungryCompanionProjectile.PreDraw (cyclomatic 18) · ×1
  • HungryCompanionProjectile.PreDraw (cyclomatic 18) Content/LegendWeapon/HalibutLegend/FishSkills/FishHunger.cs:540 — HungryCompanionProjectile.PreDraw has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MudfishSentry.AI (cyclomatic 18) · ×1
  • MudfishSentry.AI (cyclomatic 18) Content/LegendWeapon/HalibutLegend/FishSkills/FishMud.cs:157 — MudfishSentry.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SparklingFishHolder.AI (cyclomatic 18) · ×1
  • SparklingFishHolder.AI (cyclomatic 18) Content/LegendWeapon/HalibutLegend/FishSkills/FishSparkling.cs:265 — SparklingFishHolder.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · TunabeardDashProj.AI (cyclomatic 18) · ×1
  • TunabeardDashProj.AI (cyclomatic 18) Content/LegendWeapon/HalibutLegend/FishSkills/FishTunabeard.cs:122 — TunabeardDashProj.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · WaterZombie.LockChargeAI (cyclomatic 18) · ×1
  • WaterZombie.LockChargeAI (cyclomatic 18) Content/LegendWeapon/HalibutLegend/FishSkills/FishZombie.cs:384 — WaterZombie.LockChargeAI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CthulhuEye.AI (cyclomatic 18) · ×1
  • CthulhuEye.AI (cyclomatic 18) Content/LegendWeapon/HalibutLegend/FishSkills/FishofCthulu.cs:174 — CthulhuEye.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · AtlasSkillSea.DrawDetailCard (cyclomatic 18) · ×1
  • AtlasSkillSea.DrawDetailCard (cyclomatic 18) Content/LegendWeapon/HalibutLegend/UI/Atlas/AtlasSkillSea.cs:927 — AtlasSkillSea.DrawDetailCard has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaDomainFlipRender.EndCaptureDraw (cyclomatic 18) · ×1
  • KikasaDomainFlipRender.EndCaptureDraw (cyclomatic 18) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:21 — KikasaDomainFlipRender.EndCaptureDraw has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaHoundReflection.Draw (cyclomatic 18) · ×1
  • KikasaHoundReflection.Draw (cyclomatic 18) Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaHoundReflection.cs:57 — KikasaHoundReflection.Draw has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaMinionDrown.IsGrabbable (cyclomatic 18) · ×1
  • KikasaMinionDrown.IsGrabbable (cyclomatic 18) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaMinionDrown.cs:247 — KikasaMinionDrown.IsGrabbable has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaBladeServant.AI (cyclomatic 18) · ×1
  • KikasaBladeServant.AI (cyclomatic 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:254 — KikasaBladeServant.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaBladeServant.UpdateCross (cyclomatic 18) · ×1
  • KikasaBladeServant.UpdateCross (cyclomatic 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:609 — KikasaBladeServant.UpdateCross has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaGunServant.FireGun (cyclomatic 18) · ×1
  • KikasaGunServant.FireGun (cyclomatic 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:617 — KikasaGunServant.FireGun has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaGunServant.UpdateBlastWall (cyclomatic 18) · ×1
  • KikasaGunServant.UpdateBlastWall (cyclomatic 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:825 — KikasaGunServant.UpdateBlastWall has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaHalibutServant.UpdateEmerge (cyclomatic 18) · ×1
  • KikasaHalibutServant.UpdateEmerge (cyclomatic 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:338 — KikasaHalibutServant.UpdateEmerge has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaPandemoniumServant.UpdateCircleCast (cyclomatic 18) · ×1
  • KikasaPandemoniumServant.UpdateCircleCast (cyclomatic 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:562 — KikasaPandemoniumServant.UpdateCircleCast has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaSHPCServant.UpdateEmerge (cyclomatic 18) · ×1
  • KikasaSHPCServant.UpdateEmerge (cyclomatic 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:305 — KikasaSHPCServant.UpdateEmerge has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaSHPCServant.UpdateSunCast (cyclomatic 18) · ×1
  • KikasaSHPCServant.UpdateSunCast (cyclomatic 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:613 — KikasaSHPCServant.UpdateSunCast has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaThrowServant.AI (cyclomatic 18) · ×1
  • KikasaThrowServant.AI (cyclomatic 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:221 — KikasaThrowServant.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaCultistRuneCircle.AI (cyclomatic 18) · ×1
  • KikasaCultistRuneCircle.AI (cyclomatic 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistRuneCircle.cs:93 — KikasaCultistRuneCircle.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaDeerclopsServant.AI (cyclomatic 18) · ×1
  • KikasaDeerclopsServant.AI (cyclomatic 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:243 — KikasaDeerclopsServant.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaEaterCorrosiveSpit.AI (cyclomatic 18) · ×1
  • KikasaEaterCorrosiveSpit.AI (cyclomatic 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:64 — KikasaEaterCorrosiveSpit.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaEaterCorrosionMist.AI (cyclomatic 18) · ×1
  • KikasaEaterCorrosionMist.AI (cyclomatic 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:296 — KikasaEaterCorrosionMist.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaEaterServant.UpdateEmerge (cyclomatic 18) · ×1
  • KikasaEaterServant.UpdateEmerge (cyclomatic 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:366 — KikasaEaterServant.UpdateEmerge has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaFesterGlob.AI (cyclomatic 18) · ×1
  • KikasaFesterGlob.AI (cyclomatic 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterGlob.cs:60 — KikasaFesterGlob.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaFishronServant.UpdateNado (cyclomatic 18) · ×1
  • KikasaFishronServant.UpdateNado (cyclomatic 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:629 — KikasaFishronServant.UpdateNado has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaFishronServant.GetDrawPose (cyclomatic 18) · ×1
  • KikasaFishronServant.GetDrawPose (cyclomatic 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1134 — KikasaFishronServant.GetDrawPose has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaKingSlimeServant.UpdateWaveSlam (cyclomatic 18) · ×1
  • KikasaKingSlimeServant.UpdateWaveSlam (cyclomatic 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:784 — KikasaKingSlimeServant.UpdateWaveSlam has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaMoonRay.UpdateLakeBoil (cyclomatic 18) · ×1
  • KikasaMoonRay.UpdateLakeBoil (cyclomatic 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs:184 — KikasaMoonRay.UpdateLakeBoil has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaQueenBeeServant.DrawGlow (cyclomatic 18) · ×1
  • KikasaQueenBeeServant.DrawGlow (cyclomatic 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1290 — KikasaQueenBeeServant.DrawGlow has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaQueenCrystalShard.AI (cyclomatic 18) · ×1
  • KikasaQueenCrystalShard.AI (cyclomatic 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenCrystalShard.cs:57 — KikasaQueenCrystalShard.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaTwinsServant.AI (cyclomatic 18) · ×1
  • KikasaTwinsServant.AI (cyclomatic 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:267 — KikasaTwinsServant.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaWallOfFleshServant.UpdateDissolve (cyclomatic 18) · ×1
  • KikasaWallOfFleshServant.UpdateDissolve (cyclomatic 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:654 — KikasaWallOfFleshServant.UpdateDissolve has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaWallOfFleshServant.DrawGlowAccents (cyclomatic 18) · ×1
  • KikasaWallOfFleshServant.DrawGlowAccents (cyclomatic 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:1092 — KikasaWallOfFleshServant.DrawGlowAccents has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaThrallProj.UpdateReform (cyclomatic 18) · ×1
  • KikasaThrallProj.UpdateReform (cyclomatic 18) Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallProj.cs:401 — KikasaThrallProj.UpdateReform has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KikasaHudLead.ResolveSubText (cyclomatic 18) · ×1
  • KikasaHudLead.ResolveSubText (cyclomatic 18) Content/LegendWeapon/KikasaLegend/UI/KikasaHudLead.cs:720 — KikasaHudLead.ResolveSubText has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CrimsonRendSlash.OnHitNPC (cyclomatic 18) · ×1
  • CrimsonRendSlash.OnHitNPC (cyclomatic 18) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1497 — CrimsonRendSlash.OnHitNPC has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniMeiGroundBurn.TrySpawnOrRefreshAtGround (cyclomatic 18) · ×1
  • OniMeiGroundBurn.TrySpawnOrRefreshAtGround (cyclomatic 18) Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiGroundBurn.cs:163 — OniMeiGroundBurn.TrySpawnOrRefreshAtGround has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniDismemberRender.DrawNPCsOverTiles (cyclomatic 18) · ×1
  • OniDismemberRender.DrawNPCsOverTiles (cyclomatic 18) Content/LegendWeapon/OnikiriLegend/OniDismembers/OniDismemberRender.cs:30 — OniDismemberRender.DrawNPCsOverTiles has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniDomainPlayer.ReadNetworkState (cyclomatic 18) · ×1
  • OniDomainPlayer.ReadNetworkState (cyclomatic 18) Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainPlayer.cs:138 — OniDomainPlayer.ReadNetworkState has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniDomainPlayer.UpdateLocal (cyclomatic 18) · ×1
  • OniDomainPlayer.UpdateLocal (cyclomatic 18) Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainPlayer.cs:375 — OniDomainPlayer.UpdateLocal has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniOmokage.Imprint (cyclomatic 18) · ×1
  • OniOmokage.Imprint (cyclomatic 18) Content/LegendWeapon/OnikiriLegend/OniOmokages/OniOmokage.cs:208 — OniOmokage.Imprint has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniSlash.OnHitNPC (cyclomatic 18) · ×1
  • OniSlash.OnHitNPC (cyclomatic 18) Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1406 — OniSlash.OnHitNPC has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OnikiriPlayer.TryClickDismember (cyclomatic 18) · ×1
  • OnikiriPlayer.TryClickDismember (cyclomatic 18) Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs:1767 — OnikiriPlayer.TryClickDismember has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SakuraFinaleAssets.DrawReadyStar (cyclomatic 18) · ×1
  • SakuraFinaleAssets.DrawReadyStar (cyclomatic 18) Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraFinaleAssets.cs:98 — SakuraFinaleAssets.DrawReadyStar has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OnikiriTutorialPlayer.HandlePrimaryAction (cyclomatic 18) · ×1
  • OnikiriTutorialPlayer.HandlePrimaryAction (cyclomatic 18) Content/LegendWeapon/OnikiriLegend/Tutorial/OnikiriTutorialPlayer.cs:200 — OnikiriTutorialPlayer.HandlePrimaryAction has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OnikiriTutorialPlayer.PerformAssistedAction (cyclomatic 18) · ×1
  • OnikiriTutorialPlayer.PerformAssistedAction (cyclomatic 18) Content/LegendWeapon/OnikiriLegend/Tutorial/OnikiriTutorialPlayer.cs:934 — OnikiriTutorialPlayer.PerformAssistedAction has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniSigilUI.Draw (cyclomatic 18) · ×1
  • OniSigilUI.Draw (cyclomatic 18) Content/LegendWeapon/OnikiriLegend/UI/OniSigilUI.cs:726 — OniSigilUI.Draw has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · HarmonicFrameModule.OnBeamAI (cyclomatic 18) · ×1
  • HarmonicFrameModule.OnBeamAI (cyclomatic 18) Content/LegendWeapon/SHPCLegend/Modules/Frame/HarmonicFrameModule.cs:34 — HarmonicFrameModule.OnBeamAI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SHPCQuantumLinkProj.DrawAdditiveAfterNon (cyclomatic 18) · ×1
  • SHPCQuantumLinkProj.DrawAdditiveAfterNon (cyclomatic 18) Content/LegendWeapon/SHPCLegend/Modules/Frame/QuantumFrameModule.cs:320 — SHPCQuantumLinkProj.DrawAdditiveAfterNon has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SHPCThermalHeatNPC.PreAI (cyclomatic 18) · ×1
  • SHPCThermalHeatNPC.PreAI (cyclomatic 18) Content/LegendWeapon/SHPCLegend/Modules/Optic/ThermalOpticModule.cs:273 — SHPCThermalHeatNPC.PreAI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · HimayoPetalField.Tick (cyclomatic 18) · ×1
  • HimayoPetalField.Tick (cyclomatic 18) Content/MainMenus/Himayo/HimayoPetalField.cs:105 — HimayoPetalField.Tick has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BssFinHuntState.UpdateBite (cyclomatic 18) · ×1
  • BssFinHuntState.UpdateBite (cyclomatic 18) Content/NPCs/BloomsandSerpents/States/BssFinHuntState.cs:205 — BssFinHuntState.UpdateBite has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DeerclopsAI.FindFrame (cyclomatic 18) · ×1
  • DeerclopsAI.FindFrame (cyclomatic 18) Content/NPCs/BrutalNPCs/BrutalDeerclops/DeerclopsAI.cs:337 — DeerclopsAI.FindFrame has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DukeFishronAI.Draw (cyclomatic 18) · ×1
  • DukeFishronAI.Draw (cyclomatic 18) Content/NPCs/BrutalNPCs/BrutalDukeFishron/DukeFishronAI.cs:377 — DukeFishronAI.Draw has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FishronRingSpinState.OnUpdate (cyclomatic 18) · ×1
  • FishronRingSpinState.OnUpdate (cyclomatic 18) Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronRingSpinState.cs:40 — FishronRingSpinState.OnUpdate has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EowSplitPincerState.UpdateFinale (cyclomatic 18) · ×1
  • EowSplitPincerState.UpdateFinale (cyclomatic 18) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowSplitPincerState.cs:426 — EowSplitPincerState.UpdateFinale has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · GolemTrapScoreState.OnUpdate (cyclomatic 18) · ×1
  • GolemTrapScoreState.OnUpdate (cyclomatic 18) Content/NPCs/BrutalNPCs/BrutalGolem/States/GolemTrapScoreState.cs:26 — GolemTrapScoreState.OnUpdate has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · GolemWallSlamState.OnUpdate (cyclomatic 18) · ×1
  • GolemWallSlamState.OnUpdate (cyclomatic 18) Content/NPCs/BrutalNPCs/BrutalGolem/States/GolemWallSlamState.cs:61 — GolemWallSlamState.OnUpdate has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KingSlimeHopState.OnUpdate (cyclomatic 18) · ×1
  • KingSlimeHopState.OnUpdate (cyclomatic 18) Content/NPCs/BrutalNPCs/BrutalKingSlime/States/KingSlimeHopState.cs:41 — KingSlimeHopState.OnUpdate has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CultistGazeBeam.AI (cyclomatic 18) · ×1
  • CultistGazeBeam.AI (cyclomatic 18) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistGazeBeam.cs:105 — CultistGazeBeam.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CultistZodiacSealState.OnUpdate (cyclomatic 18) · ×1
  • CultistZodiacSealState.OnUpdate (cyclomatic 18) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistZodiacSealState.cs:35 — CultistZodiacSealState.OnUpdate has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · RetinazerSoloRageState.ExecuteCrossBeams (cyclomatic 18) · ×1
  • RetinazerSoloRageState.ExecuteCrossBeams (cyclomatic 18) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerSoloRageState.cs:233 — RetinazerSoloRageState.ExecuteCrossBeams has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MLordEyeLinkProj.AI (cyclomatic 18) · ×1
  • MLordEyeLinkProj.AI (cyclomatic 18) Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordEyeLinkProj.cs:49 — MLordEyeLinkProj.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MLordMoonBiteState.RunClapServer (cyclomatic 18) · ×1
  • MLordMoonBiteState.RunClapServer (cyclomatic 18) Content/NPCs/BrutalNPCs/BrutalMoonLord/States/MLordMoonBiteState.cs:136 — MLordMoonBiteState.RunClapServer has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · PlanteraBloomNovaState.UpdateBloom (cyclomatic 18) · ×1
  • PlanteraBloomNovaState.UpdateBloom (cyclomatic 18) Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraBloomNovaState.cs:152 — PlanteraBloomNovaState.UpdateBloom has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · PlanteraSeedGatlingState.OnUpdate (cyclomatic 18) · ×1
  • PlanteraSeedGatlingState.OnUpdate (cyclomatic 18) Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraSeedGatlingState.cs:66 — PlanteraSeedGatlingState.OnUpdate has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · PlanteraVineFeastState.UpdateChew (cyclomatic 18) · ×1
  • PlanteraVineFeastState.UpdateChew (cyclomatic 18) Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraVineFeastState.cs:388 — PlanteraVineFeastState.UpdateChew has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BrutalQueenBeeAI.UpdateMarkVisuals (cyclomatic 18) · ×1
  • BrutalQueenBeeAI.UpdateMarkVisuals (cyclomatic 18) Content/NPCs/BrutalNPCs/BrutalQueenBee/BrutalQueenBeeAI.cs:378 — BrutalQueenBeeAI.UpdateMarkVisuals has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · QueenSpikeRingState.OnUpdate (cyclomatic 18) · ×1
  • QueenSpikeRingState.OnUpdate (cyclomatic 18) Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenSpikeRingState.cs:50 — QueenSpikeRingState.OnUpdate has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · WofRotBeamProj.AI (cyclomatic 18) · ×1
  • WofRotBeamProj.AI (cyclomatic 18) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofRotBeamProj.cs:50 — WofRotBeamProj.AI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · WofTongueGrabState.UpdateChew (cyclomatic 18) · ×1
  • WofTongueGrabState.UpdateChew (cyclomatic 18) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/States/WofTongueGrabState.cs:309 — WofTongueGrabState.UpdateChew has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · WallOfFleshAI.EvaluateGlobalTransitions (cyclomatic 18) · ×1
  • WallOfFleshAI.EvaluateGlobalTransitions (cyclomatic 18) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/WallOfFleshAI.cs:235 — WallOfFleshAI.EvaluateGlobalTransitions has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FssLegRig.Update (cyclomatic 18) · ×1
  • FssLegRig.Update (cyclomatic 18) Content/NPCs/FestersandSerpents/FssLegRig.cs:116 — FssLegRig.Update has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FssHubState.UpdateHarass (cyclomatic 18) · ×1
  • FssHubState.UpdateHarass (cyclomatic 18) Content/NPCs/FestersandSerpents/States/FssHubState.cs:77 — FssHubState.UpdateHarass has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SeaShrimpSparkBubble.OnBurst (cyclomatic 18) · ×1
  • SeaShrimpSparkBubble.OnBurst (cyclomatic 18) Content/NPCs/SeaShrimp/Projectiles/SeaShrimpSparkBubble.cs:163 — SeaShrimpSparkBubble.OnBurst has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SeaShrimpRenderer.DrawAfterimages (cyclomatic 18) · ×1
  • SeaShrimpRenderer.DrawAfterimages (cyclomatic 18) Content/NPCs/SeaShrimp/Rendering/SeaShrimpRenderer.cs:251 — SeaShrimpRenderer.DrawAfterimages has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SeaShrimpBoss.RegisterSharedLoot (cyclomatic 18) · ×1
  • SeaShrimpBoss.RegisterSharedLoot (cyclomatic 18) Content/NPCs/SeaShrimp/SeaShrimpBoss.cs:104 — SeaShrimpBoss.RegisterSharedLoot has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SeaShrimpCavitationPunchState.OnUpdate (cyclomatic 18) · ×1
  • SeaShrimpCavitationPunchState.OnUpdate (cyclomatic 18) Content/NPCs/SeaShrimp/States/SeaShrimpCavitationPunchState.cs:34 — SeaShrimpCavitationPunchState.OnUpdate has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SeaShrimpSuperCavitationState.OnUpdate (cyclomatic 18) · ×1
  • SeaShrimpSuperCavitationState.OnUpdate (cyclomatic 18) Content/NPCs/SeaShrimp/States/SeaShrimpSuperCavitationState.cs:43 — SeaShrimpSuperCavitationState.OnUpdate has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SHPCPanelState.Update (cyclomatic 18) · ×1
  • SHPCPanelState.Update (cyclomatic 18) Content/Narrative/Presentation/Skins/SHPC/SHPCPanelState.cs:39 — SHPCPanelState.Update has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · QuestBookGuidePlayer.StepSatisfied (cyclomatic 18) · ×1
  • QuestBookGuidePlayer.StepSatisfied (cyclomatic 18) Content/QuestLogs/Guide/QuestBookGuidePlayer.cs:449 — QuestBookGuidePlayer.StepSatisfied has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ChroniclePen.InkRoute (cyclomatic 18) · ×1
  • ChroniclePen.InkRoute (cyclomatic 18) Content/QuestLogs/Styles/Chronicle/ChroniclePen.cs:503 — ChroniclePen.InkRoute has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ForestQuestLogStyle.DrawProgressBar (cyclomatic 18) · ×1
  • ForestQuestLogStyle.DrawProgressBar (cyclomatic 18) Content/QuestLogs/Styles/ForestQuestLogStyle.cs:447 — ForestQuestLogStyle.DrawProgressBar has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · HotwindQuestLogStyle.DrawNode (cyclomatic 18) · ×1
  • HotwindQuestLogStyle.DrawNode (cyclomatic 18) Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:130 — HotwindQuestLogStyle.DrawNode has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · L2CellRow.Build (cyclomatic 18) · ×1
  • L2CellRow.Build (cyclomatic 18) Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2CellRow.cs:79 — L2CellRow.Build has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · L5Content.PlaceAndBuildNode (cyclomatic 18) · ×1
  • L5Content.PlaceAndBuildNode (cyclomatic 18) Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Content.cs:229 — L5Content.PlaceAndBuildNode has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · L5Content.RouteSpineDrops (cyclomatic 18) · ×1
  • L5Content.RouteSpineDrops (cyclomatic 18) Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Content.cs:577 — L5Content.RouteSpineDrops has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · L5TunnelCarver.Carve (cyclomatic 18) · ×1
  • L5TunnelCarver.Carve (cyclomatic 18) Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5TunnelCarver.cs:79 — L5TunnelCarver.Carve has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · LanternWarden.UpdateChase (cyclomatic 18) · ×1
  • LanternWarden.UpdateChase (cyclomatic 18) Content/Scenarios/Dungeonworld/NPCs/Elites/LanternWarden.cs:288 — LanternWarden.UpdateChase has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FoundryOverseer.UpdateWheelRoll (cyclomatic 18) · ×1
  • FoundryOverseer.UpdateWheelRoll (cyclomatic 18) Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:781 — FoundryOverseer.UpdateWheelRoll has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FoundryOverseer.UpdateBreakRail (cyclomatic 18) · ×1
  • FoundryOverseer.UpdateBreakRail (cyclomatic 18) Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:848 — FoundryOverseer.UpdateBreakRail has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OverseerDormantRig.UpdateDormant (cyclomatic 18) · ×1
  • OverseerDormantRig.UpdateDormant (cyclomatic 18) Content/Scenarios/Dungeonworld/NPCs/OverseerDormantRig.cs:114 — OverseerDormantRig.UpdateDormant has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · UndrownedThrone.UpdateDormant (cyclomatic 18) · ×1
  • UndrownedThrone.UpdateDormant (cyclomatic 18) Content/Scenarios/Dungeonworld/NPCs/UndrownedThrone.cs:120 — UndrownedThrone.UpdateDormant has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ToriiShrineActor.UpdateDeparture (cyclomatic 18) · ×1
  • ToriiShrineActor.UpdateDeparture (cyclomatic 18) Content/Scenarios/Himayo/ToriiShrines/ToriiShrineActor.cs:289 — ToriiShrineActor.UpdateDeparture has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniRainWorldState.UpdateFx (cyclomatic 18) · ×1
  • OniRainWorldState.UpdateFx (cyclomatic 18) Content/Scenarios/Kiame/Overlay/OniRainWorldState.cs:200 — OniRainWorldState.UpdateFx has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OniUmbrellaPuddleRender.EndCaptureDraw (cyclomatic 18) · ×1
  • OniUmbrellaPuddleRender.EndCaptureDraw (cyclomatic 18) Content/Scenarios/Kiame/Overlay/OniUmbrellaPuddleRender.cs:27 — OniUmbrellaPuddleRender.EndCaptureDraw has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · KiyumeWhiteHound.TrySpawn (cyclomatic 18) · ×1
  • KiyumeWhiteHound.TrySpawn (cyclomatic 18) Content/Scenarios/Kiyume/NPCs/KiyumeWhiteHound.cs:288 — KiyumeWhiteHound.TrySpawn has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OldNetSkyEvents.UpdateTide (cyclomatic 18) · ×1
  • OldNetSkyEvents.UpdateTide (cyclomatic 18) Content/Scenarios/OldNet/Backgrounds/OldNetSkyEvents.cs:158 — OldNetSkyEvents.UpdateTide has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OldNetWardenICE.DrawTelegraphs (cyclomatic 18) · ×1
  • OldNetWardenICE.DrawTelegraphs (cyclomatic 18) Content/Scenarios/OldNet/NPCs/OldNetWardenICE.cs:979 — OldNetWardenICE.DrawTelegraphs has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OldNetGuideLead.UpdateUI (cyclomatic 18) · ×1
  • OldNetGuideLead.UpdateUI (cyclomatic 18) Content/Scenarios/OldNet/UI/OldNetGuideLead.cs:123 — OldNetGuideLead.UpdateUI has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SylvanOutpost.AddNaturalDecoration (cyclomatic 18) · ×1
  • SylvanOutpost.AddNaturalDecoration (cyclomatic 18) Content/Structures/DatIO/SylvanOutpost.cs:598 — SylvanOutpost.AddNaturalDecoration has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · IndustrialSkyIslandGen.PopulateDeck (cyclomatic 18) · ×1
  • IndustrialSkyIslandGen.PopulateDeck (cyclomatic 18) Content/Structures/IndustrialSkyIslandGen.cs:242 — IndustrialSkyIslandGen.PopulateDeck has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · OverhaulSettingsUI.DrawContent (cyclomatic 18) · ×1
  • OverhaulSettingsUI.DrawContent (cyclomatic 18) Content/UIs/OverhaulSettings/OverhaulSettingsUI.cs:507 — OverhaulSettingsUI.DrawContent has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · WeaponSkillHud.Update (cyclomatic 18) · ×1
  • WeaponSkillHud.Update (cyclomatic 18) Content/UIs/WeaponSkills/WeaponSkillHud.cs:135 — WeaponSkillHud.Update has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · WraithSynergy.EdgePair (cyclomatic 18) · ×1
  • WraithSynergy.EdgePair (cyclomatic 18) Content/Wraiths/Core/WraithSynergy.cs:121 — WraithSynergy.EdgePair has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BrideSeizurePerformance.Update (cyclomatic 18) · ×1
  • BrideSeizurePerformance.Update (cyclomatic 18) Content/Wraiths/Deaths/Performances/BrideSeizurePerformance.cs:59 — BrideSeizurePerformance.Update has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ModCall.HandleString (cyclomatic 18) · ×1
  • ModCall.HandleString (cyclomatic 18) ModCall.cs:67 — ModCall.HandleString has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CyberInventoryPanel.UpdateInteraction (cyclomatic 17) · ×1
  • CyberInventoryPanel.UpdateInteraction (cyclomatic 17) Content/Cyberwares/UIs/CyberInventoryPanel.cs:200 — CyberInventoryPanel.UpdateInteraction 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.
D1 · Cyclomatic Complexity · CyberInventoryPanel.DrawItemList (cyclomatic 17) · ×1
  • CyberInventoryPanel.DrawItemList (cyclomatic 17) Content/Cyberwares/UIs/CyberInventoryPanel.cs:413 — CyberInventoryPanel.DrawItemList 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.
D1 · Cyclomatic Complexity · BrinefumeHazeTideProj.AI (cyclomatic 17) · ×1
  • BrinefumeHazeTideProj.AI (cyclomatic 17) Content/GameModes/BrutalMobs/Ambience/Brinefume/Projectiles/BrinefumeHazeTideProj.cs:59 — BrinefumeHazeTideProj.AI 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.
D1 · Cyclomatic Complexity · DuskhallAmbience.UpdateCandles (cyclomatic 17) · ×1
  • DuskhallAmbience.UpdateCandles (cyclomatic 17) Content/GameModes/BrutalMobs/Ambience/Duskhall/DuskhallAmbience.cs:313 — DuskhallAmbience.UpdateCandles 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.
D1 · Cyclomatic Complexity · FleshfenDewRainProj.PreDraw (cyclomatic 17) · ×1
  • FleshfenDewRainProj.PreDraw (cyclomatic 17) Content/GameModes/BrutalMobs/Ambience/Fleshfen/Projectiles/FleshfenDewRainProj.cs:305 — FleshfenDewRainProj.PreDraw 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.
D1 · Cyclomatic Complexity · TidecallRipCurrentProj.PreDraw (cyclomatic 17) · ×1
  • TidecallRipCurrentProj.PreDraw (cyclomatic 17) Content/GameModes/BrutalMobs/Ambience/Tidecall/Projectiles/TidecallRipCurrentProj.cs:198 — TidecallRipCurrentProj.PreDraw 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.
D1 · Cyclomatic Complexity · DdFirePillarProj.AI (cyclomatic 17) · ×1
  • DdFirePillarProj.AI (cyclomatic 17) Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdFirePillarProj.cs:83 — DdFirePillarProj.AI 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.
D1 · Cyclomatic Complexity · DdHammerConeOmen.AI (cyclomatic 17) · ×1
  • DdHammerConeOmen.AI (cyclomatic 17) Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdHammerConeOmen.cs:86 — DdHammerConeOmen.AI 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.
D1 · Cyclomatic Complexity · EliteMoveNPC.ServerScatter (cyclomatic 17) · ×1
  • EliteMoveNPC.ServerScatter (cyclomatic 17) Content/GameModes/BrutalMobs/EliteMove/EliteMoveNPC.cs:482 — EliteMoveNPC.ServerScatter 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.
D1 · Cyclomatic Complexity · FrmMiniBossNPC.TryStartSignature (cyclomatic 17) · ×1
  • FrmMiniBossNPC.TryStartSignature (cyclomatic 17) Content/GameModes/BrutalMobs/FrostMoon/FrmMiniBossNPC.cs:201 — FrmMiniBossNPC.TryStartSignature 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.
D1 · Cyclomatic Complexity · MrtLaserMarkLine.AI (cyclomatic 17) · ×1
  • MrtLaserMarkLine.AI (cyclomatic 17) Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserMarkLine.cs:121 — MrtLaserMarkLine.AI 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.
D1 · Cyclomatic Complexity · MushroomSporeMistTelegraph.AI (cyclomatic 17) · ×1
  • MushroomSporeMistTelegraph.AI (cyclomatic 17) Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomSporeMistTelegraph.cs:87 — MushroomSporeMistTelegraph.AI 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.
D1 · Cyclomatic Complexity · NightPackNPC.TickTelegraph (cyclomatic 17) · ×1
  • NightPackNPC.TickTelegraph (cyclomatic 17) Content/GameModes/BrutalMobs/NightPack/NightPackNPC.cs:274 — NightPackNPC.TickTelegraph 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.
D1 · Cyclomatic Complexity · PmkChargeOmen.AI (cyclomatic 17) · ×1
  • PmkChargeOmen.AI (cyclomatic 17) Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkChargeOmen.cs:93 — PmkChargeOmen.AI 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.
D1 · Cyclomatic Complexity · PmkEmberFlareProj.AI (cyclomatic 17) · ×1
  • PmkEmberFlareProj.AI (cyclomatic 17) Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkEmberFlareProj.cs:57 — PmkEmberFlareProj.AI 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.
D1 · Cyclomatic Complexity · SlimeGelBomb.AI (cyclomatic 17) · ×1
  • SlimeGelBomb.AI (cyclomatic 17) Content/GameModes/BrutalMobs/SlimeKin/Projectiles/SlimeGelBomb.cs:67 — SlimeGelBomb.AI 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.
D1 · Cyclomatic Complexity · StonebornJavelinOmen.AI (cyclomatic 17) · ×1
  • StonebornJavelinOmen.AI (cyclomatic 17) Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornJavelinOmen.cs:82 — StonebornJavelinOmen.AI 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.
D1 · Cyclomatic Complexity · GodSmithCobaltShield.OnHurt (cyclomatic 17) · ×1
  • GodSmithCobaltShield.OnHurt (cyclomatic 17) Content/GameModes/GodSmith/Accessories/Defense/GodSmithShieldChain.cs:72 — GodSmithCobaltShield.OnHurt 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.
D1 · Cyclomatic Complexity · GsBoomerThrowHeldBase.AI (cyclomatic 17) · ×1
  • GsBoomerThrowHeldBase.AI (cyclomatic 17) Content/GameModes/GodSmith/Weapons/Boomerangs/GsBoomerThrowHeld.cs:78 — GsBoomerThrowHeldBase.AI 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.
D1 · Cyclomatic Complexity · GsStarWrathFallProj.AI (cyclomatic 17) · ×1
  • GsStarWrathFallProj.AI (cyclomatic 17) Content/GameModes/GodSmith/Weapons/Broadswords/GsStarWrath.cs:281 — GsStarWrathFallProj.AI 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.
D1 · Cyclomatic Complexity · GsFlamerHeldBase.AI (cyclomatic 17) · ×1
  • GsFlamerHeldBase.AI (cyclomatic 17) Content/GameModes/GodSmith/Weapons/Flamethrowers/FlamethrowersShared.cs:72 — GsFlamerHeldBase.AI 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.
D1 · Cyclomatic Complexity · GsElectrosphereLauncher.GsProjPostAI (cyclomatic 17) · ×1
  • GsElectrosphereLauncher.GsProjPostAI (cyclomatic 17) Content/GameModes/GodSmith/Weapons/Launchers/GsElectrosphereLauncher.cs:38 — GsElectrosphereLauncher.GsProjPostAI 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.
D1 · Cyclomatic Complexity · GsLastPrismHeldProj.ChannelAI (cyclomatic 17) · ×1
  • GsLastPrismHeldProj.ChannelAI (cyclomatic 17) Content/GameModes/GodSmith/Weapons/MagicConduit/Projectiles/GsLastPrismHeldProj.cs:84 — GsLastPrismHeldProj.ChannelAI 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.
D1 · Cyclomatic Complexity · GsScourgeTinyEaterProj.FindTarget (cyclomatic 17) · ×1
  • GsScourgeTinyEaterProj.FindTarget (cyclomatic 17) Content/GameModes/GodSmith/Weapons/MeleeOddities/GsScourgeoftheCorruptor.cs:360 — GsScourgeTinyEaterProj.FindTarget 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.
D1 · Cyclomatic Complexity · MinionDoctrine.ApplyFormationDrift (cyclomatic 17) · ×1
  • MinionDoctrine.ApplyFormationDrift (cyclomatic 17) Content/GameModes/GodSmith/Weapons/SummonMinions/MinionDoctrine.cs:333 — MinionDoctrine.ApplyFormationDrift 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.
D1 · Cyclomatic Complexity · GameModeRenderer.DrawHoverPanel (cyclomatic 17) · ×1
  • GameModeRenderer.DrawHoverPanel (cyclomatic 17) Content/GameModes/UI/GameModeRenderer.cs:404 — GameModeRenderer.DrawHoverPanel 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.
D1 · Cyclomatic Complexity · GameModeTabUI.UpdateInteraction (cyclomatic 17) · ×1
  • GameModeTabUI.UpdateInteraction (cyclomatic 17) Content/GameModes/UI/GameModeTabUI.cs:224 — GameModeTabUI.UpdateInteraction 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.
D1 · Cyclomatic Complexity · HackEffectNPCDraw.PreDraw (cyclomatic 17) · ×1
  • HackEffectNPCDraw.PreDraw (cyclomatic 17) Content/HackTimes/HackEffectNPC.cs:156 — HackEffectNPCDraw.PreDraw 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.
D1 · Cyclomatic Complexity · HackTimeNetSync.ExecuteAuthorityRequest (cyclomatic 17) · ×1
  • HackTimeNetSync.ExecuteAuthorityRequest (cyclomatic 17) Content/HackTimes/HackTimeNetSync.cs:570 — HackTimeNetSync.ExecuteAuthorityRequest 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: HackTimeNetSync.TryCreateEffectRecord (cyclomatic 21) 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.
D1 · Cyclomatic Complexity · TileConscript.GetTileMinPick (cyclomatic 17) · ×1
  • TileConscript.GetTileMinPick (cyclomatic 17) Content/HackTimes/Protocols/TileConscript.cs:70 — TileConscript.GetTileMinPick 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.
D1 · Cyclomatic Complexity · PlayerHackAuthority.UpdateAuthority (cyclomatic 17) · ×1
  • PlayerHackAuthority.UpdateAuthority (cyclomatic 17) Content/HackTimes/PvP/PlayerHackNet.cs:442 — PlayerHackAuthority.UpdateAuthority 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.
D1 · Cyclomatic Complexity · BossPartScannable.BuildScanData (cyclomatic 17) · ×1
  • BossPartScannable.BuildScanData (cyclomatic 17) Content/HackTimes/Scannables/BossPartScannable.cs:26 — BossPartScannable.BuildScanData 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.
D1 · Cyclomatic Complexity · NpcScannable.BuildScanData (cyclomatic 17) · ×1
  • NpcScannable.BuildScanData (cyclomatic 17) Content/HackTimes/Scannables/NpcScannable.cs:36 — NpcScannable.BuildScanData 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.
D1 · Cyclomatic Complexity · BottlingMachineTP.Draw (cyclomatic 17) · ×1
  • BottlingMachineTP.Draw (cyclomatic 17) Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineTP.cs:284 — BottlingMachineTP.Draw 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.
D1 · Cyclomatic Complexity · CrusherTile.PreDraw (cyclomatic 17) · ×1
  • CrusherTile.PreDraw (cyclomatic 17) Content/Industrials/ElectricPowers/Crushers/CrusherTile.cs:86 — CrusherTile.PreDraw 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.
D1 · Cyclomatic Complexity · HealStationTP.UpdateTurret (cyclomatic 17) · ×1
  • HealStationTP.UpdateTurret (cyclomatic 17) Content/Industrials/ElectricPowers/HealingStations/HealStationTP.cs:52 — HealStationTP.UpdateTurret 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.
D1 · Cyclomatic Complexity · OreDropRule.Evaluate (cyclomatic 17) · ×1
  • OreDropRule.Evaluate (cyclomatic 17) Content/Industrials/ElectricPowers/MiningMachines/MiningMachineSystem.cs:339 — OreDropRule.Evaluate 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: MiningMachineSystem.LoadStandardOres (cyclomatic 19) 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.
D1 · Cyclomatic Complexity · MushroomFarmerTP.PlayActionEffect (cyclomatic 17) · ×1
  • MushroomFarmerTP.PlayActionEffect (cyclomatic 17) Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:567 — MushroomFarmerTP.PlayActionEffect 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.
D1 · Cyclomatic Complexity · ShimmerTransmuteEngine.Classify (cyclomatic 17) · ×1
  • ShimmerTransmuteEngine.Classify (cyclomatic 17) Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterTP.cs:53 — ShimmerTransmuteEngine.Classify 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.
D1 · Cyclomatic Complexity · TreeBlueprint.CanPlaceCommonAt (cyclomatic 17) · ×1
  • TreeBlueprint.CanPlaceCommonAt (cyclomatic 17) Content/Industrials/ElectricPowers/TreeRegrowths/TreeBlueprint.cs:454 — TreeBlueprint.CanPlaceCommonAt 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.
D1 · Cyclomatic Complexity · TreeRegrowth.DrawTopFoliage (cyclomatic 17) · ×1
  • TreeRegrowth.DrawTopFoliage (cyclomatic 17) Content/Industrials/ElectricPowers/TreeRegrowths/TreeRegrowth.cs:379 — TreeRegrowth.DrawTopFoliage 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.
D1 · Cyclomatic Complexity · BiomassGeneratorTP.GeneratorUpdate (cyclomatic 17) · ×1
  • BiomassGeneratorTP.GeneratorUpdate (cyclomatic 17) Content/Industrials/Generator/Biomass/BiomassGenerator.cs:243 — BiomassGeneratorTP.GeneratorUpdate 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.
D1 · Cyclomatic Complexity · MirrorheartEchoGlobal.OnSpawn (cyclomatic 17) · ×1
  • MirrorheartEchoGlobal.OnSpawn (cyclomatic 17) Content/Items/Accessories/BrutalRelics/BrainOfCthulhu/MirrorheartEchoGlobal.cs:28 — MirrorheartEchoGlobal.OnSpawn 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.
D1 · Cyclomatic Complexity · BloodfogVeilProj.UpdateDash (cyclomatic 17) · ×1
  • BloodfogVeilProj.UpdateDash (cyclomatic 17) Content/Items/Accessories/BrutalRelics/EyeOfCthulhu/BloodfogVeilProj.cs:173 — BloodfogVeilProj.UpdateDash 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.
D1 · Cyclomatic Complexity · FallenCrownProj.AI (cyclomatic 17) · ×1
  • FallenCrownProj.AI (cyclomatic 17) Content/Items/Accessories/BrutalRelics/KingSlime/FallenCrownProj.cs:53 — FallenCrownProj.AI 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.
D1 · Cyclomatic Complexity · RoyalGelField.AI (cyclomatic 17) · ×1
  • RoyalGelField.AI (cyclomatic 17) Content/Items/Accessories/BrutalRelics/KingSlime/RoyalGelField.cs:60 — RoyalGelField.AI 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.
D1 · Cyclomatic Complexity · RefractionWaltzCrystalProj.RefreshLinkCaches (cyclomatic 17) · ×1
  • RefractionWaltzCrystalProj.RefreshLinkCaches (cyclomatic 17) Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzCrystalProj.cs:153 — RefractionWaltzCrystalProj.RefreshLinkCaches 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.
D1 · Cyclomatic Complexity · SingularityBlackHole.AI (cyclomatic 17) · ×1
  • SingularityBlackHole.AI (cyclomatic 17) Content/Items/Accessories/EyeOfSingularity.cs:96 — SingularityBlackHole.AI 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.
D1 · Cyclomatic Complexity · ElysiumPlayer.SwapSeats (cyclomatic 17) · ×1
  • ElysiumPlayer.SwapSeats (cyclomatic 17) Content/Items/Magic/Elysiums/ElysiumPlayer.cs:308 — ElysiumPlayer.SwapSeats 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.
D1 · Cyclomatic Complexity · AbyssrendClampHeld.HandleSuction (cyclomatic 17) · ×1
  • AbyssrendClampHeld.HandleSuction (cyclomatic 17) Content/Items/Melee/Abyssrends/AbyssrendClampHeld.cs:223 — AbyssrendClampHeld.HandleSuction 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.
D1 · Cyclomatic Complexity · ArbiterFlameRenderer.CollectSources (cyclomatic 17) · ×1
  • ArbiterFlameRenderer.CollectSources (cyclomatic 17) Content/Items/Melee/Arbiters/ArbiterFlameRenderer.cs:131 — ArbiterFlameRenderer.CollectSources 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.
D1 · Cyclomatic Complexity · CursedflameBloodfistHeld.AI (cyclomatic 17) · ×1
  • CursedflameBloodfistHeld.AI (cyclomatic 17) Content/Items/Melee/CursedflameBloodfists/CursedflameBloodfistHeld.cs:104 — CursedflameBloodfistHeld.AI 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.
D1 · Cyclomatic Complexity · DawnshatterHeld.AI (cyclomatic 17) · ×1
  • DawnshatterHeld.AI (cyclomatic 17) Content/Items/Melee/DawnshatterAzures/DawnshatterHeld.cs:415 — DawnshatterHeld.AI 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.
D1 · Cyclomatic Complexity · DragonsScaleGreatswordHeld.AI (cyclomatic 17) · ×1
  • DragonsScaleGreatswordHeld.AI (cyclomatic 17) Content/Items/Melee/DragonsScaleGreatsword.cs:208 — DragonsScaleGreatswordHeld.AI 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.
D1 · Cyclomatic Complexity · HeartcarverHeld.OnCarveHit (cyclomatic 17) · ×1
  • HeartcarverHeld.OnCarveHit (cyclomatic 17) Content/Items/Melee/Heartcarver.cs:359 — HeartcarverHeld.OnCarveHit 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.
D1 · Cyclomatic Complexity · NeutronGlaiveHeld.HandlePhaseEvents (cyclomatic 17) · ×1
  • NeutronGlaiveHeld.HandlePhaseEvents (cyclomatic 17) Content/Items/Melee/NeutronGlaive.cs:355 — NeutronGlaiveHeld.HandlePhaseEvents 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.
D1 · Cyclomatic Complexity · NeutronScytheHeld.AI (cyclomatic 17) · ×1
  • NeutronScytheHeld.AI (cyclomatic 17) Content/Items/Melee/NeutronScythe.cs:163 — NeutronScytheHeld.AI 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.
D1 · Cyclomatic Complexity · WeaverGrievancesHeld.AI (cyclomatic 17) · ×1
  • WeaverGrievancesHeld.AI (cyclomatic 17) Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:231 — WeaverGrievancesHeld.AI 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.
D1 · Cyclomatic Complexity · AvalancheM60Held.Fire (cyclomatic 17) · ×1
  • AvalancheM60Held.Fire (cyclomatic 17) Content/Items/Ranged/AvalancheM60.cs:145 — AvalancheM60Held.Fire 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.
D1 · Cyclomatic Complexity · DicoriaRay.AI (cyclomatic 17) · ×1
  • DicoriaRay.AI (cyclomatic 17) Content/Items/Ranged/Dicoria.cs:166 — DicoriaRay.AI 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.
D1 · Cyclomatic Complexity · NeutronBowHeld.UpdateRightCharge (cyclomatic 17) · ×1
  • NeutronBowHeld.UpdateRightCharge (cyclomatic 17) Content/Items/Ranged/NeutronBows/NeutronBow.cs:192 — NeutronBowHeld.UpdateRightCharge 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.
D1 · Cyclomatic Complexity · TiroFinaleRenderer.DrawRibbonBand (cyclomatic 17) · ×1
  • TiroFinaleRenderer.DrawRibbonBand (cyclomatic 17) Content/Items/Ranged/TiroFinales/TiroFinaleRenderer.cs:267 — TiroFinaleRenderer.DrawRibbonBand 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.
D1 · Cyclomatic Complexity · UndertowBurst.AI (cyclomatic 17) · ×1
  • UndertowBurst.AI (cyclomatic 17) Content/Items/Ranged/Undertows/UndertowSpine.cs:226 — UndertowBurst.AI 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.
D1 · Cyclomatic Complexity · MarbleShieldPlayer.BurstGuard (cyclomatic 17) · ×1
  • MarbleShieldPlayer.BurstGuard (cyclomatic 17) Content/Items/Stones/Marbles/MarbleShield.cs:179 — MarbleShieldPlayer.BurstGuard 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.
D1 · Cyclomatic Complexity · CatfishLeaper.AI (cyclomatic 17) · ×1
  • CatfishLeaper.AI (cyclomatic 17) Content/LegendWeapon/HalibutLegend/FishSkills/FishCat.cs:158 — CatfishLeaper.AI 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.
D1 · Cyclomatic Complexity · DoubleCodProjectile.AI (cyclomatic 17) · ×1
  • DoubleCodProjectile.AI (cyclomatic 17) Content/LegendWeapon/HalibutLegend/FishSkills/FishDoubleCod.cs:217 — DoubleCodProjectile.AI 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.
D1 · Cyclomatic Complexity · SoulEaterBite.AI (cyclomatic 17) · ×1
  • SoulEaterBite.AI (cyclomatic 17) Content/LegendWeapon/HalibutLegend/FishSkills/FishEaterofPlankton.cs:115 — SoulEaterBite.AI 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.
D1 · Cyclomatic Complexity · HarpyFeatherOrbit.AI (cyclomatic 17) · ×1
  • HarpyFeatherOrbit.AI (cyclomatic 17) Content/LegendWeapon/HalibutLegend/FishSkills/FishHarpy.cs:179 — HarpyFeatherOrbit.AI 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.
D1 · Cyclomatic Complexity · HoneyBeeMinion.PreDraw (cyclomatic 17) · ×1
  • HoneyBeeMinion.PreDraw (cyclomatic 17) Content/LegendWeapon/HalibutLegend/FishSkills/FishHoney.cs:728 — HoneyBeeMinion.PreDraw 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.
D1 · Cyclomatic Complexity · OilBlob.CheckForIgnition (cyclomatic 17) · ×1
  • OilBlob.CheckForIgnition (cyclomatic 17) Content/LegendWeapon/HalibutLegend/FishSkills/FishVariegatedLard.cs:342 — OilBlob.CheckForIgnition 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.
D1 · Cyclomatic Complexity · FishVoodooThread.PreDraw (cyclomatic 17) · ×1
  • FishVoodooThread.PreDraw (cyclomatic 17) Content/LegendWeapon/HalibutLegend/FishSkills/FishVoodooRitual.cs:603 — FishVoodooThread.PreDraw 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.
D1 · Cyclomatic Complexity · MiniWhiteWyvern.AI (cyclomatic 17) · ×1
  • MiniWhiteWyvern.AI (cyclomatic 17) Content/LegendWeapon/HalibutLegend/FishSkills/FishWyverntail.cs:173 — MiniWhiteWyvern.AI 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.
D1 · Cyclomatic Complexity · SkeletronHandMinion.WindUpBehavior (cyclomatic 17) · ×1
  • SkeletronHandMinion.WindUpBehavior (cyclomatic 17) Content/LegendWeapon/HalibutLegend/FishSkills/Fishotroning.cs:473 — SkeletronHandMinion.WindUpBehavior 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.
D1 · Cyclomatic Complexity · HalibutOverride.Shoot (cyclomatic 17) · ×1
  • HalibutOverride.Shoot (cyclomatic 17) Content/LegendWeapon/HalibutLegend/HalibutOverride.cs:197 — HalibutOverride.Shoot 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.
D1 · Cyclomatic Complexity · HalibutHudLead.UpdateUI (cyclomatic 17) · ×1
  • HalibutHudLead.UpdateUI (cyclomatic 17) Content/LegendWeapon/HalibutLegend/UI/HalibutHudLead.cs:224 — HalibutHudLead.UpdateUI 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.
D1 · Cyclomatic Complexity · KikasaDrown.TryDrownAtCursor (cyclomatic 17) · ×1
  • KikasaDrown.TryDrownAtCursor (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrown.cs:130 — KikasaDrown.TryDrownAtCursor 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.
D1 · Cyclomatic Complexity · KikasaDrownFX.RunCaptures (cyclomatic 17) · ×1
  • KikasaDrownFX.RunCaptures (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:838 — KikasaDrownFX.RunCaptures 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.
D1 · Cyclomatic Complexity · KikasaMinionDrown.Update (cyclomatic 17) · ×1
  • KikasaMinionDrown.Update (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaMinionDrown.cs:171 — KikasaMinionDrown.Update 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.
D1 · Cyclomatic Complexity · KikasaMinionDrownFX.Draw (cyclomatic 17) · ×1
  • KikasaMinionDrownFX.Draw (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaMinionDrownFX.cs:433 — KikasaMinionDrownFX.Draw 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.
D1 · Cyclomatic Complexity · KikasaRainUmbrella.UpdateFlip (cyclomatic 17) · ×1
  • KikasaRainUmbrella.UpdateFlip (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:922 — KikasaRainUmbrella.UpdateFlip 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.
D1 · Cyclomatic Complexity · KikasaResetHourglass.StepParticles (cyclomatic 17) · ×1
  • KikasaResetHourglass.StepParticles (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetHourglass.cs:236 — KikasaResetHourglass.StepParticles 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.
D1 · Cyclomatic Complexity · KikasaBoomerangServant.AI (cyclomatic 17) · ×1
  • KikasaBoomerangServant.AI (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:210 — KikasaBoomerangServant.AI 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.
D1 · Cyclomatic Complexity · KikasaFlailServant.AI (cyclomatic 17) · ×1
  • KikasaFlailServant.AI (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:210 — KikasaFlailServant.AI 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.
D1 · Cyclomatic Complexity · KikasaOnikiriServant.UpdateEmerge (cyclomatic 17) · ×1
  • KikasaOnikiriServant.UpdateEmerge (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:328 — KikasaOnikiriServant.UpdateEmerge 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.
D1 · Cyclomatic Complexity · KikasaOnikiriServant.UpdateGrand (cyclomatic 17) · ×1
  • KikasaOnikiriServant.UpdateGrand (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:623 — KikasaOnikiriServant.UpdateGrand 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.
D1 · Cyclomatic Complexity · KikasaPandemoniumServant.UpdateEmerge (cyclomatic 17) · ×1
  • KikasaPandemoniumServant.UpdateEmerge (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:274 — KikasaPandemoniumServant.UpdateEmerge 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.
D1 · Cyclomatic Complexity · KikasaRodServant.UpdateEmerge (cyclomatic 17) · ×1
  • KikasaRodServant.UpdateEmerge (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:247 — KikasaRodServant.UpdateEmerge 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.
D1 · Cyclomatic Complexity · KikasaSpearServant.AI (cyclomatic 17) · ×1
  • KikasaSpearServant.AI (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:221 — KikasaSpearServant.AI 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.
D1 · Cyclomatic Complexity · KikasaYoyoServant.AI (cyclomatic 17) · ×1
  • KikasaYoyoServant.AI (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:208 — KikasaYoyoServant.AI 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.
D1 · Cyclomatic Complexity · KikasaZenithServant.UpdateEmerge (cyclomatic 17) · ×1
  • KikasaZenithServant.UpdateEmerge (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:344 — KikasaZenithServant.UpdateEmerge 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.
D1 · Cyclomatic Complexity · KikasaBloomSerpentServant.UpdateEmerge (cyclomatic 17) · ×1
  • KikasaBloomSerpentServant.UpdateEmerge (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:277 — KikasaBloomSerpentServant.UpdateEmerge 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.
D1 · Cyclomatic Complexity · KikasaBloomSerpentServant.UpdateNeedleRipple (cyclomatic 17) · ×1
  • KikasaBloomSerpentServant.UpdateNeedleRipple (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:530 — KikasaBloomSerpentServant.UpdateNeedleRipple 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.
D1 · Cyclomatic Complexity · KikasaBrainServant.UpdateBlink (cyclomatic 17) · ×1
  • KikasaBrainServant.UpdateBlink (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:593 — KikasaBrainServant.UpdateBlink 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.
D1 · Cyclomatic Complexity · KikasaBrainServant.UpdateSacrifice (cyclomatic 17) · ×1
  • KikasaBrainServant.UpdateSacrifice (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:706 — KikasaBrainServant.UpdateSacrifice 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.
D1 · Cyclomatic Complexity · KikasaBrainServant.UpdateOrbit (cyclomatic 17) · ×1
  • KikasaBrainServant.UpdateOrbit (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:865 — KikasaBrainServant.UpdateOrbit 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.
D1 · Cyclomatic Complexity · KikasaCultistIceShard.AI (cyclomatic 17) · ×1
  • KikasaCultistIceShard.AI (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistIceShard.cs:57 — KikasaCultistIceShard.AI 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.
D1 · Cyclomatic Complexity · KikasaCultistServant.UpdateFollow (cyclomatic 17) · ×1
  • KikasaCultistServant.UpdateFollow (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:423 — KikasaCultistServant.UpdateFollow 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.
D1 · Cyclomatic Complexity · KikasaDeerclopsBloodSpike.AI (cyclomatic 17) · ×1
  • KikasaDeerclopsBloodSpike.AI (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsBloodSpike.cs:95 — KikasaDeerclopsBloodSpike.AI 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.
D1 · Cyclomatic Complexity · KikasaDeerclopsServant.UpdateLurch (cyclomatic 17) · ×1
  • KikasaDeerclopsServant.UpdateLurch (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:595 — KikasaDeerclopsServant.UpdateLurch 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.
D1 · Cyclomatic Complexity · KikasaDestroyerBloodJet.AI (cyclomatic 17) · ×1
  • KikasaDestroyerBloodJet.AI (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:87 — KikasaDestroyerBloodJet.AI 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.
D1 · Cyclomatic Complexity · KikasaDestroyerServant.AI (cyclomatic 17) · ×1
  • KikasaDestroyerServant.AI (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:229 — KikasaDestroyerServant.AI 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.
D1 · Cyclomatic Complexity · KikasaEaterServant.UpdateChain (cyclomatic 17) · ×1
  • KikasaEaterServant.UpdateChain (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:924 — KikasaEaterServant.UpdateChain 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.
D1 · Cyclomatic Complexity · KikasaEmpressServant.UpdateDissolve (cyclomatic 17) · ×1
  • KikasaEmpressServant.UpdateDissolve (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:671 — KikasaEmpressServant.UpdateDissolve 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.
D1 · Cyclomatic Complexity · KikasaEyeBloodShot.AI (cyclomatic 17) · ×1
  • KikasaEyeBloodShot.AI (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:69 — KikasaEyeBloodShot.AI 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.
D1 · Cyclomatic Complexity · KikasaEyeServant.AI (cyclomatic 17) · ×1
  • KikasaEyeServant.AI (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:179 — KikasaEyeServant.AI 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.
D1 · Cyclomatic Complexity · KikasaFesterPool.AI (cyclomatic 17) · ×1
  • KikasaFesterPool.AI (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterPool.cs:66 — KikasaFesterPool.AI 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.
D1 · Cyclomatic Complexity · KikasaFesterSerpentServant.UpdateEmerge (cyclomatic 17) · ×1
  • KikasaFesterSerpentServant.UpdateEmerge (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:283 — KikasaFesterSerpentServant.UpdateEmerge 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.
D1 · Cyclomatic Complexity · KikasaFishronServant.AI (cyclomatic 17) · ×1
  • KikasaFishronServant.AI (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:257 — KikasaFishronServant.AI 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.
D1 · Cyclomatic Complexity · KikasaQueenBeeServant.AI (cyclomatic 17) · ×1
  • KikasaQueenBeeServant.AI (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:212 — KikasaQueenBeeServant.AI 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: KikasaQueenBeeServant.WingIntensity (cyclomatic 18) 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.
D1 · Cyclomatic Complexity · KikasaSkeletronBloodSkull.AI (cyclomatic 17) · ×1
  • KikasaSkeletronBloodSkull.AI (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronBloodSkull.cs:65 — KikasaSkeletronBloodSkull.AI 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.
D1 · Cyclomatic Complexity · KikasaSkeletronServant.UpdateSkulls (cyclomatic 17) · ×1
  • KikasaSkeletronServant.UpdateSkulls (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:839 — KikasaSkeletronServant.UpdateSkulls 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.
D1 · Cyclomatic Complexity · KikasaSkeletronServant.UpdateDissolve (cyclomatic 17) · ×1
  • KikasaSkeletronServant.UpdateDissolve (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:960 — KikasaSkeletronServant.UpdateDissolve 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.
D1 · Cyclomatic Complexity · PRT_FuZhaBeatRing.AI (cyclomatic 17) · ×1
  • PRT_FuZhaBeatRing.AI (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuZhaFX.cs:139 — PRT_FuZhaBeatRing.AI 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.
D1 · Cyclomatic Complexity · KikasaThrallProj.UpdateGather (cyclomatic 17) · ×1
  • KikasaThrallProj.UpdateGather (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallProj.cs:298 — KikasaThrallProj.UpdateGather 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.
D1 · Cyclomatic Complexity · KikasaLakeFX.DrawGlowLayer (cyclomatic 17) · ×1
  • KikasaLakeFX.DrawGlowLayer (cyclomatic 17) Content/LegendWeapon/KikasaLegend/KikasaVaults/KikasaLakeFX.cs:546 — KikasaLakeFX.DrawGlowLayer 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.
D1 · Cyclomatic Complexity · LegendData.LoadData (cyclomatic 17) · ×1
  • LegendData.LoadData (cyclomatic 17) Content/LegendWeapon/LegendData.cs:182 — LegendData.LoadData 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.
D1 · Cyclomatic Complexity · CrimsonRendSlash.ModifyHitNPC (cyclomatic 17) · ×1
  • CrimsonRendSlash.ModifyHitNPC (cyclomatic 17) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1451 — CrimsonRendSlash.ModifyHitNPC 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.
D1 · Cyclomatic Complexity · CrimsonSlashRenderer.DrawLayer (cyclomatic 17) · ×1
  • CrimsonSlashRenderer.DrawLayer (cyclomatic 17) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSlashRenderer.cs:361 — CrimsonSlashRenderer.DrawLayer 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.
D1 · Cyclomatic Complexity · CrimsonSweepSlash.ModifyHitNPC (cyclomatic 17) · ×1
  • CrimsonSweepSlash.ModifyHitNPC (cyclomatic 17) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1168 — CrimsonSweepSlash.ModifyHitNPC 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.
D1 · Cyclomatic Complexity · OniDismember.UpdateAll (cyclomatic 17) · ×1
  • OniDismember.UpdateAll (cyclomatic 17) Content/LegendWeapon/OnikiriLegend/OniDismembers/OniDismember.cs:751 — OniDismember.UpdateAll 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.
D1 · Cyclomatic Complexity · OniFlashStep.UpdateTailPose (cyclomatic 17) · ×1
  • OniFlashStep.UpdateTailPose (cyclomatic 17) Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashStep.cs:827 — OniFlashStep.UpdateTailPose 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.
D1 · Cyclomatic Complexity · OniSlash.ModifyHitNPC (cyclomatic 17) · ×1
  • OniSlash.ModifyHitNPC (cyclomatic 17) Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1360 — OniSlash.ModifyHitNPC 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.
D1 · Cyclomatic Complexity · OnikiriNet.TryChangeMei (cyclomatic 17) · ×1
  • OnikiriNet.TryChangeMei (cyclomatic 17) Content/LegendWeapon/OnikiriLegend/OnikiriNet.cs:102 — OnikiriNet.TryChangeMei 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.
D1 · Cyclomatic Complexity · OnikiriPlayer.ClearRemovedMeiTransient (cyclomatic 17) · ×1
  • OnikiriPlayer.ClearRemovedMeiTransient (cyclomatic 17) Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs:489 — OnikiriPlayer.ClearRemovedMeiTransient 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.
D1 · Cyclomatic Complexity · SakuraDashProj.AI (cyclomatic 17) · ×1
  • SakuraDashProj.AI (cyclomatic 17) Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraDashProj.cs:51 — SakuraDashProj.AI 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.
D1 · Cyclomatic Complexity · SakuraKiriPlayer.TransformDrawData (cyclomatic 17) · ×1
  • SakuraKiriPlayer.TransformDrawData (cyclomatic 17) Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraKiriPlayer.cs:132 — SakuraKiriPlayer.TransformDrawData 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.
D1 · Cyclomatic Complexity · SakuraParticleWorld.EmitBurst (cyclomatic 17) · ×1
  • SakuraParticleWorld.EmitBurst (cyclomatic 17) Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraParticleWorld.cs:57 — SakuraParticleWorld.EmitBurst 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.
D1 · Cyclomatic Complexity · OniMeiRenderer.DrawFanRib (cyclomatic 17) · ×1
  • OniMeiRenderer.DrawFanRib (cyclomatic 17) Content/LegendWeapon/OnikiriLegend/UI/OniMeiRenderer.cs:392 — OniMeiRenderer.DrawFanRib 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.
D1 · Cyclomatic Complexity · OniSigilUI.DiffSlotStates (cyclomatic 17) · ×1
  • OniSigilUI.DiffSlotStates (cyclomatic 17) Content/LegendWeapon/OnikiriLegend/UI/OniSigilUI.cs:636 — OniSigilUI.DiffSlotStates 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.
D1 · Cyclomatic Complexity · CyberBanish.IsValidActivation (cyclomatic 17) · ×1
  • CyberBanish.IsValidActivation (cyclomatic 17) Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBanish.Net.cs:390 — CyberBanish.IsValidActivation 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.
D1 · Cyclomatic Complexity · CyberspacePlayer.ApplyRemoteState (cyclomatic 17) · ×1
  • CyberspacePlayer.ApplyRemoteState (cyclomatic 17) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspacePlayer.cs:805 — CyberspacePlayer.ApplyRemoteState 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.
D1 · Cyclomatic Complexity · CyberDomainFreeze.ResendActivation (cyclomatic 17) · ×1
  • CyberDomainFreeze.ResendActivation (cyclomatic 17) Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.Net.cs:183 — CyberDomainFreeze.ResendActivation 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.
D1 · Cyclomatic Complexity · CyberDomainFreeze.ReconcileReplicatedStateForSnapshot (cyclomatic 17) · ×1
  • CyberDomainFreeze.ReconcileReplicatedStateForSnapshot (cyclomatic 17) Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.Net.cs:952 — CyberDomainFreeze.ReconcileReplicatedStateForSnapshot 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.
D1 · Cyclomatic Complexity · CyberDomainFreeze.TryApplyNPC (cyclomatic 17) · ×1
  • CyberDomainFreeze.TryApplyNPC (cyclomatic 17) Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.cs:343 — CyberDomainFreeze.TryApplyNPC 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.
D1 · Cyclomatic Complexity · SHPCNPCEffects.HandleNet (cyclomatic 17) · ×1
  • SHPCNPCEffects.HandleNet (cyclomatic 17) Content/LegendWeapon/SHPCLegend/Cyberspaces/SHPCNPCEffects.Net.cs:61 — SHPCNPCEffects.HandleNet 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: SHPCNPCEffects.IsValidApplyPayload (cyclomatic 24) 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.
D1 · Cyclomatic Complexity · SniperOpticModule.OnPlayerUpdate (cyclomatic 17) · ×1
  • SniperOpticModule.OnPlayerUpdate (cyclomatic 17) Content/LegendWeapon/SHPCLegend/Modules/Optic/SniperOpticModule.cs:88 — SniperOpticModule.OnPlayerUpdate 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.
D1 · Cyclomatic Complexity · ThermalOpticModule.FindWhiteHotTarget (cyclomatic 17) · ×1
  • ThermalOpticModule.FindWhiteHotTarget (cyclomatic 17) Content/LegendWeapon/SHPCLegend/Modules/Optic/ThermalOpticModule.cs:73 — ThermalOpticModule.FindWhiteHotTarget 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.
D1 · Cyclomatic Complexity · MoldCategorySidebar.Draw (cyclomatic 17) · ×1
  • MoldCategorySidebar.Draw (cyclomatic 17) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCategorySidebar.cs:56 — MoldCategorySidebar.Draw 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.
D1 · Cyclomatic Complexity · CharacterDockUI.DrawOverlayText (cyclomatic 17) · ×1
  • CharacterDockUI.DrawOverlayText (cyclomatic 17) Content/MainMenus/Characters/CharacterDockUI.cs:632 — CharacterDockUI.DrawOverlayText 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.
D1 · Cyclomatic Complexity · BssSandPillar.PreDraw (cyclomatic 17) · ×1
  • BssSandPillar.PreDraw (cyclomatic 17) Content/NPCs/BloomsandSerpents/BssSandPillar.cs:667 — BssSandPillar.PreDraw 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.
D1 · Cyclomatic Complexity · BssHubState.UpdateHarass (cyclomatic 17) · ×1
  • BssHubState.UpdateHarass (cyclomatic 17) Content/NPCs/BloomsandSerpents/States/BssHubState.cs:70 — BssHubState.UpdateHarass 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.
D1 · Cyclomatic Complexity · BssNeedleRippleState.FireWave (cyclomatic 17) · ×1
  • BssNeedleRippleState.FireWave (cyclomatic 17) Content/NPCs/BloomsandSerpents/States/BssNeedleRippleState.cs:131 — BssNeedleRippleState.FireWave 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.
D1 · Cyclomatic Complexity · BrainMindSeizePlayer.Drive (cyclomatic 17) · ×1
  • BrainMindSeizePlayer.Drive (cyclomatic 17) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Core/BrainMindSeizePlayer.cs:72 — BrainMindSeizePlayer.Drive 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.
D1 · Cyclomatic Complexity · BrainPhaseTransitionState.OnUpdate (cyclomatic 17) · ×1
  • BrainPhaseTransitionState.OnUpdate (cyclomatic 17) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainPhaseTransitionState.cs:52 — BrainPhaseTransitionState.OnUpdate 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.
D1 · Cyclomatic Complexity · FishronSharkTornadoProj.AI (cyclomatic 17) · ×1
  • FishronSharkTornadoProj.AI (cyclomatic 17) Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronSharkTornadoProj.cs:96 — FishronSharkTornadoProj.AI 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.
D1 · Cyclomatic Complexity · FishronBubbleMazeState.BuildSlots (cyclomatic 17) · ×1
  • FishronBubbleMazeState.BuildSlots (cyclomatic 17) Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronBubbleMazeState.cs:52 — FishronBubbleMazeState.BuildSlots 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.
D1 · Cyclomatic Complexity · EowHeadAI.UpdateSplitSteering (cyclomatic 17) · ×1
  • EowHeadAI.UpdateSplitSteering (cyclomatic 17) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/EowHeadAI.cs:429 — EowHeadAI.UpdateSplitSteering 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.
D1 · Cyclomatic Complexity · EowApexFrenzyState.UpdateDrumRoll (cyclomatic 17) · ×1
  • EowApexFrenzyState.UpdateDrumRoll (cyclomatic 17) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowApexFrenzyState.cs:217 — EowApexFrenzyState.UpdateDrumRoll 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.
D1 · Cyclomatic Complexity · EmpressOfLightAI.AI (cyclomatic 17) · ×1
  • EmpressOfLightAI.AI (cyclomatic 17) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/EmpressOfLightAI.cs:126 — EmpressOfLightAI.AI 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.
D1 · Cyclomatic Complexity · EmpressConnectorState.PickNext (cyclomatic 17) · ×1
  • EmpressConnectorState.PickNext (cyclomatic 17) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/States/EmpressConnectorState.cs:101 — EmpressConnectorState.PickNext 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.
D1 · Cyclomatic Complexity · EmpressDashGrabState.OnUpdate (cyclomatic 17) · ×1
  • EmpressDashGrabState.OnUpdate (cyclomatic 17) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/States/EmpressDashGrabState.cs:51 — EmpressDashGrabState.OnUpdate 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.
D1 · Cyclomatic Complexity · EocBloodFountainState.OnUpdate (cyclomatic 17) · ×1
  • EocBloodFountainState.OnUpdate (cyclomatic 17) Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocBloodFountainState.cs:34 — EocBloodFountainState.OnUpdate 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.
D1 · Cyclomatic Complexity · GolemSunCore.AI (cyclomatic 17) · ×1
  • GolemSunCore.AI (cyclomatic 17) Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemSunCore.cs:110 — GolemSunCore.AI 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.
D1 · Cyclomatic Complexity · GolemFistWindupState.OnUpdate (cyclomatic 17) · ×1
  • GolemFistWindupState.OnUpdate (cyclomatic 17) Content/NPCs/BrutalNPCs/BrutalGolem/States/Fists/GolemFistStates.cs:60 — GolemFistWindupState.OnUpdate 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.
D1 · Cyclomatic Complexity · GolemPunchComboState.OnUpdate (cyclomatic 17) · ×1
  • GolemPunchComboState.OnUpdate (cyclomatic 17) Content/NPCs/BrutalNPCs/BrutalGolem/States/GolemPunchComboState.cs:31 — GolemPunchComboState.OnUpdate 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.
D1 · Cyclomatic Complexity · KingSlimeEngulfState.UpdateAirborne (cyclomatic 17) · ×1
  • KingSlimeEngulfState.UpdateAirborne (cyclomatic 17) Content/NPCs/BrutalNPCs/BrutalKingSlime/States/KingSlimeEngulfState.cs:243 — KingSlimeEngulfState.UpdateAirborne 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.
D1 · Cyclomatic Complexity · CultistPlanetAimLine.AI (cyclomatic 17) · ×1
  • CultistPlanetAimLine.AI (cyclomatic 17) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistPlanetAimLine.cs:57 — CultistPlanetAimLine.AI 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.
D1 · Cyclomatic Complexity · TwinsComboCoordinator.PincerGrabReady (cyclomatic 17) · ×1
  • TwinsComboCoordinator.PincerGrabReady (cyclomatic 17) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Core/TwinsComboCoordinator.cs:45 — TwinsComboCoordinator.PincerGrabReady 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.
D1 · Cyclomatic Complexity · RetinazerPrecisionSniperState.OnUpdate (cyclomatic 17) · ×1
  • RetinazerPrecisionSniperState.OnUpdate (cyclomatic 17) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerPrecisionSniperState.cs:47 — RetinazerPrecisionSniperState.OnUpdate 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.
D1 · Cyclomatic Complexity · MLordLocomotion.ResolveGait (cyclomatic 17) · ×1
  • MLordLocomotion.ResolveGait (cyclomatic 17) Content/NPCs/BrutalNPCs/BrutalMoonLord/Core/MLordLocomotion.cs:489 — MLordLocomotion.ResolveGait 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.
D1 · Cyclomatic Complexity · MoonLordHandAI.ComputeFormationGoal (cyclomatic 17) · ×1
  • MoonLordHandAI.ComputeFormationGoal (cyclomatic 17) Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordHandAI.cs:458 — MoonLordHandAI.ComputeFormationGoal 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.
D1 · Cyclomatic Complexity · QBDiveStrafeState.OnUpdate (cyclomatic 17) · ×1
  • QBDiveStrafeState.OnUpdate (cyclomatic 17) Content/NPCs/BrutalNPCs/BrutalQueenBee/States/QBDiveStrafeState.cs:36 — QBDiveStrafeState.OnUpdate 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.
D1 · Cyclomatic Complexity · QueenCrystalWaltzState.OnUpdate (cyclomatic 17) · ×1
  • QueenCrystalWaltzState.OnUpdate (cyclomatic 17) Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenCrystalWaltzState.cs:38 — QueenCrystalWaltzState.OnUpdate 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.
D1 · Cyclomatic Complexity · SkeletronGhostArmProj.AI (cyclomatic 17) · ×1
  • SkeletronGhostArmProj.AI (cyclomatic 17) Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronGhostArmProj.cs:78 — SkeletronGhostArmProj.AI 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.
D1 · Cyclomatic Complexity · HandSnatchState.UpdateBySubPhase (cyclomatic 17) · ×1
  • HandSnatchState.UpdateBySubPhase (cyclomatic 17) Content/NPCs/BrutalNPCs/BrutalSkeletron/States/Hands/HandSnatchState.cs:67 — HandSnatchState.UpdateBySubPhase 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.
D1 · Cyclomatic Complexity · HeadPrimeAI.ViceExecutionReady (cyclomatic 17) · ×1
  • HeadPrimeAI.ViceExecutionReady (cyclomatic 17) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/HeadPrimeAI.cs:488 — HeadPrimeAI.ViceExecutionReady 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.
D1 · Cyclomatic Complexity · PrimeDeathClawActor.AI (cyclomatic 17) · ×1
  • PrimeDeathClawActor.AI (cyclomatic 17) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/PrimeDeathClawActor.cs:41 — PrimeDeathClawActor.AI 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.
D1 · Cyclomatic Complexity · PrimeSkullBeamProj.AI (cyclomatic 17) · ×1
  • PrimeSkullBeamProj.AI (cyclomatic 17) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeSkullBeamProj.cs:50 — PrimeSkullBeamProj.AI 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.
D1 · Cyclomatic Complexity · WofGrabTongueProj.AI (cyclomatic 17) · ×1
  • WofGrabTongueProj.AI (cyclomatic 17) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofGrabTongueProj.cs:69 — WofGrabTongueProj.AI 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.
D1 · Cyclomatic Complexity · FssClawRig.ResolvePose (cyclomatic 17) · ×1
  • FssClawRig.ResolvePose (cyclomatic 17) Content/NPCs/FestersandSerpents/FssClawRig.cs:197 — FssClawRig.ResolvePose 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.
D1 · Cyclomatic Complexity · ScrapSiegeScreen.PostUpdateEverything (cyclomatic 17) · ×1
  • ScrapSiegeScreen.PostUpdateEverything (cyclomatic 17) Content/NPCs/ScrapCommanders/ScrapSiegeScreen.cs:55 — ScrapSiegeScreen.PostUpdateEverything 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.
D1 · Cyclomatic Complexity · ScrapCrossSpinState.OnUpdate (cyclomatic 17) · ×1
  • ScrapCrossSpinState.OnUpdate (cyclomatic 17) Content/NPCs/ScrapCommanders/States/ScrapCrossSpinState.cs:34 — ScrapCrossSpinState.OnUpdate 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.
D1 · Cyclomatic Complexity · SeaShrimpAbyssScreen.PostUpdateEverything (cyclomatic 17) · ×1
  • SeaShrimpAbyssScreen.PostUpdateEverything (cyclomatic 17) Content/NPCs/SeaShrimp/Rendering/SeaShrimpAbyssScreen.cs:54 — SeaShrimpAbyssScreen.PostUpdateEverything 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.
D1 · Cyclomatic Complexity · SeaShrimpCrescentClapState.OnUpdate (cyclomatic 17) · ×1
  • SeaShrimpCrescentClapState.OnUpdate (cyclomatic 17) Content/NPCs/SeaShrimp/States/SeaShrimpCrescentClapState.cs:30 — SeaShrimpCrescentClapState.OnUpdate 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.
D1 · Cyclomatic Complexity · DraedonQuestLogStyle.DrawFallbackBackground (cyclomatic 17) · ×1
  • DraedonQuestLogStyle.DrawFallbackBackground (cyclomatic 17) Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:97 — DraedonQuestLogStyle.DrawFallbackBackground 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.
D1 · Cyclomatic Complexity · DraedonQuestLogStyle.DrawNode (cyclomatic 17) · ×1
  • DraedonQuestLogStyle.DrawNode (cyclomatic 17) Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:202 — DraedonQuestLogStyle.DrawNode 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.
D1 · Cyclomatic Complexity · DraedonQuestLogStyle.DrawProgressBar (cyclomatic 17) · ×1
  • DraedonQuestLogStyle.DrawProgressBar (cyclomatic 17) Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:534 — DraedonQuestLogStyle.DrawProgressBar 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.
D1 · Cyclomatic Complexity · ForestQuestLogStyle.DrawNode (cyclomatic 17) · ×1
  • ForestQuestLogStyle.DrawNode (cyclomatic 17) Content/QuestLogs/Styles/ForestQuestLogStyle.cs:176 — ForestQuestLogStyle.DrawNode 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.
D1 · Cyclomatic Complexity · HotwindQuestLogStyle.DrawProgressBar (cyclomatic 17) · ×1
  • HotwindQuestLogStyle.DrawProgressBar (cyclomatic 17) Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:456 — HotwindQuestLogStyle.DrawProgressBar 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.
D1 · Cyclomatic Complexity · AmbientEmitters.EmitCeiling (cyclomatic 17) · ×1
  • AmbientEmitters.EmitCeiling (cyclomatic 17) Content/Scenarios/Dungeonworld/Ambience/AmbientEmitters.cs:317 — AmbientEmitters.EmitCeiling 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.
D1 · Cyclomatic Complexity · GaolRoomNet.Receive (cyclomatic 17) · ×1
  • GaolRoomNet.Receive (cyclomatic 17) Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolRoomNet.cs:70 — GaolRoomNet.Receive 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.
D1 · Cyclomatic Complexity · L1CathedralPrefab.BuildBellTower (cyclomatic 17) · ×1
  • L1CathedralPrefab.BuildBellTower (cyclomatic 17) Content/Scenarios/Dungeonworld/Gen/Layers/L1/L1CathedralPrefab.cs:341 — L1CathedralPrefab.BuildBellTower 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.
D1 · Cyclomatic Complexity · L1Style.LayerScatter (cyclomatic 17) · ×1
  • L1Style.LayerScatter (cyclomatic 17) Content/Scenarios/Dungeonworld/Gen/Layers/L1/L1Style.cs:338 — L1Style.LayerScatter 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.
D1 · Cyclomatic Complexity · L2Content.PlaceAndBuildNode (cyclomatic 17) · ×1
  • L2Content.PlaceAndBuildNode (cyclomatic 17) Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2Content.cs:134 — L2Content.PlaceAndBuildNode 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.
D1 · Cyclomatic Complexity · L5Content.PlanAndBuild (cyclomatic 17) · ×1
  • L5Content.PlanAndBuild (cyclomatic 17) Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Content.cs:61 — L5Content.PlanAndBuild 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.
D1 · Cyclomatic Complexity · SlagVentBelt.PlanAndBuild (cyclomatic 17) · ×1
  • SlagVentBelt.PlanAndBuild (cyclomatic 17) Content/Scenarios/Dungeonworld/Gen/Zones/SlagVentBelt.cs:45 — SlagVentBelt.PlanAndBuild 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.
D1 · Cyclomatic Complexity · DeepGaolWraith.UpdateSwipe (cyclomatic 17) · ×1
  • DeepGaolWraith.UpdateSwipe (cyclomatic 17) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:842 — DeepGaolWraith.UpdateSwipe 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.
D1 · Cyclomatic Complexity · BoneStitcher.DrawBones (cyclomatic 17) · ×1
  • BoneStitcher.DrawBones (cyclomatic 17) Content/Scenarios/Dungeonworld/NPCs/Elites/BoneStitcher.cs:662 — BoneStitcher.DrawBones 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.
D1 · Cyclomatic Complexity · DrownedTurnkey.UpdateLurk (cyclomatic 17) · ×1
  • DrownedTurnkey.UpdateLurk (cyclomatic 17) Content/Scenarios/Dungeonworld/NPCs/Elites/DrownedTurnkey.cs:360 — DrownedTurnkey.UpdateLurk 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.
D1 · Cyclomatic Complexity · GaolAnchorProj.AI (cyclomatic 17) · ×1
  • GaolAnchorProj.AI (cyclomatic 17) Content/Scenarios/Dungeonworld/NPCs/GaolAnchorWeapon.cs:84 — GaolAnchorProj.AI 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.
D1 · Cyclomatic Complexity · GaolCrossChain.AI (cyclomatic 17) · ×1
  • GaolCrossChain.AI (cyclomatic 17) Content/Scenarios/Dungeonworld/NPCs/GaolCrossChain.cs:47 — GaolCrossChain.AI 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.
D1 · Cyclomatic Complexity · KiyumeCrowFlight.StartleFrom (cyclomatic 17) · ×1
  • KiyumeCrowFlight.StartleFrom (cyclomatic 17) Content/Scenarios/Kiyume/Ambience/KiyumeCrowFlight.cs:143 — KiyumeCrowFlight.StartleFrom 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.
D1 · Cyclomatic Complexity · KiyumeHound.UpdateLunge (cyclomatic 17) · ×1
  • KiyumeHound.UpdateLunge (cyclomatic 17) Content/Scenarios/Kiyume/NPCs/KiyumeHound.cs:569 — KiyumeHound.UpdateLunge 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.
D1 · Cyclomatic Complexity · Z2Content.BuildSealBox (cyclomatic 17) · ×1
  • Z2Content.BuildSealBox (cyclomatic 17) Content/Scenarios/OldNet/Gen/Zones/Z2/Z2Content.cs:88 — Z2Content.BuildSealBox 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.
D1 · Cyclomatic Complexity · OldNetThreatField.TickMines (cyclomatic 17) · ×1
  • OldNetThreatField.TickMines (cyclomatic 17) Content/Scenarios/OldNet/NPCs/OldNetThreatField.cs:281 — OldNetThreatField.TickMines 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.
D1 · Cyclomatic Complexity · OldNetTurretICE.AI (cyclomatic 17) · ×1
  • OldNetTurretICE.AI (cyclomatic 17) Content/Scenarios/OldNet/NPCs/OldNetTurretICE.cs:58 — OldNetTurretICE.AI 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.
D1 · Cyclomatic Complexity · OldNetSentryMineTile.PreDraw (cyclomatic 17) · ×1
  • OldNetSentryMineTile.PreDraw (cyclomatic 17) Content/Scenarios/OldNet/Tiles/OldNetSentryMineTile.cs:97 — OldNetSentryMineTile.PreDraw 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.
D1 · Cyclomatic Complexity · CybCourseCardStyle.DrawPanelButton (cyclomatic 17) · ×1
  • CybCourseCardStyle.DrawPanelButton (cyclomatic 17) Content/Scenarios/Shepel/CybCourses/CybCourseCardStyle.cs:220 — CybCourseCardStyle.DrawPanelButton 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.
D1 · Cyclomatic Complexity · SylvanOutpost.EvaluatePositionSimple (cyclomatic 17) · ×1
  • SylvanOutpost.EvaluatePositionSimple (cyclomatic 17) Content/Structures/DatIO/SylvanOutpost.cs:360 — SylvanOutpost.EvaluatePositionSimple 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.
D1 · Cyclomatic Complexity · CrimsonBrideRitePlayer.PreUpdateMovement (cyclomatic 17) · ×1
  • CrimsonBrideRitePlayer.PreUpdateMovement (cyclomatic 17) Content/Wraiths/Abilities/CrimsonBrides/CrimsonBrideRestart.cs:219 — CrimsonBrideRitePlayer.PreUpdateMovement 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.
D1 · Cyclomatic Complexity · GhostRainFx.OnControllerTick (cyclomatic 17) · ×1
  • GhostRainFx.OnControllerTick (cyclomatic 17) Content/Wraiths/Abilities/GhostRains/GhostRainFx.cs:64 — GhostRainFx.OnControllerTick 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.
D1 · Cyclomatic Complexity · ShadeSeizurePerformance.Update (cyclomatic 17) · ×1
  • ShadeSeizurePerformance.Update (cyclomatic 17) Content/Wraiths/Deaths/Performances/ShadeSeizurePerformance.cs:63 — ShadeSeizurePerformance.Update 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.
D1 · Cyclomatic Complexity · WraithNet.RequestEquippedWraith (cyclomatic 17) · ×1
  • WraithNet.RequestEquippedWraith (cyclomatic 17) Content/Wraiths/Runtime/WraithNet.cs:149 — WraithNet.RequestEquippedWraith 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: WraithNet.Receive (cyclomatic 18) 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.
D1 · Cyclomatic Complexity · CWRItem.OverModifyTooltip (cyclomatic 16) · ×1
  • CWRItem.OverModifyTooltip (cyclomatic 16) Content/CWRItem.cs:309 — CWRItem.OverModifyTooltip 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.
D1 · Cyclomatic Complexity · SandevistanPlayer.HandleAuthorityRequest (cyclomatic 16) · ×1
  • SandevistanPlayer.HandleAuthorityRequest (cyclomatic 16) Content/Cyberwares/Implementation/Sandevistans/SandevistanPlayer.cs:182 — SandevistanPlayer.HandleAuthorityRequest 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.
D1 · Cyclomatic Complexity · SandevistanPlayer.UpdateVisuals (cyclomatic 16) · ×1
  • SandevistanPlayer.UpdateVisuals (cyclomatic 16) Content/Cyberwares/Implementation/Sandevistans/SandevistanPlayer.cs:439 — SandevistanPlayer.UpdateVisuals 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.
D1 · Cyclomatic Complexity · CyberwareSkillRadialController.HandleSkillKey (cyclomatic 16) · ×1
  • CyberwareSkillRadialController.HandleSkillKey (cyclomatic 16) Content/Cyberwares/Skills/CyberwareSkillRadialController.cs:214 — CyberwareSkillRadialController.HandleSkillKey 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.
D1 · Cyclomatic Complexity · ChronicleManagerStyle.DrawQuestEntry (cyclomatic 16) · ×1
  • ChronicleManagerStyle.DrawQuestEntry (cyclomatic 16) Content/EntrustManager/Styles/ChronicleManagerStyle.cs:142 — ChronicleManagerStyle.DrawQuestEntry 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.
D1 · Cyclomatic Complexity · AstralveilTideRender.EndEntityDraw (cyclomatic 16) · ×1
  • AstralveilTideRender.EndEntityDraw (cyclomatic 16) Content/GameModes/BrutalMobs/Ambience/Astralveil/AstralveilTideRender.cs:41 — AstralveilTideRender.EndEntityDraw 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.
D1 · Cyclomatic Complexity · DuskhallPlayer.PostUpdate (cyclomatic 16) · ×1
  • DuskhallPlayer.PostUpdate (cyclomatic 16) Content/GameModes/BrutalMobs/Ambience/Duskhall/DuskhallPlayer.cs:66 — DuskhallPlayer.PostUpdate 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.
D1 · Cyclomatic Complexity · FleshfenBloodDew.PostUpdateEverything (cyclomatic 16) · ×1
  • FleshfenBloodDew.PostUpdateEverything (cyclomatic 16) Content/GameModes/BrutalMobs/Ambience/Fleshfen/FleshfenBloodDew.cs:44 — FleshfenBloodDew.PostUpdateEverything 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.
D1 · Cyclomatic Complexity · HollowdeepRockfallProj.AI (cyclomatic 16) · ×1
  • HollowdeepRockfallProj.AI (cyclomatic 16) Content/GameModes/BrutalMobs/Ambience/Hollowdeep/Projectiles/HollowdeepRockfallProj.cs:51 — HollowdeepRockfallProj.AI 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.
D1 · Cyclomatic Complexity · LumindepthAmbientRender.EndEntityDraw (cyclomatic 16) · ×1
  • LumindepthAmbientRender.EndEntityDraw (cyclomatic 16) Content/GameModes/BrutalMobs/Ambience/Lumindepth/LumindepthAmbientRender.cs:199 — LumindepthAmbientRender.EndEntityDraw 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.
D1 · Cyclomatic Complexity · LumindepthVortexProj.PreDraw (cyclomatic 16) · ×1
  • LumindepthVortexProj.PreDraw (cyclomatic 16) Content/GameModes/BrutalMobs/Ambience/Lumindepth/Projectiles/LumindepthVortexProj.cs:177 — LumindepthVortexProj.PreDraw 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.
D1 · Cyclomatic Complexity · MireheartAmbience.TryScanRipples (cyclomatic 16) · ×1
  • MireheartAmbience.TryScanRipples (cyclomatic 16) Content/GameModes/BrutalMobs/Ambience/Mireheart/MireheartAmbience.cs:190 — MireheartAmbience.TryScanRipples 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.
D1 · Cyclomatic Complexity · RainveilThunderboltProj.AI (cyclomatic 16) · ×1
  • RainveilThunderboltProj.AI (cyclomatic 16) Content/GameModes/BrutalMobs/Ambience/Rainveil/Projectiles/RainveilThunderboltProj.cs:71 — RainveilThunderboltProj.AI 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.
D1 · Cyclomatic Complexity · VerdantMireScheduler.PostUpdateEverything (cyclomatic 16) · ×1
  • VerdantMireScheduler.PostUpdateEverything (cyclomatic 16) Content/GameModes/BrutalMobs/Ambience/Verdant/VerdantMireScheduler.cs:29 — VerdantMireScheduler.PostUpdateEverything 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.
D1 · Cyclomatic Complexity · DungeonDeepNPC.TryStartCaster (cyclomatic 16) · ×1
  • DungeonDeepNPC.TryStartCaster (cyclomatic 16) Content/GameModes/BrutalMobs/DungeonDeep/DungeonDeepNPC.Ranged.cs:72 — DungeonDeepNPC.TryStartCaster 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.
D1 · Cyclomatic Complexity · DungeonDeepNPC.TickSkull (cyclomatic 16) · ×1
  • DungeonDeepNPC.TickSkull (cyclomatic 16) Content/GameModes/BrutalMobs/DungeonDeep/DungeonDeepNPC.Ranged.cs:198 — DungeonDeepNPC.TickSkull 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.
D1 · Cyclomatic Complexity · EclManFlyFlaskProj.AI (cyclomatic 16) · ×1
  • EclManFlyFlaskProj.AI (cyclomatic 16) Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclManFlyFlaskProj.cs:57 — EclManFlyFlaskProj.AI 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.
D1 · Cyclomatic Complexity · LegionNPC.SharkStep (cyclomatic 16) · ×1
  • LegionNPC.SharkStep (cyclomatic 16) Content/GameModes/BrutalMobs/Legion/LegionNPC.cs:1153 — LegionNPC.SharkStep 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.
D1 · Cyclomatic Complexity · LegionNPC.ClownStep (cyclomatic 16) · ×1
  • LegionNPC.ClownStep (cyclomatic 16) Content/GameModes/BrutalMobs/Legion/LegionNPC.cs:1205 — LegionNPC.ClownStep 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.
D1 · Cyclomatic Complexity · LegionSurfOmen.AI (cyclomatic 16) · ×1
  • LegionSurfOmen.AI (cyclomatic 16) Content/GameModes/BrutalMobs/Legion/Projectiles/LegionSurfOmen.cs:63 — LegionSurfOmen.AI 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.
D1 · Cyclomatic Complexity · MushroomVineWhipOmen.AI (cyclomatic 16) · ×1
  • MushroomVineWhipOmen.AI (cyclomatic 16) Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomVineWhipOmen.cs:67 — MushroomVineWhipOmen.AI 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.
D1 · Cyclomatic Complexity · NightDiveOmen.AI (cyclomatic 16) · ×1
  • NightDiveOmen.AI (cyclomatic 16) Content/GameModes/BrutalMobs/NightPack/Projectiles/NightDiveOmen.cs:79 — NightDiveOmen.AI 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.
D1 · Cyclomatic Complexity · OceanBrutalNPC.TryStartShark (cyclomatic 16) · ×1
  • OceanBrutalNPC.TryStartShark (cyclomatic 16) Content/GameModes/BrutalMobs/Ocean/OceanBrutalNPC.cs:446 — OceanBrutalNPC.TryStartShark 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.
D1 · Cyclomatic Complexity · SandveilFinSurgeOmen.AI (cyclomatic 16) · ×1
  • SandveilFinSurgeOmen.AI (cyclomatic 16) Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilFinSurgeOmen.cs:87 — SandveilFinSurgeOmen.AI 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.
D1 · Cyclomatic Complexity · StonebornDiveLane.AI (cyclomatic 16) · ×1
  • StonebornDiveLane.AI (cyclomatic 16) Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornDiveLane.cs:62 — StonebornDiveLane.AI 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.
D1 · Cyclomatic Complexity · TempleBrutalNPC.MonkPresent (cyclomatic 16) · ×1
  • TempleBrutalNPC.MonkPresent (cyclomatic 16) Content/GameModes/BrutalMobs/Temple/TempleBrutalNPC.cs:870 — TempleBrutalNPC.MonkPresent 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.
D1 · Cyclomatic Complexity · GsSpookyLanternProj.AI (cyclomatic 16) · ×1
  • GsSpookyLanternProj.AI (cyclomatic 16) Content/GameModes/GodSmith/Armors/Hardmode/GsSpookyWoodArmor.cs:115 — GsSpookyLanternProj.AI 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.
D1 · Cyclomatic Complexity · GsBeeGuardProj.AI (cyclomatic 16) · ×1
  • GsBeeGuardProj.AI (cyclomatic 16) Content/GameModes/GodSmith/Armors/Reset/GsBeeArmor.cs:122 — GsBeeGuardProj.AI 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.
D1 · Cyclomatic Complexity · GsMinisharkHeld.FireOnce (cyclomatic 16) · ×1
  • GsMinisharkHeld.FireOnce (cyclomatic 16) Content/GameModes/GodSmith/Weapons/Guns/GsMinishark.cs:256 — GsMinisharkHeld.FireOnce 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.
D1 · Cyclomatic Complexity · GsConduitHeldProj.OwnerTick (cyclomatic 16) · ×1
  • GsConduitHeldProj.OwnerTick (cyclomatic 16) Content/GameModes/GodSmith/Weapons/MagicConduit/Projectiles/GsConduitHeldProj.cs:126 — GsConduitHeldProj.OwnerTick 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.
D1 · Cyclomatic Complexity · GsNorthPolePillarProj.AI (cyclomatic 16) · ×1
  • GsNorthPolePillarProj.AI (cyclomatic 16) Content/GameModes/GodSmith/Weapons/Spears/GsNorthPole.cs:279 — GsNorthPolePillarProj.AI 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.
D1 · Cyclomatic Complexity · HackTargetFrame.Draw (cyclomatic 16) · ×1
  • HackTargetFrame.Draw (cyclomatic 16) Content/HackTimes/HackTargetFrame.cs:11 — HackTargetFrame.Draw 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.
D1 · Cyclomatic Complexity · HackTimeNetSync.ReadSnapshot (cyclomatic 16) · ×1
  • HackTimeNetSync.ReadSnapshot (cyclomatic 16) Content/HackTimes/HackTimeNetSync.cs:1065 — HackTimeNetSync.ReadSnapshot 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. This is NOT this file's highest cyclomatic complexity: HackTimeNetSync.TryCreateEffectRecord (cyclomatic 21) 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.
D1 · Cyclomatic Complexity · HackTimeTileCyberPass.RenderAndComposite (cyclomatic 16) · ×1
  • HackTimeTileCyberPass.RenderAndComposite (cyclomatic 16) Content/HackTimes/HackTimeTileCyberPass.cs:68 — HackTimeTileCyberPass.RenderAndComposite 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.
D1 · Cyclomatic Complexity · PressureSurge.SlamCeilingHits (cyclomatic 16) · ×1
  • PressureSurge.SlamCeilingHits (cyclomatic 16) Content/HackTimes/Protocols/PressureSurge.cs:138 — PressureSurge.SlamCeilingHits 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.
D1 · Cyclomatic Complexity · TileDetonate.GetVanillaMinPick (cyclomatic 16) · ×1
  • TileDetonate.GetVanillaMinPick (cyclomatic 16) Content/HackTimes/Protocols/TileDetonate.cs:60 — TileDetonate.GetVanillaMinPick 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.
D1 · Cyclomatic Complexity · HackPvPRules.CanTarget (cyclomatic 16) · ×1
  • HackPvPRules.CanTarget (cyclomatic 16) Content/HackTimes/PvP/HackPvPRules.cs:82 — HackPvPRules.CanTarget 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.
D1 · Cyclomatic Complexity · PlayerHackHud.DrawImplantPanel (cyclomatic 16) · ×1
  • PlayerHackHud.DrawImplantPanel (cyclomatic 16) Content/HackTimes/PvP/UI/PlayerHackHud.cs:585 — PlayerHackHud.DrawImplantPanel 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.
D1 · Cyclomatic Complexity · ProjectileScannable.GetOwnerName (cyclomatic 16) · ×1
  • ProjectileScannable.GetOwnerName (cyclomatic 16) Content/HackTimes/Scannables/ProjectileScannable.cs:146 — ProjectileScannable.GetOwnerName 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.
D1 · Cyclomatic Complexity · TileScannable.GetMinPickPower (cyclomatic 16) · ×1
  • TileScannable.GetMinPickPower (cyclomatic 16) Content/HackTimes/Scannables/TileScannable.cs:255 — TileScannable.GetMinPickPower 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. This is NOT this file's highest cyclomatic complexity: TileScannable.IsCraftingStation (cyclomatic 32) 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.
D1 · Cyclomatic Complexity · ApiaryTP.UpdateClientVisual (cyclomatic 16) · ×1
  • ApiaryTP.UpdateClientVisual (cyclomatic 16) Content/Industrials/ElectricPowers/Apiaries/ApiaryTP.cs:470 — ApiaryTP.UpdateClientVisual 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.
D1 · Cyclomatic Complexity · AutoCrafterTile.PreDraw (cyclomatic 16) · ×1
  • AutoCrafterTile.PreDraw (cyclomatic 16) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterTile.cs:88 — AutoCrafterTile.PreDraw 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.
D1 · Cyclomatic Complexity · HerbFarmerTP.TryHarvest (cyclomatic 16) · ×1
  • HerbFarmerTP.TryHarvest (cyclomatic 16) Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerTP.cs:520 — HerbFarmerTP.TryHarvest 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.
D1 · Cyclomatic Complexity · SensorTP.EvaluateCondition (cyclomatic 16) · ×1
  • SensorTP.EvaluateCondition (cyclomatic 16) Content/Industrials/ElectricPowers/Sensors/SensorTP.cs:172 — SensorTP.EvaluateCondition 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.
D1 · Cyclomatic Complexity · SlimeVatTP.UpdateClientVisual (cyclomatic 16) · ×1
  • SlimeVatTP.UpdateClientVisual (cyclomatic 16) Content/Industrials/ElectricPowers/SlimeVats/SlimeVatTP.cs:465 — SlimeVatTP.UpdateClientVisual 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.
D1 · Cyclomatic Complexity · ThrowerUI.HandleButtonClicks (cyclomatic 16) · ×1
  • ThrowerUI.HandleButtonClicks (cyclomatic 16) Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:264 — ThrowerUI.HandleButtonClicks 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. This is NOT this file's highest cyclomatic complexity: ThrowerUI.HandleDragging (cyclomatic 17) 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.
D1 · Cyclomatic Complexity · ThrowerUI.HandleSlotInteraction (cyclomatic 16) · ×1
  • ThrowerUI.HandleSlotInteraction (cyclomatic 16) Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:323 — ThrowerUI.HandleSlotInteraction 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. This is NOT this file's highest cyclomatic complexity: ThrowerUI.HandleDragging (cyclomatic 17) 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.
D1 · Cyclomatic Complexity · FluidPipelineTP.Draw (cyclomatic 16) · ×1
  • FluidPipelineTP.Draw (cyclomatic 16) Content/Industrials/MaterialFlow/Fluids/FluidPipeline.cs:327 — FluidPipelineTP.Draw 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.
D1 · Cyclomatic Complexity · ItemPipelineTP.UpdateOutputMode (cyclomatic 16) · ×1
  • ItemPipelineTP.UpdateOutputMode (cyclomatic 16) Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs:304 — ItemPipelineTP.UpdateOutputMode 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.
D1 · Cyclomatic Complexity · TidalFinPlayer.ProcessTriggers (cyclomatic 16) · ×1
  • TidalFinPlayer.ProcessTriggers (cyclomatic 16) Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFin.cs:108 — TidalFinPlayer.ProcessTriggers 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.
D1 · Cyclomatic Complexity · WingsOfInterferenceRender.DrawBeforePlayers (cyclomatic 16) · ×1
  • WingsOfInterferenceRender.DrawBeforePlayers (cyclomatic 16) Content/Items/Accessories/BrutalRelics/EmpressOfLight/InterferenceWingRender.cs:33 — WingsOfInterferenceRender.DrawBeforePlayers 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.
D1 · Cyclomatic Complexity · BloodfogVeilProj.PreDraw (cyclomatic 16) · ×1
  • BloodfogVeilProj.PreDraw (cyclomatic 16) Content/Items/Accessories/BrutalRelics/EyeOfCthulhu/BloodfogVeilProj.cs:636 — BloodfogVeilProj.PreDraw 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.
D1 · Cyclomatic Complexity · SwarmVortexPlayer.UpdateWax (cyclomatic 16) · ×1
  • SwarmVortexPlayer.UpdateWax (cyclomatic 16) Content/Items/Accessories/BrutalRelics/QueenBee/SwarmVortexPlayer.cs:241 — SwarmVortexPlayer.UpdateWax 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.
D1 · Cyclomatic Complexity · RefractionWaltzCrystalProj.AI (cyclomatic 16) · ×1
  • RefractionWaltzCrystalProj.AI (cyclomatic 16) Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzCrystalProj.cs:92 — RefractionWaltzCrystalProj.AI 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.
D1 · Cyclomatic Complexity · EyeOfSingularityPlayer.OnHitNPCWithProj (cyclomatic 16) · ×1
  • EyeOfSingularityPlayer.OnHitNPCWithProj (cyclomatic 16) Content/Items/Accessories/EyeOfSingularity.cs:519 — EyeOfSingularityPlayer.OnHitNPCWithProj 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.
D1 · Cyclomatic Complexity · JusticeUnveiled.SpwanBool (cyclomatic 16) · ×1
  • JusticeUnveiled.SpwanBool (cyclomatic 16) Content/Items/Accessories/JusticeUnveileds/JusticeUnveiled.cs:34 — JusticeUnveiled.SpwanBool 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.
D1 · Cyclomatic Complexity · ArbiterFireSnake.FindStandableGroundY (cyclomatic 16) · ×1
  • ArbiterFireSnake.FindStandableGroundY (cyclomatic 16) Content/Items/Melee/Arbiters/Arbiter.cs:725 — ArbiterFireSnake.FindStandableGroundY 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.
D1 · Cyclomatic Complexity · ArbiterManifestationActor.UpdateLocalInteraction (cyclomatic 16) · ×1
  • ArbiterManifestationActor.UpdateLocalInteraction (cyclomatic 16) Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:639 — ArbiterManifestationActor.UpdateLocalInteraction 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.
D1 · Cyclomatic Complexity · ArbiterManifestationNet.Receive (cyclomatic 16) · ×1
  • ArbiterManifestationNet.Receive (cyclomatic 16) Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs:136 — ArbiterManifestationNet.Receive 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.
D1 · Cyclomatic Complexity · DestroyerEXPlayer.PostUpdateMiscEffects (cyclomatic 16) · ×1
  • DestroyerEXPlayer.PostUpdateMiscEffects (cyclomatic 16) Content/Items/Melee/DestroyersBladeEXs/DestroyerEXPlayer.cs:84 — DestroyerEXPlayer.PostUpdateMiscEffects 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.
D1 · Cyclomatic Complexity · EnergySwordHeld.AI (cyclomatic 16) · ×1
  • EnergySwordHeld.AI (cyclomatic 16) Content/Items/Melee/EnergySword.cs:222 — EnergySwordHeld.AI 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.
D1 · Cyclomatic Complexity · NeutronGlaiveHeldAlt.AI (cyclomatic 16) · ×1
  • NeutronGlaiveHeldAlt.AI (cyclomatic 16) Content/Items/Melee/NeutronGlaive.cs:1126 — NeutronGlaiveHeldAlt.AI 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.
D1 · Cyclomatic Complexity · ShatterfangHeld.HandleParticles (cyclomatic 16) · ×1
  • ShatterfangHeld.HandleParticles (cyclomatic 16) Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:520 — ShatterfangHeld.HandleParticles 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.
D1 · Cyclomatic Complexity · LonginusVFX.DrawHelixTrail (cyclomatic 16) · ×1
  • LonginusVFX.DrawHelixTrail (cyclomatic 16) Content/Items/Melee/SpearOfLonginuses/LonginusAssets.cs:296 — LonginusVFX.DrawHelixTrail 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.
D1 · Cyclomatic Complexity · AncientStormArc.AI (cyclomatic 16) · ×1
  • AncientStormArc.AI (cyclomatic 16) Content/Items/Melee/StormGoddessSpears/AncientStormGoddessSpear.cs:358 — AncientStormArc.AI 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.
D1 · Cyclomatic Complexity · StormGoddess.UpdateFacingDirection (cyclomatic 16) · ×1
  • StormGoddess.UpdateFacingDirection (cyclomatic 16) Content/Items/Melee/StormGoddessSpears/StormGoddess.cs:457 — StormGoddess.UpdateFacingDirection 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.
D1 · Cyclomatic Complexity · WGManifestationActor.UpdateLocalInteraction (cyclomatic 16) · ×1
  • WGManifestationActor.UpdateLocalInteraction (cyclomatic 16) Content/Items/Melee/WeaverGrievanceses/WGManifestationActor.cs:534 — WGManifestationActor.UpdateLocalInteraction 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.
D1 · Cyclomatic Complexity · WGManifestationNet.Receive (cyclomatic 16) · ×1
  • WGManifestationNet.Receive (cyclomatic 16) Content/Items/Melee/WeaverGrievanceses/WGManifestationNet.cs:137 — WGManifestationNet.Receive 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.
D1 · Cyclomatic Complexity · WeaverBeam.AI (cyclomatic 16) · ×1
  • WeaverBeam.AI (cyclomatic 16) Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:880 — WeaverBeam.AI 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.
D1 · Cyclomatic Complexity · BloodButchererHeld.HandlePhaseEvents (cyclomatic 16) · ×1
  • BloodButchererHeld.HandlePhaseEvents (cyclomatic 16) Content/Items/Modifys/RBloodButcherer.cs:406 — BloodButchererHeld.HandlePhaseEvents 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.
D1 · Cyclomatic Complexity · BloodButchererHeld.HandleParticles (cyclomatic 16) · ×1
  • BloodButchererHeld.HandleParticles (cyclomatic 16) Content/Items/Modifys/RBloodButcherer.cs:459 — BloodButchererHeld.HandleParticles 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.
D1 · Cyclomatic Complexity · DarkFrostSolsticeHeld.Fire (cyclomatic 16) · ×1
  • DarkFrostSolsticeHeld.Fire (cyclomatic 16) Content/Items/Ranged/DarkFrostSolstice.cs:160 — DarkFrostSolsticeHeld.Fire 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.
D1 · Cyclomatic Complexity · DeepclawSnapBurst.AI (cyclomatic 16) · ×1
  • DeepclawSnapBurst.AI (cyclomatic 16) Content/Items/Summon/Deepclaws/DeepclawLobster.cs:518 — DeepclawSnapBurst.AI 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.
D1 · Cyclomatic Complexity · BatSwarmMinion.AI (cyclomatic 16) · ×1
  • BatSwarmMinion.AI (cyclomatic 16) Content/LegendWeapon/HalibutLegend/FishSkills/FishBat.cs:451 — BatSwarmMinion.AI 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.
D1 · Cyclomatic Complexity · BrimfishSpitterProjectile.AI (cyclomatic 16) · ×1
  • BrimfishSpitterProjectile.AI (cyclomatic 16) Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:147 — BrimfishSpitterProjectile.AI 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.
D1 · Cyclomatic Complexity · KikasaDiveClearing.Update (cyclomatic 16) · ×1
  • KikasaDiveClearing.Update (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDiveClearing.cs:100 — KikasaDiveClearing.Update 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.
D1 · Cyclomatic Complexity · KikasaDomainNet.Receive (cyclomatic 16) · ×1
  • KikasaDomainNet.Receive (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainNet.cs:39 — KikasaDomainNet.Receive 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.
D1 · Cyclomatic Complexity · KikasaDomainRender.DrawNPCsOverTiles (cyclomatic 16) · ×1
  • KikasaDomainRender.DrawNPCsOverTiles (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainRender.cs:40 — KikasaDomainRender.DrawNPCsOverTiles 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.
D1 · Cyclomatic Complexity · KikasaLakeNPC.SurfaceFx (cyclomatic 16) · ×1
  • KikasaLakeNPC.SurfaceFx (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaLakeNPC.cs:140 — KikasaLakeNPC.SurfaceFx 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.
D1 · Cyclomatic Complexity · KikasaDrownFX.DrawGhostLayer (cyclomatic 16) · ×1
  • KikasaDrownFX.DrawGhostLayer (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1076 — KikasaDrownFX.DrawGhostLayer 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.
D1 · Cyclomatic Complexity · KikasaPlayerDrownFX.UpdateHands (cyclomatic 16) · ×1
  • KikasaPlayerDrownFX.UpdateHands (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaPlayerDrownFX.cs:313 — KikasaPlayerDrownFX.UpdateHands 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.
D1 · Cyclomatic Complexity · KikasaRainUmbrella.UpdateAutoRain (cyclomatic 16) · ×1
  • KikasaRainUmbrella.UpdateAutoRain (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:868 — KikasaRainUmbrella.UpdateAutoRain 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.
D1 · Cyclomatic Complexity · KikasaResetHistory.Update (cyclomatic 16) · ×1
  • KikasaResetHistory.Update (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetHistory.cs:100 — KikasaResetHistory.Update 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.
D1 · Cyclomatic Complexity · KikasaResetRender.EndCaptureDraw (cyclomatic 16) · ×1
  • KikasaResetRender.EndCaptureDraw (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs:38 — KikasaResetRender.EndCaptureDraw 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.
D1 · Cyclomatic Complexity · KikasaBladeServant.UpdateDissolve (cyclomatic 16) · ×1
  • KikasaBladeServant.UpdateDissolve (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:696 — KikasaBladeServant.UpdateDissolve 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.
D1 · Cyclomatic Complexity · KikasaBoomerangServant.UpdateDissolve (cyclomatic 16) · ×1
  • KikasaBoomerangServant.UpdateDissolve (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:594 — KikasaBoomerangServant.UpdateDissolve 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.
D1 · Cyclomatic Complexity · KikasaBowServant.UpdateDissolve (cyclomatic 16) · ×1
  • KikasaBowServant.UpdateDissolve (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:773 — KikasaBowServant.UpdateDissolve 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.
D1 · Cyclomatic Complexity · KikasaFlailHead.AI (cyclomatic 16) · ×1
  • KikasaFlailHead.AI (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailHead.cs:73 — KikasaFlailHead.AI 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.
D1 · Cyclomatic Complexity · KikasaFlailServant.UpdateDissolve (cyclomatic 16) · ×1
  • KikasaFlailServant.UpdateDissolve (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:600 — KikasaFlailServant.UpdateDissolve 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.
D1 · Cyclomatic Complexity · KikasaGunServant.UpdateCarousel (cyclomatic 16) · ×1
  • KikasaGunServant.UpdateCarousel (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:680 — KikasaGunServant.UpdateCarousel 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.
D1 · Cyclomatic Complexity · KikasaGunServant.UpdateDissolve (cyclomatic 16) · ×1
  • KikasaGunServant.UpdateDissolve (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:943 — KikasaGunServant.UpdateDissolve 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.
D1 · Cyclomatic Complexity · KikasaHalibutDomain.UpdatePressure (cyclomatic 16) · ×1
  • KikasaHalibutDomain.UpdatePressure (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutDomain.cs:149 — KikasaHalibutDomain.UpdatePressure 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.
D1 · Cyclomatic Complexity · KikasaOnikiriServant.AI (cyclomatic 16) · ×1
  • KikasaOnikiriServant.AI (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:266 — KikasaOnikiriServant.AI 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.
D1 · Cyclomatic Complexity · KikasaRodServant.UpdateRod (cyclomatic 16) · ×1
  • KikasaRodServant.UpdateRod (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:577 — KikasaRodServant.UpdateRod 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.
D1 · Cyclomatic Complexity · KikasaSpearServant.UpdateDissolve (cyclomatic 16) · ×1
  • KikasaSpearServant.UpdateDissolve (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:573 — KikasaSpearServant.UpdateDissolve 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.
D1 · Cyclomatic Complexity · KikasaThrowServant.UpdateDissolve (cyclomatic 16) · ×1
  • KikasaThrowServant.UpdateDissolve (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:556 — KikasaThrowServant.UpdateDissolve 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.
D1 · Cyclomatic Complexity · KikasaWhipServant.AI (cyclomatic 16) · ×1
  • KikasaWhipServant.AI (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:229 — KikasaWhipServant.AI 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.
D1 · Cyclomatic Complexity · KikasaWhipServant.UpdateDissolve (cyclomatic 16) · ×1
  • KikasaWhipServant.UpdateDissolve (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:556 — KikasaWhipServant.UpdateDissolve 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.
D1 · Cyclomatic Complexity · KikasaYoyoServant.UpdateDissolve (cyclomatic 16) · ×1
  • KikasaYoyoServant.UpdateDissolve (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:589 — KikasaYoyoServant.UpdateDissolve 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.
D1 · Cyclomatic Complexity · KikasaCultistFireOrb.AI (cyclomatic 16) · ×1
  • KikasaCultistFireOrb.AI (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistFireOrb.cs:64 — KikasaCultistFireOrb.AI 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.
D1 · Cyclomatic Complexity · KikasaCultistServant.UpdateDissolve (cyclomatic 16) · ×1
  • KikasaCultistServant.UpdateDissolve (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:805 — KikasaCultistServant.UpdateDissolve 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.
D1 · Cyclomatic Complexity · KikasaCultistServant.DrawPoseGlow (cyclomatic 16) · ×1
  • KikasaCultistServant.DrawPoseGlow (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:1173 — KikasaCultistServant.DrawPoseGlow 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.
D1 · Cyclomatic Complexity · KikasaDeerclopsServant.BodyScaleVec (cyclomatic 16) · ×1
  • KikasaDeerclopsServant.BodyScaleVec (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:1148 — KikasaDeerclopsServant.BodyScaleVec 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.
D1 · Cyclomatic Complexity · KikasaEaterServant.UpdateSeam (cyclomatic 16) · ×1
  • KikasaEaterServant.UpdateSeam (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:480 — KikasaEaterServant.UpdateSeam 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.
D1 · Cyclomatic Complexity · KikasaEmpressServant.AI (cyclomatic 16) · ×1
  • KikasaEmpressServant.AI (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:184 — KikasaEmpressServant.AI 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.
D1 · Cyclomatic Complexity · KikasaEmpressServant.UpdateLanceRain (cyclomatic 16) · ×1
  • KikasaEmpressServant.UpdateLanceRain (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:545 — KikasaEmpressServant.UpdateLanceRain 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.
D1 · Cyclomatic Complexity · KikasaEyeServant.UpdateVolley (cyclomatic 16) · ×1
  • KikasaEyeServant.UpdateVolley (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:518 — KikasaEyeServant.UpdateVolley 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.
D1 · Cyclomatic Complexity · KikasaFesterSerpentServant.AI (cyclomatic 16) · ×1
  • KikasaFesterSerpentServant.AI (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:220 — KikasaFesterSerpentServant.AI 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.
D1 · Cyclomatic Complexity · KikasaFishronServant.DrawGlow (cyclomatic 16) · ×1
  • KikasaFishronServant.DrawGlow (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1303 — KikasaFishronServant.DrawGlow 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.
D1 · Cyclomatic Complexity · KikasaBloodSurgeWave.AI (cyclomatic 16) · ×1
  • KikasaBloodSurgeWave.AI (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaBloodSurgeWave.cs:73 — KikasaBloodSurgeWave.AI 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.
D1 · Cyclomatic Complexity · KikasaKingSlimeServant.AI (cyclomatic 16) · ×1
  • KikasaKingSlimeServant.AI (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:226 — KikasaKingSlimeServant.AI 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.
D1 · Cyclomatic Complexity · KikasaMoonRay.AI (cyclomatic 16) · ×1
  • KikasaMoonRay.AI (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs:100 — KikasaMoonRay.AI 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.
D1 · Cyclomatic Complexity · KikasaPrimeMortar.AI (cyclomatic 16) · ×1
  • KikasaPrimeMortar.AI (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeMortar.cs:79 — KikasaPrimeMortar.AI 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.
D1 · Cyclomatic Complexity · KikasaQueenGelMine.UpdateCrystal (cyclomatic 16) · ×1
  • KikasaQueenGelMine.UpdateCrystal (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenGelMine.cs:173 — KikasaQueenGelMine.UpdateCrystal 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.
D1 · Cyclomatic Complexity · KikasaQueenSlimeServant.UpdateFrames (cyclomatic 16) · ×1
  • KikasaQueenSlimeServant.UpdateFrames (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:1009 — KikasaQueenSlimeServant.UpdateFrames 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.
D1 · Cyclomatic Complexity · KikasaQueenSlimeServant.DrawCoreAndAccents (cyclomatic 16) · ×1
  • KikasaQueenSlimeServant.DrawCoreAndAccents (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:1504 — KikasaQueenSlimeServant.DrawCoreAndAccents 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.
D1 · Cyclomatic Complexity · KikasaTwinsServant.UpdatePulse (cyclomatic 16) · ×1
  • KikasaTwinsServant.UpdatePulse (cyclomatic 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:663 — KikasaTwinsServant.UpdatePulse 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.
D1 · Cyclomatic Complexity · KikasaServantWheelController.HandleWheelMouse (cyclomatic 16) · ×1
  • KikasaServantWheelController.HandleWheelMouse (cyclomatic 16) Content/LegendWeapon/KikasaLegend/UI/ServantWheel/KikasaServantWheelController.cs:167 — KikasaServantWheelController.HandleWheelMouse 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.
D1 · Cyclomatic Complexity · KikasaServantWheelUI.DrawInfoPanelForHovered (cyclomatic 16) · ×1
  • KikasaServantWheelUI.DrawInfoPanelForHovered (cyclomatic 16) Content/LegendWeapon/KikasaLegend/UI/ServantWheel/KikasaServantWheelUI.cs:352 — KikasaServantWheelUI.DrawInfoPanelForHovered 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.
D1 · Cyclomatic Complexity · KikasaServantWheelUI.DrawInfoPanel (cyclomatic 16) · ×1
  • KikasaServantWheelUI.DrawInfoPanel (cyclomatic 16) Content/LegendWeapon/KikasaLegend/UI/ServantWheel/KikasaServantWheelUI.cs:426 — KikasaServantWheelUI.DrawInfoPanel 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.
D1 · Cyclomatic Complexity · CrimsonSweepSlash.OnHitNPC (cyclomatic 16) · ×1
  • CrimsonSweepSlash.OnHitNPC (cyclomatic 16) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1211 — CrimsonSweepSlash.OnHitNPC 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.
D1 · Cyclomatic Complexity · OniMeiCombat.OnExecuteStrikeHit (cyclomatic 16) · ×1
  • OniMeiCombat.OnExecuteStrikeHit (cyclomatic 16) Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiCombat.cs:623 — OniMeiCombat.OnExecuteStrikeHit 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. This is NOT this file's highest cyclomatic complexity: OniMeiCombat.IsExplicitNonHeadSegment (cyclomatic 38) 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.
D1 · Cyclomatic Complexity · OniPlayerDismemberRender.DrawNPCsOverTiles (cyclomatic 16) · ×1
  • OniPlayerDismemberRender.DrawNPCsOverTiles (cyclomatic 16) Content/LegendWeapon/OnikiriLegend/OniDismembers/OniPlayerDismember.cs:402 — OniPlayerDismemberRender.DrawNPCsOverTiles 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.
D1 · Cyclomatic Complexity · OniDomainDeco.UpdateLanterns (cyclomatic 16) · ×1
  • OniDomainDeco.UpdateLanterns (cyclomatic 16) Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainDeco.cs:328 — OniDomainDeco.UpdateLanterns 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.
D1 · Cyclomatic Complexity · OniDomainPlayer.UpdateClosing (cyclomatic 16) · ×1
  • OniDomainPlayer.UpdateClosing (cyclomatic 16) Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainPlayer.cs:648 — OniDomainPlayer.UpdateClosing 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.
D1 · Cyclomatic Complexity · OniDomainRender.ApplyUnifyAndPeel (cyclomatic 16) · ×1
  • OniDomainRender.ApplyUnifyAndPeel (cyclomatic 16) Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainRender.cs:160 — OniDomainRender.ApplyUnifyAndPeel 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.
D1 · Cyclomatic Complexity · OniFinaleLattice.DrawLines (cyclomatic 16) · ×1
  • OniFinaleLattice.DrawLines (cyclomatic 16) Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleLattice.cs:141 — OniFinaleLattice.DrawLines 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.
D1 · Cyclomatic Complexity · OniFlashStep.ResolveExecutionTargetAndTryFinale (cyclomatic 16) · ×1
  • OniFlashStep.ResolveExecutionTargetAndTryFinale (cyclomatic 16) Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashStep.cs:699 — OniFlashStep.ResolveExecutionTargetAndTryFinale 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.
D1 · Cyclomatic Complexity · OniOmokageRender.DrawThreadsAndPulses (cyclomatic 16) · ×1
  • OniOmokageRender.DrawThreadsAndPulses (cyclomatic 16) Content/LegendWeapon/OnikiriLegend/OniOmokages/OniOmokageRender.cs:580 — OniOmokageRender.DrawThreadsAndPulses 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.
D1 · Cyclomatic Complexity · SakuraFinaleFeedback.DrawBlur (cyclomatic 16) · ×1
  • SakuraFinaleFeedback.DrawBlur (cyclomatic 16) Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraFinaleFeedback.cs:140 — SakuraFinaleFeedback.DrawBlur 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.
D1 · Cyclomatic Complexity · OnikiriTutorialPlayer.TickTutorial (cyclomatic 16) · ×1
  • OnikiriTutorialPlayer.TickTutorial (cyclomatic 16) Content/LegendWeapon/OnikiriLegend/Tutorial/OnikiriTutorialPlayer.cs:105 — OnikiriTutorialPlayer.TickTutorial 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.
D1 · Cyclomatic Complexity · OnikiriTutorialPlayer.HandleUnboundFallbackInput (cyclomatic 16) · ×1
  • OnikiriTutorialPlayer.HandleUnboundFallbackInput (cyclomatic 16) Content/LegendWeapon/OnikiriLegend/Tutorial/OnikiriTutorialPlayer.cs:1004 — OnikiriTutorialPlayer.HandleUnboundFallbackInput 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.
D1 · Cyclomatic Complexity · OniMeiGlyph.DrawStroke (cyclomatic 16) · ×1
  • OniMeiGlyph.DrawStroke (cyclomatic 16) Content/LegendWeapon/OnikiriLegend/UI/OniMeiGlyph.cs:484 — OniMeiGlyph.DrawStroke 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.
D1 · Cyclomatic Complexity · CyberBanish.ReadSnapshot (cyclomatic 16) · ×1
  • CyberBanish.ReadSnapshot (cyclomatic 16) Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBanish.Net.cs:240 — CyberBanish.ReadSnapshot 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.
D1 · Cyclomatic Complexity · CyberspaceActionNet.HandleRequest (cyclomatic 16) · ×1
  • CyberspaceActionNet.HandleRequest (cyclomatic 16) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspaceActionNet.cs:123 — CyberspaceActionNet.HandleRequest 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.
D1 · Cyclomatic Complexity · CyberspacePlayer.UpdateRemoteVisuals (cyclomatic 16) · ×1
  • CyberspacePlayer.UpdateRemoteVisuals (cyclomatic 16) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspacePlayer.cs:761 — CyberspacePlayer.UpdateRemoteVisuals 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.
D1 · Cyclomatic Complexity · CyberRestart.Update (cyclomatic 16) · ×1
  • CyberRestart.Update (cyclomatic 16) Content/LegendWeapon/SHPCLegend/Cyberspaces/Restart/CyberRestart.cs:159 — CyberRestart.Update 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.
D1 · Cyclomatic Complexity · CyberTeleport.ExecuteAuthority (cyclomatic 16) · ×1
  • CyberTeleport.ExecuteAuthority (cyclomatic 16) Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberTeleport.cs:109 — CyberTeleport.ExecuteAuthority 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.
D1 · Cyclomatic Complexity · QuantumFrameModule.OnPlayerUpdate (cyclomatic 16) · ×1
  • QuantumFrameModule.OnPlayerUpdate (cyclomatic 16) Content/LegendWeapon/SHPCLegend/Modules/Frame/QuantumFrameModule.cs:110 — QuantumFrameModule.OnPlayerUpdate 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.
D1 · Cyclomatic Complexity · SHPCCapacitorBankProj.ResolveOrb (cyclomatic 16) · ×1
  • SHPCCapacitorBankProj.ResolveOrb (cyclomatic 16) Content/LegendWeapon/SHPCLegend/Modules/Power/CapacitorBankModule.cs:255 — SHPCCapacitorBankProj.ResolveOrb 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.
D1 · Cyclomatic Complexity · OverloadCoreModule.OnOrbCharging (cyclomatic 16) · ×1
  • OverloadCoreModule.OnOrbCharging (cyclomatic 16) Content/LegendWeapon/SHPCLegend/Modules/Power/OverloadCoreModule.cs:38 — OverloadCoreModule.OnOrbCharging 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.
D1 · Cyclomatic Complexity · BraceStockModule.OnPlayerUpdate (cyclomatic 16) · ×1
  • BraceStockModule.OnPlayerUpdate (cyclomatic 16) Content/LegendWeapon/SHPCLegend/Modules/Stock/BraceStockModule.cs:77 — BraceStockModule.OnPlayerUpdate 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.
D1 · Cyclomatic Complexity · MoldCodexPanel.DrawCustomTooltip (cyclomatic 16) · ×1
  • MoldCodexPanel.DrawCustomTooltip (cyclomatic 16) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:316 — MoldCodexPanel.DrawCustomTooltip 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.
D1 · Cyclomatic Complexity · MoldProcessingPanel.HandleClick (cyclomatic 16) · ×1
  • MoldProcessingPanel.HandleClick (cyclomatic 16) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingPanel.cs:100 — MoldProcessingPanel.HandleClick 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.
D1 · Cyclomatic Complexity · SHPCDomainWheelController.HandleWheelMouse (cyclomatic 16) · ×1
  • SHPCDomainWheelController.HandleWheelMouse (cyclomatic 16) Content/LegendWeapon/SHPCLegend/UI/DomainWheel/SHPCDomainWheelController.cs:144 — SHPCDomainWheelController.HandleWheelMouse 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.
D1 · Cyclomatic Complexity · DeerclopsMotion.ApplyVertical (cyclomatic 16) · ×1
  • DeerclopsMotion.ApplyVertical (cyclomatic 16) Content/NPCs/BrutalNPCs/BrutalDeerclops/Core/DeerclopsMotion.cs:71 — DeerclopsMotion.ApplyVertical 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.
D1 · Cyclomatic Complexity · DeerclopsMotion.FindSpikeY (cyclomatic 16) · ×1
  • DeerclopsMotion.FindSpikeY (cyclomatic 16) Content/NPCs/BrutalNPCs/BrutalDeerclops/Core/DeerclopsMotion.cs:136 — DeerclopsMotion.FindSpikeY 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.
D1 · Cyclomatic Complexity · DeerclopsAI.UpdateShadowShield (cyclomatic 16) · ×1
  • DeerclopsAI.UpdateShadowShield (cyclomatic 16) Content/NPCs/BrutalNPCs/BrutalDeerclops/DeerclopsAI.cs:200 — DeerclopsAI.UpdateShadowShield 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.
D1 · Cyclomatic Complexity · DestroyerBodyAI.AI (cyclomatic 16) · ×1
  • DestroyerBodyAI.AI (cyclomatic 16) Content/NPCs/BrutalNPCs/BrutalDestroyer/DestroyerBodyAI.cs:105 — DestroyerBodyAI.AI 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.
D1 · Cyclomatic Complexity · DestroyerMawBeamProj.AI (cyclomatic 16) · ×1
  • DestroyerMawBeamProj.AI (cyclomatic 16) Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:81 — DestroyerMawBeamProj.AI 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.
D1 · Cyclomatic Complexity · DestroyerCoilCrushState.OnUpdate (cyclomatic 16) · ×1
  • DestroyerCoilCrushState.OnUpdate (cyclomatic 16) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerCoilCrushState.cs:74 — DestroyerCoilCrushState.OnUpdate 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.
D1 · Cyclomatic Complexity · DestroyerCoilLockState.OnUpdate (cyclomatic 16) · ×1
  • DestroyerCoilLockState.OnUpdate (cyclomatic 16) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerCoilLockState.cs:94 — DestroyerCoilLockState.OnUpdate 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.
D1 · Cyclomatic Complexity · DestroyerLoopLashState.OnUpdate (cyclomatic 16) · ×1
  • DestroyerLoopLashState.OnUpdate (cyclomatic 16) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerLoopLashState.cs:47 — DestroyerLoopLashState.OnUpdate 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.
D1 · Cyclomatic Complexity · FishronPhaseThreeTransitionState.OnUpdate (cyclomatic 16) · ×1
  • FishronPhaseThreeTransitionState.OnUpdate (cyclomatic 16) Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronPhaseTransitionStates.cs:139 — FishronPhaseThreeTransitionState.OnUpdate 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.
D1 · Cyclomatic Complexity · EmpressGrabPerformancePlayer.PostUpdate (cyclomatic 16) · ×1
  • EmpressGrabPerformancePlayer.PostUpdate (cyclomatic 16) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/EmpressGrabCutscene.cs:114 — EmpressGrabPerformancePlayer.PostUpdate 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.
D1 · Cyclomatic Complexity · GolemFistAI.UpdateThrusterVisual (cyclomatic 16) · ×1
  • GolemFistAI.UpdateThrusterVisual (cyclomatic 16) Content/NPCs/BrutalNPCs/BrutalGolem/GolemFistAI.cs:122 — GolemFistAI.UpdateThrusterVisual 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.
D1 · Cyclomatic Complexity · GolemFreeHeadAI.UpdateMovement (cyclomatic 16) · ×1
  • GolemFreeHeadAI.UpdateMovement (cyclomatic 16) Content/NPCs/BrutalNPCs/BrutalGolem/GolemFreeHeadAI.cs:99 — GolemFreeHeadAI.UpdateMovement 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.
D1 · Cyclomatic Complexity · GolemTrapUnit.DrawBlockGlow (cyclomatic 16) · ×1
  • GolemTrapUnit.DrawBlockGlow (cyclomatic 16) Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemTrapUnit.cs:507 — GolemTrapUnit.DrawBlockGlow 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.
D1 · Cyclomatic Complexity · GolemStompComboState.OnLand (cyclomatic 16) · ×1
  • GolemStompComboState.OnLand (cyclomatic 16) Content/NPCs/BrutalNPCs/BrutalGolem/States/GolemStompComboState.cs:108 — GolemStompComboState.OnLand 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.
D1 · Cyclomatic Complexity · CultistOrbitPath.PreDraw (cyclomatic 16) · ×1
  • CultistOrbitPath.PreDraw (cyclomatic 16) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistOrbitPath.cs:231 — CultistOrbitPath.PreDraw 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.
D1 · Cyclomatic Complexity · CultistCometVolleyState.OnUpdate (cyclomatic 16) · ×1
  • CultistCometVolleyState.OnUpdate (cyclomatic 16) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistCometVolleyState.cs:39 — CultistCometVolleyState.OnUpdate 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.
D1 · Cyclomatic Complexity · CultistDeathState.OnUpdate (cyclomatic 16) · ×1
  • CultistDeathState.OnUpdate (cyclomatic 16) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistDeathState.cs:30 — CultistDeathState.OnUpdate 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.
D1 · Cyclomatic Complexity · CultistRingPrisonState.OnUpdate (cyclomatic 16) · ×1
  • CultistRingPrisonState.OnUpdate (cyclomatic 16) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistRingPrisonState.cs:25 — CultistRingPrisonState.OnUpdate 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.
D1 · Cyclomatic Complexity · TwinsPhaseTransitionState.ExecuteContractPhase (cyclomatic 16) · ×1
  • TwinsPhaseTransitionState.ExecuteContractPhase (cyclomatic 16) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsPhaseTransitionState.cs:178 — TwinsPhaseTransitionState.ExecuteContractPhase 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.
D1 · Cyclomatic Complexity · SpazmatismSoloRageState.ExecuteHomingDash (cyclomatic 16) · ×1
  • SpazmatismSoloRageState.ExecuteHomingDash (cyclomatic 16) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismSoloRageState.cs:361 — SpazmatismSoloRageState.ExecuteHomingDash 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.
D1 · Cyclomatic Complexity · MLordCoreExposureState.OnUpdate (cyclomatic 16) · ×1
  • MLordCoreExposureState.OnUpdate (cyclomatic 16) Content/NPCs/BrutalNPCs/BrutalMoonLord/States/MLordCoreExposureState.cs:52 — MLordCoreExposureState.OnUpdate 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.
D1 · Cyclomatic Complexity · MLordTidalPalmsState.OnUpdate (cyclomatic 16) · ×1
  • MLordTidalPalmsState.OnUpdate (cyclomatic 16) Content/NPCs/BrutalNPCs/BrutalMoonLord/States/MLordTidalPalmsState.cs:58 — MLordTidalPalmsState.OnUpdate 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.
D1 · Cyclomatic Complexity · SwarmDirector.GetEdgeHighlight (cyclomatic 16) · ×1
  • SwarmDirector.GetEdgeHighlight (cyclomatic 16) Content/NPCs/BrutalNPCs/BrutalQueenBee/Core/SwarmDirector.cs:462 — SwarmDirector.GetEdgeHighlight 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.
D1 · Cyclomatic Complexity · QueenSkySpikeCascadeState.OnUpdate (cyclomatic 16) · ×1
  • QueenSkySpikeCascadeState.OnUpdate (cyclomatic 16) Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenSkySpikeCascadeState.cs:51 — QueenSkySpikeCascadeState.OnUpdate 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.
D1 · Cyclomatic Complexity · WofGrabTongueProj.PreDraw (cyclomatic 16) · ×1
  • WofGrabTongueProj.PreDraw (cyclomatic 16) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofGrabTongueProj.cs:181 — WofGrabTongueProj.PreDraw 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.
D1 · Cyclomatic Complexity · WofDeathState.OnUpdate (cyclomatic 16) · ×1
  • WofDeathState.OnUpdate (cyclomatic 16) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/States/WofDeathState.cs:42 — WofDeathState.OnUpdate 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.
D1 · Cyclomatic Complexity · NPCTalkUIBase.Update (cyclomatic 16) · ×1
  • NPCTalkUIBase.Update (cyclomatic 16) Content/NPCs/CommonUIs/NPCTalkUIBase.cs:129 — NPCTalkUIBase.Update 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.
D1 · Cyclomatic Complexity · FssSkinFX.DrawSegmentCore (cyclomatic 16) · ×1
  • FssSkinFX.DrawSegmentCore (cyclomatic 16) Content/NPCs/FestersandSerpents/Rendering/FssSkinFX.cs:335 — FssSkinFX.DrawSegmentCore 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.
D1 · Cyclomatic Complexity · FssIchorSpitState.OnUpdate (cyclomatic 16) · ×1
  • FssIchorSpitState.OnUpdate (cyclomatic 16) Content/NPCs/FestersandSerpents/States/FssIchorSpitState.cs:26 — FssIchorSpitState.OnUpdate 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.
D1 · Cyclomatic Complexity · ScrapViceSnatchState.OnUpdate (cyclomatic 16) · ×1
  • ScrapViceSnatchState.OnUpdate (cyclomatic 16) Content/NPCs/ScrapCommanders/States/ScrapViceSnatchState.cs:36 — ScrapViceSnatchState.OnUpdate 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.
D1 · Cyclomatic Complexity · ScrapWaterfallState.OnUpdate (cyclomatic 16) · ×1
  • ScrapWaterfallState.OnUpdate (cyclomatic 16) Content/NPCs/ScrapCommanders/States/ScrapWaterfallState.cs:35 — ScrapWaterfallState.OnUpdate 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.
D1 · Cyclomatic Complexity · SeaShrimpPlowChargeState.OnUpdate (cyclomatic 16) · ×1
  • SeaShrimpPlowChargeState.OnUpdate (cyclomatic 16) Content/NPCs/SeaShrimp/States/SeaShrimpPlowChargeState.cs:31 — SeaShrimpPlowChargeState.OnUpdate 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.
D1 · Cyclomatic Complexity · PRT_KikasaInkSpray.AI (cyclomatic 16) · ×1
  • PRT_KikasaInkSpray.AI (cyclomatic 16) Content/PRTTypes/PRT_KikasaInkSpray.cs:87 — PRT_KikasaInkSpray.AI 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.
D1 · Cyclomatic Complexity · QuestBookGuidePlayer.Tick (cyclomatic 16) · ×1
  • QuestBookGuidePlayer.Tick (cyclomatic 16) Content/QuestLogs/Guide/QuestBookGuidePlayer.cs:124 — QuestBookGuidePlayer.Tick 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.
D1 · Cyclomatic Complexity · QuestLog.Update (cyclomatic 16) · ×1
  • QuestLog.Update (cyclomatic 16) Content/QuestLogs/QuestLog.cs:395 — QuestLog.Update 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.
D1 · Cyclomatic Complexity · DraedonCallUI.Update (cyclomatic 16) · ×1
  • DraedonCallUI.Update (cyclomatic 16) Content/Scenarios/Draedon/PQCDs/DraedonCallUI.cs:105 — DraedonCallUI.Update 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.
D1 · Cyclomatic Complexity · DungeonworldSnuff.CollectLamps (cyclomatic 16) · ×1
  • DungeonworldSnuff.CollectLamps (cyclomatic 16) Content/Scenarios/Dungeonworld/Ambience/DungeonworldSnuff.cs:223 — DungeonworldSnuff.CollectLamps 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.
D1 · Cyclomatic Complexity · DungeonworldBossRecords.HandlePacket (cyclomatic 16) · ×1
  • DungeonworldBossRecords.HandlePacket (cyclomatic 16) Content/Scenarios/Dungeonworld/DungeonworldBossRecords.cs:140 — DungeonworldBossRecords.HandlePacket 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.
D1 · Cyclomatic Complexity · L3Content.RouteChains (cyclomatic 16) · ×1
  • L3Content.RouteChains (cyclomatic 16) Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Content.cs:509 — L3Content.RouteChains 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.
D1 · Cyclomatic Complexity · L3MazeBlock.FurnishShelves (cyclomatic 16) · ×1
  • L3MazeBlock.FurnishShelves (cyclomatic 16) Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3MazeBlock.cs:282 — L3MazeBlock.FurnishShelves 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.
D1 · Cyclomatic Complexity · L4Content.RouteDryLinks (cyclomatic 16) · ×1
  • L4Content.RouteDryLinks (cyclomatic 16) Content/Scenarios/Dungeonworld/Gen/Layers/L4/L4Content.cs:323 — L4Content.RouteDryLinks 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.
D1 · Cyclomatic Complexity · L4Content.LinkWellSide (cyclomatic 16) · ×1
  • L4Content.LinkWellSide (cyclomatic 16) Content/Scenarios/Dungeonworld/Gen/Layers/L4/L4Content.cs:456 — L4Content.LinkWellSide 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.
D1 · Cyclomatic Complexity · L5Leviathan.FurnishFloor (cyclomatic 16) · ×1
  • L5Leviathan.FurnishFloor (cyclomatic 16) Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Leviathan.cs:511 — L5Leviathan.FurnishFloor 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.
D1 · Cyclomatic Complexity · L5Rooms.BuildHall (cyclomatic 16) · ×1
  • L5Rooms.BuildHall (cyclomatic 16) Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Rooms.cs:56 — L5Rooms.BuildHall 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.
D1 · Cyclomatic Complexity · L6Colossus.BuildScaffold (cyclomatic 16) · ×1
  • L6Colossus.BuildScaffold (cyclomatic 16) Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Colossus.cs:387 — L6Colossus.BuildScaffold 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.
D1 · Cyclomatic Complexity · DrownedTurnkey.UpdateSuppress (cyclomatic 16) · ×1
  • DrownedTurnkey.UpdateSuppress (cyclomatic 16) Content/Scenarios/Dungeonworld/NPCs/Elites/DrownedTurnkey.cs:549 — DrownedTurnkey.UpdateSuppress 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.
D1 · Cyclomatic Complexity · FoundryOverseer.UpdateEmerge (cyclomatic 16) · ×1
  • FoundryOverseer.UpdateEmerge (cyclomatic 16) Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:514 — FoundryOverseer.UpdateEmerge 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.
D1 · Cyclomatic Complexity · FoundryOverseer.DrawGlowLayers (cyclomatic 16) · ×1
  • FoundryOverseer.DrawGlowLayers (cyclomatic 16) Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:1392 — FoundryOverseer.DrawGlowLayers 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.
D1 · Cyclomatic Complexity · Undrowned.UpdateStalk (cyclomatic 16) · ×1
  • Undrowned.UpdateStalk (cyclomatic 16) Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:667 — Undrowned.UpdateStalk 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.
D1 · Cyclomatic Complexity · Undrowned.UpdateTideSlam (cyclomatic 16) · ×1
  • Undrowned.UpdateTideSlam (cyclomatic 16) Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:1003 — Undrowned.UpdateTideSlam 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.
D1 · Cyclomatic Complexity · Undrowned.UpdateWhirl (cyclomatic 16) · ×1
  • Undrowned.UpdateWhirl (cyclomatic 16) Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:1334 — Undrowned.UpdateWhirl 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.
D1 · Cyclomatic Complexity · HadalTerrainPlanner.TryAddGallery (cyclomatic 16) · ×1
  • HadalTerrainPlanner.TryAddGallery (cyclomatic 16) Content/Scenarios/Hadalworld/Gen/Core/HadalTerrainPlan.cs:374 — HadalTerrainPlanner.TryAddGallery 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.
D1 · Cyclomatic Complexity · HelenGiftNarrativeTracker.Tick (cyclomatic 16) · ×1
  • HelenGiftNarrativeTracker.Tick (cyclomatic 16) Content/Scenarios/Helen/Gifts/HelenGiftNarrativeTracker.cs:77 — HelenGiftNarrativeTracker.Tick 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.
D1 · Cyclomatic Complexity · ToriiShrineLocationFinder.TryEvaluateColumn (cyclomatic 16) · ×1
  • ToriiShrineLocationFinder.TryEvaluateColumn (cyclomatic 16) Content/Scenarios/Himayo/ToriiShrines/ToriiShrineLocationFinder.cs:149 — ToriiShrineLocationFinder.TryEvaluateColumn 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.
D1 · Cyclomatic Complexity · OniRainWorldRender.EndCaptureDraw (cyclomatic 16) · ×1
  • OniRainWorldRender.EndCaptureDraw (cyclomatic 16) Content/Scenarios/Kiame/Overlay/OniRainWorldRender.cs:21 — OniRainWorldRender.EndCaptureDraw 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.
D1 · Cyclomatic Complexity · OniRainWorldTransition.SpawnStageFx (cyclomatic 16) · ×1
  • OniRainWorldTransition.SpawnStageFx (cyclomatic 16) Content/Scenarios/Kiame/Overlay/OniRainWorldTransition.cs:210 — OniRainWorldTransition.SpawnStageFx 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.
D1 · Cyclomatic Complexity · OniUmbrellaWorldSpawn.TryEvaluateColumn (cyclomatic 16) · ×1
  • OniUmbrellaWorldSpawn.TryEvaluateColumn (cyclomatic 16) Content/Scenarios/Kiame/Overlay/OniUmbrellaWorldSpawn.cs:374 — OniUmbrellaWorldSpawn.TryEvaluateColumn 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.
D1 · Cyclomatic Complexity · KiyumeCrowFlight.Advance (cyclomatic 16) · ×1
  • KiyumeCrowFlight.Advance (cyclomatic 16) Content/Scenarios/Kiyume/Ambience/KiyumeCrowFlight.cs:212 — KiyumeCrowFlight.Advance 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.
D1 · Cyclomatic Complexity · KiyumeHound.AI (cyclomatic 16) · ×1
  • KiyumeHound.AI (cyclomatic 16) Content/Scenarios/Kiyume/NPCs/KiyumeHound.cs:144 — KiyumeHound.AI 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.
D1 · Cyclomatic Complexity · KiyumeHoundDirector.ArbitrateFlank (cyclomatic 16) · ×1
  • KiyumeHoundDirector.ArbitrateFlank (cyclomatic 16) Content/Scenarios/Kiyume/NPCs/KiyumeHoundDirector.cs:298 — KiyumeHoundDirector.ArbitrateFlank 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.
D1 · Cyclomatic Complexity · OldNetLinkFX.UpdateStrain (cyclomatic 16) · ×1
  • OldNetLinkFX.UpdateStrain (cyclomatic 16) Content/Scenarios/OldNet/Backgrounds/OldNetLinkFX.cs:176 — OldNetLinkFX.UpdateStrain 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.
D1 · Cyclomatic Complexity · Z3Rooms.BuildCheckpointAt (cyclomatic 16) · ×1
  • Z3Rooms.BuildCheckpointAt (cyclomatic 16) Content/Scenarios/OldNet/Gen/Zones/Z3/Z3Rooms.cs:105 — Z3Rooms.BuildCheckpointAt 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.
D1 · Cyclomatic Complexity · OldNetThreatPlayer.PostUpdate (cyclomatic 16) · ×1
  • OldNetThreatPlayer.PostUpdate (cyclomatic 16) Content/Scenarios/OldNet/NPCs/OldNetThreatField.cs:935 — OldNetThreatPlayer.PostUpdate 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.
D1 · Cyclomatic Complexity · HackTimeTutorialLead.CheckAutoAdvance (cyclomatic 16) · ×1
  • HackTimeTutorialLead.CheckAutoAdvance (cyclomatic 16) Content/Scenarios/Shepel/CybCourses/HackTimeTutorialLead.cs:345 — HackTimeTutorialLead.CheckAutoAdvance 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.
D1 · Cyclomatic Complexity · ShepelEnvironmentTracker.PreUpdate (cyclomatic 16) · ×1
  • ShepelEnvironmentTracker.PreUpdate (cyclomatic 16) Content/Scenarios/Shepel/ShepelEnvironmentTracker.cs:15 — ShepelEnvironmentTracker.PreUpdate 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.
D1 · Cyclomatic Complexity · SHPCCradleGen.CarveCrash (cyclomatic 16) · ×1
  • SHPCCradleGen.CarveCrash (cyclomatic 16) Content/Structures/SHPCCradleGen.cs:347 — SHPCCradleGen.CarveCrash 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.
D1 · Cyclomatic Complexity · TimeControlReplicationSystem.NetReceive (cyclomatic 16) · ×1
  • TimeControlReplicationSystem.NetReceive (cyclomatic 16) Content/TimeFreezes/TimeControlReplicationSystem.cs:144 — TimeControlReplicationSystem.NetReceive 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.
D1 · Cyclomatic Complexity · EntityFreezeState.UpdateState (cyclomatic 16) · ×1
  • EntityFreezeState.UpdateState (cyclomatic 16) Content/TimeFreezes/TimeFreezeSystem.cs:394 — EntityFreezeState.UpdateState 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.
D1 · Cyclomatic Complexity · EntryDecisionUI.Update (cyclomatic 16) · ×1
  • EntryDecisionUI.Update (cyclomatic 16) Content/UIs/EntryDecisions/EntryDecisionUI.cs:125 — EntryDecisionUI.Update 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.
D1 · Cyclomatic Complexity · RainSeizurePerformance.Update (cyclomatic 16) · ×1
  • RainSeizurePerformance.Update (cyclomatic 16) Content/Wraiths/Deaths/Performances/RainSeizurePerformance.cs:192 — RainSeizurePerformance.Update 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.
D1 · Cyclomatic Complexity · GhostRainProj.AI (cyclomatic 16) · ×1
  • GhostRainProj.AI (cyclomatic 16) Content/Wraiths/Projectiles/GhostRainProj.cs:114 — GhostRainProj.AI 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.
D1 · Cyclomatic Complexity · HeadlessShadeProj.AI (cyclomatic 16) · ×1
  • HeadlessShadeProj.AI (cyclomatic 16) Content/Wraiths/Projectiles/HeadlessShadeProj.cs:209 — HeadlessShadeProj.AI 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.
D1 · Cyclomatic Complexity · WikithisRef.SetupData (cyclomatic 16) · ×1
  • WikithisRef.SetupData (cyclomatic 16) OtherMods/Wikithis/WikithisRef.cs:37 — WikithisRef.SetupData 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.
D2 · Cognitive Complexity · KikasaGunServant.UpdateGuns (cognitive 145) · ×1
  • KikasaGunServant.UpdateGuns (cognitive 145) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1040 — KikasaGunServant.UpdateGuns 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.
D2 · Cognitive Complexity · CultistPlanetProj.AI (cognitive 133) · ×1
  • CultistPlanetProj.AI (cognitive 133) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistPlanetProj.cs:126 — CultistPlanetProj.AI has cognitive complexity 133 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ValidatePass.ApplyPass (cognitive 126) · ×1
  • ValidatePass.ApplyPass (cognitive 126) Content/Scenarios/Dungeonworld/Gen/Passes/ValidatePass.cs:21 — ValidatePass.ApplyPass has cognitive complexity 126 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaPanoramaUI.DrawHoverTipPanel (cognitive 117) · ×1
  • KikasaPanoramaUI.DrawHoverTipPanel (cognitive 117) Content/LegendWeapon/KikasaLegend/UI/Panorama/KikasaPanoramaUI.cs:2064 — KikasaPanoramaUI.DrawHoverTipPanel has cognitive complexity 117 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CultistConjunctionState.UpdateRelease (cognitive 109) · ×1
  • CultistConjunctionState.UpdateRelease (cognitive 109) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistConjunctionState.cs:149 — CultistConjunctionState.UpdateRelease has cognitive complexity 109 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaInkPour.AI (cognitive 102) · ×1
  • KikasaInkPour.AI (cognitive 102) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPour.cs:161 — KikasaInkPour.AI has cognitive complexity 102 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DeepGaolWraith.UpdateCuffs (cognitive 101) · ×1
  • DeepGaolWraith.UpdateCuffs (cognitive 101) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:1642 — DeepGaolWraith.UpdateCuffs 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.
D2 · Cognitive Complexity · HadalTerrainCarver.CarvePlain (cognitive 92) · ×1
  • HadalTerrainCarver.CarvePlain (cognitive 92) Content/Scenarios/Hadalworld/Gen/Core/HadalTerrainCarver.cs:204 — HadalTerrainCarver.CarvePlain has cognitive complexity 92 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · L3MazeBlock.Build (cognitive 90) · ×1
  • L3MazeBlock.Build (cognitive 90) Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3MazeBlock.cs:101 — L3MazeBlock.Build has cognitive complexity 90 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HalibutPlayer.PostUpdate (cognitive 89) · ×1
  • HalibutPlayer.PostUpdate (cognitive 89) Content/LegendWeapon/HalibutLegend/HalibutPlayer.cs:351 — HalibutPlayer.PostUpdate has cognitive complexity 89 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SHPCUI.Update (cognitive 88) · ×1
  • SHPCUI.Update (cognitive 88) Content/LegendWeapon/SHPCLegend/UI/SHPCUI.cs:472 — SHPCUI.Update has cognitive complexity 88 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaServantPlayer.LoadData (cognitive 86) · ×1
  • KikasaServantPlayer.LoadData (cognitive 86) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaServantPlayer.cs:579 — KikasaServantPlayer.LoadData has cognitive complexity 86 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaBladeServant.UpdateBlades (cognitive 85) · ×1
  • KikasaBladeServant.UpdateBlades (cognitive 85) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:787 — KikasaBladeServant.UpdateBlades has cognitive complexity 85 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaQueenBeeServant.UpdateRake (cognitive 85) · ×1
  • KikasaQueenBeeServant.UpdateRake (cognitive 85) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:517 — KikasaQueenBeeServant.UpdateRake has cognitive complexity 85 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OnikiriPlayer.PostUpdate (cognitive 83) · ×1
  • OnikiriPlayer.PostUpdate (cognitive 83) Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs:531 — OnikiriPlayer.PostUpdate has cognitive complexity 83 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · RetinazerSoloRageState.ExecuteLaserMatrix (cognitive 82) · ×1
  • RetinazerSoloRageState.ExecuteLaserMatrix (cognitive 82) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerSoloRageState.cs:401 — RetinazerSoloRageState.ExecuteLaserMatrix has cognitive complexity 82 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaBowServant.UpdateBows (cognitive 81) · ×1
  • KikasaBowServant.UpdateBows (cognitive 81) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:864 — KikasaBowServant.UpdateBows has cognitive complexity 81 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ScrapLaserSweepState.OnUpdate (cognitive 80) · ×1
  • ScrapLaserSweepState.OnUpdate (cognitive 80) Content/NPCs/ScrapCommanders/States/ScrapLaserSweepState.cs:44 — ScrapLaserSweepState.OnUpdate has cognitive complexity 80 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LegendTooltipPanel.Draw (cognitive 79) · ×1
  • LegendTooltipPanel.Draw (cognitive 79) Content/LegendWeapon/LegendTooltipLayout.cs:290 — LegendTooltipPanel.Draw has cognitive complexity 79 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FishronVortexGrabState.OnUpdate (cognitive 78) · ×1
  • FishronVortexGrabState.OnUpdate (cognitive 78) Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronVortexGrabStates.cs:313 — FishronVortexGrabState.OnUpdate has cognitive complexity 78 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniSlash.UpdateBladePose (cognitive 77) · ×1
  • OniSlash.UpdateBladePose (cognitive 77) Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:764 — OniSlash.UpdateBladePose has cognitive complexity 77 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EowSplitPincerState.UpdatePincer (cognitive 77) · ×1
  • EowSplitPincerState.UpdatePincer (cognitive 77) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowSplitPincerState.cs:207 — EowSplitPincerState.UpdatePincer has cognitive complexity 77 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MLordLocomotion.Update (cognitive 77) · ×1
  • MLordLocomotion.Update (cognitive 77) Content/NPCs/BrutalNPCs/BrutalMoonLord/Core/MLordLocomotion.cs:260 — MLordLocomotion.Update has cognitive complexity 77 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CrimsonSweepSlash.UpdateBladePose (cognitive 76) · ×1
  • CrimsonSweepSlash.UpdateBladePose (cognitive 76) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:609 — CrimsonSweepSlash.UpdateBladePose has cognitive complexity 76 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HadalValidatePass.ApplyPass (cognitive 75) · ×1
  • HadalValidatePass.ApplyPass (cognitive 75) Content/Scenarios/Hadalworld/Gen/Passes/HadalValidatePass.cs:17 — HadalValidatePass.ApplyPass has cognitive complexity 75 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · IndustrializationGen.SpawnWGGCollectorTile (cognitive 75) · ×1
  • IndustrializationGen.SpawnWGGCollectorTile (cognitive 75) Content/Structures/IndustrializationGen.cs:72 — IndustrializationGen.SpawnWGGCollectorTile has cognitive complexity 75 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CultistUmbraShade.AI (cognitive 73) · ×1
  • CultistUmbraShade.AI (cognitive 73) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistUmbraShade.cs:278 — CultistUmbraShade.AI has cognitive complexity 73 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DraedonQuestLogStyle.DrawDetailContent (cognitive 72) · ×1
  • DraedonQuestLogStyle.DrawDetailContent (cognitive 72) Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:398 — DraedonQuestLogStyle.DrawDetailContent has cognitive complexity 72 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ScrapIntroState.OnUpdate (cognitive 71) · ×1
  • ScrapIntroState.OnUpdate (cognitive 71) Content/NPCs/ScrapCommanders/States/ScrapIntroState.cs:56 — ScrapIntroState.OnUpdate has cognitive complexity 71 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OverhaulSettingsUI.Update (cognitive 70) · ×1
  • OverhaulSettingsUI.Update (cognitive 70) Content/UIs/OverhaulSettings/OverhaulSettingsUI.cs:175 — OverhaulSettingsUI.Update has cognitive complexity 70 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CrimsonRendSlash.UpdateBladePose (cognitive 69) · ×1
  • CrimsonRendSlash.UpdateBladePose (cognitive 69) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:808 — CrimsonRendSlash.UpdateBladePose has cognitive complexity 69 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HalibutSave.LoadData (cognitive 68) · ×1
  • HalibutSave.LoadData (cognitive 68) Content/LegendWeapon/HalibutLegend/HalibutSave.cs:387 — HalibutSave.LoadData has cognitive complexity 68 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaKingSlimeServant.UpdateEmerge (cognitive 67) · ×1
  • KikasaKingSlimeServant.UpdateEmerge (cognitive 67) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:299 — KikasaKingSlimeServant.UpdateEmerge has cognitive complexity 67 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaSkeletronServant.UpdateHands (cognitive 66) · ×1
  • KikasaSkeletronServant.UpdateHands (cognitive 66) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1050 — KikasaSkeletronServant.UpdateHands has cognitive complexity 66 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ForestQuestLogStyle.DrawDetailContent (cognitive 66) · ×1
  • ForestQuestLogStyle.DrawDetailContent (cognitive 66) Content/QuestLogs/Styles/ForestQuestLogStyle.cs:339 — ForestQuestLogStyle.DrawDetailContent has cognitive complexity 66 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HotwindQuestLogStyle.DrawDetailContent (cognitive 66) · ×1
  • HotwindQuestLogStyle.DrawDetailContent (cognitive 66) Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:334 — HotwindQuestLogStyle.DrawDetailContent has cognitive complexity 66 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · IndustrializationGen.SpawnWindGrivenGenerator (cognitive 65) · ×1
  • IndustrializationGen.SpawnWindGrivenGenerator (cognitive 65) Content/Structures/IndustrializationGen.cs:210 — IndustrializationGen.SpawnWindGrivenGenerator has cognitive complexity 65 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · AtlasSkillSea.Update (cognitive 63) · ×1
  • AtlasSkillSea.Update (cognitive 63) Content/LegendWeapon/HalibutLegend/UI/Atlas/AtlasSkillSea.cs:204 — AtlasSkillSea.Update has cognitive complexity 63 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · WorldGenSettingsCategory.HandleClick (cognitive 63) · ×1
  • WorldGenSettingsCategory.HandleClick (cognitive 63) Content/UIs/OverhaulSettings/WorldGenSettingsCategory.cs:310 — WorldGenSettingsCategory.HandleClick has cognitive complexity 63 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TreeBlueprint.GenerateCommon (cognitive 62) · ×1
  • TreeBlueprint.GenerateCommon (cognitive 62) Content/Industrials/ElectricPowers/TreeRegrowths/TreeBlueprint.cs:158 — TreeBlueprint.GenerateCommon has cognitive complexity 62 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaInkGeyser.AI (cognitive 62) · ×1
  • KikasaInkGeyser.AI (cognitive 62) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkGeyser.cs:138 — KikasaInkGeyser.AI has cognitive complexity 62 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniMeiUI.UpdateInteraction (cognitive 62) · ×1
  • OniMeiUI.UpdateInteraction (cognitive 62) Content/LegendWeapon/OnikiriLegend/UI/OniMeiUI.cs:619 — OniMeiUI.UpdateInteraction has cognitive complexity 62 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TheHungryAI.UpdateTetherMode (cognitive 61) · ×1
  • TheHungryAI.UpdateTetherMode (cognitive 61) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/TheHungryAI.cs:94 — TheHungryAI.UpdateTetherMode has cognitive complexity 61 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SeaDomainProj.UpdateDomainEffects (cognitive 60) · ×1
  • SeaDomainProj.UpdateDomainEffects (cognitive 60) Content/LegendWeapon/HalibutLegend/DomainSkills/SeaDomain.cs:328 — SeaDomainProj.UpdateDomainEffects has cognitive complexity 60 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaSpearServant.UpdateSpears (cognitive 60) · ×1
  • KikasaSpearServant.UpdateSpears (cognitive 60) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:662 — KikasaSpearServant.UpdateSpears has cognitive complexity 60 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Undrowned.UpdateDeath (cognitive 60) · ×1
  • Undrowned.UpdateDeath (cognitive 60) Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:1555 — Undrowned.UpdateDeath has cognitive complexity 60 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ScorpionSentry.AI (cognitive 59) · ×1
  • ScorpionSentry.AI (cognitive 59) Content/LegendWeapon/HalibutLegend/FishSkills/FishScorpio.cs:174 — ScorpionSentry.AI has cognitive complexity 59 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaOnikiriServant.UpdateBlade (cognitive 59) · ×1
  • KikasaOnikiriServant.UpdateBlade (cognitive 59) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:805 — KikasaOnikiriServant.UpdateBlade has cognitive complexity 59 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaPlanteraServant.UpdateEmerge (cognitive 59) · ×1
  • KikasaPlanteraServant.UpdateEmerge (cognitive 59) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:399 — KikasaPlanteraServant.UpdateEmerge has cognitive complexity 59 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaPrimeServant.UpdateDart (cognitive 59) · ×1
  • KikasaPrimeServant.UpdateDart (cognitive 59) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:555 — KikasaPrimeServant.UpdateDart has cognitive complexity 59 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BssIntroState.OnUpdate (cognitive 59) · ×1
  • BssIntroState.OnUpdate (cognitive 59) Content/NPCs/BloomsandSerpents/States/BssIntroState.cs:69 — BssIntroState.OnUpdate has cognitive complexity 59 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GolemTrapUnit.UpdateActive (cognitive 59) · ×1
  • GolemTrapUnit.UpdateActive (cognitive 59) Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemTrapUnit.cs:175 — GolemTrapUnit.UpdateActive has cognitive complexity 59 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HadalTerrainCarver.BaseFill (cognitive 59) · ×1
  • HadalTerrainCarver.BaseFill (cognitive 59) Content/Scenarios/Hadalworld/Gen/Core/HadalTerrainCarver.cs:39 — HadalTerrainCarver.BaseFill has cognitive complexity 59 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OldNetICEDirector.PostUpdateNPCs (cognitive 59) · ×1
  • OldNetICEDirector.PostUpdateNPCs (cognitive 59) Content/Scenarios/OldNet/NPCs/OldNetICEDirector.cs:147 — OldNetICEDirector.PostUpdateNPCs has cognitive complexity 59 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · QuestManagerUI.HandleMouseInput (cognitive 58) · ×1
  • QuestManagerUI.HandleMouseInput (cognitive 58) Content/EntrustManager/EntrustManagerUI.cs:416 — QuestManagerUI.HandleMouseInput 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.
D2 · Cognitive Complexity · DraedonManagerStyle.DrawQuestEntry (cognitive 58) · ×1
  • DraedonManagerStyle.DrawQuestEntry (cognitive 58) Content/EntrustManager/Styles/DraedonManagerStyle.cs:405 — DraedonManagerStyle.DrawQuestEntry 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.
D2 · Cognitive Complexity · ForestManagerStyle.DrawQuestEntry (cognitive 58) · ×1
  • ForestManagerStyle.DrawQuestEntry (cognitive 58) Content/EntrustManager/Styles/ForestManagerStyle.cs:414 — ForestManagerStyle.DrawQuestEntry 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.
D2 · Cognitive Complexity · HotwindManagerStyle.DrawQuestEntry (cognitive 58) · ×1
  • HotwindManagerStyle.DrawQuestEntry (cognitive 58) Content/EntrustManager/Styles/HotwindManagerStyle.cs:403 — HotwindManagerStyle.DrawQuestEntry 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.
D2 · Cognitive Complexity · KikasaMoonLordServant.DrawVesselLayer (cognitive 58) · ×1
  • KikasaMoonLordServant.DrawVesselLayer (cognitive 58) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1187 — KikasaMoonLordServant.DrawVesselLayer 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.
D2 · Cognitive Complexity · KikasaTwinsServant.UpdateScissor (cognitive 58) · ×1
  • KikasaTwinsServant.UpdateScissor (cognitive 58) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:527 — KikasaTwinsServant.UpdateScissor 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.
D2 · Cognitive Complexity · KikasaTwinsServant.UpdateEyes (cognitive 58) · ×1
  • KikasaTwinsServant.UpdateEyes (cognitive 58) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:989 — KikasaTwinsServant.UpdateEyes 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.
D2 · Cognitive Complexity · FishronMaelstromState.OnUpdate (cognitive 58) · ×1
  • FishronMaelstromState.OnUpdate (cognitive 58) Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronMaelstromState.cs:72 — FishronMaelstromState.OnUpdate 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.
D2 · Cognitive Complexity · Undrowned.UpdateEmerge (cognitive 58) · ×1
  • Undrowned.UpdateEmerge (cognitive 58) Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:551 — Undrowned.UpdateEmerge 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.
D2 · Cognitive Complexity · CyberSlotRenderer.DrawSlots (cognitive 57) · ×1
  • CyberSlotRenderer.DrawSlots (cognitive 57) Content/Cyberwares/UIs/CyberSlotRenderer.cs:143 — CyberSlotRenderer.DrawSlots has cognitive complexity 57 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaBrainServant.DrawGlow (cognitive 57) · ×1
  • KikasaBrainServant.DrawGlow (cognitive 57) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1380 — KikasaBrainServant.DrawGlow has cognitive complexity 57 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KiyumeGroundField.Scan (cognitive 57) · ×1
  • KiyumeGroundField.Scan (cognitive 57) Content/Scenarios/Kiyume/Fog/KiyumeGroundField.cs:143 — KiyumeGroundField.Scan has cognitive complexity 57 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaQueenSlimeServant.UpdateDive (cognitive 56) · ×1
  • KikasaQueenSlimeServant.UpdateDive (cognitive 56) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:636 — KikasaQueenSlimeServant.UpdateDive has cognitive complexity 56 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FssHubState.PickAttack (cognitive 56) · ×1
  • FssHubState.PickAttack (cognitive 56) Content/NPCs/FestersandSerpents/States/FssHubState.cs:140 — FssHubState.PickAttack has cognitive complexity 56 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Undrowned.UpdateAnchorThrow (cognitive 56) · ×1
  • Undrowned.UpdateAnchorThrow (cognitive 56) Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:820 — Undrowned.UpdateAnchorThrow has cognitive complexity 56 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HadalDecorPass.ApplyPass (cognitive 56) · ×1
  • HadalDecorPass.ApplyPass (cognitive 56) Content/Scenarios/Hadalworld/Gen/Passes/HadalDecorPass.cs:16 — HadalDecorPass.ApplyPass has cognitive complexity 56 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PrismgladeJudgmentProj.AI (cognitive 55) · ×1
  • PrismgladeJudgmentProj.AI (cognitive 55) Content/GameModes/BrutalMobs/Ambience/Prismglade/Projectiles/PrismgladeJudgmentProj.cs:99 — PrismgladeJudgmentProj.AI has cognitive complexity 55 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaInkDrop.AI (cognitive 55) · ×1
  • KikasaInkDrop.AI (cognitive 55) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:197 — KikasaInkDrop.AI has cognitive complexity 55 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaPlanteraServant.UpdatePounce (cognitive 55) · ×1
  • KikasaPlanteraServant.UpdatePounce (cognitive 55) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:887 — KikasaPlanteraServant.UpdatePounce has cognitive complexity 55 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaPrimeServant.UpdateArms (cognitive 55) · ×1
  • KikasaPrimeServant.UpdateArms (cognitive 55) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:982 — KikasaPrimeServant.UpdateArms has cognitive complexity 55 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BssBurrowLungeState.OnUpdate (cognitive 55) · ×1
  • BssBurrowLungeState.OnUpdate (cognitive 55) Content/NPCs/BloomsandSerpents/States/BssBurrowLungeState.cs:53 — BssBurrowLungeState.OnUpdate has cognitive complexity 55 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FloodGalleryRoom.ApplyWeathering (cognitive 55) · ×1
  • FloodGalleryRoom.ApplyWeathering (cognitive 55) Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryRoom.cs:272 — FloodGalleryRoom.ApplyWeathering has cognitive complexity 55 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FrostveilScreenFrostRender.EndCaptureDraw (cognitive 54) · ×1
  • FrostveilScreenFrostRender.EndCaptureDraw (cognitive 54) Content/GameModes/BrutalMobs/Ambience/Frostveil/FrostveilScreenFrostRender.cs:37 — FrostveilScreenFrostRender.EndCaptureDraw 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.
D2 · Cognitive Complexity · StationSnapshot.Scan (cognitive 54) · ×1
  • StationSnapshot.Scan (cognitive 54) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterRecipeId.cs:156 — StationSnapshot.Scan 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.
D2 · Cognitive Complexity · AtlasDomainEyes.Update (cognitive 54) · ×1
  • AtlasDomainEyes.Update (cognitive 54) Content/LegendWeapon/HalibutLegend/UI/Atlas/AtlasDomainEyes.cs:71 — AtlasDomainEyes.Update 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.
D2 · Cognitive Complexity · AtlasSkillSea.DrawDock (cognitive 54) · ×1
  • AtlasSkillSea.DrawDock (cognitive 54) Content/LegendWeapon/HalibutLegend/UI/Atlas/AtlasSkillSea.cs:833 — AtlasSkillSea.DrawDock 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.
D2 · Cognitive Complexity · KikasaKingSlimeServant.UpdateDissolve (cognitive 54) · ×1
  • KikasaKingSlimeServant.UpdateDissolve (cognitive 54) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:904 — KikasaKingSlimeServant.UpdateDissolve 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.
D2 · Cognitive Complexity · KikasaQueenSlimeServant.UpdateEmerge (cognitive 54) · ×1
  • KikasaQueenSlimeServant.UpdateEmerge (cognitive 54) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:281 — KikasaQueenSlimeServant.UpdateEmerge 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.
D2 · Cognitive Complexity · KikasaSkeletronServant.UpdateEmerge (cognitive 54) · ×1
  • KikasaSkeletronServant.UpdateEmerge (cognitive 54) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:331 — KikasaSkeletronServant.UpdateEmerge 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.
D2 · Cognitive Complexity · SkeletronPalmSnatchState.AuthorityUpdate (cognitive 54) · ×1
  • SkeletronPalmSnatchState.AuthorityUpdate (cognitive 54) Content/NPCs/BrutalNPCs/BrutalSkeletron/States/SkeletronPalmSnatchState.cs:141 — SkeletronPalmSnatchState.AuthorityUpdate 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.
D2 · Cognitive Complexity · ScrapDeathState.OnUpdate (cognitive 54) · ×1
  • ScrapDeathState.OnUpdate (cognitive 54) Content/NPCs/ScrapCommanders/States/ScrapDeathState.cs:50 — ScrapDeathState.OnUpdate 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.
D2 · Cognitive Complexity · AshfallStratum.BuildChute (cognitive 54) · ×1
  • AshfallStratum.BuildChute (cognitive 54) Content/Scenarios/Dungeonworld/Gen/Zones/AshfallStratum.cs:314 — AshfallStratum.BuildChute 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.
D2 · Cognitive Complexity · DeepGaolWraith.UpdateAmbush (cognitive 54) · ×1
  • DeepGaolWraith.UpdateAmbush (cognitive 54) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:1332 — DeepGaolWraith.UpdateAmbush 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.
D2 · Cognitive Complexity · CybTutorialLead.UpdateUI (cognitive 54) · ×1
  • CybTutorialLead.UpdateUI (cognitive 54) Content/Scenarios/Shepel/CybCourses/CybTutorialLead.cs:126 — CybTutorialLead.UpdateUI 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.
D2 · Cognitive Complexity · HackStatusDisplay.Draw (cognitive 53) · ×1
  • HackStatusDisplay.Draw (cognitive 53) Content/HackTimes/HackStatusDisplay.cs:37 — HackStatusDisplay.Draw has cognitive complexity 53 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · AutoFisherLootTable.RollCrate (cognitive 53) · ×1
  • AutoFisherLootTable.RollCrate (cognitive 53) Content/Industrials/ElectricPowers/AutoFishers/AutoFisherLootTable.cs:163 — AutoFisherLootTable.RollCrate has cognitive complexity 53 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaMinionDrownFX.UpdateShow (cognitive 53) · ×1
  • KikasaMinionDrownFX.UpdateShow (cognitive 53) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaMinionDrownFX.cs:235 — KikasaMinionDrownFX.UpdateShow has cognitive complexity 53 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaGolemServant.UpdateSlam (cognitive 53) · ×1
  • KikasaGolemServant.UpdateSlam (cognitive 53) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:516 — KikasaGolemServant.UpdateSlam has cognitive complexity 53 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaSkeletronServant.UpdateSpin (cognitive 53) · ×1
  • KikasaSkeletronServant.UpdateSpin (cognitive 53) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:715 — KikasaSkeletronServant.UpdateSpin has cognitive complexity 53 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ProofingHallWatcher.PostUpdateNPCs (cognitive 53) · ×1
  • ProofingHallWatcher.PostUpdateNPCs (cognitive 53) Content/Scenarios/Dungeonworld/Gen/BossRooms/ProofingHallWatcher.cs:85 — ProofingHallWatcher.PostUpdateNPCs has cognitive complexity 53 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DrownedCulverts.BuildBelt (cognitive 53) · ×1
  • DrownedCulverts.BuildBelt (cognitive 53) Content/Scenarios/Dungeonworld/Gen/Zones/DrownedCulverts.cs:91 — DrownedCulverts.BuildBelt has cognitive complexity 53 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OverseerPressStrike.AI (cognitive 53) · ×1
  • OverseerPressStrike.AI (cognitive 53) Content/Scenarios/Dungeonworld/NPCs/OverseerPressStrike.cs:75 — OverseerPressStrike.AI has cognitive complexity 53 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · IndustrialSkyIslandGen.BuildIslandBody (cognitive 53) · ×1
  • IndustrialSkyIslandGen.BuildIslandBody (cognitive 53) Content/Structures/IndustrialSkyIslandGen.cs:123 — IndustrialSkyIslandGen.BuildIslandBody has cognitive complexity 53 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CyberSlotRenderer.DrawConnectors (cognitive 52) · ×1
  • CyberSlotRenderer.DrawConnectors (cognitive 52) Content/Cyberwares/UIs/CyberSlotRenderer.cs:256 — CyberSlotRenderer.DrawConnectors has cognitive complexity 52 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaQueenBeeServant.UpdateEmerge (cognitive 52) · ×1
  • KikasaQueenBeeServant.UpdateEmerge (cognitive 52) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:278 — KikasaQueenBeeServant.UpdateEmerge has cognitive complexity 52 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SHPCNPCEffects.PreAI (cognitive 52) · ×1
  • SHPCNPCEffects.PreAI (cognitive 52) Content/LegendWeapon/SHPCLegend/Cyberspaces/SHPCNPCEffects.cs:432 — SHPCNPCEffects.PreAI has cognitive complexity 52 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CultistEclipseDragon.AI (cognitive 52) · ×1
  • CultistEclipseDragon.AI (cognitive 52) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistEclipseDragon.cs:80 — CultistEclipseDragon.AI has cognitive complexity 52 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FssMoltGrowthState.OnUpdate (cognitive 52) · ×1
  • FssMoltGrowthState.OnUpdate (cognitive 52) Content/NPCs/FestersandSerpents/States/FssMoltGrowthState.cs:47 — FssMoltGrowthState.OnUpdate has cognitive complexity 52 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FoundryOverseer.UpdateDeath (cognitive 52) · ×1
  • FoundryOverseer.UpdateDeath (cognitive 52) Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:1069 — FoundryOverseer.UpdateDeath has cognitive complexity 52 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TreeBlueprint.GenerateWithSettings (cognitive 51) · ×1
  • TreeBlueprint.GenerateWithSettings (cognitive 51) Content/Industrials/ElectricPowers/TreeRegrowths/TreeBlueprint.cs:271 — TreeBlueprint.GenerateWithSettings 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.
D2 · Cognitive Complexity · DirtFishFollower.ConvergingAI (cognitive 51) · ×1
  • DirtFishFollower.ConvergingAI (cognitive 51) Content/LegendWeapon/HalibutLegend/FishSkills/FishDirt.cs:365 — DirtFishFollower.ConvergingAI 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.
D2 · Cognitive Complexity · KikasaDestroyerServant.UpdateJet (cognitive 51) · ×1
  • KikasaDestroyerServant.UpdateJet (cognitive 51) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:529 — KikasaDestroyerServant.UpdateJet 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.
D2 · Cognitive Complexity · KikasaPanoramaUI.Update (cognitive 51) · ×1
  • KikasaPanoramaUI.Update (cognitive 51) Content/LegendWeapon/KikasaLegend/UI/Panorama/KikasaPanoramaUI.cs:369 — KikasaPanoramaUI.Update 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.
D2 · Cognitive Complexity · PotionBeaconTP.UpdateMachine (cognitive 50) · ×1
  • PotionBeaconTP.UpdateMachine (cognitive 50) Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconTP.cs:167 — PotionBeaconTP.UpdateMachine 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.
D2 · Cognitive Complexity · KikasaMoonLordServant.UpdateMoonRay (cognitive 50) · ×1
  • KikasaMoonLordServant.UpdateMoonRay (cognitive 50) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:769 — KikasaMoonLordServant.UpdateMoonRay 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.
D2 · Cognitive Complexity · OniDomainDeco.Draw (cognitive 50) · ×1
  • OniDomainDeco.Draw (cognitive 50) Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainDeco.cs:440 — OniDomainDeco.Draw 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.
D2 · Cognitive Complexity · SeaShrimpBubbleCannonState.OnUpdate (cognitive 50) · ×1
  • SeaShrimpBubbleCannonState.OnUpdate (cognitive 50) Content/NPCs/SeaShrimp/States/SeaShrimpBubbleCannonState.cs:37 — SeaShrimpBubbleCannonState.OnUpdate 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.
D2 · Cognitive Complexity · L3BookTower.Build (cognitive 50) · ×1
  • L3BookTower.Build (cognitive 50) Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3BookTower.cs:53 — L3BookTower.Build 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.
D2 · Cognitive Complexity · KiyumeVillage.BuildInterior (cognitive 50) · ×1
  • KiyumeVillage.BuildInterior (cognitive 50) Content/Scenarios/Kiyume/Gen/KiyumeVillage.cs:276 — KiyumeVillage.BuildInterior 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.
D2 · Cognitive Complexity · AutoFisherUI.Update (cognitive 49) · ×1
  • AutoFisherUI.Update (cognitive 49) Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs:136 — AutoFisherUI.Update has cognitive complexity 49 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaEaterServant.UpdateSpitVolley (cognitive 49) · ×1
  • KikasaEaterServant.UpdateSpitVolley (cognitive 49) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:734 — KikasaEaterServant.UpdateSpitVolley has cognitive complexity 49 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaLakeFX.UpdateRaise (cognitive 49) · ×1
  • KikasaLakeFX.UpdateRaise (cognitive 49) Content/LegendWeapon/KikasaLegend/KikasaVaults/KikasaLakeFX.cs:398 — KikasaLakeFX.UpdateRaise has cognitive complexity 49 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaHud.DrawTooltipOverlay (cognitive 49) · ×1
  • KikasaHud.DrawTooltipOverlay (cognitive 49) Content/LegendWeapon/KikasaLegend/UI/KikasaHud.cs:786 — KikasaHud.DrawTooltipOverlay has cognitive complexity 49 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GolemMeteorLeapState.OnUpdate (cognitive 49) · ×1
  • GolemMeteorLeapState.OnUpdate (cognitive 49) Content/NPCs/BrutalNPCs/BrutalGolem/States/GolemMeteorLeapState.cs:37 — GolemMeteorLeapState.OnUpdate has cognitive complexity 49 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DeepGaolWraith.UpdateEmerge (cognitive 49) · ×1
  • DeepGaolWraith.UpdateEmerge (cognitive 49) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:484 — DeepGaolWraith.UpdateEmerge has cognitive complexity 49 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OldNetThreatField.SeedTripwires (cognitive 49) · ×1
  • OldNetThreatField.SeedTripwires (cognitive 49) Content/Scenarios/OldNet/NPCs/OldNetThreatField.cs:669 — OldNetThreatField.SeedTripwires has cognitive complexity 49 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CWRProjectile.OnSpawn (cognitive 48) · ×1
  • CWRProjectile.OnSpawn (cognitive 48) Content/CWRProjectile.cs:48 — CWRProjectile.OnSpawn has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HackPanelRenderer.DrawConnectorTree (cognitive 48) · ×1
  • HackPanelRenderer.DrawConnectorTree (cognitive 48) Content/HackTimes/HackPanelRenderer.cs:963 — HackPanelRenderer.DrawConnectorTree has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaDreamGroundField.Scan (cognitive 48) · ×1
  • KikasaDreamGroundField.Scan (cognitive 48) Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamGroundField.cs:128 — KikasaDreamGroundField.Scan has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CyberChargeOrbProj.AI_Charging (cognitive 48) · ×1
  • CyberChargeOrbProj.AI_Charging (cognitive 48) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberChargeOrbProj.cs:212 — CyberChargeOrbProj.AI_Charging has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FloodGalleryWatcher.PostUpdateNPCs (cognitive 48) · ×1
  • FloodGalleryWatcher.PostUpdateNPCs (cognitive 48) Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryWatcher.cs:115 — FloodGalleryWatcher.PostUpdateNPCs has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · L3Content.PlaceDeckRooms (cognitive 48) · ×1
  • L3Content.PlaceDeckRooms (cognitive 48) Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Content.cs:277 — L3Content.PlaceDeckRooms has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Undrowned.UpdateBreach (cognitive 48) · ×1
  • Undrowned.UpdateBreach (cognitive 48) Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:1161 — Undrowned.UpdateBreach has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OldDukeCampsiteGenerationService.PlaceOldChest (cognitive 48) · ×1
  • OldDukeCampsiteGenerationService.PlaceOldChest (cognitive 48) Content/Scenarios/OldDuke/Campsites/OldDukeCampsiteGenerationService.cs:136 — OldDukeCampsiteGenerationService.PlaceOldChest has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OldNetWardenICE.UpdateRain (cognitive 48) · ×1
  • OldNetWardenICE.UpdateRain (cognitive 48) Content/Scenarios/OldNet/NPCs/OldNetWardenICE.cs:452 — OldNetWardenICE.UpdateRain has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SylvanOutpost.BlendEdge (cognitive 48) · ×1
  • SylvanOutpost.BlendEdge (cognitive 48) Content/Structures/DatIO/SylvanOutpost.cs:532 — SylvanOutpost.BlendEdge has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · StonewakeResonanceRingProj.AI (cognitive 47) · ×1
  • StonewakeResonanceRingProj.AI (cognitive 47) Content/GameModes/BrutalMobs/Ambience/Stonewake/Projectiles/StonewakeResonanceRingProj.cs:84 — StonewakeResonanceRingProj.AI 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.
D2 · Cognitive Complexity · KikasaBrainServant.UpdateMirages (cognitive 47) · ×1
  • KikasaBrainServant.UpdateMirages (cognitive 47) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:957 — KikasaBrainServant.UpdateMirages 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.
D2 · Cognitive Complexity · SHPCOverride.On_Shoot (cognitive 47) · ×1
  • SHPCOverride.On_Shoot (cognitive 47) Content/LegendWeapon/SHPCLegend/SHPCOverride.cs:180 — SHPCOverride.On_Shoot 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.
D2 · Cognitive Complexity · SHPCPlayer.LoadData (cognitive 47) · ×1
  • SHPCPlayer.LoadData (cognitive 47) Content/LegendWeapon/SHPCLegend/SHPCPlayer.cs:287 — SHPCPlayer.LoadData 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.
D2 · Cognitive Complexity · DeerclopsSeizeHuntState.OnUpdate (cognitive 47) · ×1
  • DeerclopsSeizeHuntState.OnUpdate (cognitive 47) Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsSeizeHuntState.cs:71 — DeerclopsSeizeHuntState.OnUpdate 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.
D2 · Cognitive Complexity · MLordTidalPalmsState.DriveSlamServer (cognitive 47) · ×1
  • MLordTidalPalmsState.DriveSlamServer (cognitive 47) Content/NPCs/BrutalNPCs/BrutalMoonLord/States/MLordTidalPalmsState.cs:161 — MLordTidalPalmsState.DriveSlamServer 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.
D2 · Cognitive Complexity · FssIntroState.OnUpdate (cognitive 47) · ×1
  • FssIntroState.OnUpdate (cognitive 47) Content/NPCs/FestersandSerpents/States/FssIntroState.cs:60 — FssIntroState.OnUpdate 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.
D2 · Cognitive Complexity · Z3Giant.BuildGiantAt (cognitive 47) · ×1
  • Z3Giant.BuildGiantAt (cognitive 47) Content/Scenarios/OldNet/Gen/Zones/Z3/Z3Giant.cs:59 — Z3Giant.BuildGiantAt 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.
D2 · Cognitive Complexity · MushroomFarmerTP.TryHarvest (cognitive 46) · ×1
  • MushroomFarmerTP.TryHarvest (cognitive 46) Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:406 — MushroomFarmerTP.TryHarvest has cognitive complexity 46 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaRainUmbrella.TickVolleyBeat (cognitive 46) · ×1
  • KikasaRainUmbrella.TickVolleyBeat (cognitive 46) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:624 — KikasaRainUmbrella.TickVolleyBeat has cognitive complexity 46 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaKingSlimeServant.UpdateSlam (cognitive 46) · ×1
  • KikasaKingSlimeServant.UpdateSlam (cognitive 46) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:604 — KikasaKingSlimeServant.UpdateSlam has cognitive complexity 46 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniMeiCodexUI.UpdateInteraction (cognitive 46) · ×1
  • OniMeiCodexUI.UpdateInteraction (cognitive 46) Content/LegendWeapon/OnikiriLegend/UI/OniMeiCodexUI.cs:340 — OniMeiCodexUI.UpdateInteraction has cognitive complexity 46 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DeerclopsEyeGrabState.DriveBossPresentation (cognitive 46) · ×1
  • DeerclopsEyeGrabState.DriveBossPresentation (cognitive 46) Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsEyeGrabState.cs:119 — DeerclopsEyeGrabState.DriveBossPresentation has cognitive complexity 46 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OldDuchestTP.Update (cognitive 46) · ×1
  • OldDuchestTP.Update (cognitive 46) Content/Scenarios/OldDuke/OldDuchests/OldDuchestTP.cs:132 — OldDuchestTP.Update has cognitive complexity 46 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaDestroyerServant.UpdateEmerge (cognitive 45) · ×1
  • KikasaDestroyerServant.UpdateEmerge (cognitive 45) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:289 — KikasaDestroyerServant.UpdateEmerge has cognitive complexity 45 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaEaterServant.UpdateRiftRam (cognitive 45) · ×1
  • KikasaEaterServant.UpdateRiftRam (cognitive 45) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:587 — KikasaEaterServant.UpdateRiftRam has cognitive complexity 45 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaLakeFX.UpdateSink (cognitive 45) · ×1
  • KikasaLakeFX.UpdateSink (cognitive 45) Content/LegendWeapon/KikasaLegend/KikasaVaults/KikasaLakeFX.cs:278 — KikasaLakeFX.UpdateSink has cognitive complexity 45 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FishronIntroState.OnUpdate (cognitive 45) · ×1
  • FishronIntroState.OnUpdate (cognitive 45) Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronIntroState.cs:44 — FishronIntroState.OnUpdate has cognitive complexity 45 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · L3Content.RouteGalleryWells (cognitive 45) · ×1
  • L3Content.RouteGalleryWells (cognitive 45) Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Content.cs:621 — L3Content.RouteGalleryWells has cognitive complexity 45 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DrownedTurnkey.UpdateBurst (cognitive 45) · ×1
  • DrownedTurnkey.UpdateBurst (cognitive 45) Content/Scenarios/Dungeonworld/NPCs/Elites/DrownedTurnkey.cs:454 — DrownedTurnkey.UpdateBurst has cognitive complexity 45 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HerbFarmerTP.ScanWorkArea (cognitive 44) · ×1
  • HerbFarmerTP.ScanWorkArea (cognitive 44) Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerTP.cs:273 — HerbFarmerTP.ScanWorkArea has cognitive complexity 44 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaGunServant.UpdateEmerge (cognitive 44) · ×1
  • KikasaGunServant.UpdateEmerge (cognitive 44) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:336 — KikasaGunServant.UpdateEmerge has cognitive complexity 44 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BssCoilOrbitState.OnUpdate (cognitive 44) · ×1
  • BssCoilOrbitState.OnUpdate (cognitive 44) Content/NPCs/BloomsandSerpents/States/BssCoilOrbitState.cs:61 — BssCoilOrbitState.OnUpdate has cognitive complexity 44 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GolemIntroState.OnUpdate (cognitive 44) · ×1
  • GolemIntroState.OnUpdate (cognitive 44) Content/NPCs/BrutalNPCs/BrutalGolem/States/GolemIntroState.cs:26 — GolemIntroState.OnUpdate has cognitive complexity 44 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KingSlimePursuitBurrowState.OnUpdate (cognitive 44) · ×1
  • KingSlimePursuitBurrowState.OnUpdate (cognitive 44) Content/NPCs/BrutalNPCs/BrutalKingSlime/States/KingSlimePursuitBurrowState.cs:40 — KingSlimePursuitBurrowState.OnUpdate has cognitive complexity 44 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · QueenBallroomStepState.OnUpdate (cognitive 44) · ×1
  • QueenBallroomStepState.OnUpdate (cognitive 44) Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenBallroomStepState.cs:51 — QueenBallroomStepState.OnUpdate has cognitive complexity 44 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SeaShrimpBubbleCurtainState.OnUpdate (cognitive 44) · ×1
  • SeaShrimpBubbleCurtainState.OnUpdate (cognitive 44) Content/NPCs/SeaShrimp/States/SeaShrimpBubbleCurtainState.cs:47 — SeaShrimpBubbleCurtainState.OnUpdate has cognitive complexity 44 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · VictorRiftPortalProj.SpawnAmbientParticles (cognitive 44) · ×1
  • VictorRiftPortalProj.SpawnAmbientParticles (cognitive 44) Content/NPCs/Victors/VictorRiftPortalProj.cs:239 — VictorRiftPortalProj.SpawnAmbientParticles has cognitive complexity 44 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HackNetworkTarget.TryCapture (cognitive 43) · ×1
  • HackNetworkTarget.TryCapture (cognitive 43) Content/HackTimes/HackTimeNetSync.cs:212 — HackNetworkTarget.TryCapture has cognitive complexity 43 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · AutoCrafterTP.ConsumeIngredients (cognitive 43) · ×1
  • AutoCrafterTP.ConsumeIngredients (cognitive 43) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterTP.cs:436 — AutoCrafterTP.ConsumeIngredients has cognitive complexity 43 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaBladeServant.UpdateEmerge (cognitive 43) · ×1
  • KikasaBladeServant.UpdateEmerge (cognitive 43) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:325 — KikasaBladeServant.UpdateEmerge has cognitive complexity 43 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaBoomerangServant.UpdateHands (cognitive 43) · ×1
  • KikasaBoomerangServant.UpdateHands (cognitive 43) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:671 — KikasaBoomerangServant.UpdateHands has cognitive complexity 43 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaBowServant.UpdateEmerge (cognitive 43) · ×1
  • KikasaBowServant.UpdateEmerge (cognitive 43) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:300 — KikasaBowServant.UpdateEmerge has cognitive complexity 43 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaFlailServant.UpdateHands (cognitive 43) · ×1
  • KikasaFlailServant.UpdateHands (cognitive 43) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:690 — KikasaFlailServant.UpdateHands has cognitive complexity 43 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaDeerclopsServant.UpdateRoar (cognitive 43) · ×1
  • KikasaDeerclopsServant.UpdateRoar (cognitive 43) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:765 — KikasaDeerclopsServant.UpdateRoar has cognitive complexity 43 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaFesterSerpentServant.UpdateCystSweep (cognitive 43) · ×1
  • KikasaFesterSerpentServant.UpdateCystSweep (cognitive 43) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:514 — KikasaFesterSerpentServant.UpdateCystSweep has cognitive complexity 43 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaHud.Update (cognitive 43) · ×1
  • KikasaHud.Update (cognitive 43) Content/LegendWeapon/KikasaLegend/UI/KikasaHud.cs:264 — KikasaHud.Update has cognitive complexity 43 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaServantWheelUI.DrawInfoPanelForHovered (cognitive 43) · ×1
  • KikasaServantWheelUI.DrawInfoPanelForHovered (cognitive 43) Content/LegendWeapon/KikasaLegend/UI/ServantWheel/KikasaServantWheelUI.cs:352 — KikasaServantWheelUI.DrawInfoPanelForHovered has cognitive complexity 43 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OnikiriTutorialRenderer.BuildAndDrawButtons (cognitive 43) · ×1
  • OnikiriTutorialRenderer.BuildAndDrawButtons (cognitive 43) Content/LegendWeapon/OnikiriLegend/Tutorial/OnikiriTutorialRenderer.cs:376 — OnikiriTutorialRenderer.BuildAndDrawButtons has cognitive complexity 43 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FishronSharkronStrafeState.OnUpdate (cognitive 43) · ×1
  • FishronSharkronStrafeState.OnUpdate (cognitive 43) Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronSharkronStrafeState.cs:55 — FishronSharkronStrafeState.OnUpdate has cognitive complexity 43 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SylvanOutpost.IsValidGroundLevel (cognitive 43) · ×1
  • SylvanOutpost.IsValidGroundLevel (cognitive 43) Content/Structures/DatIO/SylvanOutpost.cs:238 — SylvanOutpost.IsValidGroundLevel has cognitive complexity 43 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HackNetworkTarget.TryResolve (cognitive 42) · ×1
  • HackNetworkTarget.TryResolve (cognitive 42) Content/HackTimes/HackTimeNetSync.cs:133 — HackNetworkTarget.TryResolve has cognitive complexity 42 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ApiaryUI.Update (cognitive 42) · ×1
  • ApiaryUI.Update (cognitive 42) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:123 — ApiaryUI.Update has cognitive complexity 42 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · AutoFisherTP.ScanWater (cognitive 42) · ×1
  • AutoFisherTP.ScanWater (cognitive 42) Content/Industrials/ElectricPowers/AutoFishers/AutoFisherTP.cs:282 — AutoFisherTP.ScanWater has cognitive complexity 42 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HerbFarmerUI.Update (cognitive 42) · ×1
  • HerbFarmerUI.Update (cognitive 42) Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs:131 — HerbFarmerUI.Update has cognitive complexity 42 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SolarCoreFistPlayer.PreUpdateMovement (cognitive 42) · ×1
  • SolarCoreFistPlayer.PreUpdateMovement (cognitive 42) Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFist.cs:202 — SolarCoreFistPlayer.PreUpdateMovement has cognitive complexity 42 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaRainUmbrella.UpdatePour (cognitive 42) · ×1
  • KikasaRainUmbrella.UpdatePour (cognitive 42) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:1006 — KikasaRainUmbrella.UpdatePour has cognitive complexity 42 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaThrowServant.UpdateHands (cognitive 42) · ×1
  • KikasaThrowServant.UpdateHands (cognitive 42) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:633 — KikasaThrowServant.UpdateHands has cognitive complexity 42 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaWhipServant.UpdateWhips (cognitive 42) · ×1
  • KikasaWhipServant.UpdateWhips (cognitive 42) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:646 — KikasaWhipServant.UpdateWhips has cognitive complexity 42 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaYoyoServant.UpdateHands (cognitive 42) · ×1
  • KikasaYoyoServant.UpdateHands (cognitive 42) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:666 — KikasaYoyoServant.UpdateHands has cognitive complexity 42 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaBloomSerpentServant.UpdateDashRam (cognitive 42) · ×1
  • KikasaBloomSerpentServant.UpdateDashRam (cognitive 42) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:419 — KikasaBloomSerpentServant.UpdateDashRam has cognitive complexity 42 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaCultistServant.UpdateRuneRite (cognitive 42) · ×1
  • KikasaCultistServant.UpdateRuneRite (cognitive 42) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:532 — KikasaCultistServant.UpdateRuneRite has cognitive complexity 42 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OnikiriPlayer.TryDash (cognitive 42) · ×1
  • OnikiriPlayer.TryDash (cognitive 42) Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs:940 — OnikiriPlayer.TryDash has cognitive complexity 42 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SteadyStockModule.OnPlayerUpdate (cognitive 42) · ×1
  • SteadyStockModule.OnPlayerUpdate (cognitive 42) Content/LegendWeapon/SHPCLegend/Modules/Stock/SteadyStockModule.cs:116 — SteadyStockModule.OnPlayerUpdate has cognitive complexity 42 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · WallOfFleshAI.UpdateAdvance (cognitive 42) · ×1
  • WallOfFleshAI.UpdateAdvance (cognitive 42) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/WallOfFleshAI.cs:287 — WallOfFleshAI.UpdateAdvance has cognitive complexity 42 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ScrapFusedFrenzyState.OnUpdate (cognitive 42) · ×1
  • ScrapFusedFrenzyState.OnUpdate (cognitive 42) Content/NPCs/ScrapCommanders/States/ScrapFusedFrenzyState.cs:39 — ScrapFusedFrenzyState.OnUpdate has cognitive complexity 42 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SeaShrimpDeathState.OnUpdate (cognitive 42) · ×1
  • SeaShrimpDeathState.OnUpdate (cognitive 42) Content/NPCs/SeaShrimp/States/SeaShrimpDeathState.cs:41 — SeaShrimpDeathState.OnUpdate has cognitive complexity 42 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DeepGaolWraith.UpdateFlail (cognitive 42) · ×1
  • DeepGaolWraith.UpdateFlail (cognitive 42) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:1104 — DeepGaolWraith.UpdateFlail has cognitive complexity 42 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SvgPathPen.Flatten (cognitive 42) · ×1
  • SvgPathPen.Flatten (cognitive 42) Content/UIs/UIEffect/SvgPathPen.cs:185 — SvgPathPen.Flatten has cognitive complexity 42 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DdMarksmanOmen.AI (cognitive 41) · ×1
  • DdMarksmanOmen.AI (cognitive 41) Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdMarksmanOmen.cs:81 — DdMarksmanOmen.AI has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ShimmerTransmuterUI.Update (cognitive 41) · ×1
  • ShimmerTransmuterUI.Update (cognitive 41) Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterUI.cs:137 — ShimmerTransmuterUI.Update has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaSeaShrimpServant.UpdateEmerge (cognitive 41) · ×1
  • KikasaSeaShrimpServant.UpdateEmerge (cognitive 41) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:322 — KikasaSeaShrimpServant.UpdateEmerge has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaTwinsServant.UpdateEmerge (cognitive 41) · ×1
  • KikasaTwinsServant.UpdateEmerge (cognitive 41) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:337 — KikasaTwinsServant.UpdateEmerge has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniDomainDeco.UpdatePetals (cognitive 41) · ×1
  • OniDomainDeco.UpdatePetals (cognitive 41) Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainDeco.cs:210 — OniDomainDeco.UpdatePetals has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniSigilUI.UpdateInteraction (cognitive 41) · ×1
  • OniSigilUI.UpdateInteraction (cognitive 41) Content/LegendWeapon/OnikiriLegend/UI/OniSigilUI.cs:339 — OniSigilUI.UpdateInteraction has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FishronVortexSnareState.OnUpdate (cognitive 41) · ×1
  • FishronVortexSnareState.OnUpdate (cognitive 41) Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronVortexGrabStates.cs:121 — FishronVortexSnareState.OnUpdate has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KingSlimePhaseShiftState.OnUpdate (cognitive 41) · ×1
  • KingSlimePhaseShiftState.OnUpdate (cognitive 41) Content/NPCs/BrutalNPCs/BrutalKingSlime/States/KingSlimePhaseShiftState.cs:35 — KingSlimePhaseShiftState.OnUpdate has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CultistStarBead.AI (cognitive 41) · ×1
  • CultistStarBead.AI (cognitive 41) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistStarBead.cs:64 — CultistStarBead.AI has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TwinsCombinedAttackState.ExecuteBurstPhase (cognitive 41) · ×1
  • TwinsCombinedAttackState.ExecuteBurstPhase (cognitive 41) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsCombinedAttackState.cs:240 — TwinsCombinedAttackState.ExecuteBurstPhase has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ScrapSweepBeam.AI (cognitive 41) · ×1
  • ScrapSweepBeam.AI (cognitive 41) Content/NPCs/ScrapCommanders/Projectiles/ScrapSweepBeam.cs:121 — ScrapSweepBeam.AI has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ScrapCommander.DrawGlowLayer (cognitive 41) · ×1
  • ScrapCommander.DrawGlowLayer (cognitive 41) Content/NPCs/ScrapCommanders/ScrapCommander.cs:819 — ScrapCommander.DrawGlowLayer has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SeaShrimpBubbleBatState.OnUpdate (cognitive 41) · ×1
  • SeaShrimpBubbleBatState.OnUpdate (cognitive 41) Content/NPCs/SeaShrimp/States/SeaShrimpBubbleBatState.cs:37 — SeaShrimpBubbleBatState.OnUpdate has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SeaShrimpSkyLeapState.OnUpdate (cognitive 41) · ×1
  • SeaShrimpSkyLeapState.OnUpdate (cognitive 41) Content/NPCs/SeaShrimp/States/SeaShrimpSkyLeapState.cs:40 — SeaShrimpSkyLeapState.OnUpdate has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Prefab.CollectSockets (cognitive 41) · ×1
  • Prefab.CollectSockets (cognitive 41) Content/Scenarios/Dungeonworld/Gen/Prefabs/Prefab.cs:84 — Prefab.CollectSockets has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Undrowned.UpdateFloodRite (cognitive 41) · ×1
  • Undrowned.UpdateFloodRite (cognitive 41) Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:1414 — Undrowned.UpdateFloodRite has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · WheelTutorialLead.UpdateUI (cognitive 41) · ×1
  • WheelTutorialLead.UpdateUI (cognitive 41) Content/Scenarios/Shepel/CybCourses/WheelTutorialLead.cs:156 — WheelTutorialLead.UpdateUI has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SylvanOutpost.RepairFoundation (cognitive 41) · ×1
  • SylvanOutpost.RepairFoundation (cognitive 41) Content/Structures/DatIO/SylvanOutpost.cs:457 — SylvanOutpost.RepairFoundation has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EclStrikeOmen.AI (cognitive 40) · ×1
  • EclStrikeOmen.AI (cognitive 40) Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclStrikeOmen.cs:73 — EclStrikeOmen.AI 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.
D2 · Cognitive Complexity · GsChainGunHeld.AI (cognitive 40) · ×1
  • GsChainGunHeld.AI (cognitive 40) Content/GameModes/GodSmith/Weapons/Specials/GsChainGun.cs:86 — GsChainGunHeld.AI 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.
D2 · Cognitive Complexity · CrusherUI.Update (cognitive 40) · ×1
  • CrusherUI.Update (cognitive 40) Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:133 — CrusherUI.Update 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.
D2 · Cognitive Complexity · IncineratorUI.Update (cognitive 40) · ×1
  • IncineratorUI.Update (cognitive 40) Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:139 — IncineratorUI.Update 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.
D2 · Cognitive Complexity · RecyclerUI.Update (cognitive 40) · ×1
  • RecyclerUI.Update (cognitive 40) Content/Industrials/ElectricPowers/Recyclers/RecyclerUI.cs:134 — RecyclerUI.Update 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.
D2 · Cognitive Complexity · AtlasSkillSea.HandleMouseInput (cognitive 40) · ×1
  • AtlasSkillSea.HandleMouseInput (cognitive 40) Content/LegendWeapon/HalibutLegend/UI/Atlas/AtlasSkillSea.cs:351 — AtlasSkillSea.HandleMouseInput 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.
D2 · Cognitive Complexity · KikasaBoomerangServant.UpdateEmerge (cognitive 40) · ×1
  • KikasaBoomerangServant.UpdateEmerge (cognitive 40) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:324 — KikasaBoomerangServant.UpdateEmerge 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.
D2 · Cognitive Complexity · KikasaFlailServant.UpdateEmerge (cognitive 40) · ×1
  • KikasaFlailServant.UpdateEmerge (cognitive 40) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:321 — KikasaFlailServant.UpdateEmerge 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.
D2 · Cognitive Complexity · KikasaThrowServant.UpdateEmerge (cognitive 40) · ×1
  • KikasaThrowServant.UpdateEmerge (cognitive 40) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:287 — KikasaThrowServant.UpdateEmerge 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.
D2 · Cognitive Complexity · KikasaYoyoServant.UpdateEmerge (cognitive 40) · ×1
  • KikasaYoyoServant.UpdateEmerge (cognitive 40) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:319 — KikasaYoyoServant.UpdateEmerge 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.
D2 · Cognitive Complexity · KikasaBrainServant.UpdateEmerge (cognitive 40) · ×1
  • KikasaBrainServant.UpdateEmerge (cognitive 40) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:397 — KikasaBrainServant.UpdateEmerge 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.
D2 · Cognitive Complexity · KikasaDeerclopsServant.UpdateEmerge (cognitive 40) · ×1
  • KikasaDeerclopsServant.UpdateEmerge (cognitive 40) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:319 — KikasaDeerclopsServant.UpdateEmerge 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.
D2 · Cognitive Complexity · KikasaFishronServant.UpdateBubbleRing (cognitive 40) · ×1
  • KikasaFishronServant.UpdateBubbleRing (cognitive 40) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:755 — KikasaFishronServant.UpdateBubbleRing 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.
D2 · Cognitive Complexity · KikasaMoonVesselWhip.AI (cognitive 40) · ×1
  • KikasaMoonVesselWhip.AI (cognitive 40) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonVesselWhip.cs:73 — KikasaMoonVesselWhip.AI 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.
D2 · Cognitive Complexity · KikasaServantPlayer.SaveData (cognitive 40) · ×1
  • KikasaServantPlayer.SaveData (cognitive 40) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaServantPlayer.cs:489 — KikasaServantPlayer.SaveData 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.
D2 · Cognitive Complexity · KikasaThrallProj.UpdateGather (cognitive 40) · ×1
  • KikasaThrallProj.UpdateGather (cognitive 40) Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallProj.cs:298 — KikasaThrallProj.UpdateGather 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.
D2 · Cognitive Complexity · MoldProcessingUI.Update (cognitive 40) · ×1
  • MoldProcessingUI.Update (cognitive 40) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingUI.cs:122 — MoldProcessingUI.Update 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.
D2 · Cognitive Complexity · ProbeAI.AI (cognitive 40) · ×1
  • ProbeAI.AI (cognitive 40) Content/NPCs/BrutalNPCs/BrutalDestroyer/ProbeAI.cs:30 — ProbeAI.AI 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.
D2 · Cognitive Complexity · QueenCrystalCathedralState.OnUpdate (cognitive 40) · ×1
  • QueenCrystalCathedralState.OnUpdate (cognitive 40) Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenCrystalCathedralState.cs:56 — QueenCrystalCathedralState.OnUpdate 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.
D2 · Cognitive Complexity · QueenSpikeRondoState.OnUpdate (cognitive 40) · ×1
  • QueenSpikeRondoState.OnUpdate (cognitive 40) Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenSpikeRondoState.cs:55 — QueenSpikeRondoState.OnUpdate 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.
D2 · Cognitive Complexity · FssDeathState.OnUpdate (cognitive 40) · ×1
  • FssDeathState.OnUpdate (cognitive 40) Content/NPCs/FestersandSerpents/States/FssDeathState.cs:44 — FssDeathState.OnUpdate 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.
D2 · Cognitive Complexity · CrabulonCommandController.HandleInput (cognitive 40) · ×1
  • CrabulonCommandController.HandleInput (cognitive 40) Content/NPCs/Modifys/Crabulons/CrabulonUIs/CrabulonCommandUI.cs:137 — CrabulonCommandController.HandleInput 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.
D2 · Cognitive Complexity · ScrapPhaseTransitionState.OnUpdate (cognitive 40) · ×1
  • ScrapPhaseTransitionState.OnUpdate (cognitive 40) Content/NPCs/ScrapCommanders/States/ScrapPhaseTransitionState.cs:34 — ScrapPhaseTransitionState.OnUpdate 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.
D2 · Cognitive Complexity · ScrapSawLaunchState.OnUpdate (cognitive 40) · ×1
  • ScrapSawLaunchState.OnUpdate (cognitive 40) Content/NPCs/ScrapCommanders/States/ScrapSawLaunchState.cs:36 — ScrapSawLaunchState.OnUpdate 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.
D2 · Cognitive Complexity · VictorClinicPanel.UpdateInteraction (cognitive 40) · ×1
  • VictorClinicPanel.UpdateInteraction (cognitive 40) Content/NPCs/Victors/UIs/VictorClinicPanel.cs:182 — VictorClinicPanel.UpdateInteraction 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.
D2 · Cognitive Complexity · RotmireWritheProj.AI (cognitive 39) · ×1
  • RotmireWritheProj.AI (cognitive 39) Content/GameModes/BrutalMobs/Ambience/Rotmire/Projectiles/RotmireWritheProj.cs:89 — RotmireWritheProj.AI 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.
D2 · Cognitive Complexity · VerdantMireScheduler.TryFindMireAnchor (cognitive 39) · ×1
  • VerdantMireScheduler.TryFindMireAnchor (cognitive 39) Content/GameModes/BrutalMobs/Ambience/Verdant/VerdantMireScheduler.cs:79 — VerdantMireScheduler.TryFindMireAnchor 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.
D2 · Cognitive Complexity · PrtBoardHookProj.AI (cognitive 39) · ×1
  • PrtBoardHookProj.AI (cognitive 39) Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtBoardHookProj.cs:77 — PrtBoardHookProj.AI 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.
D2 · Cognitive Complexity · WaterScannable.CountNearbyBiomeTiles (cognitive 39) · ×1
  • WaterScannable.CountNearbyBiomeTiles (cognitive 39) Content/HackTimes/Scannables/WaterScannable.cs:161 — WaterScannable.CountNearbyBiomeTiles 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.
D2 · Cognitive Complexity · AutoCrafterUI.Update (cognitive 39) · ×1
  • AutoCrafterUI.Update (cognitive 39) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:152 — AutoCrafterUI.Update 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.
D2 · Cognitive Complexity · SolarCoreFistRender.EndEntityDraw (cognitive 39) · ×1
  • SolarCoreFistRender.EndEntityDraw (cognitive 39) Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFistRender.cs:24 — SolarCoreFistRender.EndEntityDraw 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.
D2 · Cognitive Complexity · ShatterfangHeld.HandlePhaseEvents (cognitive 39) · ×1
  • ShatterfangHeld.HandlePhaseEvents (cognitive 39) Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:372 — ShatterfangHeld.HandlePhaseEvents 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.
D2 · Cognitive Complexity · HalibutReset.UpdateShow (cognitive 39) · ×1
  • HalibutReset.UpdateShow (cognitive 39) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:460 — HalibutReset.UpdateShow 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.
D2 · Cognitive Complexity · AtlasDomainEyes.Draw (cognitive 39) · ×1
  • AtlasDomainEyes.Draw (cognitive 39) Content/LegendWeapon/HalibutLegend/UI/Atlas/AtlasDomainEyes.cs:202 — AtlasDomainEyes.Draw 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.
D2 · Cognitive Complexity · KikasaDestroyerServant.UpdateDiveRam (cognitive 39) · ×1
  • KikasaDestroyerServant.UpdateDiveRam (cognitive 39) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:666 — KikasaDestroyerServant.UpdateDiveRam 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.
D2 · Cognitive Complexity · KikasaGolemServant.UpdateEmerge (cognitive 39) · ×1
  • KikasaGolemServant.UpdateEmerge (cognitive 39) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:315 — KikasaGolemServant.UpdateEmerge 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.
D2 · Cognitive Complexity · KikasaPlanteraServant.UpdateRelocate (cognitive 39) · ×1
  • KikasaPlanteraServant.UpdateRelocate (cognitive 39) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:649 — KikasaPlanteraServant.UpdateRelocate 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.
D2 · Cognitive Complexity · PRT_CrimsonBloodStain.TryEnterStuck (cognitive 39) · ×1
  • PRT_CrimsonBloodStain.TryEnterStuck (cognitive 39) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendParticles.cs:269 — PRT_CrimsonBloodStain.TryEnterStuck 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.
D2 · Cognitive Complexity · CrimsonSweepSlash.UpdateCombo (cognitive 39) · ×1
  • CrimsonSweepSlash.UpdateCombo (cognitive 39) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:422 — CrimsonSweepSlash.UpdateCombo 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.
D2 · Cognitive Complexity · OniSlash.UpdateCombo (cognitive 39) · ×1
  • OniSlash.UpdateCombo (cognitive 39) Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:548 — OniSlash.UpdateCombo 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.
D2 · Cognitive Complexity · SHPCSandCurtainProj.AI (cognitive 39) · ×1
  • SHPCSandCurtainProj.AI (cognitive 39) Content/LegendWeapon/SHPCLegend/Modules/Barrel/SandstormBarrelModule.cs:75 — SHPCSandCurtainProj.AI 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.
D2 · Cognitive Complexity · EmpressPhaseTransitionState.OnUpdate (cognitive 39) · ×1
  • EmpressPhaseTransitionState.OnUpdate (cognitive 39) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/States/EmpressPhaseTransitionState.cs:34 — EmpressPhaseTransitionState.OnUpdate 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.
D2 · Cognitive Complexity · SeaShrimpVortexWallState.OnUpdate (cognitive 39) · ×1
  • SeaShrimpVortexWallState.OnUpdate (cognitive 39) Content/NPCs/SeaShrimp/States/SeaShrimpVortexWallState.cs:39 — SeaShrimpVortexWallState.OnUpdate 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.
D2 · Cognitive Complexity · GaolBossRoomWatcher.PostUpdateNPCs (cognitive 39) · ×1
  • GaolBossRoomWatcher.PostUpdateNPCs (cognitive 39) Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolBossRoomWatcher.cs:97 — GaolBossRoomWatcher.PostUpdateNPCs 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.
D2 · Cognitive Complexity · L3Rooms.BuildVault (cognitive 39) · ×1
  • L3Rooms.BuildVault (cognitive 39) Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Rooms.cs:337 — L3Rooms.BuildVault 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.
D2 · Cognitive Complexity · HadalTerrainCarver.ApplyBioSpots (cognitive 39) · ×1
  • HadalTerrainCarver.ApplyBioSpots (cognitive 39) Content/Scenarios/Hadalworld/Gen/Core/HadalTerrainCarver.cs:474 — HadalTerrainCarver.ApplyBioSpots 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.
D2 · Cognitive Complexity · KiyumeLampEvents.UpdateFall (cognitive 39) · ×1
  • KiyumeLampEvents.UpdateFall (cognitive 39) Content/Scenarios/Kiyume/Ambience/KiyumeLampEvents.cs:126 — KiyumeLampEvents.UpdateFall 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.
D2 · Cognitive Complexity · HackTimeTutorialLead.UpdateUI (cognitive 39) · ×1
  • HackTimeTutorialLead.UpdateUI (cognitive 39) Content/Scenarios/Shepel/CybCourses/HackTimeTutorialLead.cs:228 — HackTimeTutorialLead.UpdateUI 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.
D2 · Cognitive Complexity · OverhaulSettingsUI.DrawContent (cognitive 39) · ×1
  • OverhaulSettingsUI.DrawContent (cognitive 39) Content/UIs/OverhaulSettings/OverhaulSettingsUI.cs:507 — OverhaulSettingsUI.DrawContent 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.
D2 · Cognitive Complexity · BlessingWheelUI.Update (cognitive 38) · ×1
  • BlessingWheelUI.Update (cognitive 38) Content/GameModes/Blessings/UI/BlessingWheelUI.cs:125 — BlessingWheelUI.Update has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PlayerScannable.BuildScanData (cognitive 38) · ×1
  • PlayerScannable.BuildScanData (cognitive 38) Content/HackTimes/Scannables/PlayerScannable.cs:58 — PlayerScannable.BuildScanData has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ItemPipelineNetwork.Rebuild (cognitive 38) · ×1
  • ItemPipelineNetwork.Rebuild (cognitive 38) Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineNetwork.cs:93 — ItemPipelineNetwork.Rebuild has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CloudRide.UpdateCloudFishParticles (cognitive 38) · ×1
  • CloudRide.UpdateCloudFishParticles (cognitive 38) Content/LegendWeapon/HalibutLegend/FishSkills/FishCloud.cs:191 — CloudRide.UpdateCloudFishParticles has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaDeerclopsServant.UpdateFollow (cognitive 38) · ×1
  • KikasaDeerclopsServant.UpdateFollow (cognitive 38) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:508 — KikasaDeerclopsServant.UpdateFollow has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaEmpressServant.GetArmFrames (cognitive 38) · ×1
  • KikasaEmpressServant.GetArmFrames (cognitive 38) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:848 — KikasaEmpressServant.GetArmFrames has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaPrimeServant.UpdateLaser (cognitive 38) · ×1
  • KikasaPrimeServant.UpdateLaser (cognitive 38) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:782 — KikasaPrimeServant.UpdateLaser has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaSeaShrimpServant.UpdateTailVolley (cognitive 38) · ×1
  • KikasaSeaShrimpServant.UpdateTailVolley (cognitive 38) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:568 — KikasaSeaShrimpServant.UpdateTailVolley has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CrimsonRendSlash.UpdateCombo (cognitive 38) · ×1
  • CrimsonRendSlash.UpdateCombo (cognitive 38) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:612 — CrimsonRendSlash.UpdateCombo has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CyberspacePlayer.Update (cognitive 38) · ×1
  • CyberspacePlayer.Update (cognitive 38) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspacePlayer.cs:437 — CyberspacePlayer.Update has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · RapidBarrelModule.OnPlayerUpdate (cognitive 38) · ×1
  • RapidBarrelModule.OnPlayerUpdate (cognitive 38) Content/LegendWeapon/SHPCLegend/Modules/Barrel/RapidBarrelModule.cs:127 — RapidBarrelModule.OnPlayerUpdate has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BssSandSpitState.OnUpdate (cognitive 38) · ×1
  • BssSandSpitState.OnUpdate (cognitive 38) Content/NPCs/BloomsandSerpents/States/BssSandSpitState.cs:41 — BssSandSpitState.OnUpdate has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BssSkyWeaveState.OnUpdate (cognitive 38) · ×1
  • BssSkyWeaveState.OnUpdate (cognitive 38) Content/NPCs/BloomsandSerpents/States/BssSkyWeaveState.cs:45 — BssSkyWeaveState.OnUpdate has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DeerclopsWhiteoutState.OnUpdate (cognitive 38) · ×1
  • DeerclopsWhiteoutState.OnUpdate (cognitive 38) Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsWhiteoutState.cs:34 — DeerclopsWhiteoutState.OnUpdate has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · WofTongueGrabState.UpdateChew (cognitive 38) · ×1
  • WofTongueGrabState.UpdateChew (cognitive 38) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/States/WofTongueGrabState.cs:309 — WofTongueGrabState.UpdateChew has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FssCoilCascadeState.OnUpdate (cognitive 38) · ×1
  • FssCoilCascadeState.OnUpdate (cognitive 38) Content/NPCs/FestersandSerpents/States/FssCoilCascadeState.cs:55 — FssCoilCascadeState.OnUpdate has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PlayerDeath.ExecuteScapeGhostAuthority (cognitive 38) · ×1
  • PlayerDeath.ExecuteScapeGhostAuthority (cognitive 38) Content/Players/PlayerDeath.cs:186 — PlayerDeath.ExecuteScapeGhostAuthority has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DeepGaolWraith.UpdateDeath (cognitive 38) · ×1
  • DeepGaolWraith.UpdateDeath (cognitive 38) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:1498 — DeepGaolWraith.UpdateDeath has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KiyumeHound.UpdatePresentation (cognitive 38) · ×1
  • KiyumeHound.UpdatePresentation (cognitive 38) Content/Scenarios/Kiyume/NPCs/KiyumeHound.cs:826 — KiyumeHound.UpdatePresentation has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EbnBarsDisplay.DrawMana (cognitive 38) · ×1
  • EbnBarsDisplay.DrawMana (cognitive 38) Content/Scenarios/SupCal/End/EternalBlazingNow/EbnBarsDisplay.cs:324 — EbnBarsDisplay.DrawMana has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PmkClawCrossProj.AI (cognitive 37) · ×1
  • PmkClawCrossProj.AI (cognitive 37) Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkClawCrossProj.cs:74 — PmkClawCrossProj.AI has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · AutoCrafterUI.DrawRecipeList (cognitive 37) · ×1
  • AutoCrafterUI.DrawRecipeList (cognitive 37) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:433 — AutoCrafterUI.DrawRecipeList has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MushroomFarmerTP.VisualScanField (cognitive 37) · ×1
  • MushroomFarmerTP.VisualScanField (cognitive 37) Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:683 — MushroomFarmerTP.VisualScanField has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · WingsOfInterferencePlayer.DetectIntersections (cognitive 37) · ×1
  • WingsOfInterferencePlayer.DetectIntersections (cognitive 37) Content/Items/Accessories/BrutalRelics/EmpressOfLight/WingsOfInterference.cs:518 — WingsOfInterferencePlayer.DetectIntersections has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PallbearerBoomerang.AI (cognitive 37) · ×1
  • PallbearerBoomerang.AI (cognitive 37) Content/Items/Ranged/Pallbearer.cs:592 — PallbearerBoomerang.AI has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaReset.UpdateShow (cognitive 37) · ×1
  • KikasaReset.UpdateShow (cognitive 37) Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaReset.cs:448 — KikasaReset.UpdateShow has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaFishronServant.UpdateEmerge (cognitive 37) · ×1
  • KikasaFishronServant.UpdateEmerge (cognitive 37) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:327 — KikasaFishronServant.UpdateEmerge has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniDomainPlayer.UpdateFlipping (cognitive 37) · ×1
  • OniDomainPlayer.UpdateFlipping (cognitive 37) Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainPlayer.cs:546 — OniDomainPlayer.UpdateFlipping has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BrainHeartAttackState.OnUpdate (cognitive 37) · ×1
  • BrainHeartAttackState.OnUpdate (cognitive 37) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainHeartAttackState.cs:64 — BrainHeartAttackState.OnUpdate has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BrainMirrorFeintState.OnUpdate (cognitive 37) · ×1
  • BrainMirrorFeintState.OnUpdate (cognitive 37) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainMirrorFeintState.cs:45 — BrainMirrorFeintState.OnUpdate has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SkeletronSkullRainTeleportState.UpdateRound (cognitive 37) · ×1
  • SkeletronSkullRainTeleportState.UpdateRound (cognitive 37) Content/NPCs/BrutalNPCs/BrutalSkeletron/States/SkeletronSkullRainTeleportState.cs:63 — SkeletronSkullRainTeleportState.UpdateRound has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · StratosFallingStarProj.AI (cognitive 36) · ×1
  • StratosFallingStarProj.AI (cognitive 36) Content/GameModes/BrutalMobs/Ambience/Stratos/Projectiles/StratosFallingStarProj.cs:99 — StratosFallingStarProj.AI has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SunkenduneSandfallProj.AI (cognitive 36) · ×1
  • SunkenduneSandfallProj.AI (cognitive 36) Content/GameModes/BrutalMobs/Ambience/Sunkendune/Projectiles/SunkenduneSandfallProj.cs:94 — SunkenduneSandfallProj.AI has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FrmOrnamentRowOmen.AI (cognitive 36) · ×1
  • FrmOrnamentRowOmen.AI (cognitive 36) Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmOrnamentRowOmen.cs:75 — FrmOrnamentRowOmen.AI has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HackPanelRenderer.DrawRowForeground (cognitive 36) · ×1
  • HackPanelRenderer.DrawRowForeground (cognitive 36) Content/HackTimes/HackPanelRenderer.cs:659 — HackPanelRenderer.DrawRowForeground has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SlimeVatUI.Update (cognitive 36) · ×1
  • SlimeVatUI.Update (cognitive 36) Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:125 — SlimeVatUI.Update has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CryoTurretTP.UpdateCryoField (cognitive 36) · ×1
  • CryoTurretTP.UpdateCryoField (cognitive 36) Content/Industrials/ElectricPowers/Turrets/CryoTurrets/CryoTurretTP.cs:125 — CryoTurretTP.UpdateCryoField has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CosmicEddies.AI (cognitive 36) · ×1
  • CosmicEddies.AI (cognitive 36) Content/Items/Ranged/AnnihilatingUniverses/CosmicEddies.cs:33 — CosmicEddies.AI has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · AvalancheM60Held.Fire (cognitive 36) · ×1
  • AvalancheM60Held.Fire (cognitive 36) Content/Items/Ranged/AvalancheM60.cs:145 — AvalancheM60Held.Fire has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaPlayerDrownFX.UpdateHands (cognitive 36) · ×1
  • KikasaPlayerDrownFX.UpdateHands (cognitive 36) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaPlayerDrownFX.cs:313 — KikasaPlayerDrownFX.UpdateHands has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaRainRender.DrawBloodBodies (cognitive 36) · ×1
  • KikasaRainRender.DrawBloodBodies (cognitive 36) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:102 — KikasaRainRender.DrawBloodBodies has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaHalibutServant.UpdateGun (cognitive 36) · ×1
  • KikasaHalibutServant.UpdateGun (cognitive 36) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:794 — KikasaHalibutServant.UpdateGun has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaSHPCServant.UpdateGun (cognitive 36) · ×1
  • KikasaSHPCServant.UpdateGun (cognitive 36) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:772 — KikasaSHPCServant.UpdateGun has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaSpearServant.UpdateEmerge (cognitive 36) · ×1
  • KikasaSpearServant.UpdateEmerge (cognitive 36) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:287 — KikasaSpearServant.UpdateEmerge has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaWhipServant.UpdateEmerge (cognitive 36) · ×1
  • KikasaWhipServant.UpdateEmerge (cognitive 36) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:295 — KikasaWhipServant.UpdateEmerge has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaEyeServant.UpdateEmerge (cognitive 36) · ×1
  • KikasaEyeServant.UpdateEmerge (cognitive 36) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:247 — KikasaEyeServant.UpdateEmerge has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaTwinsServant.UpdateDissolve (cognitive 36) · ×1
  • KikasaTwinsServant.UpdateDissolve (cognitive 36) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:879 — KikasaTwinsServant.UpdateDissolve has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BrainIntroState.OnUpdate (cognitive 36) · ×1
  • BrainIntroState.OnUpdate (cognitive 36) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainIntroState.cs:43 — BrainIntroState.OnUpdate has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · L2CellRow.Build (cognitive 36) · ×1
  • L2CellRow.Build (cognitive 36) Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2CellRow.cs:79 — L2CellRow.Build has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · IndustrialSkyIslandGen.PopulateDeck (cognitive 36) · ×1
  • IndustrialSkyIslandGen.PopulateDeck (cognitive 36) Content/Structures/IndustrialSkyIslandGen.cs:242 — IndustrialSkyIslandGen.PopulateDeck has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CWRRef.BulkRestoreCalamityFlagsOr (cognitive 35) · ×1
  • CWRRef.BulkRestoreCalamityFlagsOr (cognitive 35) CWRRef.cs:1017 — CWRRef.BulkRestoreCalamityFlagsOr 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.
D2 · Cognitive Complexity · BaseQuestAcceptUI.Update (cognitive 35) · ×1
  • BaseQuestAcceptUI.Update (cognitive 35) Content/EntrustManager/BaseQuestAcceptUI.cs:111 — BaseQuestAcceptUI.Update 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.
D2 · Cognitive Complexity · CindercragAmbience.UpdateAuthority (cognitive 35) · ×1
  • CindercragAmbience.UpdateAuthority (cognitive 35) Content/GameModes/BrutalMobs/Ambience/Cindercrag/CindercragAmbience.cs:208 — CindercragAmbience.UpdateAuthority 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.
D2 · Cognitive Complexity · DungeonDeepNPC.TickBoneLee (cognitive 35) · ×1
  • DungeonDeepNPC.TickBoneLee (cognitive 35) Content/GameModes/BrutalMobs/DungeonDeep/DungeonDeepNPC.Melee.cs:268 — DungeonDeepNPC.TickBoneLee 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.
D2 · Cognitive Complexity · MushroomFarmerTP.ScanWorkArea (cognitive 35) · ×1
  • MushroomFarmerTP.ScanWorkArea (cognitive 35) Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:189 — MushroomFarmerTP.ScanWorkArea 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.
D2 · Cognitive Complexity · SensorUI.Update (cognitive 35) · ×1
  • SensorUI.Update (cognitive 35) Content/Industrials/ElectricPowers/Sensors/SensorUI.cs:88 — SensorUI.Update 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.
D2 · Cognitive Complexity · ShatterfangHeld.InitStage (cognitive 35) · ×1
  • ShatterfangHeld.InitStage (cognitive 35) Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:133 — ShatterfangHeld.InitStage 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.
D2 · Cognitive Complexity · FishingFly.AI (cognitive 35) · ×1
  • FishingFly.AI (cognitive 35) Content/LegendWeapon/HalibutLegend/FishSkills/FishSwarm.cs:510 — FishingFly.AI 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.
D2 · Cognitive Complexity · KikasaMinionDrownFX.Draw (cognitive 35) · ×1
  • KikasaMinionDrownFX.Draw (cognitive 35) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaMinionDrownFX.cs:433 — KikasaMinionDrownFX.Draw 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.
D2 · Cognitive Complexity · KikasaEaterServant.UpdateEmerge (cognitive 35) · ×1
  • KikasaEaterServant.UpdateEmerge (cognitive 35) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:366 — KikasaEaterServant.UpdateEmerge 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.
D2 · Cognitive Complexity · KikasaMoonLordServant.UpdateDissolve (cognitive 35) · ×1
  • KikasaMoonLordServant.UpdateDissolve (cognitive 35) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:902 — KikasaMoonLordServant.UpdateDissolve 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.
D2 · Cognitive Complexity · KikasaPlanteraServant.UpdateHookPoses (cognitive 35) · ×1
  • KikasaPlanteraServant.UpdateHookPoses (cognitive 35) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1088 — KikasaPlanteraServant.UpdateHookPoses 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.
D2 · Cognitive Complexity · KikasaWallOfFleshServant.UpdateEmerge (cognitive 35) · ×1
  • KikasaWallOfFleshServant.UpdateEmerge (cognitive 35) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:292 — KikasaWallOfFleshServant.UpdateEmerge 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.
D2 · Cognitive Complexity · RibbonMeshBuilder.Build (cognitive 35) · ×1
  • RibbonMeshBuilder.Build (cognitive 35) Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/Geometry/RibbonMesh.cs:144 — RibbonMeshBuilder.Build 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.
D2 · Cognitive Complexity · SakuraKiriRenderer.Draw (cognitive 35) · ×1
  • SakuraKiriRenderer.Draw (cognitive 35) Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraKiriRenderer.cs:111 — SakuraKiriRenderer.Draw 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.
D2 · Cognitive Complexity · OniRegisterUI.UpdateInteraction (cognitive 35) · ×1
  • OniRegisterUI.UpdateInteraction (cognitive 35) Content/LegendWeapon/OnikiriLegend/UI/OniRegisterUI.cs:353 — OniRegisterUI.UpdateInteraction 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.
D2 · Cognitive Complexity · SHPCThermalHeatNPC.PreAI (cognitive 35) · ×1
  • SHPCThermalHeatNPC.PreAI (cognitive 35) Content/LegendWeapon/SHPCLegend/Modules/Optic/ThermalOpticModule.cs:273 — SHPCThermalHeatNPC.PreAI 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.
D2 · Cognitive Complexity · BssDeathState.OnUpdate (cognitive 35) · ×1
  • BssDeathState.OnUpdate (cognitive 35) Content/NPCs/BloomsandSerpents/States/BssDeathState.cs:36 — BssDeathState.OnUpdate 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.
D2 · Cognitive Complexity · DeerclopsGazeRoarState.OnUpdate (cognitive 35) · ×1
  • DeerclopsGazeRoarState.OnUpdate (cognitive 35) Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsGazeRoarState.cs:35 — DeerclopsGazeRoarState.OnUpdate 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.
D2 · Cognitive Complexity · EmpressAscensionState.OnUpdate (cognitive 35) · ×1
  • EmpressAscensionState.OnUpdate (cognitive 35) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/States/EmpressAscensionState.cs:51 — EmpressAscensionState.OnUpdate 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.
D2 · Cognitive Complexity · CultistOrreryRingProj.AI (cognitive 35) · ×1
  • CultistOrreryRingProj.AI (cognitive 35) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistOrreryRingProj.cs:65 — CultistOrreryRingProj.AI 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.
D2 · Cognitive Complexity · QBIntroState.OnUpdate (cognitive 35) · ×1
  • QBIntroState.OnUpdate (cognitive 35) Content/NPCs/BrutalNPCs/BrutalQueenBee/States/QBIntroState.cs:40 — QBIntroState.OnUpdate 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.
D2 · Cognitive Complexity · SkeletronBoneMaelstromState.UpdateBeats (cognitive 35) · ×1
  • SkeletronBoneMaelstromState.UpdateBeats (cognitive 35) Content/NPCs/BrutalNPCs/BrutalSkeletron/States/SkeletronBoneMaelstromState.cs:71 — SkeletronBoneMaelstromState.UpdateBeats 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.
D2 · Cognitive Complexity · TBUGShopUI.Update (cognitive 35) · ×1
  • TBUGShopUI.Update (cognitive 35) Content/NPCs/TBUGs/UIs/TBUGShopUI.cs:220 — TBUGShopUI.Update 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.
D2 · Cognitive Complexity · L5Leviathan.BuildCavity (cognitive 35) · ×1
  • L5Leviathan.BuildCavity (cognitive 35) Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Leviathan.cs:311 — L5Leviathan.BuildCavity 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.
D2 · Cognitive Complexity · FrmMeleeNPC.GingerActive (cognitive 34) · ×1
  • FrmMeleeNPC.GingerActive (cognitive 34) Content/GameModes/BrutalMobs/FrostMoon/FrmMeleeNPC.cs:417 — FrmMeleeNPC.GingerActive has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FrmPoseTelegraphProj.AI (cognitive 34) · ×1
  • FrmPoseTelegraphProj.AI (cognitive 34) Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmPoseTelegraphProj.cs:72 — FrmPoseTelegraphProj.AI has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GsHelmetNestSystem.AddFamily (cognitive 34) · ×1
  • GsHelmetNestSystem.AddFamily (cognitive 34) Content/GameModes/GodSmith/Armors/Reset/GsHelmetNest.cs:125 — GsHelmetNestSystem.AddFamily has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GsChargeBowHeld.WatchTierCues (cognitive 34) · ×1
  • GsChargeBowHeld.WatchTierCues (cognitive 34) Content/GameModes/GodSmith/Weapons/Bows/GsChargeBowHeld.cs:240 — GsChargeBowHeld.WatchTierCues has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MushroomFarmerUI.Update (cognitive 34) · ×1
  • MushroomFarmerUI.Update (cognitive 34) Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:114 — MushroomFarmerUI.Update has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PotionBeaconUI.Update (cognitive 34) · ×1
  • PotionBeaconUI.Update (cognitive 34) Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconUI.cs:116 — PotionBeaconUI.Update has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ProbeMatrixPlayer.UpdateSquad (cognitive 34) · ×1
  • ProbeMatrixPlayer.UpdateSquad (cognitive 34) Content/Items/Accessories/BrutalRelics/Destroyer/ProbeMatrixCore.cs:181 — ProbeMatrixPlayer.UpdateSquad has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaDreamHound.UpdateSprint (cognitive 34) · ×1
  • KikasaDreamHound.UpdateSprint (cognitive 34) Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamHound.cs:526 — KikasaDreamHound.UpdateSprint has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaDrownFX.UpdateHands (cognitive 34) · ×1
  • KikasaDrownFX.UpdateHands (cognitive 34) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:674 — KikasaDrownFX.UpdateHands has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaBrainServant.DrawBloodForms (cognitive 34) · ×1
  • KikasaBrainServant.DrawBloodForms (cognitive 34) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1265 — KikasaBrainServant.DrawBloodForms has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaDeerclopsServant.GetPoseFrame (cognitive 34) · ×1
  • KikasaDeerclopsServant.GetPoseFrame (cognitive 34) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:1025 — KikasaDeerclopsServant.GetPoseFrame has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaEmpressServant.UpdateEmerge (cognitive 34) · ×1
  • KikasaEmpressServant.UpdateEmerge (cognitive 34) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:245 — KikasaEmpressServant.UpdateEmerge has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaFesterSerpentServant.UpdateIchorVolley (cognitive 34) · ×1
  • KikasaFesterSerpentServant.UpdateIchorVolley (cognitive 34) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:419 — KikasaFesterSerpentServant.UpdateIchorVolley has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniSeverStrike.AcceptAuthoritySnapshot (cognitive 34) · ×1
  • OniSeverStrike.AcceptAuthoritySnapshot (cognitive 34) Content/LegendWeapon/OnikiriLegend/OniDismembers/OniSeverStrike.cs:936 — OniSeverStrike.AcceptAuthoritySnapshot has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniMeiUI.LogicUpdate (cognitive 34) · ×1
  • OniMeiUI.LogicUpdate (cognitive 34) Content/LegendWeapon/OnikiriLegend/UI/OniMeiUI.cs:345 — OniMeiUI.LogicUpdate has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DeerclopsDeathState.OnUpdate (cognitive 34) · ×1
  • DeerclopsDeathState.OnUpdate (cognitive 34) Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsDeathState.cs:47 — DeerclopsDeathState.OnUpdate has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DestroyerProbeMatrixState.ExecuteFirePhase (cognitive 34) · ×1
  • DestroyerProbeMatrixState.ExecuteFirePhase (cognitive 34) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerProbeMatrixState.cs:173 — DestroyerProbeMatrixState.ExecuteFirePhase has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · WofWallField.ComputeScanTargets (cognitive 34) · ×1
  • WofWallField.ComputeScanTargets (cognitive 34) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Core/WofWallField.cs:87 — WofWallField.ComputeScanTargets has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FssPortraitActor.DrawWorm (cognitive 34) · ×1
  • FssPortraitActor.DrawWorm (cognitive 34) Content/NPCs/FestersandSerpents/Rendering/FssPortrait.cs:135 — FssPortraitActor.DrawWorm has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BoneStitcher.UpdateScavenge (cognitive 34) · ×1
  • BoneStitcher.UpdateScavenge (cognitive 34) Content/Scenarios/Dungeonworld/NPCs/Elites/BoneStitcher.cs:247 — BoneStitcher.UpdateScavenge has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EbnBarsDisplay.DrawLife (cognitive 34) · ×1
  • EbnBarsDisplay.DrawLife (cognitive 34) Content/Scenarios/SupCal/End/EternalBlazingNow/EbnBarsDisplay.cs:181 — EbnBarsDisplay.DrawLife has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DuskhallAmbience.UpdateCandles (cognitive 33) · ×1
  • DuskhallAmbience.UpdateCandles (cognitive 33) Content/GameModes/BrutalMobs/Ambience/Duskhall/DuskhallAmbience.cs:313 — DuskhallAmbience.UpdateCandles 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.
D2 · Cognitive Complexity · EMPhaseAnchorProj.AI (cognitive 33) · ×1
  • EMPhaseAnchorProj.AI (cognitive 33) Content/GameModes/BrutalMobs/EliteMove/Projectiles/EMPhaseAnchorProj.cs:62 — EMPhaseAnchorProj.AI 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.
D2 · Cognitive Complexity · FrmMiniBossNPC.RamActive (cognitive 33) · ×1
  • FrmMiniBossNPC.RamActive (cognitive 33) Content/GameModes/BrutalMobs/FrostMoon/FrmMiniBossNPC.cs:378 — FrmMiniBossNPC.RamActive 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.
D2 · Cognitive Complexity · HackEffectTracker.UpdateAuthorityList (cognitive 33) · ×1
  • HackEffectTracker.UpdateAuthorityList (cognitive 33) Content/HackTimes/HackEffectTracker.cs:368 — HackEffectTracker.UpdateAuthorityList 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.
D2 · Cognitive Complexity · FluidInjectorTP.UpdateMachine (cognitive 33) · ×1
  • FluidInjectorTP.UpdateMachine (cognitive 33) Content/Industrials/ElectricPowers/FluidInjectors/FluidInjectorTP.cs:73 — FluidInjectorTP.UpdateMachine 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.
D2 · Cognitive Complexity · ThermalHeatHazeRender.CollectSources (cognitive 33) · ×1
  • ThermalHeatHazeRender.CollectSources (cognitive 33) Content/Industrials/Generator/Thermal/ThermalHeatHazeRender.cs:30 — ThermalHeatHazeRender.CollectSources 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.
D2 · Cognitive Complexity · RefractionWaltzPlayer.ReconcileLinks (cognitive 33) · ×1
  • RefractionWaltzPlayer.ReconcileLinks (cognitive 33) Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltz.cs:262 — RefractionWaltzPlayer.ReconcileLinks 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.
D2 · Cognitive Complexity · ArbiterManifestationSystem.EnsureSingleActor (cognitive 33) · ×1
  • ArbiterManifestationSystem.EnsureSingleActor (cognitive 33) Content/Items/Melee/Arbiters/ArbiterManifestationSystem.cs:266 — ArbiterManifestationSystem.EnsureSingleActor 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.
D2 · Cognitive Complexity · WGManifestationSystem.EnsureSingleActor (cognitive 33) · ×1
  • WGManifestationSystem.EnsureSingleActor (cognitive 33) Content/Items/Melee/WeaverGrievanceses/WGManifestationSystem.cs:258 — WGManifestationSystem.EnsureSingleActor 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.
D2 · Cognitive Complexity · MarbleShieldPlayer.BurstGuard (cognitive 33) · ×1
  • MarbleShieldPlayer.BurstGuard (cognitive 33) Content/Items/Stones/Marbles/MarbleShield.cs:179 — MarbleShieldPlayer.BurstGuard 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.
D2 · Cognitive Complexity · SeaDomainProj.AI (cognitive 33) · ×1
  • SeaDomainProj.AI (cognitive 33) Content/LegendWeapon/HalibutLegend/DomainSkills/SeaDomain.cs:177 — SeaDomainProj.AI 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.
D2 · Cognitive Complexity · HungryCompanionProjectile.AI (cognitive 33) · ×1
  • HungryCompanionProjectile.AI (cognitive 33) Content/LegendWeapon/HalibutLegend/FishSkills/FishHunger.cs:186 — HungryCompanionProjectile.AI 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.
D2 · Cognitive Complexity · HalibutAtlas.Update (cognitive 33) · ×1
  • HalibutAtlas.Update (cognitive 33) Content/LegendWeapon/HalibutLegend/UI/Atlas/HalibutAtlas.cs:186 — HalibutAtlas.Update 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.
D2 · Cognitive Complexity · KikasaDrownFX.RunCaptures (cognitive 33) · ×1
  • KikasaDrownFX.RunCaptures (cognitive 33) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:838 — KikasaDrownFX.RunCaptures 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.
D2 · Cognitive Complexity · KikasaZenithServant.UpdateBlade (cognitive 33) · ×1
  • KikasaZenithServant.UpdateBlade (cognitive 33) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:971 — KikasaZenithServant.UpdateBlade 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.
D2 · Cognitive Complexity · KikasaEaterServant.DrawRifts (cognitive 33) · ×1
  • KikasaEaterServant.DrawRifts (cognitive 33) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1377 — KikasaEaterServant.DrawRifts 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.
D2 · Cognitive Complexity · KikasaEmpressLance.AI (cognitive 33) · ×1
  • KikasaEmpressLance.AI (cognitive 33) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressLance.cs:105 — KikasaEmpressLance.AI 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.
D2 · Cognitive Complexity · KikasaKingSlimeServant.UpdateFollow (cognitive 33) · ×1
  • KikasaKingSlimeServant.UpdateFollow (cognitive 33) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:502 — KikasaKingSlimeServant.UpdateFollow 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.
D2 · Cognitive Complexity · KikasaMoonLordServant.UpdateEmerge (cognitive 33) · ×1
  • KikasaMoonLordServant.UpdateEmerge (cognitive 33) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:410 — KikasaMoonLordServant.UpdateEmerge 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.
D2 · Cognitive Complexity · KikasaPlanteraVine.AI (cognitive 33) · ×1
  • KikasaPlanteraVine.AI (cognitive 33) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraVine.cs:98 — KikasaPlanteraVine.AI 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.
D2 · Cognitive Complexity · KikasaSeaShrimpServant.UpdatePunch (cognitive 33) · ×1
  • KikasaSeaShrimpServant.UpdatePunch (cognitive 33) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:481 — KikasaSeaShrimpServant.UpdatePunch 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.
D2 · Cognitive Complexity · CyberTraceBeamProj.AI (cognitive 33) · ×1
  • CyberTraceBeamProj.AI (cognitive 33) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberTraceBeamProj.cs:181 — CyberTraceBeamProj.AI 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.
D2 · Cognitive Complexity · SHPCMossPatchProj.AI (cognitive 33) · ×1
  • SHPCMossPatchProj.AI (cognitive 33) Content/LegendWeapon/SHPCLegend/Modules/Barrel/MossboundBarrelModule.cs:140 — SHPCMossPatchProj.AI 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.
D2 · Cognitive Complexity · BssStormTransitionState.OnUpdate (cognitive 33) · ×1
  • BssStormTransitionState.OnUpdate (cognitive 33) Content/NPCs/BloomsandSerpents/States/BssStormTransitionState.cs:37 — BssStormTransitionState.OnUpdate 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.
D2 · Cognitive Complexity · EocBloodFountainState.OnUpdate (cognitive 33) · ×1
  • EocBloodFountainState.OnUpdate (cognitive 33) Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocBloodFountainState.cs:34 — EocBloodFountainState.OnUpdate 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.
D2 · Cognitive Complexity · BKSTideWaveProj.AI (cognitive 33) · ×1
  • BKSTideWaveProj.AI (cognitive 33) Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSTideWaveProj.cs:88 — BKSTideWaveProj.AI 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.
D2 · Cognitive Complexity · PrimeArmStateBase.AnchoredFollow (cognitive 33) · ×1
  • PrimeArmStateBase.AnchoredFollow (cognitive 33) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Core/IPrimeArmState.cs:126 — PrimeArmStateBase.AnchoredFollow 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.
D2 · Cognitive Complexity · NPCTalkUIBase.DrawTextBlock (cognitive 33) · ×1
  • NPCTalkUIBase.DrawTextBlock (cognitive 33) Content/NPCs/CommonUIs/NPCTalkUIBase.cs:240 — NPCTalkUIBase.DrawTextBlock 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.
D2 · Cognitive Complexity · SeaShrimpAbyssJetState.OnUpdate (cognitive 33) · ×1
  • SeaShrimpAbyssJetState.OnUpdate (cognitive 33) Content/NPCs/SeaShrimp/States/SeaShrimpAbyssJetState.cs:38 — SeaShrimpAbyssJetState.OnUpdate 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.
D2 · Cognitive Complexity · SeaShrimpIntroState.OnUpdate (cognitive 33) · ×1
  • SeaShrimpIntroState.OnUpdate (cognitive 33) Content/NPCs/SeaShrimp/States/SeaShrimpIntroState.cs:44 — SeaShrimpIntroState.OnUpdate 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.
D2 · Cognitive Complexity · SeaShrimpWaterVolleyState.OnUpdate (cognitive 33) · ×1
  • SeaShrimpWaterVolleyState.OnUpdate (cognitive 33) Content/NPCs/SeaShrimp/States/SeaShrimpWaterVolleyState.cs:31 — SeaShrimpWaterVolleyState.OnUpdate 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.
D2 · Cognitive Complexity · ExoMechdusaSumRender.UpdateDecodedText (cognitive 33) · ×1
  • ExoMechdusaSumRender.UpdateDecodedText (cognitive 33) Content/Scenarios/Draedon/ExoMechdusaSums/ExoMechdusaSumRender.cs:224 — ExoMechdusaSumRender.UpdateDecodedText 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.
D2 · Cognitive Complexity · L6Colossus.BuildScaffold (cognitive 33) · ×1
  • L6Colossus.BuildScaffold (cognitive 33) Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Colossus.cs:387 — L6Colossus.BuildScaffold 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.
D2 · Cognitive Complexity · L6Content.PlanAndBuild (cognitive 33) · ×1
  • L6Content.PlanAndBuild (cognitive 33) Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Content.cs:43 — L6Content.PlanAndBuild 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.
D2 · Cognitive Complexity · DeepGaolWraith.DrawGlowLayer (cognitive 33) · ×1
  • DeepGaolWraith.DrawGlowLayer (cognitive 33) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:2438 — DeepGaolWraith.DrawGlowLayer 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.
D2 · Cognitive Complexity · HadalTerrainPlanner.BuildDeepStructures (cognitive 33) · ×1
  • HadalTerrainPlanner.BuildDeepStructures (cognitive 33) Content/Scenarios/Hadalworld/Gen/Core/HadalTerrainPlan.cs:520 — HadalTerrainPlanner.BuildDeepStructures 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.
D2 · Cognitive Complexity · KiyumeLampField.Scan (cognitive 33) · ×1
  • KiyumeLampField.Scan (cognitive 33) Content/Scenarios/Kiyume/Ambience/KiyumeLampField.cs:104 — KiyumeLampField.Scan 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.
D2 · Cognitive Complexity · SettingsCategory.Update (cognitive 33) · ×1
  • SettingsCategory.Update (cognitive 33) Content/UIs/OverhaulSettings/SettingsCategory.cs:104 — SettingsCategory.Update 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.
D2 · Cognitive Complexity · CyberInventoryPanel.DrawItemList (cognitive 32) · ×1
  • CyberInventoryPanel.DrawItemList (cognitive 32) Content/Cyberwares/UIs/CyberInventoryPanel.cs:413 — CyberInventoryPanel.DrawItemList has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SunkenduneSinkPitProj.AI (cognitive 32) · ×1
  • SunkenduneSinkPitProj.AI (cognitive 32) Content/GameModes/BrutalMobs/Ambience/Sunkendune/Projectiles/SunkenduneSinkPitProj.cs:67 — SunkenduneSinkPitProj.AI has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EliteMoveNPC.ServerLeap (cognitive 32) · ×1
  • EliteMoveNPC.ServerLeap (cognitive 32) Content/GameModes/BrutalMobs/EliteMove/EliteMoveNPC.cs:320 — EliteMoveNPC.ServerLeap has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · WastesIceSlickZone.AI (cognitive 32) · ×1
  • WastesIceSlickZone.AI (cognitive 32) Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesIceSlickZone.cs:58 — WastesIceSlickZone.AI has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GsMinisharkHeld.AI (cognitive 32) · ×1
  • GsMinisharkHeld.AI (cognitive 32) Content/GameModes/GodSmith/Weapons/Guns/GsMinishark.cs:166 — GsMinisharkHeld.AI has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HackTimeNetSync.ValidateAuthorityRequest (cognitive 32) · ×1
  • HackTimeNetSync.ValidateAuthorityRequest (cognitive 32) Content/HackTimes/HackTimeNetSync.cs:671 — HackTimeNetSync.ValidateAuthorityRequest has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CrusherTP.UpdateVisualFX (cognitive 32) · ×1
  • CrusherTP.UpdateVisualFX (cognitive 32) Content/Industrials/ElectricPowers/Crushers/CrusherTP.cs:196 — CrusherTP.UpdateVisualFX has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FluidPumpTP.UpdateMachine (cognitive 32) · ×1
  • FluidPumpTP.UpdateMachine (cognitive 32) Content/Industrials/ElectricPowers/FluidPumps/FluidPumpTP.cs:58 — FluidPumpTP.UpdateMachine has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BiomassGeneratorUI.UpdateElement (cognitive 32) · ×1
  • BiomassGeneratorUI.UpdateElement (cognitive 32) Content/Industrials/Generator/Biomass/BiomassGeneratorUI.cs:90 — BiomassGeneratorUI.UpdateElement has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ThermalGeneratorUI.UpdateElement (cognitive 32) · ×1
  • ThermalGeneratorUI.UpdateElement (cognitive 32) Content/Industrials/Generator/Thermal/ThermalGeneratorUI.cs:118 — ThermalGeneratorUI.UpdateElement has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DawnshatterHeld.ConsumeWindows (cognitive 32) · ×1
  • DawnshatterHeld.ConsumeWindows (cognitive 32) Content/Items/Melee/DawnshatterAzures/DawnshatterHeld.cs:571 — DawnshatterHeld.ConsumeWindows has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DivineSourceBladeHeld.HandleParticles (cognitive 32) · ×1
  • DivineSourceBladeHeld.HandleParticles (cognitive 32) Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:633 — DivineSourceBladeHeld.HandleParticles has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FallingPenguin.PreDraw (cognitive 32) · ×1
  • FallingPenguin.PreDraw (cognitive 32) Content/LegendWeapon/HalibutLegend/FishSkills/FishPeng.cs:513 — FallingPenguin.PreDraw has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaGunServant.DrawGlow (cognitive 32) · ×1
  • KikasaGunServant.DrawGlow (cognitive 32) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1573 — KikasaGunServant.DrawGlow has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaBloomSerpentServant.UpdateEmerge (cognitive 32) · ×1
  • KikasaBloomSerpentServant.UpdateEmerge (cognitive 32) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:277 — KikasaBloomSerpentServant.UpdateEmerge has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaFesterSerpentServant.UpdateEmerge (cognitive 32) · ×1
  • KikasaFesterSerpentServant.UpdateEmerge (cognitive 32) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:283 — KikasaFesterSerpentServant.UpdateEmerge has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaPrimeServant.UpdateEmerge (cognitive 32) · ×1
  • KikasaPrimeServant.UpdateEmerge (cognitive 32) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:342 — KikasaPrimeServant.UpdateEmerge has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaPrimeServant.UpdateDissolve (cognitive 32) · ×1
  • KikasaPrimeServant.UpdateDissolve (cognitive 32) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:886 — KikasaPrimeServant.UpdateDissolve has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaSkeletronServant.DrawGlow (cognitive 32) · ×1
  • KikasaSkeletronServant.DrawGlow (cognitive 32) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1603 — KikasaSkeletronServant.DrawGlow has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaWallOfFleshServant.DrawWallBody (cognitive 32) · ×1
  • KikasaWallOfFleshServant.DrawWallBody (cognitive 32) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:948 — KikasaWallOfFleshServant.DrawWallBody has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CyberDomainFreeze.ApplyFreezeBatch (cognitive 32) · ×1
  • CyberDomainFreeze.ApplyFreezeBatch (cognitive 32) Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.cs:275 — CyberDomainFreeze.ApplyFreezeBatch has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SHPCModPanel.DrawEquippedTooltip (cognitive 32) · ×1
  • SHPCModPanel.DrawEquippedTooltip (cognitive 32) Content/LegendWeapon/SHPCLegend/UI/SHPCModPanel.cs:372 — SHPCModPanel.DrawEquippedTooltip has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CharacterDockUI.UpdateInteraction (cognitive 32) · ×1
  • CharacterDockUI.UpdateInteraction (cognitive 32) Content/MainMenus/Characters/CharacterDockUI.cs:329 — CharacterDockUI.UpdateInteraction has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CultistStarChart.PreDraw (cognitive 32) · ×1
  • CultistStarChart.PreDraw (cognitive 32) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistStarChart.cs:192 — CultistStarChart.PreDraw has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HandClapState.OnUpdate (cognitive 32) · ×1
  • HandClapState.OnUpdate (cognitive 32) Content/NPCs/BrutalNPCs/BrutalSkeletron/States/Hands/SkeletronHandStates.cs:418 — HandClapState.OnUpdate has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SkeletronIntroState.UpdateBeats (cognitive 32) · ×1
  • SkeletronIntroState.UpdateBeats (cognitive 32) Content/NPCs/BrutalNPCs/BrutalSkeletron/States/SkeletronIntroState.cs:69 — SkeletronIntroState.UpdateBeats has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DungeonworldSnuff.Advance (cognitive 32) · ×1
  • DungeonworldSnuff.Advance (cognitive 32) Content/Scenarios/Dungeonworld/Ambience/DungeonworldSnuff.cs:257 — DungeonworldSnuff.Advance has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · L2EscapeTunnel.Carve (cognitive 32) · ×1
  • L2EscapeTunnel.Carve (cognitive 32) Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2EscapeTunnel.cs:223 — L2EscapeTunnel.Carve has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · L3Content.RouteChains (cognitive 32) · ×1
  • L3Content.RouteChains (cognitive 32) Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Content.cs:509 — L3Content.RouteChains has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LampeaterWisp.UpdatePounce (cognitive 32) · ×1
  • LampeaterWisp.UpdatePounce (cognitive 32) Content/Scenarios/Dungeonworld/NPCs/Elites/LampeaterWisp.cs:229 — LampeaterWisp.UpdatePounce has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OverseerDormantRig.UpdateRite (cognitive 32) · ×1
  • OverseerDormantRig.UpdateRite (cognitive 32) Content/Scenarios/Dungeonworld/NPCs/OverseerDormantRig.cs:173 — OverseerDormantRig.UpdateRite has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · UndrownedAnchor.AI (cognitive 32) · ×1
  • UndrownedAnchor.AI (cognitive 32) Content/Scenarios/Dungeonworld/NPCs/UndrownedAnchor.cs:53 — UndrownedAnchor.AI has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HadalTerrainModel.Flood (cognitive 32) · ×1
  • HadalTerrainModel.Flood (cognitive 32) Content/Scenarios/Hadalworld/Gen/Core/HadalTerrainModel.cs:80 — HadalTerrainModel.Flood has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OldNetICEDirector.SeedLurkers (cognitive 32) · ×1
  • OldNetICEDirector.SeedLurkers (cognitive 32) Content/Scenarios/OldNet/NPCs/OldNetICEDirector.cs:572 — OldNetICEDirector.SeedLurkers has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MusicDirector.Arbitrate (cognitive 31) · ×1
  • MusicDirector.Arbitrate (cognitive 31) Common/MusicDirector.cs:120 — MusicDirector.Arbitrate has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FlgMortarRingOmen.AI (cognitive 31) · ×1
  • FlgMortarRingOmen.AI (cognitive 31) Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarRingOmen.cs:71 — FlgMortarRingOmen.AI has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PrtRicochetShot.AI (cognitive 31) · ×1
  • PrtRicochetShot.AI (cognitive 31) Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtRicochetShot.cs:89 — PrtRicochetShot.AI has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ShimmerTransmuterTP.TryPlaceOutputs (cognitive 31) · ×1
  • ShimmerTransmuterTP.TryPlaceOutputs (cognitive 31) Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterTP.cs:318 — ShimmerTransmuterTP.TryPlaceOutputs has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SolarCoreFistPlayer.UpdateVisualEnvelopes (cognitive 31) · ×1
  • SolarCoreFistPlayer.UpdateVisualEnvelopes (cognitive 31) Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFist.cs:368 — SolarCoreFistPlayer.UpdateVisualEnvelopes has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · AbyssrendClampHeld.HandleSuction (cognitive 31) · ×1
  • AbyssrendClampHeld.HandleSuction (cognitive 31) Content/Items/Melee/Abyssrends/AbyssrendClampHeld.cs:223 — AbyssrendClampHeld.HandleSuction has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FishVoodooPlayer.OnSet (cognitive 31) · ×1
  • FishVoodooPlayer.OnSet (cognitive 31) Content/LegendWeapon/HalibutLegend/FishSkills/FishVoodoo.cs:37 — FishVoodooPlayer.OnSet has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaDrownFX.DrawHandLayer (cognitive 31) · ×1
  • KikasaDrownFX.DrawHandLayer (cognitive 31) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1005 — KikasaDrownFX.DrawHandLayer has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaGolemMagmaBall.AI (cognitive 31) · ×1
  • KikasaGolemMagmaBall.AI (cognitive 31) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemMagmaBall.cs:82 — KikasaGolemMagmaBall.AI has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaQueenSlimeServant.DrawShaderPieces (cognitive 31) · ×1
  • KikasaQueenSlimeServant.DrawShaderPieces (cognitive 31) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:1399 — KikasaQueenSlimeServant.DrawShaderPieces has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniDomainPlayer.UpdateOpening (cognitive 31) · ×1
  • OniDomainPlayer.UpdateOpening (cognitive 31) Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainPlayer.cs:431 — OniDomainPlayer.UpdateOpening has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniOmokage.UpdateReimprint (cognitive 31) · ×1
  • OniOmokage.UpdateReimprint (cognitive 31) Content/LegendWeapon/OnikiriLegend/OniOmokages/OniOmokage.cs:784 — OniOmokage.UpdateReimprint has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SHPCDomainWheelUI.DrawInfoPanelForHovered (cognitive 31) · ×1
  • SHPCDomainWheelUI.DrawInfoPanelForHovered (cognitive 31) Content/LegendWeapon/SHPCLegend/UI/DomainWheel/SHPCDomainWheelUI.cs:344 — SHPCDomainWheelUI.DrawInfoPanelForHovered has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · AcknowledgmentUI.DrawRoll (cognitive 31) · ×1
  • AcknowledgmentUI.DrawRoll (cognitive 31) Content/MainMenus/Overs/AcknowledgmentUI.cs:357 — AcknowledgmentUI.DrawRoll has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CultistPlanetProj.EmitVolley (cognitive 31) · ×1
  • CultistPlanetProj.EmitVolley (cognitive 31) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistPlanetProj.cs:526 — CultistPlanetProj.EmitVolley has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CultistEclipseState.OnUpdate (cognitive 31) · ×1
  • CultistEclipseState.OnUpdate (cognitive 31) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistEclipseState.cs:39 — CultistEclipseState.OnUpdate has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TwinsPhaseTransitionState.ExecuteBurstPhase (cognitive 31) · ×1
  • TwinsPhaseTransitionState.ExecuteBurstPhase (cognitive 31) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsPhaseTransitionState.cs:236 — TwinsPhaseTransitionState.ExecuteBurstPhase has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TwinsPincerGrabState.OnBeatChanged (cognitive 31) · ×1
  • TwinsPincerGrabState.OnBeatChanged (cognitive 31) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsPincerGrabState.cs:477 — TwinsPincerGrabState.OnBeatChanged has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BrutalQueenBeeAI.UpdateHoneyMark (cognitive 31) · ×1
  • BrutalQueenBeeAI.UpdateHoneyMark (cognitive 31) Content/NPCs/BrutalNPCs/BrutalQueenBee/BrutalQueenBeeAI.cs:283 — BrutalQueenBeeAI.UpdateHoneyMark has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · QueenCrystalPrisonWaltzState.UpdateWaltz (cognitive 31) · ×1
  • QueenCrystalPrisonWaltzState.UpdateWaltz (cognitive 31) Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenCrystalPrisonWaltzState.cs:324 — QueenCrystalPrisonWaltzState.UpdateWaltz has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · QueenCrystalWaltzState.OnUpdate (cognitive 31) · ×1
  • QueenCrystalWaltzState.OnUpdate (cognitive 31) Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenCrystalWaltzState.cs:38 — QueenCrystalWaltzState.OnUpdate has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · VictorDialogue.CollectContext (cognitive 31) · ×1
  • VictorDialogue.CollectContext (cognitive 31) Content/NPCs/Victors/VictorDialogue.cs:218 — VictorDialogue.CollectContext has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FoundryOverseer.PreDraw (cognitive 31) · ×1
  • FoundryOverseer.PreDraw (cognitive 31) Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:1244 — FoundryOverseer.PreDraw has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HadalTerrainPlanner.BuildCaveField (cognitive 31) · ×1
  • HadalTerrainPlanner.BuildCaveField (cognitive 31) Content/Scenarios/Hadalworld/Gen/Core/HadalTerrainPlan.cs:433 — HadalTerrainPlanner.BuildCaveField has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SporeshineRender.UpdateBySystem (cognitive 30) · ×1
  • SporeshineRender.UpdateBySystem (cognitive 30) Content/GameModes/BrutalMobs/Ambience/Sporeshine/SporeshineRender.cs:73 — SporeshineRender.UpdateBySystem 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.
D2 · Cognitive Complexity · GsZoneProj.AI (cognitive 30) · ×1
  • GsZoneProj.AI (cognitive 30) Content/GameModes/GodSmith/Weapons/Throwing/Projectiles/GsZoneProj.cs:61 — GsZoneProj.AI 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.
D2 · Cognitive Complexity · PlayerHackAuthority.UpdateAuthority (cognitive 30) · ×1
  • PlayerHackAuthority.UpdateAuthority (cognitive 30) Content/HackTimes/PvP/PlayerHackNet.cs:442 — PlayerHackAuthority.UpdateAuthority 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.
D2 · Cognitive Complexity · CollectorUI.Update (cognitive 30) · ×1
  • CollectorUI.Update (cognitive 30) Content/Industrials/ElectricPowers/Collectors/CollectorUI.cs:188 — CollectorUI.Update 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.
D2 · Cognitive Complexity · JusticeUnveiledExplode.AI (cognitive 30) · ×1
  • JusticeUnveiledExplode.AI (cognitive 30) Content/Items/Accessories/JusticeUnveileds/JusticeUnveiledExplode.cs:41 — JusticeUnveiledExplode.AI 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.
D2 · Cognitive Complexity · DivineSourceBladeHeld.HandlePhaseEvents (cognitive 30) · ×1
  • DivineSourceBladeHeld.HandlePhaseEvents (cognitive 30) Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:436 — DivineSourceBladeHeld.HandlePhaseEvents 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.
D2 · Cognitive Complexity · KikasaDrown.StartAuthoritative (cognitive 30) · ×1
  • KikasaDrown.StartAuthoritative (cognitive 30) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrown.cs:402 — KikasaDrown.StartAuthoritative 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.
D2 · Cognitive Complexity · KikasaResetHourglass.StepParticles (cognitive 30) · ×1
  • KikasaResetHourglass.StepParticles (cognitive 30) Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetHourglass.cs:236 — KikasaResetHourglass.StepParticles 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.
D2 · Cognitive Complexity · KikasaBladeServant.UpdateCross (cognitive 30) · ×1
  • KikasaBladeServant.UpdateCross (cognitive 30) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:609 — KikasaBladeServant.UpdateCross 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.
D2 · Cognitive Complexity · KikasaEyeServant.UpdateDash (cognitive 30) · ×1
  • KikasaEyeServant.UpdateDash (cognitive 30) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:423 — KikasaEyeServant.UpdateDash 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.
D2 · Cognitive Complexity · KikasaGolemServant.UpdateMagma (cognitive 30) · ×1
  • KikasaGolemServant.UpdateMagma (cognitive 30) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:712 — KikasaGolemServant.UpdateMagma 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.
D2 · Cognitive Complexity · KikasaGolemServant.UpdateDissolve (cognitive 30) · ×1
  • KikasaGolemServant.UpdateDissolve (cognitive 30) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:876 — KikasaGolemServant.UpdateDissolve 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.
D2 · Cognitive Complexity · KikasaHudLead.DrawOverlay (cognitive 30) · ×1
  • KikasaHudLead.DrawOverlay (cognitive 30) Content/LegendWeapon/KikasaLegend/UI/KikasaHudLead.cs:549 — KikasaHudLead.DrawOverlay 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.
D2 · Cognitive Complexity · PRT_CrimsonSteelSpark.TryRicochet (cognitive 30) · ×1
  • PRT_CrimsonSteelSpark.TryRicochet (cognitive 30) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendParticles.cs:625 — PRT_CrimsonSteelSpark.TryRicochet 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.
D2 · Cognitive Complexity · OniSigilRenderer.DrawNode (cognitive 30) · ×1
  • OniSigilRenderer.DrawNode (cognitive 30) Content/LegendWeapon/OnikiriLegend/UI/OniSigilRenderer.cs:144 — OniSigilRenderer.DrawNode 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.
D2 · Cognitive Complexity · OverloadCoreModule.OnOrbCharging (cognitive 30) · ×1
  • OverloadCoreModule.OnOrbCharging (cognitive 30) Content/LegendWeapon/SHPCLegend/Modules/Power/OverloadCoreModule.cs:38 — OverloadCoreModule.OnOrbCharging 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.
D2 · Cognitive Complexity · HimayoPetalField.Tick (cognitive 30) · ×1
  • HimayoPetalField.Tick (cognitive 30) Content/MainMenus/Himayo/HimayoPetalField.cs:105 — HimayoPetalField.Tick 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.
D2 · Cognitive Complexity · BssNeedleRippleState.FireWave (cognitive 30) · ×1
  • BssNeedleRippleState.FireWave (cognitive 30) Content/NPCs/BloomsandSerpents/States/BssNeedleRippleState.cs:131 — BssNeedleRippleState.FireWave 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.
D2 · Cognitive Complexity · BrainMirrorStrikeState.OnUpdate (cognitive 30) · ×1
  • BrainMirrorStrikeState.OnUpdate (cognitive 30) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainMirrorStrikeState.cs:101 — BrainMirrorStrikeState.OnUpdate 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.
D2 · Cognitive Complexity · FishronTidalDashCooldownState.OnUpdate (cognitive 30) · ×1
  • FishronTidalDashCooldownState.OnUpdate (cognitive 30) Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronTidalDashState.cs:229 — FishronTidalDashCooldownState.OnUpdate 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.
D2 · Cognitive Complexity · EmpressFinaleState.Swarm (cognitive 30) · ×1
  • EmpressFinaleState.Swarm (cognitive 30) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/States/EmpressFinaleState.cs:171 — EmpressFinaleState.Swarm 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.
D2 · Cognitive Complexity · EmpressMoonShadowState.OnUpdate (cognitive 30) · ×1
  • EmpressMoonShadowState.OnUpdate (cognitive 30) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/States/EmpressMoonShadowState.cs:43 — EmpressMoonShadowState.OnUpdate 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.
D2 · Cognitive Complexity · KingSlimeGelMortarState.OnUpdate (cognitive 30) · ×1
  • KingSlimeGelMortarState.OnUpdate (cognitive 30) Content/NPCs/BrutalNPCs/BrutalKingSlime/States/KingSlimeGelMortarState.cs:46 — KingSlimeGelMortarState.OnUpdate 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.
D2 · Cognitive Complexity · CultistSeekerStar.AI (cognitive 30) · ×1
  • CultistSeekerStar.AI (cognitive 30) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistSeekerStar.cs:65 — CultistSeekerStar.AI 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.
D2 · Cognitive Complexity · RetinazerSoloRageState.ExecuteCrossBeams (cognitive 30) · ×1
  • RetinazerSoloRageState.ExecuteCrossBeams (cognitive 30) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerSoloRageState.cs:233 — RetinazerSoloRageState.ExecuteCrossBeams 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.
D2 · Cognitive Complexity · MLordArmIK.SolveInner (cognitive 30) · ×1
  • MLordArmIK.SolveInner (cognitive 30) Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordArmIK.cs:114 — MLordArmIK.SolveInner 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.
D2 · Cognitive Complexity · QueenCrystalDiveStompState.OnUpdate (cognitive 30) · ×1
  • QueenCrystalDiveStompState.OnUpdate (cognitive 30) Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenCrystalDiveStompState.cs:40 — QueenCrystalDiveStompState.OnUpdate 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.
D2 · Cognitive Complexity · SkeletronPhaseTransitionState.UpdateBeats (cognitive 30) · ×1
  • SkeletronPhaseTransitionState.UpdateBeats (cognitive 30) Content/NPCs/BrutalNPCs/BrutalSkeletron/States/SkeletronPhaseTransitionState.cs:50 — SkeletronPhaseTransitionState.UpdateBeats 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.
D2 · Cognitive Complexity · TBUGDialogue.CollectContext (cognitive 30) · ×1
  • TBUGDialogue.CollectContext (cognitive 30) Content/NPCs/TBUGs/TBUGDialogue.cs:218 — TBUGDialogue.CollectContext 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.
D2 · Cognitive Complexity · UndrownedVFX.DrawAndAdvance (cognitive 30) · ×1
  • UndrownedVFX.DrawAndAdvance (cognitive 30) Content/Scenarios/Dungeonworld/NPCs/UndrownedVFX.cs:186 — UndrownedVFX.DrawAndAdvance 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.
D2 · Cognitive Complexity · EbnBarsDisplay.PreDrawResources (cognitive 30) · ×1
  • EbnBarsDisplay.PreDrawResources (cognitive 30) Content/Scenarios/SupCal/End/EternalBlazingNow/EbnBarsDisplay.cs:89 — EbnBarsDisplay.PreDrawResources 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.
D2 · Cognitive Complexity · GhostHandProj.GrippingBehavior (cognitive 30) · ×1
  • GhostHandProj.GrippingBehavior (cognitive 30) Content/Wraiths/Projectiles/GhostHandProj.cs:448 — GhostHandProj.GrippingBehavior 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.
D2 · Cognitive Complexity · CindercragVentProj.AI (cognitive 29) · ×1
  • CindercragVentProj.AI (cognitive 29) Content/GameModes/BrutalMobs/Ambience/Cindercrag/Projectiles/CindercragVentProj.cs:114 — CindercragVentProj.AI 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.
D2 · Cognitive Complexity · EliteMoveNPC.ServerScatter (cognitive 29) · ×1
  • EliteMoveNPC.ServerScatter (cognitive 29) Content/GameModes/BrutalMobs/EliteMove/EliteMoveNPC.cs:482 — EliteMoveNPC.ServerScatter 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.
D2 · Cognitive Complexity · StonebornBrutalNPC.TickTelegraph (cognitive 29) · ×1
  • StonebornBrutalNPC.TickTelegraph (cognitive 29) Content/GameModes/BrutalMobs/Stoneborn/StonebornBrutalNPC.cs:398 — StonebornBrutalNPC.TickTelegraph 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.
D2 · Cognitive Complexity · PlayerHackLinkRender.DrawSerpentine (cognitive 29) · ×1
  • PlayerHackLinkRender.DrawSerpentine (cognitive 29) Content/HackTimes/PvP/UI/PlayerHackLinkRender.cs:284 — PlayerHackLinkRender.DrawSerpentine 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.
D2 · Cognitive Complexity · SelfRigScannable.BuildScanData (cognitive 29) · ×1
  • SelfRigScannable.BuildScanData (cognitive 29) Content/HackTimes/Scannables/SelfRigScannable.cs:51 — SelfRigScannable.BuildScanData 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.
D2 · Cognitive Complexity · ApiaryTP.UpdateMachine (cognitive 29) · ×1
  • ApiaryTP.UpdateMachine (cognitive 29) Content/Industrials/ElectricPowers/Apiaries/ApiaryTP.cs:299 — ApiaryTP.UpdateMachine 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.
D2 · Cognitive Complexity · MiningMachineUI.DrawCoreSample (cognitive 29) · ×1
  • MiningMachineUI.DrawCoreSample (cognitive 29) Content/Industrials/ElectricPowers/MiningMachines/MiningMachineUI.cs:404 — MiningMachineUI.DrawCoreSample 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.
D2 · Cognitive Complexity · ChargingStationUI.Update (cognitive 29) · ×1
  • ChargingStationUI.Update (cognitive 29) Content/Industrials/Modifys/ChargingStationUI.cs:108 — ChargingStationUI.Update 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.
D2 · Cognitive Complexity · WeaverGrievancesHeld.AI (cognitive 29) · ×1
  • WeaverGrievancesHeld.AI (cognitive 29) Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:231 — WeaverGrievancesHeld.AI 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.
D2 · Cognitive Complexity · KikasaDrownFX.UpdateShow (cognitive 29) · ×1
  • KikasaDrownFX.UpdateShow (cognitive 29) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:428 — KikasaDrownFX.UpdateShow 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.
D2 · Cognitive Complexity · KikasaQueenSlimeServant.UpdateDissolve (cognitive 29) · ×1
  • KikasaQueenSlimeServant.UpdateDissolve (cognitive 29) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:879 — KikasaQueenSlimeServant.UpdateDissolve 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.
D2 · Cognitive Complexity · KikasaTwinsServant.DrawGlow (cognitive 29) · ×1
  • KikasaTwinsServant.DrawGlow (cognitive 29) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1606 — KikasaTwinsServant.DrawGlow 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.
D2 · Cognitive Complexity · KikasaWispFX.Update (cognitive 29) · ×1
  • KikasaWispFX.Update (cognitive 29) Content/LegendWeapon/KikasaLegend/KikasaWisps/KikasaWispFX.cs:63 — KikasaWispFX.Update 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.
D2 · Cognitive Complexity · SakuraKiriPlayer.TransformDrawData (cognitive 29) · ×1
  • SakuraKiriPlayer.TransformDrawData (cognitive 29) Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraKiriPlayer.cs:132 — SakuraKiriPlayer.TransformDrawData 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.
D2 · Cognitive Complexity · OnikiriTutorialPlayer.PerformAssistedAction (cognitive 29) · ×1
  • OnikiriTutorialPlayer.PerformAssistedAction (cognitive 29) Content/LegendWeapon/OnikiriLegend/Tutorial/OnikiriTutorialPlayer.cs:934 — OnikiriTutorialPlayer.PerformAssistedAction 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.
D2 · Cognitive Complexity · OniSigilUI.DiffSlotStates (cognitive 29) · ×1
  • OniSigilUI.DiffSlotStates (cognitive 29) Content/LegendWeapon/OnikiriLegend/UI/OniSigilUI.cs:636 — OniSigilUI.DiffSlotStates 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.
D2 · Cognitive Complexity · CyberRestart.Update (cognitive 29) · ×1
  • CyberRestart.Update (cognitive 29) Content/LegendWeapon/SHPCLegend/Cyberspaces/Restart/CyberRestart.cs:159 — CyberRestart.Update 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.
D2 · Cognitive Complexity · EfficientGripModule.ConsumeZeroLossShot (cognitive 29) · ×1
  • EfficientGripModule.ConsumeZeroLossShot (cognitive 29) Content/LegendWeapon/SHPCLegend/Modules/Grip/EfficientGripModule.cs:196 — EfficientGripModule.ConsumeZeroLossShot 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.
D2 · Cognitive Complexity · SHPCErgoEchoProj.AI (cognitive 29) · ×1
  • SHPCErgoEchoProj.AI (cognitive 29) Content/LegendWeapon/SHPCLegend/Modules/Stock/ErgonomicStockModule.cs:369 — SHPCErgoEchoProj.AI 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.
D2 · Cognitive Complexity · BssHead.UpdateStormPresentation (cognitive 29) · ×1
  • BssHead.UpdateStormPresentation (cognitive 29) Content/NPCs/BloomsandSerpents/BssHead.cs:752 — BssHead.UpdateStormPresentation 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.
D2 · Cognitive Complexity · BssSandPillar.PreDraw (cognitive 29) · ×1
  • BssSandPillar.PreDraw (cognitive 29) Content/NPCs/BloomsandSerpents/BssSandPillar.cs:667 — BssSandPillar.PreDraw 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.
D2 · Cognitive Complexity · BrainOrbitCageState.OnUpdate (cognitive 29) · ×1
  • BrainOrbitCageState.OnUpdate (cognitive 29) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainOrbitCageState.cs:64 — BrainOrbitCageState.OnUpdate 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.
D2 · Cognitive Complexity · FishronTsunamiSweepState.OnUpdate (cognitive 29) · ×1
  • FishronTsunamiSweepState.OnUpdate (cognitive 29) Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronTsunamiSweepState.cs:52 — FishronTsunamiSweepState.OnUpdate 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.
D2 · Cognitive Complexity · EowBurrowAmbushState.UpdateErupt (cognitive 29) · ×1
  • EowBurrowAmbushState.UpdateErupt (cognitive 29) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowBurrowAmbushState.cs:182 — EowBurrowAmbushState.UpdateErupt 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.
D2 · Cognitive Complexity · GolemDeathState.UpdateCollapse (cognitive 29) · ×1
  • GolemDeathState.UpdateCollapse (cognitive 29) Content/NPCs/BrutalNPCs/BrutalGolem/States/GolemDeathState.cs:290 — GolemDeathState.UpdateCollapse 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.
D2 · Cognitive Complexity · GolemStompComboState.OnLand (cognitive 29) · ×1
  • GolemStompComboState.OnLand (cognitive 29) Content/NPCs/BrutalNPCs/BrutalGolem/States/GolemStompComboState.cs:108 — GolemStompComboState.OnLand 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.
D2 · Cognitive Complexity · TwinsPincerGrabState.UpdateGrabBeats (cognitive 29) · ×1
  • TwinsPincerGrabState.UpdateGrabBeats (cognitive 29) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsPincerGrabState.cs:580 — TwinsPincerGrabState.UpdateGrabBeats 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.
D2 · Cognitive Complexity · MLordOrbProj.HeldVolleyAI (cognitive 29) · ×1
  • MLordOrbProj.HeldVolleyAI (cognitive 29) Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordOrbProj.cs:107 — MLordOrbProj.HeldVolleyAI 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.
D2 · Cognitive Complexity · QBSwarmLiftState.OnUpdate (cognitive 29) · ×1
  • QBSwarmLiftState.OnUpdate (cognitive 29) Content/NPCs/BrutalNPCs/BrutalQueenBee/States/QBSwarmLiftState.cs:124 — QBSwarmLiftState.OnUpdate 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.
D2 · Cognitive Complexity · PrimeViceExecutionState.ChoreographShooter (cognitive 29) · ×1
  • PrimeViceExecutionState.ChoreographShooter (cognitive 29) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/PrimeViceExecutionState.cs:492 — PrimeViceExecutionState.ChoreographShooter 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.
D2 · Cognitive Complexity · UndrownedThrone.UpdateRite (cognitive 29) · ×1
  • UndrownedThrone.UpdateRite (cognitive 29) Content/Scenarios/Dungeonworld/NPCs/UndrownedThrone.cs:179 — UndrownedThrone.UpdateRite 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.
D2 · Cognitive Complexity · KiyumeHound.UpdateLunge (cognitive 29) · ×1
  • KiyumeHound.UpdateLunge (cognitive 29) Content/Scenarios/Kiyume/NPCs/KiyumeHound.cs:569 — KiyumeHound.UpdateLunge 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.
D2 · Cognitive Complexity · CyberBodyRenderer.DrawPrimaryCurves (cognitive 28) · ×1
  • CyberBodyRenderer.DrawPrimaryCurves (cognitive 28) Content/Cyberwares/UIs/CyberBodyRenderer.cs:460 — CyberBodyRenderer.DrawPrimaryCurves has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CyberInventoryPanel.UpdateInteraction (cognitive 28) · ×1
  • CyberInventoryPanel.UpdateInteraction (cognitive 28) Content/Cyberwares/UIs/CyberInventoryPanel.cs:200 — CyberInventoryPanel.UpdateInteraction has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EntrustTrackerWidget.Update (cognitive 28) · ×1
  • EntrustTrackerWidget.Update (cognitive 28) Content/EntrustManager/EntrustTrackerWidget.cs:113 — EntrustTrackerWidget.Update has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · VerdantAmbientRender.EndEntityDraw (cognitive 28) · ×1
  • VerdantAmbientRender.EndEntityDraw (cognitive 28) Content/GameModes/BrutalMobs/Ambience/Verdant/VerdantAmbientRender.cs:30 — VerdantAmbientRender.EndEntityDraw has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PRT_WoodsongRaven.PerchAI (cognitive 28) · ×1
  • PRT_WoodsongRaven.PerchAI (cognitive 28) Content/GameModes/BrutalMobs/Ambience/Woodsong/PRT_WoodsongRaven.cs:164 — PRT_WoodsongRaven.PerchAI has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MartiansNPC.ArcStep (cognitive 28) · ×1
  • MartiansNPC.ArcStep (cognitive 28) Content/GameModes/BrutalMobs/Martians/MartiansNPC.cs:242 — MartiansNPC.ArcStep has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GsChargeBowHeld.UpdateStateMachine (cognitive 28) · ×1
  • GsChargeBowHeld.UpdateStateMachine (cognitive 28) Content/GameModes/GodSmith/Weapons/Bows/GsChargeBowHeld.cs:147 — GsChargeBowHeld.UpdateStateMachine has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GsYoyoScheme.GsProjPostAI (cognitive 28) · ×1
  • GsYoyoScheme.GsProjPostAI (cognitive 28) Content/GameModes/GodSmith/Weapons/Yoyos/GsYoyoScheme.cs:78 — GsYoyoScheme.GsProjPostAI has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HackEffectTracker.ApplyAuthorityEffect (cognitive 28) · ×1
  • HackEffectTracker.ApplyAuthorityEffect (cognitive 28) Content/HackTimes/HackEffectTracker.cs:157 — HackEffectTracker.ApplyAuthorityEffect has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Cryostasis.OnApply (cognitive 28) · ×1
  • Cryostasis.OnApply (cognitive 28) Content/HackTimes/Protocols/Cryostasis.cs:54 — Cryostasis.OnApply has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FluidPourDraw.PreDrawEverything (cognitive 28) · ×1
  • FluidPourDraw.PreDrawEverything (cognitive 28) Content/Industrials/ElectricPowers/FluidInjectors/FluidInjectorTP.cs:314 — FluidPourDraw.PreDrawEverything has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ItemFilterEditorUI.UpdateScrollAndAnims (cognitive 28) · ×1
  • ItemFilterEditorUI.UpdateScrollAndAnims (cognitive 28) Content/Industrials/ElectricPowers/ItemFilters/ItemFilterEditorUI.cs:357 — ItemFilterEditorUI.UpdateScrollAndAnims has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PlayerLauncherUI.Update (cognitive 28) · ×1
  • PlayerLauncherUI.Update (cognitive 28) Content/Industrials/ElectricPowers/Launchers/PlayerLauncherUI.cs:124 — PlayerLauncherUI.Update has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MushroomFarmerTP.TryPlant (cognitive 28) · ×1
  • MushroomFarmerTP.TryPlant (cognitive 28) Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:332 — MushroomFarmerTP.TryPlant has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · RecyclerTP.UpdateVisualFX (cognitive 28) · ×1
  • RecyclerTP.UpdateVisualFX (cognitive 28) Content/Industrials/ElectricPowers/Recyclers/RecyclerTP.cs:198 — RecyclerTP.UpdateVisualFX has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SwarmVortexProj.AI (cognitive 28) · ×1
  • SwarmVortexProj.AI (cognitive 28) Content/Items/Accessories/BrutalRelics/QueenBee/SwarmVortexProj.cs:73 — SwarmVortexProj.AI has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GodslayerScabbardPlayer.PreUpdateMovement (cognitive 28) · ×1
  • GodslayerScabbardPlayer.PreUpdateMovement (cognitive 28) Content/Items/Accessories/GodslayerScabbard.cs:71 — GodslayerScabbardPlayer.PreUpdateMovement has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PandemoniumScythe.AI (cognitive 28) · ×1
  • PandemoniumScythe.AI (cognitive 28) Content/Items/Magic/Pandemoniums/PandemoniumScythe.cs:46 — PandemoniumScythe.AI has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DestroyerBiteProj.PreDraw (cognitive 28) · ×1
  • DestroyerBiteProj.PreDraw (cognitive 28) Content/Items/Melee/DestroyersBladeEXs/DestroyerBiteProj.cs:447 — DestroyerBiteProj.PreDraw has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DragonsScaleGreatswordHeld.AI (cognitive 28) · ×1
  • DragonsScaleGreatswordHeld.AI (cognitive 28) Content/Items/Melee/DragonsScaleGreatsword.cs:208 — DragonsScaleGreatswordHeld.AI has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · WeaverBeam.AI (cognitive 28) · ×1
  • WeaverBeam.AI (cognitive 28) Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:880 — WeaverBeam.AI has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HyperionCruiseMissile.OnKill (cognitive 28) · ×1
  • HyperionCruiseMissile.OnKill (cognitive 28) Content/Items/Ranged/HyperionBarrage.cs:552 — HyperionCruiseMissile.OnKill has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DrizzleFishHolder.AI (cognitive 28) · ×1
  • DrizzleFishHolder.AI (cognitive 28) Content/LegendWeapon/HalibutLegend/FishSkills/FishDrizzle.cs:380 — DrizzleFishHolder.AI has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ObsidianFishOrbit.PreDraw (cognitive 28) · ×1
  • ObsidianFishOrbit.PreDraw (cognitive 28) Content/LegendWeapon/HalibutLegend/FishSkills/FishObsidian.cs:529 — ObsidianFishOrbit.PreDraw has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · UnicornFishDashProj.PreDraw (cognitive 28) · ×1
  • UnicornFishDashProj.PreDraw (cognitive 28) Content/LegendWeapon/HalibutLegend/FishSkills/FishUnicorn.cs:369 — UnicornFishDashProj.PreDraw has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaDomainPlayer.HandleMutateKey (cognitive 28) · ×1
  • KikasaDomainPlayer.HandleMutateKey (cognitive 28) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainPlayer.cs:378 — KikasaDomainPlayer.HandleMutateKey has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaDreamHound.DrawAll (cognitive 28) · ×1
  • KikasaDreamHound.DrawAll (cognitive 28) Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamHound.cs:947 — KikasaDreamHound.DrawAll has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaRodServant.UpdateFish (cognitive 28) · ×1
  • KikasaRodServant.UpdateFish (cognitive 28) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:371 — KikasaRodServant.UpdateFish has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaZenithServant.UpdatePhantoms (cognitive 28) · ×1
  • KikasaZenithServant.UpdatePhantoms (cognitive 28) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:788 — KikasaZenithServant.UpdatePhantoms has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaBrainServant.UpdateDissolve (cognitive 28) · ×1
  • KikasaBrainServant.UpdateDissolve (cognitive 28) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:790 — KikasaBrainServant.UpdateDissolve has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaDeerclopsServant.UpdateLurch (cognitive 28) · ×1
  • KikasaDeerclopsServant.UpdateLurch (cognitive 28) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:595 — KikasaDeerclopsServant.UpdateLurch has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaFishronServant.UpdatePorpoise (cognitive 28) · ×1
  • KikasaFishronServant.UpdatePorpoise (cognitive 28) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:529 — KikasaFishronServant.UpdatePorpoise has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaFishronServant.UpdateNado (cognitive 28) · ×1
  • KikasaFishronServant.UpdateNado (cognitive 28) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:629 — KikasaFishronServant.UpdateNado has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaKingSlimeServant.UpdateWaveSlam (cognitive 28) · ×1
  • KikasaKingSlimeServant.UpdateWaveSlam (cognitive 28) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:784 — KikasaKingSlimeServant.UpdateWaveSlam has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniDismember.UpdateAll (cognitive 28) · ×1
  • OniDismember.UpdateAll (cognitive 28) Content/LegendWeapon/OnikiriLegend/OniDismembers/OniDismember.cs:751 — OniDismember.UpdateAll has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SHPCBraceRigProj.AI (cognitive 28) · ×1
  • SHPCBraceRigProj.AI (cognitive 28) Content/LegendWeapon/SHPCLegend/Modules/Stock/BraceStockModule.cs:242 — SHPCBraceRigProj.AI has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BssBody.DrawSegment (cognitive 28) · ×1
  • BssBody.DrawSegment (cognitive 28) Content/NPCs/BloomsandSerpents/BssBody.cs:333 — BssBody.DrawSegment has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BssHubState.PickAttack (cognitive 28) · ×1
  • BssHubState.PickAttack (cognitive 28) Content/NPCs/BloomsandSerpents/States/BssHubState.cs:140 — BssHubState.PickAttack has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BrainMirrorMazeState.OnUpdate (cognitive 28) · ×1
  • BrainMirrorMazeState.OnUpdate (cognitive 28) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainMirrorMazeState.cs:67 — BrainMirrorMazeState.OnUpdate has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DestroyerEncircleState.OnUpdate (cognitive 28) · ×1
  • DestroyerEncircleState.OnUpdate (cognitive 28) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerEncircleState.cs:37 — DestroyerEncircleState.OnUpdate has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EowSplitPincerState.UpdateFinale (cognitive 28) · ×1
  • EowSplitPincerState.UpdateFinale (cognitive 28) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowSplitPincerState.cs:426 — EowSplitPincerState.UpdateFinale has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KingSlimeMassEjectState.OnUpdate (cognitive 28) · ×1
  • KingSlimeMassEjectState.OnUpdate (cognitive 28) Content/NPCs/BrutalNPCs/BrutalKingSlime/States/KingSlimeMassEjectState.cs:51 — KingSlimeMassEjectState.OnUpdate has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PlanteraSeedGatlingState.OnUpdate (cognitive 28) · ×1
  • PlanteraSeedGatlingState.OnUpdate (cognitive 28) Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraSeedGatlingState.cs:66 — PlanteraSeedGatlingState.OnUpdate has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · QueenGelSplitSummonState.OnUpdate (cognitive 28) · ×1
  • QueenGelSplitSummonState.OnUpdate (cognitive 28) Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenGelSplitSummonState.cs:61 — QueenGelSplitSummonState.OnUpdate has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · QueenWingGaleWaltzState.OnUpdate (cognitive 28) · ×1
  • QueenWingGaleWaltzState.OnUpdate (cognitive 28) Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenWingGaleWaltzState.cs:42 — QueenWingGaleWaltzState.OnUpdate has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LaserChargedShotState.OnUpdate (cognitive 28) · ×1
  • LaserChargedShotState.OnUpdate (cognitive 28) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/Arms/PrimeLaserStates.cs:133 — LaserChargedShotState.OnUpdate has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FssClawRig.Advance (cognitive 28) · ×1
  • FssClawRig.Advance (cognitive 28) Content/NPCs/FestersandSerpents/FssClawRig.cs:123 — FssClawRig.Advance has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FssHead.AI (cognitive 28) · ×1
  • FssHead.AI (cognitive 28) Content/NPCs/FestersandSerpents/FssHead.cs:231 — FssHead.AI has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · L5Content.PlanAndBuild (cognitive 28) · ×1
  • L5Content.PlanAndBuild (cognitive 28) Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Content.cs:61 — L5Content.PlanAndBuild has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · L5TunnelCarver.Carve (cognitive 28) · ×1
  • L5TunnelCarver.Carve (cognitive 28) Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5TunnelCarver.cs:79 — L5TunnelCarver.Carve has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GuideTrailPass.PaintFloodTrail (cognitive 28) · ×1
  • GuideTrailPass.PaintFloodTrail (cognitive 28) Content/Scenarios/Dungeonworld/Gen/Passes/GuideTrailPass.cs:127 — GuideTrailPass.PaintFloodTrail has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FoundryOverseer.UpdateWheelRoll (cognitive 28) · ×1
  • FoundryOverseer.UpdateWheelRoll (cognitive 28) Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:781 — FoundryOverseer.UpdateWheelRoll has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KiameRuins.TryBuildHut (cognitive 28) · ×1
  • KiameRuins.TryBuildHut (cognitive 28) Content/Scenarios/Kiame/Gen/KiameRuins.cs:60 — KiameRuins.TryBuildHut has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Z2Content.BuildSealBox (cognitive 28) · ×1
  • Z2Content.BuildSealBox (cognitive 28) Content/Scenarios/OldNet/Gen/Zones/Z2/Z2Content.cs:88 — Z2Content.BuildSealBox has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OldNetThreatField.ScanWindow (cognitive 28) · ×1
  • OldNetThreatField.ScanWindow (cognitive 28) Content/Scenarios/OldNet/NPCs/OldNetThreatField.cs:192 — OldNetThreatField.ScanWindow has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OldNetDeco.Update (cognitive 28) · ×1
  • OldNetDeco.Update (cognitive 28) Content/Scenarios/OldNet/OldNetDeco.cs:18 — OldNetDeco.Update has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OldNetCipherPanel.UpdateUI (cognitive 28) · ×1
  • OldNetCipherPanel.UpdateUI (cognitive 28) Content/Scenarios/OldNet/UI/OldNetCipherPanel.cs:155 — OldNetCipherPanel.UpdateUI has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SylvanOutpost.AddNaturalDecoration (cognitive 28) · ×1
  • SylvanOutpost.AddNaturalDecoration (cognitive 28) Content/Structures/DatIO/SylvanOutpost.cs:598 — SylvanOutpost.AddNaturalDecoration has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ChestInteraction.UpdateSlotInteraction (cognitive 28) · ×1
  • ChestInteraction.UpdateSlotInteraction (cognitive 28) Content/UIs/StorageUIs/ChestInteraction.cs:51 — ChestInteraction.UpdateSlotInteraction has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BrideSeizurePerformance.Update (cognitive 28) · ×1
  • BrideSeizurePerformance.Update (cognitive 28) Content/Wraiths/Deaths/Performances/BrideSeizurePerformance.cs:59 — BrideSeizurePerformance.Update has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CWRItem.OverModifyTooltip (cognitive 27) · ×1
  • CWRItem.OverModifyTooltip (cognitive 27) Content/CWRItem.cs:309 — CWRItem.OverModifyTooltip has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FleshfenHazeRender.UpdateBySystem (cognitive 27) · ×1
  • FleshfenHazeRender.UpdateBySystem (cognitive 27) Content/GameModes/BrutalMobs/Ambience/Fleshfen/FleshfenHazeRender.cs:52 — FleshfenHazeRender.UpdateBySystem has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · NyxdepthGaze.Update (cognitive 27) · ×1
  • NyxdepthGaze.Update (cognitive 27) Content/GameModes/BrutalMobs/Ambience/Nyxdepth/NyxdepthGaze.cs:54 — NyxdepthGaze.Update has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GsSpookyLanternProj.AI (cognitive 27) · ×1
  • GsSpookyLanternProj.AI (cognitive 27) Content/GameModes/GodSmith/Armors/Hardmode/GsSpookyWoodArmor.cs:115 — GsSpookyLanternProj.AI has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GsHelmetNestSystem.RegisterSlots (cognitive 27) · ×1
  • GsHelmetNestSystem.RegisterSlots (cognitive 27) Content/GameModes/GodSmith/Armors/Reset/GsHelmetNest.cs:104 — GsHelmetNestSystem.RegisterSlots has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · AutoCrafterTP.CountMaterials (cognitive 27) · ×1
  • AutoCrafterTP.CountMaterials (cognitive 27) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterTP.cs:247 — AutoCrafterTP.CountMaterials has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CollectorTP.DrawStorageLinks (cognitive 27) · ×1
  • CollectorTP.DrawStorageLinks (cognitive 27) Content/Industrials/ElectricPowers/Collectors/CollectorTP.cs:540 — CollectorTP.DrawStorageLinks has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ThrowerUI.Update (cognitive 27) · ×1
  • ThrowerUI.Update (cognitive 27) Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:132 — ThrowerUI.Update has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BiomassGeneratorTP.GeneratorUpdate (cognitive 27) · ×1
  • BiomassGeneratorTP.GeneratorUpdate (cognitive 27) Content/Industrials/Generator/Biomass/BiomassGenerator.cs:243 — BiomassGeneratorTP.GeneratorUpdate has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ThermalGeneratorTP.GeneratorUpdate (cognitive 27) · ×1
  • ThermalGeneratorTP.GeneratorUpdate (cognitive 27) Content/Industrials/Generator/Thermal/ThermalGenerator.cs:206 — ThermalGeneratorTP.GeneratorUpdate has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MirrorheartPlayer.FirePendingEchoes (cognitive 27) · ×1
  • MirrorheartPlayer.FirePendingEchoes (cognitive 27) Content/Items/Accessories/BrutalRelics/BrainOfCthulhu/MirrorheartParadox.cs:282 — MirrorheartPlayer.FirePendingEchoes has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BloodfogVeilProj.UpdateDash (cognitive 27) · ×1
  • BloodfogVeilProj.UpdateDash (cognitive 27) Content/Items/Accessories/BrutalRelics/EyeOfCthulhu/BloodfogVeilProj.cs:173 — BloodfogVeilProj.UpdateDash has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BloodfogVeilProj.SimulateElements (cognitive 27) · ×1
  • BloodfogVeilProj.SimulateElements (cognitive 27) Content/Items/Accessories/BrutalRelics/EyeOfCthulhu/BloodfogVeilProj.cs:534 — BloodfogVeilProj.SimulateElements has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BloomNovaBulbPlayer.TryLash (cognitive 27) · ×1
  • BloomNovaBulbPlayer.TryLash (cognitive 27) Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaBulb.cs:218 — BloomNovaBulbPlayer.TryLash has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PandemoniumFireball.AI (cognitive 27) · ×1
  • PandemoniumFireball.AI (cognitive 27) Content/Items/Magic/Pandemoniums/PandemoniumFireball.cs:35 — PandemoniumFireball.AI has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · NeutronGlaiveHeld.HandlePhaseEvents (cognitive 27) · ×1
  • NeutronGlaiveHeld.HandlePhaseEvents (cognitive 27) Content/Items/Melee/NeutronGlaive.cs:355 — NeutronGlaiveHeld.HandlePhaseEvents has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · NeutronGlaiveHeldAlt.AI (cognitive 27) · ×1
  • NeutronGlaiveHeldAlt.AI (cognitive 27) Content/Items/Melee/NeutronGlaive.cs:1126 — NeutronGlaiveHeldAlt.AI has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniMachetePlayer.PostUpdateMiscEffects (cognitive 27) · ×1
  • OniMachetePlayer.PostUpdateMiscEffects (cognitive 27) Content/Items/Melee/OniMachete.cs:217 — OniMachetePlayer.PostUpdateMiscEffects has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ResurrectionDeath.UpdateDeathAnimationPhase (cognitive 27) · ×1
  • ResurrectionDeath.UpdateDeathAnimationPhase (cognitive 27) Content/LegendWeapon/HalibutLegend/Resurrections/ResurrectionDeath.cs:248 — ResurrectionDeath.UpdateDeathAnimationPhase has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaPlayerDrownFX.Draw (cognitive 27) · ×1
  • KikasaPlayerDrownFX.Draw (cognitive 27) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaPlayerDrownFX.cs:478 — KikasaPlayerDrownFX.Draw has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaGunServant.UpdateBlastWall (cognitive 27) · ×1
  • KikasaGunServant.UpdateBlastWall (cognitive 27) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:825 — KikasaGunServant.UpdateBlastWall has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaCultistServant.UpdateEmerge (cognitive 27) · ×1
  • KikasaCultistServant.UpdateEmerge (cognitive 27) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:291 — KikasaCultistServant.UpdateEmerge has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaSkeletronServant.UpdateSlam (cognitive 27) · ×1
  • KikasaSkeletronServant.UpdateSlam (cognitive 27) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:546 — KikasaSkeletronServant.UpdateSlam has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaThrallProj.UpdateLunge (cognitive 27) · ×1
  • KikasaThrallProj.UpdateLunge (cognitive 27) Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallProj.cs:598 — KikasaThrallProj.UpdateLunge has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CrimsonRendCleave.AI (cognitive 27) · ×1
  • CrimsonRendCleave.AI (cognitive 27) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendCleave.cs:232 — CrimsonRendCleave.AI has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CrimsonRendSlash.SpawnSweepSparks (cognitive 27) · ×1
  • CrimsonRendSlash.SpawnSweepSparks (cognitive 27) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1267 — CrimsonRendSlash.SpawnSweepSparks has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniMeiBreathArc.AI (cognitive 27) · ×1
  • OniMeiBreathArc.AI (cognitive 27) Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBreathArc.cs:167 — OniMeiBreathArc.AI has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniSlash.UpdateBeatEvents (cognitive 27) · ×1
  • OniSlash.UpdateBeatEvents (cognitive 27) Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1026 — OniSlash.UpdateBeatEvents has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SakuraFinaleAssets.DrawReadyStar (cognitive 27) · ×1
  • SakuraFinaleAssets.DrawReadyStar (cognitive 27) Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraFinaleAssets.cs:98 — SakuraFinaleAssets.DrawReadyStar has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniDomainEye.Update (cognitive 27) · ×1
  • OniDomainEye.Update (cognitive 27) Content/LegendWeapon/OnikiriLegend/UI/OniDomainEye.cs:71 — OniDomainEye.Update has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SHPCQuantumLinkProj.DrawAdditiveAfterNon (cognitive 27) · ×1
  • SHPCQuantumLinkProj.DrawAdditiveAfterNon (cognitive 27) Content/LegendWeapon/SHPCLegend/Modules/Frame/QuantumFrameModule.cs:320 — SHPCQuantumLinkProj.DrawAdditiveAfterNon has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ThermalOpticModule.FindWhiteHotTarget (cognitive 27) · ×1
  • ThermalOpticModule.FindWhiteHotTarget (cognitive 27) Content/LegendWeapon/SHPCLegend/Modules/Optic/ThermalOpticModule.cs:73 — ThermalOpticModule.FindWhiteHotTarget has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SHPCStormFieldProj.AI (cognitive 27) · ×1
  • SHPCStormFieldProj.AI (cognitive 27) Content/LegendWeapon/SHPCLegend/Modules/Stock/StormStockModule.cs:102 — SHPCStormFieldProj.AI has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SHPCCyberPanel.DrawStatusColumn (cognitive 27) · ×1
  • SHPCCyberPanel.DrawStatusColumn (cognitive 27) Content/LegendWeapon/SHPCLegend/UI/SHPCCyberPanel.cs:505 — SHPCCyberPanel.DrawStatusColumn has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BssPetalShakeState.OnUpdate (cognitive 27) · ×1
  • BssPetalShakeState.OnUpdate (cognitive 27) Content/NPCs/BloomsandSerpents/States/BssPetalShakeState.cs:30 — BssPetalShakeState.OnUpdate has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DeerclopsMotion.FindSpikeY (cognitive 27) · ×1
  • DeerclopsMotion.FindSpikeY (cognitive 27) Content/NPCs/BrutalNPCs/BrutalDeerclops/Core/DeerclopsMotion.cs:136 — DeerclopsMotion.FindSpikeY has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DeerclopsIntroState.OnUpdate (cognitive 27) · ×1
  • DeerclopsIntroState.OnUpdate (cognitive 27) Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsIntroState.cs:28 — DeerclopsIntroState.OnUpdate has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FishronBubbleMazeState.BuildSlots (cognitive 27) · ×1
  • FishronBubbleMazeState.BuildSlots (cognitive 27) Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronBubbleMazeState.cs:52 — FishronBubbleMazeState.BuildSlots has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EowBossBar.ModifyInfo (cognitive 27) · ×1
  • EowBossBar.ModifyInfo (cognitive 27) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/EowBossBar.cs:27 — EowBossBar.ModifyInfo has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · RetinazerPrecisionSniperState.OnUpdate (cognitive 27) · ×1
  • RetinazerPrecisionSniperState.OnUpdate (cognitive 27) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerPrecisionSniperState.cs:47 — RetinazerPrecisionSniperState.OnUpdate has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MoonLordHandAI.UpdateAlive (cognitive 27) · ×1
  • MoonLordHandAI.UpdateAlive (cognitive 27) Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordHandAI.cs:117 — MoonLordHandAI.UpdateAlive has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · QBDiveStrafeState.OnUpdate (cognitive 27) · ×1
  • QBDiveStrafeState.OnUpdate (cognitive 27) Content/NPCs/BrutalNPCs/BrutalQueenBee/States/QBDiveStrafeState.cs:36 — QBDiveStrafeState.OnUpdate has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · QueenCrystalPrisonWaltzState.UpdateSummon (cognitive 27) · ×1
  • QueenCrystalPrisonWaltzState.UpdateSummon (cognitive 27) Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenCrystalPrisonWaltzState.cs:220 — QueenCrystalPrisonWaltzState.UpdateSummon has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · QueenPrismVolleyState.OnUpdate (cognitive 27) · ×1
  • QueenPrismVolleyState.OnUpdate (cognitive 27) Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenPrismVolleyState.cs:37 — QueenPrismVolleyState.OnUpdate has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ScrapHeadSwingState.OnUpdate (cognitive 27) · ×1
  • ScrapHeadSwingState.OnUpdate (cognitive 27) Content/NPCs/ScrapCommanders/States/ScrapHeadSwingState.cs:33 — ScrapHeadSwingState.OnUpdate has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ScrapSawCannonComboState.OnUpdate (cognitive 27) · ×1
  • ScrapSawCannonComboState.OnUpdate (cognitive 27) Content/NPCs/ScrapCommanders/States/ScrapSawCannonComboState.cs:36 — ScrapSawCannonComboState.OnUpdate has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SeaShrimpMoltTransitionState.OnUpdate (cognitive 27) · ×1
  • SeaShrimpMoltTransitionState.OnUpdate (cognitive 27) Content/NPCs/SeaShrimp/States/SeaShrimpMoltTransitionState.cs:40 — SeaShrimpMoltTransitionState.OnUpdate has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SeaShrimpTailFlipStrikeState.OnUpdate (cognitive 27) · ×1
  • SeaShrimpTailFlipStrikeState.OnUpdate (cognitive 27) Content/NPCs/SeaShrimp/States/SeaShrimpTailFlipStrikeState.cs:32 — SeaShrimpTailFlipStrikeState.OnUpdate has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaPanelState.Update (cognitive 27) · ×1
  • KikasaPanelState.Update (cognitive 27) Content/Narrative/Presentation/Skins/Kikasa/KikasaPanelState.cs:48 — KikasaPanelState.Update has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OverseerDormantRig.UpdateDormant (cognitive 27) · ×1
  • OverseerDormantRig.UpdateDormant (cognitive 27) Content/Scenarios/Dungeonworld/NPCs/OverseerDormantRig.cs:114 — OverseerDormantRig.UpdateDormant has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Undrowned.PreDraw (cognitive 27) · ×1
  • Undrowned.PreDraw (cognitive 27) Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:1786 — Undrowned.PreDraw has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · UndrownedThrone.UpdateDormant (cognitive 27) · ×1
  • UndrownedThrone.UpdateDormant (cognitive 27) Content/Scenarios/Dungeonworld/NPCs/UndrownedThrone.cs:120 — UndrownedThrone.UpdateDormant has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Z3Rooms.BuildCheckpointAt (cognitive 27) · ×1
  • Z3Rooms.BuildCheckpointAt (cognitive 27) Content/Scenarios/OldNet/Gen/Zones/Z3/Z3Rooms.cs:105 — Z3Rooms.BuildCheckpointAt has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OldNetThreatField.TickMines (cognitive 27) · ×1
  • OldNetThreatField.TickMines (cognitive 27) Content/Scenarios/OldNet/NPCs/OldNetThreatField.cs:281 — OldNetThreatField.TickMines has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SubworldDrawBlackFix.DrawBlackFullRange (cognitive 27) · ×1
  • SubworldDrawBlackFix.DrawBlackFullRange (cognitive 27) Content/Scenarios/SubworldDrawBlackFix.cs:68 — SubworldDrawBlackFix.DrawBlackFullRange has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SylvanOutpost.FullSurfaceScan (cognitive 27) · ×1
  • SylvanOutpost.FullSurfaceScan (cognitive 27) Content/Structures/DatIO/SylvanOutpost.cs:131 — SylvanOutpost.FullSurfaceScan has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SylvanOutpost.PrepareTerrainForOutpost (cognitive 27) · ×1
  • SylvanOutpost.PrepareTerrainForOutpost (cognitive 27) Content/Structures/DatIO/SylvanOutpost.cs:415 — SylvanOutpost.PrepareTerrainForOutpost has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CindercragGlowRender.TrySampleCeiling (cognitive 26) · ×1
  • CindercragGlowRender.TrySampleCeiling (cognitive 26) Content/GameModes/BrutalMobs/Ambience/Cindercrag/CindercragGlowRender.cs:163 — CindercragGlowRender.TrySampleCeiling 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.
D2 · Cognitive Complexity · FleshfenDewRainProj.PreDraw (cognitive 26) · ×1
  • FleshfenDewRainProj.PreDraw (cognitive 26) Content/GameModes/BrutalMobs/Ambience/Fleshfen/Projectiles/FleshfenDewRainProj.cs:305 — FleshfenDewRainProj.PreDraw 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.
D2 · Cognitive Complexity · MireheartBeeCloudProj.AI (cognitive 26) · ×1
  • MireheartBeeCloudProj.AI (cognitive 26) Content/GameModes/BrutalMobs/Ambience/Mireheart/Projectiles/MireheartBeeCloudProj.cs:74 — MireheartBeeCloudProj.AI 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.
D2 · Cognitive Complexity · EliteMoveNPC.ServerParry (cognitive 26) · ×1
  • EliteMoveNPC.ServerParry (cognitive 26) Content/GameModes/BrutalMobs/EliteMove/EliteMoveNPC.cs:242 — EliteMoveNPC.ServerParry 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.
D2 · Cognitive Complexity · FrmAimLaneOmen.AI (cognitive 26) · ×1
  • FrmAimLaneOmen.AI (cognitive 26) Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmAimLaneOmen.cs:83 — FrmAimLaneOmen.AI 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.
D2 · Cognitive Complexity · LegionClownBomb.AI (cognitive 26) · ×1
  • LegionClownBomb.AI (cognitive 26) Content/GameModes/BrutalMobs/Legion/Projectiles/LegionClownBomb.cs:77 — LegionClownBomb.AI 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.
D2 · Cognitive Complexity · MrtLaserMarkLine.PreDraw (cognitive 26) · ×1
  • MrtLaserMarkLine.PreDraw (cognitive 26) Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserMarkLine.cs:170 — MrtLaserMarkLine.PreDraw 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.
D2 · Cognitive Complexity · WastesElementRing.AI (cognitive 26) · ×1
  • WastesElementRing.AI (cognitive 26) Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesElementRing.cs:51 — WastesElementRing.AI 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.
D2 · Cognitive Complexity · GsBoomerThrowHeldBase.AI (cognitive 26) · ×1
  • GsBoomerThrowHeldBase.AI (cognitive 26) Content/GameModes/GodSmith/Weapons/Boomerangs/GsBoomerThrowHeld.cs:78 — GsBoomerThrowHeldBase.AI 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.
D2 · Cognitive Complexity · GsMonkStaffT2GhastProj.AI (cognitive 26) · ×1
  • GsMonkStaffT2GhastProj.AI (cognitive 26) Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT2.cs:443 — GsMonkStaffT2GhastProj.AI 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.
D2 · Cognitive Complexity · GsHornetStaff.UpdateDive (cognitive 26) · ×1
  • GsHornetStaff.UpdateDive (cognitive 26) Content/GameModes/GodSmith/Weapons/SummonMinions/Schemes/GsHornetStaff.cs:98 — GsHornetStaff.UpdateDive 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.
D2 · Cognitive Complexity · ProjectileTithe.UpdateVisualWatch (cognitive 26) · ×1
  • ProjectileTithe.UpdateVisualWatch (cognitive 26) Content/HackTimes/Protocols/ProjectileTithe.cs:256 — ProjectileTithe.UpdateVisualWatch 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.
D2 · Cognitive Complexity · AutoCrafterTP.UpdateVisualFX (cognitive 26) · ×1
  • AutoCrafterTP.UpdateVisualFX (cognitive 26) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterTP.cs:328 — AutoCrafterTP.UpdateVisualFX 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.
D2 · Cognitive Complexity · FluidInjectorTP.UpdateVisualFx (cognitive 26) · ×1
  • FluidInjectorTP.UpdateVisualFx (cognitive 26) Content/Industrials/ElectricPowers/FluidInjectors/FluidInjectorTP.cs:158 — FluidInjectorTP.UpdateVisualFx 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.
D2 · Cognitive Complexity · GridSwitchTP.UpdateLeverEnvelope (cognitive 26) · ×1
  • GridSwitchTP.UpdateLeverEnvelope (cognitive 26) Content/Industrials/ElectricPowers/GridSwitches/GridSwitchTP.cs:92 — GridSwitchTP.UpdateLeverEnvelope 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.
D2 · Cognitive Complexity · TeleportPortalDraw.PreDrawEverything (cognitive 26) · ×1
  • TeleportPortalDraw.PreDrawEverything (cognitive 26) Content/Industrials/ElectricPowers/TeleportStations/TeleportStationFX.cs:202 — TeleportPortalDraw.PreDrawEverything 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.
D2 · Cognitive Complexity · GeneratorReadoutUI.UpdateElement (cognitive 26) · ×1
  • GeneratorReadoutUI.UpdateElement (cognitive 26) Content/Industrials/Generator/GeneratorReadout.cs:124 — GeneratorReadoutUI.UpdateElement 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.
D2 · Cognitive Complexity · MachineModuleRack.Refresh (cognitive 26) · ×1
  • MachineModuleRack.Refresh (cognitive 26) Content/Industrials/MachineModules/MachineModuleCore.cs:176 — MachineModuleRack.Refresh 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.
D2 · Cognitive Complexity · ItemPipelineTP.UpdateOutputMode (cognitive 26) · ×1
  • ItemPipelineTP.UpdateOutputMode (cognitive 26) Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs:304 — ItemPipelineTP.UpdateOutputMode 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.
D2 · Cognitive Complexity · FallenKingsCrownPlayer.PostUpdate (cognitive 26) · ×1
  • FallenKingsCrownPlayer.PostUpdate (cognitive 26) Content/Items/Accessories/BrutalRelics/KingSlime/FallenKingsCrownPlayer.cs:77 — FallenKingsCrownPlayer.PostUpdate 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.
D2 · Cognitive Complexity · AbyssrendHeld.ThrustAI (cognitive 26) · ×1
  • AbyssrendHeld.ThrustAI (cognitive 26) Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:235 — AbyssrendHeld.ThrustAI 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.
D2 · Cognitive Complexity · SlimeGelOrb.UpdateConnections (cognitive 26) · ×1
  • SlimeGelOrb.UpdateConnections (cognitive 26) Content/LegendWeapon/HalibutLegend/FishSkills/FishSlime.cs:501 — SlimeGelOrb.UpdateConnections 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.
D2 · Cognitive Complexity · KikasaScourgeFX.UpdateSideLash (cognitive 26) · ×1
  • KikasaScourgeFX.UpdateSideLash (cognitive 26) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaScourgeFX.cs:444 — KikasaScourgeFX.UpdateSideLash 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.
D2 · Cognitive Complexity · KikasaScourgeFX.DrawHands (cognitive 26) · ×1
  • KikasaScourgeFX.DrawHands (cognitive 26) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaScourgeFX.cs:742 — KikasaScourgeFX.DrawHands 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.
D2 · Cognitive Complexity · KikasaRainUmbrella.UpdateFlip (cognitive 26) · ×1
  • KikasaRainUmbrella.UpdateFlip (cognitive 26) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:922 — KikasaRainUmbrella.UpdateFlip 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.
D2 · Cognitive Complexity · KikasaZenithServant.DrawGlow (cognitive 26) · ×1
  • KikasaZenithServant.DrawGlow (cognitive 26) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1438 — KikasaZenithServant.DrawGlow 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.
D2 · Cognitive Complexity · KikasaBloomSerpentServant.UpdateNeedleRipple (cognitive 26) · ×1
  • KikasaBloomSerpentServant.UpdateNeedleRipple (cognitive 26) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:530 — KikasaBloomSerpentServant.UpdateNeedleRipple 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.
D2 · Cognitive Complexity · KikasaBrainServant.UpdateSacrifice (cognitive 26) · ×1
  • KikasaBrainServant.UpdateSacrifice (cognitive 26) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:706 — KikasaBrainServant.UpdateSacrifice 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.
D2 · Cognitive Complexity · KikasaDeerclopsServant.DrawGlow (cognitive 26) · ×1
  • KikasaDeerclopsServant.DrawGlow (cognitive 26) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:1356 — KikasaDeerclopsServant.DrawGlow 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.
D2 · Cognitive Complexity · FuTing.OnRainHitNPC (cognitive 26) · ×1
  • FuTing.OnRainHitNPC (cognitive 26) Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuTing.cs:85 — FuTing.OnRainHitNPC 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.
D2 · Cognitive Complexity · CrimsonRendSlash.OnHitNPC (cognitive 26) · ×1
  • CrimsonRendSlash.OnHitNPC (cognitive 26) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1497 — CrimsonRendSlash.OnHitNPC 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.
D2 · Cognitive Complexity · OniMeiPaperEffigy.PreDraw (cognitive 26) · ×1
  • OniMeiPaperEffigy.PreDraw (cognitive 26) Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiPaperEffigy.cs:258 — OniMeiPaperEffigy.PreDraw 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.
D2 · Cognitive Complexity · OniSlash.OnHitNPC (cognitive 26) · ×1
  • OniSlash.OnHitNPC (cognitive 26) Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1406 — OniSlash.OnHitNPC 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.
D2 · Cognitive Complexity · OnikiriNet.ReceiveMeiRequest (cognitive 26) · ×1
  • OnikiriNet.ReceiveMeiRequest (cognitive 26) Content/LegendWeapon/OnikiriLegend/OnikiriNet.cs:217 — OnikiriNet.ReceiveMeiRequest 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.
D2 · Cognitive Complexity · OniTalismanHud.LogicUpdate (cognitive 26) · ×1
  • OniTalismanHud.LogicUpdate (cognitive 26) Content/LegendWeapon/OnikiriLegend/UI/OniTalismanHud.cs:232 — OniTalismanHud.LogicUpdate 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.
D2 · Cognitive Complexity · CyberspaceActionNet.ExecuteDomainAction (cognitive 26) · ×1
  • CyberspaceActionNet.ExecuteDomainAction (cognitive 26) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspaceActionNet.cs:192 — CyberspaceActionNet.ExecuteDomainAction 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.
D2 · Cognitive Complexity · SHPCRecycleCellRingProj.AI (cognitive 26) · ×1
  • SHPCRecycleCellRingProj.AI (cognitive 26) Content/LegendWeapon/SHPCLegend/Modules/Grip/EfficientGripModule.cs:362 — SHPCRecycleCellRingProj.AI 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.
D2 · Cognitive Complexity · ErgonomicStockModule.OnPlayerUpdate (cognitive 26) · ×1
  • ErgonomicStockModule.OnPlayerUpdate (cognitive 26) Content/LegendWeapon/SHPCLegend/Modules/Stock/ErgonomicStockModule.cs:215 — ErgonomicStockModule.OnPlayerUpdate 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.
D2 · Cognitive Complexity · MoldProcessingPanel.HandleClick (cognitive 26) · ×1
  • MoldProcessingPanel.HandleClick (cognitive 26) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingPanel.cs:100 — MoldProcessingPanel.HandleClick 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.
D2 · Cognitive Complexity · BrainLanceWavesState.OnUpdate (cognitive 26) · ×1
  • BrainLanceWavesState.OnUpdate (cognitive 26) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainLanceWavesState.cs:47 — BrainLanceWavesState.OnUpdate 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.
D2 · Cognitive Complexity · EocServantEncircleState.UpdateConverge (cognitive 26) · ×1
  • EocServantEncircleState.UpdateConverge (cognitive 26) Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocServantEncircleState.cs:157 — EocServantEncircleState.UpdateConverge 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.
D2 · Cognitive Complexity · GolemFistPunchState.OnUpdate (cognitive 26) · ×1
  • GolemFistPunchState.OnUpdate (cognitive 26) Content/NPCs/BrutalNPCs/BrutalGolem/States/Fists/GolemFistStates.cs:126 — GolemFistPunchState.OnUpdate 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.
D2 · Cognitive Complexity · KingSlimeEngulfState.UpdateAirborne (cognitive 26) · ×1
  • KingSlimeEngulfState.UpdateAirborne (cognitive 26) Content/NPCs/BrutalNPCs/BrutalKingSlime/States/KingSlimeEngulfState.cs:243 — KingSlimeEngulfState.UpdateAirborne 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.
D2 · Cognitive Complexity · KingSlimeHopState.OnUpdate (cognitive 26) · ×1
  • KingSlimeHopState.OnUpdate (cognitive 26) Content/NPCs/BrutalNPCs/BrutalKingSlime/States/KingSlimeHopState.cs:41 — KingSlimeHopState.OnUpdate 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.
D2 · Cognitive Complexity · TwinsRenderHelper.DrawChargeEffect (cognitive 26) · ×1
  • TwinsRenderHelper.DrawChargeEffect (cognitive 26) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Rendering/TwinsRenderHelper.cs:14 — TwinsRenderHelper.DrawChargeEffect 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.
D2 · Cognitive Complexity · SpazmatismShadowDashState.ExecuteDashSegments (cognitive 26) · ×1
  • SpazmatismShadowDashState.ExecuteDashSegments (cognitive 26) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismShadowDashState.cs:120 — SpazmatismShadowDashState.ExecuteDashSegments 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.
D2 · Cognitive Complexity · QueenPrismBeamProj.AI (cognitive 26) · ×1
  • QueenPrismBeamProj.AI (cognitive 26) Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenPrismBeamProj.cs:147 — QueenPrismBeamProj.AI 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.
D2 · Cognitive Complexity · QueenDeathState.OnUpdate (cognitive 26) · ×1
  • QueenDeathState.OnUpdate (cognitive 26) Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenDespawnState.cs:112 — QueenDeathState.OnUpdate 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.
D2 · Cognitive Complexity · FssLegRig.Update (cognitive 26) · ×1
  • FssLegRig.Update (cognitive 26) Content/NPCs/FestersandSerpents/FssLegRig.cs:116 — FssLegRig.Update 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.
D2 · Cognitive Complexity · FssFieldDetonateState.OnUpdate (cognitive 26) · ×1
  • FssFieldDetonateState.OnUpdate (cognitive 26) Content/NPCs/FestersandSerpents/States/FssFieldDetonateState.cs:60 — FssFieldDetonateState.OnUpdate 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.
D2 · Cognitive Complexity · SeaShrimpCavitationBubble.AI (cognitive 26) · ×1
  • SeaShrimpCavitationBubble.AI (cognitive 26) Content/NPCs/SeaShrimp/Projectiles/SeaShrimpCavitationBubble.cs:75 — SeaShrimpCavitationBubble.AI 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.
D2 · Cognitive Complexity · SeaShrimpCrescentClapState.OnUpdate (cognitive 26) · ×1
  • SeaShrimpCrescentClapState.OnUpdate (cognitive 26) Content/NPCs/SeaShrimp/States/SeaShrimpCrescentClapState.cs:30 — SeaShrimpCrescentClapState.OnUpdate 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.
D2 · Cognitive Complexity · SeaShrimpSuperCavitationState.OnUpdate (cognitive 26) · ×1
  • SeaShrimpSuperCavitationState.OnUpdate (cognitive 26) Content/NPCs/SeaShrimp/States/SeaShrimpSuperCavitationState.cs:43 — SeaShrimpSuperCavitationState.OnUpdate 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.
D2 · Cognitive Complexity · ChroniclePen.Wrap (cognitive 26) · ×1
  • ChroniclePen.Wrap (cognitive 26) Content/QuestLogs/Styles/Chronicle/ChroniclePen.cs:202 — ChroniclePen.Wrap 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.
D2 · Cognitive Complexity · GaolRoomNet.Receive (cognitive 26) · ×1
  • GaolRoomNet.Receive (cognitive 26) Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolRoomNet.cs:70 — GaolRoomNet.Receive 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.
D2 · Cognitive Complexity · L4Content.LinkWellSide (cognitive 26) · ×1
  • L4Content.LinkWellSide (cognitive 26) Content/Scenarios/Dungeonworld/Gen/Layers/L4/L4Content.cs:456 — L4Content.LinkWellSide 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.
D2 · Cognitive Complexity · L4WaterWorks.FillState (cognitive 26) · ×1
  • L4WaterWorks.FillState (cognitive 26) Content/Scenarios/Dungeonworld/Gen/Layers/L4/L4WaterWorks.cs:69 — L4WaterWorks.FillState 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.
D2 · Cognitive Complexity · L5Rooms.BuildHall (cognitive 26) · ×1
  • L5Rooms.BuildHall (cognitive 26) Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Rooms.cs:56 — L5Rooms.BuildHall 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.
D2 · Cognitive Complexity · L6Content.PlaceAndBuildNode (cognitive 26) · ×1
  • L6Content.PlaceAndBuildNode (cognitive 26) Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Content.cs:223 — L6Content.PlaceAndBuildNode 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.
D2 · Cognitive Complexity · FoundryOverseer.DrawGlowLayers (cognitive 26) · ×1
  • FoundryOverseer.DrawGlowLayers (cognitive 26) Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:1392 — FoundryOverseer.DrawGlowLayers 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.
D2 · Cognitive Complexity · KiyumeDirector.TryClaimScare (cognitive 26) · ×1
  • KiyumeDirector.TryClaimScare (cognitive 26) Content/Scenarios/Kiyume/Ambience/KiyumeDirector.cs:79 — KiyumeDirector.TryClaimScare 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.
D2 · Cognitive Complexity · KiyumeFogSim.SpreadLight (cognitive 26) · ×1
  • KiyumeFogSim.SpreadLight (cognitive 26) Content/Scenarios/Kiyume/Fog/KiyumeFogSim.cs:324 — KiyumeFogSim.SpreadLight 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.
D2 · Cognitive Complexity · KiyumeFogSystem.ApplyPassUniforms (cognitive 26) · ×1
  • KiyumeFogSystem.ApplyPassUniforms (cognitive 26) Content/Scenarios/Kiyume/Fog/KiyumeFogSystem.cs:256 — KiyumeFogSystem.ApplyPassUniforms 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.
D2 · Cognitive Complexity · OldNetThreatField.TickBulkheads (cognitive 26) · ×1
  • OldNetThreatField.TickBulkheads (cognitive 26) Content/Scenarios/OldNet/NPCs/OldNetThreatField.cs:457 — OldNetThreatField.TickBulkheads 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.
D2 · Cognitive Complexity · JunkmanBase.LoadChest (cognitive 26) · ×1
  • JunkmanBase.LoadChest (cognitive 26) Content/Structures/DatIO/JunkmanBase.cs:53 — JunkmanBase.LoadChest 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.
D2 · Cognitive Complexity · SylvanOutpost.EvaluatePositionSimple (cognitive 26) · ×1
  • SylvanOutpost.EvaluatePositionSimple (cognitive 26) Content/Structures/DatIO/SylvanOutpost.cs:360 — SylvanOutpost.EvaluatePositionSimple 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.
D2 · Cognitive Complexity · SettingsCategory.HandleClick (cognitive 26) · ×1
  • SettingsCategory.HandleClick (cognitive 26) Content/UIs/OverhaulSettings/SettingsCategory.cs:180 — SettingsCategory.HandleClick 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.
D2 · Cognitive Complexity · SvgPathPen.Stroke (cognitive 26) · ×1
  • SvgPathPen.Stroke (cognitive 26) Content/UIs/UIEffect/SvgPathPen.cs:74 — SvgPathPen.Stroke 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.
D2 · Cognitive Complexity · WraithPlayer.LoadData (cognitive 26) · ×1
  • WraithPlayer.LoadData (cognitive 26) Content/Wraiths/Runtime/WraithPlayer.cs:546 — WraithPlayer.LoadData 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.
D2 · Cognitive Complexity · QuestLogsAPI.TryRegisterNode (cognitive 25) · ×1
  • QuestLogsAPI.TryRegisterNode (cognitive 25) API/QuestLogsAPI.cs:28 — QuestLogsAPI.TryRegisterNode has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LumindepthAmbientRender.UpdateDapples (cognitive 25) · ×1
  • LumindepthAmbientRender.UpdateDapples (cognitive 25) Content/GameModes/BrutalMobs/Ambience/Lumindepth/LumindepthAmbientRender.cs:82 — LumindepthAmbientRender.UpdateDapples has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · StonewakeGazePillarProj.AI (cognitive 25) · ×1
  • StonewakeGazePillarProj.AI (cognitive 25) Content/GameModes/BrutalMobs/Ambience/Stonewake/Projectiles/StonewakeGazePillarProj.cs:93 — StonewakeGazePillarProj.AI has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FlgAimLineOmen.AI (cognitive 25) · ×1
  • FlgAimLineOmen.AI (cognitive 25) Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:67 — FlgAimLineOmen.AI has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FlgStabGlintOmen.AI (cognitive 25) · ×1
  • FlgStabGlintOmen.AI (cognitive 25) Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgStabGlintOmen.cs:62 — FlgStabGlintOmen.AI has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FrmYetiConeOmen.AI (cognitive 25) · ×1
  • FrmYetiConeOmen.AI (cognitive 25) Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmYetiConeOmen.cs:88 — FrmYetiConeOmen.AI has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GyGhostNameThread.AI (cognitive 25) · ×1
  • GyGhostNameThread.AI (cognitive 25) Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyGhostNameThread.cs:72 — GyGhostNameThread.AI has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SandveilVortexArrayOmen.AI (cognitive 25) · ×1
  • SandveilVortexArrayOmen.AI (cognitive 25) Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilVortexArrayOmen.cs:135 — SandveilVortexArrayOmen.AI has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TempleBrutalNPC.MonkPresent (cognitive 25) · ×1
  • TempleBrutalNPC.MonkPresent (cognitive 25) Content/GameModes/BrutalMobs/Temple/TempleBrutalNPC.cs:870 — TempleBrutalNPC.MonkPresent has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GsPhoenixBlasterHeld.AI (cognitive 25) · ×1
  • GsPhoenixBlasterHeld.AI (cognitive 25) Content/GameModes/GodSmith/Weapons/Guns/GsPhoenixBlaster.cs:154 — GsPhoenixBlasterHeld.AI has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GameModeTabUI.Update (cognitive 25) · ×1
  • GameModeTabUI.Update (cognitive 25) Content/GameModes/UI/GameModeTabUI.cs:99 — GameModeTabUI.Update has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HackTimeNetSync.TryReadTarget (cognitive 25) · ×1
  • HackTimeNetSync.TryReadTarget (cognitive 25) Content/HackTimes/HackTimeNetSync.cs:1342 — HackTimeNetSync.TryReadTarget has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · StationSnapshot.SatisfiesConditions (cognitive 25) · ×1
  • StationSnapshot.SatisfiesConditions (cognitive 25) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterRecipeId.cs:124 — StationSnapshot.SatisfiesConditions has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MushroomFarmerTP.PlayActionEffect (cognitive 25) · ×1
  • MushroomFarmerTP.PlayActionEffect (cognitive 25) Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:567 — MushroomFarmerTP.PlayActionEffect has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SensorTP.UpdateEyeEnvelope (cognitive 25) · ×1
  • SensorTP.UpdateEyeEnvelope (cognitive 25) Content/Industrials/ElectricPowers/Sensors/SensorTP.cs:292 — SensorTP.UpdateEyeEnvelope has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TeleportStationUI.Update (cognitive 25) · ×1
  • TeleportStationUI.Update (cognitive 25) Content/Industrials/ElectricPowers/TeleportStations/TeleportStationUI.cs:186 — TeleportStationUI.Update has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ThrowerUI.HandleSlotInteraction (cognitive 25) · ×1
  • ThrowerUI.HandleSlotInteraction (cognitive 25) Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:323 — ThrowerUI.HandleSlotInteraction has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · WingsOfInterferenceRender.DrawTrails (cognitive 25) · ×1
  • WingsOfInterferenceRender.DrawTrails (cognitive 25) Content/Items/Accessories/BrutalRelics/EmpressOfLight/InterferenceWingRender.cs:156 — WingsOfInterferenceRender.DrawTrails has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · RefractionWaltzBeamProj.AI (cognitive 25) · ×1
  • RefractionWaltzBeamProj.AI (cognitive 25) Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzBeamProj.cs:93 — RefractionWaltzBeamProj.AI has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SingularityBlackHole.AI (cognitive 25) · ×1
  • SingularityBlackHole.AI (cognitive 25) Content/Items/Accessories/EyeOfSingularity.cs:96 — SingularityBlackHole.AI has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EnergySwordHeld.AI (cognitive 25) · ×1
  • EnergySwordHeld.AI (cognitive 25) Content/Items/Melee/EnergySword.cs:222 — EnergySwordHeld.AI has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · NeutronScytheHeld.AI (cognitive 25) · ×1
  • NeutronScytheHeld.AI (cognitive 25) Content/Items/Melee/NeutronScythe.cs:163 — NeutronScytheHeld.AI has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LonginusThrow.DrawPrimitives (cognitive 25) · ×1
  • LonginusThrow.DrawPrimitives (cognitive 25) Content/Items/Melee/SpearOfLonginuses/LonginusThrow.cs:184 — LonginusThrow.DrawPrimitives has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BloodButchererHeld.HandlePhaseEvents (cognitive 25) · ×1
  • BloodButchererHeld.HandlePhaseEvents (cognitive 25) Content/Items/Modifys/RBloodButcherer.cs:406 — BloodButchererHeld.HandlePhaseEvents has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · NeutronBowHeld.UpdateRightCharge (cognitive 25) · ×1
  • NeutronBowHeld.UpdateRightCharge (cognitive 25) Content/Items/Ranged/NeutronBows/NeutronBow.cs:192 — NeutronBowHeld.UpdateRightCharge has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ThornstringHeld.UpdateRightCharge (cognitive 25) · ×1
  • ThornstringHeld.UpdateRightCharge (cognitive 25) Content/Items/Ranged/Thornstrings/ThornstringHeld.cs:115 — ThornstringHeld.UpdateRightCharge has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TiroFinaleRenderer.DrawHeldLayer (cognitive 25) · ×1
  • TiroFinaleRenderer.DrawHeldLayer (cognitive 25) Content/Items/Ranged/TiroFinales/TiroFinaleRenderer.cs:41 — TiroFinaleRenderer.DrawHeldLayer has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · UndertowHeld.UpdateRightCharge (cognitive 25) · ×1
  • UndertowHeld.UpdateRightCharge (cognitive 25) Content/Items/Ranged/Undertows/UndertowHeld.cs:118 — UndertowHeld.UpdateRightCharge has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · UndertowSpine.AI (cognitive 25) · ×1
  • UndertowSpine.AI (cognitive 25) Content/Items/Ranged/Undertows/UndertowSpine.cs:56 — UndertowSpine.AI has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DestroyerHead.AttackAI (cognitive 25) · ×1
  • DestroyerHead.AttackAI (cognitive 25) Content/Items/Summon/StaffoftheDestroyer.cs:215 — DestroyerHead.AttackAI has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FishVoodooRitual.AI (cognitive 25) · ×1
  • FishVoodooRitual.AI (cognitive 25) Content/LegendWeapon/HalibutLegend/FishSkills/FishVoodooRitual.cs:149 — FishVoodooRitual.AI has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HalibutOverride.Shoot (cognitive 25) · ×1
  • HalibutOverride.Shoot (cognitive 25) Content/LegendWeapon/HalibutLegend/HalibutOverride.cs:197 — HalibutOverride.Shoot has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · AtlasFishStudyPanel.Update (cognitive 25) · ×1
  • AtlasFishStudyPanel.Update (cognitive 25) Content/LegendWeapon/HalibutLegend/UI/Atlas/AtlasFishStudyPanel.cs:124 — AtlasFishStudyPanel.Update has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · AtlasSkillSea.DrawDetailCard (cognitive 25) · ×1
  • AtlasSkillSea.DrawDetailCard (cognitive 25) Content/LegendWeapon/HalibutLegend/UI/Atlas/AtlasSkillSea.cs:927 — AtlasSkillSea.DrawDetailCard has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaMinionDrown.Update (cognitive 25) · ×1
  • KikasaMinionDrown.Update (cognitive 25) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaMinionDrown.cs:171 — KikasaMinionDrown.Update has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaGunServant.UpdateFollow (cognitive 25) · ×1
  • KikasaGunServant.UpdateFollow (cognitive 25) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:482 — KikasaGunServant.UpdateFollow has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaGunServant.UpdateCarousel (cognitive 25) · ×1
  • KikasaGunServant.UpdateCarousel (cognitive 25) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:680 — KikasaGunServant.UpdateCarousel has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaBrainServant.UpdateBlink (cognitive 25) · ×1
  • KikasaBrainServant.UpdateBlink (cognitive 25) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:593 — KikasaBrainServant.UpdateBlink has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaDeerclopsBloodSpike.AI (cognitive 25) · ×1
  • KikasaDeerclopsBloodSpike.AI (cognitive 25) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsBloodSpike.cs:95 — KikasaDeerclopsBloodSpike.AI has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaEmpressServant.DrawGlow (cognitive 25) · ×1
  • KikasaEmpressServant.DrawGlow (cognitive 25) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:1036 — KikasaEmpressServant.DrawGlow has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaKingSlimeServant.SlamImpact (cognitive 25) · ×1
  • KikasaKingSlimeServant.SlamImpact (cognitive 25) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:725 — KikasaKingSlimeServant.SlamImpact has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaPlanteraServant.DrawGlow (cognitive 25) · ×1
  • KikasaPlanteraServant.DrawGlow (cognitive 25) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1519 — KikasaPlanteraServant.DrawGlow has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaTwinsServant.UpdateCord (cognitive 25) · ×1
  • KikasaTwinsServant.UpdateCord (cognitive 25) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1223 — KikasaTwinsServant.UpdateCord has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaPanoramaUI.ResolveHover (cognitive 25) · ×1
  • KikasaPanoramaUI.ResolveHover (cognitive 25) Content/LegendWeapon/KikasaLegend/UI/Panorama/KikasaPanoramaUI.cs:642 — KikasaPanoramaUI.ResolveHover has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniSigilRenderer.DrawEdges (cognitive 25) · ×1
  • OniSigilRenderer.DrawEdges (cognitive 25) Content/LegendWeapon/OnikiriLegend/UI/OniSigilRenderer.cs:239 — OniSigilRenderer.DrawEdges has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SHPCFrostfernLineProj.BuildLSystem (cognitive 25) · ×1
  • SHPCFrostfernLineProj.BuildLSystem (cognitive 25) Content/LegendWeapon/SHPCLegend/Modules/Barrel/FrostfernBarrelModule.cs:110 — SHPCFrostfernLineProj.BuildLSystem has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SHPCRedlineGaugeProj.DrawPrimitives (cognitive 25) · ×1
  • SHPCRedlineGaugeProj.DrawPrimitives (cognitive 25) Content/LegendWeapon/SHPCLegend/Modules/Barrel/RapidBarrelModule.cs:555 — SHPCRedlineGaugeProj.DrawPrimitives has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ResonanceFrameModule.SweepDead (cognitive 25) · ×1
  • ResonanceFrameModule.SweepDead (cognitive 25) Content/LegendWeapon/SHPCLegend/Modules/Frame/ResonanceFrameModule.cs:332 — ResonanceFrameModule.SweepDead has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SHPCRecycleCellRingProj.DrawAdditiveAfterNon (cognitive 25) · ×1
  • SHPCRecycleCellRingProj.DrawAdditiveAfterNon (cognitive 25) Content/LegendWeapon/SHPCLegend/Modules/Grip/EfficientGripModule.cs:524 — SHPCRecycleCellRingProj.DrawAdditiveAfterNon has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SHPCModuleItem.BuildStatLines (cognitive 25) · ×1
  • SHPCModuleItem.BuildStatLines (cognitive 25) Content/LegendWeapon/SHPCLegend/Modules/SHPCModuleItem.cs:92 — SHPCModuleItem.BuildStatLines has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MoldCodexPanel.DrawCustomTooltip (cognitive 25) · ×1
  • MoldCodexPanel.DrawCustomTooltip (cognitive 25) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:316 — MoldCodexPanel.DrawCustomTooltip has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BssSandPillar.UpdateOmen (cognitive 25) · ×1
  • BssSandPillar.UpdateOmen (cognitive 25) Content/NPCs/BloomsandSerpents/BssSandPillar.cs:404 — BssSandPillar.UpdateOmen has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DeerclopsShadowClawState.SpawnWave (cognitive 25) · ×1
  • DeerclopsShadowClawState.SpawnWave (cognitive 25) Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsShadowClawState.cs:68 — DeerclopsShadowClawState.SpawnWave has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FishronDiveBreachState.UpdateAirRoll (cognitive 25) · ×1
  • FishronDiveBreachState.UpdateAirRoll (cognitive 25) Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronDiveBreachState.cs:236 — FishronDiveBreachState.UpdateAirRoll has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EmpressTrackBeam.AI (cognitive 25) · ×1
  • EmpressTrackBeam.AI (cognitive 25) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Projectiles/EmpressTrackBeam.cs:87 — EmpressTrackBeam.AI has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EmpressTrackBeam.MarkerUpdate (cognitive 25) · ×1
  • EmpressTrackBeam.MarkerUpdate (cognitive 25) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Projectiles/EmpressTrackBeam.cs:140 — EmpressTrackBeam.MarkerUpdate has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EmpressIntroState.OnUpdate (cognitive 25) · ×1
  • EmpressIntroState.OnUpdate (cognitive 25) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/States/EmpressIntroState.cs:30 — EmpressIntroState.OnUpdate has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EmpressLacewingState.OnUpdate (cognitive 25) · ×1
  • EmpressLacewingState.OnUpdate (cognitive 25) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/States/EmpressLacewingState.cs:37 — EmpressLacewingState.OnUpdate has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GolemStompComboState.OnUpdate (cognitive 25) · ×1
  • GolemStompComboState.OnUpdate (cognitive 25) Content/NPCs/BrutalNPCs/BrutalGolem/States/GolemStompComboState.cs:34 — GolemStompComboState.OnUpdate has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CultistOrbitPath.PreDraw (cognitive 25) · ×1
  • CultistOrbitPath.PreDraw (cognitive 25) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistOrbitPath.cs:231 — CultistOrbitPath.PreDraw has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MLordLocomotion.TryLaunchStep (cognitive 25) · ×1
  • MLordLocomotion.TryLaunchStep (cognitive 25) Content/NPCs/BrutalNPCs/BrutalMoonLord/Core/MLordLocomotion.cs:434 — MLordLocomotion.TryLaunchStep has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · QueenRoyalChandelierProj.AI (cognitive 25) · ×1
  • QueenRoyalChandelierProj.AI (cognitive 25) Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenRoyalChandelierProj.cs:63 — QueenRoyalChandelierProj.AI has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · QueenSpikeRingState.OnUpdate (cognitive 25) · ×1
  • QueenSpikeRingState.OnUpdate (cognitive 25) Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenSpikeRingState.cs:50 — QueenSpikeRingState.OnUpdate has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PrimeIntroState.OnUpdate (cognitive 25) · ×1
  • PrimeIntroState.OnUpdate (cognitive 25) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/PrimeIntroState.cs:20 — PrimeIntroState.OnUpdate has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FssClawReapState.UpdateSlice (cognitive 25) · ×1
  • FssClawReapState.UpdateSlice (cognitive 25) Content/NPCs/FestersandSerpents/States/FssClawReapState.cs:116 — FssClawReapState.UpdateSlice has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ScrapCrossSpinState.OnUpdate (cognitive 25) · ×1
  • ScrapCrossSpinState.OnUpdate (cognitive 25) Content/NPCs/ScrapCommanders/States/ScrapCrossSpinState.cs:34 — ScrapCrossSpinState.OnUpdate has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · L6Rooms.BuildWell (cognitive 25) · ×1
  • L6Rooms.BuildWell (cognitive 25) Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Rooms.cs:552 — L6Rooms.BuildWell has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GuideTrailPass.PaintThreshold (cognitive 25) · ×1
  • GuideTrailPass.PaintThreshold (cognitive 25) Content/Scenarios/Dungeonworld/Gen/Passes/GuideTrailPass.cs:233 — GuideTrailPass.PaintThreshold has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SlagVentBelt.TryBuildCavern (cognitive 25) · ×1
  • SlagVentBelt.TryBuildCavern (cognitive 25) Content/Scenarios/Dungeonworld/Gen/Zones/SlagVentBelt.cs:127 — SlagVentBelt.TryBuildCavern has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Undrowned.UpdateTideSlam (cognitive 25) · ×1
  • Undrowned.UpdateTideSlam (cognitive 25) Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:1003 — Undrowned.UpdateTideSlam has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KiyumeGroundFogRender.DetectFalls (cognitive 25) · ×1
  • KiyumeGroundFogRender.DetectFalls (cognitive 25) Content/Scenarios/Kiyume/Fog/KiyumeGroundFogRender.cs:277 — KiyumeGroundFogRender.DetectFalls has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KiyumeWhiteHound.TrySpawn (cognitive 25) · ×1
  • KiyumeWhiteHound.TrySpawn (cognitive 25) Content/Scenarios/Kiyume/NPCs/KiyumeWhiteHound.cs:288 — KiyumeWhiteHound.TrySpawn has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OldNetTracerICE.PreDraw (cognitive 25) · ×1
  • OldNetTracerICE.PreDraw (cognitive 25) Content/Scenarios/OldNet/NPCs/OldNetTracerICE.cs:403 — OldNetTracerICE.PreDraw has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · WeaponSkillHud.Update (cognitive 25) · ×1
  • WeaponSkillHud.Update (cognitive 25) Content/UIs/WeaponSkills/WeaponSkillHud.cs:135 — WeaponSkillHud.Update has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BrideHallRenderer.OnRiteTick (cognitive 25) · ×1
  • BrideHallRenderer.OnRiteTick (cognitive 25) Content/Wraiths/Abilities/CrimsonBrides/BrideHallRenderer.cs:79 — BrideHallRenderer.OnRiteTick has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CWRNpc.OnKill (cognitive 24) · ×1
  • CWRNpc.OnKill (cognitive 24) Content/CWRNpc.cs:124 — CWRNpc.OnKill has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EntrustTrackerWidget.DrawDefaultContent (cognitive 24) · ×1
  • EntrustTrackerWidget.DrawDefaultContent (cognitive 24) Content/EntrustManager/EntrustTrackerWidget.cs:404 — EntrustTrackerWidget.DrawDefaultContent has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DuskhallGazeRender.EndEntityDraw (cognitive 24) · ×1
  • DuskhallGazeRender.EndEntityDraw (cognitive 24) Content/GameModes/BrutalMobs/Ambience/Duskhall/DuskhallGazeRender.cs:35 — DuskhallGazeRender.EndEntityDraw has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · VerdantPlayer.PostUpdate (cognitive 24) · ×1
  • VerdantPlayer.PostUpdate (cognitive 24) Content/GameModes/BrutalMobs/Ambience/Verdant/VerdantPlayer.cs:44 — VerdantPlayer.PostUpdate has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DungeonDeepNPC.TickSkull (cognitive 24) · ×1
  • DungeonDeepNPC.TickSkull (cognitive 24) Content/GameModes/BrutalMobs/DungeonDeep/DungeonDeepNPC.Ranged.cs:198 — DungeonDeepNPC.TickSkull has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FrmFlockoBurstOmen.AI (cognitive 24) · ×1
  • FrmFlockoBurstOmen.AI (cognitive 24) Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmFlockoBurstOmen.cs:75 — FrmFlockoBurstOmen.AI has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · NightPackNPC.TickTelegraph (cognitive 24) · ×1
  • NightPackNPC.TickTelegraph (cognitive 24) Content/GameModes/BrutalMobs/NightPack/NightPackNPC.cs:274 — NightPackNPC.TickTelegraph has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · StonebornGazeOmen.AI (cognitive 24) · ×1
  • StonebornGazeOmen.AI (cognitive 24) Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornGazeOmen.cs:79 — StonebornGazeOmen.AI has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GsHarpoonSpearProj.AI (cognitive 24) · ×1
  • GsHarpoonSpearProj.AI (cognitive 24) Content/GameModes/GodSmith/Weapons/Guns/GsHarpoon.cs:165 — GsHarpoonSpearProj.AI has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · StressInvert.TickCollisionDamage (cognitive 24) · ×1
  • StressInvert.TickCollisionDamage (cognitive 24) Content/HackTimes/Protocols/StressInvert.cs:151 — StressInvert.TickCollisionDamage has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TileConscript.OnApply (cognitive 24) · ×1
  • TileConscript.OnApply (cognitive 24) Content/HackTimes/Protocols/TileConscript.cs:177 — TileConscript.OnApply has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PlayerHackHud.DrawImplantPanel (cognitive 24) · ×1
  • PlayerHackHud.DrawImplantPanel (cognitive 24) Content/HackTimes/PvP/UI/PlayerHackHud.cs:585 — PlayerHackHud.DrawImplantPanel has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ApiaryTP.CheckEnvironment (cognitive 24) · ×1
  • ApiaryTP.CheckEnvironment (cognitive 24) Content/Industrials/ElectricPowers/Apiaries/ApiaryTP.cs:255 — ApiaryTP.CheckEnvironment has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FluidPipelineTP.Draw (cognitive 24) · ×1
  • FluidPipelineTP.Draw (cognitive 24) Content/Industrials/MaterialFlow/Fluids/FluidPipeline.cs:327 — FluidPipelineTP.Draw has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · RealityShockProj.AI (cognitive 24) · ×1
  • RealityShockProj.AI (cognitive 24) Content/Items/Accessories/ArcaneThroneOfEternity.cs:376 — RealityShockProj.AI has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · JusticeUnveiledCross.AI (cognitive 24) · ×1
  • JusticeUnveiledCross.AI (cognitive 24) Content/Items/Accessories/JusticeUnveileds/JusticeUnveiledCross.cs:38 — JusticeUnveiledCross.AI has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DestroyersBladeHeldBase.AI (cognitive 24) · ×1
  • DestroyersBladeHeldBase.AI (cognitive 24) Content/Items/Melee/DestroyersBlade.cs:199 — DestroyersBladeHeldBase.AI has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · WraithKunaiProj.AI (cognitive 24) · ×1
  • WraithKunaiProj.AI (cognitive 24) Content/Items/Melee/WraithKunai.cs:107 — WraithKunaiProj.AI has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BloodButchererHeld.HandleParticles (cognitive 24) · ×1
  • BloodButchererHeld.HandleParticles (cognitive 24) Content/Items/Modifys/RBloodButcherer.cs:459 — BloodButchererHeld.HandleParticles has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TiroFinaleRenderer.DrawRibbonBand (cognitive 24) · ×1
  • TiroFinaleRenderer.DrawRibbonBand (cognitive 24) Content/Items/Ranged/TiroFinales/TiroFinaleRenderer.cs:267 — TiroFinaleRenderer.DrawRibbonBand has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SlimeGelOrb.OnTileCollide (cognitive 24) · ×1
  • SlimeGelOrb.OnTileCollide (cognitive 24) Content/LegendWeapon/HalibutLegend/FishSkills/FishSlime.cs:636 — SlimeGelOrb.OnTileCollide has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HalibutRenderer.DrawCursorPanel (cognitive 24) · ×1
  • HalibutRenderer.DrawCursorPanel (cognitive 24) Content/LegendWeapon/HalibutLegend/UI/HalibutRenderer.cs:549 — HalibutRenderer.DrawCursorPanel has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaDomainDeco.Draw (cognitive 24) · ×1
  • KikasaDomainDeco.Draw (cognitive 24) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainDeco.cs:560 — KikasaDomainDeco.Draw has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaDreamHound.UpdateFrame (cognitive 24) · ×1
  • KikasaDreamHound.UpdateFrame (cognitive 24) Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamHound.cs:814 — KikasaDreamHound.UpdateFrame has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaPlayerDrownFX.UpdateShow (cognitive 24) · ×1
  • KikasaPlayerDrownFX.UpdateShow (cognitive 24) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaPlayerDrownFX.cs:230 — KikasaPlayerDrownFX.UpdateShow has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaHalibutDomain.UpdatePressure (cognitive 24) · ×1
  • KikasaHalibutDomain.UpdatePressure (cognitive 24) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutDomain.cs:149 — KikasaHalibutDomain.UpdatePressure has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaDeerclopsServant.UpdateStomp (cognitive 24) · ×1
  • KikasaDeerclopsServant.UpdateStomp (cognitive 24) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:671 — KikasaDeerclopsServant.UpdateStomp has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaEaterServant.UpdateChain (cognitive 24) · ×1
  • KikasaEaterServant.UpdateChain (cognitive 24) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:924 — KikasaEaterServant.UpdateChain has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaPlanteraServant.SyncLatchesQuietly (cognitive 24) · ×1
  • KikasaPlanteraServant.SyncLatchesQuietly (cognitive 24) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:331 — KikasaPlanteraServant.SyncLatchesQuietly has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaPlanteraServant.UpdateDissolve (cognitive 24) · ×1
  • KikasaPlanteraServant.UpdateDissolve (cognitive 24) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1016 — KikasaPlanteraServant.UpdateDissolve has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaPrimeServant.DrawGlowLayer (cognitive 24) · ×1
  • KikasaPrimeServant.DrawGlowLayer (cognitive 24) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1536 — KikasaPrimeServant.DrawGlowLayer has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaTwinsFlameBreath.AI (cognitive 24) · ×1
  • KikasaTwinsFlameBreath.AI (cognitive 24) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsFlameBreath.cs:52 — KikasaTwinsFlameBreath.AI has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaWallOfFleshServant.DrawGlowAccents (cognitive 24) · ×1
  • KikasaWallOfFleshServant.DrawGlowAccents (cognitive 24) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:1092 — KikasaWallOfFleshServant.DrawGlowAccents has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaLakeFX.DrawGlowLayer (cognitive 24) · ×1
  • KikasaLakeFX.DrawGlowLayer (cognitive 24) Content/LegendWeapon/KikasaLegend/KikasaVaults/KikasaLakeFX.cs:546 — KikasaLakeFX.DrawGlowLayer has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LegendTooltipPanel.WrapBodyText (cognitive 24) · ×1
  • LegendTooltipPanel.WrapBodyText (cognitive 24) Content/LegendWeapon/LegendTooltipLayout.cs:168 — LegendTooltipPanel.WrapBodyText has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CrimsonSlashRenderer.DrawLayer (cognitive 24) · ×1
  • CrimsonSlashRenderer.DrawLayer (cognitive 24) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSlashRenderer.cs:361 — CrimsonSlashRenderer.DrawLayer has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniSeverStrike.UpdatePose (cognitive 24) · ×1
  • OniSeverStrike.UpdatePose (cognitive 24) Content/LegendWeapon/OnikiriLegend/OniDismembers/OniSeverStrike.cs:1259 — OniSeverStrike.UpdatePose has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniFlashStep.MarkSweep (cognitive 24) · ×1
  • OniFlashStep.MarkSweep (cognitive 24) Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashStep.cs:575 — OniFlashStep.MarkSweep has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniOmokageRender.CapturePending (cognitive 24) · ×1
  • OniOmokageRender.CapturePending (cognitive 24) Content/LegendWeapon/OnikiriLegend/OniOmokages/OniOmokageRender.cs:61 — OniOmokageRender.CapturePending has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniSlashRenderer.SubmitBand (cognitive 24) · ×1
  • OniSlashRenderer.SubmitBand (cognitive 24) Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlashRenderer.cs:441 — OniSlashRenderer.SubmitBand has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniHangingSwitch.Update (cognitive 24) · ×1
  • OniHangingSwitch.Update (cognitive 24) Content/LegendWeapon/OnikiriLegend/UI/OniHangingSwitch.cs:65 — OniHangingSwitch.Update has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniMeiRite.Update (cognitive 24) · ×1
  • OniMeiRite.Update (cognitive 24) Content/LegendWeapon/OnikiriLegend/UI/OniMeiRite.cs:107 — OniMeiRite.Update has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniMeiUI.ResolveTag (cognitive 24) · ×1
  • OniMeiUI.ResolveTag (cognitive 24) Content/LegendWeapon/OnikiriLegend/UI/OniMeiUI.cs:1008 — OniMeiUI.ResolveTag has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SHPCMultiCellMatrixProj.AI (cognitive 24) · ×1
  • SHPCMultiCellMatrixProj.AI (cognitive 24) Content/LegendWeapon/SHPCLegend/Modules/Frame/MultiCellFrameModule.cs:163 — SHPCMultiCellMatrixProj.AI has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HimayoMenuButtons.Tick (cognitive 24) · ×1
  • HimayoMenuButtons.Tick (cognitive 24) Content/MainMenus/Himayo/HimayoMenuButtons.cs:61 — HimayoMenuButtons.Tick has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ShenyoMenuButtons.Tick (cognitive 24) · ×1
  • ShenyoMenuButtons.Tick (cognitive 24) Content/MainMenus/Shenyo/ShenyoMenuButtons.cs:63 — ShenyoMenuButtons.Tick has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BssFinHuntState.UpdateBite (cognitive 24) · ×1
  • BssFinHuntState.UpdateBite (cognitive 24) Content/NPCs/BloomsandSerpents/States/BssFinHuntState.cs:205 — BssFinHuntState.UpdateBite has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FishronRingSpinState.OnUpdate (cognitive 24) · ×1
  • FishronRingSpinState.OnUpdate (cognitive 24) Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronRingSpinState.cs:40 — FishronRingSpinState.OnUpdate has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EowApexFrenzyState.UpdateDrumRoll (cognitive 24) · ×1
  • EowApexFrenzyState.UpdateDrumRoll (cognitive 24) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowApexFrenzyState.cs:217 — EowApexFrenzyState.UpdateDrumRoll has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EmpressLacewing.AI (cognitive 24) · ×1
  • EmpressLacewing.AI (cognitive 24) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Projectiles/EmpressLacewing.cs:70 — EmpressLacewing.AI has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GolemFistGrabState.OnUpdate (cognitive 24) · ×1
  • GolemFistGrabState.OnUpdate (cognitive 24) Content/NPCs/BrutalNPCs/BrutalGolem/States/Fists/GolemFistGrabState.cs:74 — GolemFistGrabState.OnUpdate has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KingSlimeTowerCollapseState.OnUpdate (cognitive 24) · ×1
  • KingSlimeTowerCollapseState.OnUpdate (cognitive 24) Content/NPCs/BrutalNPCs/BrutalKingSlime/States/KingSlimeTowerCollapseState.cs:48 — KingSlimeTowerCollapseState.OnUpdate has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CultistRingPrisonState.OnUpdate (cognitive 24) · ×1
  • CultistRingPrisonState.OnUpdate (cognitive 24) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistRingPrisonState.cs:25 — CultistRingPrisonState.OnUpdate has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · RetinazerDeathRay.AI (cognitive 24) · ×1
  • RetinazerDeathRay.AI (cognitive 24) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs:47 — RetinazerDeathRay.AI has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · RetinazerLaserSweepState.ExecuteChargePhase (cognitive 24) · ×1
  • RetinazerLaserSweepState.ExecuteChargePhase (cognitive 24) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerLaserSweepState.cs:105 — RetinazerLaserSweepState.ExecuteChargePhase has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MLordTidalPalmsState.OnUpdate (cognitive 24) · ×1
  • MLordTidalPalmsState.OnUpdate (cognitive 24) Content/NPCs/BrutalNPCs/BrutalMoonLord/States/MLordTidalPalmsState.cs:58 — MLordTidalPalmsState.OnUpdate has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PlanteraBloomNovaState.UpdateBloom (cognitive 24) · ×1
  • PlanteraBloomNovaState.UpdateBloom (cognitive 24) Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraBloomNovaState.cs:152 — PlanteraBloomNovaState.UpdateBloom has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ScrapCommander.AI (cognitive 24) · ×1
  • ScrapCommander.AI (cognitive 24) Content/NPCs/ScrapCommanders/ScrapCommander.cs:207 — ScrapCommander.AI has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ScrapViceSnatchState.OnUpdate (cognitive 24) · ×1
  • ScrapViceSnatchState.OnUpdate (cognitive 24) Content/NPCs/ScrapCommanders/States/ScrapViceSnatchState.cs:36 — ScrapViceSnatchState.OnUpdate has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ScrapWaterfallState.OnUpdate (cognitive 24) · ×1
  • ScrapWaterfallState.OnUpdate (cognitive 24) Content/NPCs/ScrapCommanders/States/ScrapWaterfallState.cs:35 — ScrapWaterfallState.OnUpdate has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SeaShrimpSparkBubble.OnBurst (cognitive 24) · ×1
  • SeaShrimpSparkBubble.OnBurst (cognitive 24) Content/NPCs/SeaShrimp/Projectiles/SeaShrimpSparkBubble.cs:163 — SeaShrimpSparkBubble.OnBurst has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · VictorClinicPanel.DrawList (cognitive 24) · ×1
  • VictorClinicPanel.DrawList (cognitive 24) Content/NPCs/Victors/UIs/VictorClinicPanel.cs:449 — VictorClinicPanel.DrawList has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DraedonQuestLogStyle.DrawProgressBar (cognitive 24) · ×1
  • DraedonQuestLogStyle.DrawProgressBar (cognitive 24) Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:534 — DraedonQuestLogStyle.DrawProgressBar has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HotwindQuestLogStyle.DrawProgressBar (cognitive 24) · ×1
  • HotwindQuestLogStyle.DrawProgressBar (cognitive 24) Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:456 — HotwindQuestLogStyle.DrawProgressBar has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GaolBossRoom.Place (cognitive 24) · ×1
  • GaolBossRoom.Place (cognitive 24) Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolBossRoom.cs:114 — GaolBossRoom.Place has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · AnnexPlanner.BuildWing (cognitive 24) · ×1
  • AnnexPlanner.BuildWing (cognitive 24) Content/Scenarios/Dungeonworld/Gen/Infill/AnnexPlanner.cs:107 — AnnexPlanner.BuildWing has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · L1CathedralPrefab.BuildBellTower (cognitive 24) · ×1
  • L1CathedralPrefab.BuildBellTower (cognitive 24) Content/Scenarios/Dungeonworld/Gen/Layers/L1/L1CathedralPrefab.cs:341 — L1CathedralPrefab.BuildBellTower has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · L2CellRow.FurnishCells (cognitive 24) · ×1
  • L2CellRow.FurnishCells (cognitive 24) Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2CellRow.cs:184 — L2CellRow.FurnishCells has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · L2EscapeTunnel.Plan (cognitive 24) · ×1
  • L2EscapeTunnel.Plan (cognitive 24) Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2EscapeTunnel.cs:111 — L2EscapeTunnel.Plan has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · L4Content.RouteDryLinks (cognitive 24) · ×1
  • L4Content.RouteDryLinks (cognitive 24) Content/Scenarios/Dungeonworld/Gen/Layers/L4/L4Content.cs:323 — L4Content.RouteDryLinks has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MacroRoutePass.ApplyPass (cognitive 24) · ×1
  • MacroRoutePass.ApplyPass (cognitive 24) Content/Scenarios/Dungeonworld/Gen/Passes/MacroRoutePass.cs:12 — MacroRoutePass.ApplyPass has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FoundryOverseer.UpdatePendulum (cognitive 24) · ×1
  • FoundryOverseer.UpdatePendulum (cognitive 24) Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:916 — FoundryOverseer.UpdatePendulum has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniRainWorldTransition.AdvanceEnvelopes (cognitive 24) · ×1
  • OniRainWorldTransition.AdvanceEnvelopes (cognitive 24) Content/Scenarios/Kiame/Overlay/OniRainWorldTransition.cs:133 — OniRainWorldTransition.AdvanceEnvelopes has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KiameLoadingScreen.DrawRain (cognitive 24) · ×1
  • KiameLoadingScreen.DrawRain (cognitive 24) Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:403 — KiameLoadingScreen.DrawRain has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KiyumeHoundDirector.TrySpawnAt (cognitive 24) · ×1
  • KiyumeHoundDirector.TrySpawnAt (cognitive 24) Content/Scenarios/Kiyume/NPCs/KiyumeHoundDirector.cs:235 — KiyumeHoundDirector.TrySpawnAt has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OldNetSky.Draw (cognitive 24) · ×1
  • OldNetSky.Draw (cognitive 24) Content/Scenarios/OldNet/Backgrounds/OldNetSky.cs:75 — OldNetSky.Draw has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OldNetWardenICE.DrawTelegraphs (cognitive 24) · ×1
  • OldNetWardenICE.DrawTelegraphs (cognitive 24) Content/Scenarios/OldNet/NPCs/OldNetWardenICE.cs:979 — OldNetWardenICE.DrawTelegraphs has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OldNetSentryMineTile.PreDraw (cognitive 24) · ×1
  • OldNetSentryMineTile.PreDraw (cognitive 24) Content/Scenarios/OldNet/Tiles/OldNetSentryMineTile.cs:97 — OldNetSentryMineTile.PreDraw has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CybCourseCardStyle.DrawPanelButton (cognitive 24) · ×1
  • CybCourseCardStyle.DrawPanelButton (cognitive 24) Content/Scenarios/Shepel/CybCourses/CybCourseCardStyle.cs:220 — CybCourseCardStyle.DrawPanelButton has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SHPCCradleGen.TryFindRelaxedPlacement (cognitive 24) · ×1
  • SHPCCradleGen.TryFindRelaxedPlacement (cognitive 24) Content/Structures/SHPCCradleGen.cs:169 — SHPCCradleGen.TryFindRelaxedPlacement has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LanternBoyProj.DrawLanternLayer (cognitive 24) · ×1
  • LanternBoyProj.DrawLanternLayer (cognitive 24) Content/Wraiths/Projectiles/LanternBoyProj.cs:458 — LanternBoyProj.DrawLanternLayer has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · AshreignPlayer.LocalStormTick (cognitive 23) · ×1
  • AshreignPlayer.LocalStormTick (cognitive 23) Content/GameModes/BrutalMobs/Ambience/Ashreign/AshreignPlayer.cs:78 — AshreignPlayer.LocalStormTick 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.
D2 · Cognitive Complexity · RimehollowRender.UpdateBySystem (cognitive 23) · ×1
  • RimehollowRender.UpdateBySystem (cognitive 23) Content/GameModes/BrutalMobs/Ambience/Rimehollow/RimehollowRender.cs:56 — RimehollowRender.UpdateBySystem 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.
D2 · Cognitive Complexity · SilkcryptPlayer.TryDropShadow (cognitive 23) · ×1
  • SilkcryptPlayer.TryDropShadow (cognitive 23) Content/GameModes/BrutalMobs/Ambience/Silkcrypt/SilkcryptPlayer.cs:254 — SilkcryptPlayer.TryDropShadow 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.
D2 · Cognitive Complexity · WoodsongBrambleProj.AI (cognitive 23) · ×1
  • WoodsongBrambleProj.AI (cognitive 23) Content/GameModes/BrutalMobs/Ambience/Woodsong/WoodsongBramble.cs:215 — WoodsongBrambleProj.AI 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.
D2 · Cognitive Complexity · EclipseNPC.TryStart (cognitive 23) · ×1
  • EclipseNPC.TryStart (cognitive 23) Content/GameModes/BrutalMobs/Eclipse/EclipseNPC.cs:230 — EclipseNPC.TryStart 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.
D2 · Cognitive Complexity · OceanSandMound.AI (cognitive 23) · ×1
  • OceanSandMound.AI (cognitive 23) Content/GameModes/BrutalMobs/Ocean/Projectiles/OceanSandMound.cs:79 — OceanSandMound.AI 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.
D2 · Cognitive Complexity · SandveilSurgeColumnProj.AI (cognitive 23) · ×1
  • SandveilSurgeColumnProj.AI (cognitive 23) Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilSurgeColumnProj.cs:93 — SandveilSurgeColumnProj.AI 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.
D2 · Cognitive Complexity · GsHuntressArmor.OnEndowHitNPC (cognitive 23) · ×1
  • GsHuntressArmor.OnEndowHitNPC (cognitive 23) Content/GameModes/GodSmith/Armors/Endgame/GsHuntressArmor.cs:45 — GsHuntressArmor.OnEndowHitNPC 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.
D2 · Cognitive Complexity · HackTimeNetSync.UpdatePlayerUploads (cognitive 23) · ×1
  • HackTimeNetSync.UpdatePlayerUploads (cognitive 23) Content/HackTimes/HackTimeNetSync.cs:787 — HackTimeNetSync.UpdatePlayerUploads 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.
D2 · Cognitive Complexity · DelayFuse.HasTriggerContact (cognitive 23) · ×1
  • DelayFuse.HasTriggerContact (cognitive 23) Content/HackTimes/Protocols/DelayFuse.cs:142 — DelayFuse.HasTriggerContact 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.
D2 · Cognitive Complexity · MachineShortCircuit.OnApply (cognitive 23) · ×1
  • MachineShortCircuit.OnApply (cognitive 23) Content/HackTimes/Protocols/MachineShortCircuit.cs:32 — MachineShortCircuit.OnApply 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.
D2 · Cognitive Complexity · BossPartScannable.BuildScanData (cognitive 23) · ×1
  • BossPartScannable.BuildScanData (cognitive 23) Content/HackTimes/Scannables/BossPartScannable.cs:26 — BossPartScannable.BuildScanData 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.
D2 · Cognitive Complexity · ProjectileScannable.GetOwnerName (cognitive 23) · ×1
  • ProjectileScannable.GetOwnerName (cognitive 23) Content/HackTimes/Scannables/ProjectileScannable.cs:146 — ProjectileScannable.GetOwnerName 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.
D2 · Cognitive Complexity · AutoFisherLootTable.RollFish (cognitive 23) · ×1
  • AutoFisherLootTable.RollFish (cognitive 23) Content/Industrials/ElectricPowers/AutoFishers/AutoFisherLootTable.cs:208 — AutoFisherLootTable.RollFish 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.
D2 · Cognitive Complexity · BaseMiningMachineTP.UpdateMachine (cognitive 23) · ×1
  • BaseMiningMachineTP.UpdateMachine (cognitive 23) Content/Industrials/ElectricPowers/MiningMachines/BaseMiningMachineTP.cs:272 — BaseMiningMachineTP.UpdateMachine 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.
D2 · Cognitive Complexity · ItemPipelineTP.SelectRoutedDirection (cognitive 23) · ×1
  • ItemPipelineTP.SelectRoutedDirection (cognitive 23) Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs:597 — ItemPipelineTP.SelectRoutedDirection 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.
D2 · Cognitive Complexity · ItemPipelineTP.LoadData (cognitive 23) · ×1
  • ItemPipelineTP.LoadData (cognitive 23) Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs:921 — ItemPipelineTP.LoadData 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.
D2 · Cognitive Complexity · BlackFlashSigilRender.DrawTimeSenseGhosts (cognitive 23) · ×1
  • BlackFlashSigilRender.DrawTimeSenseGhosts (cognitive 23) Content/Items/Accessories/BrutalRelics/MoonLord/BlackFlashSigilRender.cs:43 — BlackFlashSigilRender.DrawTimeSenseGhosts 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.
D2 · Cognitive Complexity · JusticeUnveiled.SpwanBool (cognitive 23) · ×1
  • JusticeUnveiled.SpwanBool (cognitive 23) Content/Items/Accessories/JusticeUnveileds/JusticeUnveiled.cs:34 — JusticeUnveiled.SpwanBool 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.
D2 · Cognitive Complexity · AncientStormArc.AI (cognitive 23) · ×1
  • AncientStormArc.AI (cognitive 23) Content/Items/Melee/StormGoddessSpears/AncientStormGoddessSpear.cs:358 — AncientStormArc.AI 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.
D2 · Cognitive Complexity · SparklingFishHolder.AI (cognitive 23) · ×1
  • SparklingFishHolder.AI (cognitive 23) Content/LegendWeapon/HalibutLegend/FishSkills/FishSparkling.cs:265 — SparklingFishHolder.AI 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.
D2 · Cognitive Complexity · FishVoodooThread.PreDraw (cognitive 23) · ×1
  • FishVoodooThread.PreDraw (cognitive 23) Content/LegendWeapon/HalibutLegend/FishSkills/FishVoodooRitual.cs:603 — FishVoodooThread.PreDraw 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.
D2 · Cognitive Complexity · KikasaDomainPlayer.UpdateFlipping (cognitive 23) · ×1
  • KikasaDomainPlayer.UpdateFlipping (cognitive 23) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainPlayer.cs:1154 — KikasaDomainPlayer.UpdateFlipping 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.
D2 · Cognitive Complexity · KikasaRainRender.EndEntityDraw (cognitive 23) · ×1
  • KikasaRainRender.EndEntityDraw (cognitive 23) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:30 — KikasaRainRender.EndEntityDraw 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.
D2 · Cognitive Complexity · KikasaArmsQuickSink.TryQuickSink (cognitive 23) · ×1
  • KikasaArmsQuickSink.TryQuickSink (cognitive 23) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaArmsQuickSink.cs:23 — KikasaArmsQuickSink.TryQuickSink 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.
D2 · Cognitive Complexity · KikasaBowServant.DrawGlow (cognitive 23) · ×1
  • KikasaBowServant.DrawGlow (cognitive 23) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1237 — KikasaBowServant.DrawGlow 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.
D2 · Cognitive Complexity · KikasaRodServant.PullCatch (cognitive 23) · ×1
  • KikasaRodServant.PullCatch (cognitive 23) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:453 — KikasaRodServant.PullCatch 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.
D2 · Cognitive Complexity · KikasaDeerclopsServant.UpdateDissolve (cognitive 23) · ×1
  • KikasaDeerclopsServant.UpdateDissolve (cognitive 23) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:877 — KikasaDeerclopsServant.UpdateDissolve 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.
D2 · Cognitive Complexity · KikasaGolemServant.UpdateShards (cognitive 23) · ×1
  • KikasaGolemServant.UpdateShards (cognitive 23) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1004 — KikasaGolemServant.UpdateShards 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.
D2 · Cognitive Complexity · KikasaGolemServant.DrawGlow (cognitive 23) · ×1
  • KikasaGolemServant.DrawGlow (cognitive 23) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1336 — KikasaGolemServant.DrawGlow 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.
D2 · Cognitive Complexity · KikasaMoonVesselWhip.PreDraw (cognitive 23) · ×1
  • KikasaMoonVesselWhip.PreDraw (cognitive 23) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonVesselWhip.cs:278 — KikasaMoonVesselWhip.PreDraw 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.
D2 · Cognitive Complexity · KikasaPrimeMortar.AI (cognitive 23) · ×1
  • KikasaPrimeMortar.AI (cognitive 23) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeMortar.cs:79 — KikasaPrimeMortar.AI 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.
D2 · Cognitive Complexity · KikasaQueenGelMine.UpdateCrystal (cognitive 23) · ×1
  • KikasaQueenGelMine.UpdateCrystal (cognitive 23) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenGelMine.cs:173 — KikasaQueenGelMine.UpdateCrystal 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.
D2 · Cognitive Complexity · KikasaWallOfFleshServant.UpdateDissolve (cognitive 23) · ×1
  • KikasaWallOfFleshServant.UpdateDissolve (cognitive 23) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:654 — KikasaWallOfFleshServant.UpdateDissolve 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.
D2 · Cognitive Complexity · OniFinaleLattice.DrawLines (cognitive 23) · ×1
  • OniFinaleLattice.DrawLines (cognitive 23) Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleLattice.cs:141 — OniFinaleLattice.DrawLines 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.
D2 · Cognitive Complexity · RibbonDefinition.Validate (cognitive 23) · ×1
  • RibbonDefinition.Validate (cognitive 23) Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/Geometry/RibbonMesh.cs:94 — RibbonDefinition.Validate 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.
D2 · Cognitive Complexity · SakuraFinaleFeedback.DrawSparks (cognitive 23) · ×1
  • SakuraFinaleFeedback.DrawSparks (cognitive 23) Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraFinaleFeedback.cs:100 — SakuraFinaleFeedback.DrawSparks 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.
D2 · Cognitive Complexity · SakuraParticleWorld.EmitBurst (cognitive 23) · ×1
  • SakuraParticleWorld.EmitBurst (cognitive 23) Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraParticleWorld.cs:57 — SakuraParticleWorld.EmitBurst 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.
D2 · Cognitive Complexity · CyberDomainFreeze.WriteSnapshot (cognitive 23) · ×1
  • CyberDomainFreeze.WriteSnapshot (cognitive 23) Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.Net.cs:829 — CyberDomainFreeze.WriteSnapshot 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.
D2 · Cognitive Complexity · CyberDomainFreeze.UpdateClientPresentation (cognitive 23) · ×1
  • CyberDomainFreeze.UpdateClientPresentation (cognitive 23) Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.cs:574 — CyberDomainFreeze.UpdateClientPresentation 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.
D2 · Cognitive Complexity · SHPCRenderer.DrawRAMBar_CPU (cognitive 23) · ×1
  • SHPCRenderer.DrawRAMBar_CPU (cognitive 23) Content/LegendWeapon/SHPCLegend/UI/SHPCRenderer.cs:613 — SHPCRenderer.DrawRAMBar_CPU 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.
D2 · Cognitive Complexity · SHPCUI.HandleModuleSelectClick (cognitive 23) · ×1
  • SHPCUI.HandleModuleSelectClick (cognitive 23) Content/LegendWeapon/SHPCLegend/UI/SHPCUI.cs:227 — SHPCUI.HandleModuleSelectClick 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.
D2 · Cognitive Complexity · BssHead.AI (cognitive 23) · ×1
  • BssHead.AI (cognitive 23) Content/NPCs/BloomsandSerpents/BssHead.cs:272 — BssHead.AI 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.
D2 · Cognitive Complexity · BrainFrenzyChaseState.OnUpdate (cognitive 23) · ×1
  • BrainFrenzyChaseState.OnUpdate (cognitive 23) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainFrenzyChaseState.cs:38 — BrainFrenzyChaseState.OnUpdate 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.
D2 · Cognitive Complexity · BrainMindSeizeState.UpdateComboPresentation (cognitive 23) · ×1
  • BrainMindSeizeState.UpdateComboPresentation (cognitive 23) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainMindSeizeState.cs:408 — BrainMindSeizeState.UpdateComboPresentation 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.
D2 · Cognitive Complexity · FishronPhaseThreeTransitionState.OnUpdate (cognitive 23) · ×1
  • FishronPhaseThreeTransitionState.OnUpdate (cognitive 23) Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronPhaseTransitionStates.cs:139 — FishronPhaseThreeTransitionState.OnUpdate 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.
D2 · Cognitive Complexity · EmpressFinaleState.Whiteout (cognitive 23) · ×1
  • EmpressFinaleState.Whiteout (cognitive 23) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/States/EmpressFinaleState.cs:231 — EmpressFinaleState.Whiteout 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.
D2 · Cognitive Complexity · EocIntroState.OnUpdate (cognitive 23) · ×1
  • EocIntroState.OnUpdate (cognitive 23) Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocIntroState.cs:34 — EocIntroState.OnUpdate 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.
D2 · Cognitive Complexity · EocVeilHoverState.OnUpdate (cognitive 23) · ×1
  • EocVeilHoverState.OnUpdate (cognitive 23) Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocVeilHoverState.cs:42 — EocVeilHoverState.OnUpdate 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.
D2 · Cognitive Complexity · GolemHookSwingState.OnUpdate (cognitive 23) · ×1
  • GolemHookSwingState.OnUpdate (cognitive 23) Content/NPCs/BrutalNPCs/BrutalGolem/States/GolemHookSwingState.cs:26 — GolemHookSwingState.OnUpdate 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.
D2 · Cognitive Complexity · GolemPunchComboState.OnUpdate (cognitive 23) · ×1
  • GolemPunchComboState.OnUpdate (cognitive 23) Content/NPCs/BrutalNPCs/BrutalGolem/States/GolemPunchComboState.cs:31 — GolemPunchComboState.OnUpdate 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.
D2 · Cognitive Complexity · SpazmatismFlameChaseState.OnUpdate (cognitive 23) · ×1
  • SpazmatismFlameChaseState.OnUpdate (cognitive 23) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismFlameChaseState.cs:80 — SpazmatismFlameChaseState.OnUpdate 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.
D2 · Cognitive Complexity · MLordLocomotion.ApplyHandMotion (cognitive 23) · ×1
  • MLordLocomotion.ApplyHandMotion (cognitive 23) Content/NPCs/BrutalNPCs/BrutalMoonLord/Core/MLordLocomotion.cs:661 — MLordLocomotion.ApplyHandMotion 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.
D2 · Cognitive Complexity · MoonLordFreeEyeAI.UpdateStarArray (cognitive 23) · ×1
  • MoonLordFreeEyeAI.UpdateStarArray (cognitive 23) Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordFreeEyeAI.cs:464 — MoonLordFreeEyeAI.UpdateStarArray 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.
D2 · Cognitive Complexity · MLordCrescentCloseState.OnUpdate (cognitive 23) · ×1
  • MLordCrescentCloseState.OnUpdate (cognitive 23) Content/NPCs/BrutalNPCs/BrutalMoonLord/States/MLordCrescentCloseState.cs:148 — MLordCrescentCloseState.OnUpdate 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.
D2 · Cognitive Complexity · PlanteraVineFeastState.UpdateChew (cognitive 23) · ×1
  • PlanteraVineFeastState.UpdateChew (cognitive 23) Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraVineFeastState.cs:388 — PlanteraVineFeastState.UpdateChew 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.
D2 · Cognitive Complexity · QBSwarmArrowState.OnUpdate (cognitive 23) · ×1
  • QBSwarmArrowState.OnUpdate (cognitive 23) Content/NPCs/BrutalNPCs/BrutalQueenBee/States/QBSwarmArrowState.cs:35 — QBSwarmArrowState.OnUpdate 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.
D2 · Cognitive Complexity · FssSkinFX.DrawChain (cognitive 23) · ×1
  • FssSkinFX.DrawChain (cognitive 23) Content/NPCs/FestersandSerpents/Rendering/FssSkinFX.cs:28 — FssSkinFX.DrawChain 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.
D2 · Cognitive Complexity · SeaShrimpHubState.PickAttack (cognitive 23) · ×1
  • SeaShrimpHubState.PickAttack (cognitive 23) Content/NPCs/SeaShrimp/States/SeaShrimpHubState.cs:86 — SeaShrimpHubState.PickAttack 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.
D2 · Cognitive Complexity · SHPCPanelState.Update (cognitive 23) · ×1
  • SHPCPanelState.Update (cognitive 23) Content/Narrative/Presentation/Skins/SHPC/SHPCPanelState.cs:39 — SHPCPanelState.Update 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.
D2 · Cognitive Complexity · QuestLog.UpdateChrome (cognitive 23) · ×1
  • QuestLog.UpdateChrome (cognitive 23) Content/QuestLogs/QuestLog.cs:561 — QuestLog.UpdateChrome 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.
D2 · Cognitive Complexity · ForestQuestLogStyle.DrawProgressBar (cognitive 23) · ×1
  • ForestQuestLogStyle.DrawProgressBar (cognitive 23) Content/QuestLogs/Styles/ForestQuestLogStyle.cs:447 — ForestQuestLogStyle.DrawProgressBar 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.
D2 · Cognitive Complexity · ProofingHallRoom.PaintSignatures (cognitive 23) · ×1
  • ProofingHallRoom.PaintSignatures (cognitive 23) Content/Scenarios/Dungeonworld/Gen/BossRooms/ProofingHallRoom.cs:275 — ProofingHallRoom.PaintSignatures 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.
D2 · Cognitive Complexity · L3MazeBlock.FurnishShelves (cognitive 23) · ×1
  • L3MazeBlock.FurnishShelves (cognitive 23) Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3MazeBlock.cs:282 — L3MazeBlock.FurnishShelves 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.
D2 · Cognitive Complexity · L4Palette.BandWalls (cognitive 23) · ×1
  • L4Palette.BandWalls (cognitive 23) Content/Scenarios/Dungeonworld/Gen/Layers/L4/L4Palette.cs:209 — L4Palette.BandWalls 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.
D2 · Cognitive Complexity · L5Content.RouteStrataConnectors (cognitive 23) · ×1
  • L5Content.RouteStrataConnectors (cognitive 23) Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Content.cs:365 — L5Content.RouteStrataConnectors 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.
D2 · Cognitive Complexity · L5Content.RouteSpineDrops (cognitive 23) · ×1
  • L5Content.RouteSpineDrops (cognitive 23) Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Content.cs:577 — L5Content.RouteSpineDrops 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.
D2 · Cognitive Complexity · AshfallStratum.PickSite (cognitive 23) · ×1
  • AshfallStratum.PickSite (cognitive 23) Content/Scenarios/Dungeonworld/Gen/Zones/AshfallStratum.cs:89 — AshfallStratum.PickSite 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.
D2 · Cognitive Complexity · DeepGaolWraith.UpdateEmergeFromSkull (cognitive 23) · ×1
  • DeepGaolWraith.UpdateEmergeFromSkull (cognitive 23) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:640 — DeepGaolWraith.UpdateEmergeFromSkull 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.
D2 · Cognitive Complexity · BoneStitcher.DrawThreadWeb (cognitive 23) · ×1
  • BoneStitcher.DrawThreadWeb (cognitive 23) Content/Scenarios/Dungeonworld/NPCs/Elites/BoneStitcher.cs:716 — BoneStitcher.DrawThreadWeb 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.
D2 · Cognitive Complexity · LanternWarden.UpdateChase (cognitive 23) · ×1
  • LanternWarden.UpdateChase (cognitive 23) Content/Scenarios/Dungeonworld/NPCs/Elites/LanternWarden.cs:288 — LanternWarden.UpdateChase 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.
D2 · Cognitive Complexity · FoundryOverseer.EvaluateGlobalTransitions (cognitive 23) · ×1
  • FoundryOverseer.EvaluateGlobalTransitions (cognitive 23) Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:276 — FoundryOverseer.EvaluateGlobalTransitions 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.
D2 · Cognitive Complexity · KiameSkeletonPass.CarvePools (cognitive 23) · ×1
  • KiameSkeletonPass.CarvePools (cognitive 23) Content/Scenarios/Kiame/Gen/Passes/KiameSkeletonPass.cs:135 — KiameSkeletonPass.CarvePools 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.
D2 · Cognitive Complexity · OniRainWorldTransition.SpawnStageFx (cognitive 23) · ×1
  • OniRainWorldTransition.SpawnStageFx (cognitive 23) Content/Scenarios/Kiame/Overlay/OniRainWorldTransition.cs:210 — OniRainWorldTransition.SpawnStageFx 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.
D2 · Cognitive Complexity · KiyumeCrowFlight.StartleFrom (cognitive 23) · ×1
  • KiyumeCrowFlight.StartleFrom (cognitive 23) Content/Scenarios/Kiyume/Ambience/KiyumeCrowFlight.cs:143 — KiyumeCrowFlight.StartleFrom 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.
D2 · Cognitive Complexity · OldNetTripwireTile.SpecialDraw (cognitive 23) · ×1
  • OldNetTripwireTile.SpecialDraw (cognitive 23) Content/Scenarios/OldNet/Tiles/OldNetTripwireTile.cs:89 — OldNetTripwireTile.SpecialDraw 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.
D2 · Cognitive Complexity · SylvanOutpost.SearchInRange (cognitive 23) · ×1
  • SylvanOutpost.SearchInRange (cognitive 23) Content/Structures/DatIO/SylvanOutpost.cs:77 — SylvanOutpost.SearchInRange 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.
D2 · Cognitive Complexity · CyberTooltipRenderer.DrawTooltip (cognitive 22) · ×1
  • CyberTooltipRenderer.DrawTooltip (cognitive 22) Content/Cyberwares/UIs/CyberTooltipRenderer.cs:20 — CyberTooltipRenderer.DrawTooltip has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · AetherglimPlayer.UpdateDeepPull (cognitive 22) · ×1
  • AetherglimPlayer.UpdateDeepPull (cognitive 22) Content/GameModes/BrutalMobs/Ambience/Aetherglim/AetherglimPlayer.cs:139 — AetherglimPlayer.UpdateDeepPull has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FleshfenBloodDew.PostUpdateEverything (cognitive 22) · ×1
  • FleshfenBloodDew.PostUpdateEverything (cognitive 22) Content/GameModes/BrutalMobs/Ambience/Fleshfen/FleshfenBloodDew.cs:44 — FleshfenBloodDew.PostUpdateEverything has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TidecallRipCurrentProj.PreDraw (cognitive 22) · ×1
  • TidecallRipCurrentProj.PreDraw (cognitive 22) Content/GameModes/BrutalMobs/Ambience/Tidecall/Projectiles/TidecallRipCurrentProj.cs:198 — TidecallRipCurrentProj.PreDraw has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · WoodsongAmbience.UpdateThreatWarning (cognitive 22) · ×1
  • WoodsongAmbience.UpdateThreatWarning (cognitive 22) Content/GameModes/BrutalMobs/Ambience/Woodsong/WoodsongAmbience.cs:548 — WoodsongAmbience.UpdateThreatWarning has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · WoodsongAmbience.TryFindRoost (cognitive 22) · ×1
  • WoodsongAmbience.TryFindRoost (cognitive 22) Content/GameModes/BrutalMobs/Ambience/Woodsong/WoodsongAmbience.cs:758 — WoodsongAmbience.TryFindRoost has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EclMothronNPC.SpawnSharedTick (cognitive 22) · ×1
  • EclMothronNPC.SpawnSharedTick (cognitive 22) Content/GameModes/BrutalMobs/Eclipse/EclMothronNPC.cs:374 — EclMothronNPC.SpawnSharedTick has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EclManFlyFlaskProj.AI (cognitive 22) · ×1
  • EclManFlyFlaskProj.AI (cognitive 22) Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclManFlyFlaskProj.cs:57 — EclManFlyFlaskProj.AI has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LegionNPC.ThiefStep (cognitive 22) · ×1
  • LegionNPC.ThiefStep (cognitive 22) Content/GameModes/BrutalMobs/Legion/LegionNPC.cs:815 — LegionNPC.ThiefStep has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LegionNPC.TryFindWaterSurface (cognitive 22) · ×1
  • LegionNPC.TryFindWaterSurface (cognitive 22) Content/GameModes/BrutalMobs/Legion/LegionNPC.cs:992 — LegionNPC.TryFindWaterSurface has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LegionPoseOmen.AI (cognitive 22) · ×1
  • LegionPoseOmen.AI (cognitive 22) Content/GameModes/BrutalMobs/Legion/Projectiles/LegionPoseOmen.cs:72 — LegionPoseOmen.AI has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MrtGuardShieldProj.AI (cognitive 22) · ×1
  • MrtGuardShieldProj.AI (cognitive 22) Content/GameModes/BrutalMobs/Martians/Projectiles/MrtGuardShieldProj.cs:70 — MrtGuardShieldProj.AI has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GsChantScheme.ResolveBeat (cognitive 22) · ×1
  • GsChantScheme.ResolveBeat (cognitive 22) Content/GameModes/GodSmith/Weapons/MagicChant/GsChantScheme.cs:92 — GsChantScheme.ResolveBeat has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LiquidPurge.OnApply (cognitive 22) · ×1
  • LiquidPurge.OnApply (cognitive 22) Content/HackTimes/Protocols/LiquidPurge.cs:23 — LiquidPurge.OnApply has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CollectorArm.State_Depositing (cognitive 22) · ×1
  • CollectorArm.State_Depositing (cognitive 22) Content/Industrials/ElectricPowers/Collectors/CollectorArm.cs:692 — CollectorArm.State_Depositing has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LumberjackSaw.FindNearestTree (cognitive 22) · ×1
  • LumberjackSaw.FindNearestTree (cognitive 22) Content/Industrials/ElectricPowers/Lumberjacks/LumberjackSaw.cs:105 — LumberjackSaw.FindNearestTree has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MiningSurvey.Scan (cognitive 22) · ×1
  • MiningSurvey.Scan (cognitive 22) Content/Industrials/ElectricPowers/MiningMachines/MiningMachineSystem.cs:174 — MiningSurvey.Scan has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SensorUI.DrawParamColumn (cognitive 22) · ×1
  • SensorUI.DrawParamColumn (cognitive 22) Content/Industrials/ElectricPowers/Sensors/SensorUI.cs:322 — SensorUI.DrawParamColumn has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ArcaneEternityGlobalProj.OnSpawn (cognitive 22) · ×1
  • ArcaneEternityGlobalProj.OnSpawn (cognitive 22) Content/Items/Accessories/ArcaneThroneOfEternity.cs:812 — ArcaneEternityGlobalProj.OnSpawn has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GluttonousRetinaRender.EndEntityDraw (cognitive 22) · ×1
  • GluttonousRetinaRender.EndEntityDraw (cognitive 22) Content/Items/Accessories/BrutalRelics/WallOfFlesh/GluttonousRetinaRender.cs:42 — GluttonousRetinaRender.EndEntityDraw has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · AccretionDisk.ThrownBehavior (cognitive 22) · ×1
  • AccretionDisk.ThrownBehavior (cognitive 22) Content/Items/Magic/AriaofTheCosmoses/AccretionDisk.cs:201 — AccretionDisk.ThrownBehavior has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EverdeepRing.AI (cognitive 22) · ×1
  • EverdeepRing.AI (cognitive 22) Content/Items/Magic/Everdeeps/EverdeepRing.cs:88 — EverdeepRing.AI has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PandemoniumChannel.AI (cognitive 22) · ×1
  • PandemoniumChannel.AI (cognitive 22) Content/Items/Magic/Pandemoniums/PandemoniumChannel.cs:123 — PandemoniumChannel.AI has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DestroyerEXPlayer.PostUpdateMiscEffects (cognitive 22) · ×1
  • DestroyerEXPlayer.PostUpdateMiscEffects (cognitive 22) Content/Items/Melee/DestroyersBladeEXs/DestroyerEXPlayer.cs:84 — DestroyerEXPlayer.PostUpdateMiscEffects has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DestroyerHeadMissile.AI (cognitive 22) · ×1
  • DestroyerHeadMissile.AI (cognitive 22) Content/Items/Melee/DestroyersBladeEXs/DestroyerHeadMissile.cs:46 — DestroyerHeadMissile.AI has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniHandMinion.AI (cognitive 22) · ×1
  • OniHandMinion.AI (cognitive 22) Content/Items/Melee/OniMacheteHands.cs:210 — OniHandMinion.AI has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DynamiteExplosionEffect.SpawnTimedSmoke (cognitive 22) · ×1
  • DynamiteExplosionEffect.SpawnTimedSmoke (cognitive 22) Content/LegendWeapon/HalibutLegend/FishSkills/FishDynamite.cs:553 — DynamiteExplosionEffect.SpawnTimedSmoke has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · RockHammerFish.PreDraw (cognitive 22) · ×1
  • RockHammerFish.PreDraw (cognitive 22) Content/LegendWeapon/HalibutLegend/FishSkills/FishRock.cs:683 — RockHammerFish.PreDraw has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TropicalBarracudaProjectile.AI (cognitive 22) · ×1
  • TropicalBarracudaProjectile.AI (cognitive 22) Content/LegendWeapon/HalibutLegend/FishSkills/FishTropicalBarracuda.cs:203 — TropicalBarracudaProjectile.AI has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · UnicornFishDashProj.ActionUpdate (cognitive 22) · ×1
  • UnicornFishDashProj.ActionUpdate (cognitive 22) Content/LegendWeapon/HalibutLegend/FishSkills/FishUnicorn.cs:164 — UnicornFishDashProj.ActionUpdate has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaDiveClearing.Update (cognitive 22) · ×1
  • KikasaDiveClearing.Update (cognitive 22) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDiveClearing.cs:100 — KikasaDiveClearing.Update has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaLakeHighlight.CaptureMask (cognitive 22) · ×1
  • KikasaLakeHighlight.CaptureMask (cognitive 22) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaLakeHighlight.cs:183 — KikasaLakeHighlight.CaptureMask has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaDrownFX.DrawGhostLayer (cognitive 22) · ×1
  • KikasaDrownFX.DrawGhostLayer (cognitive 22) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1076 — KikasaDrownFX.DrawGhostLayer has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaDrownNet.Receive (cognitive 22) · ×1
  • KikasaDrownNet.Receive (cognitive 22) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownNet.cs:105 — KikasaDrownNet.Receive has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaInkDrop.UpdatePlunge (cognitive 22) · ×1
  • KikasaInkDrop.UpdatePlunge (cognitive 22) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:445 — KikasaInkDrop.UpdatePlunge has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaRainRender.DrawInkBodies (cognitive 22) · ×1
  • KikasaRainRender.DrawInkBodies (cognitive 22) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:177 — KikasaRainRender.DrawInkBodies has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaRainUmbrella.FireDrop (cognitive 22) · ×1
  • KikasaRainUmbrella.FireDrop (cognitive 22) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:1366 — KikasaRainUmbrella.FireDrop has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaFlailHead.AI (cognitive 22) · ×1
  • KikasaFlailHead.AI (cognitive 22) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailHead.cs:73 — KikasaFlailHead.AI has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaHalibutServant.UpdateEmerge (cognitive 22) · ×1
  • KikasaHalibutServant.UpdateEmerge (cognitive 22) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:338 — KikasaHalibutServant.UpdateEmerge has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaOnikiriServant.FillGrandTargets (cognitive 22) · ×1
  • KikasaOnikiriServant.FillGrandTargets (cognitive 22) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:556 — KikasaOnikiriServant.FillGrandTargets has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaPandemoniumServant.UpdateBook (cognitive 22) · ×1
  • KikasaPandemoniumServant.UpdateBook (cognitive 22) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:724 — KikasaPandemoniumServant.UpdateBook has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaSHPCServant.UpdateEmerge (cognitive 22) · ×1
  • KikasaSHPCServant.UpdateEmerge (cognitive 22) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:305 — KikasaSHPCServant.UpdateEmerge has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaBloomSerpentServant.UpdateSegmentCrossings (cognitive 22) · ×1
  • KikasaBloomSerpentServant.UpdateSegmentCrossings (cognitive 22) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:788 — KikasaBloomSerpentServant.UpdateSegmentCrossings has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaCultistServant.UpdateElementCast (cognitive 22) · ×1
  • KikasaCultistServant.UpdateElementCast (cognitive 22) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:637 — KikasaCultistServant.UpdateElementCast has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaDestroyerServant.UpdateSegmentCrossings (cognitive 22) · ×1
  • KikasaDestroyerServant.UpdateSegmentCrossings (cognitive 22) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:869 — KikasaDestroyerServant.UpdateSegmentCrossings has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaEaterServant.UpdateSegmentCrossings (cognitive 22) · ×1
  • KikasaEaterServant.UpdateSegmentCrossings (cognitive 22) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1044 — KikasaEaterServant.UpdateSegmentCrossings has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaEmpressServant.UpdateLanceRain (cognitive 22) · ×1
  • KikasaEmpressServant.UpdateLanceRain (cognitive 22) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:545 — KikasaEmpressServant.UpdateLanceRain has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaFesterSerpentServant.UpdateSegmentCrossings (cognitive 22) · ×1
  • KikasaFesterSerpentServant.UpdateSegmentCrossings (cognitive 22) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:784 — KikasaFesterSerpentServant.UpdateSegmentCrossings has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaPlanteraServant.AI (cognitive 22) · ×1
  • KikasaPlanteraServant.AI (cognitive 22) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:233 — KikasaPlanteraServant.AI has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaQueenBeeStinger.AI (cognitive 22) · ×1
  • KikasaQueenBeeStinger.AI (cognitive 22) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeStinger.cs:88 — KikasaQueenBeeStinger.AI has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaQueenSlimeServant.DrawCoreAndAccents (cognitive 22) · ×1
  • KikasaQueenSlimeServant.DrawCoreAndAccents (cognitive 22) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:1504 — KikasaQueenSlimeServant.DrawCoreAndAccents has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FuLao.OnPuddleUpdate (cognitive 22) · ×1
  • FuLao.OnPuddleUpdate (cognitive 22) Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuLao.cs:59 — FuLao.OnPuddleUpdate has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaThrallProj.UpdateReform (cognitive 22) · ×1
  • KikasaThrallProj.UpdateReform (cognitive 22) Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallProj.cs:401 — KikasaThrallProj.UpdateReform has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaPanoramaUI.DrawSeats (cognitive 22) · ×1
  • KikasaPanoramaUI.DrawSeats (cognitive 22) Content/LegendWeapon/KikasaLegend/UI/Panorama/KikasaPanoramaUI.cs:1679 — KikasaPanoramaUI.DrawSeats has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LegendData.LoadData (cognitive 22) · ×1
  • LegendData.LoadData (cognitive 22) Content/LegendWeapon/LegendData.cs:182 — LegendData.LoadData has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniSeverStrike.ValidateRequest (cognitive 22) · ×1
  • OniSeverStrike.ValidateRequest (cognitive 22) Content/LegendWeapon/OnikiriLegend/OniDismembers/OniSeverStrike.cs:572 — OniSeverStrike.ValidateRequest has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniDomainDeco.UpdateLanterns (cognitive 22) · ×1
  • OniDomainDeco.UpdateLanterns (cognitive 22) Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainDeco.cs:328 — OniDomainDeco.UpdateLanterns has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniOmokageRender.DrawThreadsAndPulses (cognitive 22) · ×1
  • OniOmokageRender.DrawThreadsAndPulses (cognitive 22) Content/LegendWeapon/OnikiriLegend/OniOmokages/OniOmokageRender.cs:580 — OniOmokageRender.DrawThreadsAndPulses has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SakuraReadyStanceWeaponVisual.CreateGlowMask (cognitive 22) · ×1
  • SakuraReadyStanceWeaponVisual.CreateGlowMask (cognitive 22) Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraReadyStanceWeaponVisual.cs:55 — SakuraReadyStanceWeaponVisual.CreateGlowMask has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniMeiGlyph.DrawStroke (cognitive 22) · ×1
  • OniMeiGlyph.DrawStroke (cognitive 22) Content/LegendWeapon/OnikiriLegend/UI/OniMeiGlyph.cs:484 — OniMeiGlyph.DrawStroke has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniSigilUI.ResolveFooterLine (cognitive 22) · ×1
  • OniSigilUI.ResolveFooterLine (cognitive 22) Content/LegendWeapon/OnikiriLegend/UI/OniSigilUI.cs:968 — OniSigilUI.ResolveFooterLine has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SHPCSniperLockLineProj.AI (cognitive 22) · ×1
  • SHPCSniperLockLineProj.AI (cognitive 22) Content/LegendWeapon/SHPCLegend/Modules/Optic/SniperOpticModule.cs:281 — SHPCSniperLockLineProj.AI has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SHPCCapacitorBankProj.AI_Venting (cognitive 22) · ×1
  • SHPCCapacitorBankProj.AI_Venting (cognitive 22) Content/LegendWeapon/SHPCLegend/Modules/Power/CapacitorBankModule.cs:476 — SHPCCapacitorBankProj.AI_Venting has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MoldCodexPanel.DrawCell (cognitive 22) · ×1
  • MoldCodexPanel.DrawCell (cognitive 22) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:217 — MoldCodexPanel.DrawCell has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MoldProcessingPanel.DrawReforgePreview (cognitive 22) · ×1
  • MoldProcessingPanel.DrawReforgePreview (cognitive 22) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingPanel.cs:375 — MoldProcessingPanel.DrawReforgePreview has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SHPCCyberPanel.HitTest (cognitive 22) · ×1
  • SHPCCyberPanel.HitTest (cognitive 22) Content/LegendWeapon/SHPCLegend/UI/SHPCCyberPanel.cs:214 — SHPCCyberPanel.HitTest has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SHPCModuleSelectPanel.Draw (cognitive 22) · ×1
  • SHPCModuleSelectPanel.Draw (cognitive 22) Content/LegendWeapon/SHPCLegend/UI/SHPCModuleSelectPanel.cs:145 — SHPCModuleSelectPanel.Draw has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BrainBloodPulseState.OnUpdate (cognitive 22) · ×1
  • BrainBloodPulseState.OnUpdate (cognitive 22) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainBloodPulseState.cs:44 — BrainBloodPulseState.OnUpdate has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DeerclopsAI.FindFrame (cognitive 22) · ×1
  • DeerclopsAI.FindFrame (cognitive 22) Content/NPCs/BrutalNPCs/BrutalDeerclops/DeerclopsAI.cs:337 — DeerclopsAI.FindFrame has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DeerRubbleProj.AI (cognitive 22) · ×1
  • DeerRubbleProj.AI (cognitive 22) Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerRubbleProj.cs:45 — DeerRubbleProj.AI has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DeerclopsPhaseRoarState.OnUpdate (cognitive 22) · ×1
  • DeerclopsPhaseRoarState.OnUpdate (cognitive 22) Content/NPCs/BrutalNPCs/BrutalDeerclops/States/DeerclopsPhaseRoarState.cs:29 — DeerclopsPhaseRoarState.OnUpdate has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DestroyerCoilCrushState.UpdatePierce (cognitive 22) · ×1
  • DestroyerCoilCrushState.UpdatePierce (cognitive 22) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerCoilCrushState.cs:330 — DestroyerCoilCrushState.UpdatePierce has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DestroyerLoopLashState.OnUpdate (cognitive 22) · ×1
  • DestroyerLoopLashState.OnUpdate (cognitive 22) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerLoopLashState.cs:47 — DestroyerLoopLashState.OnUpdate has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DukeFishronAI.Draw (cognitive 22) · ×1
  • DukeFishronAI.Draw (cognitive 22) Content/NPCs/BrutalNPCs/BrutalDukeFishron/DukeFishronAI.cs:377 — DukeFishronAI.Draw has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EmpressDashGrabState.OnUpdate (cognitive 22) · ×1
  • EmpressDashGrabState.OnUpdate (cognitive 22) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/States/EmpressDashGrabState.cs:51 — EmpressDashGrabState.OnUpdate has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TwinsTetherArc.AI (cognitive 22) · ×1
  • TwinsTetherArc.AI (cognitive 22) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/TwinsTetherArc.cs:50 — TwinsTetherArc.AI has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SpazmatismFlameStormState.ExecuteWarningPhase (cognitive 22) · ×1
  • SpazmatismFlameStormState.ExecuteWarningPhase (cognitive 22) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismFlameStormState.cs:105 — SpazmatismFlameStormState.ExecuteWarningPhase has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PrimeArcChainProj.AI (cognitive 22) · ×1
  • PrimeArcChainProj.AI (cognitive 22) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeArcChainProj.cs:58 — PrimeArcChainProj.AI has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · WofRetinaScanBeam.AI (cognitive 22) · ×1
  • WofRetinaScanBeam.AI (cognitive 22) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofRetinaScanBeam.cs:104 — WofRetinaScanBeam.AI has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FssLegRig.UpdateWalk (cognitive 22) · ×1
  • FssLegRig.UpdateWalk (cognitive 22) Content/NPCs/FestersandSerpents/FssLegRig.cs:232 — FssLegRig.UpdateWalk has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FssIchorPool.AI (cognitive 22) · ×1
  • FssIchorPool.AI (cognitive 22) Content/NPCs/FestersandSerpents/Projectiles/FssIchorPool.cs:110 — FssIchorPool.AI has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ScrapGroundSaw.AI (cognitive 22) · ×1
  • ScrapGroundSaw.AI (cognitive 22) Content/NPCs/ScrapCommanders/Projectiles/ScrapGroundSaw.cs:39 — ScrapGroundSaw.AI has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ScrapMagnetStormState.OnUpdate (cognitive 22) · ×1
  • ScrapMagnetStormState.OnUpdate (cognitive 22) Content/NPCs/ScrapCommanders/States/ScrapMagnetStormState.cs:41 — ScrapMagnetStormState.OnUpdate has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SeaShrimpBoss.RegisterSharedLoot (cognitive 22) · ×1
  • SeaShrimpBoss.RegisterSharedLoot (cognitive 22) Content/NPCs/SeaShrimp/SeaShrimpBoss.cs:104 — SeaShrimpBoss.RegisterSharedLoot has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SeaShrimpVortexTossState.OnUpdate (cognitive 22) · ×1
  • SeaShrimpVortexTossState.OnUpdate (cognitive 22) Content/NPCs/SeaShrimp/States/SeaShrimpVortexTossState.cs:27 — SeaShrimpVortexTossState.OnUpdate has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FloodGalleryWatcher.ApplyWater (cognitive 22) · ×1
  • FloodGalleryWatcher.ApplyWater (cognitive 22) Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryWatcher.cs:255 — FloodGalleryWatcher.ApplyWater has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GuideTrailPass.PaintProofTrail (cognitive 22) · ×1
  • GuideTrailPass.PaintProofTrail (cognitive 22) Content/Scenarios/Dungeonworld/Gen/Passes/GuideTrailPass.cs:182 — GuideTrailPass.PaintProofTrail has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BoneStitcher.DrawBones (cognitive 22) · ×1
  • BoneStitcher.DrawBones (cognitive 22) Content/Scenarios/Dungeonworld/NPCs/Elites/BoneStitcher.cs:662 — BoneStitcher.DrawBones has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Undrowned.UpdateDragLunge (cognitive 22) · ×1
  • Undrowned.UpdateDragLunge (cognitive 22) Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:1074 — Undrowned.UpdateDragLunge has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HadalTilePass.ApplyPass (cognitive 22) · ×1
  • HadalTilePass.ApplyPass (cognitive 22) Content/Scenarios/Hadalworld/Gen/Passes/HadalTilePass.cs:16 — HadalTilePass.ApplyPass has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ToriiShrineActor.UpdateDeparture (cognitive 22) · ×1
  • ToriiShrineActor.UpdateDeparture (cognitive 22) Content/Scenarios/Himayo/ToriiShrines/ToriiShrineActor.cs:289 — ToriiShrineActor.UpdateDeparture has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OldNetSkyEvents.UpdateTide (cognitive 22) · ×1
  • OldNetSkyEvents.UpdateTide (cognitive 22) Content/Scenarios/OldNet/Backgrounds/OldNetSkyEvents.cs:158 — OldNetSkyEvents.UpdateTide has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OldNetSkeletonPass.ApplyPass (cognitive 22) · ×1
  • OldNetSkeletonPass.ApplyPass (cognitive 22) Content/Scenarios/OldNet/Gen/Passes/OldNetSkeletonPass.cs:15 — OldNetSkeletonPass.ApplyPass has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BloodAltarRite.OnPhaseEnter (cognitive 22) · ×1
  • BloodAltarRite.OnPhaseEnter (cognitive 22) Content/Tiles/BloodAltars/BloodAltarRite.cs:221 — BloodAltarRite.OnPhaseEnter has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LanternSeizurePerformance.Update (cognitive 22) · ×1
  • LanternSeizurePerformance.Update (cognitive 22) Content/Wraiths/Deaths/Performances/LanternSeizurePerformance.cs:79 — LanternSeizurePerformance.Update has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CWRCrafted.AddResultContent (cognitive 21) · ×1
  • CWRCrafted.AddResultContent (cognitive 21) Content/CWRCrafted.cs:41 — CWRCrafted.AddResultContent 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.
D2 · Cognitive Complexity · CyberwareNet.ExecuteSurgery (cognitive 21) · ×1
  • CyberwareNet.ExecuteSurgery (cognitive 21) Content/Cyberwares/CyberwareNet.cs:531 — CyberwareNet.ExecuteSurgery 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.
D2 · Cognitive Complexity · SandevistanPlayer.ApplySnapshot (cognitive 21) · ×1
  • SandevistanPlayer.ApplySnapshot (cognitive 21) Content/Cyberwares/Implementation/Sandevistans/SandevistanPlayer.cs:234 — SandevistanPlayer.ApplySnapshot 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.
D2 · Cognitive Complexity · CyberwareGuideLead.DrawOverlay (cognitive 21) · ×1
  • CyberwareGuideLead.DrawOverlay (cognitive 21) Content/Cyberwares/Tutorial/CyberwareGuideLead.cs:274 — CyberwareGuideLead.DrawOverlay 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.
D2 · Cognitive Complexity · AstralveilSpearDirector.PickTarget (cognitive 21) · ×1
  • AstralveilSpearDirector.PickTarget (cognitive 21) Content/GameModes/BrutalMobs/Ambience/Astralveil/AstralveilSpearDirector.cs:111 — AstralveilSpearDirector.PickTarget 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.
D2 · Cognitive Complexity · AstralveilSpearMarkProj.PreDraw (cognitive 21) · ×1
  • AstralveilSpearMarkProj.PreDraw (cognitive 21) Content/GameModes/BrutalMobs/Ambience/Astralveil/Projectiles/AstralveilSpearMarkProj.cs:176 — AstralveilSpearMarkProj.PreDraw 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.
D2 · Cognitive Complexity · BrinefumeBoilZoneProj.AI (cognitive 21) · ×1
  • BrinefumeBoilZoneProj.AI (cognitive 21) Content/GameModes/BrutalMobs/Ambience/Brinefume/Projectiles/BrinefumeBoilZoneProj.cs:64 — BrinefumeBoilZoneProj.AI 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.
D2 · Cognitive Complexity · BrinefumeHazeTideProj.AI (cognitive 21) · ×1
  • BrinefumeHazeTideProj.AI (cognitive 21) Content/GameModes/BrutalMobs/Ambience/Brinefume/Projectiles/BrinefumeHazeTideProj.cs:59 — BrinefumeHazeTideProj.AI 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.
D2 · Cognitive Complexity · CindercragGlowRender.EndEntityDraw (cognitive 21) · ×1
  • CindercragGlowRender.EndEntityDraw (cognitive 21) Content/GameModes/BrutalMobs/Ambience/Cindercrag/CindercragGlowRender.cs:267 — CindercragGlowRender.EndEntityDraw 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.
D2 · Cognitive Complexity · DuneStormRender.UpdateStreaks (cognitive 21) · ×1
  • DuneStormRender.UpdateStreaks (cognitive 21) Content/GameModes/BrutalMobs/Ambience/DuneStorm/DuneStormRender.cs:71 — DuneStormRender.UpdateStreaks 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.
D2 · Cognitive Complexity · DuneStormScheduler.TryLashRound (cognitive 21) · ×1
  • DuneStormScheduler.TryLashRound (cognitive 21) Content/GameModes/BrutalMobs/Ambience/DuneStorm/DuneStormScheduler.cs:93 — DuneStormScheduler.TryLashRound 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.
D2 · Cognitive Complexity · DuneStormSandLashOmen.AI (cognitive 21) · ×1
  • DuneStormSandLashOmen.AI (cognitive 21) Content/GameModes/BrutalMobs/Ambience/DuneStorm/Projectiles/DuneStormSandLashOmen.cs:52 — DuneStormSandLashOmen.AI 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.
D2 · Cognitive Complexity · FrostveilAuroraSky.Draw (cognitive 21) · ×1
  • FrostveilAuroraSky.Draw (cognitive 21) Content/GameModes/BrutalMobs/Ambience/Frostveil/FrostveilAuroraSky.cs:66 — FrostveilAuroraSky.Draw 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.
D2 · Cognitive Complexity · HollowdeepRockfallProj.AI (cognitive 21) · ×1
  • HollowdeepRockfallProj.AI (cognitive 21) Content/GameModes/BrutalMobs/Ambience/Hollowdeep/Projectiles/HollowdeepRockfallProj.cs:51 — HollowdeepRockfallProj.AI 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.
D2 · Cognitive Complexity · MournfogGrudgeRingProj.AI (cognitive 21) · ×1
  • MournfogGrudgeRingProj.AI (cognitive 21) Content/GameModes/BrutalMobs/Ambience/Mournfog/Projectiles/MournfogGrudgeRingProj.cs:95 — MournfogGrudgeRingProj.AI 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.
D2 · Cognitive Complexity · PrismgladeAmbience.BuildCandidates (cognitive 21) · ×1
  • PrismgladeAmbience.BuildCandidates (cognitive 21) Content/GameModes/BrutalMobs/Ambience/Prismglade/PrismgladeAmbience.cs:158 — PrismgladeAmbience.BuildCandidates 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.
D2 · Cognitive Complexity · RotmireVentProj.AI (cognitive 21) · ×1
  • RotmireVentProj.AI (cognitive 21) Content/GameModes/BrutalMobs/Ambience/Rotmire/Projectiles/RotmireVentProj.cs:87 — RotmireVentProj.AI 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.
D2 · Cognitive Complexity · SilkcryptWebPatchProj.AI (cognitive 21) · ×1
  • SilkcryptWebPatchProj.AI (cognitive 21) Content/GameModes/BrutalMobs/Ambience/Silkcrypt/Projectiles/SilkcryptWebPatchProj.cs:62 — SilkcryptWebPatchProj.AI 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.
D2 · Cognitive Complexity · SunkendunePlayer.TrySpawnSandfall (cognitive 21) · ×1
  • SunkendunePlayer.TrySpawnSandfall (cognitive 21) Content/GameModes/BrutalMobs/Ambience/Sunkendune/SunkendunePlayer.cs:147 — SunkendunePlayer.TrySpawnSandfall 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.
D2 · Cognitive Complexity · WoodsongAmbience.FindWispTarget (cognitive 21) · ×1
  • WoodsongAmbience.FindWispTarget (cognitive 21) Content/GameModes/BrutalMobs/Ambience/Woodsong/WoodsongAmbience.cs:645 — WoodsongAmbience.FindWispTarget 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.
D2 · Cognitive Complexity · DdCastOmen.AI (cognitive 21) · ×1
  • DdCastOmen.AI (cognitive 21) Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdCastOmen.cs:124 — DdCastOmen.AI 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.
D2 · Cognitive Complexity · DdFirePillarProj.AI (cognitive 21) · ×1
  • DdFirePillarProj.AI (cognitive 21) Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdFirePillarProj.cs:83 — DdFirePillarProj.AI 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.
D2 · Cognitive Complexity · EclMothronDiveOmen.AI (cognitive 21) · ×1
  • EclMothronDiveOmen.AI (cognitive 21) Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclMothronDiveOmen.cs:62 — EclMothronDiveOmen.AI 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.
D2 · Cognitive Complexity · GyRavenSwoopOmen.AI (cognitive 21) · ×1
  • GyRavenSwoopOmen.AI (cognitive 21) Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyRavenSwoopOmen.cs:77 — GyRavenSwoopOmen.AI 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.
D2 · Cognitive Complexity · LegionNPC.OfficerStep (cognitive 21) · ×1
  • LegionNPC.OfficerStep (cognitive 21) Content/GameModes/BrutalMobs/Legion/LegionNPC.cs:357 — LegionNPC.OfficerStep 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.
D2 · Cognitive Complexity · MushroomBrutalNPC.TickFish (cognitive 21) · ×1
  • MushroomBrutalNPC.TickFish (cognitive 21) Content/GameModes/BrutalMobs/Mushroom/MushroomBrutalNPC.cs:570 — MushroomBrutalNPC.TickFish 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.
D2 · Cognitive Complexity · NightPackNPC.TryStart (cognitive 21) · ×1
  • NightPackNPC.TryStart (cognitive 21) Content/GameModes/BrutalMobs/NightPack/NightPackNPC.cs:166 — NightPackNPC.TryStart 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.
D2 · Cognitive Complexity · OceanSharkOmen.AI (cognitive 21) · ×1
  • OceanSharkOmen.AI (cognitive 21) Content/GameModes/BrutalMobs/Ocean/Projectiles/OceanSharkOmen.cs:82 — OceanSharkOmen.AI 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.
D2 · Cognitive Complexity · PmkChargeOmen.AI (cognitive 21) · ×1
  • PmkChargeOmen.AI (cognitive 21) Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkChargeOmen.cs:93 — PmkChargeOmen.AI 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.
D2 · Cognitive Complexity · StonebornCounterRing.AI (cognitive 21) · ×1
  • StonebornCounterRing.AI (cognitive 21) Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornCounterRing.cs:78 — StonebornCounterRing.AI 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.
D2 · Cognitive Complexity · StonebornJavelinOmen.AI (cognitive 21) · ×1
  • StonebornJavelinOmen.AI (cognitive 21) Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornJavelinOmen.cs:82 — StonebornJavelinOmen.AI 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.
D2 · Cognitive Complexity · WastesSandGeyserProj.AI (cognitive 21) · ×1
  • WastesSandGeyserProj.AI (cognitive 21) Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandGeyserProj.cs:83 — WastesSandGeyserProj.AI 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.
D2 · Cognitive Complexity · GsRedRyderPelletProj.OnHitNPC (cognitive 21) · ×1
  • GsRedRyderPelletProj.OnHitNPC (cognitive 21) Content/GameModes/GodSmith/Weapons/Guns/GsRedRyder.cs:184 — GsRedRyderPelletProj.OnHitNPC 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.
D2 · Cognitive Complexity · GsDrainTetherProj.OwnerExtraTick (cognitive 21) · ×1
  • GsDrainTetherProj.OwnerExtraTick (cognitive 21) Content/GameModes/GodSmith/Weapons/MagicConduit/Projectiles/GsDrainTetherProj.cs:54 — GsDrainTetherProj.OwnerExtraTick 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.
D2 · Cognitive Complexity · GsThunderSpearHeld.OnHitTarget (cognitive 21) · ×1
  • GsThunderSpearHeld.OnHitTarget (cognitive 21) Content/GameModes/GodSmith/Weapons/Spears/GsThunderSpear.cs:67 — GsThunderSpearHeld.OnHitTarget 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.
D2 · Cognitive Complexity · GsWhipMorningStarFallProj.AI (cognitive 21) · ×1
  • GsWhipMorningStarFallProj.AI (cognitive 21) Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipMorningStarProj.cs:59 — GsWhipMorningStarFallProj.AI 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.
D2 · Cognitive Complexity · GameModeTabUI.Draw (cognitive 21) · ×1
  • GameModeTabUI.Draw (cognitive 21) Content/GameModes/UI/GameModeTabUI.cs:359 — GameModeTabUI.Draw 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.
D2 · Cognitive Complexity · TilePhase.OnApply (cognitive 21) · ×1
  • TilePhase.OnApply (cognitive 21) Content/HackTimes/Protocols/TilePhase.cs:35 — TilePhase.OnApply 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.
D2 · Cognitive Complexity · CollectorUI.DrawBindings (cognitive 21) · ×1
  • CollectorUI.DrawBindings (cognitive 21) Content/Industrials/ElectricPowers/Collectors/CollectorUI.cs:570 — CollectorUI.DrawBindings 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.
D2 · Cognitive Complexity · ProcessingChainVFX.OreChipColors (cognitive 21) · ×1
  • ProcessingChainVFX.OreChipColors (cognitive 21) Content/Industrials/ElectricPowers/Crushers/ProcessingChainVFX.cs:76 — ProcessingChainVFX.OreChipColors 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.
D2 · Cognitive Complexity · ShimmerTransmuteEngine.TryResolve (cognitive 21) · ×1
  • ShimmerTransmuteEngine.TryResolve (cognitive 21) Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterTP.cs:111 — ShimmerTransmuteEngine.TryResolve 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.
D2 · Cognitive Complexity · SlimeVatTP.TryPumpWater (cognitive 21) · ×1
  • SlimeVatTP.TryPumpWater (cognitive 21) Content/Industrials/ElectricPowers/SlimeVats/SlimeVatTP.cs:232 — SlimeVatTP.TryPumpWater 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.
D2 · Cognitive Complexity · MirrorheartPlayer.TickTimers (cognitive 21) · ×1
  • MirrorheartPlayer.TickTimers (cognitive 21) Content/Items/Accessories/BrutalRelics/BrainOfCthulhu/MirrorheartParadox.cs:120 — MirrorheartPlayer.TickTimers 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.
D2 · Cognitive Complexity · MirrorheartPulse.AI (cognitive 21) · ×1
  • MirrorheartPulse.AI (cognitive 21) Content/Items/Accessories/BrutalRelics/BrainOfCthulhu/MirrorheartPulse.cs:59 — MirrorheartPulse.AI 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.
D2 · Cognitive Complexity · MirrorheartRender.DrawBeforePlayers (cognitive 21) · ×1
  • MirrorheartRender.DrawBeforePlayers (cognitive 21) Content/Items/Accessories/BrutalRelics/BrainOfCthulhu/MirrorheartRender.cs:30 — MirrorheartRender.DrawBeforePlayers 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.
D2 · Cognitive Complexity · WingsOfInterferencePlayer.PostUpdate (cognitive 21) · ×1
  • WingsOfInterferencePlayer.PostUpdate (cognitive 21) Content/Items/Accessories/BrutalRelics/EmpressOfLight/WingsOfInterference.cs:304 — WingsOfInterferencePlayer.PostUpdate 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.
D2 · Cognitive Complexity · SwarmVortexPlayer.UpdateWax (cognitive 21) · ×1
  • SwarmVortexPlayer.UpdateWax (cognitive 21) Content/Items/Accessories/BrutalRelics/QueenBee/SwarmVortexPlayer.cs:241 — SwarmVortexPlayer.UpdateWax 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.
D2 · Cognitive Complexity · SwarmVortexProj.UpdateSoundAndParticles (cognitive 21) · ×1
  • SwarmVortexProj.UpdateSoundAndParticles (cognitive 21) Content/Items/Accessories/BrutalRelics/QueenBee/SwarmVortexProj.cs:226 — SwarmVortexProj.UpdateSoundAndParticles 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.
D2 · Cognitive Complexity · RefractionWaltzCrystalProj.RefreshLinkCaches (cognitive 21) · ×1
  • RefractionWaltzCrystalProj.RefreshLinkCaches (cognitive 21) Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzCrystalProj.cs:153 — RefractionWaltzCrystalProj.RefreshLinkCaches 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.
D2 · Cognitive Complexity · SoulbindingArmRender.EndEntityDraw (cognitive 21) · ×1
  • SoulbindingArmRender.EndEntityDraw (cognitive 21) Content/Items/Accessories/BrutalRelics/Skeletron/SoulbindingArmRender.cs:260 — SoulbindingArmRender.EndEntityDraw 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.
D2 · Cognitive Complexity · ElysiumRoseWindow.UpdateInteraction (cognitive 21) · ×1
  • ElysiumRoseWindow.UpdateInteraction (cognitive 21) Content/Items/Magic/Elysiums/UI/ElysiumRoseWindow.cs:125 — ElysiumRoseWindow.UpdateInteraction 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.
D2 · Cognitive Complexity · WheezingWyrmHeld.BreathePhase (cognitive 21) · ×1
  • WheezingWyrmHeld.BreathePhase (cognitive 21) Content/Items/Magic/WheezingWyrms/WheezingWyrmHeld.cs:231 — WheezingWyrmHeld.BreathePhase 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.
D2 · Cognitive Complexity · DawnshatterHeld.SpawnBladeFire (cognitive 21) · ×1
  • DawnshatterHeld.SpawnBladeFire (cognitive 21) Content/Items/Melee/DawnshatterAzures/DawnshatterHeld.cs:740 — DawnshatterHeld.SpawnBladeFire 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.
D2 · Cognitive Complexity · DivineSourceBoltProjectile.AI (cognitive 21) · ×1
  • DivineSourceBoltProjectile.AI (cognitive 21) Content/Items/Melee/DivineSourceBlades/DivineSourceBoltProjectile.cs:62 — DivineSourceBoltProjectile.AI 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.
D2 · Cognitive Complexity · HeartcarverPlayer.PostUpdate (cognitive 21) · ×1
  • HeartcarverPlayer.PostUpdate (cognitive 21) Content/Items/Melee/HeartcarverCore.cs:126 — HeartcarverPlayer.PostUpdate 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.
D2 · Cognitive Complexity · WastelandFangProj.AI (cognitive 21) · ×1
  • WastelandFangProj.AI (cognitive 21) Content/Items/Melee/WastelandFang.cs:75 — WastelandFangProj.AI 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.
D2 · Cognitive Complexity · GlacierWave.AI (cognitive 21) · ×1
  • GlacierWave.AI (cognitive 21) Content/Items/Ranged/CrystalDimming.cs:445 — GlacierWave.AI 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.
D2 · Cognitive Complexity · DarkFrostSolsticeHeld.Fire (cognitive 21) · ×1
  • DarkFrostSolsticeHeld.Fire (cognitive 21) Content/Items/Ranged/DarkFrostSolstice.cs:160 — DarkFrostSolsticeHeld.Fire 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.
D2 · Cognitive Complexity · DicoriaRay.AI (cognitive 21) · ×1
  • DicoriaRay.AI (cognitive 21) Content/Items/Ranged/Dicoria.cs:166 — DicoriaRay.AI 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.
D2 · Cognitive Complexity · UndertowBurst.AI (cognitive 21) · ×1
  • UndertowBurst.AI (cognitive 21) Content/Items/Ranged/Undertows/UndertowSpine.cs:226 — UndertowBurst.AI 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.
D2 · Cognitive Complexity · MarbleHuntingKnifeHeld.AI (cognitive 21) · ×1
  • MarbleHuntingKnifeHeld.AI (cognitive 21) Content/Items/Stones/Marbles/MarbleHuntingKnife.cs:171 — MarbleHuntingKnifeHeld.AI 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.
D2 · Cognitive Complexity · DeepclawSnapBurst.AI (cognitive 21) · ×1
  • DeepclawSnapBurst.AI (cognitive 21) Content/Items/Summon/Deepclaws/DeepclawLobster.cs:518 — DeepclawSnapBurst.AI 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.
D2 · Cognitive Complexity · DynamiteFishProjectile.LandedPhaseAI (cognitive 21) · ×1
  • DynamiteFishProjectile.LandedPhaseAI (cognitive 21) Content/LegendWeapon/HalibutLegend/FishSkills/FishDynamite.cs:145 — DynamiteFishProjectile.LandedPhaseAI 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.
D2 · Cognitive Complexity · DynamiteFishProjectile.PreDraw (cognitive 21) · ×1
  • DynamiteFishProjectile.PreDraw (cognitive 21) Content/LegendWeapon/HalibutLegend/FishSkills/FishDynamite.cs:419 — DynamiteFishProjectile.PreDraw 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.
D2 · Cognitive Complexity · HoneyBeeMinion.PreDraw (cognitive 21) · ×1
  • HoneyBeeMinion.PreDraw (cognitive 21) Content/LegendWeapon/HalibutLegend/FishSkills/FishHoney.cs:728 — HoneyBeeMinion.PreDraw 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.
D2 · Cognitive Complexity · MiniWhiteWyvern.AI (cognitive 21) · ×1
  • MiniWhiteWyvern.AI (cognitive 21) Content/LegendWeapon/HalibutLegend/FishSkills/FishWyverntail.cs:173 — MiniWhiteWyvern.AI 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.
D2 · Cognitive Complexity · KikasaDreamHound.AI (cognitive 21) · ×1
  • KikasaDreamHound.AI (cognitive 21) Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamHound.cs:185 — KikasaDreamHound.AI 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.
D2 · Cognitive Complexity · KikasaDreamProjectileBan.IsSwallowed (cognitive 21) · ×1
  • KikasaDreamProjectileBan.IsSwallowed (cognitive 21) Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamProjectileBan.cs:73 — KikasaDreamProjectileBan.IsSwallowed 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.
D2 · Cognitive Complexity · KikasaRainUmbrella.AI (cognitive 21) · ×1
  • KikasaRainUmbrella.AI (cognitive 21) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:327 — KikasaRainUmbrella.AI 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.
D2 · Cognitive Complexity · KikasaOnikiriServant.UpdateEmerge (cognitive 21) · ×1
  • KikasaOnikiriServant.UpdateEmerge (cognitive 21) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:328 — KikasaOnikiriServant.UpdateEmerge 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.
D2 · Cognitive Complexity · KikasaPandemoniumServant.UpdateEmerge (cognitive 21) · ×1
  • KikasaPandemoniumServant.UpdateEmerge (cognitive 21) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:274 — KikasaPandemoniumServant.UpdateEmerge 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.
D2 · Cognitive Complexity · KikasaRodServant.UpdateEmerge (cognitive 21) · ×1
  • KikasaRodServant.UpdateEmerge (cognitive 21) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:247 — KikasaRodServant.UpdateEmerge 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.
D2 · Cognitive Complexity · KikasaZenithServant.UpdateEmerge (cognitive 21) · ×1
  • KikasaZenithServant.UpdateEmerge (cognitive 21) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:344 — KikasaZenithServant.UpdateEmerge 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.
D2 · Cognitive Complexity · KikasaCultistServant.DrawGatherLayer (cognitive 21) · ×1
  • KikasaCultistServant.DrawGatherLayer (cognitive 21) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:1283 — KikasaCultistServant.DrawGatherLayer 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.
D2 · Cognitive Complexity · KikasaEaterServant.UpdateSeam (cognitive 21) · ×1
  • KikasaEaterServant.UpdateSeam (cognitive 21) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:480 — KikasaEaterServant.UpdateSeam 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.
D2 · Cognitive Complexity · KikasaEmpressServant.UpdateFollow (cognitive 21) · ×1
  • KikasaEmpressServant.UpdateFollow (cognitive 21) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:385 — KikasaEmpressServant.UpdateFollow 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.
D2 · Cognitive Complexity · KikasaSkeletronServant.UpdateSkulls (cognitive 21) · ×1
  • KikasaSkeletronServant.UpdateSkulls (cognitive 21) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:839 — KikasaSkeletronServant.UpdateSkulls 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.
D2 · Cognitive Complexity · KikasaSkeletronServant.UpdateDissolve (cognitive 21) · ×1
  • KikasaSkeletronServant.UpdateDissolve (cognitive 21) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:960 — KikasaSkeletronServant.UpdateDissolve 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.
D2 · Cognitive Complexity · KikasaTalismanGlyph.DrawInk (cognitive 21) · ×1
  • KikasaTalismanGlyph.DrawInk (cognitive 21) Content/LegendWeapon/KikasaLegend/KikasaTalismans/KikasaTalismanGlyph.cs:103 — KikasaTalismanGlyph.DrawInk 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.
D2 · Cognitive Complexity · KikasaHudLead.ResolveSubText (cognitive 21) · ×1
  • KikasaHudLead.ResolveSubText (cognitive 21) Content/LegendWeapon/KikasaLegend/UI/KikasaHudLead.cs:720 — KikasaHudLead.ResolveSubText 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.
D2 · Cognitive Complexity · OniDomainPlayer.UpdateClosing (cognitive 21) · ×1
  • OniDomainPlayer.UpdateClosing (cognitive 21) Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainPlayer.cs:648 — OniDomainPlayer.UpdateClosing 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.
D2 · Cognitive Complexity · OnikiriPlayer.OnFlashStepFinished (cognitive 21) · ×1
  • OnikiriPlayer.OnFlashStepFinished (cognitive 21) Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs:1535 — OnikiriPlayer.OnFlashStepFinished 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.
D2 · Cognitive Complexity · SakuraDashProj.AI (cognitive 21) · ×1
  • SakuraDashProj.AI (cognitive 21) Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraDashProj.cs:51 — SakuraDashProj.AI 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.
D2 · Cognitive Complexity · OniSigilUI.Draw (cognitive 21) · ×1
  • OniSigilUI.Draw (cognitive 21) Content/LegendWeapon/OnikiriLegend/UI/OniSigilUI.cs:726 — OniSigilUI.Draw 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.
D2 · Cognitive Complexity · CyberRestartProj.Warp (cognitive 21) · ×1
  • CyberRestartProj.Warp (cognitive 21) Content/LegendWeapon/SHPCLegend/Cyberspaces/Restart/CyberRestartProj.cs:571 — CyberRestartProj.Warp 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.
D2 · Cognitive Complexity · QuantumFrameModule.HandleHit (cognitive 21) · ×1
  • QuantumFrameModule.HandleHit (cognitive 21) Content/LegendWeapon/SHPCLegend/Modules/Frame/QuantumFrameModule.cs:48 — QuantumFrameModule.HandleHit 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.
D2 · Cognitive Complexity · QuantumFrameModule.OnPlayerUpdate (cognitive 21) · ×1
  • QuantumFrameModule.OnPlayerUpdate (cognitive 21) Content/LegendWeapon/SHPCLegend/Modules/Frame/QuantumFrameModule.cs:110 — QuantumFrameModule.OnPlayerUpdate 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.
D2 · Cognitive Complexity · MoldCategorySidebar.Draw (cognitive 21) · ×1
  • MoldCategorySidebar.Draw (cognitive 21) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCategorySidebar.cs:56 — MoldCategorySidebar.Draw 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.
D2 · Cognitive Complexity · MoldCodexPanel.Draw (cognitive 21) · ×1
  • MoldCodexPanel.Draw (cognitive 21) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldCodexPanel.cs:101 — MoldCodexPanel.Draw 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.
D2 · Cognitive Complexity · SHPCPlayer.BackfillDiscoveredFromInventoryAndPresets (cognitive 21) · ×1
  • SHPCPlayer.BackfillDiscoveredFromInventoryAndPresets (cognitive 21) Content/LegendWeapon/SHPCLegend/SHPCPlayer.cs:386 — SHPCPlayer.BackfillDiscoveredFromInventoryAndPresets 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.
D2 · Cognitive Complexity · SHPCModuleSelectPanel.DrawCustomTooltip (cognitive 21) · ×1
  • SHPCModuleSelectPanel.DrawCustomTooltip (cognitive 21) Content/LegendWeapon/SHPCLegend/UI/SHPCModuleSelectPanel.cs:332 — SHPCModuleSelectPanel.DrawCustomTooltip 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.
D2 · Cognitive Complexity · BssLegRig.Advance (cognitive 21) · ×1
  • BssLegRig.Advance (cognitive 21) Content/NPCs/BloomsandSerpents/BssLegRig.cs:245 — BssLegRig.Advance 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.
D2 · Cognitive Complexity · BssLegRig.UpdateWalk (cognitive 21) · ×1
  • BssLegRig.UpdateWalk (cognitive 21) Content/NPCs/BloomsandSerpents/BssLegRig.cs:405 — BssLegRig.UpdateWalk 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.
D2 · Cognitive Complexity · BssSandVortexProj.Detonate (cognitive 21) · ×1
  • BssSandVortexProj.Detonate (cognitive 21) Content/NPCs/BloomsandSerpents/Projectiles/BssSandVortexProj.cs:167 — BssSandVortexProj.Detonate 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.
D2 · Cognitive Complexity · BssApexBloomState.OnUpdate (cognitive 21) · ×1
  • BssApexBloomState.OnUpdate (cognitive 21) Content/NPCs/BloomsandSerpents/States/BssApexBloomState.cs:28 — BssApexBloomState.OnUpdate 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.
D2 · Cognitive Complexity · DestroyerBodyAI.AI (cognitive 21) · ×1
  • DestroyerBodyAI.AI (cognitive 21) Content/NPCs/BrutalNPCs/BrutalDestroyer/DestroyerBodyAI.cs:105 — DestroyerBodyAI.AI 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.
D2 · Cognitive Complexity · DestroyerHeadAI.HandleMouth (cognitive 21) · ×1
  • DestroyerHeadAI.HandleMouth (cognitive 21) Content/NPCs/BrutalNPCs/BrutalDestroyer/DestroyerHeadAI.cs:308 — DestroyerHeadAI.HandleMouth 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.
D2 · Cognitive Complexity · DestroyerBurrowAmbushState.UpdateErupt (cognitive 21) · ×1
  • DestroyerBurrowAmbushState.UpdateErupt (cognitive 21) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:221 — DestroyerBurrowAmbushState.UpdateErupt 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.
D2 · Cognitive Complexity · DestroyerCoilLockState.OnUpdate (cognitive 21) · ×1
  • DestroyerCoilLockState.OnUpdate (cognitive 21) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerCoilLockState.cs:94 — DestroyerCoilLockState.OnUpdate 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.
D2 · Cognitive Complexity · DestroyerDiveStrikeState.UpdatePass (cognitive 21) · ×1
  • DestroyerDiveStrikeState.UpdatePass (cognitive 21) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerDiveStrikeState.cs:99 — DestroyerDiveStrikeState.UpdatePass 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.
D2 · Cognitive Complexity · FishronBubbleMazeState.OnUpdate (cognitive 21) · ×1
  • FishronBubbleMazeState.OnUpdate (cognitive 21) Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronBubbleMazeState.cs:98 — FishronBubbleMazeState.OnUpdate 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.
D2 · Cognitive Complexity · EowHeadAI.UpdateSplitSteering (cognitive 21) · ×1
  • EowHeadAI.UpdateSplitSteering (cognitive 21) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/EowHeadAI.cs:429 — EowHeadAI.UpdateSplitSteering 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.
D2 · Cognitive Complexity · EowLungeFlurryState.UpdateLunge (cognitive 21) · ×1
  • EowLungeFlurryState.UpdateLunge (cognitive 21) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowLungeFlurryState.cs:52 — EowLungeFlurryState.UpdateLunge 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.
D2 · Cognitive Complexity · EocGrabPerformancePlayer.PostUpdate (cognitive 21) · ×1
  • EocGrabPerformancePlayer.PostUpdate (cognitive 21) Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/EocGrabPerformancePlayer.cs:95 — EocGrabPerformancePlayer.PostUpdate 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.
D2 · Cognitive Complexity · GolemHeadDetachState.OnUpdate (cognitive 21) · ×1
  • GolemHeadDetachState.OnUpdate (cognitive 21) Content/NPCs/BrutalNPCs/BrutalGolem/States/GolemHeadDetachState.cs:54 — GolemHeadDetachState.OnUpdate 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.
D2 · Cognitive Complexity · GolemWallSlamState.OnUpdate (cognitive 21) · ×1
  • GolemWallSlamState.OnUpdate (cognitive 21) Content/NPCs/BrutalNPCs/BrutalGolem/States/GolemWallSlamState.cs:61 — GolemWallSlamState.OnUpdate 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.
D2 · Cognitive Complexity · CultistGazeBeam.AI (cognitive 21) · ×1
  • CultistGazeBeam.AI (cognitive 21) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistGazeBeam.cs:105 — CultistGazeBeam.AI 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.
D2 · Cognitive Complexity · PincerBindTether.AI (cognitive 21) · ×1
  • PincerBindTether.AI (cognitive 21) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/PincerBindTether.cs:65 — PincerBindTether.AI 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.
D2 · Cognitive Complexity · TwinsScissorRayState.ExecuteSweepPhase (cognitive 21) · ×1
  • TwinsScissorRayState.ExecuteSweepPhase (cognitive 21) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsScissorRayState.cs:168 — TwinsScissorRayState.ExecuteSweepPhase 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.
D2 · Cognitive Complexity · RetinazerHorizontalBarrageState.OnUpdate (cognitive 21) · ×1
  • RetinazerHorizontalBarrageState.OnUpdate (cognitive 21) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerHorizontalBarrageState.cs:40 — RetinazerHorizontalBarrageState.OnUpdate 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.
D2 · Cognitive Complexity · SpazmatismFireVortexState.OnUpdate (cognitive 21) · ×1
  • SpazmatismFireVortexState.OnUpdate (cognitive 21) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismFireVortexState.cs:42 — SpazmatismFireVortexState.OnUpdate 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.
D2 · Cognitive Complexity · SpazmatismSoloRageState.ExecuteBurstFire (cognitive 21) · ×1
  • SpazmatismSoloRageState.ExecuteBurstFire (cognitive 21) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismSoloRageState.cs:293 — SpazmatismSoloRageState.ExecuteBurstFire 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.
D2 · Cognitive Complexity · TwinsAIController.ExecuteDebutSequence (cognitive 21) · ×1
  • TwinsAIController.ExecuteDebutSequence (cognitive 21) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/TwinsAIController.cs:498 — TwinsAIController.ExecuteDebutSequence 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.
D2 · Cognitive Complexity · MLordLocomotion.ResolveGait (cognitive 21) · ×1
  • MLordLocomotion.ResolveGait (cognitive 21) Content/NPCs/BrutalNPCs/BrutalMoonLord/Core/MLordLocomotion.cs:489 — MLordLocomotion.ResolveGait 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.
D2 · Cognitive Complexity · QBSwarmWallState.OnUpdate (cognitive 21) · ×1
  • QBSwarmWallState.OnUpdate (cognitive 21) Content/NPCs/BrutalNPCs/BrutalQueenBee/States/QBSwarmWallState.cs:49 — QBSwarmWallState.OnUpdate 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.
D2 · Cognitive Complexity · QueenSlimePerformancePlayer.HandleGrabbed (cognitive 21) · ×1
  • QueenSlimePerformancePlayer.HandleGrabbed (cognitive 21) Content/NPCs/BrutalNPCs/BrutalQueenSlime/QueenSlimePerformancePlayer.cs:80 — QueenSlimePerformancePlayer.HandleGrabbed 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.
D2 · Cognitive Complexity · QueenSkySpikeCascadeState.OnUpdate (cognitive 21) · ×1
  • QueenSkySpikeCascadeState.OnUpdate (cognitive 21) Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenSkySpikeCascadeState.cs:51 — QueenSkySpikeCascadeState.OnUpdate 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.
D2 · Cognitive Complexity · WofEyeScanState.FireBeams (cognitive 21) · ×1
  • WofEyeScanState.FireBeams (cognitive 21) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/States/WofEyeScanState.cs:78 — WofEyeScanState.FireBeams 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.
D2 · Cognitive Complexity · FssHead.UpdateStormPresentation (cognitive 21) · ×1
  • FssHead.UpdateStormPresentation (cognitive 21) Content/NPCs/FestersandSerpents/FssHead.cs:742 — FssHead.UpdateStormPresentation 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.
D2 · Cognitive Complexity · FssIchorSpitState.OnUpdate (cognitive 21) · ×1
  • FssIchorSpitState.OnUpdate (cognitive 21) Content/NPCs/FestersandSerpents/States/FssIchorSpitState.cs:26 — FssIchorSpitState.OnUpdate 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.
D2 · Cognitive Complexity · CrabulonPlayer.PostUpdate (cognitive 21) · ×1
  • CrabulonPlayer.PostUpdate (cognitive 21) Content/NPCs/Modifys/Crabulons/CrabulonPlayer.cs:37 — CrabulonPlayer.PostUpdate 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.
D2 · Cognitive Complexity · ScrapHubState.OnUpdate (cognitive 21) · ×1
  • ScrapHubState.OnUpdate (cognitive 21) Content/NPCs/ScrapCommanders/States/ScrapHubState.cs:24 — ScrapHubState.OnUpdate 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.
D2 · Cognitive Complexity · ScrapHubState.PickAttack (cognitive 21) · ×1
  • ScrapHubState.PickAttack (cognitive 21) Content/NPCs/ScrapCommanders/States/ScrapHubState.cs:131 — ScrapHubState.PickAttack 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.
D2 · Cognitive Complexity · ScrapLaserMatrixState.OnUpdate (cognitive 21) · ×1
  • ScrapLaserMatrixState.OnUpdate (cognitive 21) Content/NPCs/ScrapCommanders/States/ScrapLaserMatrixState.cs:34 — ScrapLaserMatrixState.OnUpdate 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.
D2 · Cognitive Complexity · SeaShrimpRenderer.DrawAfterimages (cognitive 21) · ×1
  • SeaShrimpRenderer.DrawAfterimages (cognitive 21) Content/NPCs/SeaShrimp/Rendering/SeaShrimpRenderer.cs:251 — SeaShrimpRenderer.DrawAfterimages 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.
D2 · Cognitive Complexity · SeaShrimpPlowChargeState.OnUpdate (cognitive 21) · ×1
  • SeaShrimpPlowChargeState.OnUpdate (cognitive 21) Content/NPCs/SeaShrimp/States/SeaShrimpPlowChargeState.cs:31 — SeaShrimpPlowChargeState.OnUpdate 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.
D2 · Cognitive Complexity · QuestLog.Draw (cognitive 21) · ×1
  • QuestLog.Draw (cognitive 21) Content/QuestLogs/QuestLog.cs:804 — QuestLog.Draw 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.
D2 · Cognitive Complexity · HotwindQuestLogStyle.DrawNode (cognitive 21) · ×1
  • HotwindQuestLogStyle.DrawNode (cognitive 21) Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:130 — HotwindQuestLogStyle.DrawNode 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.
D2 · Cognitive Complexity · AnnexPlanner.HangSealedRooms (cognitive 21) · ×1
  • AnnexPlanner.HangSealedRooms (cognitive 21) Content/Scenarios/Dungeonworld/Gen/Infill/AnnexPlanner.cs:237 — AnnexPlanner.HangSealedRooms 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.
D2 · Cognitive Complexity · L2Rooms.BuildHall (cognitive 21) · ×1
  • L2Rooms.BuildHall (cognitive 21) Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2Rooms.cs:124 — L2Rooms.BuildHall 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.
D2 · Cognitive Complexity · L6Rooms.BuildFoundryHall (cognitive 21) · ×1
  • L6Rooms.BuildFoundryHall (cognitive 21) Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Rooms.cs:227 — L6Rooms.BuildFoundryHall 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.
D2 · Cognitive Complexity · SlagVentBelt.AssertLavaSealed (cognitive 21) · ×1
  • SlagVentBelt.AssertLavaSealed (cognitive 21) Content/Scenarios/Dungeonworld/Gen/Zones/SlagVentBelt.cs:329 — SlagVentBelt.AssertLavaSealed 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.
D2 · Cognitive Complexity · DeepGaolWraith.UpdateCage (cognitive 21) · ×1
  • DeepGaolWraith.UpdateCage (cognitive 21) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:1268 — DeepGaolWraith.UpdateCage 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.
D2 · Cognitive Complexity · RestitchedBones.DrawAssembly (cognitive 21) · ×1
  • RestitchedBones.DrawAssembly (cognitive 21) Content/Scenarios/Dungeonworld/NPCs/Elites/BoneStitcher.cs:991 — RestitchedBones.DrawAssembly 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.
D2 · Cognitive Complexity · DrownedTurnkey.UpdateVisualEnvelopes (cognitive 21) · ×1
  • DrownedTurnkey.UpdateVisualEnvelopes (cognitive 21) Content/Scenarios/Dungeonworld/NPCs/Elites/DrownedTurnkey.cs:275 — DrownedTurnkey.UpdateVisualEnvelopes 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.
D2 · Cognitive Complexity · DrownedTurnkey.UpdateSuppress (cognitive 21) · ×1
  • DrownedTurnkey.UpdateSuppress (cognitive 21) Content/Scenarios/Dungeonworld/NPCs/Elites/DrownedTurnkey.cs:549 — DrownedTurnkey.UpdateSuppress 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.
D2 · Cognitive Complexity · FoundryOverseer.UpdateEmerge (cognitive 21) · ×1
  • FoundryOverseer.UpdateEmerge (cognitive 21) Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:514 — FoundryOverseer.UpdateEmerge 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.
D2 · Cognitive Complexity · FoundryOverseer.UpdateBreakRail (cognitive 21) · ×1
  • FoundryOverseer.UpdateBreakRail (cognitive 21) Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:848 — FoundryOverseer.UpdateBreakRail 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.
D2 · Cognitive Complexity · GaolCrossChain.AI (cognitive 21) · ×1
  • GaolCrossChain.AI (cognitive 21) Content/Scenarios/Dungeonworld/NPCs/GaolCrossChain.cs:47 — GaolCrossChain.AI 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.
D2 · Cognitive Complexity · HadalTerrainCarver.CarveTrench (cognitive 21) · ×1
  • HadalTerrainCarver.CarveTrench (cognitive 21) Content/Scenarios/Hadalworld/Gen/Core/HadalTerrainCarver.cs:128 — HadalTerrainCarver.CarveTrench 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.
D2 · Cognitive Complexity · ToriiShrineLocationFinder.TryEvaluateColumn (cognitive 21) · ×1
  • ToriiShrineLocationFinder.TryEvaluateColumn (cognitive 21) Content/Scenarios/Himayo/ToriiShrines/ToriiShrineLocationFinder.cs:149 — ToriiShrineLocationFinder.TryEvaluateColumn 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.
D2 · Cognitive Complexity · KiameOniDirector.MaintainPopulation (cognitive 21) · ×1
  • KiameOniDirector.MaintainPopulation (cognitive 21) Content/Scenarios/Kiame/NPCs/KiameOniDirector.cs:48 — KiameOniDirector.MaintainPopulation 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.
D2 · Cognitive Complexity · OniUmbrellaWorldSpawn.TryEvaluateColumn (cognitive 21) · ×1
  • OniUmbrellaWorldSpawn.TryEvaluateColumn (cognitive 21) Content/Scenarios/Kiame/Overlay/OniUmbrellaWorldSpawn.cs:374 — OniUmbrellaWorldSpawn.TryEvaluateColumn 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.
D2 · Cognitive Complexity · KiyumeFogSim.Step (cognitive 21) · ×1
  • KiyumeFogSim.Step (cognitive 21) Content/Scenarios/Kiyume/Fog/KiyumeFogSim.cs:259 — KiyumeFogSim.Step 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.
D2 · Cognitive Complexity · KiyumeShoalWrecks.BuildReedCell (cognitive 21) · ×1
  • KiyumeShoalWrecks.BuildReedCell (cognitive 21) Content/Scenarios/Kiyume/Gen/KiyumeShoalWrecks.cs:288 — KiyumeShoalWrecks.BuildReedCell 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.
D2 · Cognitive Complexity · KiyumeHoundDirector.ArbitrateFlank (cognitive 21) · ×1
  • KiyumeHoundDirector.ArbitrateFlank (cognitive 21) Content/Scenarios/Kiyume/NPCs/KiyumeHoundDirector.cs:298 — KiyumeHoundDirector.ArbitrateFlank 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.
D2 · Cognitive Complexity · KiyumeHoundEyeGleam.Draw (cognitive 21) · ×1
  • KiyumeHoundEyeGleam.Draw (cognitive 21) Content/Scenarios/Kiyume/NPCs/KiyumeHoundEyeGleam.cs:33 — KiyumeHoundEyeGleam.Draw 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.
D2 · Cognitive Complexity · OldNetRoomBuilder.HangRoomsOffLanding (cognitive 21) · ×1
  • OldNetRoomBuilder.HangRoomsOffLanding (cognitive 21) Content/Scenarios/OldNet/Gen/Rooms/OldNetRoomBuilder.cs:29 — OldNetRoomBuilder.HangRoomsOffLanding 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.
D2 · Cognitive Complexity · SHPCCradleGen.CarveCrash (cognitive 21) · ×1
  • SHPCCradleGen.CarveCrash (cognitive 21) Content/Structures/SHPCCradleGen.cs:347 — SHPCCradleGen.CarveCrash 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.
D2 · Cognitive Complexity · EntryDecisionUI.SyncSlots (cognitive 21) · ×1
  • EntryDecisionUI.SyncSlots (cognitive 21) Content/UIs/EntryDecisions/EntryDecisionUI.cs:176 — EntryDecisionUI.SyncSlots 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.
D2 · Cognitive Complexity · CrimsonBrideRitePlayer.PreUpdateMovement (cognitive 21) · ×1
  • CrimsonBrideRitePlayer.PreUpdateMovement (cognitive 21) Content/Wraiths/Abilities/CrimsonBrides/CrimsonBrideRestart.cs:219 — CrimsonBrideRitePlayer.PreUpdateMovement 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.
D2 · Cognitive Complexity · LanternBoyProj.TryApplyAuthorityImpact (cognitive 21) · ×1
  • LanternBoyProj.TryApplyAuthorityImpact (cognitive 21) Content/Wraiths/Projectiles/LanternBoyProj.cs:248 — LanternBoyProj.TryApplyAuthorityImpact 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.
D2 · Cognitive Complexity · WraithPlayer.UpdateAuthority (cognitive 21) · ×1
  • WraithPlayer.UpdateAuthority (cognitive 21) Content/Wraiths/Runtime/WraithPlayer.cs:385 — WraithPlayer.UpdateAuthority 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.
D2 · Cognitive Complexity · EntrustAPI.TryRegister (cognitive 20) · ×1
  • EntrustAPI.TryRegister (cognitive 20) API/EntrustAPI.cs:58 — EntrustAPI.TryRegister has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · QuestLogsAPI.ApplyLayout (cognitive 20) · ×1
  • QuestLogsAPI.ApplyLayout (cognitive 20) API/QuestLogsAPI.cs:193 — QuestLogsAPI.ApplyLayout has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CWRID.Get (cognitive 20) · ×1
  • CWRID.Get (cognitive 20) CWRID.cs:465 — CWRID.Get has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CyberwareSkillRadialController.HandleSkillKey (cognitive 20) · ×1
  • CyberwareSkillRadialController.HandleSkillKey (cognitive 20) Content/Cyberwares/Skills/CyberwareSkillRadialController.cs:214 — CyberwareSkillRadialController.HandleSkillKey has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · AstralveilTideRender.EndEntityDraw (cognitive 20) · ×1
  • AstralveilTideRender.EndEntityDraw (cognitive 20) Content/GameModes/BrutalMobs/Ambience/Astralveil/AstralveilTideRender.cs:41 — AstralveilTideRender.EndEntityDraw has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BrinefumeAmbientRender.UpdateBySystem (cognitive 20) · ×1
  • BrinefumeAmbientRender.UpdateBySystem (cognitive 20) Content/GameModes/BrutalMobs/Ambience/Brinefume/BrinefumeAmbientRender.cs:48 — BrinefumeAmbientRender.UpdateBySystem has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FrostveilGaleWallProj.ApplyToLocalPlayer (cognitive 20) · ×1
  • FrostveilGaleWallProj.ApplyToLocalPlayer (cognitive 20) Content/GameModes/BrutalMobs/Ambience/Frostveil/Projectiles/FrostveilGaleWallProj.cs:189 — FrostveilGaleWallProj.ApplyToLocalPlayer has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HollowdeepPlayer.PostUpdate (cognitive 20) · ×1
  • HollowdeepPlayer.PostUpdate (cognitive 20) Content/GameModes/BrutalMobs/Ambience/Hollowdeep/HollowdeepPlayer.cs:52 — HollowdeepPlayer.PostUpdate has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PrismgladeAmbience.UpdateCrystalFlashes (cognitive 20) · ×1
  • PrismgladeAmbience.UpdateCrystalFlashes (cognitive 20) Content/GameModes/BrutalMobs/Ambience/Prismglade/PrismgladeAmbience.cs:353 — PrismgladeAmbience.UpdateCrystalFlashes has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · RainveilThunderboltProj.AI (cognitive 20) · ×1
  • RainveilThunderboltProj.AI (cognitive 20) Content/GameModes/BrutalMobs/Ambience/Rainveil/Projectiles/RainveilThunderboltProj.cs:71 — RainveilThunderboltProj.AI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · RimehollowDirector.TrySpawnIcicles (cognitive 20) · ×1
  • RimehollowDirector.TrySpawnIcicles (cognitive 20) Content/GameModes/BrutalMobs/Ambience/Rimehollow/RimehollowDirector.cs:87 — RimehollowDirector.TrySpawnIcicles has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · RotmireWritheProj.PreDraw (cognitive 20) · ×1
  • RotmireWritheProj.PreDraw (cognitive 20) Content/GameModes/BrutalMobs/Ambience/Rotmire/Projectiles/RotmireWritheProj.cs:237 — RotmireWritheProj.PreDraw has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SunkenduneAmbientRender.UpdateBeetles (cognitive 20) · ×1
  • SunkenduneAmbientRender.UpdateBeetles (cognitive 20) Content/GameModes/BrutalMobs/Ambience/Sunkendune/SunkenduneAmbientRender.cs:198 — SunkenduneAmbientRender.UpdateBeetles has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TidecallRogueWaveProj.DrawBreakAndWash (cognitive 20) · ×1
  • TidecallRogueWaveProj.DrawBreakAndWash (cognitive 20) Content/GameModes/BrutalMobs/Ambience/Tidecall/Projectiles/TidecallRogueWaveProj.cs:449 — TidecallRogueWaveProj.DrawBreakAndWash has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EclipseNPC.TickTelegraph (cognitive 20) · ×1
  • EclipseNPC.TickTelegraph (cognitive 20) Content/GameModes/BrutalMobs/Eclipse/EclipseNPC.cs:331 — EclipseNPC.TickTelegraph has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MrtLaserMarkLine.AI (cognitive 20) · ×1
  • MrtLaserMarkLine.AI (cognitive 20) Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserMarkLine.cs:121 — MrtLaserMarkLine.AI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MrtTeslaArcProj.AI (cognitive 20) · ×1
  • MrtTeslaArcProj.AI (cognitive 20) Content/GameModes/BrutalMobs/Martians/Projectiles/MrtTeslaArcProj.cs:79 — MrtTeslaArcProj.AI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · NightDiveOmen.AI (cognitive 20) · ×1
  • NightDiveOmen.AI (cognitive 20) Content/GameModes/BrutalMobs/NightPack/Projectiles/NightDiveOmen.cs:79 — NightDiveOmen.AI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PmkEmberFlareProj.AI (cognitive 20) · ×1
  • PmkEmberFlareProj.AI (cognitive 20) Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkEmberFlareProj.cs:57 — PmkEmberFlareProj.AI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PmkEmberProj.AI (cognitive 20) · ×1
  • PmkEmberProj.AI (cognitive 20) Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkEmberProj.cs:66 — PmkEmberProj.AI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PmkRootSpikeProj.AI (cognitive 20) · ×1
  • PmkRootSpikeProj.AI (cognitive 20) Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkRootSpikeProj.cs:87 — PmkRootSpikeProj.AI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SlimeGelBomb.AI (cognitive 20) · ×1
  • SlimeGelBomb.AI (cognitive 20) Content/GameModes/BrutalMobs/SlimeKin/Projectiles/SlimeGelBomb.cs:67 — SlimeGelBomb.AI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · StonebornQuakeCharge.AI (cognitive 20) · ×1
  • StonebornQuakeCharge.AI (cognitive 20) Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornQuakeCharge.cs:48 — StonebornQuakeCharge.AI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GodSmithCobaltShield.OnHurt (cognitive 20) · ×1
  • GodSmithCobaltShield.OnHurt (cognitive 20) Content/GameModes/GodSmith/Accessories/Defense/GodSmithShieldChain.cs:72 — GodSmithCobaltShield.OnHurt has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GsCrimsonArmorLeechProj.AI (cognitive 20) · ×1
  • GsCrimsonArmorLeechProj.AI (cognitive 20) Content/GameModes/GodSmith/Armors/Reset/GsCrimsonArmor.cs:70 — GsCrimsonArmorLeechProj.AI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GsPalladiumArmorOrbProj.AI (cognitive 20) · ×1
  • GsPalladiumArmorOrbProj.AI (cognitive 20) Content/GameModes/GodSmith/Armors/Reset/GsOreArmorsHardmode.cs:332 — GsPalladiumArmorOrbProj.AI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GodSmithArmorPiece.ModifyTooltips (cognitive 20) · ×1
  • GodSmithArmorPiece.ModifyTooltips (cognitive 20) Content/GameModes/GodSmith/Framework/GodSmithArmorReset.cs:105 — GodSmithArmorPiece.ModifyTooltips has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GodSmithHelmetNestItem.PostDrawTooltip (cognitive 20) · ×1
  • GodSmithHelmetNestItem.PostDrawTooltip (cognitive 20) Content/GameModes/GodSmith/Framework/GodSmithHelmetNestItem.cs:193 — GodSmithHelmetNestItem.PostDrawTooltip has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GsFlamerHeldBase.AI (cognitive 20) · ×1
  • GsFlamerHeldBase.AI (cognitive 20) Content/GameModes/GodSmith/Weapons/Flamethrowers/FlamethrowersShared.cs:72 — GsFlamerHeldBase.AI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GsNimbusCorridorProj.AI (cognitive 20) · ×1
  • GsNimbusCorridorProj.AI (cognitive 20) Content/GameModes/GodSmith/Weapons/MagicMorph/Projectiles/GsNimbusCorridorProj.cs:73 — GsNimbusCorridorProj.AI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GsScourgeTinyEaterProj.FindTarget (cognitive 20) · ×1
  • GsScourgeTinyEaterProj.FindTarget (cognitive 20) Content/GameModes/GodSmith/Weapons/MeleeOddities/GsScourgeoftheCorruptor.cs:360 — GsScourgeTinyEaterProj.FindTarget has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MinionDoctrine.GetCache (cognitive 20) · ×1
  • MinionDoctrine.GetCache (cognitive 20) Content/GameModes/GodSmith/Weapons/SummonMinions/MinionDoctrine.cs:256 — MinionDoctrine.GetCache has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MinionDoctrine.ApplyFormationDrift (cognitive 20) · ×1
  • MinionDoctrine.ApplyFormationDrift (cognitive 20) Content/GameModes/GodSmith/Weapons/SummonMinions/MinionDoctrine.cs:333 — MinionDoctrine.ApplyFormationDrift has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BeaconForgeSpawnControl.TryRelocateToRing (cognitive 20) · ×1
  • BeaconForgeSpawnControl.TryRelocateToRing (cognitive 20) Content/HackTimes/Protocols/BeaconForge.cs:223 — BeaconForgeSpawnControl.TryRelocateToRing has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TurretMesh.OnApply (cognitive 20) · ×1
  • TurretMesh.OnApply (cognitive 20) Content/HackTimes/Protocols/TurretMesh.cs:78 — TurretMesh.OnApply has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PlayerHackNet.HandleScanProbe (cognitive 20) · ×1
  • PlayerHackNet.HandleScanProbe (cognitive 20) Content/HackTimes/PvP/PlayerHackNet.cs:880 — PlayerHackNet.HandleScanProbe has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · NpcScannable.BuildScanData (cognitive 20) · ×1
  • NpcScannable.BuildScanData (cognitive 20) Content/HackTimes/Scannables/NpcScannable.cs:36 — NpcScannable.BuildScanData has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · AutoCrafterTile.DrawHologram (cognitive 20) · ×1
  • AutoCrafterTile.DrawHologram (cognitive 20) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterTile.cs:174 — AutoCrafterTile.DrawHologram has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BottlingMachineTP.Draw (cognitive 20) · ×1
  • BottlingMachineTP.Draw (cognitive 20) Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineTP.cs:284 — BottlingMachineTP.Draw has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · IncineratorTP.UpdateMachine (cognitive 20) · ×1
  • IncineratorTP.UpdateMachine (cognitive 20) Content/Industrials/ElectricPowers/Incinerators/IncineratorTP.cs:47 — IncineratorTP.UpdateMachine has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PlayerLauncherTP.UpdateMachine (cognitive 20) · ×1
  • PlayerLauncherTP.UpdateMachine (cognitive 20) Content/Industrials/ElectricPowers/Launchers/PlayerLauncherTP.cs:100 — PlayerLauncherTP.UpdateMachine has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ShimmerTransmuterTP.RightClickByTile (cognitive 20) · ×1
  • ShimmerTransmuterTP.RightClickByTile (cognitive 20) Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterTP.cs:514 — ShimmerTransmuterTP.RightClickByTile has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SlimeVatTP.UpdateMachine (cognitive 20) · ×1
  • SlimeVatTP.UpdateMachine (cognitive 20) Content/Industrials/ElectricPowers/SlimeVats/SlimeVatTP.cs:314 — SlimeVatTP.UpdateMachine has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · InterferenceDawnBurst.AI (cognitive 20) · ×1
  • InterferenceDawnBurst.AI (cognitive 20) Content/Items/Accessories/BrutalRelics/EmpressOfLight/InterferenceBursts.cs:138 — InterferenceDawnBurst.AI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · RoyalGelField.AI (cognitive 20) · ×1
  • RoyalGelField.AI (cognitive 20) Content/Items/Accessories/BrutalRelics/KingSlime/RoyalGelField.cs:60 — RoyalGelField.AI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · RiteMirrorPhantom.TryResolveWeaponShot (cognitive 20) · ×1
  • RiteMirrorPhantom.TryResolveWeaponShot (cognitive 20) Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMirrorPhantom.cs:114 — RiteMirrorPhantom.TryResolveWeaponShot has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SandSmallTornado.OnTileCollide (cognitive 20) · ×1
  • SandSmallTornado.OnTileCollide (cognitive 20) Content/Items/Magic/MelodyTheSand.cs:203 — SandSmallTornado.OnTileCollide has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ArbiterFlameRenderer.CollectSources (cognitive 20) · ×1
  • ArbiterFlameRenderer.CollectSources (cognitive 20) Content/Items/Melee/Arbiters/ArbiterFlameRenderer.cs:131 — ArbiterFlameRenderer.CollectSources has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DivineSourceChargeBarLayer.Draw (cognitive 20) · ×1
  • DivineSourceChargeBarLayer.Draw (cognitive 20) Content/Items/Melee/DivineSourceBlades/DivineSourcePlayer.cs:158 — DivineSourceChargeBarLayer.Draw has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DivineSourceWaveProjectile.AI (cognitive 20) · ×1
  • DivineSourceWaveProjectile.AI (cognitive 20) Content/Items/Melee/DivineSourceBlades/DivineSourceWaveProjectile.cs:119 — DivineSourceWaveProjectile.AI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · RebelBladeHeld.AI (cognitive 20) · ×1
  • RebelBladeHeld.AI (cognitive 20) Content/Items/Melee/RebelBlade.cs:249 — RebelBladeHeld.AI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ShatterfangHeld.HandleParticles (cognitive 20) · ×1
  • ShatterfangHeld.HandleParticles (cognitive 20) Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:520 — ShatterfangHeld.HandleParticles has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LonginusVFX.DrawHelixTrail (cognitive 20) · ×1
  • LonginusVFX.DrawHelixTrail (cognitive 20) Content/Items/Melee/SpearOfLonginuses/LonginusAssets.cs:296 — LonginusVFX.DrawHelixTrail has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · RTerraBladeHeld.KickSlash (cognitive 20) · ×1
  • RTerraBladeHeld.KickSlash (cognitive 20) Content/Items/Modifys/RTerraBlades/RTerraBladeHeld.cs:472 — RTerraBladeHeld.KickSlash has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PallbearerCoffinSeal.AI (cognitive 20) · ×1
  • PallbearerCoffinSeal.AI (cognitive 20) Content/Items/Ranged/Pallbearer.cs:1077 — PallbearerCoffinSeal.AI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MarbleClubHeld.AI (cognitive 20) · ×1
  • MarbleClubHeld.AI (cognitive 20) Content/Items/Stones/Marbles/MarbleClub.cs:162 — MarbleClubHeld.AI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DestroyerHead.AI (cognitive 20) · ×1
  • DestroyerHead.AI (cognitive 20) Content/Items/Summon/StaffoftheDestroyer.cs:158 — DestroyerHead.AI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BatSwarmMinion.AI (cognitive 20) · ×1
  • BatSwarmMinion.AI (cognitive 20) Content/LegendWeapon/HalibutLegend/FishSkills/FishBat.cs:451 — BatSwarmMinion.AI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DynamiteExplosionEffect.PreDraw (cognitive 20) · ×1
  • DynamiteExplosionEffect.PreDraw (cognitive 20) Content/LegendWeapon/HalibutLegend/FishSkills/FishDynamite.cs:614 — DynamiteExplosionEffect.PreDraw has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SlimeGelOrb.AttachedPhaseAI (cognitive 20) · ×1
  • SlimeGelOrb.AttachedPhaseAI (cognitive 20) Content/LegendWeapon/HalibutLegend/FishSkills/FishSlime.cs:371 — SlimeGelOrb.AttachedPhaseAI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FishingFly.PreDraw (cognitive 20) · ×1
  • FishingFly.PreDraw (cognitive 20) Content/LegendWeapon/HalibutLegend/FishSkills/FishSwarm.cs:1106 — FishingFly.PreDraw has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · WhiteWyvernTailController.AI (cognitive 20) · ×1
  • WhiteWyvernTailController.AI (cognitive 20) Content/LegendWeapon/HalibutLegend/FishSkills/FishWyverntail.cs:73 — WhiteWyvernTailController.AI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · WaterZombie.LockChargeAI (cognitive 20) · ×1
  • WaterZombie.LockChargeAI (cognitive 20) Content/LegendWeapon/HalibutLegend/FishSkills/FishZombie.cs:384 — WaterZombie.LockChargeAI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaLakeSurface.ApplyStanding (cognitive 20) · ×1
  • KikasaLakeSurface.ApplyStanding (cognitive 20) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaLakeSurface.cs:40 — KikasaLakeSurface.ApplyStanding has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaMinionDrown.AdvanceWave (cognitive 20) · ×1
  • KikasaMinionDrown.AdvanceWave (cognitive 20) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaMinionDrown.cs:360 — KikasaMinionDrown.AdvanceWave has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaMinionDrownFX.DrainEmergences (cognitive 20) · ×1
  • KikasaMinionDrownFX.DrainEmergences (cognitive 20) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaMinionDrownFX.cs:391 — KikasaMinionDrownFX.DrainEmergences has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaInkFX.Update (cognitive 20) · ×1
  • KikasaInkFX.Update (cognitive 20) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkFX.cs:443 — KikasaInkFX.Update has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaInkFX.UpdateSurfaceDrip (cognitive 20) · ×1
  • KikasaInkFX.UpdateSurfaceDrip (cognitive 20) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkFX.cs:484 — KikasaInkFX.UpdateSurfaceDrip has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaRainUmbrella.UpdateEye (cognitive 20) · ×1
  • KikasaRainUmbrella.UpdateEye (cognitive 20) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:1291 — KikasaRainUmbrella.UpdateEye has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaBrainServant.UpdateOrbit (cognitive 20) · ×1
  • KikasaBrainServant.UpdateOrbit (cognitive 20) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:865 — KikasaBrainServant.UpdateOrbit has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaCultistServant.UpdateFollow (cognitive 20) · ×1
  • KikasaCultistServant.UpdateFollow (cognitive 20) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:423 — KikasaCultistServant.UpdateFollow has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaEaterServant.UpdateFeint (cognitive 20) · ×1
  • KikasaEaterServant.UpdateFeint (cognitive 20) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1147 — KikasaEaterServant.UpdateFeint has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaMoonLordServant.UpdateMoonOrbs (cognitive 20) · ×1
  • KikasaMoonLordServant.UpdateMoonOrbs (cognitive 20) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:633 — KikasaMoonLordServant.UpdateMoonOrbs has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaPlanteraServant.UpdateVine (cognitive 20) · ×1
  • KikasaPlanteraServant.UpdateVine (cognitive 20) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:742 — KikasaPlanteraServant.UpdateVine has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaPrimeServant.AI (cognitive 20) · ×1
  • KikasaPrimeServant.AI (cognitive 20) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:255 — KikasaPrimeServant.AI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FuLongFX.RunWash (cognitive 20) · ×1
  • FuLongFX.RunWash (cognitive 20) Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuLongFX.cs:49 — FuLongFX.RunWash has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaPanoramaUI.DrawTalisZone (cognitive 20) · ×1
  • KikasaPanoramaUI.DrawTalisZone (cognitive 20) Content/LegendWeapon/KikasaLegend/UI/Panorama/KikasaPanoramaUI.cs:1351 — KikasaPanoramaUI.DrawTalisZone has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CrimsonRendSlash.UpdateMeiOnBeatFired (cognitive 20) · ×1
  • CrimsonRendSlash.UpdateMeiOnBeatFired (cognitive 20) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:772 — CrimsonRendSlash.UpdateMeiOnBeatFired has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CrimsonRendSlash.ModifyHitNPC (cognitive 20) · ×1
  • CrimsonRendSlash.ModifyHitNPC (cognitive 20) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1451 — CrimsonRendSlash.ModifyHitNPC has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CrimsonSweepSlash.UpdateMeiOnBeatFired (cognitive 20) · ×1
  • CrimsonSweepSlash.UpdateMeiOnBeatFired (cognitive 20) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:572 — CrimsonSweepSlash.UpdateMeiOnBeatFired has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CrimsonSweepSlash.ModifyHitNPC (cognitive 20) · ×1
  • CrimsonSweepSlash.ModifyHitNPC (cognitive 20) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1168 — CrimsonSweepSlash.ModifyHitNPC has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniOmokage.Update (cognitive 20) · ×1
  • OniOmokage.Update (cognitive 20) Content/LegendWeapon/OnikiriLegend/OniOmokages/OniOmokage.cs:742 — OniOmokage.Update has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniSlash.UpdateMeiOnBeatFired (cognitive 20) · ×1
  • OniSlash.UpdateMeiOnBeatFired (cognitive 20) Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:725 — OniSlash.UpdateMeiOnBeatFired has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniSlash.ModifyHitNPC (cognitive 20) · ×1
  • OniSlash.ModifyHitNPC (cognitive 20) Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1360 — OniSlash.ModifyHitNPC has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SakuraSlashBaseProj.AI (cognitive 20) · ×1
  • SakuraSlashBaseProj.AI (cognitive 20) Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraSlashProj.cs:85 — SakuraSlashBaseProj.AI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniMeiUI.Draw (cognitive 20) · ×1
  • OniMeiUI.Draw (cognitive 20) Content/LegendWeapon/OnikiriLegend/UI/OniMeiUI.cs:1122 — OniMeiUI.Draw has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CyberBanish.ReadSnapshot (cognitive 20) · ×1
  • CyberBanish.ReadSnapshot (cognitive 20) Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBanish.Net.cs:240 — CyberBanish.ReadSnapshot has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CyberspaceRender.DrawFallbackTriLattice (cognitive 20) · ×1
  • CyberspaceRender.DrawFallbackTriLattice (cognitive 20) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspaceRender.cs:315 — CyberspaceRender.DrawFallbackTriLattice has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HypersonicBarrelModule.OnBeamAI (cognitive 20) · ×1
  • HypersonicBarrelModule.OnBeamAI (cognitive 20) Content/LegendWeapon/SHPCLegend/Modules/Barrel/HypersonicBarrelModule.cs:42 — HypersonicBarrelModule.OnBeamAI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MossboundBarrelModule.OnOrbFlyingAI (cognitive 20) · ×1
  • MossboundBarrelModule.OnOrbFlyingAI (cognitive 20) Content/LegendWeapon/SHPCLegend/Modules/Barrel/MossboundBarrelModule.cs:56 — MossboundBarrelModule.OnOrbFlyingAI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HarmonicFrameModule.OnBeamAI (cognitive 20) · ×1
  • HarmonicFrameModule.OnBeamAI (cognitive 20) Content/LegendWeapon/SHPCLegend/Modules/Frame/HarmonicFrameModule.cs:34 — HarmonicFrameModule.OnBeamAI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ShenyoGhostLakeScene.TickFigure (cognitive 20) · ×1
  • ShenyoGhostLakeScene.TickFigure (cognitive 20) Content/MainMenus/Shenyo/ShenyoGhostLakeScene.cs:229 — ShenyoGhostLakeScene.TickFigure has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BssCactusBallState.OnUpdate (cognitive 20) · ×1
  • BssCactusBallState.OnUpdate (cognitive 20) Content/NPCs/BloomsandSerpents/States/BssCactusBallState.cs:38 — BssCactusBallState.OnUpdate has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BrainPhaseTransitionState.OnUpdate (cognitive 20) · ×1
  • BrainPhaseTransitionState.OnUpdate (cognitive 20) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainPhaseTransitionState.cs:52 — BrainPhaseTransitionState.OnUpdate has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FishronGrabPlayer.PreUpdateMovement (cognitive 20) · ×1
  • FishronGrabPlayer.PreUpdateMovement (cognitive 20) Content/NPCs/BrutalNPCs/BrutalDukeFishron/FishronGrabCutscene.cs:114 — FishronGrabPlayer.PreUpdateMovement has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FishronStormChainDashState.OnUpdate (cognitive 20) · ×1
  • FishronStormChainDashState.OnUpdate (cognitive 20) Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronStormChainDashState.cs:43 — FishronStormChainDashState.OnUpdate has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EowBodyAI.AI (cognitive 20) · ×1
  • EowBodyAI.AI (cognitive 20) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/EowBodyAI.cs:97 — EowBodyAI.AI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EowGeyserRakeState.UpdateRake (cognitive 20) · ×1
  • EowGeyserRakeState.UpdateRake (cognitive 20) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowGeyserRakeState.cs:109 — EowGeyserRakeState.UpdateRake has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EmpressScorchPlayer.TryResolve (cognitive 20) · ×1
  • EmpressScorchPlayer.TryResolve (cognitive 20) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Core/EmpressScorch.cs:62 — EmpressScorchPlayer.TryResolve has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EmpressGrabPerformancePlayer.PostUpdate (cognitive 20) · ×1
  • EmpressGrabPerformancePlayer.PostUpdate (cognitive 20) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/EmpressGrabCutscene.cs:114 — EmpressGrabPerformancePlayer.PostUpdate has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EmpressScreenRender.EndCaptureDraw (cognitive 20) · ×1
  • EmpressScreenRender.EndCaptureDraw (cognitive 20) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Rendering/EmpressScreenRender.cs:15 — EmpressScreenRender.EndCaptureDraw has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EocFeintDashState.UpdateReel (cognitive 20) · ×1
  • EocFeintDashState.UpdateReel (cognitive 20) Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocFeintDashState.cs:122 — EocFeintDashState.UpdateReel has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GolemFreeHeadAI.UpdateMovement (cognitive 20) · ×1
  • GolemFreeHeadAI.UpdateMovement (cognitive 20) Content/NPCs/BrutalNPCs/BrutalGolem/GolemFreeHeadAI.cs:99 — GolemFreeHeadAI.UpdateMovement has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GolemTrapScoreState.OnUpdate (cognitive 20) · ×1
  • GolemTrapScoreState.OnUpdate (cognitive 20) Content/NPCs/BrutalNPCs/BrutalGolem/States/GolemTrapScoreState.cs:26 — GolemTrapScoreState.OnUpdate has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KingSlimeEngulfState.OnUpdate (cognitive 20) · ×1
  • KingSlimeEngulfState.OnUpdate (cognitive 20) Content/NPCs/BrutalNPCs/BrutalKingSlime/States/KingSlimeEngulfState.cs:94 — KingSlimeEngulfState.OnUpdate has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CultistPlanetAimLine.AI (cognitive 20) · ×1
  • CultistPlanetAimLine.AI (cognitive 20) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistPlanetAimLine.cs:57 — CultistPlanetAimLine.AI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CultistArcaneNovaState.OnUpdate (cognitive 20) · ×1
  • CultistArcaneNovaState.OnUpdate (cognitive 20) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistArcaneNovaState.cs:35 — CultistArcaneNovaState.OnUpdate has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CultistPlanetHurlState.OnUpdate (cognitive 20) · ×1
  • CultistPlanetHurlState.OnUpdate (cognitive 20) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistPlanetHurlState.cs:56 — CultistPlanetHurlState.OnUpdate has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CultistZodiacSealState.OnUpdate (cognitive 20) · ×1
  • CultistZodiacSealState.OnUpdate (cognitive 20) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistZodiacSealState.cs:35 — CultistZodiacSealState.OnUpdate has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TwinsPincerGrabState.UpdateFlameOrbit (cognitive 20) · ×1
  • TwinsPincerGrabState.UpdateFlameOrbit (cognitive 20) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsPincerGrabState.cs:671 — TwinsPincerGrabState.UpdateFlameOrbit has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SpazmatismSoloRageState.ExecuteFrenziedDash (cognitive 20) · ×1
  • SpazmatismSoloRageState.ExecuteFrenziedDash (cognitive 20) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismSoloRageState.cs:159 — SpazmatismSoloRageState.ExecuteFrenziedDash has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MLordDrawHelper.DrawHandAssembly (cognitive 20) · ×1
  • MLordDrawHelper.DrawHandAssembly (cognitive 20) Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordDrawHelper.cs:207 — MLordDrawHelper.DrawHandAssembly has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MLordMoonBiteState.RunClapServer (cognitive 20) · ×1
  • MLordMoonBiteState.RunClapServer (cognitive 20) Content/NPCs/BrutalNPCs/BrutalMoonLord/States/MLordMoonBiteState.cs:136 — MLordMoonBiteState.RunClapServer has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PlanteraVineLattice.AI (cognitive 20) · ×1
  • PlanteraVineLattice.AI (cognitive 20) Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraVineLattice.cs:66 — PlanteraVineLattice.AI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BrutalBeeAI.FormationBeeAI (cognitive 20) · ×1
  • BrutalBeeAI.FormationBeeAI (cognitive 20) Content/NPCs/BrutalNPCs/BrutalQueenBee/BrutalBeeAI.cs:45 — BrutalBeeAI.FormationBeeAI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · QBPhaseTransitionState.OnUpdate (cognitive 20) · ×1
  • QBPhaseTransitionState.OnUpdate (cognitive 20) Content/NPCs/BrutalNPCs/BrutalQueenBee/States/QBPhaseTransitionState.cs:35 — QBPhaseTransitionState.OnUpdate has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · QueenChandelierFallState.OnUpdate (cognitive 20) · ×1
  • QueenChandelierFallState.OnUpdate (cognitive 20) Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenChandelierFallState.cs:40 — QueenChandelierFallState.OnUpdate has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SkeletronStateBase.HoverMovement (cognitive 20) · ×1
  • SkeletronStateBase.HoverMovement (cognitive 20) Content/NPCs/BrutalNPCs/BrutalSkeletron/Core/ISkeletronState.cs:96 — SkeletronStateBase.HoverMovement has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PrimeStateBase.HoverMovement (cognitive 20) · ×1
  • PrimeStateBase.HoverMovement (cognitive 20) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Core/IPrimeState.cs:100 — PrimeStateBase.HoverMovement has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · WofGrabTongueProj.PreDraw (cognitive 20) · ×1
  • WofGrabTongueProj.PreDraw (cognitive 20) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofGrabTongueProj.cs:181 — WofGrabTongueProj.PreDraw has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · WofTongueGrabState.OnUpdate (cognitive 20) · ×1
  • WofTongueGrabState.OnUpdate (cognitive 20) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/States/WofTongueGrabState.cs:119 — WofTongueGrabState.OnUpdate has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · WallOfFleshAI.EvaluateGlobalTransitions (cognitive 20) · ×1
  • WallOfFleshAI.EvaluateGlobalTransitions (cognitive 20) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/WallOfFleshAI.cs:235 — WallOfFleshAI.EvaluateGlobalTransitions has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CrabulonCommandController.ScanCrabulons (cognitive 20) · ×1
  • CrabulonCommandController.ScanCrabulons (cognitive 20) Content/NPCs/Modifys/Crabulons/CrabulonUIs/CrabulonCommandUI.cs:74 — CrabulonCommandController.ScanCrabulons has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ScrapAutonomousTool.AI (cognitive 20) · ×1
  • ScrapAutonomousTool.AI (cognitive 20) Content/NPCs/ScrapCommanders/Projectiles/ScrapAutonomousTool.cs:47 — ScrapAutonomousTool.AI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SeaShrimpVoltBubble.AI (cognitive 20) · ×1
  • SeaShrimpVoltBubble.AI (cognitive 20) Content/NPCs/SeaShrimp/Projectiles/SeaShrimpVoltBubble.cs:83 — SeaShrimpVoltBubble.AI has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SeaShrimpVoltBubble.PreDraw (cognitive 20) · ×1
  • SeaShrimpVoltBubble.PreDraw (cognitive 20) Content/NPCs/SeaShrimp/Projectiles/SeaShrimpVoltBubble.cs:260 — SeaShrimpVoltBubble.PreDraw has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SeaShrimpCavitationPunchState.OnUpdate (cognitive 20) · ×1
  • SeaShrimpCavitationPunchState.OnUpdate (cognitive 20) Content/NPCs/SeaShrimp/States/SeaShrimpCavitationPunchState.cs:34 — SeaShrimpCavitationPunchState.OnUpdate has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ExploreFloatingIsland.CheckIsOnFloatingIsland (cognitive 20) · ×1
  • ExploreFloatingIsland.CheckIsOnFloatingIsland (cognitive 20) Content/QuestLogs/QLNodes/AdventurerQuests.cs:772 — ExploreFloatingIsland.CheckIsOnFloatingIsland has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FirstQuest.OnWorldEnter (cognitive 20) · ×1
  • FirstQuest.OnWorldEnter (cognitive 20) Content/QuestLogs/QLNodes/FirstQuest.cs:26 — FirstQuest.OnWorldEnter has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DraedonQuestLogStyle.DrawNode (cognitive 20) · ×1
  • DraedonQuestLogStyle.DrawNode (cognitive 20) Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:202 — DraedonQuestLogStyle.DrawNode has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ForestQuestLogStyle.DrawNode (cognitive 20) · ×1
  • ForestQuestLogStyle.DrawNode (cognitive 20) Content/QuestLogs/Styles/ForestQuestLogStyle.cs:176 — ForestQuestLogStyle.DrawNode has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · AmbientEmitters.EmitAir (cognitive 20) · ×1
  • AmbientEmitters.EmitAir (cognitive 20) Content/Scenarios/Dungeonworld/Ambience/AmbientEmitters.cs:262 — AmbientEmitters.EmitAir has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DungeonworldBossRecords.HandlePacket (cognitive 20) · ×1
  • DungeonworldBossRecords.HandlePacket (cognitive 20) Content/Scenarios/Dungeonworld/DungeonworldBossRecords.cs:140 — DungeonworldBossRecords.HandlePacket has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DungeonworldFogSim.Step (cognitive 20) · ×1
  • DungeonworldFogSim.Step (cognitive 20) Content/Scenarios/Dungeonworld/Fog/DungeonworldFogSim.cs:171 — DungeonworldFogSim.Step has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · InfillRooms.BuildRubble (cognitive 20) · ×1
  • InfillRooms.BuildRubble (cognitive 20) Content/Scenarios/Dungeonworld/Gen/Infill/InfillRooms.cs:178 — InfillRooms.BuildRubble has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · L3Palette.MoldBlotch (cognitive 20) · ×1
  • L3Palette.MoldBlotch (cognitive 20) Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Palette.cs:207 — L3Palette.MoldBlotch has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · L3Rooms.BuildReadingHall (cognitive 20) · ×1
  • L3Rooms.BuildReadingHall (cognitive 20) Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Rooms.cs:100 — L3Rooms.BuildReadingHall has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · L6Colossus.FindEntry (cognitive 20) · ×1
  • L6Colossus.FindEntry (cognitive 20) Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Colossus.cs:131 — L6Colossus.FindEntry has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · L6Colossus.BuildInterior (cognitive 20) · ×1
  • L6Colossus.BuildInterior (cognitive 20) Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Colossus.cs:253 — L6Colossus.BuildInterior has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · L6Content.RouteChain (cognitive 20) · ×1
  • L6Content.RouteChain (cognitive 20) Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Content.cs:345 — L6Content.RouteChain has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DeepGaolWraith.UpdateSwipe (cognitive 20) · ×1
  • DeepGaolWraith.UpdateSwipe (cognitive 20) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:842 — DeepGaolWraith.UpdateSwipe has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DeepGaolWraith.UpdateVolley (cognitive 20) · ×1
  • DeepGaolWraith.UpdateVolley (cognitive 20) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:979 — DeepGaolWraith.UpdateVolley has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DrownedTurnkey.UpdateLurk (cognitive 20) · ×1
  • DrownedTurnkey.UpdateLurk (cognitive 20) Content/Scenarios/Dungeonworld/NPCs/Elites/DrownedTurnkey.cs:360 — DrownedTurnkey.UpdateLurk has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Undrowned.UpdateWhirl (cognitive 20) · ×1
  • Undrowned.UpdateWhirl (cognitive 20) Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:1334 — Undrowned.UpdateWhirl has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FishoilQuestScenario.Tick (cognitive 20) · ×1
  • FishoilQuestScenario.Tick (cognitive 20) Content/Scenarios/Helen/Quest/FishoilQuest/FishoilQuestScenario.cs:74 — FishoilQuestScenario.Tick has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ToriiShrineActor.UpdatePullRite (cognitive 20) · ×1
  • ToriiShrineActor.UpdatePullRite (cognitive 20) Content/Scenarios/Himayo/ToriiShrines/ToriiShrineActor.cs:353 — ToriiShrineActor.UpdatePullRite has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KasaOniActor.TryFindStandableGround (cognitive 20) · ×1
  • KasaOniActor.TryFindStandableGround (cognitive 20) Content/Scenarios/Kiame/KasaOnis/KasaOniActor.cs:843 — KasaOniActor.TryFindStandableGround has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KiyumeMicroSites.ScatterDecor (cognitive 20) · ×1
  • KiyumeMicroSites.ScatterDecor (cognitive 20) Content/Scenarios/Kiyume/Gen/KiyumeMicroSites.cs:325 — KiyumeMicroSites.ScatterDecor has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OldNetICEDirector.SeedTurrets (cognitive 20) · ×1
  • OldNetICEDirector.SeedTurrets (cognitive 20) Content/Scenarios/OldNet/NPCs/OldNetICEDirector.cs:538 — OldNetICEDirector.SeedTurrets has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OldNetWardenICE.UpdateDash (cognitive 20) · ×1
  • OldNetWardenICE.UpdateDash (cognitive 20) Content/Scenarios/OldNet/NPCs/OldNetWardenICE.cs:353 — OldNetWardenICE.UpdateDash has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OldNetPlayer.PostUpdate (cognitive 20) · ×1
  • OldNetPlayer.PostUpdate (cognitive 20) Content/Scenarios/OldNet/OldNetPlayer.cs:557 — OldNetPlayer.PostUpdate has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OldNetTileFXRender.DrawBulkheadOverlay (cognitive 20) · ×1
  • OldNetTileFXRender.DrawBulkheadOverlay (cognitive 20) Content/Scenarios/OldNet/Renders/OldNetTileFXRender.cs:234 — OldNetTileFXRender.DrawBulkheadOverlay has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SylvanOutpost.SetChestItem (cognitive 20) · ×1
  • SylvanOutpost.SetChestItem (cognitive 20) Content/Structures/DatIO/SylvanOutpost.cs:650 — SylvanOutpost.SetChestItem has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EntityFreezeState.UpdateState (cognitive 20) · ×1
  • EntityFreezeState.UpdateState (cognitive 20) Content/TimeFreezes/TimeFreezeSystem.cs:394 — EntityFreezeState.UpdateState has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · WraithSynergy.EdgePair (cognitive 20) · ×1
  • WraithSynergy.EdgePair (cognitive 20) Content/Wraiths/Core/WraithSynergy.cs:121 — WraithSynergy.EdgePair has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ShadeSeizurePerformance.Update (cognitive 20) · ×1
  • ShadeSeizurePerformance.Update (cognitive 20) Content/Wraiths/Deaths/Performances/ShadeSeizurePerformance.cs:63 — ShadeSeizurePerformance.Update has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ExternalCallUtil.TryReadReward (cognitive 19) · ×1
  • ExternalCallUtil.TryReadReward (cognitive 19) API/ExternalCallUtil.cs:198 — ExternalCallUtil.TryReadReward has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CWRWorld.PostUpdateEverything (cognitive 19) · ×1
  • CWRWorld.PostUpdateEverything (cognitive 19) Content/CWRWorld.cs:96 — CWRWorld.PostUpdateEverything has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DuneStormScheduler.TryGustRound (cognitive 19) · ×1
  • DuneStormScheduler.TryGustRound (cognitive 19) Content/GameModes/BrutalMobs/Ambience/DuneStorm/DuneStormScheduler.cs:58 — DuneStormScheduler.TryGustRound has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FleshfenAmbience.UpdateMireBubbles (cognitive 19) · ×1
  • FleshfenAmbience.UpdateMireBubbles (cognitive 19) Content/GameModes/BrutalMobs/Ambience/Fleshfen/FleshfenAmbience.cs:303 — FleshfenAmbience.UpdateMireBubbles has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MireheartAmbience.PostUpdateEverything (cognitive 19) · ×1
  • MireheartAmbience.PostUpdateEverything (cognitive 19) Content/GameModes/BrutalMobs/Ambience/Mireheart/MireheartAmbience.cs:100 — MireheartAmbience.PostUpdateEverything has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · NyxdepthSinkColumnProj.AI (cognitive 19) · ×1
  • NyxdepthSinkColumnProj.AI (cognitive 19) Content/GameModes/BrutalMobs/Ambience/Nyxdepth/Projectiles/NyxdepthSinkColumnProj.cs:54 — NyxdepthSinkColumnProj.AI has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · RotmireMistRender.UpdateBySystem (cognitive 19) · ×1
  • RotmireMistRender.UpdateBySystem (cognitive 19) Content/GameModes/BrutalMobs/Ambience/Rotmire/RotmireMistRender.cs:58 — RotmireMistRender.UpdateBySystem has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SilkcryptAmbience.UpdateCocoonTwitch (cognitive 19) · ×1
  • SilkcryptAmbience.UpdateCocoonTwitch (cognitive 19) Content/GameModes/BrutalMobs/Ambience/Silkcrypt/SilkcryptAmbience.cs:226 — SilkcryptAmbience.UpdateCocoonTwitch has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SporeshineCapSwellProj.AI (cognitive 19) · ×1
  • SporeshineCapSwellProj.AI (cognitive 19) Content/GameModes/BrutalMobs/Ambience/Sporeshine/Projectiles/SporeshineCapSwellProj.cs:63 — SporeshineCapSwellProj.AI has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SporeshineAmbience.UpdateChorus (cognitive 19) · ×1
  • SporeshineAmbience.UpdateChorus (cognitive 19) Content/GameModes/BrutalMobs/Ambience/Sporeshine/SporeshineAmbience.cs:241 — SporeshineAmbience.UpdateChorus has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EclipseNPC.TickStrike (cognitive 19) · ×1
  • EclipseNPC.TickStrike (cognitive 19) Content/GameModes/BrutalMobs/Eclipse/EclipseNPC.cs:457 — EclipseNPC.TickStrike has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FrmSiegeNPC.StrafeActive (cognitive 19) · ×1
  • FrmSiegeNPC.StrafeActive (cognitive 19) Content/GameModes/BrutalMobs/FrostMoon/FrmSiegeNPC.cs:281 — FrmSiegeNPC.StrafeActive has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GraveyardBrutalNPC.PostAI (cognitive 19) · ×1
  • GraveyardBrutalNPC.PostAI (cognitive 19) Content/GameModes/BrutalMobs/Graveyard/GraveyardBrutalNPC.cs:215 — GraveyardBrutalNPC.PostAI has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · JungleHellNPC.FrenzyPresentTick (cognitive 19) · ×1
  • JungleHellNPC.FrenzyPresentTick (cognitive 19) Content/GameModes/BrutalMobs/JungleHell/JungleHellNPC.cs:459 — JungleHellNPC.FrenzyPresentTick has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · JhAmbushOmen.AI (cognitive 19) · ×1
  • JhAmbushOmen.AI (cognitive 19) Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhAmbushOmen.cs:61 — JhAmbushOmen.AI has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LegionNPC.SharkStep (cognitive 19) · ×1
  • LegionNPC.SharkStep (cognitive 19) Content/GameModes/BrutalMobs/Legion/LegionNPC.cs:1153 — LegionNPC.SharkStep has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OceanBrutalNPC.TickStrike (cognitive 19) · ×1
  • OceanBrutalNPC.TickStrike (cognitive 19) Content/GameModes/BrutalMobs/Ocean/OceanBrutalNPC.cs:633 — OceanBrutalNPC.TickStrike has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SandveilBounceMarkOmen.AI (cognitive 19) · ×1
  • SandveilBounceMarkOmen.AI (cognitive 19) Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilBounceMarkOmen.cs:65 — SandveilBounceMarkOmen.AI has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GodSmithScheme.ModifyTooltips (cognitive 19) · ×1
  • GodSmithScheme.ModifyTooltips (cognitive 19) Content/GameModes/GodSmith/Framework/GodSmithScheme.cs:363 — GodSmithScheme.ModifyTooltips has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GsHarpoon.OnBlockedUse (cognitive 19) · ×1
  • GsHarpoon.OnBlockedUse (cognitive 19) Content/GameModes/GodSmith/Weapons/Guns/GsHarpoon.cs:52 — GsHarpoon.OnBlockedUse has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GsMinisharkHeld.FireOnce (cognitive 19) · ×1
  • GsMinisharkHeld.FireOnce (cognitive 19) Content/GameModes/GodSmith/Weapons/Guns/GsMinishark.cs:256 — GsMinisharkHeld.FireOnce has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GsOnyxBlaster.GsProjOnKill (cognitive 19) · ×1
  • GsOnyxBlaster.GsProjOnKill (cognitive 19) Content/GameModes/GodSmith/Weapons/Guns/GsOnyxBlaster.cs:118 — GsOnyxBlaster.GsProjOnKill has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GsAquaScepter.ChantHoldItem (cognitive 19) · ×1
  • GsAquaScepter.ChantHoldItem (cognitive 19) Content/GameModes/GodSmith/Weapons/MagicChant/GsAquaScepter.cs:40 — GsAquaScepter.ChantHoldItem has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GsVampireKnives.GsCanUseItem (cognitive 19) · ×1
  • GsVampireKnives.GsCanUseItem (cognitive 19) Content/GameModes/GodSmith/Weapons/MeleeOddities/GsVampireKnives.cs:27 — GsVampireKnives.GsCanUseItem has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GsNorthPolePillarProj.AI (cognitive 19) · ×1
  • GsNorthPolePillarProj.AI (cognitive 19) Content/GameModes/GodSmith/Weapons/Spears/GsNorthPole.cs:279 — GsNorthPolePillarProj.AI has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GsLegionBannerProj.AI (cognitive 19) · ×1
  • GsLegionBannerProj.AI (cognitive 19) Content/GameModes/GodSmith/Weapons/SummonMinions/GsLegionBannerProj.cs:56 — GsLegionBannerProj.AI has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HackPanelRenderer.UpdateHover (cognitive 19) · ×1
  • HackPanelRenderer.UpdateHover (cognitive 19) Content/HackTimes/HackPanelRenderer.cs:221 — HackPanelRenderer.UpdateHover has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HackTimeTileCyberPass.RedrawTileRegion (cognitive 19) · ×1
  • HackTimeTileCyberPass.RedrawTileRegion (cognitive 19) Content/HackTimes/HackTimeTileCyberPass.cs:190 — HackTimeTileCyberPass.RedrawTileRegion has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HackTimeUI.UpdateClickSelection (cognitive 19) · ×1
  • HackTimeUI.UpdateClickSelection (cognitive 19) Content/HackTimes/HackTimeUI.cs:71 — HackTimeUI.UpdateClickSelection has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MirrorSurface.MirrorCrossings (cognitive 19) · ×1
  • MirrorSurface.MirrorCrossings (cognitive 19) Content/HackTimes/Protocols/MirrorSurface.cs:187 — MirrorSurface.MirrorCrossings has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · AutoCrafterUI.DrawStatusRow (cognitive 19) · ×1
  • AutoCrafterUI.DrawStatusRow (cognitive 19) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:551 — AutoCrafterUI.DrawStatusRow has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BottlingMachineStorageProvider.FindNearPosition (cognitive 19) · ×1
  • BottlingMachineStorageProvider.FindNearPosition (cognitive 19) Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineStorageProvider.cs:88 — BottlingMachineStorageProvider.FindNearPosition has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CrusherStorageProvider.FindNearPosition (cognitive 19) · ×1
  • CrusherStorageProvider.FindNearPosition (cognitive 19) Content/Industrials/ElectricPowers/Crushers/CrusherStorageProvider.cs:97 — CrusherStorageProvider.FindNearPosition has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CrusherTP.RightClickByTile (cognitive 19) · ×1
  • CrusherTP.RightClickByTile (cognitive 19) Content/Industrials/ElectricPowers/Crushers/CrusherTP.cs:424 — CrusherTP.RightClickByTile has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HealStationTP.UpdateTurret (cognitive 19) · ×1
  • HealStationTP.UpdateTurret (cognitive 19) Content/Industrials/ElectricPowers/HealingStations/HealStationTP.cs:52 — HealStationTP.UpdateTurret has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HerbFarmerTP.TryHarvest (cognitive 19) · ×1
  • HerbFarmerTP.TryHarvest (cognitive 19) Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerTP.cs:520 — HerbFarmerTP.TryHarvest has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · IncineratorStorageProvider.FindNearPosition (cognitive 19) · ×1
  • IncineratorStorageProvider.FindNearPosition (cognitive 19) Content/Industrials/ElectricPowers/Incinerators/IncineratorStorageProvider.cs:105 — IncineratorStorageProvider.FindNearPosition has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · IncineratorTP.RightClickByTile (cognitive 19) · ×1
  • IncineratorTP.RightClickByTile (cognitive 19) Content/Industrials/ElectricPowers/Incinerators/IncineratorTP.cs:312 — IncineratorTP.RightClickByTile has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MushroomFarmerTP.UpdateMachine (cognitive 19) · ×1
  • MushroomFarmerTP.UpdateMachine (cognitive 19) Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:265 — MushroomFarmerTP.UpdateMachine has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · RecyclerStorageProvider.FindNearPosition (cognitive 19) · ×1
  • RecyclerStorageProvider.FindNearPosition (cognitive 19) Content/Industrials/ElectricPowers/Recyclers/RecyclerStorageProvider.cs:93 — RecyclerStorageProvider.FindNearPosition has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ShieldGeneratorTP.UpdateDomeVisual (cognitive 19) · ×1
  • ShieldGeneratorTP.UpdateDomeVisual (cognitive 19) Content/Industrials/ElectricPowers/ShieldGenerators/ShieldGeneratorTP.cs:120 — ShieldGeneratorTP.UpdateDomeVisual has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ShimmerTransmuterStorageProvider.FindNearPosition (cognitive 19) · ×1
  • ShimmerTransmuterStorageProvider.FindNearPosition (cognitive 19) Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterStorageProvider.cs:94 — ShimmerTransmuterStorageProvider.FindNearPosition has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TreeRegrowth.PreDraw (cognitive 19) · ×1
  • TreeRegrowth.PreDraw (cognitive 19) Content/Industrials/ElectricPowers/TreeRegrowths/TreeRegrowth.cs:275 — TreeRegrowth.PreDraw has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TreeRegrowth.DrawTopFoliage (cognitive 19) · ×1
  • TreeRegrowth.DrawTopFoliage (cognitive 19) Content/Industrials/ElectricPowers/TreeRegrowths/TreeRegrowth.cs:379 — TreeRegrowth.DrawTopFoliage has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MawWormProj.DrawWormChain (cognitive 19) · ×1
  • MawWormProj.DrawWormChain (cognitive 19) Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawWormProj.cs:501 — MawWormProj.DrawWormChain has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · WingsOfInterferenceRender.DrawBeforePlayers (cognitive 19) · ×1
  • WingsOfInterferenceRender.DrawBeforePlayers (cognitive 19) Content/Items/Accessories/BrutalRelics/EmpressOfLight/InterferenceWingRender.cs:33 — WingsOfInterferenceRender.DrawBeforePlayers has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FallenCrownProj.AI (cognitive 19) · ×1
  • FallenCrownProj.AI (cognitive 19) Content/Items/Accessories/BrutalRelics/KingSlime/FallenCrownProj.cs:53 — FallenCrownProj.AI has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BlackFlashSigilPlayer.PreUpdateMovement (cognitive 19) · ×1
  • BlackFlashSigilPlayer.PreUpdateMovement (cognitive 19) Content/Items/Accessories/BrutalRelics/MoonLord/BlackFlashSigil.cs:149 — BlackFlashSigilPlayer.PreUpdateMovement has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SoulbindingGhostHand.AI (cognitive 19) · ×1
  • SoulbindingGhostHand.AI (cognitive 19) Content/Items/Accessories/BrutalRelics/Skeletron/SoulbindingGhostHand.cs:87 — SoulbindingGhostHand.AI has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SupernovaExplosion.AI (cognitive 19) · ×1
  • SupernovaExplosion.AI (cognitive 19) Content/Items/Accessories/EyeOfSingularity.cs:248 — SupernovaExplosion.AI has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ElysiumPlayer.UpdateEquips (cognitive 19) · ×1
  • ElysiumPlayer.UpdateEquips (cognitive 19) Content/Items/Magic/Elysiums/ElysiumPlayer.cs:477 — ElysiumPlayer.UpdateEquips has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PandemoniumChannel.PerformTieredAttack (cognitive 19) · ×1
  • PandemoniumChannel.PerformTieredAttack (cognitive 19) Content/Items/Magic/Pandemoniums/PandemoniumChannel.cs:529 — PandemoniumChannel.PerformTieredAttack has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ArbiterFlameRenderer.DrawSegment (cognitive 19) · ×1
  • ArbiterFlameRenderer.DrawSegment (cognitive 19) Content/Items/Melee/Arbiters/ArbiterFlameRenderer.cs:197 — ArbiterFlameRenderer.DrawSegment has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DawnshatterHeld.AI (cognitive 19) · ×1
  • DawnshatterHeld.AI (cognitive 19) Content/Items/Melee/DawnshatterAzures/DawnshatterHeld.cs:415 — DawnshatterHeld.AI has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DestroyersBladeEXHeld.OnHitNPC (cognitive 19) · ×1
  • DestroyersBladeEXHeld.OnHitNPC (cognitive 19) Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:566 — DestroyersBladeEXHeld.OnHitNPC has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HeartcarverDash.AI (cognitive 19) · ×1
  • HeartcarverDash.AI (cognitive 19) Content/Items/Melee/Heartcarver.cs:591 — HeartcarverDash.AI has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ShatterfangHeld.DrawBladeSet (cognitive 19) · ×1
  • ShatterfangHeld.DrawBladeSet (cognitive 19) Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:787 — ShatterfangHeld.DrawBladeSet has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · StormGoddess.UpdateFacingDirection (cognitive 19) · ×1
  • StormGoddess.UpdateFacingDirection (cognitive 19) Content/Items/Melee/StormGoddessSpears/StormGoddess.cs:457 — StormGoddess.UpdateFacingDirection has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HalibutResetNet.Receive (cognitive 19) · ×1
  • HalibutResetNet.Receive (cognitive 19) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutResetNet.cs:64 — HalibutResetNet.Receive has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BloodySwarmController.PreDraw (cognitive 19) · ×1
  • BloodySwarmController.PreDraw (cognitive 19) Content/LegendWeapon/HalibutLegend/FishSkills/FishBloodyManowar.cs:347 — BloodySwarmController.PreDraw has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DrizzleFishHolder.UpdateJetParticles (cognitive 19) · ×1
  • DrizzleFishHolder.UpdateJetParticles (cognitive 19) Content/LegendWeapon/HalibutLegend/FishSkills/FishDrizzle.cs:534 — DrizzleFishHolder.UpdateJetParticles has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DrizzleFishHolder.PreDraw (cognitive 19) · ×1
  • DrizzleFishHolder.PreDraw (cognitive 19) Content/LegendWeapon/HalibutLegend/FishSkills/FishDrizzle.cs:586 — DrizzleFishHolder.PreDraw has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · RockHammerFish.TriggerImpact (cognitive 19) · ×1
  • RockHammerFish.TriggerImpact (cognitive 19) Content/LegendWeapon/HalibutLegend/FishSkills/FishRock.cs:490 — RockHammerFish.TriggerImpact has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaHoundReflection.Draw (cognitive 19) · ×1
  • KikasaHoundReflection.Draw (cognitive 19) Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaHoundReflection.cs:57 — KikasaHoundReflection.Draw has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaDrownFX.DrawGlowLayer (cognitive 19) · ×1
  • KikasaDrownFX.DrawGlowLayer (cognitive 19) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:954 — KikasaDrownFX.DrawGlowLayer has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaRainRender.DrawOneInkTrail (cognitive 19) · ×1
  • KikasaRainRender.DrawOneInkTrail (cognitive 19) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:368 — KikasaRainRender.DrawOneInkTrail has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaResetHistory.Update (cognitive 19) · ×1
  • KikasaResetHistory.Update (cognitive 19) Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetHistory.cs:100 — KikasaResetHistory.Update has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaResetNet.Receive (cognitive 19) · ×1
  • KikasaResetNet.Receive (cognitive 19) Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetNet.cs:63 — KikasaResetNet.Receive has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaBowServant.UpdateVolley (cognitive 19) · ×1
  • KikasaBowServant.UpdateVolley (cognitive 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:459 — KikasaBowServant.UpdateVolley has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaBowServant.UpdateRain (cognitive 19) · ×1
  • KikasaBowServant.UpdateRain (cognitive 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:608 — KikasaBowServant.UpdateRain has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaGunBullet.AI (cognitive 19) · ×1
  • KikasaGunBullet.AI (cognitive 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunBullet.cs:76 — KikasaGunBullet.AI has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaGunServant.UpdateVolley (cognitive 19) · ×1
  • KikasaGunServant.UpdateVolley (cognitive 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:544 — KikasaGunServant.UpdateVolley has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaHalibutServant.UpdateDomainCast (cognitive 19) · ×1
  • KikasaHalibutServant.UpdateDomainCast (cognitive 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:638 — KikasaHalibutServant.UpdateDomainCast has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaOnikiriServant.UpdateGrand (cognitive 19) · ×1
  • KikasaOnikiriServant.UpdateGrand (cognitive 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:623 — KikasaOnikiriServant.UpdateGrand has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaZenithServant.UpdateStorm (cognitive 19) · ×1
  • KikasaZenithServant.UpdateStorm (cognitive 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:538 — KikasaZenithServant.UpdateStorm has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaCultistFireOrb.AI (cognitive 19) · ×1
  • KikasaCultistFireOrb.AI (cognitive 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistFireOrb.cs:64 — KikasaCultistFireOrb.AI has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaEmpressServant.DrawLayeredBody (cognitive 19) · ×1
  • KikasaEmpressServant.DrawLayeredBody (cognitive 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:927 — KikasaEmpressServant.DrawLayeredBody has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaEyeServant.UpdateVolley (cognitive 19) · ×1
  • KikasaEyeServant.UpdateVolley (cognitive 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:518 — KikasaEyeServant.UpdateVolley has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaFishronServant.DrawBody (cognitive 19) · ×1
  • KikasaFishronServant.DrawBody (cognitive 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1218 — KikasaFishronServant.DrawBody has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaMoonLordServant.DrawGlow (cognitive 19) · ×1
  • KikasaMoonLordServant.DrawGlow (cognitive 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1459 — KikasaMoonLordServant.DrawGlow has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaQueenSlimeServant.UpdateMines (cognitive 19) · ×1
  • KikasaQueenSlimeServant.UpdateMines (cognitive 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:514 — KikasaQueenSlimeServant.UpdateMines has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaSeaShrimpServant.UpdateFollow (cognitive 19) · ×1
  • KikasaSeaShrimpServant.UpdateFollow (cognitive 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:424 — KikasaSeaShrimpServant.UpdateFollow has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaWallOfFleshServant.UpdateFrames (cognitive 19) · ×1
  • KikasaWallOfFleshServant.UpdateFrames (cognitive 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:821 — KikasaWallOfFleshServant.UpdateFrames has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaTeleportProj.EruptBeat (cognitive 19) · ×1
  • KikasaTeleportProj.EruptBeat (cognitive 19) Content/LegendWeapon/KikasaLegend/KikasaTeleports/KikasaTeleportProj.cs:269 — KikasaTeleportProj.EruptBeat has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaWisp.Update (cognitive 19) · ×1
  • KikasaWisp.Update (cognitive 19) Content/LegendWeapon/KikasaLegend/KikasaWisps/KikasaWisp.cs:66 — KikasaWisp.Update has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KikasaHudLead.PollFallbackKey (cognitive 19) · ×1
  • KikasaHudLead.PollFallbackKey (cognitive 19) Content/LegendWeapon/KikasaLegend/UI/KikasaHudLeadInput.cs:80 — KikasaHudLead.PollFallbackKey has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CrimsonSweepSlash.OnHitNPC (cognitive 19) · ×1
  • CrimsonSweepSlash.OnHitNPC (cognitive 19) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1211 — CrimsonSweepSlash.OnHitNPC has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniMeiDeedProgress.Load (cognitive 19) · ×1
  • OniMeiDeedProgress.Load (cognitive 19) Content/LegendWeapon/OnikiriLegend/Inscriptions/Deeds/OniMeiDeedProgress.cs:104 — OniMeiDeedProgress.Load has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniDismemberRender.DrawNPCsOverTiles (cognitive 19) · ×1
  • OniDismemberRender.DrawNPCsOverTiles (cognitive 19) Content/LegendWeapon/OnikiriLegend/OniDismembers/OniDismemberRender.cs:30 — OniDismemberRender.DrawNPCsOverTiles has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniFinaleCut.DrawDetonateDressing (cognitive 19) · ×1
  • OniFinaleCut.DrawDetonateDressing (cognitive 19) Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleCut.cs:592 — OniFinaleCut.DrawDetonateDressing has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniOmokage.SegmentIntersectsRect (cognitive 19) · ×1
  • OniOmokage.SegmentIntersectsRect (cognitive 19) Content/LegendWeapon/OnikiriLegend/OniOmokages/OniOmokage.cs:985 — OniOmokage.SegmentIntersectsRect has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniSlash.Colliding (cognitive 19) · ×1
  • OniSlash.Colliding (cognitive 19) Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1279 — OniSlash.Colliding has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OnikiriPlayer.TryPetalPruneOnKill (cognitive 19) · ×1
  • OnikiriPlayer.TryPetalPruneOnKill (cognitive 19) Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs:2175 — OnikiriPlayer.TryPetalPruneOnKill has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SakuraKiriPlayerProj.AI (cognitive 19) · ×1
  • SakuraKiriPlayerProj.AI (cognitive 19) Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraKiriPlayerProj.cs:390 — SakuraKiriPlayerProj.AI has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SakuraSlashPetalBurst.Emit (cognitive 19) · ×1
  • SakuraSlashPetalBurst.Emit (cognitive 19) Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraSlashPetalBurst.cs:57 — SakuraSlashPetalBurst.Emit has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OniMeiUI.DrawTray (cognitive 19) · ×1
  • OniMeiUI.DrawTray (cognitive 19) Content/LegendWeapon/OnikiriLegend/UI/OniMeiUI.cs:1383 — OniMeiUI.DrawTray has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CyberspacePlayer.UpdateRemoteVisuals (cognitive 19) · ×1
  • CyberspacePlayer.UpdateRemoteVisuals (cognitive 19) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspacePlayer.cs:761 — CyberspacePlayer.UpdateRemoteVisuals has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CyberDomainFreeze.ReadSnapshot (cognitive 19) · ×1
  • CyberDomainFreeze.ReadSnapshot (cognitive 19) Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.Net.cs:882 — CyberDomainFreeze.ReadSnapshot has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SHPCCumulusNodeProj.AI (cognitive 19) · ×1
  • SHPCCumulusNodeProj.AI (cognitive 19) Content/LegendWeapon/SHPCLegend/Modules/Barrel/CumulusBarrelModule.cs:91 — SHPCCumulusNodeProj.AI has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SHPCMossPatchProj.BurstRoots (cognitive 19) · ×1
  • SHPCMossPatchProj.BurstRoots (cognitive 19) Content/LegendWeapon/SHPCLegend/Modules/Barrel/MossboundBarrelModule.cs:207 — SHPCMossPatchProj.BurstRoots has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SHPCHoloLatticeProj.CalibrateBeams (cognitive 19) · ×1
  • SHPCHoloLatticeProj.CalibrateBeams (cognitive 19) Content/LegendWeapon/SHPCLegend/Modules/Optic/HoloOpticModule.cs:134 — SHPCHoloLatticeProj.CalibrateBeams has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SHPCCapacitorBankProj.AI_Charging (cognitive 19) · ×1
  • SHPCCapacitorBankProj.AI_Charging (cognitive 19) Content/LegendWeapon/SHPCLegend/Modules/Power/CapacitorBankModule.cs:288 — SHPCCapacitorBankProj.AI_Charging has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SHPCCyberPanel.DrawRingSegment (cognitive 19) · ×1
  • SHPCCyberPanel.DrawRingSegment (cognitive 19) Content/LegendWeapon/SHPCLegend/UI/SHPCCyberPanel.cs:414 — SHPCCyberPanel.DrawRingSegment has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SHPCModPanel.DrawSlot (cognitive 19) · ×1
  • SHPCModPanel.DrawSlot (cognitive 19) Content/LegendWeapon/SHPCLegend/UI/SHPCModPanel.cs:297 — SHPCModPanel.DrawSlot has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SHPCModPanel.DrawPresetBar (cognitive 19) · ×1
  • SHPCModPanel.DrawPresetBar (cognitive 19) Content/LegendWeapon/SHPCLegend/UI/SHPCModPanel.cs:511 — SHPCModPanel.DrawPresetBar has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CharacterDockUI.DrawExpressionSwitch (cognitive 19) · ×1
  • CharacterDockUI.DrawExpressionSwitch (cognitive 19) Content/MainMenus/Characters/CharacterDockUI.cs:671 — CharacterDockUI.DrawExpressionSwitch has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BssNeedleRippleState.OnUpdate (cognitive 19) · ×1
  • BssNeedleRippleState.OnUpdate (cognitive 19) Content/NPCs/BloomsandSerpents/States/BssNeedleRippleState.cs:46 — BssNeedleRippleState.OnUpdate has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · BrainMindSeizePlayer.Drive (cognitive 19) · ×1
  • BrainMindSeizePlayer.Drive (cognitive 19) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Core/BrainMindSeizePlayer.cs:72 — BrainMindSeizePlayer.Drive has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DeerclopsAI.UpdateShadowShield (cognitive 19) · ×1
  • DeerclopsAI.UpdateShadowShield (cognitive 19) Content/NPCs/BrutalNPCs/BrutalDeerclops/DeerclopsAI.cs:200 — DeerclopsAI.UpdateShadowShield has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FishronSharkTornadoProj.AI (cognitive 19) · ×1
  • FishronSharkTornadoProj.AI (cognitive 19) Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronSharkTornadoProj.cs:96 — FishronSharkTornadoProj.AI has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FishronDiveBreachState.UpdateUnderwater (cognitive 19) · ×1
  • FishronDiveBreachState.UpdateUnderwater (cognitive 19) Content/NPCs/BrutalNPCs/BrutalDukeFishron/States/FishronDiveBreachState.cs:171 — FishronDiveBreachState.UpdateUnderwater has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EowMoltTransitionState.OnUpdate (cognitive 19) · ×1
  • EowMoltTransitionState.OnUpdate (cognitive 19) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowMoltTransitionState.cs:43 — EowMoltTransitionState.OnUpdate has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EmpressDashGrabState.DashUpdate (cognitive 19) · ×1
  • EmpressDashGrabState.DashUpdate (cognitive 19) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/States/EmpressDashGrabState.cs:147 — EmpressDashGrabState.DashUpdate has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EmpressDeathState.DissolveUpdate (cognitive 19) · ×1
  • EmpressDeathState.DissolveUpdate (cognitive 19) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/States/EmpressDeathState.cs:188 — EmpressDeathState.DissolveUpdate has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EocMawDragState.UpdateDrag (cognitive 19) · ×1
  • EocMawDragState.UpdateDrag (cognitive 19) Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocMawDragState.cs:441 — EocMawDragState.UpdateDrag has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KingSlimeDeathState.UpdateAgony (cognitive 19) · ×1
  • KingSlimeDeathState.UpdateAgony (cognitive 19) Content/NPCs/BrutalNPCs/BrutalKingSlime/States/KingSlimeDespawnState.cs:155 — KingSlimeDeathState.UpdateAgony has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CultistOrbitPath.AI (cognitive 19) · ×1
  • CultistOrbitPath.AI (cognitive 19) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistOrbitPath.cs:154 — CultistOrbitPath.AI has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CultistDeathState.OnUpdate (cognitive 19) · ×1
  • CultistDeathState.OnUpdate (cognitive 19) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistDeathState.cs:30 — CultistDeathState.OnUpdate has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TwinsCrossDashState.ExecuteDashPhase (cognitive 19) · ×1
  • TwinsCrossDashState.ExecuteDashPhase (cognitive 19) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsCrossDashState.cs:150 — TwinsCrossDashState.ExecuteDashPhase has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TwinsPincerGrabState.OnUpdate (cognitive 19) · ×1
  • TwinsPincerGrabState.OnUpdate (cognitive 19) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsPincerGrabState.cs:168 — TwinsPincerGrabState.OnUpdate has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TwinsTetherSweepState.ExecuteSweepPhase (cognitive 19) · ×1
  • TwinsTetherSweepState.ExecuteSweepPhase (cognitive 19) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsTetherSweepState.cs:127 — TwinsTetherSweepState.ExecuteSweepPhase has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · RetinazerLaserMatrixState.ExecuteChargePhase (cognitive 19) · ×1
  • RetinazerLaserMatrixState.ExecuteChargePhase (cognitive 19) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerLaserMatrixState.cs:149 — RetinazerLaserMatrixState.ExecuteChargePhase has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · RetinazerLaserMatrixState.ExecuteFirePhase (cognitive 19) · ×1
  • RetinazerLaserMatrixState.ExecuteFirePhase (cognitive 19) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerLaserMatrixState.cs:196 — RetinazerLaserMatrixState.ExecuteFirePhase has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TwinsAIController.CheckSoloRageMode (cognitive 19) · ×1
  • TwinsAIController.CheckSoloRageMode (cognitive 19) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/TwinsAIController.cs:323 — TwinsAIController.CheckSoloRageMode has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TwinsGrabPerformancePlayer.PostUpdate (cognitive 19) · ×1
  • TwinsGrabPerformancePlayer.PostUpdate (cognitive 19) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/TwinsGrabPerformancePlayer.cs:61 — TwinsGrabPerformancePlayer.PostUpdate has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MoonLordLeechBlobAI.DistributeHeal (cognitive 19) · ×1
  • MoonLordLeechBlobAI.DistributeHeal (cognitive 19) Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordLeechBlobAI.cs:85 — MoonLordLeechBlobAI.DistributeHeal has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MLordAnnihilationRayProj.AI (cognitive 19) · ×1
  • MLordAnnihilationRayProj.AI (cognitive 19) Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordAnnihilationRayProj.cs:173 — MLordAnnihilationRayProj.AI has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MLordEyeLinkProj.AI (cognitive 19) · ×1
  • MLordEyeLinkProj.AI (cognitive 19) Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordEyeLinkProj.cs:49 — MLordEyeLinkProj.AI has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MLordCrescentCloseState.FireArcs (cognitive 19) · ×1
  • MLordCrescentCloseState.FireArcs (cognitive 19) Content/NPCs/BrutalNPCs/BrutalMoonLord/States/MLordCrescentCloseState.cs:201 — MLordCrescentCloseState.FireArcs has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MLordPartBreakState.OnUpdate (cognitive 19) · ×1
  • MLordPartBreakState.OnUpdate (cognitive 19) Content/NPCs/BrutalNPCs/BrutalMoonLord/States/MLordPartBreakState.cs:43 — MLordPartBreakState.OnUpdate has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · QBWaxTurretState.OnUpdate (cognitive 19) · ×1
  • QBWaxTurretState.OnUpdate (cognitive 19) Content/NPCs/BrutalNPCs/BrutalQueenBee/States/QBWaxTurretState.cs:34 — QBWaxTurretState.OnUpdate has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · WofRotBeamProj.AI (cognitive 19) · ×1
  • WofRotBeamProj.AI (cognitive 19) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofRotBeamProj.cs:50 — WofRotBeamProj.AI has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · WofRotEyeBudProj.AI (cognitive 19) · ×1
  • WofRotEyeBudProj.AI (cognitive 19) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofRotEyeBudProj.cs:61 — WofRotEyeBudProj.AI has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FssBreachFountState.UpdateAirborne (cognitive 19) · ×1
  • FssBreachFountState.UpdateAirborne (cognitive 19) Content/NPCs/FestersandSerpents/States/FssBreachFountState.cs:169 — FssBreachFountState.UpdateAirborne has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FssCoilCascadeState.UpdateCircle (cognitive 19) · ×1
  • FssCoilCascadeState.UpdateCircle (cognitive 19) Content/NPCs/FestersandSerpents/States/FssCoilCascadeState.cs:169 — FssCoilCascadeState.UpdateCircle has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ScrapCommander.UpdateArms (cognitive 19) · ×1
  • ScrapCommander.UpdateArms (cognitive 19) Content/NPCs/ScrapCommanders/ScrapCommander.cs:484 — ScrapCommander.UpdateArms has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ScrapLegionProbe.AI (cognitive 19) · ×1
  • ScrapLegionProbe.AI (cognitive 19) Content/NPCs/ScrapCommanders/ScrapLegionProbe.cs:57 — ScrapLegionProbe.AI has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ScrapSiegeScreen.PostUpdateEverything (cognitive 19) · ×1
  • ScrapSiegeScreen.PostUpdateEverything (cognitive 19) Content/NPCs/ScrapCommanders/ScrapSiegeScreen.cs:55 — ScrapSiegeScreen.PostUpdateEverything has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ShrimpSkeleton.SolveArms (cognitive 19) · ×1
  • ShrimpSkeleton.SolveArms (cognitive 19) Content/NPCs/SeaShrimp/Kinematics/ShrimpSkeleton.cs:182 — ShrimpSkeleton.SolveArms has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SeaShrimpAbyssScreen.PostUpdateEverything (cognitive 19) · ×1
  • SeaShrimpAbyssScreen.PostUpdateEverything (cognitive 19) Content/NPCs/SeaShrimp/Rendering/SeaShrimpAbyssScreen.cs:54 — SeaShrimpAbyssScreen.PostUpdateEverything has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SeaShrimpCrystalSpikesState.OnUpdate (cognitive 19) · ×1
  • SeaShrimpCrystalSpikesState.OnUpdate (cognitive 19) Content/NPCs/SeaShrimp/States/SeaShrimpCrystalSpikesState.cs:34 — SeaShrimpCrystalSpikesState.OnUpdate has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TBUG.AI (cognitive 19) · ×1
  • TBUG.AI (cognitive 19) Content/NPCs/TBUGs/TBUG.cs:225 — TBUG.AI has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TBUGRiftSpawner.TryFindSpawnPoint (cognitive 19) · ×1
  • TBUGRiftSpawner.TryFindSpawnPoint (cognitive 19) Content/NPCs/TBUGs/TBUGRiftSpawner.cs:117 — TBUGRiftSpawner.TryFindSpawnPoint has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Victor.AI (cognitive 19) · ×1
  • Victor.AI (cognitive 19) Content/NPCs/Victors/Victor.cs:314 — Victor.AI has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · VictorPortalSpawner.TryFindSpawnPoint (cognitive 19) · ×1
  • VictorPortalSpawner.TryFindSpawnPoint (cognitive 19) Content/NPCs/Victors/VictorPortalSpawner.cs:138 — VictorPortalSpawner.TryFindSpawnPoint has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · QuestBookGuidePlayer.Tick (cognitive 19) · ×1
  • QuestBookGuidePlayer.Tick (cognitive 19) Content/QuestLogs/Guide/QuestBookGuidePlayer.cs:124 — QuestBookGuidePlayer.Tick has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · QuestLog.UpdateCanvas (cognitive 19) · ×1
  • QuestLog.UpdateCanvas (cognitive 19) Content/QuestLogs/QuestLog.cs:655 — QuestLog.UpdateCanvas has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ChroniclePen.InkRoute (cognitive 19) · ×1
  • ChroniclePen.InkRoute (cognitive 19) Content/QuestLogs/Styles/Chronicle/ChroniclePen.cs:503 — ChroniclePen.InkRoute has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ChronicleQuestLogStyle.DrawStationTabs (cognitive 19) · ×1
  • ChronicleQuestLogStyle.DrawStationTabs (cognitive 19) Content/QuestLogs/Styles/Chronicle/ChronicleQuestLogStyle.cs:120 — ChronicleQuestLogStyle.DrawStationTabs has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · RamNet.HandleUpgradeRequest (cognitive 19) · ×1
  • RamNet.HandleUpgradeRequest (cognitive 19) Content/RAMSystems/RamNet.cs:276 — RamNet.HandleUpgradeRequest has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CQETConstructorTP.Update (cognitive 19) · ×1
  • CQETConstructorTP.Update (cognitive 19) Content/Scenarios/Draedon/Quest/DeploySignaltowers/CQETConstructor.cs:159 — CQETConstructorTP.Update has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · AmbientEmitters.EmitCeiling (cognitive 19) · ×1
  • AmbientEmitters.EmitCeiling (cognitive 19) Content/Scenarios/Dungeonworld/Ambience/AmbientEmitters.cs:317 — AmbientEmitters.EmitCeiling has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · L3MazeBlock.Roll (cognitive 19) · ×1
  • L3MazeBlock.Roll (cognitive 19) Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3MazeBlock.cs:50 — L3MazeBlock.Roll has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GaolDormantSkull.UpdateActivate (cognitive 19) · ×1
  • GaolDormantSkull.UpdateActivate (cognitive 19) Content/Scenarios/Dungeonworld/NPCs/GaolDormantSkull.cs:125 — GaolDormantSkull.UpdateActivate has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KiameGateSpawn.TryEvaluateColumn (cognitive 19) · ×1
  • KiameGateSpawn.TryEvaluateColumn (cognitive 19) Content/Scenarios/Kiame/Gate/KiameGateSpawn.cs:311 — KiameGateSpawn.TryEvaluateColumn has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KiameRuins.BuildRoof (cognitive 19) · ×1
  • KiameRuins.BuildRoof (cognitive 19) Content/Scenarios/Kiame/Gen/KiameRuins.cs:175 — KiameRuins.BuildRoof has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KiyumeCrowFlight.Advance (cognitive 19) · ×1
  • KiyumeCrowFlight.Advance (cognitive 19) Content/Scenarios/Kiyume/Ambience/KiyumeCrowFlight.cs:212 — KiyumeCrowFlight.Advance has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KiyumeMicroSites.BuildGraveyard (cognitive 19) · ×1
  • KiyumeMicroSites.BuildGraveyard (cognitive 19) Content/Scenarios/Kiyume/Gen/KiyumeMicroSites.cs:202 — KiyumeMicroSites.BuildGraveyard has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · KiyumeStealthSense.SoundExposure (cognitive 19) · ×1
  • KiyumeStealthSense.SoundExposure (cognitive 19) Content/Scenarios/Kiyume/Stealth/KiyumeStealthSense.cs:175 — KiyumeStealthSense.SoundExposure has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OldNetScatterPass.ScatterEventNodes (cognitive 19) · ×1
  • OldNetScatterPass.ScatterEventNodes (cognitive 19) Content/Scenarios/OldNet/Gen/Passes/OldNetScatterPass.cs:138 — OldNetScatterPass.ScatterEventNodes has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OldNetValidatePass.AuditWalls (cognitive 19) · ×1
  • OldNetValidatePass.AuditWalls (cognitive 19) Content/Scenarios/OldNet/Gen/Passes/OldNetValidatePass.cs:213 — OldNetValidatePass.AuditWalls has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OldNetThreatField.ScanProjectiles (cognitive 19) · ×1
  • OldNetThreatField.ScanProjectiles (cognitive 19) Content/Scenarios/OldNet/NPCs/OldNetThreatField.cs:248 — OldNetThreatField.ScanProjectiles has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OldNetWardenICE.UpdateDeathArc (cognitive 19) · ×1
  • OldNetWardenICE.UpdateDeathArc (cognitive 19) Content/Scenarios/OldNet/NPCs/OldNetWardenICE.cs:706 — OldNetWardenICE.UpdateDeathArc has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OldNetCipherPanel.CashOut (cognitive 19) · ×1
  • OldNetCipherPanel.CashOut (cognitive 19) Content/Scenarios/OldNet/UI/OldNetCipherPanel.cs:337 — OldNetCipherPanel.CashOut has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OldNetGuideLead.UpdateUI (cognitive 19) · ×1
  • OldNetGuideLead.UpdateUI (cognitive 19) Content/Scenarios/OldNet/UI/OldNetGuideLead.cs:123 — OldNetGuideLead.UpdateUI has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SubworldMapGrid.Upkeep (cognitive 19) · ×1
  • SubworldMapGrid.Upkeep (cognitive 19) Content/Scenarios/SubworldMapGrid.cs:59 — SubworldMapGrid.Upkeep has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TimeControlReplicationSystem.NetReceive (cognitive 19) · ×1
  • TimeControlReplicationSystem.NetReceive (cognitive 19) Content/TimeFreezes/TimeControlReplicationSystem.cs:144 — TimeControlReplicationSystem.NetReceive has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TimeFreezeSystem.EndWorldFreeze (cognitive 19) · ×1
  • TimeFreezeSystem.EndWorldFreeze (cognitive 19) Content/TimeFreezes/TimeFreezeSystem.cs:1023 — TimeFreezeSystem.EndWorldFreeze has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · WraithCovenBurst.TryBurst (cognitive 19) · ×1
  • WraithCovenBurst.TryBurst (cognitive 19) Content/Wraiths/Marks/WraithCovenBurst.cs:23 — WraithCovenBurst.TryBurst has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EntrustStatusEntry.DrawStatusOverlay (cognitive 18) · ×1
  • EntrustStatusEntry.DrawStatusOverlay (cognitive 18) Content/EntrustManager/EntrustStatusEntry.cs:337 — EntrustStatusEntry.DrawStatusOverlay 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.
D2 · Cognitive Complexity · EntrustTrackerWidget.Draw (cognitive 18) · ×1
  • EntrustTrackerWidget.Draw (cognitive 18) Content/EntrustManager/EntrustTrackerWidget.cs:314 — EntrustTrackerWidget.Draw 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.
D2 · Cognitive Complexity · ChronicleManagerStyle.DrawQuestEntry (cognitive 18) · ×1
  • ChronicleManagerStyle.DrawQuestEntry (cognitive 18) Content/EntrustManager/Styles/ChronicleManagerStyle.cs:142 — ChronicleManagerStyle.DrawQuestEntry 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.
D2 · Cognitive Complexity · AetherglimAmbience.UpdateBubbleDirector (cognitive 18) · ×1
  • AetherglimAmbience.UpdateBubbleDirector (cognitive 18) Content/GameModes/BrutalMobs/Ambience/Aetherglim/AetherglimAmbience.cs:208 — AetherglimAmbience.UpdateBubbleDirector 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.
D2 · Cognitive Complexity · AshreignAshStormProj.PreDraw (cognitive 18) · ×1
  • AshreignAshStormProj.PreDraw (cognitive 18) Content/GameModes/BrutalMobs/Ambience/Ashreign/Projectiles/AshreignAshStormProj.cs:108 — AshreignAshStormProj.PreDraw 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.
D2 · Cognitive Complexity · AstralveilSpearMarkProj.AI (cognitive 18) · ×1
  • AstralveilSpearMarkProj.AI (cognitive 18) Content/GameModes/BrutalMobs/Ambience/Astralveil/Projectiles/AstralveilSpearMarkProj.cs:71 — AstralveilSpearMarkProj.AI 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.
D2 · Cognitive Complexity · DuneStormPlayer.PostUpdateMiscEffects (cognitive 18) · ×1
  • DuneStormPlayer.PostUpdateMiscEffects (cognitive 18) Content/GameModes/BrutalMobs/Ambience/DuneStorm/DuneStormPlayer.cs:34 — DuneStormPlayer.PostUpdateMiscEffects 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.
D2 · Cognitive Complexity · LumindepthCrystalChime.ScanAround (cognitive 18) · ×1
  • LumindepthCrystalChime.ScanAround (cognitive 18) Content/GameModes/BrutalMobs/Ambience/Lumindepth/LumindepthCrystalChime.cs:76 — LumindepthCrystalChime.ScanAround 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.
D2 · Cognitive Complexity · MireheartPlayer.TrySampleMudWaterSpot (cognitive 18) · ×1
  • MireheartPlayer.TrySampleMudWaterSpot (cognitive 18) Content/GameModes/BrutalMobs/Ambience/Mireheart/MireheartPlayer.cs:216 — MireheartPlayer.TrySampleMudWaterSpot 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.
D2 · Cognitive Complexity · MireheartTempleRender.TryBuildChain (cognitive 18) · ×1
  • MireheartTempleRender.TryBuildChain (cognitive 18) Content/GameModes/BrutalMobs/Ambience/Mireheart/MireheartTempleGlyphs.cs:141 — MireheartTempleRender.TryBuildChain 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.
D2 · Cognitive Complexity · StratosAmbienceSystem.UpdateSchedulers (cognitive 18) · ×1
  • StratosAmbienceSystem.UpdateSchedulers (cognitive 18) Content/GameModes/BrutalMobs/Ambience/Stratos/StratosAmbience.cs:109 — StratosAmbienceSystem.UpdateSchedulers 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.
D2 · Cognitive Complexity · VerdantThornRingProj.AI (cognitive 18) · ×1
  • VerdantThornRingProj.AI (cognitive 18) Content/GameModes/BrutalMobs/Ambience/Verdant/Projectiles/VerdantThornRingProj.cs:105 — VerdantThornRingProj.AI 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.
D2 · Cognitive Complexity · VerdantAmbience.UpdateAccents (cognitive 18) · ×1
  • VerdantAmbience.UpdateAccents (cognitive 18) Content/GameModes/BrutalMobs/Ambience/Verdant/VerdantAmbience.cs:166 — VerdantAmbience.UpdateAccents 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.
D2 · Cognitive Complexity · DdChargeOmen.AI (cognitive 18) · ×1
  • DdChargeOmen.AI (cognitive 18) Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdChargeOmen.cs:150 — DdChargeOmen.AI 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.
D2 · Cognitive Complexity · EclBloodMarkProj.AI (cognitive 18) · ×1
  • EclBloodMarkProj.AI (cognitive 18) Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclBloodMarkProj.cs:69 — EclBloodMarkProj.AI 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.
D2 · Cognitive Complexity · FlgMortarRingOmen.PreDraw (cognitive 18) · ×1
  • FlgMortarRingOmen.PreDraw (cognitive 18) Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarRingOmen.cs:141 — FlgMortarRingOmen.PreDraw 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.
D2 · Cognitive Complexity · LegionNPC.TideStep (cognitive 18) · ×1
  • LegionNPC.TideStep (cognitive 18) Content/GameModes/BrutalMobs/Legion/LegionNPC.cs:561 — LegionNPC.TideStep 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.
D2 · Cognitive Complexity · LegionInkOmen.AI (cognitive 18) · ×1
  • LegionInkOmen.AI (cognitive 18) Content/GameModes/BrutalMobs/Legion/Projectiles/LegionInkOmen.cs:72 — LegionInkOmen.AI 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.
D2 · Cognitive Complexity · PrtBroadsideOmen.AI (cognitive 18) · ×1
  • PrtBroadsideOmen.AI (cognitive 18) Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtBroadsideOmen.cs:91 — PrtBroadsideOmen.AI 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.
D2 · Cognitive Complexity · PumpkinMoonNPC.TickChargeTelegraph (cognitive 18) · ×1
  • PumpkinMoonNPC.TickChargeTelegraph (cognitive 18) Content/GameModes/BrutalMobs/PumpkinMoon/PumpkinMoonNPC.cs:715 — PumpkinMoonNPC.TickChargeTelegraph 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.
D2 · Cognitive Complexity · StonebornDiveLane.AI (cognitive 18) · ×1
  • StonebornDiveLane.AI (cognitive 18) Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornDiveLane.cs:62 — StonebornDiveLane.AI 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.
D2 · Cognitive Complexity · GameModeRenderer.DrawLockSeal (cognitive 18) · ×1
  • GameModeRenderer.DrawLockSeal (cognitive 18) Content/GameModes/UI/GameModeRenderer.cs:202 — GameModeRenderer.DrawLockSeal 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.
D2 · Cognitive Complexity · HackEffectNPC.RedirectAI (cognitive 18) · ×1
  • HackEffectNPC.RedirectAI (cognitive 18) Content/HackTimes/HackEffectNPC.cs:88 — HackEffectNPC.RedirectAI 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.
D2 · Cognitive Complexity · MirrorSurface.TryComputeMirrorLine (cognitive 18) · ×1
  • MirrorSurface.TryComputeMirrorLine (cognitive 18) Content/HackTimes/Protocols/MirrorSurface.cs:119 — MirrorSurface.TryComputeMirrorLine 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.
D2 · Cognitive Complexity · PressureSurge.LaunchEntities (cognitive 18) · ×1
  • PressureSurge.LaunchEntities (cognitive 18) Content/HackTimes/Protocols/PressureSurge.cs:92 — PressureSurge.LaunchEntities 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.
D2 · Cognitive Complexity · TileDetonate.OnApply (cognitive 18) · ×1
  • TileDetonate.OnApply (cognitive 18) Content/HackTimes/Protocols/TileDetonate.cs:106 — TileDetonate.OnApply 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.
D2 · Cognitive Complexity · PlayerHackMirror.ApplyStateSnapshot (cognitive 18) · ×1
  • PlayerHackMirror.ApplyStateSnapshot (cognitive 18) Content/HackTimes/PvP/PlayerHackNet.cs:686 — PlayerHackMirror.ApplyStateSnapshot 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.
D2 · Cognitive Complexity · TeleportStationUI.DrawStationList (cognitive 18) · ×1
  • TeleportStationUI.DrawStationList (cognitive 18) Content/Industrials/ElectricPowers/TeleportStations/TeleportStationUI.cs:435 — TeleportStationUI.DrawStationList 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.
D2 · Cognitive Complexity · ThrowerUI.HandleButtonClicks (cognitive 18) · ×1
  • ThrowerUI.HandleButtonClicks (cognitive 18) Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:264 — ThrowerUI.HandleButtonClicks 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.
D2 · Cognitive Complexity · MagmaThermalGeneratorTP.GeneratorUpdate (cognitive 18) · ×1
  • MagmaThermalGeneratorTP.GeneratorUpdate (cognitive 18) Content/Industrials/Generator/MagmaThermal/MagmaThermalGenerator.cs:165 — MagmaThermalGeneratorTP.GeneratorUpdate 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.
D2 · Cognitive Complexity · RiteMirrorPhantom.AI (cognitive 18) · ×1
  • RiteMirrorPhantom.AI (cognitive 18) Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMirrorPhantom.cs:44 — RiteMirrorPhantom.AI 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.
D2 · Cognitive Complexity · RiteStarCore.AI (cognitive 18) · ×1
  • RiteStarCore.AI (cognitive 18) Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteStarSurge.cs:58 — RiteStarCore.AI 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.
D2 · Cognitive Complexity · BloomNovaRender.DrawStandbyFeetVines (cognitive 18) · ×1
  • BloomNovaRender.DrawStandbyFeetVines (cognitive 18) Content/Items/Accessories/BrutalRelics/Plantera/BloomNovaRender.cs:145 — BloomNovaRender.DrawStandbyFeetVines 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.
D2 · Cognitive Complexity · EyeOfSingularityPlayer.PostUpdateMiscEffects (cognitive 18) · ×1
  • EyeOfSingularityPlayer.PostUpdateMiscEffects (cognitive 18) Content/Items/Accessories/EyeOfSingularity.cs:463 — EyeOfSingularityPlayer.PostUpdateMiscEffects 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.
D2 · Cognitive Complexity · AbyssrendHeld.OnHitNPC (cognitive 18) · ×1
  • AbyssrendHeld.OnHitNPC (cognitive 18) Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:558 — AbyssrendHeld.OnHitNPC 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.
D2 · Cognitive Complexity · ArbiterFireSnake.FindStandableGroundY (cognitive 18) · ×1
  • ArbiterFireSnake.FindStandableGroundY (cognitive 18) Content/Items/Melee/Arbiters/Arbiter.cs:725 — ArbiterFireSnake.FindStandableGroundY 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.
D2 · Cognitive Complexity · CloudwalkingSkyLootSystem.PlaceInChest (cognitive 18) · ×1
  • CloudwalkingSkyLootSystem.PlaceInChest (cognitive 18) Content/Items/Melee/Cloudwalking.cs:496 — CloudwalkingSkyLootSystem.PlaceInChest 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.
D2 · Cognitive Complexity · DawnshatterDash.ReleaseDash (cognitive 18) · ×1
  • DawnshatterDash.ReleaseDash (cognitive 18) Content/Items/Melee/DawnshatterAzures/DawnshatterDash.cs:167 — DawnshatterDash.ReleaseDash 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.
D2 · Cognitive Complexity · DragonSoulSerpent.AI (cognitive 18) · ×1
  • DragonSoulSerpent.AI (cognitive 18) Content/Items/Melee/DragonsScaleGreatsword.cs:728 — DragonSoulSerpent.AI 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.
D2 · Cognitive Complexity · HeartcarverHeld.OnCarveHit (cognitive 18) · ×1
  • HeartcarverHeld.OnCarveHit (cognitive 18) Content/Items/Melee/Heartcarver.cs:359 — HeartcarverHeld.OnCarveHit 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.
D2 · Cognitive Complexity · NeutronGlaiveHeld.HandleParticles (cognitive 18) · ×1
  • NeutronGlaiveHeld.HandleParticles (cognitive 18) Content/Items/Melee/NeutronGlaive.cs:408 — NeutronGlaiveHeld.HandleParticles 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.
D2 · Cognitive Complexity · EXNeutronExplode.AI (cognitive 18) · ×1
  • EXNeutronExplode.AI (cognitive 18) Content/Items/Melee/NeutronGlaive.cs:1317 — EXNeutronExplode.AI 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.
D2 · Cognitive Complexity · OniHandMinion.WindupBehavior (cognitive 18) · ×1
  • OniHandMinion.WindupBehavior (cognitive 18) Content/Items/Melee/OniMacheteHands.cs:472 — OniHandMinion.WindupBehavior 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.
D2 · Cognitive Complexity · ShatterfangHeld.OnHitNPC (cognitive 18) · ×1
  • ShatterfangHeld.OnHitNPC (cognitive 18) Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:624 — ShatterfangHeld.OnHitNPC 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.
D2 · Cognitive Complexity · StarshipHeld.AI (cognitive 18) · ×1
  • StarshipHeld.AI (cognitive 18) Content/Items/Ranged/Starships/StarshipHeld.cs:84 — StarshipHeld.AI 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.
D2 · Cognitive Complexity · FishTeleportProj.AI (cognitive 18) · ×1
  • FishTeleportProj.AI (cognitive 18) Content/LegendWeapon/HalibutLegend/DomainSkills/FishTeleport.cs:219 — FishTeleportProj.AI 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.
D2 · Cognitive Complexity · DirtBall.AI (cognitive 18) · ×1
  • DirtBall.AI (cognitive 18) Content/LegendWeapon/HalibutLegend/FishSkills/FishDirt.cs:660 — DirtBall.AI 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.
D2 · Cognitive Complexity · SlimeGelOrb.FloatingPhaseAI (cognitive 18) · ×1
  • SlimeGelOrb.FloatingPhaseAI (cognitive 18) Content/LegendWeapon/HalibutLegend/FishSkills/FishSlime.cs:308 — SlimeGelOrb.FloatingPhaseAI 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.
D2 · Cognitive Complexity · TunabeardDashProj.ControlFrame (cognitive 18) · ×1
  • TunabeardDashProj.ControlFrame (cognitive 18) Content/LegendWeapon/HalibutLegend/FishSkills/FishTunabeard.cs:173 — TunabeardDashProj.ControlFrame 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.
D2 · Cognitive Complexity · KikasaDomainPlayer.UpdateRainCurtain (cognitive 18) · ×1
  • KikasaDomainPlayer.UpdateRainCurtain (cognitive 18) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainPlayer.cs:1368 — KikasaDomainPlayer.UpdateRainCurtain 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.
D2 · Cognitive Complexity · KikasaDomainSystem.UpdateSkyActivation (cognitive 18) · ×1
  • KikasaDomainSystem.UpdateSkyActivation (cognitive 18) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainSystem.cs:33 — KikasaDomainSystem.UpdateSkyActivation 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.
D2 · Cognitive Complexity · KikasaRainUmbrella.UpdateAutoRain (cognitive 18) · ×1
  • KikasaRainUmbrella.UpdateAutoRain (cognitive 18) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:868 — KikasaRainUmbrella.UpdateAutoRain 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.
D2 · Cognitive Complexity · KikasaBladeServant.UpdateDissolve (cognitive 18) · ×1
  • KikasaBladeServant.UpdateDissolve (cognitive 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:696 — KikasaBladeServant.UpdateDissolve 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.
D2 · Cognitive Complexity · KikasaBoomerangServant.UpdateDissolve (cognitive 18) · ×1
  • KikasaBoomerangServant.UpdateDissolve (cognitive 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:594 — KikasaBoomerangServant.UpdateDissolve 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.
D2 · Cognitive Complexity · KikasaBowServant.DrawPullOf (cognitive 18) · ×1
  • KikasaBowServant.DrawPullOf (cognitive 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:511 — KikasaBowServant.DrawPullOf 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.
D2 · Cognitive Complexity · KikasaBowServant.FireArrow (cognitive 18) · ×1
  • KikasaBowServant.FireArrow (cognitive 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:558 — KikasaBowServant.FireArrow 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.
D2 · Cognitive Complexity · KikasaBowServant.UpdateDissolve (cognitive 18) · ×1
  • KikasaBowServant.UpdateDissolve (cognitive 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:773 — KikasaBowServant.UpdateDissolve 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.
D2 · Cognitive Complexity · KikasaFlailServant.UpdateDissolve (cognitive 18) · ×1
  • KikasaFlailServant.UpdateDissolve (cognitive 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:600 — KikasaFlailServant.UpdateDissolve 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.
D2 · Cognitive Complexity · KikasaGunServant.UpdateDissolve (cognitive 18) · ×1
  • KikasaGunServant.UpdateDissolve (cognitive 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:943 — KikasaGunServant.UpdateDissolve 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.
D2 · Cognitive Complexity · KikasaHalibutDomain.UpdateVisuals (cognitive 18) · ×1
  • KikasaHalibutDomain.UpdateVisuals (cognitive 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutDomain.cs:206 — KikasaHalibutDomain.UpdateVisuals 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.
D2 · Cognitive Complexity · KikasaHalibutServant.UpdateSurge (cognitive 18) · ×1
  • KikasaHalibutServant.UpdateSurge (cognitive 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:579 — KikasaHalibutServant.UpdateSurge 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.
D2 · Cognitive Complexity · KikasaRodServant.UpdateRod (cognitive 18) · ×1
  • KikasaRodServant.UpdateRod (cognitive 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:577 — KikasaRodServant.UpdateRod 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.
D2 · Cognitive Complexity · KikasaSpearServant.UpdateSurround (cognitive 18) · ×1
  • KikasaSpearServant.UpdateSurround (cognitive 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:504 — KikasaSpearServant.UpdateSurround 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.
D2 · Cognitive Complexity · KikasaSpearServant.UpdateDissolve (cognitive 18) · ×1
  • KikasaSpearServant.UpdateDissolve (cognitive 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:573 — KikasaSpearServant.UpdateDissolve 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.
D2 · Cognitive Complexity · KikasaThrowServant.UpdateDissolve (cognitive 18) · ×1
  • KikasaThrowServant.UpdateDissolve (cognitive 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:556 — KikasaThrowServant.UpdateDissolve 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.
D2 · Cognitive Complexity · KikasaWhipServant.UpdateLash (cognitive 18) · ×1
  • KikasaWhipServant.UpdateLash (cognitive 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:471 — KikasaWhipServant.UpdateLash 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.
D2 · Cognitive Complexity · KikasaWhipServant.UpdateDissolve (cognitive 18) · ×1
  • KikasaWhipServant.UpdateDissolve (cognitive 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:556 — KikasaWhipServant.UpdateDissolve 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.
D2 · Cognitive Complexity · KikasaYoyoServant.UpdateDissolve (cognitive 18) · ×1
  • KikasaYoyoServant.UpdateDissolve (cognitive 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:589 — KikasaYoyoServant.UpdateDissolve 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.
D2 · Cognitive Complexity · KikasaBrainClot.AI (cognitive 18) · ×1
  • KikasaBrainClot.AI (cognitive 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:80 — KikasaBrainClot.AI 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.
D2 · Cognitive Complexity · KikasaCultistServant.UpdateDissolve (cognitive 18) · ×1
  • KikasaCultistServant.UpdateDissolve (cognitive 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:805 — KikasaCultistServant.UpdateDissolve 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.
D2 · Cognitive Complexity · KikasaCultistServant.DrawPoseGlow (cognitive 18) · ×1
  • KikasaCultistServant.DrawPoseGlow (cognitive 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:1173 — KikasaCultistServant.DrawPoseGlow 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.
D2 · Cognitive Complexity · KikasaEaterServant.UpdateRiftVisual (cognitive 18) · ×1
  • KikasaEaterServant.UpdateRiftVisual (cognitive 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1084 — KikasaEaterServant.UpdateRiftVisual 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.
D2 · Cognitive Complexity · KikasaMoonRay.AI (cognitive 18) · ×1
  • KikasaMoonRay.AI (cognitive 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs:100 — KikasaMoonRay.AI 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.
D2 · Cognitive Complexity · KikasaPrimeMortar.ExplosionFX (cognitive 18) · ×1
  • KikasaPrimeMortar.ExplosionFX (cognitive 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeMortar.cs:178 — KikasaPrimeMortar.ExplosionFX 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.
D2 · Cognitive Complexity · KikasaQueenSlimeServant.ImpactBurst (cognitive 18) · ×1
  • KikasaQueenSlimeServant.ImpactBurst (cognitive 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:802 — KikasaQueenSlimeServant.ImpactBurst 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.
D2 · Cognitive Complexity · KikasaQueenSlimeServant.UpdateFrames (cognitive 18) · ×1
  • KikasaQueenSlimeServant.UpdateFrames (cognitive 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:1009 — KikasaQueenSlimeServant.UpdateFrames 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.
D2 · Cognitive Complexity · KikasaSeaShrimpServant.SolveArms (cognitive 18) · ×1
  • KikasaSeaShrimpServant.SolveArms (cognitive 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:803 — KikasaSeaShrimpServant.SolveArms 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.
D2 · Cognitive Complexity · KikasaSeaShrimpServant.UpdateNodeCrossings (cognitive 18) · ×1
  • KikasaSeaShrimpServant.UpdateNodeCrossings (cognitive 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:952 — KikasaSeaShrimpServant.UpdateNodeCrossings 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.
D2 · Cognitive Complexity · KikasaSkeletronBloodSkull.AI (cognitive 18) · ×1
  • KikasaSkeletronBloodSkull.AI (cognitive 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronBloodSkull.cs:65 — KikasaSkeletronBloodSkull.AI 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.
D2 · Cognitive Complexity · PRT_FuZhaBeatRing.AI (cognitive 18) · ×1
  • PRT_FuZhaBeatRing.AI (cognitive 18) Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuZhaFX.cs:139 — PRT_FuZhaBeatRing.AI 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.
D2 · Cognitive Complexity · CrimsonHitSurface.HitsIncludingTops (cognitive 18) · ×1
  • CrimsonHitSurface.HitsIncludingTops (cognitive 18) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendParticles.cs:513 — CrimsonHitSurface.HitsIncludingTops 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.
D2 · Cognitive Complexity · CrimsonRendSlash.DrawSmears (cognitive 18) · ×1
  • CrimsonRendSlash.DrawSmears (cognitive 18) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1592 — CrimsonRendSlash.DrawSmears 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.
D2 · Cognitive Complexity · OniMeiGroundBurn.TrySpawnOrRefreshAtGround (cognitive 18) · ×1
  • OniMeiGroundBurn.TrySpawnOrRefreshAtGround (cognitive 18) Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiGroundBurn.cs:163 — OniMeiGroundBurn.TrySpawnOrRefreshAtGround 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.
D2 · Cognitive Complexity · OniFlashStep.FinishDash (cognitive 18) · ×1
  • OniFlashStep.FinishDash (cognitive 18) Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashStep.cs:518 — OniFlashStep.FinishDash 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.
D2 · Cognitive Complexity · OniFlashStep.UpdateTailPose (cognitive 18) · ×1
  • OniFlashStep.UpdateTailPose (cognitive 18) Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashStep.cs:827 — OniFlashStep.UpdateTailPose 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.
D2 · Cognitive Complexity · OnikiriPlayer.TryClickDismember (cognitive 18) · ×1
  • OnikiriPlayer.TryClickDismember (cognitive 18) Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs:1767 — OnikiriPlayer.TryClickDismember 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.
D2 · Cognitive Complexity · SakuraKiriChargeFlowRenderer.FillStrip (cognitive 18) · ×1
  • SakuraKiriChargeFlowRenderer.FillStrip (cognitive 18) Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraKiriChargeFlowRenderer.cs:84 — SakuraKiriChargeFlowRenderer.FillStrip 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.
D2 · Cognitive Complexity · SakuraWeaponAnimation.Validate (cognitive 18) · ×1
  • SakuraWeaponAnimation.Validate (cognitive 18) Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraWeaponAnimation.cs:139 — SakuraWeaponAnimation.Validate 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.
D2 · Cognitive Complexity · OniSigilUI.AdvanceFx (cognitive 18) · ×1
  • OniSigilUI.AdvanceFx (cognitive 18) Content/LegendWeapon/OnikiriLegend/UI/OniSigilUI.cs:573 — OniSigilUI.AdvanceFx 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.
D2 · Cognitive Complexity · CyberDomainFreeze.CollectFreezeTargets (cognitive 18) · ×1
  • CyberDomainFreeze.CollectFreezeTargets (cognitive 18) Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.cs:209 — CyberDomainFreeze.CollectFreezeTargets 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.
D2 · Cognitive Complexity · CyberRestartProj.DrawCracks (cognitive 18) · ×1
  • CyberRestartProj.DrawCracks (cognitive 18) Content/LegendWeapon/SHPCLegend/Cyberspaces/Restart/CyberRestartProj.cs:226 — CyberRestartProj.DrawCracks 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.
D2 · Cognitive Complexity · SHPCRedlineGaugeProj.AI (cognitive 18) · ×1
  • SHPCRedlineGaugeProj.AI (cognitive 18) Content/LegendWeapon/SHPCLegend/Modules/Barrel/RapidBarrelModule.cs:447 — SHPCRedlineGaugeProj.AI 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.
D2 · Cognitive Complexity · SHPCMultiCellMatrixProj.DrawAdditiveAfterNon (cognitive 18) · ×1
  • SHPCMultiCellMatrixProj.DrawAdditiveAfterNon (cognitive 18) Content/LegendWeapon/SHPCLegend/Modules/Frame/MultiCellFrameModule.cs:339 — SHPCMultiCellMatrixProj.DrawAdditiveAfterNon 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.
D2 · Cognitive Complexity · BraceStockModule.UpdateState (cognitive 18) · ×1
  • BraceStockModule.UpdateState (cognitive 18) Content/LegendWeapon/SHPCLegend/Modules/Stock/BraceStockModule.cs:115 — BraceStockModule.UpdateState 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.
D2 · Cognitive Complexity · MoldProcessingPanel.DrawDecomposeColumn (cognitive 18) · ×1
  • MoldProcessingPanel.DrawDecomposeColumn (cognitive 18) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingPanel.cs:186 — MoldProcessingPanel.DrawDecomposeColumn 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.
D2 · Cognitive Complexity · SHPCDomainWheelController.HandleWheelMouse (cognitive 18) · ×1
  • SHPCDomainWheelController.HandleWheelMouse (cognitive 18) Content/LegendWeapon/SHPCLegend/UI/DomainWheel/SHPCDomainWheelController.cs:144 — SHPCDomainWheelController.HandleWheelMouse 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.
D2 · Cognitive Complexity · CharacterDockUI.DrawOverlayText (cognitive 18) · ×1
  • CharacterDockUI.DrawOverlayText (cognitive 18) Content/MainMenus/Characters/CharacterDockUI.cs:632 — CharacterDockUI.DrawOverlayText 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.
D2 · Cognitive Complexity · FeedbackUI.Update (cognitive 18) · ×1
  • FeedbackUI.Update (cognitive 18) Content/MainMenus/Overs/FeedbackUI.cs:62 — FeedbackUI.Update 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.
D2 · Cognitive Complexity · BssBody.FollowChain (cognitive 18) · ×1
  • BssBody.FollowChain (cognitive 18) Content/NPCs/BloomsandSerpents/BssBody.cs:165 — BssBody.FollowChain 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.
D2 · Cognitive Complexity · BssDustDevilProj.AI (cognitive 18) · ×1
  • BssDustDevilProj.AI (cognitive 18) Content/NPCs/BloomsandSerpents/Projectiles/BssDustDevilProj.cs:60 — BssDustDevilProj.AI 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.
D2 · Cognitive Complexity · BssCoilRingState.FireSpokes (cognitive 18) · ×1
  • BssCoilRingState.FireSpokes (cognitive 18) Content/NPCs/BloomsandSerpents/States/BssCoilRingState.cs:280 — BssCoilRingState.FireSpokes 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.
D2 · Cognitive Complexity · BssWindBladeState.FireBurst (cognitive 18) · ×1
  • BssWindBladeState.FireBurst (cognitive 18) Content/NPCs/BloomsandSerpents/States/BssWindBladeState.cs:202 — BssWindBladeState.FireBurst 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.
D2 · Cognitive Complexity · BrainMindSeizeState.OnUpdate (cognitive 18) · ×1
  • BrainMindSeizeState.OnUpdate (cognitive 18) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainMindSeizeState.cs:166 — BrainMindSeizeState.OnUpdate 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.
D2 · Cognitive Complexity · DestroyerBodyAI.SetMechQueenUp (cognitive 18) · ×1
  • DestroyerBodyAI.SetMechQueenUp (cognitive 18) Content/NPCs/BrutalNPCs/BrutalDestroyer/DestroyerBodyAI.cs:288 — DestroyerBodyAI.SetMechQueenUp 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.
D2 · Cognitive Complexity · FishronGrabPlayer.PostUpdate (cognitive 18) · ×1
  • FishronGrabPlayer.PostUpdate (cognitive 18) Content/NPCs/BrutalNPCs/BrutalDukeFishron/FishronGrabCutscene.cs:260 — FishronGrabPlayer.PostUpdate 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.
D2 · Cognitive Complexity · EowDevourPlayer.RescueFromGround (cognitive 18) · ×1
  • EowDevourPlayer.RescueFromGround (cognitive 18) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/EowDevourPlayer.cs:307 — EowDevourPlayer.RescueFromGround 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.
D2 · Cognitive Complexity · EmpressOfLightAI.AI (cognitive 18) · ×1
  • EmpressOfLightAI.AI (cognitive 18) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/EmpressOfLightAI.cs:126 — EmpressOfLightAI.AI 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.
D2 · Cognitive Complexity · EmpressFinaleState.EchoWaltz (cognitive 18) · ×1
  • EmpressFinaleState.EchoWaltz (cognitive 18) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/States/EmpressFinaleState.cs:132 — EmpressFinaleState.EchoWaltz 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.
D2 · Cognitive Complexity · EmpressLightBindWaltzState.DanceUpdate (cognitive 18) · ×1
  • EmpressLightBindWaltzState.DanceUpdate (cognitive 18) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/States/EmpressLightBindWaltzState.cs:186 — EmpressLightBindWaltzState.DanceUpdate 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.
D2 · Cognitive Complexity · EocFogAmbushState.UpdateEmerge (cognitive 18) · ×1
  • EocFogAmbushState.UpdateEmerge (cognitive 18) Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocFogAmbushState.cs:280 — EocFogAmbushState.UpdateEmerge 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.
D2 · Cognitive Complexity · GolemSunBarrageState.OnUpdate (cognitive 18) · ×1
  • GolemSunBarrageState.OnUpdate (cognitive 18) Content/NPCs/BrutalNPCs/BrutalGolem/States/GolemSunBarrageState.cs:26 — GolemSunBarrageState.OnUpdate 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.
D2 · Cognitive Complexity · KingSlimeRoyalDecreeState.UpdateFinale (cognitive 18) · ×1
  • KingSlimeRoyalDecreeState.UpdateFinale (cognitive 18) Content/NPCs/BrutalNPCs/BrutalKingSlime/States/KingSlimeRoyalDecreeState.cs:207 — KingSlimeRoyalDecreeState.UpdateFinale 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.
D2 · Cognitive Complexity · CultistEclipseDragon.PreDraw (cognitive 18) · ×1
  • CultistEclipseDragon.PreDraw (cognitive 18) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistEclipseDragon.cs:240 — CultistEclipseDragon.PreDraw 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.
D2 · Cognitive Complexity · CultistSeekerStar.PreDraw (cognitive 18) · ×1
  • CultistSeekerStar.PreDraw (cognitive 18) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistSeekerStar.cs:152 — CultistSeekerStar.PreDraw 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.
D2 · Cognitive Complexity · CultistStasisMinesState.OnUpdate (cognitive 18) · ×1
  • CultistStasisMinesState.OnUpdate (cognitive 18) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistStasisMinesState.cs:33 — CultistStasisMinesState.OnUpdate 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.
D2 · Cognitive Complexity · TwinsCombinedAttackState.ExecuteChargePhase (cognitive 18) · ×1
  • TwinsCombinedAttackState.ExecuteChargePhase (cognitive 18) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsCombinedAttackState.cs:165 — TwinsCombinedAttackState.ExecuteChargePhase 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.
D2 · Cognitive Complexity · SpazmatismHoverShootState.OnUpdate (cognitive 18) · ×1
  • SpazmatismHoverShootState.OnUpdate (cognitive 18) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismHoverShootState.cs:38 — SpazmatismHoverShootState.OnUpdate 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.
D2 · Cognitive Complexity · TwinsGrabPerformancePlayer.FindEyeGrabbingMe (cognitive 18) · ×1
  • TwinsGrabPerformancePlayer.FindEyeGrabbingMe (cognitive 18) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/TwinsGrabPerformancePlayer.cs:29 — TwinsGrabPerformancePlayer.FindEyeGrabbingMe 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.
D2 · Cognitive Complexity · MLordBlackHoleProj.Warp (cognitive 18) · ×1
  • MLordBlackHoleProj.Warp (cognitive 18) Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordBlackHoleProj.cs:640 — MLordBlackHoleProj.Warp 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.
D2 · Cognitive Complexity · MLordMoonBiteState.RunServer (cognitive 18) · ×1
  • MLordMoonBiteState.RunServer (cognitive 18) Content/NPCs/BrutalNPCs/BrutalMoonLord/States/MLordMoonBiteState.cs:92 — MLordMoonBiteState.RunServer 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.
D2 · Cognitive Complexity · PlanteraVineLattice.AbsorbPlayerDamage (cognitive 18) · ×1
  • PlanteraVineLattice.AbsorbPlayerDamage (cognitive 18) Content/NPCs/BrutalNPCs/BrutalPlantera/Projectiles/PlanteraVineLattice.cs:129 — PlanteraVineLattice.AbsorbPlayerDamage 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.
D2 · Cognitive Complexity · PlanteraSporeSowState.OnUpdate (cognitive 18) · ×1
  • PlanteraSporeSowState.OnUpdate (cognitive 18) Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraSporeSowState.cs:29 — PlanteraSporeSowState.OnUpdate 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.
D2 · Cognitive Complexity · QueenGaleFieldProj.AI (cognitive 18) · ×1
  • QueenGaleFieldProj.AI (cognitive 18) Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenGaleFieldProj.cs:40 — QueenGaleFieldProj.AI 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.
D2 · Cognitive Complexity · PrimeIonOverloadState.OnUpdate (cognitive 18) · ×1
  • PrimeIonOverloadState.OnUpdate (cognitive 18) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/PrimeIonOverloadState.cs:23 — PrimeIonOverloadState.OnUpdate 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.
D2 · Cognitive Complexity · PrimeTetherSpinState.OnUpdate (cognitive 18) · ×1
  • PrimeTetherSpinState.OnUpdate (cognitive 18) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/PrimeTetherSpinState.cs:37 — PrimeTetherSpinState.OnUpdate 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.
D2 · Cognitive Complexity · WofJawMawProj.UpdateBite (cognitive 18) · ×1
  • WofJawMawProj.UpdateBite (cognitive 18) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofJawMawProj.cs:123 — WofJawMawProj.UpdateBite 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.
D2 · Cognitive Complexity · FssBody.FollowChain (cognitive 18) · ×1
  • FssBody.FollowChain (cognitive 18) Content/NPCs/FestersandSerpents/FssBody.cs:213 — FssBody.FollowChain 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.
D2 · Cognitive Complexity · FssClawRig.ResolvePose (cognitive 18) · ×1
  • FssClawRig.ResolvePose (cognitive 18) Content/NPCs/FestersandSerpents/FssClawRig.cs:197 — FssClawRig.ResolvePose 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.
D2 · Cognitive Complexity · FssClawReapState.UpdateFling (cognitive 18) · ×1
  • FssClawReapState.UpdateFling (cognitive 18) Content/NPCs/FestersandSerpents/States/FssClawReapState.cs:206 — FssClawReapState.UpdateFling 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.
D2 · Cognitive Complexity · ScrapLegionState.OnUpdate (cognitive 18) · ×1
  • ScrapLegionState.OnUpdate (cognitive 18) Content/NPCs/ScrapCommanders/States/ScrapLegionState.cs:29 — ScrapLegionState.OnUpdate 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.
D2 · Cognitive Complexity · SeaShrimpGeyserMarchState.OnUpdate (cognitive 18) · ×1
  • SeaShrimpGeyserMarchState.OnUpdate (cognitive 18) Content/NPCs/SeaShrimp/States/SeaShrimpGeyserMarchState.cs:28 — SeaShrimpGeyserMarchState.OnUpdate 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.
D2 · Cognitive Complexity · TBUGShopUI.DrawGrid (cognitive 18) · ×1
  • TBUGShopUI.DrawGrid (cognitive 18) Content/NPCs/TBUGs/UIs/TBUGShopUI.cs:532 — TBUGShopUI.DrawGrid 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.
D2 · Cognitive Complexity · DraedonQuestLogStyle.DrawFallbackBackground (cognitive 18) · ×1
  • DraedonQuestLogStyle.DrawFallbackBackground (cognitive 18) Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:97 — DraedonQuestLogStyle.DrawFallbackBackground 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.
D2 · Cognitive Complexity · ForestQuestLogStyle.DrawBackground (cognitive 18) · ×1
  • ForestQuestLogStyle.DrawBackground (cognitive 18) Content/QuestLogs/Styles/ForestQuestLogStyle.cs:128 — ForestQuestLogStyle.DrawBackground 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.
D2 · Cognitive Complexity · DraedonCallUI.Update (cognitive 18) · ×1
  • DraedonCallUI.Update (cognitive 18) Content/Scenarios/Draedon/PQCDs/DraedonCallUI.cs:105 — DraedonCallUI.Update 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.
D2 · Cognitive Complexity · DungeonworldSnuff.CollectLamps (cognitive 18) · ×1
  • DungeonworldSnuff.CollectLamps (cognitive 18) Content/Scenarios/Dungeonworld/Ambience/DungeonworldSnuff.cs:223 — DungeonworldSnuff.CollectLamps 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.
D2 · Cognitive Complexity · DungeonworldBossRecords.ServerSettleKill (cognitive 18) · ×1
  • DungeonworldBossRecords.ServerSettleKill (cognitive 18) Content/Scenarios/Dungeonworld/DungeonworldBossRecords.cs:200 — DungeonworldBossRecords.ServerSettleKill 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.
D2 · Cognitive Complexity · L1Content.RouteChainEdges (cognitive 18) · ×1
  • L1Content.RouteChainEdges (cognitive 18) Content/Scenarios/Dungeonworld/Gen/Layers/L1/L1Content.cs:179 — L1Content.RouteChainEdges 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.
D2 · Cognitive Complexity · L4Content.TryBuild (cognitive 18) · ×1
  • L4Content.TryBuild (cognitive 18) Content/Scenarios/Dungeonworld/Gen/Layers/L4/L4Content.cs:248 — L4Content.TryBuild 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.
D2 · Cognitive Complexity · L5Rooms.CarvePit (cognitive 18) · ×1
  • L5Rooms.CarvePit (cognitive 18) Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Rooms.cs:517 — L5Rooms.CarvePit 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.
D2 · Cognitive Complexity · GuideTrailPass.PaintGaolTrail (cognitive 18) · ×1
  • GuideTrailPass.PaintGaolTrail (cognitive 18) Content/Scenarios/Dungeonworld/Gen/Passes/GuideTrailPass.cs:57 — GuideTrailPass.PaintGaolTrail 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.
D2 · Cognitive Complexity · LanternWarden.UpdatePatrol (cognitive 18) · ×1
  • LanternWarden.UpdatePatrol (cognitive 18) Content/Scenarios/Dungeonworld/NPCs/Elites/LanternWarden.cs:203 — LanternWarden.UpdatePatrol 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.
D2 · Cognitive Complexity · Undrowned.UpdateStalk (cognitive 18) · ×1
  • Undrowned.UpdateStalk (cognitive 18) Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:667 — Undrowned.UpdateStalk 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.
D2 · Cognitive Complexity · Undrowned.PickNextAttack (cognitive 18) · ×1
  • Undrowned.PickNextAttack (cognitive 18) Content/Scenarios/Dungeonworld/NPCs/Undrowned.cs:736 — Undrowned.PickNextAttack 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.
D2 · Cognitive Complexity · DungeonworldCageRig.Step (cognitive 18) · ×1
  • DungeonworldCageRig.Step (cognitive 18) Content/Scenarios/Dungeonworld/UI/DungeonworldCageRig.cs:127 — DungeonworldCageRig.Step 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.
D2 · Cognitive Complexity · DungeonworldEntryReveal.DrawAndAdvance (cognitive 18) · ×1
  • DungeonworldEntryReveal.DrawAndAdvance (cognitive 18) Content/Scenarios/Dungeonworld/UI/DungeonworldEntryReveal.cs:105 — DungeonworldEntryReveal.DrawAndAdvance 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.
D2 · Cognitive Complexity · HelenGiftNarrativeTracker.Tick (cognitive 18) · ×1
  • HelenGiftNarrativeTracker.Tick (cognitive 18) Content/Scenarios/Helen/Gifts/HelenGiftNarrativeTracker.cs:77 — HelenGiftNarrativeTracker.Tick 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.
D2 · Cognitive Complexity · HimayoGiftNarrativeTracker.RegisterAll (cognitive 18) · ×1
  • HimayoGiftNarrativeTracker.RegisterAll (cognitive 18) Content/Scenarios/Himayo/Gifts/HimayoGiftNarrativeTracker.cs:80 — HimayoGiftNarrativeTracker.RegisterAll 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.
D2 · Cognitive Complexity · KiameRuins.PunchWallHoles (cognitive 18) · ×1
  • KiameRuins.PunchWallHoles (cognitive 18) Content/Scenarios/Kiame/Gen/KiameRuins.cs:213 — KiameRuins.PunchWallHoles 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.
D2 · Cognitive Complexity · OniRainWorldState.UpdateFx (cognitive 18) · ×1
  • OniRainWorldState.UpdateFx (cognitive 18) Content/Scenarios/Kiame/Overlay/OniRainWorldState.cs:200 — OniRainWorldState.UpdateFx 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.
D2 · Cognitive Complexity · OceanRaidersTP.UpdateMachine (cognitive 18) · ×1
  • OceanRaidersTP.UpdateMachine (cognitive 18) Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersTP.cs:395 — OceanRaidersTP.UpdateMachine 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.
D2 · Cognitive Complexity · OldNetBlackICE.AI (cognitive 18) · ×1
  • OldNetBlackICE.AI (cognitive 18) Content/Scenarios/OldNet/NPCs/OldNetBlackICE.cs:78 — OldNetBlackICE.AI 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.
D2 · Cognitive Complexity · OldNetTurretICE.AI (cognitive 18) · ×1
  • OldNetTurretICE.AI (cognitive 18) Content/Scenarios/OldNet/NPCs/OldNetTurretICE.cs:58 — OldNetTurretICE.AI 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.
D2 · Cognitive Complexity · OldNetTileFXRender.DrawBeams (cognitive 18) · ×1
  • OldNetTileFXRender.DrawBeams (cognitive 18) Content/Scenarios/OldNet/Renders/OldNetTileFXRender.cs:145 — OldNetTileFXRender.DrawBeams 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.
D2 · Cognitive Complexity · ShenyoGiftNarrativeTracker.RegisterAll (cognitive 18) · ×1
  • ShenyoGiftNarrativeTracker.RegisterAll (cognitive 18) Content/Scenarios/Shenyo/Gifts/ShenyoGiftNarrativeTracker.cs:77 — ShenyoGiftNarrativeTracker.RegisterAll 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.
D2 · Cognitive Complexity · ShepelGiftNarrativeTracker.Tick (cognitive 18) · ×1
  • ShepelGiftNarrativeTracker.Tick (cognitive 18) Content/Scenarios/Shepel/Gifts/ShepelBossGiftNarrative.cs:88 — ShepelGiftNarrativeTracker.Tick 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.
D2 · Cognitive Complexity · BloodAltarRite.SpawnPhaseParticles (cognitive 18) · ×1
  • BloodAltarRite.SpawnPhaseParticles (cognitive 18) Content/Tiles/BloodAltars/BloodAltarRite.cs:316 — BloodAltarRite.SpawnPhaseParticles 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.
D2 · Cognitive Complexity · BottomLeftHudStack.Layout (cognitive 18) · ×1
  • BottomLeftHudStack.Layout (cognitive 18) Content/UIs/HudStack/BottomLeftHudStack.cs:78 — BottomLeftHudStack.Layout 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.
D2 · Cognitive Complexity · NotificationPopupSystem.Update (cognitive 18) · ×1
  • NotificationPopupSystem.Update (cognitive 18) Content/UIs/NotificationPopup/NotificationPopupSystem.cs:74 — NotificationPopupSystem.Update 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.
D2 · Cognitive Complexity · RainSeizurePerformance.Update (cognitive 18) · ×1
  • RainSeizurePerformance.Update (cognitive 18) Content/Wraiths/Deaths/Performances/RainSeizurePerformance.cs:192 — RainSeizurePerformance.Update 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.
D2 · Cognitive Complexity · GhostRainProj.AI (cognitive 18) · ×1
  • GhostRainProj.AI (cognitive 18) Content/Wraiths/Projectiles/GhostRainProj.cs:114 — GhostRainProj.AI 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.
D2 · Cognitive Complexity · CindercragVentProj.PreDraw (cognitive 17) · ×1
  • CindercragVentProj.PreDraw (cognitive 17) Content/GameModes/BrutalMobs/Ambience/Cindercrag/Projectiles/CindercragVentProj.cs:225 — CindercragVentProj.PreDraw 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.
D2 · Cognitive Complexity · DuskhallPlayer.PostUpdate (cognitive 17) · ×1
  • DuskhallPlayer.PostUpdate (cognitive 17) Content/GameModes/BrutalMobs/Ambience/Duskhall/DuskhallPlayer.cs:66 — DuskhallPlayer.PostUpdate 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.
D2 · Cognitive Complexity · FleshfenAmbience.TrySpawnPulseSpot (cognitive 17) · ×1
  • FleshfenAmbience.TrySpawnPulseSpot (cognitive 17) Content/GameModes/BrutalMobs/Ambience/Fleshfen/FleshfenAmbience.cs:230 — FleshfenAmbience.TrySpawnPulseSpot 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.
D2 · Cognitive Complexity · FrostveilAmbience.UpdateAurora (cognitive 17) · ×1
  • FrostveilAmbience.UpdateAurora (cognitive 17) Content/GameModes/BrutalMobs/Ambience/Frostveil/FrostveilAmbience.cs:279 — FrostveilAmbience.UpdateAurora 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.
D2 · Cognitive Complexity · HollowdeepAmbience.UpdateHollowListen (cognitive 17) · ×1
  • HollowdeepAmbience.UpdateHollowListen (cognitive 17) Content/GameModes/BrutalMobs/Ambience/Hollowdeep/HollowdeepAmbience.cs:278 — HollowdeepAmbience.UpdateHollowListen 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.
D2 · Cognitive Complexity · LumindepthAmbientRender.UpdateMotes (cognitive 17) · ×1
  • LumindepthAmbientRender.UpdateMotes (cognitive 17) Content/GameModes/BrutalMobs/Ambience/Lumindepth/LumindepthAmbientRender.cs:136 — LumindepthAmbientRender.UpdateMotes 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.
D2 · Cognitive Complexity · LumindepthAmbientRender.EndEntityDraw (cognitive 17) · ×1
  • LumindepthAmbientRender.EndEntityDraw (cognitive 17) Content/GameModes/BrutalMobs/Ambience/Lumindepth/LumindepthAmbientRender.cs:199 — LumindepthAmbientRender.EndEntityDraw 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.
D2 · Cognitive Complexity · LumindepthVortexProj.PreDraw (cognitive 17) · ×1
  • LumindepthVortexProj.PreDraw (cognitive 17) Content/GameModes/BrutalMobs/Ambience/Lumindepth/Projectiles/LumindepthVortexProj.cs:177 — LumindepthVortexProj.PreDraw 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.
D2 · Cognitive Complexity · SilkcryptPlayer.TryPlacePatch (cognitive 17) · ×1
  • SilkcryptPlayer.TryPlacePatch (cognitive 17) Content/GameModes/BrutalMobs/Ambience/Silkcrypt/SilkcryptPlayer.cs:186 — SilkcryptPlayer.TryPlacePatch 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.
D2 · Cognitive Complexity · SporeshinePlayer.UpdateDazeLocal (cognitive 17) · ×1
  • SporeshinePlayer.UpdateDazeLocal (cognitive 17) Content/GameModes/BrutalMobs/Ambience/Sporeshine/SporeshinePlayer.cs:83 — SporeshinePlayer.UpdateDazeLocal 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.
D2 · Cognitive Complexity · SporeshinePlayer.TryFindCap (cognitive 17) · ×1
  • SporeshinePlayer.TryFindCap (cognitive 17) Content/GameModes/BrutalMobs/Ambience/Sporeshine/SporeshinePlayer.cs:168 — SporeshinePlayer.TryFindCap 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.
D2 · Cognitive Complexity · StarfallAmbience.ScanAnchors (cognitive 17) · ×1
  • StarfallAmbience.ScanAnchors (cognitive 17) Content/GameModes/BrutalMobs/Ambience/Starfall/StarfallAmbience.cs:103 — StarfallAmbience.ScanAnchors 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.
D2 · Cognitive Complexity · StratosFallingStarProj.PreDraw (cognitive 17) · ×1
  • StratosFallingStarProj.PreDraw (cognitive 17) Content/GameModes/BrutalMobs/Ambience/Stratos/Projectiles/StratosFallingStarProj.cs:250 — StratosFallingStarProj.PreDraw 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.
D2 · Cognitive Complexity · StratosAmbientRender.UpdateBySystem (cognitive 17) · ×1
  • StratosAmbientRender.UpdateBySystem (cognitive 17) Content/GameModes/BrutalMobs/Ambience/Stratos/StratosAmbientRender.cs:41 — StratosAmbientRender.UpdateBySystem 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.
D2 · Cognitive Complexity · StratosAmbientRender.DrawNPCsOverTiles (cognitive 17) · ×1
  • StratosAmbientRender.DrawNPCsOverTiles (cognitive 17) Content/GameModes/BrutalMobs/Ambience/Stratos/StratosAmbientRender.cs:99 — StratosAmbientRender.DrawNPCsOverTiles 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.
D2 · Cognitive Complexity · SunkenduneAmbientRender.TrySpawnTrickle (cognitive 17) · ×1
  • SunkenduneAmbientRender.TrySpawnTrickle (cognitive 17) Content/GameModes/BrutalMobs/Ambience/Sunkendune/SunkenduneAmbientRender.cs:148 — SunkenduneAmbientRender.TrySpawnTrickle 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.
D2 · Cognitive Complexity · TidecallRogueWaveProj.AI (cognitive 17) · ×1
  • TidecallRogueWaveProj.AI (cognitive 17) Content/GameModes/BrutalMobs/Ambience/Tidecall/Projectiles/TidecallRogueWaveProj.cs:141 — TidecallRogueWaveProj.AI 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.
D2 · Cognitive Complexity · WoodsongMistRender.UpdateBySystem (cognitive 17) · ×1
  • WoodsongMistRender.UpdateBySystem (cognitive 17) Content/GameModes/BrutalMobs/Ambience/Woodsong/WoodsongMistRender.cs:47 — WoodsongMistRender.UpdateBySystem 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.
D2 · Cognitive Complexity · WoodsongMistRender.EndEntityDraw (cognitive 17) · ×1
  • WoodsongMistRender.EndEntityDraw (cognitive 17) Content/GameModes/BrutalMobs/Ambience/Woodsong/WoodsongMistRender.cs:106 — WoodsongMistRender.EndEntityDraw 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.
D2 · Cognitive Complexity · DungeonDeepNPC.TickCharge (cognitive 17) · ×1
  • DungeonDeepNPC.TickCharge (cognitive 17) Content/GameModes/BrutalMobs/DungeonDeep/DungeonDeepNPC.Melee.cs:93 — DungeonDeepNPC.TickCharge 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.
D2 · Cognitive Complexity · DdRocketProj.AI (cognitive 17) · ×1
  • DdRocketProj.AI (cognitive 17) Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdRocketProj.cs:69 — DdRocketProj.AI 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.
D2 · Cognitive Complexity · DdSkullOmen.AI (cognitive 17) · ×1
  • DdSkullOmen.AI (cognitive 17) Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdSkullOmen.cs:70 — DdSkullOmen.AI 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.
D2 · Cognitive Complexity · FrmMiniBossNPC.TryStartSignature (cognitive 17) · ×1
  • FrmMiniBossNPC.TryStartSignature (cognitive 17) Content/GameModes/BrutalMobs/FrostMoon/FrmMiniBossNPC.cs:201 — FrmMiniBossNPC.TryStartSignature 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.
D2 · Cognitive Complexity · FrmMortarBlastProj.AI (cognitive 17) · ×1
  • FrmMortarBlastProj.AI (cognitive 17) Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmMortarBlastProj.cs:57 — FrmMortarBlastProj.AI 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.
D2 · Cognitive Complexity · FrmStrafeLaneProj.AI (cognitive 17) · ×1
  • FrmStrafeLaneProj.AI (cognitive 17) Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmStrafeLaneProj.cs:60 — FrmStrafeLaneProj.AI 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.
D2 · Cognitive Complexity · OceanBrutalNPC.TryStartShark (cognitive 17) · ×1
  • OceanBrutalNPC.TryStartShark (cognitive 17) Content/GameModes/BrutalMobs/Ocean/OceanBrutalNPC.cs:446 — OceanBrutalNPC.TryStartShark 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.
D2 · Cognitive Complexity · PrtBannerMark.AI (cognitive 17) · ×1
  • PrtBannerMark.AI (cognitive 17) Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtBannerMark.cs:58 — PrtBannerMark.AI 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.
D2 · Cognitive Complexity · PrtRicochetShot.ComputePath (cognitive 17) · ×1
  • PrtRicochetShot.ComputePath (cognitive 17) Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtRicochetShot.cs:199 — PrtRicochetShot.ComputePath 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.
D2 · Cognitive Complexity · SandveilFinSurgeOmen.AI (cognitive 17) · ×1
  • SandveilFinSurgeOmen.AI (cognitive 17) Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilFinSurgeOmen.cs:87 — SandveilFinSurgeOmen.AI 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.
D2 · Cognitive Complexity · GsApprenticeArmor.OnEndowHitNPC (cognitive 17) · ×1
  • GsApprenticeArmor.OnEndowHitNPC (cognitive 17) Content/GameModes/GodSmith/Armors/Endgame/GsApprenticeArmor.cs:42 — GsApprenticeArmor.OnEndowHitNPC 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.
D2 · Cognitive Complexity · GsBeeGuardProj.AI (cognitive 17) · ×1
  • GsBeeGuardProj.AI (cognitive 17) Content/GameModes/GodSmith/Armors/Reset/GsBeeArmor.cs:122 — GsBeeGuardProj.AI 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.
D2 · Cognitive Complexity · GsElectrosphereLauncher.GsProjPostAI (cognitive 17) · ×1
  • GsElectrosphereLauncher.GsProjPostAI (cognitive 17) Content/GameModes/GodSmith/Weapons/Launchers/GsElectrosphereLauncher.cs:38 — GsElectrosphereLauncher.GsProjPostAI 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.
D2 · Cognitive Complexity · GsLastPrismHeldProj.ChannelAI (cognitive 17) · ×1
  • GsLastPrismHeldProj.ChannelAI (cognitive 17) Content/GameModes/GodSmith/Weapons/MagicConduit/Projectiles/GsLastPrismHeldProj.cs:84 — GsLastPrismHeldProj.ChannelAI 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.
D2 · Cognitive Complexity · GsDayBreakSpearProj.HandlePinBookkeeping (cognitive 17) · ×1
  • GsDayBreakSpearProj.HandlePinBookkeeping (cognitive 17) Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:471 — GsDayBreakSpearProj.HandlePinBookkeeping 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.
D2 · Cognitive Complexity · GsScourgeTinyEaterProj.HomeTo (cognitive 17) · ×1
  • GsScourgeTinyEaterProj.HomeTo (cognitive 17) Content/GameModes/GodSmith/Weapons/MeleeOddities/GsScourgeoftheCorruptor.cs:403 — GsScourgeTinyEaterProj.HomeTo 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.
D2 · Cognitive Complexity · SentryGrid.RebuildGraph (cognitive 17) · ×1
  • SentryGrid.RebuildGraph (cognitive 17) Content/GameModes/GodSmith/Weapons/SummonSentries/SentryGrid.cs:189 — SentryGrid.RebuildGraph 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.
D2 · Cognitive Complexity · GsWhipDurendalVerdictProj.AI (cognitive 17) · ×1
  • GsWhipDurendalVerdictProj.AI (cognitive 17) Content/GameModes/GodSmith/Weapons/SummonWhips/Projectiles/GsWhipDurendalProj.cs:58 — GsWhipDurendalVerdictProj.AI 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.
D2 · Cognitive Complexity · HackEffectTracker.TryResolveTarget (cognitive 17) · ×1
  • HackEffectTracker.TryResolveTarget (cognitive 17) Content/HackTimes/HackEffectTracker.cs:480 — HackEffectTracker.TryResolveTarget 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.
D2 · Cognitive Complexity · HackQueueRenderer.Update (cognitive 17) · ×1
  • HackQueueRenderer.Update (cognitive 17) Content/HackTimes/HackQueueRenderer.cs:309 — HackQueueRenderer.Update 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.
D2 · Cognitive Complexity · HackTimeNetSync.ExecuteAuthorityRequest (cognitive 17) · ×1
  • HackTimeNetSync.ExecuteAuthorityRequest (cognitive 17) Content/HackTimes/HackTimeNetSync.cs:570 — HackTimeNetSync.ExecuteAuthorityRequest 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.
D2 · Cognitive Complexity · HackTimeNetSync.ReadSnapshot (cognitive 17) · ×1
  • HackTimeNetSync.ReadSnapshot (cognitive 17) Content/HackTimes/HackTimeNetSync.cs:1065 — HackTimeNetSync.ReadSnapshot 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.
D2 · Cognitive Complexity · InfiniteHackRenderer.Update (cognitive 17) · ×1
  • InfiniteHackRenderer.Update (cognitive 17) Content/HackTimes/InfiniteHackRenderer.cs:90 — InfiniteHackRenderer.Update 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.
D2 · Cognitive Complexity · DataPurge.OnApply (cognitive 17) · ×1
  • DataPurge.OnApply (cognitive 17) Content/HackTimes/Protocols/DataPurge.cs:30 — DataPurge.OnApply 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.
D2 · Cognitive Complexity · PressureSurge.SlamCeilingHits (cognitive 17) · ×1
  • PressureSurge.SlamCeilingHits (cognitive 17) Content/HackTimes/Protocols/PressureSurge.cs:138 — PressureSurge.SlamCeilingHits 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.
D2 · Cognitive Complexity · SegmentDelink.OnRemove (cognitive 17) · ×1
  • SegmentDelink.OnRemove (cognitive 17) Content/HackTimes/Protocols/SegmentDelink.cs:90 — SegmentDelink.OnRemove 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.
D2 · Cognitive Complexity · VeinResonance.ScanVeins (cognitive 17) · ×1
  • VeinResonance.ScanVeins (cognitive 17) Content/HackTimes/Protocols/VeinResonance.cs:134 — VeinResonance.ScanVeins 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.
D2 · Cognitive Complexity · PlayerHackAuthority.ExecuteTraceback (cognitive 17) · ×1
  • PlayerHackAuthority.ExecuteTraceback (cognitive 17) Content/HackTimes/PvP/PlayerHackNet.cs:244 — PlayerHackAuthority.ExecuteTraceback 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.
D2 · Cognitive Complexity · PlayerHackLinkRender.DrawDefenderLines (cognitive 17) · ×1
  • PlayerHackLinkRender.DrawDefenderLines (cognitive 17) Content/HackTimes/PvP/UI/PlayerHackLinkRender.cs:84 — PlayerHackLinkRender.DrawDefenderLines 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.
D2 · Cognitive Complexity · BottlingMachineTP.RightClickByTile (cognitive 17) · ×1
  • BottlingMachineTP.RightClickByTile (cognitive 17) Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineTP.cs:364 — BottlingMachineTP.RightClickByTile 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.
D2 · Cognitive Complexity · CrusherTile.PreDraw (cognitive 17) · ×1
  • CrusherTile.PreDraw (cognitive 17) Content/Industrials/ElectricPowers/Crushers/CrusherTile.cs:86 — CrusherTile.PreDraw 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.
D2 · Cognitive Complexity · PlayerLauncherUI.HandleButtonClicks (cognitive 17) · ×1
  • PlayerLauncherUI.HandleButtonClicks (cognitive 17) Content/Industrials/ElectricPowers/Launchers/PlayerLauncherUI.cs:216 — PlayerLauncherUI.HandleButtonClicks 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.
D2 · Cognitive Complexity · OreDropRule.Evaluate (cognitive 17) · ×1
  • OreDropRule.Evaluate (cognitive 17) Content/Industrials/ElectricPowers/MiningMachines/MiningMachineSystem.cs:339 — OreDropRule.Evaluate 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.
D2 · Cognitive Complexity · ShieldGeneratorTP.UpdateTurret (cognitive 17) · ×1
  • ShieldGeneratorTP.UpdateTurret (cognitive 17) Content/Industrials/ElectricPowers/ShieldGenerators/ShieldGeneratorTP.cs:64 — ShieldGeneratorTP.UpdateTurret 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.
D2 · Cognitive Complexity · TeslaElectromagneticTowerTP.UpdateTurret (cognitive 17) · ×1
  • TeslaElectromagneticTowerTP.UpdateTurret (cognitive 17) Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:430 — TeslaElectromagneticTowerTP.UpdateTurret 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.
D2 · Cognitive Complexity · TeslaBallByAttack.Chase (cognitive 17) · ×1
  • TeslaBallByAttack.Chase (cognitive 17) Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:830 — TeslaBallByAttack.Chase 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.
D2 · Cognitive Complexity · TeslaBallByGuard.Chase (cognitive 17) · ×1
  • TeslaBallByGuard.Chase (cognitive 17) Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:967 — TeslaBallByGuard.Chase 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.
D2 · Cognitive Complexity · TreeBlueprint.GeneratePalm (cognitive 17) · ×1
  • TreeBlueprint.GeneratePalm (cognitive 17) Content/Industrials/ElectricPowers/TreeRegrowths/TreeBlueprint.cs:362 — TreeBlueprint.GeneratePalm 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.
D2 · Cognitive Complexity · TreeRegrowth.EmitGrowthDust (cognitive 17) · ×1
  • TreeRegrowth.EmitGrowthDust (cognitive 17) Content/Industrials/ElectricPowers/TreeRegrowths/TreeRegrowth.cs:193 — TreeRegrowth.EmitGrowthDust 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.
D2 · Cognitive Complexity · FluidPipelineTP.UpdateSidesAndFlow (cognitive 17) · ×1
  • FluidPipelineTP.UpdateSidesAndFlow (cognitive 17) Content/Industrials/MaterialFlow/Fluids/FluidPipeline.cs:169 — FluidPipelineTP.UpdateSidesAndFlow 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.
D2 · Cognitive Complexity · PipelineSideState.HandleBatteryConnection (cognitive 17) · ×1
  • PipelineSideState.HandleBatteryConnection (cognitive 17) Content/Industrials/MaterialFlow/Pipelines/PipelineSideState.cs:107 — PipelineSideState.HandleBatteryConnection 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.
D2 · Cognitive Complexity · ProbeOrbitalStrike.EmitAmbientFx (cognitive 17) · ×1
  • ProbeOrbitalStrike.EmitAmbientFx (cognitive 17) Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:151 — ProbeOrbitalStrike.EmitAmbientFx 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.
D2 · Cognitive Complexity · MawWormProj.AI (cognitive 17) · ×1
  • MawWormProj.AI (cognitive 17) Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawWormProj.cs:103 — MawWormProj.AI 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.
D2 · Cognitive Complexity · MawWormProj.UpdateGroundCrossing (cognitive 17) · ×1
  • MawWormProj.UpdateGroundCrossing (cognitive 17) Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawWormProj.cs:413 — MawWormProj.UpdateGroundCrossing 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.
D2 · Cognitive Complexity · RiteMoonFlare.AI (cognitive 17) · ×1
  • RiteMoonFlare.AI (cognitive 17) Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMoonFlare.cs:107 — RiteMoonFlare.AI 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.
D2 · Cognitive Complexity · JamesChainStrike.BuildChain (cognitive 17) · ×1
  • JamesChainStrike.BuildChain (cognitive 17) Content/Items/Magic/Elysiums/Disciples/James.cs:100 — JamesChainStrike.BuildChain 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.
D2 · Cognitive Complexity · ElysiumPlayer.TickRevelation (cognitive 17) · ×1
  • ElysiumPlayer.TickRevelation (cognitive 17) Content/Items/Magic/Elysiums/ElysiumPlayer.cs:271 — ElysiumPlayer.TickRevelation 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.
D2 · Cognitive Complexity · AbyssrendUndercurrent.AI (cognitive 17) · ×1
  • AbyssrendUndercurrent.AI (cognitive 17) Content/Items/Melee/Abyssrends/AbyssrendUndercurrent.cs:52 — AbyssrendUndercurrent.AI 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.
D2 · Cognitive Complexity · DestroyersBladeEXHeld.KickSlash (cognitive 17) · ×1
  • DestroyersBladeEXHeld.KickSlash (cognitive 17) Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:419 — DestroyersBladeEXHeld.KickSlash 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.
D2 · Cognitive Complexity · HeartcarverHeld.AI (cognitive 17) · ×1
  • HeartcarverHeld.AI (cognitive 17) Content/Items/Melee/Heartcarver.cs:212 — HeartcarverHeld.AI 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.
D2 · Cognitive Complexity · OniMacheteHeld.StrikeMotion (cognitive 17) · ×1
  • OniMacheteHeld.StrikeMotion (cognitive 17) Content/Items/Melee/OniMachete.cs:728 — OniMacheteHeld.StrikeMotion 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.
D2 · Cognitive Complexity · LonginusHeld.AI (cognitive 17) · ×1
  • LonginusHeld.AI (cognitive 17) Content/Items/Melee/SpearOfLonginuses/LonginusHeld.cs:65 — LonginusHeld.AI 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.
D2 · Cognitive Complexity · WeaverGrievancesDash.AI (cognitive 17) · ×1
  • WeaverGrievancesDash.AI (cognitive 17) Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:590 — WeaverGrievancesDash.AI 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.
D2 · Cognitive Complexity · RTerraBladeHeld.HandleParticles (cognitive 17) · ×1
  • RTerraBladeHeld.HandleParticles (cognitive 17) Content/Items/Modifys/RTerraBlades/RTerraBladeHeld.cs:623 — RTerraBladeHeld.HandleParticles 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.
D2 · Cognitive Complexity · HalibutReset.CollectNpcs (cognitive 17) · ×1
  • HalibutReset.CollectNpcs (cognitive 17) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:286 — HalibutReset.CollectNpcs 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.
D2 · Cognitive Complexity · FishSwarmController.AI (cognitive 17) · ×1
  • FishSwarmController.AI (cognitive 17) Content/LegendWeapon/HalibutLegend/FishSkills/FishSwarm.cs:222 — FishSwarmController.AI 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.
D2 · Cognitive Complexity · TropicalBarracudaProjectile.PreDraw (cognitive 17) · ×1
  • TropicalBarracudaProjectile.PreDraw (cognitive 17) Content/LegendWeapon/HalibutLegend/FishSkills/FishTropicalBarracuda.cs:390 — TropicalBarracudaProjectile.PreDraw 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.
D2 · Cognitive Complexity · CthulhuEye.AI (cognitive 17) · ×1
  • CthulhuEye.AI (cognitive 17) Content/LegendWeapon/HalibutLegend/FishSkills/FishofCthulu.cs:174 — CthulhuEye.AI 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.
D2 · Cognitive Complexity · KikasaDomainNet.Receive (cognitive 17) · ×1
  • KikasaDomainNet.Receive (cognitive 17) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainNet.cs:39 — KikasaDomainNet.Receive 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.
D2 · Cognitive Complexity · KikasaDrown.UpdateAuthority (cognitive 17) · ×1
  • KikasaDrown.UpdateAuthority (cognitive 17) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrown.cs:547 — KikasaDrown.UpdateAuthority 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.
D2 · Cognitive Complexity · KikasaPlayerDrown.UpdateAuthority (cognitive 17) · ×1
  • KikasaPlayerDrown.UpdateAuthority (cognitive 17) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaPlayerDrown.cs:425 — KikasaPlayerDrown.UpdateAuthority 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.
D2 · Cognitive Complexity · KikasaBloodColumn.AI (cognitive 17) · ×1
  • KikasaBloodColumn.AI (cognitive 17) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaBloodColumn.cs:156 — KikasaBloodColumn.AI 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.
D2 · Cognitive Complexity · KikasaReset.CollectNpcs (cognitive 17) · ×1
  • KikasaReset.CollectNpcs (cognitive 17) Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaReset.cs:309 — KikasaReset.CollectNpcs 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.
D2 · Cognitive Complexity · KikasaPandemoniumCircle.UpdateAttacks (cognitive 17) · ×1
  • KikasaPandemoniumCircle.UpdateAttacks (cognitive 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumCircle.cs:191 — KikasaPandemoniumCircle.UpdateAttacks 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.
D2 · Cognitive Complexity · KikasaPandemoniumServant.UpdateCircleCast (cognitive 17) · ×1
  • KikasaPandemoniumServant.UpdateCircleCast (cognitive 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:562 — KikasaPandemoniumServant.UpdateCircleCast 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.
D2 · Cognitive Complexity · KikasaSHPCServant.UpdateSunCast (cognitive 17) · ×1
  • KikasaSHPCServant.UpdateSunCast (cognitive 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:613 — KikasaSHPCServant.UpdateSunCast 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.
D2 · Cognitive Complexity · KikasaCultistServant.AI (cognitive 17) · ×1
  • KikasaCultistServant.AI (cognitive 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:216 — KikasaCultistServant.AI 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.
D2 · Cognitive Complexity · KikasaCultistThunderOrb.AI (cognitive 17) · ×1
  • KikasaCultistThunderOrb.AI (cognitive 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistThunderOrb.cs:82 — KikasaCultistThunderOrb.AI 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.
D2 · Cognitive Complexity · KikasaDestroyerBloodJet.AI (cognitive 17) · ×1
  • KikasaDestroyerBloodJet.AI (cognitive 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerBloodJet.cs:87 — KikasaDestroyerBloodJet.AI 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.
D2 · Cognitive Complexity · KikasaEmpressServant.UpdateRibbon (cognitive 17) · ×1
  • KikasaEmpressServant.UpdateRibbon (cognitive 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:605 — KikasaEmpressServant.UpdateRibbon 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.
D2 · Cognitive Complexity · KikasaEyeServant.DrawGlow (cognitive 17) · ×1
  • KikasaEyeServant.DrawGlow (cognitive 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:896 — KikasaEyeServant.DrawGlow 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.
D2 · Cognitive Complexity · KikasaFesterSerpentServant.DrawChain (cognitive 17) · ×1
  • KikasaFesterSerpentServant.DrawChain (cognitive 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:927 — KikasaFesterSerpentServant.DrawChain 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.
D2 · Cognitive Complexity · KikasaFishronServant.OverrideFrame (cognitive 17) · ×1
  • KikasaFishronServant.OverrideFrame (cognitive 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1027 — KikasaFishronServant.OverrideFrame 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.
D2 · Cognitive Complexity · KikasaGolemServant.AI (cognitive 17) · ×1
  • KikasaGolemServant.AI (cognitive 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:235 — KikasaGolemServant.AI 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.
D2 · Cognitive Complexity · KikasaKingSlimeServant.WaveImpact (cognitive 17) · ×1
  • KikasaKingSlimeServant.WaveImpact (cognitive 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:854 — KikasaKingSlimeServant.WaveImpact 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.
D2 · Cognitive Complexity · KikasaMoonLordServant.BodyScale (cognitive 17) · ×1
  • KikasaMoonLordServant.BodyScale (cognitive 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1072 — KikasaMoonLordServant.BodyScale 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.
D2 · Cognitive Complexity · KikasaQueenGelMine.PreDraw (cognitive 17) · ×1
  • KikasaQueenGelMine.PreDraw (cognitive 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenGelMine.cs:334 — KikasaQueenGelMine.PreDraw 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.
D2 · Cognitive Complexity · KikasaCavitationOrb.AI (cognitive 17) · ×1
  • KikasaCavitationOrb.AI (cognitive 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaCavitationOrb.cs:79 — KikasaCavitationOrb.AI 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.
D2 · Cognitive Complexity · KikasaTwinsServant.UpdateFlame (cognitive 17) · ×1
  • KikasaTwinsServant.UpdateFlame (cognitive 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:791 — KikasaTwinsServant.UpdateFlame 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.
D2 · Cognitive Complexity · KikasaWallOfFleshServant.AI (cognitive 17) · ×1
  • KikasaWallOfFleshServant.AI (cognitive 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:216 — KikasaWallOfFleshServant.AI 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.
D2 · Cognitive Complexity · KikasaThrallMeltFX.Draw (cognitive 17) · ×1
  • KikasaThrallMeltFX.Draw (cognitive 17) Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallMeltFX.cs:234 — KikasaThrallMeltFX.Draw 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.
D2 · Cognitive Complexity · KikasaTipPanel.Draw (cognitive 17) · ×1
  • KikasaTipPanel.Draw (cognitive 17) Content/LegendWeapon/KikasaLegend/UI/KikasaHudTooltip.cs:37 — KikasaTipPanel.Draw 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.
D2 · Cognitive Complexity · KikasaPanoramaUI.DrawVault (cognitive 17) · ×1
  • KikasaPanoramaUI.DrawVault (cognitive 17) Content/LegendWeapon/KikasaLegend/UI/Panorama/KikasaPanoramaUI.cs:1859 — KikasaPanoramaUI.DrawVault 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.
D2 · Cognitive Complexity · KikasaServantWheelController.HandleWheelMouse (cognitive 17) · ×1
  • KikasaServantWheelController.HandleWheelMouse (cognitive 17) Content/LegendWeapon/KikasaLegend/UI/ServantWheel/KikasaServantWheelController.cs:167 — KikasaServantWheelController.HandleWheelMouse 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.
D2 · Cognitive Complexity · CrimsonRendSlash.Colliding (cognitive 17) · ×1
  • CrimsonRendSlash.Colliding (cognitive 17) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1372 — CrimsonRendSlash.Colliding 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.
D2 · Cognitive Complexity · CrimsonSweepSlash.Colliding (cognitive 17) · ×1
  • CrimsonSweepSlash.Colliding (cognitive 17) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1083 — CrimsonSweepSlash.Colliding 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.
D2 · Cognitive Complexity · OniMeiCombat.OnExecuteStrikeHit (cognitive 17) · ×1
  • OniMeiCombat.OnExecuteStrikeHit (cognitive 17) Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiCombat.cs:623 — OniMeiCombat.OnExecuteStrikeHit 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.
D2 · Cognitive Complexity · OniMeiStrikes.SpawnSeverLine (cognitive 17) · ×1
  • OniMeiStrikes.SpawnSeverLine (cognitive 17) Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiStrikes.cs:747 — OniMeiStrikes.SpawnSeverLine 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.
D2 · Cognitive Complexity · OniFlashStep.ResolveExecutionTargetAndTryFinale (cognitive 17) · ×1
  • OniFlashStep.ResolveExecutionTargetAndTryFinale (cognitive 17) Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashStep.cs:699 — OniFlashStep.ResolveExecutionTargetAndTryFinale 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.
D2 · Cognitive Complexity · OniOmokage.Imprint (cognitive 17) · ×1
  • OniOmokage.Imprint (cognitive 17) Content/LegendWeapon/OnikiriLegend/OniOmokages/OniOmokage.cs:208 — OniOmokage.Imprint 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.
D2 · Cognitive Complexity · OniOmokageRender.DrawFallbackDolls (cognitive 17) · ×1
  • OniOmokageRender.DrawFallbackDolls (cognitive 17) Content/LegendWeapon/OnikiriLegend/OniOmokages/OniOmokageRender.cs:407 — OniOmokageRender.DrawFallbackDolls 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.
D2 · Cognitive Complexity · OnikiriPlayer.ResolveEngraveHoriLit (cognitive 17) · ×1
  • OnikiriPlayer.ResolveEngraveHoriLit (cognitive 17) Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs:3233 — OnikiriPlayer.ResolveEngraveHoriLit 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.
D2 · Cognitive Complexity · SakuraRangedSlashProj.AI (cognitive 17) · ×1
  • SakuraRangedSlashProj.AI (cognitive 17) Content/LegendWeapon/OnikiriLegend/OnikiriRebuild/SakuraRangedSlashProj.cs:50 — SakuraRangedSlashProj.AI 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.
D2 · Cognitive Complexity · OnikiriTutorialPlayer.TickTutorial (cognitive 17) · ×1
  • OnikiriTutorialPlayer.TickTutorial (cognitive 17) Content/LegendWeapon/OnikiriLegend/Tutorial/OnikiriTutorialPlayer.cs:105 — OnikiriTutorialPlayer.TickTutorial 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.
D2 · Cognitive Complexity · OnikiriTutorialRenderer.UpdateInput (cognitive 17) · ×1
  • OnikiriTutorialRenderer.UpdateInput (cognitive 17) Content/LegendWeapon/OnikiriLegend/Tutorial/OnikiriTutorialRenderer.cs:79 — OnikiriTutorialRenderer.UpdateInput 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.
D2 · Cognitive Complexity · OniTooltipPanel.Draw (cognitive 17) · ×1
  • OniTooltipPanel.Draw (cognitive 17) Content/LegendWeapon/OnikiriLegend/UI/OniHudTooltipOverlay.cs:33 — OniTooltipPanel.Draw 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.
D2 · Cognitive Complexity · OniRope.Update (cognitive 17) · ×1
  • OniRope.Update (cognitive 17) Content/LegendWeapon/OnikiriLegend/UI/OniRope.cs:37 — OniRope.Update 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.
D2 · Cognitive Complexity · OniSigilUI.DrawHoverPartnerThreads (cognitive 17) · ×1
  • OniSigilUI.DrawHoverPartnerThreads (cognitive 17) Content/LegendWeapon/OnikiriLegend/UI/OniSigilUI.cs:884 — OniSigilUI.DrawHoverPartnerThreads 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.
D2 · Cognitive Complexity · CyberPrismLaserProj.AI (cognitive 17) · ×1
  • CyberPrismLaserProj.AI (cognitive 17) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberPrismLaserProj.cs:97 — CyberPrismLaserProj.AI 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.
D2 · Cognitive Complexity · CyberspacePlayer.ActivateAuthority (cognitive 17) · ×1
  • CyberspacePlayer.ActivateAuthority (cognitive 17) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspacePlayer.cs:297 — CyberspacePlayer.ActivateAuthority 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.
D2 · Cognitive Complexity · CyberDomainFreeze.UpdateAuthoritativeNPCs (cognitive 17) · ×1
  • CyberDomainFreeze.UpdateAuthoritativeNPCs (cognitive 17) Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.cs:519 — CyberDomainFreeze.UpdateAuthoritativeNPCs 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.
D2 · Cognitive Complexity · SniperOpticModule.OnPlayerUpdate (cognitive 17) · ×1
  • SniperOpticModule.OnPlayerUpdate (cognitive 17) Content/LegendWeapon/SHPCLegend/Modules/Optic/SniperOpticModule.cs:88 — SniperOpticModule.OnPlayerUpdate 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.
D2 · Cognitive Complexity · SHPCBeamSegmentProj.AI (cognitive 17) · ×1
  • SHPCBeamSegmentProj.AI (cognitive 17) Content/LegendWeapon/SHPCLegend/Modules/Stock/LightStockModule.cs:165 — SHPCBeamSegmentProj.AI 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.
D2 · Cognitive Complexity · BssHead.PreDraw (cognitive 17) · ×1
  • BssHead.PreDraw (cognitive 17) Content/NPCs/BloomsandSerpents/BssHead.cs:823 — BssHead.PreDraw 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.
D2 · Cognitive Complexity · BrainBloodRainState.OnUpdate (cognitive 17) · ×1
  • BrainBloodRainState.OnUpdate (cognitive 17) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainBloodRainState.cs:50 — BrainBloodRainState.OnUpdate 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.
D2 · Cognitive Complexity · DestroyerCoilCrushState.OnUpdate (cognitive 17) · ×1
  • DestroyerCoilCrushState.OnUpdate (cognitive 17) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerCoilCrushState.cs:74 — DestroyerCoilCrushState.OnUpdate 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.
D2 · Cognitive Complexity · DestroyerDashCooldownState.OnUpdate (cognitive 17) · ×1
  • DestroyerDashCooldownState.OnUpdate (cognitive 17) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerDashingState.cs:121 — DestroyerDashCooldownState.OnUpdate 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.
D2 · Cognitive Complexity · EowGeyserProj.AI (cognitive 17) · ×1
  • EowGeyserProj.AI (cognitive 17) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowGeyserProj.cs:54 — EowGeyserProj.AI 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.
D2 · Cognitive Complexity · EowHuskMinesState.OnUpdate (cognitive 17) · ×1
  • EowHuskMinesState.OnUpdate (cognitive 17) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowHuskMinesState.cs:42 — EowHuskMinesState.OnUpdate 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.
D2 · Cognitive Complexity · EmpressArenaPlayer.PreUpdateMovement (cognitive 17) · ×1
  • EmpressArenaPlayer.PreUpdateMovement (cognitive 17) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Core/EmpressArena.cs:118 — EmpressArenaPlayer.PreUpdateMovement 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.
D2 · Cognitive Complexity · EmpressFinaleState.Final (cognitive 17) · ×1
  • EmpressFinaleState.Final (cognitive 17) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/States/EmpressFinaleState.cs:341 — EmpressFinaleState.Final 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.
D2 · Cognitive Complexity · EmpressSunDanceState.OnUpdate (cognitive 17) · ×1
  • EmpressSunDanceState.OnUpdate (cognitive 17) Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/States/EmpressSunDanceState.cs:52 — EmpressSunDanceState.OnUpdate 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.
D2 · Cognitive Complexity · EocBlindsideCrossState.UpdateVanish (cognitive 17) · ×1
  • EocBlindsideCrossState.UpdateVanish (cognitive 17) Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocBlindsideCrossState.cs:116 — EocBlindsideCrossState.UpdateVanish 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.
D2 · Cognitive Complexity · EocDeathState.UpdateConvulsion (cognitive 17) · ×1
  • EocDeathState.UpdateConvulsion (cognitive 17) Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocDeathState.cs:100 — EocDeathState.UpdateConvulsion 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.
D2 · Cognitive Complexity · EocMaelstromState.UpdateTripleDash (cognitive 17) · ×1
  • EocMaelstromState.UpdateTripleDash (cognitive 17) Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocMaelstromState.cs:226 — EocMaelstromState.UpdateTripleDash 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.
D2 · Cognitive Complexity · EocMawDragState.UpdateRealDash (cognitive 17) · ×1
  • EocMawDragState.UpdateRealDash (cognitive 17) Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/States/EocMawDragState.cs:317 — EocMawDragState.UpdateRealDash 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.
D2 · Cognitive Complexity · GolemFistAI.UpdateThrusterVisual (cognitive 17) · ×1
  • GolemFistAI.UpdateThrusterVisual (cognitive 17) Content/NPCs/BrutalNPCs/BrutalGolem/GolemFistAI.cs:122 — GolemFistAI.UpdateThrusterVisual 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.
D2 · Cognitive Complexity · GolemShockWave.AI (cognitive 17) · ×1
  • GolemShockWave.AI (cognitive 17) Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemShockWave.cs:26 — GolemShockWave.AI 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.
D2 · Cognitive Complexity · GolemRenderHelper.DrawFistThruster (cognitive 17) · ×1
  • GolemRenderHelper.DrawFistThruster (cognitive 17) Content/NPCs/BrutalNPCs/BrutalGolem/Rendering/GolemRenderHelper.cs:200 — GolemRenderHelper.DrawFistThruster 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.
D2 · Cognitive Complexity · GolemFistWindupState.OnUpdate (cognitive 17) · ×1
  • GolemFistWindupState.OnUpdate (cognitive 17) Content/NPCs/BrutalNPCs/BrutalGolem/States/Fists/GolemFistStates.cs:60 — GolemFistWindupState.OnUpdate 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.
D2 · Cognitive Complexity · KingSlimeEngulfState.SyncClientPhase (cognitive 17) · ×1
  • KingSlimeEngulfState.SyncClientPhase (cognitive 17) Content/NPCs/BrutalNPCs/BrutalKingSlime/States/KingSlimeEngulfState.cs:537 — KingSlimeEngulfState.SyncClientPhase 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.
D2 · Cognitive Complexity · CultistCometVolleyState.OnUpdate (cognitive 17) · ×1
  • CultistCometVolleyState.OnUpdate (cognitive 17) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistCometVolleyState.cs:39 — CultistCometVolleyState.OnUpdate 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.
D2 · Cognitive Complexity · TwinsRenderHelper.DrawSyncPhaseTransitionEffect (cognitive 17) · ×1
  • TwinsRenderHelper.DrawSyncPhaseTransitionEffect (cognitive 17) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Rendering/TwinsRenderHelper.cs:843 — TwinsRenderHelper.DrawSyncPhaseTransitionEffect 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.
D2 · Cognitive Complexity · TwinsScissorRayState.ExecuteLockPhase (cognitive 17) · ×1
  • TwinsScissorRayState.ExecuteLockPhase (cognitive 17) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsScissorRayState.cs:117 — TwinsScissorRayState.ExecuteLockPhase 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.
D2 · Cognitive Complexity · RetinazerVerticalBarrageState.OnUpdate (cognitive 17) · ×1
  • RetinazerVerticalBarrageState.OnUpdate (cognitive 17) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerVerticalBarrageState.cs:68 — RetinazerVerticalBarrageState.OnUpdate 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.
D2 · Cognitive Complexity · MLordLocomotion.UpdateBody (cognitive 17) · ×1
  • MLordLocomotion.UpdateBody (cognitive 17) Content/NPCs/BrutalNPCs/BrutalMoonLord/Core/MLordLocomotion.cs:546 — MLordLocomotion.UpdateBody 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.
D2 · Cognitive Complexity · MoonLordCoreAI.EvaluateGlobalTransitions (cognitive 17) · ×1
  • MoonLordCoreAI.EvaluateGlobalTransitions (cognitive 17) Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordCoreAI.cs:185 — MoonLordCoreAI.EvaluateGlobalTransitions 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.
D2 · Cognitive Complexity · MoonLordHeadAI.UpdateAlive (cognitive 17) · ×1
  • MoonLordHeadAI.UpdateAlive (cognitive 17) Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordHeadAI.cs:82 — MoonLordHeadAI.UpdateAlive 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.
D2 · Cognitive Complexity · MLordCoreExposureState.OnUpdate (cognitive 17) · ×1
  • MLordCoreExposureState.OnUpdate (cognitive 17) Content/NPCs/BrutalNPCs/BrutalMoonLord/States/MLordCoreExposureState.cs:52 — MLordCoreExposureState.OnUpdate 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.
D2 · Cognitive Complexity · MLordCrescentCloseState.GetEyeReplayArcs (cognitive 17) · ×1
  • MLordCrescentCloseState.GetEyeReplayArcs (cognitive 17) Content/NPCs/BrutalNPCs/BrutalMoonLord/States/MLordCrescentCloseState.cs:83 — MLordCrescentCloseState.GetEyeReplayArcs 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.
D2 · Cognitive Complexity · MLordIntroState.UpdateAssembly (cognitive 17) · ×1
  • MLordIntroState.UpdateAssembly (cognitive 17) Content/NPCs/BrutalNPCs/BrutalMoonLord/States/MLordIntroState.cs:100 — MLordIntroState.UpdateAssembly 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.
D2 · Cognitive Complexity · PlanteraSporeAI.AI (cognitive 17) · ×1
  • PlanteraSporeAI.AI (cognitive 17) Content/NPCs/BrutalNPCs/BrutalPlantera/PlanteraSporeAI.cs:54 — PlanteraSporeAI.AI 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.
D2 · Cognitive Complexity · PlanteraTentacleRingState.OnUpdate (cognitive 17) · ×1
  • PlanteraTentacleRingState.OnUpdate (cognitive 17) Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraTentacleRingState.cs:54 — PlanteraTentacleRingState.OnUpdate 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.
D2 · Cognitive Complexity · PlanteraVineFeastState.UpdateDrag (cognitive 17) · ×1
  • PlanteraVineFeastState.UpdateDrag (cognitive 17) Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraVineFeastState.cs:344 — PlanteraVineFeastState.UpdateDrag 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.
D2 · Cognitive Complexity · BrutalQueenBeeAI.UpdateMarkVisuals (cognitive 17) · ×1
  • BrutalQueenBeeAI.UpdateMarkVisuals (cognitive 17) Content/NPCs/BrutalNPCs/BrutalQueenBee/BrutalQueenBeeAI.cs:378 — BrutalQueenBeeAI.UpdateMarkVisuals 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.
D2 · Cognitive Complexity · QueenCrystalPrisonWaltzState.FireWaltzBeats (cognitive 17) · ×1
  • QueenCrystalPrisonWaltzState.FireWaltzBeats (cognitive 17) Content/NPCs/BrutalNPCs/BrutalQueenSlime/States/QueenCrystalPrisonWaltzState.cs:417 — QueenCrystalPrisonWaltzState.FireWaltzBeats 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.
D2 · Cognitive Complexity · HandGuardState.UpdateFlick (cognitive 17) · ×1
  • HandGuardState.UpdateFlick (cognitive 17) Content/NPCs/BrutalNPCs/BrutalSkeletron/States/Hands/SkeletronHandStates.cs:70 — HandGuardState.UpdateFlick 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.
D2 · Cognitive Complexity · SkeletronCurseDomainState.UpdateStalk (cognitive 17) · ×1
  • SkeletronCurseDomainState.UpdateStalk (cognitive 17) Content/NPCs/BrutalNPCs/BrutalSkeletron/States/SkeletronCurseDomainState.cs:93 — SkeletronCurseDomainState.UpdateStalk 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.
D2 · Cognitive Complexity · PrimeGuillotineSpinState.OnUpdate (cognitive 17) · ×1
  • PrimeGuillotineSpinState.OnUpdate (cognitive 17) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/PrimeGuillotineSpinState.cs:33 — PrimeGuillotineSpinState.OnUpdate 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.
D2 · Cognitive Complexity · PrimeViceExecutionState.PlayBeatEffects (cognitive 17) · ×1
  • PrimeViceExecutionState.PlayBeatEffects (cognitive 17) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/PrimeViceExecutionState.cs:273 — PrimeViceExecutionState.PlayBeatEffects 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.
D2 · Cognitive Complexity · WofHungryNetState.OnUpdate (cognitive 17) · ×1
  • WofHungryNetState.OnUpdate (cognitive 17) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/States/WofHungryNetState.cs:47 — WofHungryNetState.OnUpdate 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.
D2 · Cognitive Complexity · WofMawVortexState.UpdatePull (cognitive 17) · ×1
  • WofMawVortexState.UpdatePull (cognitive 17) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/States/WofMawVortexState.cs:80 — WofMawVortexState.UpdatePull 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.
D2 · Cognitive Complexity · WallOfFleshAI.Draw (cognitive 17) · ×1
  • WallOfFleshAI.Draw (cognitive 17) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/WallOfFleshAI.cs:501 — WallOfFleshAI.Draw 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.
D2 · Cognitive Complexity · NPCTalkUIBase.Update (cognitive 17) · ×1
  • NPCTalkUIBase.Update (cognitive 17) Content/NPCs/CommonUIs/NPCTalkUIBase.cs:129 — NPCTalkUIBase.Update 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.
D2 · Cognitive Complexity · FssBreachOmen.AI (cognitive 17) · ×1
  • FssBreachOmen.AI (cognitive 17) Content/NPCs/FestersandSerpents/Projectiles/FssBreachOmen.cs:31 — FssBreachOmen.AI 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.
D2 · Cognitive Complexity · FssPortalRushState.UpdateDiveIn (cognitive 17) · ×1
  • FssPortalRushState.UpdateDiveIn (cognitive 17) Content/NPCs/FestersandSerpents/States/FssPortalRushState.cs:146 — FssPortalRushState.UpdateDiveIn 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.
D2 · Cognitive Complexity · ScrapDebris.AI (cognitive 17) · ×1
  • ScrapDebris.AI (cognitive 17) Content/NPCs/ScrapCommanders/Projectiles/ScrapDebris.cs:44 — ScrapDebris.AI 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.
D2 · Cognitive Complexity · ScrapMortarShell.OnKill (cognitive 17) · ×1
  • ScrapMortarShell.OnKill (cognitive 17) Content/NPCs/ScrapCommanders/Projectiles/ScrapMortarShell.cs:77 — ScrapMortarShell.OnKill 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.
D2 · Cognitive Complexity · ShrimpVerletStrand.Update (cognitive 17) · ×1
  • ShrimpVerletStrand.Update (cognitive 17) Content/NPCs/SeaShrimp/Kinematics/ShrimpVerletStrand.cs:39 — ShrimpVerletStrand.Update 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.
D2 · Cognitive Complexity · SeaShrimpClawJabState.OnUpdate (cognitive 17) · ×1
  • SeaShrimpClawJabState.OnUpdate (cognitive 17) Content/NPCs/SeaShrimp/States/SeaShrimpClawJabState.cs:29 — SeaShrimpClawJabState.OnUpdate 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.
D2 · Cognitive Complexity · TBUGRiftPortalProj.SpawnAmbientParticles (cognitive 17) · ×1
  • TBUGRiftPortalProj.SpawnAmbientParticles (cognitive 17) Content/NPCs/TBUGs/TBUGRiftPortalProj.cs:184 — TBUGRiftPortalProj.SpawnAmbientParticles 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.
D2 · Cognitive Complexity · StoryProgress.LoadData (cognitive 17) · ×1
  • StoryProgress.LoadData (cognitive 17) Content/Narrative/Data/StoryProgress.cs:65 — StoryProgress.LoadData 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.
D2 · Cognitive Complexity · PRT_GhostRainDrop.AI (cognitive 17) · ×1
  • PRT_GhostRainDrop.AI (cognitive 17) Content/PRTTypes/PRT_GhostRainDrop.cs:79 — PRT_GhostRainDrop.AI 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.
D2 · Cognitive Complexity · PRT_TempleRubble.AI (cognitive 17) · ×1
  • PRT_TempleRubble.AI (cognitive 17) Content/PRTTypes/PRT_TempleRubble.cs:76 — PRT_TempleRubble.AI 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.
D2 · Cognitive Complexity · QuestBookGuidePlayer.OnStepEnter (cognitive 17) · ×1
  • QuestBookGuidePlayer.OnStepEnter (cognitive 17) Content/QuestLogs/Guide/QuestBookGuidePlayer.cs:367 — QuestBookGuidePlayer.OnStepEnter 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.
D2 · Cognitive Complexity · QuestBookGuidePlayer.PerformStepForPlayer (cognitive 17) · ×1
  • QuestBookGuidePlayer.PerformStepForPlayer (cognitive 17) Content/QuestLogs/Guide/QuestBookGuidePlayer.cs:512 — QuestBookGuidePlayer.PerformStepForPlayer 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.
D2 · Cognitive Complexity · HotwindQuestLogStyle.DrawFallbackBackground (cognitive 17) · ×1
  • HotwindQuestLogStyle.DrawFallbackBackground (cognitive 17) Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:62 — HotwindQuestLogStyle.DrawFallbackBackground 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.
D2 · Cognitive Complexity · ModifyDraedonNPC.PostAI (cognitive 17) · ×1
  • ModifyDraedonNPC.PostAI (cognitive 17) Content/Scenarios/Draedon/ModifyDraedonNPC.cs:53 — ModifyDraedonNPC.PostAI 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.
D2 · Cognitive Complexity · ShopHandle.GetMaterialValueRecursive (cognitive 17) · ×1
  • ShopHandle.GetMaterialValueRecursive (cognitive 17) Content/Scenarios/Draedon/PQCDs/DraedonShops/ShopHandle.cs:119 — ShopHandle.GetMaterialValueRecursive 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.
D2 · Cognitive Complexity · DungeonworldAmbientRender.UpdateBySystem (cognitive 17) · ×1
  • DungeonworldAmbientRender.UpdateBySystem (cognitive 17) Content/Scenarios/Dungeonworld/Ambience/DungeonworldAmbientRender.cs:53 — DungeonworldAmbientRender.UpdateBySystem 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.
D2 · Cognitive Complexity · GaolBossRoomWatcher.SealDoors (cognitive 17) · ×1
  • GaolBossRoomWatcher.SealDoors (cognitive 17) Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolBossRoomWatcher.cs:228 — GaolBossRoomWatcher.SealDoors 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.
D2 · Cognitive Complexity · GaolBossRoomWatcher.UnsealDoors (cognitive 17) · ×1
  • GaolBossRoomWatcher.UnsealDoors (cognitive 17) Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolBossRoomWatcher.cs:255 — GaolBossRoomWatcher.UnsealDoors 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.
D2 · Cognitive Complexity · ProofingHallRoom.HashScorch (cognitive 17) · ×1
  • ProofingHallRoom.HashScorch (cognitive 17) Content/Scenarios/Dungeonworld/Gen/BossRooms/ProofingHallRoom.cs:343 — ProofingHallRoom.HashScorch 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.
D2 · Cognitive Complexity · ProofingHallScene.UpdateBySystem (cognitive 17) · ×1
  • ProofingHallScene.UpdateBySystem (cognitive 17) Content/Scenarios/Dungeonworld/Gen/BossRooms/ProofingHallScene.cs:66 — ProofingHallScene.UpdateBySystem 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.
D2 · Cognitive Complexity · L1Style.AgeLightsInRect (cognitive 17) · ×1
  • L1Style.AgeLightsInRect (cognitive 17) Content/Scenarios/Dungeonworld/Gen/Layers/L1/L1Style.cs:226 — L1Style.AgeLightsInRect 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.
D2 · Cognitive Complexity · L3Content.PlanAndBuild (cognitive 17) · ×1
  • L3Content.PlanAndBuild (cognitive 17) Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Content.cs:80 — L3Content.PlanAndBuild 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.
D2 · Cognitive Complexity · L3Palette.MoldUnderShelves (cognitive 17) · ×1
  • L3Palette.MoldUnderShelves (cognitive 17) Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Palette.cs:234 — L3Palette.MoldUnderShelves 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.
D2 · Cognitive Complexity · L3Scatter.WallBookNooks (cognitive 17) · ×1
  • L3Scatter.WallBookNooks (cognitive 17) Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Scatter.cs:71 — L3Scatter.WallBookNooks 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.
D2 · Cognitive Complexity · L5Leviathan.TryBuild (cognitive 17) · ×1
  • L5Leviathan.TryBuild (cognitive 17) Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Leviathan.cs:136 — L5Leviathan.TryBuild 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.
D2 · Cognitive Complexity · L6Palette.ScorchDisk (cognitive 17) · ×1
  • L6Palette.ScorchDisk (cognitive 17) Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Palette.cs:114 — L6Palette.ScorchDisk 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.
D2 · Cognitive Complexity · AshfallStratum.CollectCrackedRooms (cognitive 17) · ×1
  • AshfallStratum.CollectCrackedRooms (cognitive 17) Content/Scenarios/Dungeonworld/Gen/Zones/AshfallStratum.cs:136 — AshfallStratum.CollectCrackedRooms 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.
D2 · Cognitive Complexity · FoundryOverseer.UpdateStunned (cognitive 17) · ×1
  • FoundryOverseer.UpdateStunned (cognitive 17) Content/Scenarios/Dungeonworld/NPCs/FoundryOverseer.cs:1004 — FoundryOverseer.UpdateStunned 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.
D2 · Cognitive Complexity · GaolAnchorProj.AI (cognitive 17) · ×1
  • GaolAnchorProj.AI (cognitive 17) Content/Scenarios/Dungeonworld/NPCs/GaolAnchorWeapon.cs:84 — GaolAnchorProj.AI 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.
D2 · Cognitive Complexity · DungeonworldTransitionGate.PostUpdateEverything (cognitive 17) · ×1
  • DungeonworldTransitionGate.PostUpdateEverything (cognitive 17) Content/Scenarios/Dungeonworld/UI/DungeonworldTransitionGate.cs:61 — DungeonworldTransitionGate.PostUpdateEverything 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.
D2 · Cognitive Complexity · HadalTerrainPlanner.BuildSeabed (cognitive 17) · ×1
  • HadalTerrainPlanner.BuildSeabed (cognitive 17) Content/Scenarios/Hadalworld/Gen/Core/HadalTerrainPlan.cs:167 — HadalTerrainPlanner.BuildSeabed 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.
D2 · Cognitive Complexity · HadalworldTransitionGate.PostUpdateEverything (cognitive 17) · ×1
  • HadalworldTransitionGate.PostUpdateEverything (cognitive 17) Content/Scenarios/Hadalworld/UI/HadalworldTransitionGate.cs:60 — HadalworldTransitionGate.PostUpdateEverything 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.
D2 · Cognitive Complexity · FishoilQuestEntry.ConsumeAvailableFish (cognitive 17) · ×1
  • FishoilQuestEntry.ConsumeAvailableFish (cognitive 17) Content/Scenarios/Helen/Quest/FishoilQuest/FishoilQuestEntry.cs:75 — FishoilQuestEntry.ConsumeAvailableFish 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.
D2 · Cognitive Complexity · OniRainDescentTransition.SpawnStageFx (cognitive 17) · ×1
  • OniRainDescentTransition.SpawnStageFx (cognitive 17) Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:175 — OniRainDescentTransition.SpawnStageFx 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.
D2 · Cognitive Complexity · OniRainExitTransition.SpawnStageFx (cognitive 17) · ×1
  • OniRainExitTransition.SpawnStageFx (cognitive 17) Content/Scenarios/Kiame/Overlay/OniRainExitTransition.cs:132 — OniRainExitTransition.SpawnStageFx 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.
D2 · Cognitive Complexity · KiyumeCrowRoost.AuthorityTick (cognitive 17) · ×1
  • KiyumeCrowRoost.AuthorityTick (cognitive 17) Content/Scenarios/Kiyume/Ambience/KiyumeCrowRoost.cs:110 — KiyumeCrowRoost.AuthorityTick 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.
D2 · Cognitive Complexity · KiyumeCrowRoost.Draw (cognitive 17) · ×1
  • KiyumeCrowRoost.Draw (cognitive 17) Content/Scenarios/Kiyume/Ambience/KiyumeCrowRoost.cs:437 — KiyumeCrowRoost.Draw 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.
D2 · Cognitive Complexity · KiyumeGroundFogRender.SampleGround (cognitive 17) · ×1
  • KiyumeGroundFogRender.SampleGround (cognitive 17) Content/Scenarios/Kiyume/Fog/KiyumeGroundFogRender.cs:187 — KiyumeGroundFogRender.SampleGround 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.
D2 · Cognitive Complexity · KiyumeHauntDirector.PumpCortege (cognitive 17) · ×1
  • KiyumeHauntDirector.PumpCortege (cognitive 17) Content/Scenarios/Kiyume/NPCs/KiyumeHauntDirector.cs:227 — KiyumeHauntDirector.PumpCortege 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.
D2 · Cognitive Complexity · KiyumeHound.SampleSenses (cognitive 17) · ×1
  • KiyumeHound.SampleSenses (cognitive 17) Content/Scenarios/Kiyume/NPCs/KiyumeHound.cs:213 — KiyumeHound.SampleSenses 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.
D2 · Cognitive Complexity · OldDukeShopInteraction.TryPurchaseItem (cognitive 17) · ×1
  • OldDukeShopInteraction.TryPurchaseItem (cognitive 17) Content/Scenarios/OldDuke/OldDukeShops/OldDukeShopInteraction.cs:203 — OldDukeShopInteraction.TryPurchaseItem 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.
D2 · Cognitive Complexity · OldNetLurkerICE.PreDraw (cognitive 17) · ×1
  • OldNetLurkerICE.PreDraw (cognitive 17) Content/Scenarios/OldNet/NPCs/OldNetLurkerICE.cs:262 — OldNetLurkerICE.PreDraw 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.
D2 · Cognitive Complexity · OldNetRelicTile.TryWrite (cognitive 17) · ×1
  • OldNetRelicTile.TryWrite (cognitive 17) Content/Scenarios/OldNet/Tiles/OldNetRelicTile.cs:52 — OldNetRelicTile.TryWrite 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.
D2 · Cognitive Complexity · ModifySupCalNPC.AI (cognitive 17) · ×1
  • ModifySupCalNPC.AI (cognitive 17) Content/Scenarios/SupCal/ModifySupCalNPCs/ModifySupCalNPC.cs:62 — ModifySupCalNPC.AI 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.
D2 · Cognitive Complexity · IndustrialSkyIslandGen.TryFindFreeSpot (cognitive 17) · ×1
  • IndustrialSkyIslandGen.TryFindFreeSpot (cognitive 17) Content/Structures/IndustrialSkyIslandGen.cs:309 — IndustrialSkyIslandGen.TryFindFreeSpot 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.
D2 · Cognitive Complexity · TimeFreezeSystem.SynchronizeEntitySources (cognitive 17) · ×1
  • TimeFreezeSystem.SynchronizeEntitySources (cognitive 17) Content/TimeFreezes/TimeFreezeSystem.cs:945 — TimeFreezeSystem.SynchronizeEntitySources 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.
D2 · Cognitive Complexity · EntryDecisionUI.HandleSlotInput (cognitive 17) · ×1
  • EntryDecisionUI.HandleSlotInput (cognitive 17) Content/UIs/EntryDecisions/EntryDecisionUI.cs:289 — EntryDecisionUI.HandleSlotInput 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.
D2 · Cognitive Complexity · WorldGenSettingsCategory.DrawRowExtra (cognitive 17) · ×1
  • WorldGenSettingsCategory.DrawRowExtra (cognitive 17) Content/UIs/OverhaulSettings/WorldGenSettingsCategory.cs:411 — WorldGenSettingsCategory.DrawRowExtra 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.
D2 · Cognitive Complexity · GhostHandAbility.Update (cognitive 17) · ×1
  • GhostHandAbility.Update (cognitive 17) Content/Wraiths/Abilities/GhostHandAbility.cs:100 — GhostHandAbility.Update 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.
D2 · Cognitive Complexity · GenericSeizurePerformance.Update (cognitive 17) · ×1
  • GenericSeizurePerformance.Update (cognitive 17) Content/Wraiths/Deaths/GenericSeizurePerformance.cs:42 — GenericSeizurePerformance.Update 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.
D2 · Cognitive Complexity · HandSeizurePerformance.Update (cognitive 17) · ×1
  • HandSeizurePerformance.Update (cognitive 17) Content/Wraiths/Deaths/Performances/HandSeizurePerformance.cs:162 — HandSeizurePerformance.Update 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.
D2 · Cognitive Complexity · MSRef.Compile (cognitive 17) · ×1
  • MSRef.Compile (cognitive 17) OtherMods/MagicStorage/MSRef.cs:140 — MSRef.Compile 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.
D2 · Cognitive Complexity · CWRRef.ApplyEnchantmentToItem (cognitive 16) · ×1
  • CWRRef.ApplyEnchantmentToItem (cognitive 16) CWRRef.cs:1340 — CWRRef.ApplyEnchantmentToItem 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.
D2 · Cognitive Complexity · Sandevistan.RecalculateAuthorityAggregate (cognitive 16) · ×1
  • Sandevistan.RecalculateAuthorityAggregate (cognitive 16) Content/Cyberwares/Implementation/Sandevistans/Sandevistan.cs:133 — Sandevistan.RecalculateAuthorityAggregate 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.
D2 · Cognitive Complexity · AshreignAmbience.UpdateLavaScan (cognitive 16) · ×1
  • AshreignAmbience.UpdateLavaScan (cognitive 16) Content/GameModes/BrutalMobs/Ambience/Ashreign/AshreignAmbience.cs:126 — AshreignAmbience.UpdateLavaScan 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.
D2 · Cognitive Complexity · BrinefumeAmbience.TryFindWaterSurface (cognitive 16) · ×1
  • BrinefumeAmbience.TryFindWaterSurface (cognitive 16) Content/GameModes/BrutalMobs/Ambience/Brinefume/BrinefumeAmbience.cs:413 — BrinefumeAmbience.TryFindWaterSurface 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.
D2 · Cognitive Complexity · FleshfenDewRainProj.AI (cognitive 16) · ×1
  • FleshfenDewRainProj.AI (cognitive 16) Content/GameModes/BrutalMobs/Ambience/Fleshfen/Projectiles/FleshfenDewRainProj.cs:101 — FleshfenDewRainProj.AI 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.
D2 · Cognitive Complexity · HollowdeepQuakeScan.PostUpdateProjectiles (cognitive 16) · ×1
  • HollowdeepQuakeScan.PostUpdateProjectiles (cognitive 16) Content/GameModes/BrutalMobs/Ambience/Hollowdeep/HollowdeepPlayer.cs:169 — HollowdeepQuakeScan.PostUpdateProjectiles 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.
D2 · Cognitive Complexity · LumindepthPlayer.TrySpawnVortex (cognitive 16) · ×1
  • LumindepthPlayer.TrySpawnVortex (cognitive 16) Content/GameModes/BrutalMobs/Ambience/Lumindepth/LumindepthPlayer.cs:58 — LumindepthPlayer.TrySpawnVortex 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.
D2 · Cognitive Complexity · MournfogAmbience.UpdateScratch (cognitive 16) · ×1
  • MournfogAmbience.UpdateScratch (cognitive 16) Content/GameModes/BrutalMobs/Ambience/Mournfog/MournfogAmbience.cs:189 — MournfogAmbience.UpdateScratch 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.
D2 · Cognitive Complexity · MournfogGrudgeRingProj.PreDraw (cognitive 16) · ×1
  • MournfogGrudgeRingProj.PreDraw (cognitive 16) Content/GameModes/BrutalMobs/Ambience/Mournfog/Projectiles/MournfogGrudgeRingProj.cs:242 — MournfogGrudgeRingProj.PreDraw 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.
D2 · Cognitive Complexity · NyxdepthPlayer.TryFindColumnSpot (cognitive 16) · ×1
  • NyxdepthPlayer.TryFindColumnSpot (cognitive 16) Content/GameModes/BrutalMobs/Ambience/Nyxdepth/NyxdepthPlayer.cs:98 — NyxdepthPlayer.TryFindColumnSpot 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.
D2 · Cognitive Complexity · RotmireVentSystem.PostUpdateEverything (cognitive 16) · ×1
  • RotmireVentSystem.PostUpdateEverything (cognitive 16) Content/GameModes/BrutalMobs/Ambience/Rotmire/RotmireVentSystem.cs:60 — RotmireVentSystem.PostUpdateEverything 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.
D2 · Cognitive Complexity · StarfallAmbientRender.UpdateBySystem (cognitive 16) · ×1
  • StarfallAmbientRender.UpdateBySystem (cognitive 16) Content/GameModes/BrutalMobs/Ambience/Starfall/StarfallAmbientRender.cs:150 — StarfallAmbientRender.UpdateBySystem 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.
D2 · Cognitive Complexity · StonewakeFX.TryFindGraniteAnchor (cognitive 16) · ×1
  • StonewakeFX.TryFindGraniteAnchor (cognitive 16) Content/GameModes/BrutalMobs/Ambience/Stonewake/StonewakeFX.cs:63 — StonewakeFX.TryFindGraniteAnchor 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.
D2 · Cognitive Complexity · SunkenduneAmbientRender.TrySpawnSwarm (cognitive 16) · ×1
  • SunkenduneAmbientRender.TrySpawnSwarm (cognitive 16) Content/GameModes/BrutalMobs/Ambience/Sunkendune/SunkenduneAmbientRender.cs:263 — SunkenduneAmbientRender.TrySpawnSwarm 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.
D2 · Cognitive Complexity · VerdantAmbientRender.DrawThornRing (cognitive 16) · ×1
  • VerdantAmbientRender.DrawThornRing (cognitive 16) Content/GameModes/BrutalMobs/Ambience/Verdant/VerdantAmbientRender.cs:121 — VerdantAmbientRender.DrawThornRing 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.
D2 · Cognitive Complexity · WoodsongAmbience.UpdateSoundSchedulers (cognitive 16) · ×1
  • WoodsongAmbience.UpdateSoundSchedulers (cognitive 16) Content/GameModes/BrutalMobs/Ambience/Woodsong/WoodsongAmbience.cs:271 — WoodsongAmbience.UpdateSoundSchedulers 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.
D2 · Cognitive Complexity · DdHammerConeOmen.AI (cognitive 16) · ×1
  • DdHammerConeOmen.AI (cognitive 16) Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdHammerConeOmen.cs:86 — DdHammerConeOmen.AI 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.
D2 · Cognitive Complexity · EclipseNPC.FirePayload (cognitive 16) · ×1
  • EclipseNPC.FirePayload (cognitive 16) Content/GameModes/BrutalMobs/Eclipse/EclipseNPC.cs:408 — EclipseNPC.FirePayload 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.
D2 · Cognitive Complexity · EMParryStanceProj.AI (cognitive 16) · ×1
  • EMParryStanceProj.AI (cognitive 16) Content/GameModes/BrutalMobs/EliteMove/Projectiles/EMParryStanceProj.cs:44 — EMParryStanceProj.AI 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.
D2 · Cognitive Complexity · FrostLegionNPC.PostAI (cognitive 16) · ×1
  • FrostLegionNPC.PostAI (cognitive 16) Content/GameModes/BrutalMobs/FrostLegion/FrostLegionNPC.cs:282 — FrostLegionNPC.PostAI 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.
D2 · Cognitive Complexity · FrmMiniBossNPC.NeedleActive (cognitive 16) · ×1
  • FrmMiniBossNPC.NeedleActive (cognitive 16) Content/GameModes/BrutalMobs/FrostMoon/FrmMiniBossNPC.cs:282 — FrmMiniBossNPC.NeedleActive 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.
D2 · Cognitive Complexity · JhBreachOmen.AI (cognitive 16) · ×1
  • JhBreachOmen.AI (cognitive 16) Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhBreachOmen.cs:51 — JhBreachOmen.AI 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.
D2 · Cognitive Complexity · LegionNPC.ScoutStep (cognitive 16) · ×1
  • LegionNPC.ScoutStep (cognitive 16) Content/GameModes/BrutalMobs/Legion/LegionNPC.cs:867 — LegionNPC.ScoutStep 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.
D2 · Cognitive Complexity · LegionNPC.ClownStep (cognitive 16) · ×1
  • LegionNPC.ClownStep (cognitive 16) Content/GameModes/BrutalMobs/Legion/LegionNPC.cs:1205 — LegionNPC.ClownStep 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.
D2 · Cognitive Complexity · LegionNPC.SquidStep (cognitive 16) · ×1
  • LegionNPC.SquidStep (cognitive 16) Content/GameModes/BrutalMobs/Legion/LegionNPC.cs:1274 — LegionNPC.SquidStep 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.
D2 · Cognitive Complexity · LegionSurfOmen.AI (cognitive 16) · ×1
  • LegionSurfOmen.AI (cognitive 16) Content/GameModes/BrutalMobs/Legion/Projectiles/LegionSurfOmen.cs:63 — LegionSurfOmen.AI 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.
D2 · Cognitive Complexity · MartiansNPC.TickTelegraph (cognitive 16) · ×1
  • MartiansNPC.TickTelegraph (cognitive 16) Content/GameModes/BrutalMobs/Martians/MartiansNPC.cs:415 — MartiansNPC.TickTelegraph 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.
D2 · Cognitive Complexity · MrtSaucerScanProj.AI (cognitive 16) · ×1
  • MrtSaucerScanProj.AI (cognitive 16) Content/GameModes/BrutalMobs/Martians/Projectiles/MrtSaucerScanProj.cs:53 — MrtSaucerScanProj.AI 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.
D2 · Cognitive Complexity · MushroomBrutalNPC.TickRoll (cognitive 16) · ×1
  • MushroomBrutalNPC.TickRoll (cognitive 16) Content/GameModes/BrutalMobs/Mushroom/MushroomBrutalNPC.cs:377 — MushroomBrutalNPC.TickRoll 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.
D2 · Cognitive Complexity · MushroomSporeMistTelegraph.AI (cognitive 16) · ×1
  • MushroomSporeMistTelegraph.AI (cognitive 16) Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomSporeMistTelegraph.cs:87 — MushroomSporeMistTelegraph.AI 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.
D2 · Cognitive Complexity · PmkClawCrossProj.PreDraw (cognitive 16) · ×1
  • PmkClawCrossProj.PreDraw (cognitive 16) Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkClawCrossProj.cs:171 — PmkClawCrossProj.PreDraw 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.
D2 · Cognitive Complexity · PmkRitualWispProj.AI (cognitive 16) · ×1
  • PmkRitualWispProj.AI (cognitive 16) Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkRitualWispProj.cs:80 — PmkRitualWispProj.AI 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.
D2 · Cognitive Complexity · PumpkinMoonNPC.TryStartEmberMove (cognitive 16) · ×1
  • PumpkinMoonNPC.TryStartEmberMove (cognitive 16) Content/GameModes/BrutalMobs/PumpkinMoon/PumpkinMoonNPC.cs:420 — PumpkinMoonNPC.TryStartEmberMove 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.
D2 · Cognitive Complexity · TempleDiveOmen.AI (cognitive 16) · ×1
  • TempleDiveOmen.AI (cognitive 16) Content/GameModes/BrutalMobs/Temple/Projectiles/TempleDiveOmen.cs:73 — TempleDiveOmen.AI 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.
D2 · Cognitive Complexity · GsVolleyBowScheme.GsShoot (cognitive 16) · ×1
  • GsVolleyBowScheme.GsShoot (cognitive 16) Content/GameModes/GodSmith/Weapons/Bows/GsVolleyBowScheme.cs:90 — GsVolleyBowScheme.GsShoot 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.
D2 · Cognitive Complexity · GsVolleyPlayer.PostUpdate (cognitive 16) · ×1
  • GsVolleyPlayer.PostUpdate (cognitive 16) Content/GameModes/GodSmith/Weapons/Bows/GsVolleyPlayer.cs:50 — GsVolleyPlayer.PostUpdate 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.
D2 · Cognitive Complexity · GsStarWrathFallProj.AI (cognitive 16) · ×1
  • GsStarWrathFallProj.AI (cognitive 16) Content/GameModes/GodSmith/Weapons/Broadswords/GsStarWrath.cs:281 — GsStarWrathFallProj.AI 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.
D2 · Cognitive Complexity · GsNebulaArcanum.GsProjPostAI (cognitive 16) · ×1
  • GsNebulaArcanum.GsProjPostAI (cognitive 16) Content/GameModes/GodSmith/Weapons/MagicCataclysm/GsNebulaArcanum.cs:43 — GsNebulaArcanum.GsProjPostAI 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.
D2 · Cognitive Complexity · GsDayBreakSpearProj.AI (cognitive 16) · ×1
  • GsDayBreakSpearProj.AI (cognitive 16) Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:388 — GsDayBreakSpearProj.AI 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.
D2 · Cognitive Complexity · GsMonkStaffT1Held.AdvanceSpin (cognitive 16) · ×1
  • GsMonkStaffT1Held.AdvanceSpin (cognitive 16) Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT1.cs:226 — GsMonkStaffT1Held.AdvanceSpin 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.
D2 · Cognitive Complexity · GameModeRenderer.DrawHoverPanel (cognitive 16) · ×1
  • GameModeRenderer.DrawHoverPanel (cognitive 16) Content/GameModes/UI/GameModeRenderer.cs:404 — GameModeRenderer.DrawHoverPanel 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.
D2 · Cognitive Complexity · Contagion.OnRemove (cognitive 16) · ×1
  • Contagion.OnRemove (cognitive 16) Content/HackTimes/Protocols/Contagion.cs:70 — Contagion.OnRemove 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.
D2 · Cognitive Complexity · PlayerHackAuthority.TickUpload (cognitive 16) · ×1
  • PlayerHackAuthority.TickUpload (cognitive 16) Content/HackTimes/PvP/PlayerHackNet.cs:324 — PlayerHackAuthority.TickUpload 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.
D2 · Cognitive Complexity · PlayerHackMirror.Tick (cognitive 16) · ×1
  • PlayerHackMirror.Tick (cognitive 16) Content/HackTimes/PvP/PlayerHackNet.cs:758 — PlayerHackMirror.Tick 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.
D2 · Cognitive Complexity · BossPartTargetType.TryDetectHovered (cognitive 16) · ×1
  • BossPartTargetType.TryDetectHovered (cognitive 16) Content/HackTimes/Targets/BossPartTargetType.cs:67 — BossPartTargetType.TryDetectHovered 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.
D2 · Cognitive Complexity · AutoCrafterTile.PreDraw (cognitive 16) · ×1
  • AutoCrafterTile.PreDraw (cognitive 16) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterTile.cs:88 — AutoCrafterTile.PreDraw 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.
D2 · Cognitive Complexity · CollectorArm.FindNearestItem (cognitive 16) · ×1
  • CollectorArm.FindNearestItem (cognitive 16) Content/Industrials/ElectricPowers/Collectors/CollectorArm.cs:124 — CollectorArm.FindNearestItem 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.
D2 · Cognitive Complexity · CollectorArm.State_Grasping (cognitive 16) · ×1
  • CollectorArm.State_Grasping (cognitive 16) Content/Industrials/ElectricPowers/Collectors/CollectorArm.cs:610 — CollectorArm.State_Grasping 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.
D2 · Cognitive Complexity · CrusherTP.UpdateMachine (cognitive 16) · ×1
  • CrusherTP.UpdateMachine (cognitive 16) Content/Industrials/ElectricPowers/Crushers/CrusherTP.cs:109 — CrusherTP.UpdateMachine 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.
D2 · Cognitive Complexity · HealAuraRender.PreDrawEverything (cognitive 16) · ×1
  • HealAuraRender.PreDrawEverything (cognitive 16) Content/Industrials/ElectricPowers/HealingStations/HealAuraRender.cs:18 — HealAuraRender.PreDrawEverything 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.
D2 · Cognitive Complexity · HerbFarmerTP.TryPlantSeed (cognitive 16) · ×1
  • HerbFarmerTP.TryPlantSeed (cognitive 16) Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerTP.cs:460 — HerbFarmerTP.TryPlantSeed 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.
D2 · Cognitive Complexity · IncineratorTP.CompleteSmelting (cognitive 16) · ×1
  • IncineratorTP.CompleteSmelting (cognitive 16) Content/Industrials/ElectricPowers/Incinerators/IncineratorTP.cs:165 — IncineratorTP.CompleteSmelting 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.
D2 · Cognitive Complexity · LumberjackSaw.FindGroundBelowTree (cognitive 16) · ×1
  • LumberjackSaw.FindGroundBelowTree (cognitive 16) Content/Industrials/ElectricPowers/Lumberjacks/LumberjackSaw.cs:523 — LumberjackSaw.FindGroundBelowTree 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.
D2 · Cognitive Complexity · WGGLumberjackSaw.FindNearestTree (cognitive 16) · ×1
  • WGGLumberjackSaw.FindNearestTree (cognitive 16) Content/Industrials/ElectricPowers/Lumberjacks/WGGLumberjack.cs:728 — WGGLumberjackSaw.FindNearestTree 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.
D2 · Cognitive Complexity · MiningMachineSystem.LoadStandardOres (cognitive 16) · ×1
  • MiningMachineSystem.LoadStandardOres (cognitive 16) Content/Industrials/ElectricPowers/MiningMachines/MiningMachineSystem.cs:466 — MiningMachineSystem.LoadStandardOres 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.
D2 · Cognitive Complexity · MiningMachineUI.DrawReport (cognitive 16) · ×1
  • MiningMachineUI.DrawReport (cognitive 16) Content/Industrials/ElectricPowers/MiningMachines/MiningMachineUI.cs:557 — MiningMachineUI.DrawReport 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.
D2 · Cognitive Complexity · RecyclerTP.UpdateMachine (cognitive 16) · ×1
  • RecyclerTP.UpdateMachine (cognitive 16) Content/Industrials/ElectricPowers/Recyclers/RecyclerTP.cs:116 — RecyclerTP.UpdateMachine 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.
D2 · Cognitive Complexity · ShieldDomeFX.OnAbsorb (cognitive 16) · ×1
  • ShieldDomeFX.OnAbsorb (cognitive 16) Content/Industrials/ElectricPowers/ShieldGenerators/ShieldDomeRender.cs:47 — ShieldDomeFX.OnAbsorb 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.
D2 · Cognitive Complexity · ShimmerTransmuterUI.DrawStatusRow (cognitive 16) · ×1
  • ShimmerTransmuterUI.DrawStatusRow (cognitive 16) Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterUI.cs:443 — ShimmerTransmuterUI.DrawStatusRow 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.
D2 · Cognitive Complexity · TeleportWatcher.HookTeleport (cognitive 16) · ×1
  • TeleportWatcher.HookTeleport (cognitive 16) Content/Industrials/ElectricPowers/TeleportStations/TeleportStationFX.cs:306 — TeleportWatcher.HookTeleport 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.
D2 · Cognitive Complexity · TeslaGuardRingDraw.PreDrawEverything (cognitive 16) · ×1
  • TeslaGuardRingDraw.PreDrawEverything (cognitive 16) Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:560 — TeslaGuardRingDraw.PreDrawEverything 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.
D2 · Cognitive Complexity · ThrowerTP.UpdateMachine (cognitive 16) · ×1
  • ThrowerTP.UpdateMachine (cognitive 16) Content/Industrials/ElectricPowers/Throwers/ThrowerTP.cs:244 — ThrowerTP.UpdateMachine 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.
D2 · Cognitive Complexity · BiomassGeneratorTP.UpdateClientVisual (cognitive 16) · ×1
  • BiomassGeneratorTP.UpdateClientVisual (cognitive 16) Content/Industrials/Generator/Biomass/BiomassGenerator.cs:304 — BiomassGeneratorTP.UpdateClientVisual 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.
D2 · Cognitive Complexity · BiomassGeneratorTP.RightClickByTile (cognitive 16) · ×1
  • BiomassGeneratorTP.RightClickByTile (cognitive 16) Content/Industrials/Generator/Biomass/BiomassGenerator.cs:439 — BiomassGeneratorTP.RightClickByTile 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.
D2 · Cognitive Complexity · ThermalGeneratorTP.RightClickByTile (cognitive 16) · ×1
  • ThermalGeneratorTP.RightClickByTile (cognitive 16) Content/Industrials/Generator/Thermal/ThermalGenerator.cs:313 — ThermalGeneratorTP.RightClickByTile 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.
D2 · Cognitive Complexity · ItemPipelineTP.UpdateInputMode (cognitive 16) · ×1
  • ItemPipelineTP.UpdateInputMode (cognitive 16) Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs:385 — ItemPipelineTP.UpdateInputMode 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.
D2 · Cognitive Complexity · ItemPipelineTP.UpdateTransportingItem (cognitive 16) · ×1
  • ItemPipelineTP.UpdateTransportingItem (cognitive 16) Content/Industrials/MaterialFlow/ItemPipelines/ItemPipelineTP.cs:487 — ItemPipelineTP.UpdateTransportingItem 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.
D2 · Cognitive Complexity · ChargingStationUI.DrawBar (cognitive 16) · ×1
  • ChargingStationUI.DrawBar (cognitive 16) Content/Industrials/Modifys/ChargingStationUI.cs:510 — ChargingStationUI.DrawBar 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.
D2 · Cognitive Complexity · ModuleSocketStrip.Draw (cognitive 16) · ×1
  • ModuleSocketStrip.Draw (cognitive 16) Content/Industrials/UIs/ModuleSocketStrip.cs:116 — ModuleSocketStrip.Draw 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.
D2 · Cognitive Complexity · WingsOfInterferencePlayer.ExtendTrails (cognitive 16) · ×1
  • WingsOfInterferencePlayer.ExtendTrails (cognitive 16) Content/Items/Accessories/BrutalRelics/EmpressOfLight/WingsOfInterference.cs:384 — WingsOfInterferencePlayer.ExtendTrails 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.
D2 · Cognitive Complexity · OverloadArmProj.UpdateMeleeStrike (cognitive 16) · ×1
  • OverloadArmProj.UpdateMeleeStrike (cognitive 16) Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadArmProj.cs:249 — OverloadArmProj.UpdateMeleeStrike 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.
D2 · Cognitive Complexity · OverloadCommandRender.DrawCommandStream (cognitive 16) · ×1
  • OverloadCommandRender.DrawCommandStream (cognitive 16) Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadCommandRender.cs:78 — OverloadCommandRender.DrawCommandStream 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.
D2 · Cognitive Complexity · TwinPupilOrbiter.FindTarget (cognitive 16) · ×1
  • TwinPupilOrbiter.FindTarget (cognitive 16) Content/Items/Accessories/BrutalRelics/Twins/TwinPupilOrbiter.cs:264 — TwinPupilOrbiter.FindTarget 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.
D2 · Cognitive Complexity · TwinPupilTetherPlayer.PostUpdateEquips (cognitive 16) · ×1
  • TwinPupilTetherPlayer.PostUpdateEquips (cognitive 16) Content/Items/Accessories/BrutalRelics/Twins/TwinPupilTether.cs:108 — TwinPupilTetherPlayer.PostUpdateEquips 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.
D2 · Cognitive Complexity · GluttonousDetonateNet.Receive (cognitive 16) · ×1
  • GluttonousDetonateNet.Receive (cognitive 16) Content/Items/Accessories/BrutalRelics/WallOfFlesh/GluttonousThroat.cs:292 — GluttonousDetonateNet.Receive 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.
D2 · Cognitive Complexity · DivineJustice.AI (cognitive 16) · ×1
  • DivineJustice.AI (cognitive 16) Content/Items/Accessories/JusticeUnveileds/DivineJustice.cs:40 — DivineJustice.AI 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.
D2 · Cognitive Complexity · JudasIscariot.BetrayBehavior (cognitive 16) · ×1
  • JudasIscariot.BetrayBehavior (cognitive 16) Content/Items/Magic/Elysiums/Disciples/JudasIscariot.cs:67 — JudasIscariot.BetrayBehavior 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.
D2 · Cognitive Complexity · ApocalypseHorseman.AI (cognitive 16) · ×1
  • ApocalypseHorseman.AI (cognitive 16) Content/Items/Magic/Elysiums/Revelations/ApocalypseHorseman.cs:52 — ApocalypseHorseman.AI 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.
D2 · Cognitive Complexity · EverdeepMaelstrom.UpdateVisuals (cognitive 16) · ×1
  • EverdeepMaelstrom.UpdateVisuals (cognitive 16) Content/Items/Magic/Everdeeps/EverdeepMaelstrom.cs:218 — EverdeepMaelstrom.UpdateVisuals 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.
D2 · Cognitive Complexity · EverdeepRing.ReturnTargetPos (cognitive 16) · ×1
  • EverdeepRing.ReturnTargetPos (cognitive 16) Content/Items/Magic/Everdeeps/EverdeepRing.cs:177 — EverdeepRing.ReturnTargetPos 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.
D2 · Cognitive Complexity · SandSmallTornado.AI (cognitive 16) · ×1
  • SandSmallTornado.AI (cognitive 16) Content/Items/Magic/MelodyTheSand.cs:145 — SandSmallTornado.AI 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.
D2 · Cognitive Complexity · ArbiterManifestationActor.UpdateLocalPull (cognitive 16) · ×1
  • ArbiterManifestationActor.UpdateLocalPull (cognitive 16) Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:707 — ArbiterManifestationActor.UpdateLocalPull 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.
D2 · Cognitive Complexity · DestroyersBladeEXHeld.FireShots (cognitive 16) · ×1
  • DestroyersBladeEXHeld.FireShots (cognitive 16) Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:497 — DestroyersBladeEXHeld.FireShots 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.
D2 · Cognitive Complexity · DestroyersBladeEXHeld.DrawPrimitives (cognitive 16) · ×1
  • DestroyersBladeEXHeld.DrawPrimitives (cognitive 16) Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:704 — DestroyersBladeEXHeld.DrawPrimitives 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.
D2 · Cognitive Complexity · DivineSourceBoltProjectile.OnKill (cognitive 16) · ×1
  • DivineSourceBoltProjectile.OnKill (cognitive 16) Content/Items/Melee/DivineSourceBlades/DivineSourceBoltProjectile.cs:200 — DivineSourceBoltProjectile.OnKill 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.
D2 · Cognitive Complexity · HeartcarverExcisedHeart.AI (cognitive 16) · ×1
  • HeartcarverExcisedHeart.AI (cognitive 16) Content/Items/Melee/HeartcarverHeart.cs:64 — HeartcarverExcisedHeart.AI 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.
D2 · Cognitive Complexity · RebelBladeFlyAttcke.AI (cognitive 16) · ×1
  • RebelBladeFlyAttcke.AI (cognitive 16) Content/Items/Melee/RebelBlade.cs:679 — RebelBladeFlyAttcke.AI 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.
D2 · Cognitive Complexity · SeasonalKunaiProj.AI (cognitive 16) · ×1
  • SeasonalKunaiProj.AI (cognitive 16) Content/Items/Melee/SeasonalKunai.cs:100 — SeasonalKunaiProj.AI 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.
D2 · Cognitive Complexity · LonginusWings.Draw (cognitive 16) · ×1
  • LonginusWings.Draw (cognitive 16) Content/Items/Melee/SpearOfLonginuses/LonginusWings.cs:81 — LonginusWings.Draw 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.
D2 · Cognitive Complexity · WGManifestationActor.UpdateLocalPull (cognitive 16) · ×1
  • WGManifestationActor.UpdateLocalPull (cognitive 16) Content/Items/Melee/WeaverGrievanceses/WGManifestationActor.cs:602 — WGManifestationActor.UpdateLocalPull 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.
D2 · Cognitive Complexity · TerraSoulJudgmentProj.AI (cognitive 16) · ×1
  • TerraSoulJudgmentProj.AI (cognitive 16) Content/Items/Modifys/RTerraBlades/TerraSoulJudgmentProj.cs:56 — TerraSoulJudgmentProj.AI 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.
D2 · Cognitive Complexity · TiroFinaleHeld.FinaleAI (cognitive 16) · ×1
  • TiroFinaleHeld.FinaleAI (cognitive 16) Content/Items/Ranged/TiroFinales/TiroFinaleHeld.cs:395 — TiroFinaleHeld.FinaleAI 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.
D2 · Cognitive Complexity · MarbleShieldPlayer.ShatterNearbyProjectiles (cognitive 16) · ×1
  • MarbleShieldPlayer.ShatterNearbyProjectiles (cognitive 16) Content/Items/Stones/Marbles/MarbleShield.cs:234 — MarbleShieldPlayer.ShatterNearbyProjectiles 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.
D2 · Cognitive Complexity · HalibutReset.UpdateShowFX (cognitive 16) · ×1
  • HalibutReset.UpdateShowFX (cognitive 16) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:601 — HalibutReset.UpdateShowFX 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.
D2 · Cognitive Complexity · CannonFishSwarmHitbox.AI (cognitive 16) · ×1
  • CannonFishSwarmHitbox.AI (cognitive 16) Content/LegendWeapon/HalibutLegend/DomainSkills/Superposition.cs:1092 — CannonFishSwarmHitbox.AI 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.
D2 · Cognitive Complexity · BloodyJellyfishUnit.SwimAI (cognitive 16) · ×1
  • BloodyJellyfishUnit.SwimAI (cognitive 16) Content/LegendWeapon/HalibutLegend/FishSkills/FishBloodyManowar.cs:558 — BloodyJellyfishUnit.SwimAI 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.
D2 · Cognitive Complexity · SoulEaterBite.AI (cognitive 16) · ×1
  • SoulEaterBite.AI (cognitive 16) Content/LegendWeapon/HalibutLegend/FishSkills/FishEaterofPlankton.cs:115 — SoulEaterBite.AI 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.
D2 · Cognitive Complexity · PrismiteWaveProjectile.AI (cognitive 16) · ×1
  • PrismiteWaveProjectile.AI (cognitive 16) Content/LegendWeapon/HalibutLegend/FishSkills/FishPrismite.cs:117 — PrismiteWaveProjectile.AI 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.
D2 · Cognitive Complexity · SlimeGelOrb.CheckAttachment (cognitive 16) · ×1
  • SlimeGelOrb.CheckAttachment (cognitive 16) Content/LegendWeapon/HalibutLegend/FishSkills/FishSlime.cs:438 — SlimeGelOrb.CheckAttachment 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.
D2 · Cognitive Complexity · OilBlob.CheckForIgnition (cognitive 16) · ×1
  • OilBlob.CheckForIgnition (cognitive 16) Content/LegendWeapon/HalibutLegend/FishSkills/FishVariegatedLard.cs:342 — OilBlob.CheckForIgnition 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.
D2 · Cognitive Complexity · CthulhuEye.UpdateRibbon (cognitive 16) · ×1
  • CthulhuEye.UpdateRibbon (cognitive 16) Content/LegendWeapon/HalibutLegend/FishSkills/FishofCthulu.cs:299 — CthulhuEye.UpdateRibbon 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.
D2 · Cognitive Complexity · KikasaLakeNPC.SurfaceFx (cognitive 16) · ×1
  • KikasaLakeNPC.SurfaceFx (cognitive 16) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaLakeNPC.cs:140 — KikasaLakeNPC.SurfaceFx 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.
D2 · Cognitive Complexity · KikasaBoomerangProj.AI (cognitive 16) · ×1
  • KikasaBoomerangProj.AI (cognitive 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangProj.cs:63 — KikasaBoomerangProj.AI 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.
D2 · Cognitive Complexity · KikasaGunServant.FireGun (cognitive 16) · ×1
  • KikasaGunServant.FireGun (cognitive 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:617 — KikasaGunServant.FireGun 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.
D2 · Cognitive Complexity · KikasaThrowServant.UpdateFan (cognitive 16) · ×1
  • KikasaThrowServant.UpdateFan (cognitive 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:497 — KikasaThrowServant.UpdateFan 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.
D2 · Cognitive Complexity · KikasaYoyoProj.AI (cognitive 16) · ×1
  • KikasaYoyoProj.AI (cognitive 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoProj.cs:72 — KikasaYoyoProj.AI 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.
D2 · Cognitive Complexity · KikasaBrainServant.UpdateFollow (cognitive 16) · ×1
  • KikasaBrainServant.UpdateFollow (cognitive 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:530 — KikasaBrainServant.UpdateFollow 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.
D2 · Cognitive Complexity · KikasaCultistRuneCircle.AI (cognitive 16) · ×1
  • KikasaCultistRuneCircle.AI (cognitive 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistRuneCircle.cs:93 — KikasaCultistRuneCircle.AI 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.
D2 · Cognitive Complexity · KikasaEmpressServant.UpdateDissolve (cognitive 16) · ×1
  • KikasaEmpressServant.UpdateDissolve (cognitive 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:671 — KikasaEmpressServant.UpdateDissolve 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.
D2 · Cognitive Complexity · KikasaFesterGlob.AI (cognitive 16) · ×1
  • KikasaFesterGlob.AI (cognitive 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterGlob.cs:60 — KikasaFesterGlob.AI 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.
D2 · Cognitive Complexity · KikasaKingSlimeServant.UpdateJelly (cognitive 16) · ×1
  • KikasaKingSlimeServant.UpdateJelly (cognitive 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1034 — KikasaKingSlimeServant.UpdateJelly 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.
D2 · Cognitive Complexity · KikasaMoonLordServant.AI (cognitive 16) · ×1
  • KikasaMoonLordServant.AI (cognitive 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:233 — KikasaMoonLordServant.AI 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.
D2 · Cognitive Complexity · KikasaMoonRay.UpdateLakeBoil (cognitive 16) · ×1
  • KikasaMoonRay.UpdateLakeBoil (cognitive 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs:184 — KikasaMoonRay.UpdateLakeBoil 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.
D2 · Cognitive Complexity · KikasaPrimeServant.UpdateMortar (cognitive 16) · ×1
  • KikasaPrimeServant.UpdateMortar (cognitive 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:676 — KikasaPrimeServant.UpdateMortar 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.
D2 · Cognitive Complexity · KikasaQueenBeeServant.UpdateBees (cognitive 16) · ×1
  • KikasaQueenBeeServant.UpdateBees (cognitive 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:717 — KikasaQueenBeeServant.UpdateBees 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.
D2 · Cognitive Complexity · KikasaQueenBeeServant.DrawGlow (cognitive 16) · ×1
  • KikasaQueenBeeServant.DrawGlow (cognitive 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1290 — KikasaQueenBeeServant.DrawGlow 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.
D2 · Cognitive Complexity · KikasaQueenSlimeServant.UpdateFollow (cognitive 16) · ×1
  • KikasaQueenSlimeServant.UpdateFollow (cognitive 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:457 — KikasaQueenSlimeServant.UpdateFollow 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.
D2 · Cognitive Complexity · KikasaSkeletronServant.DrawBodies (cognitive 16) · ×1
  • KikasaSkeletronServant.DrawBodies (cognitive 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1530 — KikasaSkeletronServant.DrawBodies 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.
D2 · Cognitive Complexity · KikasaTwinsServant.UpdatePulse (cognitive 16) · ×1
  • KikasaTwinsServant.UpdatePulse (cognitive 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:663 — KikasaTwinsServant.UpdatePulse 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.
D2 · Cognitive Complexity · FuFeiMistCloud.AI (cognitive 16) · ×1
  • FuFeiMistCloud.AI (cognitive 16) Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuFeiFX.cs:72 — FuFeiMistCloud.AI 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.
D2 · Cognitive Complexity · KikasaThrallMeltFX.AdvanceShow (cognitive 16) · ×1
  • KikasaThrallMeltFX.AdvanceShow (cognitive 16) Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallMeltFX.cs:141 — KikasaThrallMeltFX.AdvanceShow 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.
D2 · Cognitive Complexity · CrimsonRendHitVFX.SpawnHitTick (cognitive 16) · ×1
  • CrimsonRendHitVFX.SpawnHitTick (cognitive 16) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendParticles.cs:34 — CrimsonRendHitVFX.SpawnHitTick 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.
D2 · Cognitive Complexity · CrimsonRendSlash.CutTiles (cognitive 16) · ×1
  • CrimsonRendSlash.CutTiles (cognitive 16) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1413 — CrimsonRendSlash.CutTiles 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.
D2 · Cognitive Complexity · CrimsonSweepSlash.CutTiles (cognitive 16) · ×1
  • CrimsonSweepSlash.CutTiles (cognitive 16) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1127 — CrimsonSweepSlash.CutTiles 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.
D2 · Cognitive Complexity · OniAnnihilate.ModifyHitNPC (cognitive 16) · ×1
  • OniAnnihilate.ModifyHitNPC (cognitive 16) Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:277 — OniAnnihilate.ModifyHitNPC 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.
D2 · Cognitive Complexity · OniBladeProfile.EnsureProfile (cognitive 16) · ×1
  • OniBladeProfile.EnsureProfile (cognitive 16) Content/LegendWeapon/OnikiriLegend/OniBladeProfile.cs:112 — OniBladeProfile.EnsureProfile 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.
D2 · Cognitive Complexity · OniSeverStrike.UpdateAuthority (cognitive 16) · ×1
  • OniSeverStrike.UpdateAuthority (cognitive 16) Content/LegendWeapon/OnikiriLegend/OniDismembers/OniSeverStrike.cs:649 — OniSeverStrike.UpdateAuthority 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.
D2 · Cognitive Complexity · OniFinaleCut.SpawnDetonationParticles (cognitive 16) · ×1
  • OniFinaleCut.SpawnDetonationParticles (cognitive 16) Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleCut.cs:273 — OniFinaleCut.SpawnDetonationParticles 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.
D2 · Cognitive Complexity · OniOmokage.ClipLineToRect (cognitive 16) · ×1
  • OniOmokage.ClipLineToRect (cognitive 16) Content/LegendWeapon/OnikiriLegend/OniOmokages/OniOmokage.cs:547 — OniOmokage.ClipLineToRect 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.
D2 · Cognitive Complexity · OniSlash.CutTiles (cognitive 16) · ×1
  • OniSlash.CutTiles (cognitive 16) Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1322 — OniSlash.CutTiles 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.
D2 · Cognitive Complexity · OniZanshinSlash.ModifyHitNPC (cognitive 16) · ×1
  • OniZanshinSlash.ModifyHitNPC (cognitive 16) Content/LegendWeapon/OnikiriLegend/OniZanshinSlashs/OniZanshinSlash.cs:364 — OniZanshinSlash.ModifyHitNPC 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.
D2 · Cognitive Complexity · OnikiriNet.ReconcileAuthoritativeState (cognitive 16) · ×1
  • OnikiriNet.ReconcileAuthoritativeState (cognitive 16) Content/LegendWeapon/OnikiriLegend/OnikiriNet.cs:456 — OnikiriNet.ReconcileAuthoritativeState 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.
D2 · Cognitive Complexity · OnikiriNet.RepairDuplicateIdentities (cognitive 16) · ×1
  • OnikiriNet.RepairDuplicateIdentities (cognitive 16) Content/LegendWeapon/OnikiriLegend/OnikiriNet.cs:510 — OnikiriNet.RepairDuplicateIdentities 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.
D2 · Cognitive Complexity · OnikiriPlayer.ClearRemovedMeiTransient (cognitive 16) · ×1
  • OnikiriPlayer.ClearRemovedMeiTransient (cognitive 16) Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs:489 — OnikiriPlayer.ClearRemovedMeiTransient 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.
D2 · Cognitive Complexity · OnikiriPlayer.ResolveEngraveHiTarget (cognitive 16) · ×1
  • OnikiriPlayer.ResolveEngraveHiTarget (cognitive 16) Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs:3174 — OnikiriPlayer.ResolveEngraveHiTarget 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.
D2 · Cognitive Complexity · OniMeiRenderer.DrawMedallion (cognitive 16) · ×1
  • OniMeiRenderer.DrawMedallion (cognitive 16) Content/LegendWeapon/OnikiriLegend/UI/OniMeiRenderer.cs:129 — OniMeiRenderer.DrawMedallion 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.
D2 · Cognitive Complexity · OniSigilBoardDraw.ReadSlotState (cognitive 16) · ×1
  • OniSigilBoardDraw.ReadSlotState (cognitive 16) Content/LegendWeapon/OnikiriLegend/UI/OniSigilBoardDraw.cs:71 — OniSigilBoardDraw.ReadSlotState 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.
D2 · Cognitive Complexity · CyberChargeOrbProj.AI (cognitive 16) · ×1
  • CyberChargeOrbProj.AI (cognitive 16) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberChargeOrbProj.cs:164 — CyberChargeOrbProj.AI 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.
D2 · Cognitive Complexity · CyberDomainFreeze.ReconcileReplicatedStateForSnapshot (cognitive 16) · ×1
  • CyberDomainFreeze.ReconcileReplicatedStateForSnapshot (cognitive 16) Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.Net.cs:952 — CyberDomainFreeze.ReconcileReplicatedStateForSnapshot 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.
D2 · Cognitive Complexity · GraviticBarrelModule.OnBeamAI (cognitive 16) · ×1
  • GraviticBarrelModule.OnBeamAI (cognitive 16) Content/LegendWeapon/SHPCLegend/Modules/Barrel/GraviticBarrelModule.cs:23 — GraviticBarrelModule.OnBeamAI 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.
D2 · Cognitive Complexity · SHPCHiveDroneProj.DrawAdditiveAfterNon (cognitive 16) · ×1
  • SHPCHiveDroneProj.DrawAdditiveAfterNon (cognitive 16) Content/LegendWeapon/SHPCLegend/Modules/Barrel/HiveBarrelModule.cs:195 — SHPCHiveDroneProj.DrawAdditiveAfterNon 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.
D2 · Cognitive Complexity · SHPCMagmaVentProj.UpdateFluidSim (cognitive 16) · ×1
  • SHPCMagmaVentProj.UpdateFluidSim (cognitive 16) Content/LegendWeapon/SHPCLegend/Modules/Barrel/MagmaVentBarrelModule.cs:181 — SHPCMagmaVentProj.UpdateFluidSim 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.
D2 · Cognitive Complexity · SHPCRedlineGaugeProj.SpawnStateParticles (cognitive 16) · ×1
  • SHPCRedlineGaugeProj.SpawnStateParticles (cognitive 16) Content/LegendWeapon/SHPCLegend/Modules/Barrel/RapidBarrelModule.cs:495 — SHPCRedlineGaugeProj.SpawnStateParticles 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.
D2 · Cognitive Complexity · PhantomFrameModule.BlinkVisuals (cognitive 16) · ×1
  • PhantomFrameModule.BlinkVisuals (cognitive 16) Content/LegendWeapon/SHPCLegend/Modules/Frame/PhantomFrameModule.cs:55 — PhantomFrameModule.BlinkVisuals 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.
D2 · Cognitive Complexity · ShenyoGhostLakeScene.DrawFallback (cognitive 16) · ×1
  • ShenyoGhostLakeScene.DrawFallback (cognitive 16) Content/MainMenus/Shenyo/ShenyoGhostLakeScene.cs:716 — ShenyoGhostLakeScene.DrawFallback 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.
D2 · Cognitive Complexity · BssDustDevilState.OnUpdate (cognitive 16) · ×1
  • BssDustDevilState.OnUpdate (cognitive 16) Content/NPCs/BloomsandSerpents/States/BssDustDevilState.cs:38 — BssDustDevilState.OnUpdate 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.
D2 · Cognitive Complexity · BssHubState.UpdateHarass (cognitive 16) · ×1
  • BssHubState.UpdateHarass (cognitive 16) Content/NPCs/BloomsandSerpents/States/BssHubState.cs:70 — BssHubState.UpdateHarass 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.
D2 · Cognitive Complexity · BssPetalShakeState.SpawnPetals (cognitive 16) · ×1
  • BssPetalShakeState.SpawnPetals (cognitive 16) Content/NPCs/BloomsandSerpents/States/BssPetalShakeState.cs:89 — BssPetalShakeState.SpawnPetals 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.
D2 · Cognitive Complexity · BssQuicksandState.UpdatePull (cognitive 16) · ×1
  • BssQuicksandState.UpdatePull (cognitive 16) Content/NPCs/BloomsandSerpents/States/BssQuicksandState.cs:142 — BssQuicksandState.UpdatePull 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.
D2 · Cognitive Complexity · BrainDespawnState.OnUpdate (cognitive 16) · ×1
  • BrainDespawnState.OnUpdate (cognitive 16) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/States/BrainDespawnState.cs:36 — BrainDespawnState.OnUpdate 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.
D2 · Cognitive Complexity · DestroyerBodyAI.HandleDespawnBehavior (cognitive 16) · ×1
  • DestroyerBodyAI.HandleDespawnBehavior (cognitive 16) Content/NPCs/BrutalNPCs/BrutalDestroyer/DestroyerBodyAI.cs:485 — DestroyerBodyAI.HandleDespawnBehavior 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.
D2 · Cognitive Complexity · DestroyerMawBeamProj.AI (cognitive 16) · ×1
  • DestroyerMawBeamProj.AI (cognitive 16) Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:81 — DestroyerMawBeamProj.AI 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.
D2 · Cognitive Complexity · DestroyerDeathState.UpdatePerformanceVisuals (cognitive 16) · ×1
  • DestroyerDeathState.UpdatePerformanceVisuals (cognitive 16) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerDespawnState.cs:144 — DestroyerDeathState.UpdatePerformanceVisuals 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.
D2 · Cognitive Complexity · DestroyerOrbitalStrikeState.UpdateCrossDives (cognitive 16) · ×1
  • DestroyerOrbitalStrikeState.UpdateCrossDives (cognitive 16) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerOrbitalStrikeState.cs:178 — DestroyerOrbitalStrikeState.UpdateCrossDives 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.
D2 · Cognitive Complexity · EowBodyAI.DrawSegment (cognitive 16) · ×1
  • EowBodyAI.DrawSegment (cognitive 16) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/EowBodyAI.cs:409 — EowBodyAI.DrawSegment 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.
D2 · Cognitive Complexity · EowHeadAI.FindTarget (cognitive 16) · ×1
  • EowHeadAI.FindTarget (cognitive 16) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/EowHeadAI.cs:218 — EowHeadAI.FindTarget 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.
D2 · Cognitive Complexity · EowApexFrenzyState.UpdateFinale (cognitive 16) · ×1
  • EowApexFrenzyState.UpdateFinale (cognitive 16) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowApexFrenzyState.cs:341 — EowApexFrenzyState.UpdateFinale 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.
D2 · Cognitive Complexity · EowDevourState.UpdateEject (cognitive 16) · ×1
  • EowDevourState.UpdateEject (cognitive 16) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowDevourState.cs:554 — EowDevourState.UpdateEject 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.
D2 · Cognitive Complexity · GolemSunCore.AI (cognitive 16) · ×1
  • GolemSunCore.AI (cognitive 16) Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemSunCore.cs:110 — GolemSunCore.AI 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.
D2 · Cognitive Complexity · GolemFistGrabState.UpdateFx (cognitive 16) · ×1
  • GolemFistGrabState.UpdateFx (cognitive 16) Content/NPCs/BrutalNPCs/BrutalGolem/States/Fists/GolemFistGrabState.cs:158 — GolemFistGrabState.UpdateFx 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.
D2 · Cognitive Complexity · BKSGeyserProj.AI (cognitive 16) · ×1
  • BKSGeyserProj.AI (cognitive 16) Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSGeyserProj.cs:62 — BKSGeyserProj.AI 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.
D2 · Cognitive Complexity · KingSlimeEngulfState.UpdateCharge (cognitive 16) · ×1
  • KingSlimeEngulfState.UpdateCharge (cognitive 16) Content/NPCs/BrutalNPCs/BrutalKingSlime/States/KingSlimeEngulfState.cs:167 — KingSlimeEngulfState.UpdateCharge 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.
D2 · Cognitive Complexity · CultistGoldRingSeal.AI (cognitive 16) · ×1
  • CultistGoldRingSeal.AI (cognitive 16) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistGoldRingSeal.cs:81 — CultistGoldRingSeal.AI 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.
D2 · Cognitive Complexity · CultistStarfallState.OnUpdate (cognitive 16) · ×1
  • CultistStarfallState.OnUpdate (cognitive 16) Content/NPCs/BrutalNPCs/BrutalLunaticCultist/States/CultistStarfallState.cs:43 — CultistStarfallState.OnUpdate 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.
D2 · Cognitive Complexity · TwinsPhaseTransitionState.ExecuteContractPhase (cognitive 16) · ×1
  • TwinsPhaseTransitionState.ExecuteContractPhase (cognitive 16) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsPhaseTransitionState.cs:178 — TwinsPhaseTransitionState.ExecuteContractPhase 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.
D2 · Cognitive Complexity · RetinazerSoloRageState.ExecuteHomingLaser (cognitive 16) · ×1
  • RetinazerSoloRageState.ExecuteHomingLaser (cognitive 16) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerSoloRageState.cs:330 — RetinazerSoloRageState.ExecuteHomingLaser 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.
D2 · Cognitive Complexity · SpazmatismPhase2DashingState.OnUpdate (cognitive 16) · ×1
  • SpazmatismPhase2DashingState.OnUpdate (cognitive 16) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismPhase2DashingState.cs:45 — SpazmatismPhase2DashingState.OnUpdate 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.
D2 · Cognitive Complexity · SpazmatismSoloRageState.ExecuteHomingDash (cognitive 16) · ×1
  • SpazmatismSoloRageState.ExecuteHomingDash (cognitive 16) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismSoloRageState.cs:361 — SpazmatismSoloRageState.ExecuteHomingDash 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.
D2 · Cognitive Complexity · MLordFacts.ScanParts (cognitive 16) · ×1
  • MLordFacts.ScanParts (cognitive 16) Content/NPCs/BrutalNPCs/BrutalMoonLord/Core/MLordContracts.cs:256 — MLordFacts.ScanParts 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.
D2 · Cognitive Complexity · MLordGrabPlayer.ResolveGrab (cognitive 16) · ×1
  • MLordGrabPlayer.ResolveGrab (cognitive 16) Content/NPCs/BrutalNPCs/BrutalMoonLord/MLordGrabPlayer.cs:92 — MLordGrabPlayer.ResolveGrab 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.
D2 · Cognitive Complexity · MoonLordFreeEyeAI.AI (cognitive 16) · ×1
  • MoonLordFreeEyeAI.AI (cognitive 16) Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordFreeEyeAI.cs:100 — MoonLordFreeEyeAI.AI 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.
D2 · Cognitive Complexity · MoonLordFreeEyeAI.UpdateScissorSweep (cognitive 16) · ×1
  • MoonLordFreeEyeAI.UpdateScissorSweep (cognitive 16) Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordFreeEyeAI.cs:357 — MoonLordFreeEyeAI.UpdateScissorSweep 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.
D2 · Cognitive Complexity · MoonLordHandAI.ApplyIdleEyeCue (cognitive 16) · ×1
  • MoonLordHandAI.ApplyIdleEyeCue (cognitive 16) Content/NPCs/BrutalNPCs/BrutalMoonLord/MoonLordHandAI.cs:199 — MoonLordHandAI.ApplyIdleEyeCue 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.
D2 · Cognitive Complexity · MLordBlackHoleProj.UpdateCollapse (cognitive 16) · ×1
  • MLordBlackHoleProj.UpdateCollapse (cognitive 16) Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordBlackHoleProj.cs:324 — MLordBlackHoleProj.UpdateCollapse 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.
D2 · Cognitive Complexity · MLordScanRayProj.AI (cognitive 16) · ×1
  • MLordScanRayProj.AI (cognitive 16) Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordScanRayProj.cs:46 — MLordScanRayProj.AI 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.
D2 · Cognitive Complexity · MLordBlackFlashState.BuildArmDrive (cognitive 16) · ×1
  • MLordBlackFlashState.BuildArmDrive (cognitive 16) Content/NPCs/BrutalNPCs/BrutalMoonLord/States/MLordBlackFlashState.cs:312 — MLordBlackFlashState.BuildArmDrive 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.
D2 · Cognitive Complexity · PlanteraTentacleAI.UpdateWhip (cognitive 16) · ×1
  • PlanteraTentacleAI.UpdateWhip (cognitive 16) Content/NPCs/BrutalNPCs/BrutalPlantera/PlanteraTentacleAI.cs:196 — PlanteraTentacleAI.UpdateWhip 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.
D2 · Cognitive Complexity · PlanteraVineLatticeState.OnUpdate (cognitive 16) · ×1
  • PlanteraVineLatticeState.OnUpdate (cognitive 16) Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraVineLatticeState.cs:95 — PlanteraVineLatticeState.OnUpdate 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.
D2 · Cognitive Complexity · SwarmDirector.GetEdgeHighlight (cognitive 16) · ×1
  • SwarmDirector.GetEdgeHighlight (cognitive 16) Content/NPCs/BrutalNPCs/BrutalQueenBee/Core/SwarmDirector.cs:462 — SwarmDirector.GetEdgeHighlight 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.
D2 · Cognitive Complexity · QBDespawnState.OnUpdate (cognitive 16) · ×1
  • QBDespawnState.OnUpdate (cognitive 16) Content/NPCs/BrutalNPCs/BrutalQueenBee/States/QBDespawnState.cs:23 — QBDespawnState.OnUpdate 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.
D2 · Cognitive Complexity · QueenCrystalSpireProj.AI (cognitive 16) · ×1
  • QueenCrystalSpireProj.AI (cognitive 16) Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenCrystalSpireProj.cs:46 — QueenCrystalSpireProj.AI 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.
D2 · Cognitive Complexity · SkeletronOrbitSkull.AI (cognitive 16) · ×1
  • SkeletronOrbitSkull.AI (cognitive 16) Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronOrbitSkull.cs:56 — SkeletronOrbitSkull.AI 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.
D2 · Cognitive Complexity · HandSnatchState.UpdateBySubPhase (cognitive 16) · ×1
  • HandSnatchState.UpdateBySubPhase (cognitive 16) Content/NPCs/BrutalNPCs/BrutalSkeletron/States/Hands/HandSnatchState.cs:67 — HandSnatchState.UpdateBySubPhase 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.
D2 · Cognitive Complexity · HandCrushState.OnUpdate (cognitive 16) · ×1
  • HandCrushState.OnUpdate (cognitive 16) Content/NPCs/BrutalNPCs/BrutalSkeletron/States/Hands/SkeletronHandStates.cs:204 — HandCrushState.OnUpdate 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.
D2 · Cognitive Complexity · SkeletronDeathState.UpdateFall (cognitive 16) · ×1
  • SkeletronDeathState.UpdateFall (cognitive 16) Content/NPCs/BrutalNPCs/BrutalSkeletron/States/SkeletronDeathState.cs:122 — SkeletronDeathState.UpdateFall 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.
D2 · Cognitive Complexity · PrimeSkullBeamProj.AI (cognitive 16) · ×1
  • PrimeSkullBeamProj.AI (cognitive 16) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeSkullBeamProj.cs:50 — PrimeSkullBeamProj.AI 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.
D2 · Cognitive Complexity · WofGrabTongueProj.AI (cognitive 16) · ×1
  • WofGrabTongueProj.AI (cognitive 16) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofGrabTongueProj.cs:69 — WofGrabTongueProj.AI 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.
D2 · Cognitive Complexity · WofDeathState.OnUpdate (cognitive 16) · ×1
  • WofDeathState.OnUpdate (cognitive 16) Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/States/WofDeathState.cs:42 — WofDeathState.OnUpdate 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.
D2 · Cognitive Complexity · NPCUIStyle.DrawCursorPanel (cognitive 16) · ×1
  • NPCUIStyle.DrawCursorPanel (cognitive 16) Content/NPCs/CommonUIs/NPCUIStyle.cs:301 — NPCUIStyle.DrawCursorPanel 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.
D2 · Cognitive Complexity · FssGeyserColumn.AI (cognitive 16) · ×1
  • FssGeyserColumn.AI (cognitive 16) Content/NPCs/FestersandSerpents/Projectiles/FssGeyserColumn.cs:54 — FssGeyserColumn.AI 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.
D2 · Cognitive Complexity · FssVenomSkimState.UpdateWindup (cognitive 16) · ×1
  • FssVenomSkimState.UpdateWindup (cognitive 16) Content/NPCs/FestersandSerpents/States/FssVenomSkimState.cs:120 — FssVenomSkimState.UpdateWindup 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.
D2 · Cognitive Complexity · ScrapJunkPile.AI (cognitive 16) · ×1
  • ScrapJunkPile.AI (cognitive 16) Content/NPCs/ScrapCommanders/Projectiles/ScrapJunkPile.cs:41 — ScrapJunkPile.AI 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.
D2 · Cognitive Complexity · ScrapMortarState.OnUpdate (cognitive 16) · ×1
  • ScrapMortarState.OnUpdate (cognitive 16) Content/NPCs/ScrapCommanders/States/ScrapMortarState.cs:34 — ScrapMortarState.OnUpdate 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.
D2 · Cognitive Complexity · SeaShrimpVoltBubble.OnBurst (cognitive 16) · ×1
  • SeaShrimpVoltBubble.OnBurst (cognitive 16) Content/NPCs/SeaShrimp/Projectiles/SeaShrimpVoltBubble.cs:144 — SeaShrimpVoltBubble.OnBurst 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.
D2 · Cognitive Complexity · TBUGDialogue.Pick (cognitive 16) · ×1
  • TBUGDialogue.Pick (cognitive 16) Content/NPCs/TBUGs/TBUGDialogue.cs:183 — TBUGDialogue.Pick 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.
D2 · Cognitive Complexity · VictorDialogue.Pick (cognitive 16) · ×1
  • VictorDialogue.Pick (cognitive 16) Content/NPCs/Victors/VictorDialogue.cs:183 — VictorDialogue.Pick 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.
D2 · Cognitive Complexity · DraedonPanelState.Update (cognitive 16) · ×1
  • DraedonPanelState.Update (cognitive 16) Content/Narrative/Presentation/Skins/Draedon/DraedonPanelState.cs:34 — DraedonPanelState.Update 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.
D2 · Cognitive Complexity · QLPlayer.LoadData (cognitive 16) · ×1
  • QLPlayer.LoadData (cognitive 16) Content/QuestLogs/QLPlayer.cs:50 — QLPlayer.LoadData 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.
D2 · Cognitive Complexity · QuestLog.DrawCanvasContent (cognitive 16) · ×1
  • QuestLog.DrawCanvasContent (cognitive 16) Content/QuestLogs/QuestLog.cs:865 — QuestLog.DrawCanvasContent 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.
D2 · Cognitive Complexity · ChroniclePen.Tally (cognitive 16) · ×1
  • ChroniclePen.Tally (cognitive 16) Content/QuestLogs/Styles/Chronicle/ChroniclePen.cs:317 — ChroniclePen.Tally 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.
D2 · Cognitive Complexity · ChronicleQuestLogStyle.DrawObjectiveRow (cognitive 16) · ×1
  • ChronicleQuestLogStyle.DrawObjectiveRow (cognitive 16) Content/QuestLogs/Styles/Chronicle/ChronicleQuestLogStyle.cs:657 — ChronicleQuestLogStyle.DrawObjectiveRow 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.
D2 · Cognitive Complexity · DraedonShopRenderer.DrawRecord (cognitive 16) · ×1
  • DraedonShopRenderer.DrawRecord (cognitive 16) Content/Scenarios/Draedon/PQCDs/DraedonShops/DraedonShopRenderer.cs:54 — DraedonShopRenderer.DrawRecord 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.
D2 · Cognitive Complexity · DungeonworldAmbientFX.TryRegisterShaft (cognitive 16) · ×1
  • DungeonworldAmbientFX.TryRegisterShaft (cognitive 16) Content/Scenarios/Dungeonworld/Ambience/DungeonworldAmbientFX.cs:170 — DungeonworldAmbientFX.TryRegisterShaft 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.
D2 · Cognitive Complexity · DungeonworldAmbientFX.UpdateShafts (cognitive 16) · ×1
  • DungeonworldAmbientFX.UpdateShafts (cognitive 16) Content/Scenarios/Dungeonworld/Ambience/DungeonworldAmbientFX.cs:225 — DungeonworldAmbientFX.UpdateShafts 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.
D2 · Cognitive Complexity · DungeonworldAmbientFX.HookMachines (cognitive 16) · ×1
  • DungeonworldAmbientFX.HookMachines (cognitive 16) Content/Scenarios/Dungeonworld/Ambience/DungeonworldAmbientFX.cs:318 — DungeonworldAmbientFX.HookMachines 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.
D2 · Cognitive Complexity · DungeonworldAmbientRender.EndEntityDraw (cognitive 16) · ×1
  • DungeonworldAmbientRender.EndEntityDraw (cognitive 16) Content/Scenarios/Dungeonworld/Ambience/DungeonworldAmbientRender.cs:109 — DungeonworldAmbientRender.EndEntityDraw 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.
D2 · Cognitive Complexity · L4MuteBell.TryBuild (cognitive 16) · ×1
  • L4MuteBell.TryBuild (cognitive 16) Content/Scenarios/Dungeonworld/Gen/Layers/L4/L4MuteBell.cs:44 — L4MuteBell.TryBuild 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.
D2 · Cognitive Complexity · L5Leviathan.FindHostWell (cognitive 16) · ×1
  • L5Leviathan.FindHostWell (cognitive 16) Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Leviathan.cs:204 — L5Leviathan.FindHostWell 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.
D2 · Cognitive Complexity · L5Rooms.BuildGallery (cognitive 16) · ×1
  • L5Rooms.BuildGallery (cognitive 16) Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Rooms.cs:146 — L5Rooms.BuildGallery 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.
D2 · Cognitive Complexity · L7Style.ChainBundleBelowSolid (cognitive 16) · ×1
  • L7Style.ChainBundleBelowSolid (cognitive 16) Content/Scenarios/Dungeonworld/Gen/Layers/L7/L7Style.cs:98 — L7Style.ChainBundleBelowSolid 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.
D2 · Cognitive Complexity · AshfallStratum.SwapWalls (cognitive 16) · ×1
  • AshfallStratum.SwapWalls (cognitive 16) Content/Scenarios/Dungeonworld/Gen/Zones/AshfallStratum.cs:173 — AshfallStratum.SwapWalls 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.
D2 · Cognitive Complexity · GaolWraithDraw.DrawRibbon (cognitive 16) · ×1
  • GaolWraithDraw.DrawRibbon (cognitive 16) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:2605 — GaolWraithDraw.DrawRibbon 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.
D2 · Cognitive Complexity · LanternWarden.TryFindPerch (cognitive 16) · ×1
  • LanternWarden.TryFindPerch (cognitive 16) Content/Scenarios/Dungeonworld/NPCs/Elites/LanternWarden.cs:418 — LanternWarden.TryFindPerch 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.
D2 · Cognitive Complexity · UndrownedAnchor.PreDraw (cognitive 16) · ×1
  • UndrownedAnchor.PreDraw (cognitive 16) Content/Scenarios/Dungeonworld/NPCs/UndrownedAnchor.cs:183 — UndrownedAnchor.PreDraw 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.
D2 · Cognitive Complexity · HadalTerrainPlanner.TryAddGallery (cognitive 16) · ×1
  • HadalTerrainPlanner.TryAddGallery (cognitive 16) Content/Scenarios/Hadalworld/Gen/Core/HadalTerrainPlan.cs:374 — HadalTerrainPlanner.TryAddGallery 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.
D2 · Cognitive Complexity · OniUmbrellaPuddleRender.EndCaptureDraw (cognitive 16) · ×1
  • OniUmbrellaPuddleRender.EndCaptureDraw (cognitive 16) Content/Scenarios/Kiame/Overlay/OniUmbrellaPuddleRender.cs:27 — OniUmbrellaPuddleRender.EndCaptureDraw 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.
D2 · Cognitive Complexity · OniUmbrellaWorldSpawn.EnsureSingleUmbrellaActor (cognitive 16) · ×1
  • OniUmbrellaWorldSpawn.EnsureSingleUmbrellaActor (cognitive 16) Content/Scenarios/Kiame/Overlay/OniUmbrellaWorldSpawn.cs:236 — OniUmbrellaWorldSpawn.EnsureSingleUmbrellaActor 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.
D2 · Cognitive Complexity · KiameLoadingScreen.DrawRuinHut (cognitive 16) · ×1
  • KiameLoadingScreen.DrawRuinHut (cognitive 16) Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:272 — KiameLoadingScreen.DrawRuinHut 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.
D2 · Cognitive Complexity · KiyumeSoundscape.UpdateAccents (cognitive 16) · ×1
  • KiyumeSoundscape.UpdateAccents (cognitive 16) Content/Scenarios/Kiyume/Ambience/KiyumeSoundscape.cs:251 — KiyumeSoundscape.UpdateAccents 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.
D2 · Cognitive Complexity · KiyumeHauntDirector.PumpLanternGuide (cognitive 16) · ×1
  • KiyumeHauntDirector.PumpLanternGuide (cognitive 16) Content/Scenarios/Kiyume/NPCs/KiyumeHauntDirector.cs:147 — KiyumeHauntDirector.PumpLanternGuide 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.
D2 · Cognitive Complexity · RidgeWalkerYokai.PlayStateCue (cognitive 16) · ×1
  • RidgeWalkerYokai.PlayStateCue (cognitive 16) Content/Scenarios/Kiyume/NPCs/RidgeWalkerYokai.cs:457 — RidgeWalkerYokai.PlayStateCue 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.
D2 · Cognitive Complexity · KiyumeLoadingScreen.DrawVillageRow (cognitive 16) · ×1
  • KiyumeLoadingScreen.DrawVillageRow (cognitive 16) Content/Scenarios/Kiyume/UI/KiyumeLoadingScreen.cs:210 — KiyumeLoadingScreen.DrawVillageRow 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.
D2 · Cognitive Complexity · CampsiteLocationFinder.HasHorizontalSpace (cognitive 16) · ×1
  • CampsiteLocationFinder.HasHorizontalSpace (cognitive 16) Content/Scenarios/OldDuke/Campsites/CampsiteLocationFinder.cs:288 — CampsiteLocationFinder.HasHorizontalSpace 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.
D2 · Cognitive Complexity · CampsitePotActor.UpdateParticles (cognitive 16) · ×1
  • CampsitePotActor.UpdateParticles (cognitive 16) Content/Scenarios/OldDuke/Campsites/CampsitePotActor.cs:78 — CampsitePotActor.UpdateParticles 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.
D2 · Cognitive Complexity · OldDukeScrollBar.Update (cognitive 16) · ×1
  • OldDukeScrollBar.Update (cognitive 16) Content/Scenarios/OldDuke/OldDukeShops/OldDukeScrollBar.cs:18 — OldDukeScrollBar.Update 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.
D2 · Cognitive Complexity · OldDukeShopInteraction.HandlePurchaseInput (cognitive 16) · ×1
  • OldDukeShopInteraction.HandlePurchaseInput (cognitive 16) Content/Scenarios/OldDuke/OldDukeShops/OldDukeShopInteraction.cs:158 — OldDukeShopInteraction.HandlePurchaseInput 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.
D2 · Cognitive Complexity · ShepelEnvironmentTracker.PreUpdate (cognitive 16) · ×1
  • ShepelEnvironmentTracker.PreUpdate (cognitive 16) Content/Scenarios/Shepel/ShepelEnvironmentTracker.cs:15 — ShepelEnvironmentTracker.PreUpdate 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.
D2 · Cognitive Complexity · EnchantUI.UpdateParticles (cognitive 16) · ×1
  • EnchantUI.UpdateParticles (cognitive 16) Content/Scenarios/SupCal/End/EternalBlazingNow/Enchants/EnchantUI.cs:188 — EnchantUI.UpdateParticles 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.
D2 · Cognitive Complexity · IndustrialSkyIslandGen.Generate (cognitive 16) · ×1
  • IndustrialSkyIslandGen.Generate (cognitive 16) Content/Structures/IndustrialSkyIslandGen.cs:27 — IndustrialSkyIslandGen.Generate 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.
D2 · Cognitive Complexity · SHPCCradleGen.TryFindSkyPlacement (cognitive 16) · ×1
  • SHPCCradleGen.TryFindSkyPlacement (cognitive 16) Content/Structures/SHPCCradleGen.cs:97 — SHPCCradleGen.TryFindSkyPlacement 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.
D2 · Cognitive Complexity · HeadlessShadeProj.TryApplyAuthorityImpact (cognitive 16) · ×1
  • HeadlessShadeProj.TryApplyAuthorityImpact (cognitive 16) Content/Wraiths/Projectiles/HeadlessShadeProj.cs:550 — HeadlessShadeProj.TryApplyAuthorityImpact 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.
D2 · Cognitive Complexity · LanternBoyProj.AI (cognitive 16) · ×1
  • LanternBoyProj.AI (cognitive 16) Content/Wraiths/Projectiles/LanternBoyProj.cs:148 — LanternBoyProj.AI 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.
D2 · Cognitive Complexity · WikithisRef.SetupData (cognitive 16) · ×1
  • WikithisRef.SetupData (cognitive 16) OtherMods/Wikithis/WikithisRef.cs:37 — WikithisRef.SetupData 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.
D4 · Code Duplication · Near-duplicate member family (20 members, 16 shared lines) · ×1
  • Near-duplicate member family (20 members, 16 shared lines) Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineTile.cs:15 — Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineTile.cs:15-34 | Content/Industrials/ElectricPowers/FluidInjectors/FluidInjectorTile.cs:13-32 | Content/Industrials/ElectricPowers/FluidPumps/FluidPumpTile.cs:13-32 | Content/Industrials/ElectricPowers/HealingStations/HealStationTile.cs:23-44 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconTile.cs:20-41 | Content/Industrials/ElectricPowers/ShieldGenerators/ShieldGeneratorTile.cs:23-44 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterTile.cs:15-34 | Content/Industrials/ElectricPowers/Suppressors/PacifierTowerTile.cs:23-44 | Content/Industrials/ElectricPowers/TeleportStations/TeleportStationTile.cs:20-42 | Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:123-144 | Content/Industrials/ElectricPowers/Turrets/CryoTurrets/CryoTurretTile.cs:23-44 | Content/Industrials/ElectricPowers/Turrets/FlameTurrets/FlameTurretTile.cs:23-44 | Content/Industrials/ElectricPowers/Turrets/LaserTurrets/LaserTurretTile.cs:23-44 | Content/Industrials/Generator/Biomass/BiomassGenerator.cs:72-91 | Content/Industrials/Generator/MagmaThermal/MagmaThermalGenerator.cs:64-83 | Content/Industrials/Generator/Thermal/ThermalGenerator.cs:56-75 | Content/Industrials/MaterialFlow/Batterys/CapacitorMatrix.cs:62-81 | Content/Industrials/MaterialFlow/Batterys/ThermalBattery.cs:52-71 | Content/Industrials/MaterialFlow/Fluids/FluidTank.cs:51-70 | Content/Industrials/MaterialFlow/Fluids/LargeFluidTank.cs:46-65 — These 20 members are variants of one another: a block of 16 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 20 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 20 times.
D4 · Code Duplication · Near-duplicate member family (18 members, 15 shared lines) · ×1
  • Near-duplicate member family (18 members, 15 shared lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1154 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1154-1217 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:914-972 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1173-1235 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:971-1030 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1507-1571 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1095-1154 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1236-1296 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:981-1037 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:807-864 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:1050-1106 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:976-1036 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:875-933 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:935-998 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:908-966 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1376-1436 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1278-1315 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1442-1509 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1555-1604 — These 18 members are variants of one another: a block of 15 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 18 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 18 times.
D4 · Code Duplication · Near-duplicate member family (15 members, 25 shared lines) · ×1
  • Near-duplicate member family (15 members, 25 shared lines) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:123 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:123-218 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs:136-240 | Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:133-235 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs:131-226 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:139-241 | Content/Industrials/ElectricPowers/Launchers/PlayerLauncherUI.cs:124-199 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:114-197 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconUI.cs:116-199 | Content/Industrials/ElectricPowers/Recyclers/RecyclerUI.cs:134-236 | Content/Industrials/ElectricPowers/Sensors/SensorUI.cs:88-181 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterUI.cs:137-238 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:125-215 | Content/Industrials/Generator/Biomass/BiomassGeneratorUI.cs:90-169 | Content/Industrials/Generator/GeneratorReadout.cs:124-201 | Content/Industrials/Generator/Thermal/ThermalGeneratorUI.cs:118-198 — These 15 members are variants of one another: a block of 25 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them 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 · Near-duplicate member family (14 members, 18 shared lines) · ×1
  • Near-duplicate member family (14 members, 18 shared lines) Content/Industrials/ElectricPowers/Collectors/Collector.cs:66 — Content/Industrials/ElectricPowers/Collectors/Collector.cs:66-85 | Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs:47-69 | Content/Industrials/ElectricPowers/LifeWeavers/LifeWeaverTile.cs:17-36 | Content/Industrials/ElectricPowers/LifeWeavers/WGGLifeWeaver.cs:52-74 | Content/Industrials/ElectricPowers/Lumberjacks/LumberjackTile.cs:16-35 | Content/Industrials/ElectricPowers/Lumberjacks/WGGLumberjack.cs:47-69 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatTile.cs:21-40 | Content/Industrials/ElectricPowers/Spectrometers/Spectrometer.cs:53-72 | Content/Industrials/ElectricPowers/Sundials/ElectricSundialTile.cs:25-48 | Content/Industrials/ElectricPowers/Throwers/ThrowerTile.cs:25-48 | Content/Industrials/MaterialFlow/LaserEnergyTrans.cs:64-83 | Content/Scenarios/OldDuke/MermanRod.cs:49-70 | Content/Scenarios/OldDuke/OldDuchests/OldDuchest.cs:55-75 | OtherMods/Coralite/Arcanes/ArcaneTransformer.cs:40-59 — These 14 members are variants of one another: a block of 18 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them 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.
D4 · Code Duplication · Near-duplicate member family (13 members, 16 shared lines) · ×1
  • Near-duplicate member family (13 members, 16 shared lines) Content/Items/Accessories/ArcaneThroneOfEternity.cs:149 — Content/Items/Accessories/ArcaneThroneOfEternity.cs:149-194 | Content/Items/Accessories/ArcaneThroneOfEternity.cs:296-340 | Content/Items/Accessories/ArcaneThroneOfEternity.cs:424-471 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDetonationProj.cs:154-221 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberShockwaveProj.cs:56-108 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberFreezeWaveProj.cs:45-102 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberPixelDecomposeProj.cs:41-101 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberReformProj.cs:44-107 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/HeavyBarrelModule.cs:295-332 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/HypersonicBarrelModule.cs:191-225 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/ScattershotBarrelModule.cs:361-398 | Content/LegendWeapon/SHPCLegend/Modules/Power/PlasmaInjectorModule.cs:148-182 | Content/LegendWeapon/SHPCLegend/Modules/Stock/ExtenderStockModule.cs:403-450 — These 13 members are variants of one another: a block of 16 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 13 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 13 times.
D4 · Code Duplication · Near-duplicate member family (12 members, 13 shared lines) · ×1
  • Near-duplicate member family (12 members, 13 shared lines) Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs:94 — Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs:94-119 | Content/Industrials/ElectricPowers/Incinerators/IncineratorTile.cs:84-111 | Content/Industrials/ElectricPowers/LifeWeavers/LifeWeaverTile.cs:47-72 | Content/Industrials/ElectricPowers/LifeWeavers/WGGLifeWeaver.cs:99-124 | Content/Industrials/ElectricPowers/Lumberjacks/LumberjackTile.cs:46-71 | Content/Industrials/ElectricPowers/Lumberjacks/WGGLumberjack.cs:94-119 | Content/Industrials/ElectricPowers/Spectrometers/Spectrometer.cs:90-115 | Content/Industrials/Generator/Thermal/ThermalGenerator.cs:84-110 | Content/Industrials/Generator/Thermal/ThermalGeneratorMK2.cs:84-110 | Content/Items/Placeable/HoChaMeditatorItem.cs:61-88 | Content/Items/Placeable/StarflowPlatedBlock.cs:70-87 | Content/Scenarios/Draedon/Quest/DeploySignaltowers/CQETConstructor.cs:97-122 — These 12 members are variants of one another: a block of 13 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 12 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 12 times.
D4 · Code Duplication · Near-duplicate member family (10 members, 16 shared lines) · ×1
  • Near-duplicate member family (10 members, 16 shared lines) Content/Items/Melee/DestroyersBlade.cs:494 — Content/Items/Melee/DestroyersBlade.cs:494-547 | Content/Items/Melee/DragonsScaleGreatsword.cs:517-568 | Content/Items/Melee/EnergySword.cs:533-584 | Content/Items/Melee/OniMacheteHands.cs:1061-1126 | Content/Items/Melee/OniMacheteHands.cs:1303-1367 | Content/Items/Melee/RebelBlade.cs:563-615 | Content/Items/Melee/StormGoddessSpears/StormGoddessSpearHeld.cs:513-555 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:499-550 | Content/LegendWeapon/HalibutLegend/FishSkills/FishEaterofPlankton.cs:377-426 | Content/LegendWeapon/HalibutLegend/FishSkills/FishFallenStarVFX.cs:168-231 — These 10 members are variants of one another: a block of 16 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 10 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 10 times.
D4 · Code Duplication · Near-duplicate member family (9 members, 25 shared lines) · ×1
  • Near-duplicate member family (9 members, 25 shared lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:696 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:696-746 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:594-642 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:773-821 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:600-648 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:943-995 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:573-621 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:556-604 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:556-606 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:589-637 — These 9 members are variants of one another: a block of 25 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 9 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 9 times.
D4 · Code Duplication · Near-duplicate member family (9 members, 23 shared lines) · ×1
  • Near-duplicate member family (9 members, 23 shared lines) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:123 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:123-218 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs:136-240 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs:131-226 | Content/Industrials/ElectricPowers/Launchers/PlayerLauncherUI.cs:124-199 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:114-197 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconUI.cs:116-199 | Content/Industrials/ElectricPowers/Sensors/SensorUI.cs:88-181 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:125-215 | Content/Industrials/ElectricPowers/TeleportStations/TeleportStationUI.cs:186-264 — These 9 members are variants of one another: a block of 23 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 9 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 9 times.
D4 · Code Duplication · Near-duplicate member family (9 members, 22 shared lines) · ×1
  • Near-duplicate member family (9 members, 22 shared lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:325 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:325-420 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:324-415 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:300-391 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:321-413 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:336-436 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:287-368 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:287-378 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:295-380 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:319-410 — These 9 members are variants of one another: a block of 22 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 9 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 9 times.
D4 · Code Duplication · Near-duplicate member family (8 members, 23 shared lines) · ×1
  • Near-duplicate member family (8 members, 23 shared lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:710 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:710-754 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:724-768 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:642-684 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:504-546 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:692-734 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:660-704 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:790-861 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:626-670 — These 8 members are variants of one another: a block of 23 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 8 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 8 times.
D4 · Code Duplication · Near-duplicate member family (8 members, 10 shared lines) · ×1
  • Near-duplicate member family (8 members, 10 shared lines) Content/Industrials/ElectricPowers/HealingStations/HealStationTile.cs:88 — Content/Industrials/ElectricPowers/HealingStations/HealStationTile.cs:88-128 | Content/Industrials/ElectricPowers/ShieldGenerators/ShieldGeneratorTile.cs:88-128 | Content/Industrials/ElectricPowers/Suppressors/PacifierTowerTile.cs:88-128 | Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:168-199 | Content/Industrials/ElectricPowers/Turrets/CryoTurrets/CryoTurretTile.cs:88-128 | Content/Industrials/ElectricPowers/Turrets/FlameTurrets/FlameTurretTile.cs:88-128 | Content/Industrials/ElectricPowers/Turrets/LaserTurrets/LaserTurretTile.cs:88-128 | Content/Tiles/NeutronStarIngotTile.cs:34-57 — These 8 members are variants of one another: a block of 10 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 8 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 8 times.
D4 · Code Duplication · Near-duplicate member family (7 members, 16 shared lines) · ×1
  • Near-duplicate member family (7 members, 16 shared lines) Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs:102 — Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs:102-141 | Content/LegendWeapon/KikasaLegend/TrialQuests/KikasaTrackerWidgetStyle.cs:79-115 | Content/LegendWeapon/OnikiriLegend/TrialQuests/OnikiriTrackerWidgetStyle.cs:70-101 | Content/LegendWeapon/SHPCLegend/TrialQuests/SHPCTrackerWidgetStyle.cs:95-132 | Content/Scenarios/Draedon/Quest/DraedonTrackerWidgetStyle.cs:117-163 | Content/Scenarios/OldDuke/Quest/SulfseaTrackerWidgetStyle.cs:114-157 | Content/Scenarios/SupCal/Quest/BrimstoneTrackerWidgetStyle.cs:109-155 — These 7 members are variants of one another: a block of 16 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 7 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 7 times.
D4 · Code Duplication · Near-duplicate member family (7 members, 13 shared lines) · ×1
  • Near-duplicate member family (7 members, 13 shared lines) Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:252 — Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:252-279 | Content/Items/Accessories/BrutalRelics/QueenBee/SwarmVortexProj.cs:402-455 | Content/NPCs/BloomsandSerpents/Projectiles/BssDashOmen.cs:100-128 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerStrikeTelegraph.cs:93-117 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronGeyserProj.cs:137-163 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronTelegraph.cs:103-131 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Projectiles/QueenBeeTelegraphLine.cs:87-112 — These 7 members are variants of one another: a block of 13 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 7 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 7 times.
D4 · Code Duplication · Near-duplicate member family (6 members, 26 shared lines) · ×1
  • Near-duplicate member family (6 members, 26 shared lines) Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:841 — Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:841-954 | Content/Items/Melee/DivineSourceBlades/DivineSourceWaveProjectile.cs:336-412 | Content/Items/Melee/NeutronGlaive.cs:545-629 | Content/Items/Melee/NeutronGlaive.cs:1023-1095 | Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:676-766 | Content/Items/Modifys/RBloodButcherer.cs:664-750 — These 6 members are variants of one another: a block of 26 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 6 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 6 times.
D4 · Code Duplication · Near-duplicate member family (6 members, 21 shared lines) · ×1
  • Near-duplicate member family (6 members, 21 shared lines) Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:164 — Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:164-214 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerFrostPulseProj.cs:118-161 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerIceSpikeProj.cs:146-197 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordRayRender.cs:17-66 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenGaleFieldProj.cs:97-137 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenPrismBeamProj.cs:262-307 — These 6 members are variants of one another: a block of 21 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 6 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 6 times.
D4 · Code Duplication · Near-duplicate member family (6 members, 17 shared lines) · ×1
  • Near-duplicate member family (6 members, 17 shared lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:423 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:423-452 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:393-420 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:424-451 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:410-437 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:385-410 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:426-453 — These 6 members are variants of one another: a block of 17 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 6 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 6 times.
D4 · Code Duplication · Near-duplicate member family (5 members, 29 shared lines) · ×1
  • Near-duplicate member family (5 members, 29 shared lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1219 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1219-1289 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1237-1327 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1573-1688 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:1000-1056 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1606-1717 — These 5 members are variants of one another: a block of 29 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 5 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 5 times.
D4 · Code Duplication · Near-duplicate member family (5 members, 22 shared lines) · ×1
  • Near-duplicate member family (5 members, 22 shared lines) Content/Scenarios/Kiyume/NPCs/KiyumeHound.cs:1017 — Content/Scenarios/Kiyume/NPCs/KiyumeHound.cs:1017-1091 | Content/Scenarios/Kiyume/NPCs/KiyumeWhiteHound.cs:443-517 | Content/Scenarios/Kiyume/NPCs/RidgeWalkerYokai.cs:553-634 | Content/Scenarios/Kiyume/NPCs/ShallowHandsYokai.cs:354-427 | Content/Scenarios/Kiyume/NPCs/WellHandYokai.cs:362-439 — These 5 members are variants of one another: a block of 22 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 5 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 5 times.
D4 · Code Duplication · Near-duplicate member family (5 members, 21 shared lines) · ×1
  • Near-duplicate member family (5 members, 21 shared lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:790 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:790-861 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:805-860 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:626-670 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:931-978 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:960-1016 — These 5 members are variants of one another: a block of 21 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 5 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 5 times.
D4 · Code Duplication · Near-duplicate member family (5 members, 19 shared lines) · ×1
  • Near-duplicate member family (5 members, 19 shared lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:927 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:927-991 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:1106-1157 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1314-1373 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:927-1002 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:948-1047 — These 5 members are variants of one another: a block of 19 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 5 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 5 times.
D4 · Code Duplication · Near-duplicate member family (5 members, 14 shared lines) · ×1
  • Near-duplicate member family (5 members, 14 shared lines) Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs:178 — Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs:178-223 | Content/Items/Magic/Everdeeps/EverdeepMaelstrom.cs:288-347 | Content/Items/Magic/Everdeeps/EverdeepRing.cs:330-377 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronSharkTornadoProj.cs:292-340 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronTsunamiWallProj.cs:135-193 — These 5 members are variants of one another: a block of 14 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 5 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 5 times.
D4 · Code Duplication · Near-duplicate member family (5 members, 13 shared lines) · ×1
  • Near-duplicate member family (5 members, 13 shared lines) Content/Items/Melee/CursedflameBloodfists/CursedflameFistProj.cs:167 — Content/Items/Melee/CursedflameBloodfists/CursedflameFistProj.cs:167-199 | Content/Items/Melee/StormGoddessSpears/AncientStormGoddessSpear.cs:296-328 | Content/Items/Melee/StormGoddessSpears/AncientStormGoddessSpear.cs:461-493 | Content/Items/Ranged/NeutronBows/EXNeutronArrow.cs:61-90 | Content/Items/Summon/WhiplashGalactica.cs:217-246 — These 5 members are variants of one another: a block of 13 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 5 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 5 times.
D4 · Code Duplication · Near-duplicate member family (5 members, 10 shared lines) · ×1
  • Near-duplicate member family (5 members, 10 shared lines) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:392 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:392-434 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs:403-474 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:319-361 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconUI.cs:354-396 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:392-439 — These 5 members are variants of one another: a block of 10 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 5 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 5 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 82 shared lines) · ×1
  • Near-duplicate member family (4 members, 82 shared lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:671 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:671-791 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:690-807 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:633-753 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:666-785 — These 4 members are variants of one another: a block of 82 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 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 4 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 43 shared lines) · ×1
  • Near-duplicate member family (4 members, 43 shared lines) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1006 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1006-1071 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaMinionDrownFX.cs:434-509 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaPlayerDrownFX.cs:479-545 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaScourgeFX.cs:743-806 — These 4 members are variants of one another: a block of 43 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 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 4 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 34 shared lines) · ×1
  • Near-duplicate member family (4 members, 34 shared lines) Content/Items/Melee/DestroyersBlade.cs:199 — Content/Items/Melee/DestroyersBlade.cs:199-290 | Content/Items/Melee/DragonsScaleGreatsword.cs:208-303 | Content/Items/Melee/EnergySword.cs:222-313 | Content/Items/Melee/RebelBlade.cs:249-334 — These 4 members are variants of one another: a block of 34 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 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 4 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 26 shared lines) · ×1
  • Near-duplicate member family (4 members, 26 shared lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:1036 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:1036-1143 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:896-973 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1536-1630 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1290-1376 — These 4 members are variants of one another: a block of 26 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 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 4 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 25 shared lines) · ×1
  • Near-duplicate member family (4 members, 25 shared lines) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainSky.cs:89 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainSky.cs:89-190 | Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamSky.cs:55-108 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainSky.cs:70-147 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspaceSky.cs:52-108 — These 4 members are variants of one another: a block of 25 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 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 4 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 23 shared lines) · ×1
  • Near-duplicate member family (4 members, 23 shared lines) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownRender.cs:15 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownRender.cs:15-61 | Content/LegendWeapon/OnikiriLegend/OniDismembers/OniDismemberRender.cs:30-97 | Content/LegendWeapon/OnikiriLegend/OniDismembers/OniPlayerDismember.cs:402-456 | Content/LegendWeapon/OnikiriLegend/OniOmokages/OniOmokageRender.cs:61-144 — These 4 members are variants of one another: a block of 23 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 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 4 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 17 shared lines) · ×1
  • Near-duplicate member family (4 members, 17 shared lines) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterTile.cs:26 — Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterTile.cs:26-44 | Content/Industrials/ElectricPowers/Crushers/CrusherTile.cs:24-42 | Content/Industrials/ElectricPowers/Incinerators/IncineratorTile.cs:18-39 | Content/Industrials/ElectricPowers/Recyclers/RecyclerTile.cs:19-39 — These 4 members are variants of one another: a block of 17 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 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 4 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 15 shared lines) · ×1
  • Near-duplicate member family (4 members, 15 shared lines) Content/Items/Melee/HeartcarverHeart.cs:234 — Content/Items/Melee/HeartcarverHeart.cs:234-270 | Content/Items/Melee/OniMacheteHands.cs:1476-1516 | Content/Items/Ranged/UniversalFrost.cs:378-413 | Content/LegendWeapon/HalibutLegend/FishSkills/FishRock.cs:743-782 — These 4 members are variants of one another: a block of 15 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 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 4 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 13 shared lines) · ×1
  • Near-duplicate member family (4 members, 13 shared lines) Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFistProj.cs:368 — Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFistProj.cs:368-408 | Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFistProj.cs:519-563 | Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemSunCore.cs:265-309 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Rendering/SkeletronRenderHelper.cs:479-514 — These 4 members are variants of one another: a block of 13 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 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 4 times.
D4 · Code Duplication · Near-duplicate member family (3 members, 130 shared lines) · ×1
  • Near-duplicate member family (3 members, 130 shared lines) Content/EntrustManager/Styles/DraedonManagerStyle.cs:406 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:406-570 | Content/EntrustManager/Styles/ForestManagerStyle.cs:415-579 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:404-568 — These 3 members are variants of one another: a block of 130 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 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 3 times.
D4 · Code Duplication · Near-duplicate member family (3 members, 33 shared lines) · ×1
  • Near-duplicate member family (3 members, 33 shared lines) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:21 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:21-96 | Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs:23-104 | Content/Scenarios/Kiame/Overlay/OniRainWorldRender.cs:21-90 — These 3 members are variants of one another: a block of 33 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 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 3 times.
D4 · Code Duplication · Near-duplicate member family (3 members, 32 shared lines) · ×1
  • Near-duplicate member family (3 members, 32 shared lines) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:674 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:674-784 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaMinionDrownFX.cs:235-362 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaPlayerDrownFX.cs:313-425 — These 3 members are variants of one another: a block of 32 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 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 3 times.
D4 · Code Duplication · Near-duplicate member family (3 members, 26 shared lines) · ×1
  • Near-duplicate member family (3 members, 26 shared lines) Content/Items/Ranged/Pallbearer.cs:1225 — Content/Items/Ranged/Pallbearer.cs:1225-1281 | Content/LegendWeapon/HalibutLegend/FishSkills/FishAmanita.cs:643-702 | Content/LegendWeapon/HalibutLegend/FishSkills/FishHoney.cs:236-294 — These 3 members are variants of one another: a block of 26 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 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 3 times.
D4 · Code Duplication · Near-duplicate member family (3 members, 22 shared lines) · ×1
  • Near-duplicate member family (3 members, 22 shared lines) Content/GameModes/BrutalMobs/Legion/Projectiles/LegionInkGlob.cs:80 — Content/GameModes/BrutalMobs/Legion/Projectiles/LegionInkGlob.cs:80-104 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionScoutBolt.cs:79-103 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionVolleyArrow.cs:83-107 — These 3 members are variants of one another: a block of 22 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 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 3 times.
D4 · Code Duplication · Near-duplicate member family (3 members, 8 shared lines) · ×1
  • Near-duplicate member family (3 members, 8 shared lines) Content/Narrative/Common/BaseRecipeDisplayUI.cs:250 — Content/Narrative/Common/BaseRecipeDisplayUI.cs:250-259 | Content/Scenarios/Draedon/Quest/DeploySignaltowers/DeploySignaltowerRender.cs:266-278 | Content/Scenarios/Draedon/Quest/DeploySignaltowers/DeploySignaltowerRender.cs:720-747 — These 3 members are variants of one another: a block of 8 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 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 3 times.
D4 · Code Duplication · Near-duplicate member family (3 members, 5 shared lines) · ×1
  • Near-duplicate member family (3 members, 5 shared lines) Content/Items/Melee/OniMachete.cs:407 — Content/Items/Melee/OniMachete.cs:407-455 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSlashRenderer.cs:364-435 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleCut.cs:567-589 — These 3 members are variants of one another: a block of 5 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 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 3 times.
D4 · Code Duplication · Near-duplicate member pair (73 shared lines) · ×1
  • Near-duplicate member pair (73 shared lines) Content/NPCs/BloomsandSerpents/BssHead.cs:272 — Content/NPCs/BloomsandSerpents/BssHead.cs:272-373 | Content/NPCs/FestersandSerpents/FssHead.cs:231-327 — These two members are variants of one another: 73 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 · Near-duplicate member pair (58 shared lines) · ×1
  • Near-duplicate member pair (58 shared lines) Content/NPCs/ScrapCommanders/States/ScrapSawLaunchState.cs:36 — Content/NPCs/ScrapCommanders/States/ScrapSawLaunchState.cs:36-187 | Content/NPCs/ScrapCommanders/States/ScrapViceSnatchState.cs:36-182 — These two members are variants of one another: 58 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 · Near-duplicate member pair (53 shared lines) · ×1
  • Near-duplicate member pair (53 shared lines) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterTile.cs:88 — Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterTile.cs:88-167 | Content/Industrials/ElectricPowers/Crushers/CrusherTile.cs:86-178 — These two members are variants of one another: 53 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 · Near-duplicate member pair (42 shared lines) · ×1
  • Near-duplicate member pair (42 shared lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:283 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:283-346 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:322-403 — These two members are variants of one another: 42 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 · Near-duplicate member pair (39 shared lines) · ×1
  • Near-duplicate member pair (39 shared lines) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:103 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:103-175 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainRender.cs:177-236 — These two members are variants of one another: 39 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 · Near-duplicate member pair (38 shared lines) · ×1
  • Near-duplicate member pair (38 shared lines) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowGeyserProj.cs:54 — Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowGeyserProj.cs:54-114 | Content/NPCs/FestersandSerpents/Projectiles/FssGeyserColumn.cs:54-112 — These two members are variants of one another: 38 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 · Near-duplicate member pair (35 shared lines) · ×1
  • Near-duplicate member pair (35 shared lines) Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:534 — Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:534-606 | Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:456-521 — These two members are variants of one another: 35 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 · Near-duplicate member pair (34 shared lines) · ×1
  • Near-duplicate member pair (34 shared lines) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:755 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:755-794 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:800-838 — These two members are variants of one another: 34 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 · Near-duplicate member pair (30 shared lines) · ×1
  • Near-duplicate member pair (30 shared lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishDrizzle.cs:380 — Content/LegendWeapon/HalibutLegend/FishSkills/FishDrizzle.cs:380-481 | Content/LegendWeapon/HalibutLegend/FishSkills/FishSparkling.cs:265-348 — These two members are variants of one another: 30 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 · Near-duplicate member pair (26 shared lines) · ×1
  • Near-duplicate member pair (26 shared lines) Content/Industrials/ElectricPowers/Sundials/ElectricSundialTile.cs:96 — Content/Industrials/ElectricPowers/Sundials/ElectricSundialTile.cs:96-136 | Content/Industrials/ElectricPowers/Throwers/ThrowerTile.cs:94-132 — These two members are variants of one another: 26 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 · Near-duplicate member pair (25 shared lines) · ×1
  • Near-duplicate member pair (25 shared lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:994 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:994-1044 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:1005-1057 — These two members are variants of one another: 25 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 · Near-duplicate member pair (20 shared lines) · ×1
  • Near-duplicate member pair (20 shared lines) Content/Scenarios/Dungeonworld/UI/DungeonworldLoadingScreen.cs:577 — Content/Scenarios/Dungeonworld/UI/DungeonworldLoadingScreen.cs:577-628 | Content/Scenarios/Hadalworld/UI/HadalworldLoadingScreen.cs:434-489 — These two members are variants of one another: 20 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 · Near-duplicate member pair (19 shared lines) · ×1
  • Near-duplicate member pair (19 shared lines) Content/Industrials/ElectricPowers/GridSwitches/GridSwitchTP.cs:266 — Content/Industrials/ElectricPowers/GridSwitches/GridSwitchTP.cs:266-359 | Content/Industrials/ElectricPowers/WireInterfaces/WireInterfaceTP.cs:303-380 — These two members are variants of one another: 19 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 · Edited copy of a member (60 corresponding lines) · ×1
  • Edited copy of a member (60 corresponding lines) Content/Scenarios/Draedon/Quest/DeploySignaltowers/CQETConstructor.cs:358 — Content/Scenarios/Draedon/Quest/DeploySignaltowers/CQETConstructor.cs:358-471 | Content/Scenarios/Draedon/Quest/DeploySignaltowers/CQETConstructor.cs:497-602 — These two members are one piece of code written twice and then edited apart: 60 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (121 corresponding lines) · ×1
  • Edited copy of a member (121 corresponding lines) Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:398 — Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:398-532 | Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:334-454 — These two members are one piece of code written twice and then edited apart: 121 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (112 corresponding lines) · ×1
  • Edited copy of a member (112 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:794 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:794-915 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:772-883 — These two members are one piece of code written twice and then edited apart: 112 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (106 corresponding lines) · ×1
  • Edited copy of a member (106 corresponding lines) Content/NPCs/BloomsandSerpents/States/BssDeathState.cs:36 — Content/NPCs/BloomsandSerpents/States/BssDeathState.cs:36-141 | Content/NPCs/FestersandSerpents/States/FssDeathState.cs:44-169 — These two members are one piece of code written twice and then edited apart: 106 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (111 corresponding lines) · ×1
  • Edited copy of a member (111 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:715 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:715-835 | Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:1104-1214 — These two members are one piece of code written twice and then edited apart: 111 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (92 corresponding lines) · ×1
  • Edited copy of a member (92 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:734 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:734-843 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:419-510 — These two members are one piece of code written twice and then edited apart: 92 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (104 corresponding lines) · ×1
  • Edited copy of a member (104 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:419 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:419-526 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:514-617 — These two members are one piece of code written twice and then edited apart: 104 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (71 corresponding lines) · ×1
  • Edited copy of a member (71 corresponding lines) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberChargeOrbProj.cs:565 — Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberChargeOrbProj.cs:565-639 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberTraceBeamProj.cs:420-490 — These two members are one piece of code written twice and then edited apart: 71 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (72 corresponding lines) · ×1
  • Edited copy of a member (72 corresponding lines) Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:704 — Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:704-775 | Content/Items/Modifys/RTerraBlades/RTerraBladeHeld.cs:932-1008 — These two members are one piece of code written twice and then edited apart: 72 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (74 corresponding lines) · ×1
  • Edited copy of a member (74 corresponding lines) Content/NPCs/BloomsandSerpents/BssLegRig.cs:640 — Content/NPCs/BloomsandSerpents/BssLegRig.cs:640-713 | Content/NPCs/FestersandSerpents/FssLegRig.cs:453-539 — These two members are one piece of code written twice and then edited apart: 74 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (80 corresponding lines) · ×1
  • Edited copy of a member (80 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:546 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:546-634 | Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:842-921 — These two members are one piece of code written twice and then edited apart: 80 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 22+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 22+ corresponding lines) Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:545 — Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:545-569 | Content/Industrials/Modifys/ChargingStationUI.cs:391-413 | Content/Narrative/Presentation/Skins/Brimstone/BrimstonePanelDraw.cs:40-61 | Content/Narrative/Presentation/Skins/StarStream/StarStreamPanelDraw.cs:36-68 | Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersUIs/OceanRaidersRenderer.cs:189-211 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 46+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 46+ corresponding lines) Content/EntrustManager/Styles/DraedonManagerStyle.cs:250 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:250-295 | Content/EntrustManager/Styles/ForestManagerStyle.cs:252-300 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:237-289 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 46 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (61 corresponding lines) · ×1
  • Edited copy of a member (61 corresponding lines) Content/Scenarios/Kiame/Backgrounds/KiameSky.cs:90 — Content/Scenarios/Kiame/Backgrounds/KiameSky.cs:90-150 | Content/Scenarios/Kiame/Overlay/OniRainWorldSky.cs:92-154 — These two members are one piece of code written twice and then edited apart: 61 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (76 corresponding lines) · ×1
  • Edited copy of a member (76 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs:39 — Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs:39-118 | Content/Scenarios/Kiame/KiameWakeResetRender.cs:41-116 — These two members are one piece of code written twice and then edited apart: 76 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (88 corresponding lines) · ×1
  • Edited copy of a member (88 corresponding lines) Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:460 — Content/LegendWeapon/HalibutLegend/DomainSkills/Restarts/HalibutReset.cs:460-552 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaReset.cs:448-535 — These two members are one piece of code written twice and then edited apart: 88 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (69 corresponding lines) · ×1
  • Edited copy of a member (69 corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamGroundField.cs:128 — Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamGroundField.cs:128-196 | Content/Scenarios/Kiyume/Fog/KiyumeGroundField.cs:143-231 — These two members are one piece of code written twice and then edited apart: 69 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (85 corresponding lines) · ×1
  • Edited copy of a member (85 corresponding lines) Content/NPCs/TBUGs/TBUGDialogue.cs:218 — Content/NPCs/TBUGs/TBUGDialogue.cs:218-302 | Content/NPCs/Victors/VictorDialogue.cs:218-306 — These two members are one piece of code written twice and then edited apart: 85 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 67+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 67+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerDiveStrikeState.cs:99 — Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerDiveStrikeState.cs:99-181 | Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerIntroState.cs:200-266 | Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerOrbitalStrikeState.cs:178-254 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 67 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 45+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 45+ corresponding lines) Content/Items/Melee/DragonsScaleGreatsword.cs:650 — Content/Items/Melee/DragonsScaleGreatsword.cs:650-694 | Content/Items/Melee/DragonsScaleGreatsword.cs:860-905 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:1009-1057 | Content/LegendWeapon/HalibutLegend/FishSkills/FishFrostMinnowVFX.cs:317-367 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 45 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 61+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 61+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:638 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:638-698 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:562-630 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:613-680 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 61 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (55 corresponding lines) · ×1
  • Edited copy of a member (55 corresponding lines) Content/NPCs/BloomsandSerpents/BssBody.cs:165 — Content/NPCs/BloomsandSerpents/BssBody.cs:165-221 | Content/NPCs/FestersandSerpents/FssBody.cs:213-267 — These two members are one piece of code written twice and then edited apart: 55 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (70 corresponding lines) · ×1
  • Edited copy of a member (70 corresponding lines) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerVerticalBarrageState.cs:68 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerVerticalBarrageState.cs:68-141 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismHoverShootState.cs:38-107 — These two members are one piece of code written twice and then edited apart: 70 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 57+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 57+ corresponding lines) Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:67 — Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:67-131 | Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgStabGlintOmen.cs:62-119 | Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyGhostNameThread.cs:72-143 | Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyRavenSwoopOmen.cs:77-133 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 57 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 58+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 58+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangProj.cs:63 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangProj.cs:63-124 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailHead.cs:73-138 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoProj.cs:72-129 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 58 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (86 corresponding lines) · ×1
  • Edited copy of a member (86 corresponding lines) Content/Industrials/ElectricPowers/Apiaries/ApiaryTP.cs:299 — Content/Industrials/ElectricPowers/Apiaries/ApiaryTP.cs:299-404 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatTP.cs:314-399 — These two members are one piece of code written twice and then edited apart: 86 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 35+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 35+ corresponding lines) Content/Items/Accessories/Proverbs.cs:226 — Content/Items/Accessories/Proverbs.cs:226-267 | Content/Items/Magic/Pandemoniums/PandemoniumBlastWave.cs:64-102 | Content/Items/Magic/Pandemoniums/PandemoniumChannel.cs:808-848 | Content/Items/Magic/Pandemoniums/PandemoniumCircle.cs:306-345 | Content/Items/Magic/Pandemoniums/PandemoniumRSkill.cs:438-479 | Content/Items/Ranged/BarrenBow.cs:454-488 | Content/Items/Ranged/NeutronBows/NeutronBow.cs:436-472 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumCircle.cs:330-365 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 35 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 36+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 36+ corresponding lines) Content/LegendWeapon/SHPCLegend/Modules/Barrel/RapidBarrelModule.cs:635 — Content/LegendWeapon/SHPCLegend/Modules/Barrel/RapidBarrelModule.cs:635-673 | Content/LegendWeapon/SHPCLegend/Modules/Optic/HoloOpticModule.cs:172-211 | Content/LegendWeapon/SHPCLegend/Modules/Optic/PrecisionOpticModule.cs:218-253 | Content/LegendWeapon/SHPCLegend/Modules/Optic/SniperOpticModule.cs:378-419 | Content/LegendWeapon/SHPCLegend/Modules/Optic/SniperOpticModule.cs:593-632 | Content/LegendWeapon/SHPCLegend/Modules/Stock/BraceStockModule.cs:464-502 | Content/LegendWeapon/SHPCLegend/Modules/Stock/StormStockModule.cs:289-327 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 36 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 40+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 40+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/MachineEffect.cs:102 — Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/MachineEffect.cs:102-144 | Content/Scenarios/Draedon/Tzeentch/TzeentchEffect.cs:47-86 | Content/Scenarios/OldDuke/OldDukeEffect.cs:59-100 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 40 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 52+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 52+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:210 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:210-261 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:230-286 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:210-261 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:261-322 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:221-273 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:221-273 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:229-281 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:208-259 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 52 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 58+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 58+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:254 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:254-311 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:257-318 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:185-245 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:237-296 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 58 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 28+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 28+ corresponding lines) Content/Items/Melee/OniMacheteHands.cs:856 — Content/Items/Melee/OniMacheteHands.cs:856-884 | Content/LegendWeapon/HalibutLegend/FishSkills/Fishotroning.cs:834-875 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaHandRig.cs:68-95 | Content/Wraiths/Projectiles/GhostHandRig.cs:64-91 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 28 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 52+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 52+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:217 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:217-268 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:229-280 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:282-348 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:220-274 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 52 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 28+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 28+ corresponding lines) Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadArcProj.cs:197 — Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadArcProj.cs:197-224 | Content/Items/Accessories/BrutalRelics/Twins/TwinPupilOrbiter.cs:508-535 | Content/Items/Accessories/BrutalRelics/Twins/TwinPupilShots.cs:318-345 | Content/Items/Accessories/BrutalRelics/Twins/TwinPupilTetherBeam.cs:200-228 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs:179-211 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeArcChainProj.cs:222-249 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeHeatRay.cs:167-196 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeSkullBeamProj.cs:178-207 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 28 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 39+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 39+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:819 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:819-858 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1287-1325 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1178-1218 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 39 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 55+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 55+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:243 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:243-304 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:179-238 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:226-281 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:212-269 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:218-272 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 55 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 43+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 43+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:516 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:516-560 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:509-551 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:471-523 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 43 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 30+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 30+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemEyeSpit.cs:49 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemEyeSpit.cs:49-83 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraSeed.cs:49-87 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeLaserBolt.cs:53-82 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsPulseShot.cs:67-108 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 30 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 26+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 26+ corresponding lines) Content/Items/Melee/DestroyersBlade.cs:444 — Content/Items/Melee/DestroyersBlade.cs:444-469 | Content/Items/Melee/DragonsScaleGreatsword.cs:470-495 | Content/Items/Melee/EnergySword.cs:481-506 | Content/Items/Melee/RebelBlade.cs:507-532 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:452-477 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 26 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 35+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 35+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:650 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:650-686 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:656-690 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:672-706 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 35 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 37+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 37+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:534 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:534-582 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:540-588 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:408-444 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:497-544 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:530-577 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 37 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 43+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 43+ corresponding lines) Content/LegendWeapon/HalibutLegend/UI/HalibutItemTooltipPanel.cs:102 — Content/LegendWeapon/HalibutLegend/UI/HalibutItemTooltipPanel.cs:102-148 | Content/LegendWeapon/KikasaLegend/UI/KikasaItemTooltipPanel.cs:139-182 | Content/LegendWeapon/OnikiriLegend/UI/OniItemTooltipPanel.cs:112-154 | Content/LegendWeapon/SHPCLegend/UI/SHPCItemTooltipPanel.cs:205-248 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 43 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 22+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 22+ corresponding lines) Content/LegendWeapon/HalibutLegend/FishSkills/FishIchornVFX.cs:183 — Content/LegendWeapon/HalibutLegend/FishSkills/FishIchornVFX.cs:183-206 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressPetal.cs:271-293 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:323-345 | Content/PRTTypes/PRT_KikasaInkBead.cs:60-81 | Content/PRTTypes/PRT_KikasaTwinsFlame.cs:71-93 | Content/Scenarios/Dungeonworld/NPCs/GaolFireBolt.cs:273-294 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 29+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 29+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:456 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:456-488 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:419-447 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:417-445 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:441-472 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:394-422 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:382-410 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:414-442 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:457-488 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 29 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 44+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 44+ corresponding lines) Content/Items/Summon/BloomCallers/BloomCallerSprout.cs:86 — Content/Items/Summon/BloomCallers/BloomCallerSprout.cs:86-129 | Content/Items/Summon/Deepclaws/DeepclawLobster.cs:101-148 | Content/Items/Summon/EyekiteStaffs/EyekiteMinion.cs:85-129 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 44 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 37+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 37+ corresponding lines) Content/GameModes/BrutalMobs/Ambience/DuneStorm/DuneStormRender.cs:188 — Content/GameModes/BrutalMobs/Ambience/DuneStorm/DuneStormRender.cs:188-224 | Content/GameModes/BrutalMobs/Ambience/Starfall/StarfallAmbientRender.cs:197-233 | Content/GameModes/BrutalMobs/Ambience/Sunkendune/SunkenduneAmbientRender.cs:308-344 | Content/Scenarios/Dungeonworld/Ambience/DungeonworldAmbientRender.cs:110-150 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 37 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 40+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 40+ corresponding lines) Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineStorageProvider.cs:88 — Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineStorageProvider.cs:88-127 | Content/Industrials/ElectricPowers/Crushers/CrusherStorageProvider.cs:97-138 | Content/Industrials/ElectricPowers/Incinerators/IncineratorStorageProvider.cs:105-148 | Content/Industrials/ElectricPowers/Recyclers/RecyclerStorageProvider.cs:93-134 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterStorageProvider.cs:94-133 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 40 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 21+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 21+ corresponding lines) Content/Scenarios/Dungeonworld/DungeonworldGuard.cs:78 — Content/Scenarios/Dungeonworld/DungeonworldGuard.cs:78-105 | Content/Scenarios/Hadalworld/HadalworldGuard.cs:78-105 | Content/Scenarios/Kiame/KiameGuard.cs:78-105 | Content/Scenarios/Kiyume/KiyumeGuard.cs:78-105 | Content/Scenarios/OldNet/OldNetGuard.cs:78-105 | Content/Scenarios/Shepel/CybCourses/CybCourseWorldGuard.cs:84-104 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 31+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 31+ corresponding lines) Content/Industrials/ElectricPowers/Apiaries/ApiaryStorageProvider.cs:172 — Content/Industrials/ElectricPowers/Apiaries/ApiaryStorageProvider.cs:172-202 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherStorageProvider.cs:171-201 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerStorageProvider.cs:171-201 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerStorageProvider.cs:111-141 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatStorageProvider.cs:111-141 | Content/Industrials/ElectricPowers/Throwers/ThrowerStorageProvider.cs:177-207 | Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersStorageProvider.cs:173-203 | Content/Scenarios/OldDuke/OldDuchests/OldDuchestStorageProvider.cs:159-190 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 31 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 27+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 27+ corresponding lines) Content/Items/Melee/OniMacheteHands.cs:534 — Content/Items/Melee/OniMacheteHands.cs:534-562 | Content/Items/Melee/OniMacheteHands.cs:601-627 | Content/LegendWeapon/HalibutLegend/FishSkills/Fishotroning.cs:548-586 | Content/LegendWeapon/HalibutLegend/FishSkills/Fishotroning.cs:632-668 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 27 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 22+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 22+ corresponding lines) Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:330 — Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:330-352 | Content/Items/Melee/DestroyersBlade.cs:345-368 | Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:473-494 | Content/Items/Melee/DragonsScaleGreatsword.cs:358-381 | Content/Items/Melee/EnergySword.cs:374-396 | Content/Items/Melee/RebelBlade.cs:395-418 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:357-380 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 33+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 33+ corresponding lines) Content/NPCs/BloomsandSerpents/BssHead.cs:426 — Content/NPCs/BloomsandSerpents/BssHead.cs:426-465 | Content/NPCs/FestersandSerpents/FssHead.cs:380-415 | Content/NPCs/ScrapCommanders/ScrapCommander.cs:347-379 | Content/NPCs/SeaShrimp/SeaShrimpBoss.cs:319-351 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 33 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 38+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 38+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistThunderOrb.cs:227 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistThunderOrb.cs:227-269 | Content/LegendWeapon/KikasaLegend/KikasaTalismans/Roster/FuTingFX.cs:166-207 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/TwinsTetherArc.cs:116-154 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeArcChainProj.cs:125-162 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpBubbleArc.cs:100-137 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 38 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 24+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 24+ corresponding lines) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:278 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:278-301 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs:310-333 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs:294-317 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:217-240 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterTP.cs:601-628 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:250-273 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 27+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 27+ corresponding lines) Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:250 — Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:250-276 | Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:290-316 | Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:330-359 | Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:373-405 | Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:419-451 | Content/QuestLogs/QLNodes/PostMoonLordBossQuests.cs:465-497 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 27 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 19+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 19+ corresponding lines) Content/Scenarios/OldNet/Gen/Zones/Z1/Z1Rooms.cs:13 — Content/Scenarios/OldNet/Gen/Zones/Z1/Z1Rooms.cs:13-32 | Content/Scenarios/OldNet/Gen/Zones/Z2/Z2Rooms.cs:16-34 | Content/Scenarios/OldNet/Gen/Zones/Z2/Z2Rooms.cs:65-84 | Content/Scenarios/OldNet/Gen/Zones/Z2/Z2Rooms.cs:90-110 | Content/Scenarios/OldNet/Gen/Zones/Z2/Z2Rooms.cs:155-174 | Content/Scenarios/OldNet/Gen/Zones/Z3/Z3Rooms.cs:16-34 | Content/Scenarios/OldNet/Gen/Zones/Z3/Z3Rooms.cs:212-230 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 22+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 22+ corresponding lines) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:436 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:436-464 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs:501-529 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs:476-504 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:441-462 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 19+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 19+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:211 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainFlipRender.cs:211-230 | Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamPullRender.cs:280-299 | Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs:194-215 | Content/Scenarios/Kiame/KiameWakeResetRender.cs:189-210 | Content/Scenarios/Kiame/Overlay/OniRainDescentRender.cs:152-170 | Content/Scenarios/Kiame/Overlay/OniRainWorldRender.cs:213-232 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 13+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 13+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeSlash.cs:115 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeSlash.cs:115-133 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangProj.cs:168-184 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriSlash.cs:192-209 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoProj.cs:198-210 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithSlash.cs:128-145 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshEyeLaser.cs:177-191 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 18+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 18+ corresponding lines) Content/Items/Ranged/CrystalDimming.cs:20 — Content/Items/Ranged/CrystalDimming.cs:20-38 | Content/Items/Ranged/DarkFrostSolstice.cs:26-43 | Content/Items/Ranged/SnowQuay.cs:22-40 | Content/Items/Ranged/SnowQuayMK2.cs:23-41 | Content/Items/Ranged/Snowblindness.cs:16-34 | Content/Items/Ranged/UniversalFrost.cs:21-39 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 20+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 20+ corresponding lines) Content/QuestLogs/QLNodes/CalamityBiomeQuests.cs:50 — Content/QuestLogs/QLNodes/CalamityBiomeQuests.cs:50-69 | Content/QuestLogs/QLNodes/CalamityBiomeQuests.cs:152-171 | Content/QuestLogs/QLNodes/CalamityBiomeQuests.cs:251-271 | Content/QuestLogs/QLNodes/EventQuests.cs:80-100 | Content/QuestLogs/QLNodes/GrowthQuests.cs:13-33 | Content/QuestLogs/QLNodes/GrowthQuests.cs:43-62 | Content/QuestLogs/QLNodes/GrowthQuests.cs:72-92 | Content/QuestLogs/QLNodes/GrowthQuests.cs:133-154 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 20+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 20+ corresponding lines) Content/QuestLogs/QLNodes/CalamityBiomeQuests.cs:83 — Content/QuestLogs/QLNodes/CalamityBiomeQuests.cs:83-103 | Content/QuestLogs/QLNodes/CalamityBiomeQuests.cs:185-204 | Content/QuestLogs/QLNodes/CalamityBiomeQuests.cs:218-237 | Content/QuestLogs/QLNodes/EventQuests.cs:111-138 | Content/QuestLogs/QLNodes/EventQuests.cs:152-172 | Content/QuestLogs/QLNodes/GrowthQuests.cs:102-121 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 30+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 30+ corresponding lines) Content/NPCs/BloomsandSerpents/States/BssCoilRingState.cs:60 — Content/NPCs/BloomsandSerpents/States/BssCoilRingState.cs:60-92 | Content/NPCs/BloomsandSerpents/States/BssFinHuntState.cs:54-85 | Content/NPCs/BloomsandSerpents/States/BssGeyserMarchState.cs:49-78 | Content/NPCs/BloomsandSerpents/States/BssLoopCascadeState.cs:57-92 | Content/NPCs/BloomsandSerpents/States/BssQuicksandState.cs:51-82 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 30 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 21+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 21+ corresponding lines) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterStorageProvider.cs:135 — Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterStorageProvider.cs:135-159 | Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineStorageProvider.cs:177-197 | Content/Industrials/ElectricPowers/Crushers/CrusherStorageProvider.cs:201-225 | Content/Industrials/ElectricPowers/Incinerators/IncineratorStorageProvider.cs:217-242 | Content/Industrials/ElectricPowers/Recyclers/RecyclerStorageProvider.cs:179-203 | Content/Industrials/Generator/Biomass/BiomassStorageProvider.cs:170-194 | Content/Industrials/Generator/Thermal/ThermalStorageProvider.cs:186-210 | Content/Industrials/Generator/Thermal/ThermalStorageProvider.cs:426-450 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 17+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 17+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalDeerclops/DeerclopsPerformancePlayer.cs:48 — Content/NPCs/BrutalNPCs/BrutalDeerclops/DeerclopsPerformancePlayer.cs:48-68 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerSeizeHandProj.cs:220-236 | Content/NPCs/BrutalNPCs/BrutalDestroyer/DestroyerGrabPlayer.cs:101-124 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/EmpressGrabCutscene.cs:78-98 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/EocGrabPerformancePlayer.cs:55-78 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 20+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 20+ corresponding lines) Content/NPCs/BrutalNPCs/BrutalDukeFishron/FishronDeathCutscene.cs:60 — Content/NPCs/BrutalNPCs/BrutalDukeFishron/FishronDeathCutscene.cs:60-79 | Content/NPCs/BrutalNPCs/BrutalGolem/GolemDeathPerformancePlayer.cs:33-52 | Content/NPCs/BrutalNPCs/BrutalMoonLord/MLordPerformancePlayer.cs:31-50 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/PrimeDeathPerformancePlayer.cs:106-125 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 13+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 13+ corresponding lines) Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs:26 — Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs:26-41 | Content/Industrials/ElectricPowers/LifeWeavers/LifeWeaver.cs:22-37 | Content/Industrials/Generator/WindGriven/WGGMK2Wilderness.cs:19-34 | Content/Industrials/Generator/WindGriven/WGGWilderness.cs:19-34 | Content/Industrials/MaterialFlow/Batterys/ThermalBattery.cs:18-33 | Content/Industrials/MaterialFlow/Fluids/FluidTank.cs:22-35 | Content/Scenarios/OldDuke/MermanRod.cs:22-34 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 6+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 6+ corresponding lines) Content/Scenarios/Shenyo/Gifts/ShenyoBossRushGift.cs:28 — Content/Scenarios/Shenyo/Gifts/ShenyoBossRushGift.cs:28-35 | Content/Scenarios/Shenyo/Gifts/ShenyoCalamityEvilGift.cs:26-31 | Content/Scenarios/Shenyo/Gifts/ShenyoDevourerOfGodsGift.cs:26-31 | Content/Scenarios/Shenyo/Gifts/ShenyoEyeOfCthulhuGift.cs:26-31 | Content/Scenarios/Shenyo/Gifts/ShenyoKingSlimeGift.cs:26-31 | Content/Scenarios/Shenyo/Gifts/ShenyoOldDukeGift.cs:26-31 | Content/Scenarios/Shenyo/Gifts/ShenyoSeaShrimpGift.cs:26-31 | Content/Scenarios/Shenyo/Gifts/ShenyoSlimeGodGift.cs:26-31 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 25+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 25+ corresponding lines) Content/NPCs/BloomsandSerpents/States/BssClawFlingState.cs:44 — Content/NPCs/BloomsandSerpents/States/BssClawFlingState.cs:44-71 | Content/NPCs/BloomsandSerpents/States/BssPincerSnapState.cs:49-73 | Content/NPCs/BloomsandSerpents/States/BssPounceState.cs:45-73 | Content/NPCs/BloomsandSerpents/States/BssWindBladeState.cs:47-74 | Content/NPCs/FestersandSerpents/States/FssClawReapState.cs:61-85 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 15+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 15+ corresponding lines) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:353 — Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:353-367 | Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:290-304 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:312-326 | Content/Industrials/ElectricPowers/Recyclers/RecyclerUI.cs:290-304 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterUI.cs:304-318 | Content/Industrials/Generator/Thermal/ThermalGeneratorUI.cs:271-285 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 14+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 14+ corresponding lines) Content/NPCs/ScrapCommanders/ScrapLegionProbe.cs:42 — Content/NPCs/ScrapCommanders/ScrapLegionProbe.cs:42-55 | Content/Scenarios/Dungeonworld/NPCs/Elites/DrownedTurnkey.cs:123-140 | Content/Scenarios/Dungeonworld/NPCs/Elites/LampeaterWisp.cs:90-106 | Content/Scenarios/Dungeonworld/NPCs/GaolDormantSkull.cs:55-70 | Content/Scenarios/Dungeonworld/NPCs/OverseerDormantRig.cs:76-91 | Content/Scenarios/Dungeonworld/NPCs/UndrownedThrone.cs:82-97 | Content/Scenarios/OldNet/NPCs/OldNetTaggerICE.cs:52-67 | Content/Scenarios/Shepel/CybCourses/CybTrainingDummy.cs:41-55 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (9 members, 6+ corresponding lines) · ×1
  • Edited copies of one member (9 members, 6+ corresponding lines) Content/Scenarios/Himayo/Gifts/HimayoBrimstoneElementalGift.cs:26 — Content/Scenarios/Himayo/Gifts/HimayoBrimstoneElementalGift.cs:26-31 | Content/Scenarios/Himayo/Gifts/HimayoCalamitasCloneGift.cs:26-31 | Content/Scenarios/Himayo/Gifts/HimayoDevourerOfGodsGift.cs:26-31 | Content/Scenarios/Himayo/Gifts/HimayoExoMechsGift.cs:26-31 | Content/Scenarios/Himayo/Gifts/HimayoPlanteraGift.cs:28-34 | Content/Scenarios/Himayo/Gifts/HimayoPolterghastGift.cs:28-34 | Content/Scenarios/Himayo/Gifts/HimayoSkeletronPrimeGift.cs:26-31 | Content/Scenarios/Himayo/Gifts/HimayoSupremeCalamitasGift.cs:26-31 | Content/Scenarios/Himayo/Gifts/HimayoTwinsGift.cs:28-34 — These 9 members are one piece of code written 9 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 9 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 17+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 17+ corresponding lines) Content/GameModes/BrutalMobs/DungeonDeep/DungeonDeepNPC.cs:206 — Content/GameModes/BrutalMobs/DungeonDeep/DungeonDeepNPC.cs:206-222 | Content/GameModes/BrutalMobs/FrostLegion/FrostLegionNPC.cs:201-217 | Content/GameModes/BrutalMobs/Graveyard/GraveyardBrutalNPC.cs:129-145 | Content/GameModes/BrutalMobs/Ocean/OceanBrutalNPC.cs:218-234 | Content/GameModes/BrutalMobs/PumpkinMoon/PumpkinMoonNPC.cs:217-233 | Content/GameModes/BrutalMobs/Sandveil/SandveilBrutalNPC.cs:174-190 | Content/GameModes/BrutalMobs/Stoneborn/StonebornBrutalNPC.cs:161-177 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 8+ corresponding lines) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:852 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:852-859 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1091-1098 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:877-884 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1391-1398 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:900-907 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:806-813 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:846-853 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1357-1364 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 11+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 11+ corresponding lines) Content/GameModes/GodSmith/Weapons/Guns/GsShotgun.cs:103 — Content/GameModes/GodSmith/Weapons/Guns/GsShotgun.cs:103-113 | Content/GameModes/GodSmith/Weapons/Guns/GsUzi.cs:92-103 | Content/Industrials/ElectricPowers/Turrets/LaserTurrets/LaserTurretBolt.cs:95-108 | Content/Items/Magic/AriaofTheCosmoses/AriaQSkill.cs:222-235 | Content/LegendWeapon/HalibutLegend/FishSkills/FishEaterofPlankton.cs:94-105 | Content/LegendWeapon/HalibutLegend/FishSkills/FishMud.cs:827-838 | Content/LegendWeapon/HalibutLegend/FishSkills/FishPrincess.cs:592-605 | Content/LegendWeapon/HalibutLegend/FishSkills/FishTropicalBarracuda.cs:185-198 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 5+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 5+ corresponding lines) Content/Narrative/Presentation/Skins/Draedon/DraedonDialogueSkin.cs:47 — Content/Narrative/Presentation/Skins/Draedon/DraedonDialogueSkin.cs:47-51 | Content/Narrative/Presentation/Skins/Kikasa/KikasaDialogueSkin.cs:86-90 | Content/Narrative/Presentation/Skins/Onikiri/OnikiriDialogueSkin.cs:86-90 | Content/Narrative/Presentation/Skins/SHPC/SHPCDialogueSkin.cs:115-129 | Content/Narrative/Presentation/Skins/Tzeentch/TzeentchDialogueSkin.cs:63-70 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 4+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 4+ corresponding lines) Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:377 — Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:377-380 | Content/Items/Melee/DestroyersBlade.cs:329-332 | Content/Items/Melee/DestroyersBladeEXs/DestroyersBladeEXHeld.cs:468-471 | Content/Items/Melee/DragonsScaleGreatsword.cs:342-345 | Content/Items/Melee/EnergySword.cs:358-361 | Content/Items/Melee/RebelBlade.cs:379-382 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:352-355 | Content/Items/Modifys/RTerraBlades/RTerraBladeHeld.cs:456-459 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 1+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 1+ corresponding lines) Content/GameModes/BrutalMobs/Ambience/Tidecall/Projectiles/TidecallRogueWaveProj.cs:323 — Content/GameModes/BrutalMobs/Ambience/Tidecall/Projectiles/TidecallRogueWaveProj.cs:323-326 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDirtParticles.cs:28-28 | Content/LegendWeapon/HalibutLegend/FishSkills/FishVoodooRitual.cs:44-44 | Content/NPCs/BloomsandSerpents/BssPortrait.cs:267-267 | Content/NPCs/FestersandSerpents/Rendering/FssPortrait.cs:326-326 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (2 corresponding lines) · ×1
  • Edited copy of a member (2 corresponding lines) Content/GameModes/BrutalMobs/FrostMoon/FrmMeleeNPC.cs:202 — Content/GameModes/BrutalMobs/FrostMoon/FrmMeleeNPC.cs:202-203 | Content/GameModes/BrutalMobs/FrostMoon/FrmSiegeNPC.cs:151-152 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 7+ corresponding lines) Content/Industrials/ElectricPowers/FluidInjectors/FluidInjectorTile.cs:34 — Content/Industrials/ElectricPowers/FluidInjectors/FluidInjectorTile.cs:34-40 | Content/Industrials/ElectricPowers/FluidPumps/FluidPumpTile.cs:34-40 | Content/Industrials/Generator/BaseGeneratorTile.cs:24-30 | Content/Industrials/MaterialFlow/Batterys/CapacitorMatrix.cs:83-89 | Content/Industrials/MaterialFlow/Batterys/ThermalBattery.cs:73-79 | Content/Industrials/MaterialFlow/Fluids/FluidTank.cs:72-78 | Content/Industrials/MaterialFlow/Fluids/LargeFluidTank.cs:67-73 | Content/Scenarios/OldDuke/OldDuchests/OldDuchest.cs:92-98 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 3+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 3+ corresponding lines) Content/Items/Accessories/ArcaneThroneOfEternity.cs:64 — Content/Items/Accessories/ArcaneThroneOfEternity.cs:64-66 | Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFin.cs:34-38 | Content/Items/Accessories/EmblemOfDread.cs:118-120 | Content/Items/Accessories/EyeOfSingularity.cs:73-75 | Content/Items/Accessories/JusticeUnveileds/JusticeUnveiled.cs:26-28 | Content/Items/Stones/Marbles/MarbleShield.cs:36-39 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (1 corresponding lines) · ×1
  • Edited copy of a member (1 corresponding lines) Content/Items/Melee/OniMachete.cs:340 — Content/Items/Melee/OniMachete.cs:340-340 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSlashRenderer.cs:156-156 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (74–88 lines × 3) · ×1
  • Duplicated block (74–88 lines × 3) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:614 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:614-701 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:431-504 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:560-647 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:614` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (68 lines × 2) · ×1
  • Duplicated block (68 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:340 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:340-407 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:356-423 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs` as WHOLE FILES: this scan already matched 68 separate duplicated blocks between them, totalling at least 933 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:340` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (65 lines × 2) · ×1
  • Duplicated block (65 lines × 2) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerDiveStrikeState.cs:100 — Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerDiveStrikeState.cs:100-164 | Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerOrbitalStrikeState.cs:179-243 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerDiveStrikeState.cs:100` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (88–89 lines × 4) · ×1
  • Duplicated block (88–89 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:326 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:326-413 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:323-411 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:289-376 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:321-408 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs` as WHOLE FILES: this scan already matched 75 separate duplicated blocks between them, totalling at least 912 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:326` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (59–63 lines × 2) · ×1
  • Duplicated block (59–63 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:794 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:794-856 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:772-830 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs` as WHOLE FILES: this scan already matched 79 separate duplicated blocks between them, totalling at least 1151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:794` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (60–61 lines × 2) · ×1
  • Duplicated block (60–61 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamGroundField.cs:132 — Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamGroundField.cs:132-192 | Content/Scenarios/Kiyume/Fog/KiyumeGroundField.cs:152-211 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamGroundField.cs` and `Content/Scenarios/Kiyume/Fog/KiyumeGroundField.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamGroundField.cs:132` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Scenarios/Kiyume/Fog/KiyumeGroundField.cs:151` calls `Sample`, `Color` and `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamGroundField.cs:132` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (58 lines × 2) · ×1
  • Duplicated block (58 lines × 2) Content/NPCs/TBUGs/TBUGDialogue.cs:245 — Content/NPCs/TBUGs/TBUGDialogue.cs:245-302 | Content/NPCs/Victors/VictorDialogue.cs:249-306 — before extracting anything, compare `Content/NPCs/TBUGs/TBUGDialogue.cs` and `Content/NPCs/Victors/VictorDialogue.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/TBUGs/TBUGDialogue.cs:245` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (57 lines × 2) · ×1
  • Duplicated block (57 lines × 2) Content/Scenarios/Draedon/Quest/DeploySignaltowers/CQETConstructor.cs:367 — Content/Scenarios/Draedon/Quest/DeploySignaltowers/CQETConstructor.cs:367-423 | Content/Scenarios/Draedon/Quest/DeploySignaltowers/CQETConstructor.cs:527-583 — 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.
D4 · Code Duplication · Duplicated block (49–54 lines × 2) · ×1
  • Duplicated block (49–54 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:732 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:732-785 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:733-781 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs` as WHOLE FILES: this scan already matched 70 separate duplicated blocks between them, totalling at least 835 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:732` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (52 lines × 2) · ×1
  • Duplicated block (52 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:805 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:805-856 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:971-1022 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs` as WHOLE FILES: this scan already matched 68 separate duplicated blocks between them, totalling at least 933 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:805` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (47–50 lines × 2) · ×1
  • Duplicated block (47–50 lines × 2) Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:258 — Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:258-304 | Content/Items/Modifys/RBloodButcherer.cs:292-341 — before extracting anything, compare `Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs` and `Content/Items/Modifys/RBloodButcherer.cs` as WHOLE FILES: this scan already matched 36 separate duplicated blocks between them, totalling at least 458 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:258` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:308` calls `Sin` and `Content/Items/Modifys/RBloodButcherer.cs:343` 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.
D4 · Code Duplication · Duplicated block (49–50 lines × 2) · ×1
  • Duplicated block (49–50 lines × 2) Content/NPCs/BloomsandSerpents/BssHead.cs:288 — Content/NPCs/BloomsandSerpents/BssHead.cs:288-337 | Content/NPCs/FestersandSerpents/FssHead.cs:247-295 — before extracting anything, compare `Content/NPCs/BloomsandSerpents/BssHead.cs` and `Content/NPCs/FestersandSerpents/FssHead.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 321 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BloomsandSerpents/BssHead.cs:288` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (49 lines × 2) · ×1
  • Duplicated block (49 lines × 2) Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:175 — Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:175-223 | Content/Scenarios/Kiame/Overlay/OniRainExitTransition.cs:132-180 — before extracting anything, compare `Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs` and `Content/Scenarios/Kiame/Overlay/OniRainExitTransition.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 186 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:175` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (45 lines × 3) · ×1
  • Duplicated block (45 lines × 3) Content/EntrustManager/Styles/DraedonManagerStyle.cs:503 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:503-547 | Content/EntrustManager/Styles/ForestManagerStyle.cs:512-556 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:501-545 — before extracting anything, compare `Content/EntrustManager/Styles/DraedonManagerStyle.cs` and `Content/EntrustManager/Styles/ForestManagerStyle.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 334 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/EntrustManager/Styles/DraedonManagerStyle.cs:503` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (47–48 lines × 2) · ×1
  • Duplicated block (47–48 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:945 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:945-991 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1051-1098 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs` as WHOLE FILES: this scan already matched 68 separate duplicated blocks between them, totalling at least 933 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:945` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (46 lines × 2) · ×1
  • Duplicated block (46 lines × 2) Content/Items/Melee/DestroyersBlade.cs:643 — Content/Items/Melee/DestroyersBlade.cs:643-688 | Content/Items/Melee/DestroyersBladeEXs/DestroyersBeamEX.cs:127-172 — before extracting anything, compare `Content/Items/Melee/DestroyersBlade.cs` and `Content/Items/Melee/DestroyersBladeEXs/DestroyersBeamEX.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DestroyersBlade.cs:643` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (44–47 lines × 2) · ×1
  • Duplicated block (44–47 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1108 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1108-1154 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:1063-1106 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs` as WHOLE FILES: this scan already matched 79 separate duplicated blocks between them, totalling at least 1151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1108` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (40–45 lines × 2) · ×1
  • Duplicated block (40–45 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:871 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:871-915 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:844-883 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs` as WHOLE FILES: this scan already matched 79 separate duplicated blocks between them, totalling at least 1151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:871` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (43–45 lines × 2) · ×1
  • Duplicated block (43–45 lines × 2) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismDashPrepareState.cs:37 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismDashPrepareState.cs:37-81 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismPhase2DashPrepareState.cs:36-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 both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismDashPrepareState.cs:37` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (45 lines × 2) · ×1
  • Duplicated block (45 lines × 2) Content/PRTTypes/PRT_AccretionDiskImpact.cs:81 — Content/PRTTypes/PRT_AccretionDiskImpact.cs:81-125 | Content/PRTTypes/PRT_GammaImpact.cs:104-148 — before extracting anything, compare `Content/PRTTypes/PRT_AccretionDiskImpact.cs` and `Content/PRTTypes/PRT_GammaImpact.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 65 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (37–44 lines × 2) · ×1
  • Duplicated block (37–44 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:45 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:45-81 | Content/NPCs/SeaShrimp/Rendering/SeaShrimpRenderer.cs:17-60 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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.
D4 · Code Duplication · Duplicated block (41 lines × 3) · ×1
  • Duplicated block (41 lines × 3) Content/EntrustManager/Styles/DraedonManagerStyle.cs:459 — Content/EntrustManager/Styles/DraedonManagerStyle.cs:459-499 | Content/EntrustManager/Styles/ForestManagerStyle.cs:468-508 | Content/EntrustManager/Styles/HotwindManagerStyle.cs:457-497 — before extracting anything, compare `Content/EntrustManager/Styles/DraedonManagerStyle.cs` and `Content/EntrustManager/Styles/ForestManagerStyle.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 334 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/EntrustManager/Styles/DraedonManagerStyle.cs:459` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (42–43 lines × 2) · ×1
  • Duplicated block (42–43 lines × 2) Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:216 — Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:216-258 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerIceSpikeProj.cs:199-240 — before extracting anything, compare `Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs` and `Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerIceSpikeProj.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 189 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:216` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (38–42 lines × 4) · ×1
  • Duplicated block (38–42 lines × 4) Content/LegendWeapon/HalibutLegend/UI/HalibutItemTooltipPanel.cs:107 — Content/LegendWeapon/HalibutLegend/UI/HalibutItemTooltipPanel.cs:107-148 | Content/LegendWeapon/KikasaLegend/UI/KikasaItemTooltipPanel.cs:144-182 | Content/LegendWeapon/OnikiriLegend/UI/OniItemTooltipPanel.cs:117-154 | Content/LegendWeapon/SHPCLegend/UI/SHPCItemTooltipPanel.cs:211-248 — before extracting anything, compare `Content/LegendWeapon/HalibutLegend/UI/HalibutItemTooltipPanel.cs` and `Content/LegendWeapon/KikasaLegend/UI/KikasaItemTooltipPanel.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/UI/HalibutItemTooltipPanel.cs:107` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/SHPCLegend/UI/SHPCItemTooltipPanel.cs:209` calls `Refresh` and `Content/LegendWeapon/HalibutLegend/UI/HalibutItemTooltipPanel.cs:105` does not — after which the two agree again for 4 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.
D4 · Code Duplication · Duplicated block (41 lines × 2) · ×1
  • Duplicated block (41 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaHandRig.cs:215 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaHandRig.cs:215-255 | Content/Wraiths/Projectiles/GhostHandRig.cs:226-266 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (91–104 lines × 3) · ×1
  • Duplicated block (91–104 lines × 3) Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:426 — Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:426-529 | Content/QuestLogs/Styles/ForestQuestLogStyle.cs:352-442 | Content/QuestLogs/Styles/HotwindQuestLogStyle.cs:350-451 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/QuestLogs/Styles/DraedonQuestLogStyle.cs:426` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (5–40 lines × 3) · ×1
  • Duplicated block (5–40 lines × 3) Content/HackTimes/HackStatusDisplay.cs:271 — Content/HackTimes/HackStatusDisplay.cs:271-275 | Content/HackTimes/HackStatusDisplay.cs:291-330 | Content/HackTimes/HackStatusDisplay.cs:333-364 — 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. 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.
D4 · Code Duplication · Duplicated block (34 lines × 3) · ×1
  • Duplicated block (34 lines × 3) Content/Industrials/ElectricPowers/Apiaries/ApiaryTP.cs:299 — Content/Industrials/ElectricPowers/Apiaries/ApiaryTP.cs:299-332 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:265-298 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatTP.cs:314-347 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Apiaries/ApiaryTP.cs:299` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (34–37 lines × 3) · ×1
  • Duplicated block (34–37 lines × 3) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1499 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1499-1535 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1213-1246 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1408-1444 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1499` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (37 lines × 2) · ×1
  • Duplicated block (37 lines × 2) Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:381 — Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs:381-417 | Content/Items/Melee/WeaverGrievanceses/WGManifestationActor.cs:316-352 — before extracting anything, compare `Content/Items/Melee/Arbiters/ArbiterManifestationActor.cs` and `Content/Items/Melee/WeaverGrievanceses/WGManifestationActor.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 237 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (33–37 lines × 2) · ×1
  • Duplicated block (33–37 lines × 2) Content/LegendWeapon/HalibutLegend/FishSkills/FishBat.cs:641 — Content/LegendWeapon/HalibutLegend/FishSkills/FishBat.cs:641-673 | Content/LegendWeapon/HalibutLegend/FishSkills/FishSwarm.cs:1026-1062 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishBat.cs:641` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (34–36 lines × 2) · ×1
  • Duplicated block (34–36 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:350 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:350-385 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:316-349 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs` as WHOLE FILES: this scan already matched 79 separate duplicated blocks between them, totalling at least 1151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:350` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (30–36 lines × 2) · ×1
  • Duplicated block (30–36 lines × 2) Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemTelegraph.cs:61 — Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemTelegraph.cs:61-90 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeTelegraphLine.cs:70-105 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemTelegraph.cs` and `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeTelegraphLine.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (32 lines × 3) · ×1
  • Duplicated block (32 lines × 3) Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:177 — Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:177-208 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:183-214 | Content/Industrials/ElectricPowers/Recyclers/RecyclerUI.cs:178-209 — before extracting anything, compare `Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs` and `Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 303 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (35 lines × 2) · ×1
  • Duplicated block (35 lines × 2) Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadArcProj.cs:97 — Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadArcProj.cs:97-131 | Content/Items/Stones/Granites/GraniteThrowingKnife.cs:271-305 — before extracting anything, compare `Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadArcProj.cs` and `Content/Items/Stones/Granites/GraniteThrowingKnife.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 70 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (34 lines × 2) · ×1
  • Duplicated block (34 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs:69 — Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs:69-102 | Content/Scenarios/Kiame/KiameWakeResetRender.cs:67-100 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs` and `Content/Scenarios/Kiame/KiameWakeResetRender.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 168 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaResets/KikasaResetRender.cs:69` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (33–35 lines × 2) · ×1
  • Duplicated block (33–35 lines × 2) Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerMotionFX.cs:32 — Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerMotionFX.cs:32-66 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Rendering/EocRenderHelper.cs:138-170 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (34–35 lines × 2) · ×1
  • Duplicated block (34–35 lines × 2) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/TwinsTetherArc.cs:120 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/TwinsTetherArc.cs:120-154 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeArcChainProj.cs:129-162 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/TwinsTetherArc.cs` and `Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeArcChainProj.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 146 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/TwinsTetherArc.cs:120` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (25–34 lines × 3) · ×1
  • Duplicated block (25–34 lines × 3) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:136 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:136-169 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:95-119 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:107-140 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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.
D4 · Code Duplication · Duplicated block (24–34 lines × 2) · ×1
  • Duplicated block (24–34 lines × 2) Content/Items/Melee/OniMacheteHands.cs:856 — Content/Items/Melee/OniMacheteHands.cs:856-879 | Content/LegendWeapon/HalibutLegend/FishSkills/Fishotroning.cs:834-867 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/OniMacheteHands.cs:856` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (33–34 lines × 2) · ×1
  • Duplicated block (33–34 lines × 2) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Rendering/TwinsRenderHelper.cs:398 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Rendering/TwinsRenderHelper.cs:398-431 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Rendering/TwinsRenderHelper.cs:849-881 — 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.
D4 · Code Duplication · Duplicated block (31 lines × 3) · ×1
  • Duplicated block (31 lines × 3) Content/Scenarios/Himayo/ToriiShrines/ToriiShrineLocationFinder.cs:216 — Content/Scenarios/Himayo/ToriiShrines/ToriiShrineLocationFinder.cs:216-246 | Content/Scenarios/Kiame/Gate/KiameGateSpawn.cs:367-397 | Content/Scenarios/Kiame/Overlay/OniUmbrellaWorldSpawn.cs:441-471 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Himayo/ToriiShrines/ToriiShrineLocationFinder.cs:216` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (20–33 lines × 2) · ×1
  • Duplicated block (20–33 lines × 2) Content/LegendWeapon/HalibutLegend/DomainSkills/Superposition.cs:211 — Content/LegendWeapon/HalibutLegend/DomainSkills/Superposition.cs:211-243 | Content/LegendWeapon/HalibutLegend/DomainSkills/YourLevelIsTooLow.cs:867-886 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/DomainSkills/Superposition.cs:211` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (32–33 lines × 2) · ×1
  • Duplicated block (32–33 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:712 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:712-744 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:694-725 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs` as WHOLE FILES: this scan already matched 79 separate duplicated blocks between them, totalling at least 1151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:712` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (32 lines × 4) · ×1
  • Duplicated block (32 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:597 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:597-628 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:603-634 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:559-590 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:592-623 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs` as WHOLE FILES: this scan already matched 75 separate duplicated blocks between them, totalling at least 912 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:597` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (40 lines × 3) · ×1
  • Duplicated block (40 lines × 3) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerDespawnState.cs:215 — Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerDespawnState.cs:215-254 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsDeathState.cs:168-207 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/PrimeDeathState.cs:404-443 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerDespawnState.cs` and `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsDeathState.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 111 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerDespawnState.cs:215` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (28–31 lines × 2) · ×1
  • Duplicated block (28–31 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:110 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:110-140 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:94-121 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs` as WHOLE FILES: this scan already matched 79 separate duplicated blocks between them, totalling at least 1151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (28–30 lines × 3) · ×1
  • Duplicated block (28–30 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:638 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:638-665 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:562-589 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:613-642 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs` as WHOLE FILES: this scan already matched 43 separate duplicated blocks between them, totalling at least 492 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:638` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (29–30 lines × 2) · ×1
  • Duplicated block (29–30 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:296 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:296-324 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterPool.cs:66-95 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterPool.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:296` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (28–29 lines × 3) · ×1
  • Duplicated block (28–29 lines × 3) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:389 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:389-417 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:264-291 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:351-379 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:389` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (27–29 lines × 2) · ×1
  • Duplicated block (27–29 lines × 2) Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:19 — Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:19-47 | Content/Scenarios/Kiame/Overlay/OniRainExitTransition.cs:20-46 — before extracting anything, compare `Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs` and `Content/Scenarios/Kiame/Overlay/OniRainExitTransition.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 186 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Kiame/Overlay/OniRainDescentTransition.cs:19` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (26 lines × 4) · ×1
  • Duplicated block (26 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:766 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:766-791 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:782-807 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:728-753 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:760-785 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs` as WHOLE FILES: this scan already matched 75 separate duplicated blocks between them, totalling at least 912 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:766` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (27–28 lines × 3) · ×1
  • Duplicated block (27–28 lines × 3) Content/NPCs/SeaShrimp/Projectiles/SeaShrimpLeapVortex.cs:125 — Content/NPCs/SeaShrimp/Projectiles/SeaShrimpLeapVortex.cs:125-151 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpMiniVortex.cs:124-150 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpVortexWall.cs:125-152 — before extracting anything, compare `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpLeapVortex.cs` and `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpMiniVortex.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 99 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpLeapVortex.cs:125` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (18–28 lines × 2) · ×1
  • Duplicated block (18–28 lines × 2) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSlashRenderer.cs:20 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSlashRenderer.cs:20-37 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleRenderer.cs:50-77 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (26–27 lines × 8) · ×1
  • Duplicated block (26–27 lines × 8) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:132 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:132-157 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs:145-170 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs:140-165 | Content/Industrials/ElectricPowers/Launchers/PlayerLauncherUI.cs:133-159 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:123-148 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconUI.cs:125-150 | Content/Industrials/ElectricPowers/Sensors/SensorUI.cs:97-122 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:134-159 — before extracting anything, compare `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs` and `Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 188 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:161` calls `Clamp`, `Lerp` and `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:159` 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.
D4 · Code Duplication · Duplicated block (25–27 lines × 6) · ×1
  • Duplicated block (25–27 lines × 6) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:338 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:338-364 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:328-354 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:274-298 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:247-271 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:305-329 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:344-370 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 598 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:338` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (25–27 lines × 5) · ×1
  • Duplicated block (25–27 lines × 5) Content/NPCs/BrutalNPCs/BrutalGolem/Core/GolemScreenEffects.cs:59 — Content/NPCs/BrutalNPCs/BrutalGolem/Core/GolemScreenEffects.cs:59-85 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Core/MLordScreenEffects.cs:46-72 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Core/SkeletronScreenEffects.cs:58-84 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Core/PrimeScreenEffects.cs:46-72 | Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:2809-2833 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalGolem/Core/GolemScreenEffects.cs` and `Content/NPCs/BrutalNPCs/BrutalMoonLord/Core/MLordScreenEffects.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (26–27 lines × 4) · ×1
  • Duplicated block (26–27 lines × 4) Content/Items/Melee/NeutronGlaive.cs:1252 — Content/Items/Melee/NeutronGlaive.cs:1252-1277 | Content/Items/Melee/NeutronScythe.cs:322-348 | Content/Items/Ranged/NeutronBows/EXNeutronExplosionRanged.cs:29-54 | Content/Items/Ranged/NeutronBows/NeutronExplosionRanged.cs:28-53 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
D4 · Code Duplication · Duplicated block (27 lines × 4) · ×1
  • Duplicated block (27 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:671 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:671-697 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:690-716 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:633-659 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:666-692 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs` as WHOLE FILES: this scan already matched 75 separate duplicated blocks between them, totalling at least 912 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:671` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (23–27 lines × 2) · ×1
  • Duplicated block (23–27 lines × 2) Content/Items/Ranged/TiroFinales/FinaleMagicBolt.cs:45 — Content/Items/Ranged/TiroFinales/FinaleMagicBolt.cs:45-67 | Content/Items/Ranged/TiroFinales/FinaleMusketRound.cs:43-69 — before extracting anything, compare `Content/Items/Ranged/TiroFinales/FinaleMagicBolt.cs` and `Content/Items/Ranged/TiroFinales/FinaleMusketRound.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 81 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.
D4 · Code Duplication · Duplicated block (25–26 lines × 8) · ×1
  • Duplicated block (25–26 lines × 8) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1221 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1221-1246 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1575-1600 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1158-1183 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1300-1325 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:1110-1134 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:1002-1027 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1441-1466 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1608-1633 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs` as WHOLE FILES: this scan already matched 68 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1221` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (4–26 lines × 5) · ×1
  • Duplicated block (4–26 lines × 5) Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:890 — Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:890-893 | Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:894-919 | Content/Items/Melee/NeutronGlaive.cs:575-599 | Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:709-733 | Content/Items/Modifys/RBloodButcherer.cs:694-718 — there are 5 copies across 4 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:890` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:736` calls `Pow` and `Content/Items/Melee/NeutronGlaive.cs:601` does not — after which the two agree again for 4 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.
D4 · Code Duplication · Duplicated block (23–26 lines × 3) · ×1
  • Duplicated block (23–26 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:375 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:375-399 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:537-562 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:377-399 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs` as WHOLE FILES: this scan already matched 48 separate duplicated blocks between them, totalling at least 508 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (24–26 lines × 2) · ×1
  • Duplicated block (24–26 lines × 2) Content/EntrustManager/BaseQuestAcceptUI.cs:356 — Content/EntrustManager/BaseQuestAcceptUI.cs:356-381 | Content/UIs/OverhaulSettings/OverhaulSettingsUI.cs:482-505 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (4–26 lines × 3) · ×1
  • Duplicated block (4–26 lines × 3) Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:164 — Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:164-188 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerFrostPulseProj.cs:133-136 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerIceSpikeProj.cs:146-171 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:164` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:188` calls `VertexPositionColorTexture`, `Vector3`, `Vector2` and `Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerFrostPulseProj.cs:136` does not — after which the two agree again for 5 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.
D4 · Code Duplication · Duplicated block (23–26 lines × 2) · ×1
  • Duplicated block (23–26 lines × 2) Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/BrainOfCthulhuAI.cs:179 — Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/BrainOfCthulhuAI.cs:179-204 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/EowHeadAI.cs:327-349 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/BrainOfCthulhuAI.cs:179` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (23 lines × 3) · ×1
  • Duplicated block (23 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1383 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1383-1405 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:898-920 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1292-1314 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 408 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1383` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (24 lines × 3) · ×1
  • Duplicated block (24 lines × 3) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:711 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:711-734 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:514-537 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:657-680 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (20–25 lines × 3) · ×1
  • Duplicated block (20–25 lines × 3) Content/Scenarios/OldDuke/Campsites/OldDuchestLootGenerator.cs:108 — Content/Scenarios/OldDuke/Campsites/OldDuchestLootGenerator.cs:108-127 | Content/Scenarios/OldDuke/Campsites/OldDuchestLootGenerator.cs:130-154 | Content/Scenarios/OldDuke/Campsites/OldDuchestLootGenerator.cs:170-193 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/OldDuke/Campsites/OldDuchestLootGenerator.cs:108` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (23–25 lines × 2) · ×1
  • Duplicated block (23–25 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:459 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:459-483 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:417-439 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs` as WHOLE FILES: this scan already matched 79 separate duplicated blocks between them, totalling at least 1151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:459` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (4–25 lines × 3) · ×1
  • Duplicated block (4–25 lines × 3) Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberChargeOrbProj.cs:540 — Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberChargeOrbProj.cs:540-543 | Content/Scenarios/SupCal/End/EternalBlazingNow/EbnEffect.cs:371-392 | Content/Scenarios/SupCal/SupCalEffect.cs:193-217 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberChargeOrbProj.cs:540` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Scenarios/SupCal/SupCalEffect.cs:219` calls `NextFloat` and `Content/Scenarios/SupCal/End/EternalBlazingNow/EbnEffect.cs:393` 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.
D4 · Code Duplication · Duplicated block (23–24 lines × 11) · ×1
  • Duplicated block (23–24 lines × 11) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1221 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1221-1244 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1575-1598 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1158-1181 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1300-1323 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:1110-1132 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:1002-1025 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1441-1464 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1383-1406 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:898-921 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1292-1315 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1608-1631 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs` as WHOLE FILES: this scan already matched 68 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1221` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1183` calls `EnsureBegin` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:923` 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.
D4 · Code Duplication · Duplicated block (24 lines × 4) · ×1
  • Duplicated block (24 lines × 4) Content/Items/Melee/DestroyersBlade.cs:370 — Content/Items/Melee/DestroyersBlade.cs:370-393 | Content/Items/Melee/DragonsScaleGreatsword.cs:383-406 | Content/Items/Melee/EnergySword.cs:398-421 | Content/Items/Melee/RebelBlade.cs:420-443 — before extracting anything, compare `Content/Items/Melee/DestroyersBlade.cs` and `Content/Items/Melee/DragonsScaleGreatsword.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 419 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.
D4 · Code Duplication · Duplicated block (23–24 lines × 3) · ×1
  • Duplicated block (23–24 lines × 3) Content/NPCs/BloomsandSerpents/BssHead.cs:605 — Content/NPCs/BloomsandSerpents/BssHead.cs:605-627 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/EowHeadAI.cs:397-420 | Content/NPCs/FestersandSerpents/FssHead.cs:546-568 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BloomsandSerpents/BssHead.cs:605` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (51–53 lines × 2) · ×1
  • Duplicated block (51–53 lines × 2) Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs:126 — Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs:126-176 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronSharkTornadoProj.cs:238-290 — before extracting anything, compare `Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs` and `Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronSharkTornadoProj.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 181 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (21–24 lines × 2) · ×1
  • Duplicated block (21–24 lines × 2) Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:355 — Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:355-375 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:382-405 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (22–24 lines × 2) · ×1
  • Duplicated block (22–24 lines × 2) Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerStrikeTelegraph.cs:121 — Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerStrikeTelegraph.cs:121-144 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Projectiles/QueenBeeTelegraphLine.cs:116-137 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerStrikeTelegraph.cs` and `Content/NPCs/BrutalNPCs/BrutalQueenBee/Projectiles/QueenBeeTelegraphLine.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 128 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (23 lines × 37) · ×1
  • Duplicated block (23 lines × 37) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1009 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1009-1031 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:812-834 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1051-1073 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:828-850 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1351-1373 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:943-965 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1049-1071 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:856-878 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:665-687 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:917-939 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:868-890 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:774-796 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:800-822 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:806-828 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1125-1147 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:857-879 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1108-1130 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:864-886 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:943-965 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:909-931 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1225-1247 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:730-752 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:674-696 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:850-872 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1002-1024 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1060-1082 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1179-1201 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:996-1018 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1238-1260 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1192-1214 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:982-1004 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:960-982 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:1005-1027 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1231-1253 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1301-1323 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:730-752 | Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallProj.cs:862-884 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:690` calls `RodTipPos`, `ToRotationVector2` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1033` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (23 lines × 14) · ×1
  • Duplicated block (23 lines × 14) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1220 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1220-1243 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1238-1261 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1574-1597 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1157-1180 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1299-1322 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:1109-1131 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:1001-1024 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1440-1463 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1382-1405 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:897-920 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1537-1560 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1291-1314 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1604-1627 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1607-1630 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs` as WHOLE FILES: this scan already matched 55 separate duplicated blocks between them, totalling at least 611 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1220` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1183` calls `EnsureBegin` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:923` 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.
D4 · Code Duplication · Duplicated block (23 lines × 5) · ×1
  • Duplicated block (23 lines × 5) Content/Industrials/ElectricPowers/Apiaries/ApiaryTP.cs:406 — Content/Industrials/ElectricPowers/Apiaries/ApiaryTP.cs:406-428 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherTP.cs:533-555 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerTP.cs:607-629 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:521-543 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatTP.cs:401-423 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerTP.cs:631` calls `PromptNoEnergy`, `Prompt` and `Content/Industrials/ElectricPowers/Apiaries/ApiaryTP.cs:430` does not — after which the two agree again for 4 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.
D4 · Code Duplication · Duplicated block (22–23 lines × 4) · ×1
  • Duplicated block (22–23 lines × 4) Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:73 — Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:73-94 | Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgStabGlintOmen.cs:68-89 | Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyGhostNameThread.cs:78-100 | Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyRavenSwoopOmen.cs:83-104 — before extracting anything, compare `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs` and `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgStabGlintOmen.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 89 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:73` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (20–23 lines × 4) · ×1
  • Duplicated block (20–23 lines × 4) Content/Items/Melee/StormGoddessSpears/AncientStormGoddessSpear.cs:296 — Content/Items/Melee/StormGoddessSpears/AncientStormGoddessSpear.cs:296-318 | Content/Items/Melee/StormGoddessSpears/AncientStormGoddessSpear.cs:461-483 | Content/Items/Ranged/NeutronBows/EXNeutronArrow.cs:61-80 | Content/Items/Summon/WhiplashGalactica.cs:217-236 — before extracting anything, compare `Content/Items/Melee/StormGoddessSpears/AncientStormGoddessSpear.cs` and `Content/Items/Ranged/NeutronBows/EXNeutronArrow.cs` 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/StormGoddessSpears/AncientStormGoddessSpear.cs:296` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (21–23 lines × 3) · ×1
  • Duplicated block (21–23 lines × 3) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1130 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1130-1152 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:951-971 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1136-1158 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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.
D4 · Code Duplication · Duplicated block (22–23 lines × 3) · ×1
  • Duplicated block (22–23 lines × 3) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1909 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1909-1931 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1558-1579 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1774-1796 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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.
D4 · Code Duplication · Duplicated block (19–23 lines × 2) · ×1
  • Duplicated block (19–23 lines × 2) Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadArcProj.cs:56 — Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadArcProj.cs:56-78 | Content/Items/Stones/Granites/GraniteThrowingKnife.cs:236-254 — before extracting anything, compare `Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadArcProj.cs` and `Content/Items/Stones/Granites/GraniteThrowingKnife.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 70 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadArcProj.cs:56` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (21 lines × 15) · ×1
  • Duplicated block (21 lines × 15) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1220 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1220-1240 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1238-1258 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1574-1594 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1157-1177 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1299-1319 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:1040-1060 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:1109-1129 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:1001-1021 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:1089-1109 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:897-917 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1418-1438 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1537-1557 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1291-1311 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1604-1624 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1607-1627 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs` as WHOLE FILES: this scan already matched 55 separate duplicated blocks between them, totalling at least 611 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (22 lines × 4) · ×1
  • Duplicated block (22 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1050 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1050-1071 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaMinionDrownFX.cs:488-509 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaPlayerDrownFX.cs:524-545 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaScourgeFX.cs:785-806 — 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 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1050` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (15–22 lines × 4) · ×1
  • Duplicated block (15–22 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1110 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1110-1131 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1141-1155 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1451-1472 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:894-915 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs` as WHOLE FILES: this scan already matched 55 separate duplicated blocks between them, totalling at least 611 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1107` calls `BladeDrawRot` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1446` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (21 lines × 4) · ×1
  • Duplicated block (21 lines × 4) Content/UIs/UIEffect/BrimstoneShaderPanel.cs:21 — Content/UIs/UIEffect/BrimstoneShaderPanel.cs:21-41 | Content/UIs/UIEffect/SeaShaderPanel.cs:21-41 | Content/UIs/UIEffect/SulfseaShaderPanel.cs:21-41 | Content/UIs/UIEffect/TzeentchShaderPanel.cs:21-41 — before extracting anything, compare `Content/UIs/UIEffect/BrimstoneShaderPanel.cs` and `Content/UIs/UIEffect/SeaShaderPanel.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 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.
D4 · Code Duplication · Duplicated block (20–22 lines × 3) · ×1
  • Duplicated block (20–22 lines × 3) Content/Industrials/Generator/Biomass/BiomassGeneratorUI.cs:126 — Content/Industrials/Generator/Biomass/BiomassGeneratorUI.cs:126-145 | Content/Industrials/Generator/GeneratorReadout.cs:170-190 | Content/Industrials/Generator/Thermal/ThermalGeneratorUI.cs:151-172 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/Generator/Biomass/BiomassGeneratorUI.cs:126` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (37–39 lines × 2) · ×1
  • Duplicated block (37–39 lines × 2) Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:245 — Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:245-283 | Content/Items/Melee/NeutronGlaive.cs:256-292 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DivineSourceBlades/DivineSourceBladeHeld.cs:245` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (21 lines × 38) · ×1
  • Duplicated block (21 lines × 38) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1010 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1010-1030 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:813-833 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1052-1072 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:829-849 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1352-1372 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:944-964 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1050-1070 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:857-877 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:666-686 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:918-938 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:869-889 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:775-795 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:801-821 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:807-827 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1126-1146 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:858-878 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1109-1129 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:865-885 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:944-964 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:910-930 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1226-1246 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:731-751 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:675-695 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:851-871 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1003-1023 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1061-1081 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1180-1200 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:997-1017 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1239-1259 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1193-1213 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:983-1003 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:961-981 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:1006-1026 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1232-1252 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsFlameBreath.cs:184-204 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1302-1322 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:731-751 | Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallProj.cs:863-883 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:690` calls `RodTipPos`, `ToRotationVector2` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1033` 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.
D4 · Code Duplication · Duplicated block (20 lines × 18) · ×1
  • Duplicated block (20 lines × 18) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1221 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1221-1240 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1239-1258 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1575-1594 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1158-1177 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1300-1319 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:1041-1060 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:1110-1129 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:1002-1021 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1441-1460 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1383-1402 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:1090-1109 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:1039-1058 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:898-917 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1419-1438 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1538-1557 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1292-1311 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1605-1624 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1608-1627 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs` as WHOLE FILES: this scan already matched 55 separate duplicated blocks between them, totalling at least 611 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (21 lines × 5) · ×1
  • Duplicated block (21 lines × 5) Content/Items/Melee/DestroyersBlade.cs:141 — Content/Items/Melee/DestroyersBlade.cs:141-161 | Content/Items/Melee/DragonsScaleGreatsword.cs:157-177 | Content/Items/Melee/EnergySword.cs:171-191 | Content/Items/Melee/RebelBlade.cs:195-215 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:176-196 — before extracting anything, compare `Content/Items/Melee/DestroyersBlade.cs` and `Content/Items/Melee/DragonsScaleGreatsword.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 419 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (19 lines × 4) · ×1
  • Duplicated block (19 lines × 4) Content/Items/Melee/DestroyersBlade.cs:204 — Content/Items/Melee/DestroyersBlade.cs:204-222 | Content/Items/Melee/DragonsScaleGreatsword.cs:213-231 | Content/Items/Melee/EnergySword.cs:227-245 | Content/Items/Melee/RebelBlade.cs:254-272 — before extracting anything, compare `Content/Items/Melee/DestroyersBlade.cs` and `Content/Items/Melee/DragonsScaleGreatsword.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 419 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/DestroyersBlade.cs:204` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (20–21 lines × 3) · ×1
  • Duplicated block (20–21 lines × 3) Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteDiveOmen.cs:66 — Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteDiveOmen.cs:66-85 | Content/GameModes/BrutalMobs/Sky/Projectiles/SkyGaleDiveOmen.cs:79-98 | Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornDiveLane.cs:74-94 — before extracting anything, compare `Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteDiveOmen.cs` and `Content/GameModes/BrutalMobs/Sky/Projectiles/SkyGaleDiveOmen.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 156 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteDiveOmen.cs:66` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (19–20 lines × 4) · ×1
  • Duplicated block (19–20 lines × 4) Content/Items/Melee/Shatterfangs/ShatterfangPRT.cs:56 — Content/Items/Melee/Shatterfangs/ShatterfangPRT.cs:56-74 | Content/LegendWeapon/HalibutLegend/FishSkills/FishEaterofPlanktonVFX.cs:153-172 | Content/LegendWeapon/HalibutLegend/FishSkills/FishHungerVFX.cs:217-236 | Content/LegendWeapon/HalibutLegend/FishSkills/FishRockParticles.cs:149-168 — before extracting anything, compare `Content/Items/Melee/Shatterfangs/ShatterfangPRT.cs` and `Content/LegendWeapon/HalibutLegend/FishSkills/FishRockParticles.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Shatterfangs/ShatterfangPRT.cs:56` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (15–20 lines × 3) · ×1
  • Duplicated block (15–20 lines × 3) Content/Items/Melee/StormGoddessSpears/StormArc.cs:284 — Content/Items/Melee/StormGoddessSpears/StormArc.cs:284-303 | Content/Items/Melee/StormGoddessSpears/StormLightning.cs:284-303 | Content/Projectiles/Lightning.cs:187-201 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/StormGoddessSpears/StormArc.cs:284` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (17–20 lines × 3) · ×1
  • Duplicated block (17–20 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:679 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:679-698 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaMinionDrownFX.cs:264-280 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaPlayerDrownFX.cs:322-339 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:679` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaPlayerDrownFX.cs:319` calls `Vector2` and `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:677` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (26–27 lines × 3) · ×1
  • Duplicated block (26–27 lines × 3) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1742 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1742-1768 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1412-1437 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1607-1633 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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.
D4 · Code Duplication · Duplicated block (18–20 lines × 3) · ×1
  • Duplicated block (18–20 lines × 3) Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:104 — Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:104-121 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs:75-94 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeSkullBeamProj.cs:74-91 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:104` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (16–20 lines × 2) · ×1
  • Duplicated block (16–20 lines × 2) Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFistProj.cs:212 — Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFistProj.cs:212-227 | Content/NPCs/BrutalNPCs/BrutalGolem/Rendering/GolemRenderHelper.cs:35-54 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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.
D4 · Code Duplication · Duplicated block (15–19 lines × 34) · ×1
  • Duplicated block (15–19 lines × 34) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:254 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:254-269 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:210-224 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:230-244 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:210-224 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:261-276 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:257-272 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:266-281 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:185-199 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:194-208 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:237-251 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:221-235 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:221-235 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:229-244 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:208-222 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:267-282 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:217-232 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:275-293 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:216-233 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:243-260 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:229-245 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:282-297 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:184-202 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:179-197 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:220-234 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:235-251 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:226-242 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:233-249 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:233-249 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:255-272 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:212-229 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:218-236 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:266-280 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:259-275 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:267-283 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:254` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (3–19 lines × 6) · ×1
  • Duplicated block (3–19 lines × 6) Content/Items/Magic/WheezingWyrms/WyrmfirePRT.cs:154 — Content/Items/Magic/WheezingWyrms/WyrmfirePRT.cs:154-171 | Content/Items/Melee/CursedflameBloodfists/CursedflamePRT.cs:111-127 | Content/Items/Melee/DawnshatterAzures/DawnshatterPRT.cs:64-81 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCursedVFX.cs:257-259 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDemonicHell.cs:756-774 | Content/PRTTypes/PRT_PallbearerEmber.cs:56-72 — before extracting anything, compare `Content/Items/Magic/WheezingWyrms/WyrmfirePRT.cs` and `Content/Items/Melee/CursedflameBloodfists/CursedflamePRT.cs` 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/WheezingWyrms/WyrmfirePRT.cs:154` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (18 lines × 5) · ×1
  • Duplicated block (18 lines × 5) Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2Scatter.cs:85 — Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2Scatter.cs:85-102 | Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Scatter.cs:192-209 | Content/Scenarios/Dungeonworld/Gen/Layers/L4/L4Scatter.cs:139-156 | Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Scatter.cs:152-169 | Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Scatter.cs:131-148 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2Scatter.cs:85` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (17–19 lines × 3) · ×1
  • Duplicated block (17–19 lines × 3) Content/Industrials/ElectricPowers/Collectors/CollectorUI.cs:505 — Content/Industrials/ElectricPowers/Collectors/CollectorUI.cs:505-522 | Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:443-461 | Content/Industrials/Modifys/ChargingStationUI.cs:295-311 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Collectors/CollectorUI.cs:505` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Industrials/ElectricPowers/Collectors/CollectorUI.cs:505` calls `Rectangle` and `Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:443` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (8–19 lines × 3) · ×1
  • Duplicated block (8–19 lines × 3) Content/Narrative/Common/BaseRecipeDisplayUI.cs:250 — Content/Narrative/Common/BaseRecipeDisplayUI.cs:250-257 | Content/Scenarios/Draedon/Quest/DeploySignaltowers/DeploySignaltowerRender.cs:266-273 | Content/Scenarios/Draedon/Quest/DeploySignaltowers/DeploySignaltowerRender.cs:720-738 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Narrative/Common/BaseRecipeDisplayUI.cs:250` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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.
D4 · Code Duplication · Duplicated block (10–19 lines × 2) · ×1
  • Duplicated block (10–19 lines × 2) Content/Narrative/Presentation/Skins/SHPC/SHPCDialogueSkin.cs:145 — Content/Narrative/Presentation/Skins/SHPC/SHPCDialogueSkin.cs:145-163 | Content/Narrative/Presentation/Skins/Sea/SeaDialogueSkin.cs:81-90 — before extracting anything, compare `Content/Narrative/Presentation/Skins/SHPC/SHPCDialogueSkin.cs` and `Content/Narrative/Presentation/Skins/Sea/SeaDialogueSkin.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Narrative/Presentation/Skins/SHPC/SHPCDialogueSkin.cs:145` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (16–18 lines × 9) · ×1
  • Duplicated block (16–18 lines × 9) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:325 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:325-341 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:324-339 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:300-315 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:321-336 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:336-353 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:287-302 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:287-302 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:295-310 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:319-334 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:325` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (17–18 lines × 8) · ×1
  • Duplicated block (17–18 lines × 8) Content/Scenarios/Kiame/KiameAmbience.cs:225 — Content/Scenarios/Kiame/KiameAmbience.cs:225-242 | Content/Scenarios/Kiame/Overlay/OniRainWorldState.cs:317-334 | Content/Scenarios/Kiyume/Ambience/KiyumeCrowFlight.cs:372-388 | Content/Scenarios/Kiyume/Ambience/KiyumeTraces.cs:251-267 | Content/Scenarios/Kiyume/Fog/KiyumeHoundShade.cs:219-235 | Content/Scenarios/Kiyume/NPCs/FuneralCortegeYokai.cs:1097-1113 | Content/Scenarios/Kiyume/NPCs/LanternGuideYokai.cs:357-373 | Content/Wraiths/Abilities/GhostRains/GhostRainFx.cs:280-297 — before extracting anything, compare `Content/Scenarios/Kiame/KiameAmbience.cs` and `Content/Scenarios/Kiame/Overlay/OniRainWorldState.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Scenarios/Kiame/KiameAmbience.cs:244` calls `ModifyLightingBrightness` and `Content/Scenarios/Kiyume/Fog/KiyumeHoundShade.cs:236` 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.
D4 · Code Duplication · Duplicated block (16 lines × 7) · ×1
  • Duplicated block (16 lines × 7) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:177 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:177-192 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs:192-207 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs:185-200 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:159-174 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconUI.cs:161-176 | Content/Industrials/ElectricPowers/Sensors/SensorUI.cs:136-151 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:174-189 — before extracting anything, compare `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs` and `Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 188 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:177` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs:189` calls `Contains` and `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:175` 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.
D4 · Code Duplication · Duplicated block (16–18 lines × 4) · ×1
  • Duplicated block (16–18 lines × 4) Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs:112 — Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs:112-129 | Content/Scenarios/Draedon/Quest/DraedonTrackerWidgetStyle.cs:127-144 | Content/Scenarios/OldDuke/Quest/SulfseaTrackerWidgetStyle.cs:123-139 | Content/Scenarios/SupCal/Quest/BrimstoneTrackerWidgetStyle.cs:117-132 — before extracting anything, compare `Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs` and `Content/Scenarios/Draedon/Quest/DraedonTrackerWidgetStyle.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutTrackerWidgetStyle.cs:112` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (17–18 lines × 4) · ×1
  • Duplicated block (17–18 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:434 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:434-451 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:420-437 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:394-410 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:436-453 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 598 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:434` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (16–18 lines × 3) · ×1
  • Duplicated block (16–18 lines × 3) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1865 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1865-1882 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1517-1532 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1730-1747 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1865` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (30–33 lines × 2) · ×1
  • Duplicated block (30–33 lines × 2) Content/NPCs/BloomsandSerpents/BssPortrait.cs:206 — Content/NPCs/BloomsandSerpents/BssPortrait.cs:206-238 | Content/NPCs/FestersandSerpents/Rendering/FssPortrait.cs:277-306 — before extracting anything, compare `Content/NPCs/BloomsandSerpents/BssPortrait.cs` and `Content/NPCs/FestersandSerpents/Rendering/FssPortrait.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 108 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BloomsandSerpents/BssPortrait.cs:206` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (15–18 lines × 2) · ×1
  • Duplicated block (15–18 lines × 2) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerHoverShootState.cs:96 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerHoverShootState.cs:96-113 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerSoloRageState.cs:350-364 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerHoverShootState.cs` and `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerSoloRageState.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 47 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerHoverShootState.cs:96` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerHoverShootState.cs:114` calls `PushDashVisuals` and `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerSoloRageState.cs:366` 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.
D4 · Code Duplication · Duplicated block (4–18 lines × 4) · ×1
  • Duplicated block (4–18 lines × 4) Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:593 — Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:593-610 | Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:689-706 | Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:1477-1480 | Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:1564-1567 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:1477` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (14–17 lines × 4) · ×1
  • Duplicated block (14–17 lines × 4) Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs:207 — Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs:207-221 | Content/Items/Magic/Everdeeps/EverdeepMaelstrom.cs:332-345 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronSharkTornadoProj.cs:323-338 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronTsunamiWallProj.cs:175-191 — before extracting anything, compare `Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs` and `Content/Items/Magic/Everdeeps/EverdeepMaelstrom.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs:207` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (14–17 lines × 3) · ×1
  • Duplicated block (14–17 lines × 3) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerHoverShootState.cs:97 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerHoverShootState.cs:97-113 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerSoloRageState.cs:351-364 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerVerticalBarrageState.cs:103-119 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerHoverShootState.cs` and `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerSoloRageState.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 47 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerHoverShootState.cs:114` calls `PushDashVisuals` and `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Retinazer/RetinazerSoloRageState.cs:366` 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.
D4 · Code Duplication · Duplicated block (12–17 lines × 2) · ×1
  • Duplicated block (12–17 lines × 2) Content/Items/Melee/Arbiters/Arbiter.cs:192 — Content/Items/Melee/Arbiters/Arbiter.cs:192-208 | Content/Items/Melee/Cloudwalking.cs:179-190 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/Arbiters/Arbiter.cs:192` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (14–17 lines × 2) · ×1
  • Duplicated block (14–17 lines × 2) Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:436 — Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:436-449 | Content/Scenarios/Kiyume/UI/KiyumeLoadingScreen.cs:390-406 — before extracting anything, compare `Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs` and `Content/Scenarios/Kiyume/UI/KiyumeLoadingScreen.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 214 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/Kiame/UI/KiameLoadingScreen.cs:436` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (14–16 lines × 6) · ×1
  • Duplicated block (14–16 lines × 6) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1828 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1828-1841 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1873-1888 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1489-1502 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1524-1538 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1693-1706 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1738-1753 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1828` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (16 lines × 5) · ×1
  • Duplicated block (16 lines × 5) Content/Industrials/ElectricPowers/Apiaries/ApiaryStorageProvider.cs:182 — Content/Industrials/ElectricPowers/Apiaries/ApiaryStorageProvider.cs:182-197 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherStorageProvider.cs:181-196 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerStorageProvider.cs:181-196 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerStorageProvider.cs:121-136 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatStorageProvider.cs:121-136 — before extracting anything, compare `Content/Industrials/ElectricPowers/Apiaries/ApiaryStorageProvider.cs` and `Content/Industrials/ElectricPowers/AutoFishers/AutoFisherStorageProvider.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Apiaries/ApiaryStorageProvider.cs:182` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10–16 lines × 4) · ×1
  • Duplicated block (10–16 lines × 4) Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutQuestLine.cs:19 — Content/LegendWeapon/HalibutLegend/TrialQuests/HalibutQuestLine.cs:19-34 | Content/LegendWeapon/KikasaLegend/TrialQuests/KikasaTrialQuestLine.cs:21-30 | Content/LegendWeapon/OnikiriLegend/TrialQuests/OnikiriTrialQuestLine.cs:18-27 | Content/LegendWeapon/SHPCLegend/TrialQuests/SHPCTrialQuestLine.cs:17-28 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/TrialQuests/KikasaTrialQuestLine.cs` and `Content/LegendWeapon/OnikiriLegend/TrialQuests/OnikiriTrialQuestLine.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (14–16 lines × 4) · ×1
  • Duplicated block (14–16 lines × 4) Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:105 — Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:105-118 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Projectiles/RetinazerDeathRay.cs:76-91 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeSkullBeamProj.cs:75-88 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofRetinaScanBeam.cs:140-154 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerMawBeamProj.cs:105` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (11–16 lines × 2) · ×1
  • Duplicated block (11–16 lines × 2) Content/EntrustManager/BaseManagerStyle.cs:53 — Content/EntrustManager/BaseManagerStyle.cs:53-63 | Content/EntrustManager/BaseManagerStyle.cs:65-80 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/EntrustManager/BaseManagerStyle.cs:65` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (10–16 lines × 2) · ×1
  • Duplicated block (10–16 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:142 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:142-151 | Content/NPCs/SeaShrimp/Kinematics/ShrimpSkeleton.cs:47-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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.
D4 · Code Duplication · Duplicated block (14 lines × 16) · ×1
  • Duplicated block (14 lines × 16) Content/Items/Accessories/BrutalRelics/Deerclops/WhiteoutVeilRender.cs:73 — Content/Items/Accessories/BrutalRelics/Deerclops/WhiteoutVeilRender.cs:73-86 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonImpactFX.cs:221-234 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleFX.cs:231-244 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleShatter.cs:289-302 | Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Core/BrainScreenRender.cs:58-71 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Rendering/DeerclopsVeilRender.cs:72-85 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Rendering/EmpressScreenRender.cs:107-120 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Rendering/EocFogRender.cs:110-123 | Content/NPCs/BrutalNPCs/BrutalGolem/Rendering/GolemScreenEffectRender.cs:124-137 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistVeilRender.cs:60-73 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordBlackFlashRender.cs:109-122 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordScreenRender.cs:94-107 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Rendering/SkeletronScreenRender.cs:83-96 | Content/Renders/PrimeScreenEffectRender.cs:132-145 | Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:3011-3024 | Content/Scenarios/Dungeonworld/NPCs/Elites/LampeaterWispRendering.cs:227-240 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 16 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 16 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (13–15 lines × 15) · ×1
  • Duplicated block (13–15 lines × 15) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:178 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:178-190 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs:193-205 | Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:174-188 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs:186-198 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:180-194 | Content/Industrials/ElectricPowers/Launchers/PlayerLauncherUI.cs:169-182 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:160-172 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconUI.cs:162-174 | Content/Industrials/ElectricPowers/Recyclers/RecyclerUI.cs:175-189 | Content/Industrials/ElectricPowers/Sensors/SensorUI.cs:137-149 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterUI.cs:183-197 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:175-187 | Content/Industrials/Generator/Biomass/BiomassGeneratorUI.cs:123-135 | Content/Industrials/Generator/GeneratorReadout.cs:167-180 | Content/Industrials/Generator/Thermal/ThermalGeneratorUI.cs:148-162 — before extracting anything, compare `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs` and `Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 188 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:172` calls `Contains` and `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:175` 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.
D4 · Code Duplication · Duplicated block (14 lines × 9) · ×1
  • Duplicated block (14 lines × 9) Content/GameModes/GodSmith/Accessories/Defense/GodSmithShieldChain.cs:275 — Content/GameModes/GodSmith/Accessories/Defense/GodSmithShieldChain.cs:275-288 | Content/GameModes/GodSmith/Accessories/Offense/GodSmithManaFlowerChain.cs:288-301 | Content/GameModes/GodSmith/Accessories/Offense/GodSmithSummonChain.cs:202-215 | Content/GameModes/GodSmith/Armors/Hardmode/GsForbiddenArmor.cs:154-167 | Content/GameModes/GodSmith/Armors/Hardmode/GsSpookyWoodArmor.cs:169-182 | Content/GameModes/GodSmith/Armors/Reset/GsHallowedArmor.cs:124-137 | Content/GameModes/GodSmith/Armors/Reset/GsOreArmorsHardmode.cs:511-524 | Content/GameModes/GodSmith/Armors/Reset/GsSpectreArmors.cs:128-141 | Content/GameModes/GodSmith/Armors/Reset/GsTikiArmor.cs:93-106 — before extracting anything, compare `Content/GameModes/GodSmith/Armors/Hardmode/GsForbiddenArmor.cs` and `Content/GameModes/GodSmith/Armors/Hardmode/GsSpookyWoodArmor.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/GameModes/GodSmith/Armors/Reset/GsTikiArmor.cs:109` calls `AddBuff` and `Content/GameModes/GodSmith/Accessories/Defense/GodSmithShieldChain.cs:291` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (14–15 lines × 9) · ×1
  • Duplicated block (14–15 lines × 9) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:261 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:261-274 | Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:287-300 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs:286-299 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs:319-332 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs:270-283 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs:303-316 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:226-239 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconUI.cs:241-255 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:259-272 — before extracting anything, compare `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs` and `Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 188 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:261` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (14 lines × 7) · ×1
  • Duplicated block (14 lines × 7) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:377 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:377-390 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs:414-427 | Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:412-425 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs:388-401 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:442-455 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:304-317 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:377-390 — before extracting anything, compare `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs` and `Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 188 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (12–15 lines × 6) · ×1
  • Duplicated block (12–15 lines × 6) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1478 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1478-1492 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1195-1206 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleCut.cs:331-345 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleRing.cs:235-249 | Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashMark.cs:226-240 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1387-1401 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1478` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashMark.cs:223` calls `Cos`, `ApplySlashPenetration` and `Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleCut.cs:329` 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.
D4 · Code Duplication · Duplicated block (14–15 lines × 5) · ×1
  • Duplicated block (14–15 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:424 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:424-438 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:410-424 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:349-362 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:385-398 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:426-440 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 598 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:424` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8–15 lines × 5) · ×1
  • Duplicated block (8–15 lines × 5) Content/Narrative/Presentation/Skins/Brimstone/BrimstoneChoiceSkin.cs:127 — Content/Narrative/Presentation/Skins/Brimstone/BrimstoneChoiceSkin.cs:127-141 | Content/Narrative/Presentation/Skins/Draedon/DraedonChoiceSkin.cs:67-75 | Content/Narrative/Presentation/Skins/StarStream/StarStreamChoiceSkin.cs:54-62 | Content/Narrative/Presentation/Skins/Sulfsea/SulfseaChoiceSkin.cs:66-73 | Content/Narrative/Presentation/Skins/Tzeentch/TzeentchChoiceSkin.cs:70-77 — before extracting anything, compare `Content/Narrative/Presentation/Skins/Brimstone/BrimstoneChoiceSkin.cs` and `Content/Narrative/Presentation/Skins/Sulfsea/SulfseaChoiceSkin.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Narrative/Presentation/Skins/Brimstone/BrimstoneChoiceSkin.cs:127` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (6–15 lines × 4) · ×1
  • Duplicated block (6–15 lines × 4) Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkClawCrossProj.cs:125 — Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkClawCrossProj.cs:125-130 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:511-525 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:777-791 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBrimlish.cs:811-825 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkClawCrossProj.cs:125` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (3–15 lines × 5) · ×1
  • Duplicated block (3–15 lines × 5) Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1814 — Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1814-1826 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1857-1871 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1486-1488 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1679-1691 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1722-1736 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1814` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (11–15 lines × 2) · ×1
  • Duplicated block (11–15 lines × 2) Content/LegendWeapon/HalibutLegend/FishSkills/FishBunny.cs:792 — Content/LegendWeapon/HalibutLegend/FishSkills/FishBunny.cs:792-806 | Content/LegendWeapon/HalibutLegend/FishSkills/FishCat.cs:511-521 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishBunny.cs:792` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (5–15 lines × 3) · ×1
  • Duplicated block (5–15 lines × 3) Content/LegendWeapon/OnikiriLegend/UI/OniMeiRenderer.cs:105 — Content/LegendWeapon/OnikiriLegend/UI/OniMeiRenderer.cs:105-109 | Content/LegendWeapon/OnikiriLegend/UI/OniMeiRenderer.cs:755-767 | Content/LegendWeapon/OnikiriLegend/UI/OniMeiRenderer.cs:865-879 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/UI/OniMeiRenderer.cs:105` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/OnikiriLegend/UI/OniMeiRenderer.cs:767` calls `Hash01` and `Content/LegendWeapon/OnikiriLegend/UI/OniMeiRenderer.cs:109` does not — after which the two agree again for 4 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.
D4 · Code Duplication · Duplicated block (4–15 lines × 3) · ×1
  • Duplicated block (4–15 lines × 3) Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowApexFrenzyState.cs:373 — Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowApexFrenzyState.cs:373-376 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowBurrowAmbushState.cs:205-219 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowSplitPincerState.cs:469-483 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowApexFrenzyState.cs:373` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (12–14 lines × 20) · ×1
  • Duplicated block (12–14 lines × 20) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:696 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:696-707 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:594-605 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:773-784 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:600-611 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:943-955 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:710-721 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:724-735 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:642-653 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:504-515 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:692-703 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:573-584 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:556-567 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:556-567 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:589-600 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:660-671 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:790-803 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:805-818 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:626-639 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:931-944 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:960-973 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:696` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:821` calls `PlaySound` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:642` 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.
D4 · Code Duplication · Duplicated block (13–14 lines × 14) · ×1
  • Duplicated block (13–14 lines × 14) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:468 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:468-481 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:429-441 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:434-446 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:427-439 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:494-507 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:467-480 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:453-466 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:424-436 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:404-416 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:392-404 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:424-437 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:424-436 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:469-482 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:486-499 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:468` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13–14 lines × 9) · ×1
  • Duplicated block (13–14 lines × 9) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:733 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:733-746 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:630-642 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:809-821 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:636-648 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:982-995 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:609-621 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:592-604 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:593-606 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:625-637 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:733` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13–14 lines × 6) · ×1
  • Duplicated block (13–14 lines × 6) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1118 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1118-1131 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1260-1273 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:1004-1016 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:831-843 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:1073-1085 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1400-1413 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 598 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1118` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:831` calls `Size` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1260` 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.
D4 · Code Duplication · Duplicated block (13–14 lines × 5) · ×1
  • Duplicated block (13–14 lines × 5) Content/Items/Melee/NeutronGlaive.cs:1262 — Content/Items/Melee/NeutronGlaive.cs:1262-1274 | Content/Items/Melee/NeutronGlaive.cs:1341-1353 | Content/Items/Melee/NeutronScythe.cs:332-345 | Content/Items/Ranged/NeutronBows/EXNeutronExplosionRanged.cs:39-51 | Content/Items/Ranged/NeutronBows/NeutronExplosionRanged.cs:38-50 — there are 5 copies across 4 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/NeutronGlaive.cs:1262` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12–14 lines × 5) · ×1
  • Duplicated block (12–14 lines × 5) Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Rendering/EocFogRender.cs:56 — Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Rendering/EocFogRender.cs:56-69 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistVeilRender.cs:38-50 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Rendering/SkeletronScreenRender.cs:60-73 | Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:2990-3001 | Content/Scenarios/Dungeonworld/NPCs/Elites/LampeaterWispRendering.cs:196-208 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Rendering/EocFogRender.cs` and `Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistVeilRender.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (11–14 lines × 3) · ×1
  • Duplicated block (11–14 lines × 3) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:722 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:722-734 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:832-845 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:725-735 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:722` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12 lines × 22) · ×1
  • Duplicated block (12 lines × 22) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:157 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:157-168 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:192-203 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:172-183 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:179-190 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:169-180 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:192-203 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:141-152 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:127-138 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:160-171 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:194-205 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:175-186 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:171-182 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:183-194 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:188-199 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:191-202 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:166-177 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:156-167 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:208-219 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:170-181 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:203-214 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:150-161 | Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallProj.cs:186-197 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 22 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 22 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:157` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:185` calls `MinionContactDamage` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:155` does not — after which the two agree again for 4 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.
D4 · Code Duplication · Duplicated block (10–13 lines × 21) · ×1
  • Duplicated block (10–13 lines × 21) Content/Industrials/ElectricPowers/Collectors/Collector.cs:74 — Content/Industrials/ElectricPowers/Collectors/Collector.cs:74-84 | Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs:55-65 | Content/Industrials/ElectricPowers/LifeWeavers/LifeWeaverTile.cs:25-35 | Content/Industrials/ElectricPowers/LifeWeavers/WGGLifeWeaver.cs:60-70 | Content/Industrials/ElectricPowers/Lumberjacks/LumberjackTile.cs:24-34 | Content/Industrials/ElectricPowers/Lumberjacks/WGGLumberjack.cs:55-65 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatTile.cs:29-39 | Content/Industrials/ElectricPowers/Spectrometers/Spectrometer.cs:61-71 | Content/Industrials/ElectricPowers/Sundials/ElectricSundialTile.cs:33-44 | Content/Industrials/ElectricPowers/Throwers/ThrowerTile.cs:33-44 | Content/Industrials/Generator/Hydroelectrics/Hydroelectric.cs:80-89 | Content/Industrials/Generator/Hydroelectrics/HydroelectricMK2.cs:70-79 | Content/Industrials/Generator/Thermal/ThermalGeneratorMK2.cs:64-74 | Content/Industrials/Generator/WindGriven/WGGMK2Wilderness.cs:53-64 | Content/Industrials/Generator/WindGriven/WGGWilderness.cs:53-62 | Content/Industrials/Generator/WindGriven/WindGrivenGenerator.cs:89-98 | Content/Industrials/Generator/WindGriven/WindGrivenGeneratorMk2.cs:90-102 | Content/Industrials/MaterialFlow/LaserEnergyTrans.cs:72-82 | Content/Scenarios/OldDuke/MermanRod.cs:57-67 | Content/Scenarios/OldDuke/OldDuchests/OldDuchest.cs:63-74 | OtherMods/Coralite/Arcanes/ArcaneTransformer.cs:48-58 — before extracting anything, compare `Content/Industrials/ElectricPowers/Collectors/Collector.cs` and `Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 49 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.
D4 · Code Duplication · Duplicated block (12–13 lines × 17) · ×1
  • Duplicated block (12–13 lines × 17) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:123 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:123-134 | Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:152-163 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs:136-147 | Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:133-144 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs:131-142 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:139-150 | Content/Industrials/ElectricPowers/Launchers/PlayerLauncherUI.cs:124-135 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:114-125 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconUI.cs:116-127 | Content/Industrials/ElectricPowers/Recyclers/RecyclerUI.cs:134-145 | Content/Industrials/ElectricPowers/Sensors/SensorUI.cs:88-99 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterUI.cs:137-148 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:125-136 | Content/Industrials/ElectricPowers/TeleportStations/TeleportStationUI.cs:186-197 | Content/Industrials/Generator/Biomass/BiomassGeneratorUI.cs:90-101 | Content/Industrials/Generator/GeneratorReadout.cs:124-135 | Content/Industrials/Generator/Thermal/ThermalGeneratorUI.cs:118-130 — before extracting anything, compare `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs` and `Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 188 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:123` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (16 lines × 15) · ×1
  • Duplicated block (16 lines × 15) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1155 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1155-1170 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:915-930 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1174-1189 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:972-987 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1508-1523 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1096-1111 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1237-1252 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:982-997 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:808-823 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:1051-1066 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:977-992 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:876-891 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:936-951 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:909-924 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1377-1392 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (12–13 lines × 14) · ×1
  • Duplicated block (12–13 lines × 14) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:466 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:466-477 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs:531-542 | Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:529-541 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs:506-517 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:563-575 | Content/Industrials/ElectricPowers/Launchers/PlayerLauncherUI.cs:395-406 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:383-394 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconUI.cs:421-432 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterUI.cs:527-539 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:464-475 | Content/Industrials/ElectricPowers/Turrets/TurretControlUI.cs:377-388 | Content/Industrials/Generator/Biomass/BiomassGeneratorUI.cs:366-377 | Content/Industrials/Generator/GeneratorReadout.cs:346-357 | Content/Industrials/Generator/Thermal/ThermalGeneratorUI.cs:505-517 — before extracting anything, compare `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs` and `Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 188 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:466` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:527` calls `ShowTip` and `Content/Industrials/ElectricPowers/Turrets/TurretControlUI.cs:375` 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.
D4 · Code Duplication · Duplicated block (12–13 lines × 13) · ×1
  • Duplicated block (12–13 lines × 13) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainDeco.cs:502 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainDeco.cs:502-514 | Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallMeltFX.cs:399-411 | Content/Scenarios/Kiame/KasaOnis/KasaOniActor.cs:892-904 | Content/Scenarios/Kiame/KiameAmbience.cs:230-242 | Content/Scenarios/Kiame/Overlay/OniRainWorldState.cs:322-334 | Content/Scenarios/Kiyume/Ambience/KiyumeCrowFlight.cs:377-388 | Content/Scenarios/Kiyume/Ambience/KiyumeTraces.cs:256-267 | Content/Scenarios/Kiyume/Fog/KiyumeGroundFogRender.cs:238-249 | Content/Scenarios/Kiyume/Fog/KiyumeHoundShade.cs:224-235 | Content/Scenarios/Kiyume/NPCs/FuneralCortegeYokai.cs:1102-1113 | Content/Scenarios/Kiyume/NPCs/LanternGuideYokai.cs:362-373 | Content/Scenarios/Kiyume/NPCs/ScarecrowWatcherYokai.cs:504-515 | Content/Wraiths/Abilities/GhostRains/GhostRainFx.cs:285-297 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 13 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 13 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainDeco.cs:502` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Scenarios/Kiame/KiameAmbience.cs:244` calls `ModifyLightingBrightness` and `Content/Scenarios/Kiyume/Fog/KiyumeHoundShade.cs:236` 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.
D4 · Code Duplication · Duplicated block (12–13 lines × 11) · ×1
  • Duplicated block (12–13 lines × 11) Content/HackTimes/Protocols/ProjectileTithe.cs:424 — Content/HackTimes/Protocols/ProjectileTithe.cs:424-436 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDetonationProj.cs:29-41 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/HeavyBarrelModule.cs:206-217 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/HypersonicBarrelModule.cs:141-152 | Content/LegendWeapon/SHPCLegend/Modules/Frame/ResonanceFrameModule.cs:564-575 | Content/LegendWeapon/SHPCLegend/Modules/Optic/PrecisionOpticModule.cs:127-138 | Content/LegendWeapon/SHPCLegend/Modules/Optic/SniperOpticModule.cs:470-481 | Content/LegendWeapon/SHPCLegend/Modules/Power/HighVoltageCoreModule.cs:116-127 | Content/LegendWeapon/SHPCLegend/Modules/Stock/ExtenderStockModule.cs:284-296 | Content/LegendWeapon/SHPCLegend/Modules/Stock/KineticDamperModule.cs:98-109 | Content/LegendWeapon/SHPCLegend/Modules/Stock/StormStockModule.cs:376-387 — before extracting anything, compare `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDetonationProj.cs` and `Content/LegendWeapon/SHPCLegend/Modules/Barrel/HeavyBarrelModule.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/HackTimes/Protocols/ProjectileTithe.cs:424` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/SHPCLegend/Modules/Barrel/HypersonicBarrelModule.cs:155` calls `ShouldUpdatePosition` and `Content/HackTimes/Protocols/ProjectileTithe.cs:439` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (11–13 lines × 11) · ×1
  • Duplicated block (11–13 lines × 11) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:993 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:993-1005 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1121-1133 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:901-912 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:710-721 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:964-975 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1187-1199 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1175-1185 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:786-796 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:756-766 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1091-1101 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:1160-1170 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 598 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:750` calls `StartPulse` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1172` does not — after which the two agree again for 4 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.
D4 · Code Duplication · Duplicated block (13 lines × 9) · ×1
  • Duplicated block (13 lines × 9) Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:83 — Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:83-95 | Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgStabGlintOmen.cs:78-90 | Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyGhostNameThread.cs:88-101 | Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyRavenSwoopOmen.cs:93-105 | Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteDiveOmen.cs:66-79 | Content/GameModes/BrutalMobs/NightPack/Projectiles/NightDiveOmen.cs:93-107 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkChargeOmen.cs:105-119 | Content/GameModes/BrutalMobs/Sky/Projectiles/SkyGaleDiveOmen.cs:79-92 | Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornDiveLane.cs:74-88 — before extracting anything, compare `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs` and `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgStabGlintOmen.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 89 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:83` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (12–13 lines × 9) · ×1
  • Duplicated block (12–13 lines × 9) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:425 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:425-437 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:395-406 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:442-454 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:426-438 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:412-424 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:351-362 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:387-398 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:428-440 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:438-450 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs` as WHOLE FILES: this scan already matched 55 separate duplicated blocks between them, totalling at least 611 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:442` calls `RippleAt`, `Vector2` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:351` 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.
D4 · Code Duplication · Duplicated block (12 lines × 8) · ×1
  • Duplicated block (12 lines × 8) Content/GameModes/BrutalMobs/FrostMoon/FrmMeleeNPC.cs:270 — Content/GameModes/BrutalMobs/FrostMoon/FrmMeleeNPC.cs:270-281 | Content/GameModes/BrutalMobs/FrostMoon/FrmSiegeNPC.cs:199-210 | Content/GameModes/BrutalMobs/Martians/MartiansNPC.cs:351-362 | Content/GameModes/BrutalMobs/Meteorite/MeteoriteBrutalNPC.cs:164-175 | Content/GameModes/BrutalMobs/NightPack/NightPackNPC.cs:168-179 | Content/GameModes/BrutalMobs/PumpkinMoon/PumpkinMoonNPC.cs:422-433 | Content/GameModes/BrutalMobs/PumpkinMoon/PumpkinMoonNPC.cs:656-667 | Content/GameModes/BrutalMobs/Sky/SkyBrutalNPC.cs:201-212 — there are 8 copies across 7 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 8 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/FrostMoon/FrmMeleeNPC.cs:270` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (12–13 lines × 7) · ×1
  • Duplicated block (12–13 lines × 7) Content/Items/Accessories/ArcaneThroneOfEternity.cs:325 — Content/Items/Accessories/ArcaneThroneOfEternity.cs:325-336 | Content/Items/Accessories/ArcaneThroneOfEternity.cs:456-467 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDetonationProj.cs:205-217 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberPixelDecomposeProj.cs:85-97 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberReformProj.cs:91-103 | Content/LegendWeapon/SHPCLegend/Modules/Frame/ResonanceFrameModule.cs:695-707 | Content/LegendWeapon/SHPCLegend/Modules/Power/PlasmaInjectorModule.cs:167-179 — before extracting anything, compare `Content/Items/Accessories/ArcaneThroneOfEternity.cs` and `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDetonationProj.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 112 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/ArcaneThroneOfEternity.cs:325` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (8–13 lines × 7) · ×1
  • Duplicated block (8–13 lines × 7) Content/Items/Accessories/Proverbs.cs:253 — Content/Items/Accessories/Proverbs.cs:253-265 | Content/Items/Magic/Pandemoniums/PandemoniumBlastWave.cs:88-100 | Content/Items/Magic/Pandemoniums/PandemoniumChannel.cs:834-846 | Content/Items/Magic/Pandemoniums/PandemoniumCircle.cs:331-343 | Content/Items/Magic/Pandemoniums/PandemoniumRSkill.cs:465-477 | Content/Items/Tools/EncyclopediaofOceanicKnowledge.cs:474-481 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumCircle.cs:354-363 — before extracting anything, compare `Content/Items/Accessories/Proverbs.cs` and `Content/Items/Magic/Pandemoniums/PandemoniumBlastWave.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/Proverbs.cs:253` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (11–13 lines × 5) · ×1
  • Duplicated block (11–13 lines × 5) Content/Cyberwares/Implementation/Sandevistans/SandevistanRender.cs:76 — Content/Cyberwares/Implementation/Sandevistans/SandevistanRender.cs:76-87 | Content/HackTimes/HackTimeRender.cs:106-117 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainRender.cs:69-81 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspaceRender.cs:177-188 | Content/Scenarios/OldNet/Renders/OldNetGradeRender.cs:84-94 — before extracting anything, compare `Content/Cyberwares/Implementation/Sandevistans/SandevistanRender.cs` and `Content/HackTimes/HackTimeRender.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Cyberwares/Implementation/Sandevistans/SandevistanRender.cs:76` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7–13 lines × 4) · ×1
  • Duplicated block (7–13 lines × 4) Content/Narrative/Presentation/Skins/Brimstone/BrimstoneChoiceSkin.cs:59 — Content/Narrative/Presentation/Skins/Brimstone/BrimstoneChoiceSkin.cs:59-71 | Content/Narrative/Presentation/Skins/SHPC/SHPCChoiceSkin.cs:30-36 | Content/Narrative/Presentation/Skins/Sulfsea/SulfseaChoiceSkin.cs:34-40 | Content/Narrative/Presentation/Skins/Tzeentch/TzeentchChoiceSkin.cs:34-40 — before extracting anything, compare `Content/Narrative/Presentation/Skins/Brimstone/BrimstoneChoiceSkin.cs` and `Content/Narrative/Presentation/Skins/Sulfsea/SulfseaChoiceSkin.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (3–13 lines × 4) · ×1
  • Duplicated block (3–13 lines × 4) Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:433 — Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:433-444 | Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:445-447 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:463-475 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:476-478 — before extracting anything, compare `Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs` and `Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 303 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:433` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:446` calls `Draw`, `Rectangle`, `ToRotation` and `Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:448` 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.
D4 · Code Duplication · Duplicated block (9–13 lines × 2) · ×1
  • Duplicated block (9–13 lines × 2) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingUI.cs:364 — Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingUI.cs:364-372 | Content/LegendWeapon/SHPCLegend/UI/SHPCModPanel.cs:222-234 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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.
D4 · Code Duplication · Duplicated block (11 lines × 36) · ×1
  • Duplicated block (11 lines × 36) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:192 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:192-202 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:151-161 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:171-181 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:151-161 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:199-209 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:200-210 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:204-214 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:137-147 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:142-152 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:182-192 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:162-172 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:162-172 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:167-177 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:149-159 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:213-223 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:154-164 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:189-199 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:169-179 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:176-186 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:166-176 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:189-199 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:138-148 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:124-134 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:157-167 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:191-201 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:172-182 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:168-178 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:180-190 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:185-195 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:188-198 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:163-173 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:153-163 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:205-215 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:167-177 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:200-210 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:147-157 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:192` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12 lines × 16) · ×1
  • Duplicated block (12 lines × 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:468 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:468-480 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:429-440 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:434-445 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:427-438 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:494-506 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:467-479 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:453-465 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:424-435 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:404-415 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:392-403 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:424-436 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:424-435 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:469-481 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:545-558 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:479-490 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:486-498 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:468` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:468` calls `RebuildBlades` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:545` 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.
D4 · Code Duplication · Duplicated block (11–12 lines × 15) · ×1
  • Duplicated block (11–12 lines × 15) Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:203 — Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:203-213 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerFrostPulseProj.cs:150-160 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Projectiles/DeerIceSpikeProj.cs:186-196 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSRoyalPillarProj.cs:146-157 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Rendering/KingSlimeGelFX.cs:194-204 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordRayRender.cs:55-65 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenChandelierProj.cs:170-180 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenCrystalPrisonProj.cs:180-190 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenCrystalSpireProj.cs:160-170 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenGaleFieldProj.cs:126-136 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenPrismBeamProj.cs:296-306 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenRoyalChandelierProj.cs:178-188 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Rendering/QueenPrismNodeRenderer.cs:74-84 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofRetinaScanBeam.cs:246-256 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofRotBeamProj.cs:176-186 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 15 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 15 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Accessories/BrutalRelics/Deerclops/RelicIceSpikeProj.cs:203` calls `SetValue` and `Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenChandelierProj.cs:170` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (9–12 lines × 15) · ×1
  • Duplicated block (9–12 lines × 15) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1200 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1200-1211 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:958-966 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1221-1229 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:1016-1024 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1554-1565 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1138-1148 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1280-1290 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:1023-1031 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:850-858 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:1092-1100 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:1022-1030 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:919-927 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:981-992 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:952-960 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1420-1430 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1200` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (12 lines × 13) · ×1
  • Duplicated block (12 lines × 13) Content/Items/Accessories/BrutalRelics/EyeOfCthulhu/BloodfogIrisRender.cs:46 — Content/Items/Accessories/BrutalRelics/EyeOfCthulhu/BloodfogIrisRender.cs:46-57 | Content/Items/Melee/HeartcarverCore.cs:262-273 | Content/Items/Melee/OniMacheteHands.cs:1607-1618 | Content/Items/Melee/SpearOfLonginuses/LonginusAssets.cs:105-116 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleFX.cs:215-226 | Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Core/BrainScreenRender.cs:42-53 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Rendering/EocFogRender.cs:63-74 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistVeilRender.cs:44-55 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordBlackFlashRender.cs:93-104 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Rendering/SkeletronScreenRender.cs:67-78 | Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:2995-3006 | Content/Scenarios/Dungeonworld/NPCs/Elites/LampeaterWispRendering.cs:202-213 | Content/Scenarios/Dungeonworld/NPCs/OverseerVfx.cs:246-257 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleFX.cs` and `Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Core/BrainScreenRender.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Accessories/BrutalRelics/EyeOfCthulhu/BloodfogIrisRender.cs:60` calls `SetRenderTarget` and `Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:3007` 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.
D4 · Code Duplication · Duplicated block (11–12 lines × 12) · ×1
  • Duplicated block (11–12 lines × 12) Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:230 — Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:230-240 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT2.cs:127-137 | Content/GameModes/GodSmith/Weapons/Shortswords/GsThrustHeldBase.cs:286-296 | Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:111-121 | Content/Items/Melee/CosmicCalamity.cs:143-153 | Content/Items/Melee/DawnshatterAzures/DawnshatterHeld.cs:124-134 | Content/Items/Melee/EnergySword.cs:154-164 | Content/Items/Melee/NeutronGlaive.cs:199-209 | Content/Items/Melee/RebelBlade.cs:178-188 | Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:117-127 | Content/Items/Modifys/RBloodButcherer.cs:185-195 | Content/Items/Modifys/RTerraBlades/RTerraBladeHeld.cs:151-162 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 12 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 12 times.
D4 · Code Duplication · Duplicated block (9–12 lines × 12) · ×1
  • Duplicated block (9–12 lines × 12) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:456 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:456-467 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:419-428 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:424-433 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:417-426 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:482-493 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:455-466 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:373-381 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:414-423 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:394-403 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:382-391 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:412-423 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:414-423 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:456` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12 lines × 10) · ×1
  • Duplicated block (12 lines × 10) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistIceShard.cs:94 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistIceShard.cs:94-105 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressPetal.cs:101-112 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemEyeSpit.cs:63-74 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraSeed.cs:68-79 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeLaserBolt.cs:62-73 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeBloodBee.cs:97-108 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeStinger.cs:143-154 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronBloodSkull.cs:104-115 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsPulseShot.cs:88-99 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshLeech.cs:94-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 10 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 10 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistIceShard.cs:94` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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.
D4 · Code Duplication · Duplicated block (11–12 lines × 8) · ×1
  • Duplicated block (11–12 lines × 8) Content/Industrials/ElectricPowers/Collectors/Collector.cs:112 — Content/Industrials/ElectricPowers/Collectors/Collector.cs:112-122 | Content/Industrials/ElectricPowers/HealingStations/HealStationTile.cs:113-124 | Content/Industrials/ElectricPowers/ShieldGenerators/ShieldGeneratorTile.cs:113-124 | Content/Industrials/ElectricPowers/Suppressors/PacifierTowerTile.cs:113-124 | Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:184-195 | Content/Industrials/ElectricPowers/Turrets/CryoTurrets/CryoTurretTile.cs:113-124 | Content/Industrials/ElectricPowers/Turrets/FlameTurrets/FlameTurretTile.cs:113-124 | Content/Industrials/ElectricPowers/Turrets/LaserTurrets/LaserTurretTile.cs:113-124 — before extracting anything, compare `Content/Industrials/ElectricPowers/Collectors/Collector.cs` and `Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Collectors/Collector.cs:112` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8–12 lines × 8) · ×1
  • Duplicated block (8–12 lines × 8) Content/Items/Accessories/Proverbs.cs:254 — Content/Items/Accessories/Proverbs.cs:254-265 | Content/Items/Magic/Pandemoniums/PandemoniumBlastWave.cs:89-100 | Content/Items/Magic/Pandemoniums/PandemoniumChannel.cs:835-846 | Content/Items/Magic/Pandemoniums/PandemoniumCircle.cs:332-343 | Content/Items/Magic/Pandemoniums/PandemoniumRSkill.cs:466-477 | Content/Items/Tools/EncyclopediaofOceanicKnowledge.cs:474-481 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumCircle.cs:355-363 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreezeGlobalNPC.cs:101-111 — before extracting anything, compare `Content/Items/Accessories/Proverbs.cs` and `Content/Items/Magic/Pandemoniums/PandemoniumBlastWave.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/Proverbs.cs:254` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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.
D4 · Code Duplication · Duplicated block (11–12 lines × 6) · ×1
  • Duplicated block (11–12 lines × 6) Content/LegendWeapon/SHPCLegend/Modules/Barrel/RapidBarrelModule.cs:651 — Content/LegendWeapon/SHPCLegend/Modules/Barrel/RapidBarrelModule.cs:651-661 | Content/LegendWeapon/SHPCLegend/Modules/Optic/HoloOpticModule.cs:188-198 | Content/LegendWeapon/SHPCLegend/Modules/Optic/PrecisionOpticModule.cs:230-241 | Content/LegendWeapon/SHPCLegend/Modules/Optic/SniperOpticModule.cs:397-407 | Content/LegendWeapon/SHPCLegend/Modules/Optic/SniperOpticModule.cs:610-620 | Content/LegendWeapon/SHPCLegend/Modules/Stock/ExtenderStockModule.cs:428-438 — there are 6 copies across 5 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 6 sites; resolving a subset leaves the remainder to drift apart. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/SHPCLegend/Modules/Optic/HoloOpticModule.cs:187` calls `SetValue`, `ToVector3` and `Content/LegendWeapon/SHPCLegend/Modules/Barrel/RapidBarrelModule.cs:651` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (10–12 lines × 4) · ×1
  • Duplicated block (10–12 lines × 4) Content/Industrials/ElectricPowers/Apiaries/ApiaryTP.cs:647 — Content/Industrials/ElectricPowers/Apiaries/ApiaryTP.cs:647-656 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerTP.cs:703-712 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTP.cs:787-798 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatTP.cs:606-617 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Apiaries/ApiaryTP.cs:647` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (9–12 lines × 3) · ×1
  • Duplicated block (9–12 lines × 3) Content/Cyberwares/Tutorial/CyberwareGuideLead.cs:406 — Content/Cyberwares/Tutorial/CyberwareGuideLead.cs:406-414 | Content/LegendWeapon/OnikiriLegend/UI/OniGhostShadowDraw.cs:47-58 | Content/Scenarios/Shepel/CybCourses/CybCourseCardStyle.cs:66-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Cyberwares/Tutorial/CyberwareGuideLead.cs:406` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8–12 lines × 2) · ×1
  • Duplicated block (8–12 lines × 2) Content/LegendWeapon/HalibutLegend/FishSkills/FishSwarm.cs:534 — Content/LegendWeapon/HalibutLegend/FishSkills/FishSwarm.cs:534-541 | Content/LegendWeapon/HalibutLegend/FishSkills/FishSwarm.cs:849-860 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishSwarm.cs:534` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10 lines × 66) · ×1
  • Duplicated block (10 lines × 66) Content/Industrials/ElectricPowers/Apiaries/Apiary.cs:29 — Content/Industrials/ElectricPowers/Apiaries/Apiary.cs:29-38 | Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafter.cs:15-24 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisher.cs:31-40 | Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachine.cs:14-23 | Content/Industrials/ElectricPowers/Collectors/Collector.cs:29-38 | Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs:26-35 | Content/Industrials/ElectricPowers/Crushers/Crusher.cs:15-24 | Content/Industrials/ElectricPowers/ElectricMinRocket.cs:35-44 | Content/Industrials/ElectricPowers/FluidInjectors/FluidInjector.cs:14-23 | Content/Industrials/ElectricPowers/FluidPumps/FluidPump.cs:14-23 | Content/Industrials/ElectricPowers/GridSwitches/GridSwitch.cs:27-36 | Content/Industrials/ElectricPowers/HealingStations/HealStation.cs:29-38 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmer.cs:27-36 | Content/Industrials/ElectricPowers/Incinerators/Incinerator.cs:14-23 | Content/Industrials/ElectricPowers/Launchers/PlayerLauncher.cs:25-34 | Content/Industrials/ElectricPowers/LifeWeavers/LifeWeaver.cs:22-31 | Content/Industrials/ElectricPowers/LifeWeavers/WGGLifeWeaver.cs:31-40 | Content/Industrials/ElectricPowers/Lumberjacks/Lumberjack.cs:26-35 | Content/Industrials/ElectricPowers/Lumberjacks/WGGLumberjack.cs:26-35 | Content/Industrials/ElectricPowers/MiningMachines/MiningMachine.cs:27-36 | Content/Industrials/ElectricPowers/MiningMachines/MiningMachineMk2.cs:27-36 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmer.cs:27-36 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeacon.cs:25-34 | Content/Industrials/ElectricPowers/Recyclers/Recycler.cs:14-23 | Content/Industrials/ElectricPowers/Sensors/Sensor.cs:68-77 | Content/Industrials/ElectricPowers/ShieldGenerators/ShieldGenerator.cs:29-38 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuter.cs:14-23 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVat.cs:31-40 | Content/Industrials/ElectricPowers/Spectrometers/Spectrometer.cs:24-33 | Content/Industrials/ElectricPowers/Sundials/ElectricSundial.cs:29-38 | Content/Industrials/ElectricPowers/Suppressors/PacifierTower.cs:29-38 | Content/Industrials/ElectricPowers/TeleportStations/TeleportStation.cs:29-38 | Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:31-40 | Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:77-86 | Content/Industrials/ElectricPowers/Throwers/Thrower.cs:33-42 | Content/Industrials/ElectricPowers/Turrets/CryoTurrets/CryoTurret.cs:29-38 | Content/Industrials/ElectricPowers/Turrets/FlameTurrets/FlameTurret.cs:33-42 | Content/Industrials/ElectricPowers/Turrets/LaserTurrets/LaserTurret.cs:29-38 | Content/Industrials/ElectricPowers/WeatherControllers/WeatherController.cs:29-38 | Content/Industrials/ElectricPowers/WireInterfaces/WireInterface.cs:33-42 | Content/Industrials/Generator/Biomass/BiomassGenerator.cs:35-44 | Content/Industrials/Generator/Hydroelectrics/Hydroelectric.cs:25-34 | Content/Industrials/Generator/Hydroelectrics/HydroelectricMK2.cs:24-33 | Content/Industrials/Generator/MagmaThermal/MagmaThermalGenerator.cs:29-38 | Content/Industrials/Generator/SolarPanels/SolarPanel.cs:163-172 | Content/Industrials/Generator/SolarPanels/SolarPanelMK2.cs:23-32 | Content/Industrials/Generator/Thermal/ThermalGenerator.cs:21-30 | Content/Industrials/Generator/Thermal/ThermalGeneratorMK2.cs:20-29 | Content/Industrials/Generator/WindGriven/WGGMK2Wilderness.cs:19-28 | Content/Industrials/Generator/WindGriven/WGGWilderness.cs:19-28 | Content/Industrials/Generator/WindGriven/WindGrivenGenerator.cs:31-40 | Content/Industrials/Generator/WindGriven/WindGrivenGeneratorMk2.cs:31-40 | Content/Industrials/MaterialFlow/Batterys/CapacitorMatrix.cs:29-38 | Content/Industrials/MaterialFlow/Batterys/ThermalBattery.cs:18-27 | Content/Industrials/MaterialFlow/Fluids/FluidTank.cs:22-31 | Content/Industrials/MaterialFlow/Fluids/LargeFluidTank.cs:17-26 | Content/Industrials/MaterialFlow/LaserEnergyTrans.cs:26-35 | Content/Industrials/MaterialFlow/Pipelines/BasePipelineItem.cs:14-23 | Content/Items/Painting/CalSelfPortrait.cs:12-21 | Content/Items/Painting/WUTIVSelfPortrait.cs:12-21 | Content/Items/Placeable/StarflowPlatedBlock.cs:12-21 | Content/Items/Tools/SirenMusicalBox.cs:36-45 | Content/Scenarios/Draedon/Quest/DeploySignaltowers/CQETConstructor.cs:29-38 | Content/Scenarios/Draedon/Quest/DeploySignaltowers/DeploySignaltower.cs:20-29 | Content/Scenarios/OldDuke/OceanRaiderses/OceanRaiders.cs:27-36 | Content/Scenarios/OldDuke/OldDuchests/OldDuchest.cs:26-35 — before extracting anything, compare `Content/Industrials/ElectricPowers/Collectors/Collector.cs` and `Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 49 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Apiaries/Apiary.cs:29` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Industrials/ElectricPowers/ElectricMinRocket.cs:33` calls `VaultLoaden` and `Content/Industrials/ElectricPowers/Apiaries/Apiary.cs:27` 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.
D4 · Code Duplication · Duplicated block (10 lines × 39) · ×1
  • Duplicated block (10 lines × 39) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1014 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1014-1023 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:817-826 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1056-1065 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:833-842 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1356-1365 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:948-957 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1054-1063 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:861-870 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:670-679 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:922-931 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:873-882 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:779-788 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:805-814 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:811-820 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1130-1139 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:862-871 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1113-1122 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:869-878 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:948-957 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:914-923 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1230-1239 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:735-744 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:679-688 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:855-864 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1007-1016 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1065-1074 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1184-1193 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1001-1010 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1243-1252 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1197-1206 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:987-996 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:965-974 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:1010-1019 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1236-1245 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsFlameBreath.cs:188-197 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1306-1315 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshLeech.cs:123-132 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:735-744 | Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallProj.cs:867-876 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1014` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (10–11 lines × 18) · ×1
  • Duplicated block (10–11 lines × 18) Content/Items/Accessories/ArcaneThroneOfEternity.cs:451 — Content/Items/Accessories/ArcaneThroneOfEternity.cs:451-460 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDetonationProj.cs:200-209 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberShockwaveProj.cs:86-95 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberFreezeWaveProj.cs:79-88 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberPixelDecomposeProj.cs:80-89 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberReformProj.cs:86-95 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/HeavyBarrelModule.cs:312-321 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/HypersonicBarrelModule.cs:205-214 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/RapidBarrelModule.cs:653-662 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/ScattershotBarrelModule.cs:378-387 | Content/LegendWeapon/SHPCLegend/Modules/Frame/ResonanceFrameModule.cs:690-700 | Content/LegendWeapon/SHPCLegend/Modules/Optic/HoloOpticModule.cs:190-199 | Content/LegendWeapon/SHPCLegend/Modules/Optic/PrecisionOpticModule.cs:233-242 | Content/LegendWeapon/SHPCLegend/Modules/Optic/SniperOpticModule.cs:399-408 | Content/LegendWeapon/SHPCLegend/Modules/Optic/SniperOpticModule.cs:612-621 | Content/LegendWeapon/SHPCLegend/Modules/Power/PlasmaInjectorModule.cs:162-171 | Content/LegendWeapon/SHPCLegend/Modules/Stock/ExtenderStockModule.cs:430-439 | Content/LegendWeapon/SHPCLegend/Modules/Stock/SteadyStockModule.cs:560-570 — before extracting anything, compare `Content/Items/Accessories/ArcaneThroneOfEternity.cs` and `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDetonationProj.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 112 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberShockwaveProj.cs:82` calls `SetValue` and `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDetonationProj.cs:196` 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.
D4 · Code Duplication · Duplicated block (10–11 lines × 16) · ×1
  • Duplicated block (10–11 lines × 16) Content/Scenarios/OldNet/Tiles/OldNetAccessTerminalTile.cs:34 — Content/Scenarios/OldNet/Tiles/OldNetAccessTerminalTile.cs:34-44 | Content/Scenarios/OldNet/Tiles/OldNetBreakerTile.cs:25-34 | Content/Scenarios/OldNet/Tiles/OldNetCacheTile.cs:27-36 | Content/Scenarios/OldNet/Tiles/OldNetCipherVaultTile.cs:31-41 | Content/Scenarios/OldNet/Tiles/OldNetColdNodeTile.cs:30-40 | Content/Scenarios/OldNet/Tiles/OldNetDataNodeTile.cs:23-33 | Content/Scenarios/OldNet/Tiles/OldNetEchoNodeTile.cs:28-37 | Content/Scenarios/OldNet/Tiles/OldNetEncryptedNodeTile.cs:28-38 | Content/Scenarios/OldNet/Tiles/OldNetEscrowTile.cs:27-37 | Content/Scenarios/OldNet/Tiles/OldNetEventNodeTile.cs:27-36 | Content/Scenarios/OldNet/Tiles/OldNetLedgerDockTile.cs:26-36 | Content/Scenarios/OldNet/Tiles/OldNetLogoutTerminalTile.cs:19-29 | Content/Scenarios/OldNet/Tiles/OldNetRelayTile.cs:24-34 | Content/Scenarios/OldNet/Tiles/OldNetRelicTile.cs:35-45 | Content/Scenarios/OldNet/Tiles/OldNetSentryMineTile.cs:27-36 | Content/Scenarios/OldNet/Tiles/OldNetTripwireTile.cs:29-38 — 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 16 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (10–11 lines × 14) · ×1
  • Duplicated block (10–11 lines × 14) Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:332 — Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:332-341 | Content/Items/Magic/AriaofTheCosmoses/GammaRayBeam.cs:215-225 | Content/Items/Magic/CommandersStaff.cs:362-371 | Content/Items/Melee/DragonsScaleGreatsword.cs:685-694 | Content/Items/Melee/DragonsScaleGreatsword.cs:896-905 | Content/Items/Melee/Heartcarver.cs:520-529 | Content/Items/Melee/HeartcarverHeart.cs:261-270 | Content/Items/Melee/OniMacheteHands.cs:1507-1516 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:1048-1057 | Content/Items/Ranged/CrystalDimming.cs:412-421 | Content/Items/Ranged/UniversalFrost.cs:404-413 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDemonicHell.cs:294-303 | Content/LegendWeapon/HalibutLegend/FishSkills/FishRock.cs:773-782 | Content/LegendWeapon/HalibutLegend/FishSkills/FishVariegatedLard.cs:711-720 — there are 14 copies across 13 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 14 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:332` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Accessories/BrutalRelics/Destroyer/ProbeOrbitalStrike.cs:331` calls `SetValue` and `Content/Items/Melee/OniMacheteHands.cs:1506` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (11 lines × 13) · ×1
  • Duplicated block (11 lines × 13) Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:229 — Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:229-239 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT2.cs:126-136 | Content/GameModes/GodSmith/Weapons/Shortswords/GsThrustHeldBase.cs:285-295 | Content/Items/Melee/Abyssrends/AbyssrendHeld.cs:110-120 | Content/Items/Melee/CosmicCalamity.cs:142-152 | Content/Items/Melee/DawnshatterAzures/DawnshatterHeld.cs:123-133 | Content/Items/Melee/EnergySword.cs:153-163 | Content/Items/Melee/NeutronGlaive.cs:198-208 | Content/Items/Melee/RebelBlade.cs:177-187 | Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:116-126 | Content/Items/Melee/StormGoddessSpears/StormGoddessSpearHeld.cs:68-78 | Content/Items/Modifys/RBloodButcherer.cs:184-194 | Content/Items/Modifys/RTerraBlades/RTerraBladeHeld.cs:150-161 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 13 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 13 times. 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.
D4 · Code Duplication · Duplicated block (11 lines × 11) · ×1
  • Duplicated block (11 lines × 11) Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsDeadlySphereSawProj.cs:42 — Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsDeadlySphereSawProj.cs:42-53 | Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsEmpressFinaleProj.cs:45-56 | Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsImpPyreProj.cs:34-45 | Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsOpticCrossrayProj.cs:33-44 | Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsRavenOmenProj.cs:44-54 | Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsStardustDragonRiftProj.cs:48-59 | Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsStormTigerRendProj.cs:44-55 | Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsTempestSurgeProj.cs:49-60 | Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsVenomPodProj.cs:34-44 | Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsXenoOrbitalProj.cs:50-60 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPour.cs:147-157 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 11 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 11 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/SummonMinions/Projectiles/GsDeadlySphereSawProj.cs:42` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (10–11 lines × 10) · ×1
  • Duplicated block (10–11 lines × 10) Content/Industrials/ElectricPowers/Apiaries/ApiaryTile.cs:28 — Content/Industrials/ElectricPowers/Apiaries/ApiaryTile.cs:28-37 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherTile.cs:28-37 | Content/Industrials/ElectricPowers/GridSwitches/GridSwitchTile.cs:27-36 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerTile.cs:28-37 | Content/Industrials/ElectricPowers/Launchers/PlayerLauncherTile.cs:28-38 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTile.cs:28-37 | Content/Industrials/ElectricPowers/Sensors/SensorTile.cs:29-38 | Content/Industrials/Generator/SolarPanels/SolarPanel.cs:208-218 | Content/Industrials/Generator/SolarPanels/SolarPanelMK2.cs:68-78 | Content/Scenarios/Draedon/Quest/DeploySignaltowers/CQETConstructor.cs:72-81 — before extracting anything, compare `Content/Industrials/Generator/SolarPanels/SolarPanel.cs` and `Content/Industrials/Generator/SolarPanels/SolarPanelMK2.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 45 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.
D4 · Code Duplication · Duplicated block (11 lines × 10) · ×1
  • Duplicated block (11 lines × 10) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:59 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:59-71 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistRuneCircle.cs:63-73 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsBloodSpike.cs:48-58 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:283-293 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterPool.cs:53-63 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaBloodSurgeWave.cs:55-65 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaMiniBloodSlime.cs:52-62 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonVesselWhip.cs:60-70 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraVine.cs:58-68 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaCavitationOrb.cs:48-58 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterPool.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:59` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterCorrosiveSpit.cs:280` calls `Clamp` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaBloodSurgeWave.cs:53` 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.
D4 · Code Duplication · Duplicated block (8–11 lines × 6) · ×1
  • Duplicated block (8–11 lines × 6) Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs:251 — Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs:251-261 | Content/HackTimes/HackRamRenderer.cs:191-201 | Content/HackTimes/ScanInfoRenderer.cs:305-312 | Content/LegendWeapon/SHPCLegend/UI/DomainWheel/SHPCDomainWheelUI.cs:237-247 | Content/LegendWeapon/SHPCLegend/UI/SHPCRenderer.cs:155-163 | Content/LegendWeapon/SHPCLegend/UI/SHPCRenderer.cs:602-610 — before extracting anything, compare `Content/Cyberwares/Skills/CyberwareSkillRadialUI.cs` and `Content/LegendWeapon/SHPCLegend/UI/DomainWheel/SHPCDomainWheelUI.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (10–11 lines × 6) · ×1
  • Duplicated block (10–11 lines × 6) Content/GameModes/GodSmith/Weapons/Broadswords/BroadswordSchemes.Wood.cs:44 — Content/GameModes/GodSmith/Weapons/Broadswords/BroadswordSchemes.Wood.cs:44-53 | Content/GameModes/GodSmith/Weapons/Broadswords/BroadswordSchemes.Wood.cs:441-450 | Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordScheme.cs:32-42 | Content/GameModes/GodSmith/Weapons/Broadswords/GsDD2SquireDemonSword.cs:46-55 | Content/GameModes/GodSmith/Weapons/Broadswords/GsZombieArm.cs:31-40 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsOdditiesComboScheme.cs:31-41 — before extracting anything, compare `Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordScheme.cs` and `Content/GameModes/GodSmith/Weapons/MeleeOddities/GsOdditiesComboScheme.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Weapons/Broadswords/BroadswordSchemes.Wood.cs:44` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/GodSmith/Weapons/Broadswords/GsDD2SquireDemonSword.cs:40` calls `GsModifyWeaponDamage` and `Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordScheme.cs:30` 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.
D4 · Code Duplication · Duplicated block (10–11 lines × 5) · ×1
  • Duplicated block (10–11 lines × 5) Content/GameModes/BrutalMobs/Legion/Projectiles/LegionScoutOmen.cs:58 — Content/GameModes/BrutalMobs/Legion/Projectiles/LegionScoutOmen.cs:58-68 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionSurfOmen.cs:65-74 | Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomSporeMistTelegraph.cs:99-109 | Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomVineWhipOmen.cs:75-85 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandConeTelegraph.cs:116-126 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Legion/Projectiles/LegionScoutOmen.cs:58` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomVineWhipOmen.cs:71` calls `PlaySound` and `Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandConeTelegraph.cs:112` 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.
D4 · Code Duplication · Duplicated block (6–11 lines × 5) · ×1
  • Duplicated block (6–11 lines × 5) Content/Narrative/Presentation/Skins/Brimstone/BrimstoneChoiceSkin.cs:91 — Content/Narrative/Presentation/Skins/Brimstone/BrimstoneChoiceSkin.cs:91-101 | Content/Narrative/Presentation/Skins/Draedon/DraedonChoiceSkin.cs:45-50 | Content/Narrative/Presentation/Skins/Sea/SeaChoiceSkin.cs:42-47 | Content/Narrative/Presentation/Skins/Sulfsea/SulfseaChoiceSkin.cs:48-53 | Content/Narrative/Presentation/Skins/Tzeentch/TzeentchChoiceSkin.cs:48-53 — before extracting anything, compare `Content/Narrative/Presentation/Skins/Brimstone/BrimstoneChoiceSkin.cs` and `Content/Narrative/Presentation/Skins/Sulfsea/SulfseaChoiceSkin.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Narrative/Presentation/Skins/Brimstone/BrimstoneChoiceSkin.cs:91` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (4–11 lines × 7) · ×1
  • Duplicated block (4–11 lines × 7) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:423 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:423-433 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs:496-499 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs:463-473 | Content/Industrials/ElectricPowers/Launchers/PlayerLauncherUI.cs:350-353 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:350-360 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconUI.cs:393-396 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:428-438 — before extracting anything, compare `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs` and `Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 188 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:423` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (6–11 lines × 3) · ×1
  • Duplicated block (6–11 lines × 3) Content/Narrative/Presentation/Skins/Brimstone/BrimstoneDialogueSkin.cs:76 — Content/Narrative/Presentation/Skins/Brimstone/BrimstoneDialogueSkin.cs:76-81 | Content/Narrative/Presentation/Skins/SHPC/SHPCDialogueSkin.cs:133-143 | Content/Narrative/Presentation/Skins/Sea/SeaDialogueSkin.cs:74-79 — before extracting anything, compare `Content/Narrative/Presentation/Skins/Brimstone/BrimstoneDialogueSkin.cs` and `Content/Narrative/Presentation/Skins/Sea/SeaDialogueSkin.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Narrative/Presentation/Skins/Brimstone/BrimstoneDialogueSkin.cs:76` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (3–11 lines × 3) · ×1
  • Duplicated block (3–11 lines × 3) Content/Items/Magic/WheezingWyrms/WheezingWyrmHeld.cs:210 — Content/Items/Magic/WheezingWyrms/WheezingWyrmHeld.cs:210-220 | Content/Items/Magic/WheezingWyrms/WheezingWyrmHeld.cs:296-306 | Content/Items/Ranged/SneezingWyrms/SneezingWyrmHeld.cs:127-129 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/WheezingWyrms/WheezingWyrmHeld.cs:210` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (6–11 lines × 2) · ×1
  • Duplicated block (6–11 lines × 2) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:474 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:474-479 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:748-758 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:474` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (5–11 lines × 3) · ×1
  • Duplicated block (5–11 lines × 3) Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsPhaseTransitionState.cs:264 — Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsPhaseTransitionState.cs:264-268 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismFireVortexState.cs:69-77 | Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismShadowDashState.cs:167-177 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Common/TwinsPhaseTransitionState.cs:264` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (9–10 lines × 34) · ×1
  • Duplicated block (9–10 lines × 34) Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzCrystalProj.cs:265 — Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzCrystalProj.cs:265-274 | Content/Items/Accessories/BrutalRelics/WallOfFlesh/GluttonousTongueProj.cs:564-572 | Content/Items/Melee/DestroyersBlade.cs:527-535 | Content/Items/Melee/DragonsScaleGreatsword.cs:550-558 | Content/Items/Melee/DragonsScaleGreatsword.cs:676-684 | Content/Items/Melee/DragonsScaleGreatsword.cs:886-894 | Content/Items/Melee/EnergySword.cs:566-574 | Content/Items/Melee/HeartcarverHeart.cs:250-258 | Content/Items/Melee/OniMacheteHands.cs:1106-1114 | Content/Items/Melee/OniMacheteHands.cs:1349-1357 | Content/Items/Melee/RebelBlade.cs:597-605 | Content/Items/Melee/StormGoddessSpears/StormGoddessSpearHeld.cs:537-545 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:532-540 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:1038-1046 | Content/Items/Ranged/UniversalFrost.cs:395-403 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDemonicHell.cs:280-288 | Content/LegendWeapon/HalibutLegend/FishSkills/FishEaterofPlankton.cs:405-413 | Content/LegendWeapon/HalibutLegend/FishSkills/FishFallenStarVFX.cs:213-221 | Content/LegendWeapon/HalibutLegend/FishSkills/FishRock.cs:764-772 | Content/LegendWeapon/HalibutLegend/FishSkills/FishVariegatedLard.cs:696-704 | Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamHound.cs:1060-1068 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1030-1038 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaMinionDrownFX.cs:468-476 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaPlayerDrownFX.cs:504-512 | Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaScourgeFX.cs:765-773 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1407-1415 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1208-1216 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonRay.cs:328-336 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonVesselWhip.cs:316-324 | Content/NPCs/BrutalNPCs/BrutalPlantera/Rendering/PlanteraVineRenderer.cs:139-147 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenCrystalPrisonProj.cs:167-175 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Rendering/QueenPrismNodeRenderer.cs:61-69 | Content/NPCs/BrutalNPCs/BrutalWallOfFlesh/Projectiles/WofRotBeamProj.cs:162-171 | Content/Wraiths/Projectiles/GhostHandProj.cs:947-955 — there are 34 copies across 30 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 34 sites; resolving a subset leaves the remainder to drift apart. 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `effect` to `Effect` in one and `out SpriteEffects` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Accessories/BrutalRelics/WallOfFlesh/GluttonousTongueProj.cs:572` calls `SetValue` and `Content/Items/Accessories/BrutalRelics/QueenSlime/RefractionWaltzCrystalProj.cs:274` 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.
D4 · Code Duplication · Duplicated block (9–10 lines × 27) · ×1
  • Duplicated block (9–10 lines × 27) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1156 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1156-1164 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:916-924 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1175-1183 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:973-981 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1509-1517 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1097-1105 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1238-1246 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:983-991 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:809-817 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:1052-1060 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:978-986 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:877-885 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:937-945 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:910-918 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1378-1386 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:929-937 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1268-1276 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:1108-1116 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1316-1324 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:956-965 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:929-937 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1444-1452 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1365-1373 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:1401-1409 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1533-1541 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1557-1565 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:966-974 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1156` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:967` calls `SetValue`, `CurrentDissolve` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:1411` 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.
D4 · Code Duplication · Duplicated block (10 lines × 21) · ×1
  • Duplicated block (10 lines × 21) Content/Items/Accessories/BrutalRelics/Deerclops/WhiteoutVeilRender.cs:59 — Content/Items/Accessories/BrutalRelics/Deerclops/WhiteoutVeilRender.cs:59-68 | Content/Items/Accessories/BrutalRelics/EyeOfCthulhu/BloodfogIrisRender.cs:48-57 | Content/Items/Melee/HeartcarverCore.cs:264-273 | Content/Items/Melee/OniMacheteHands.cs:1609-1618 | Content/Items/Melee/SpearOfLonginuses/LonginusAssets.cs:107-116 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonImpactFX.cs:207-216 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleFX.cs:217-226 | Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Core/BrainScreenRender.cs:44-53 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Rendering/DeerclopsVeilRender.cs:58-67 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Rendering/FishronGrabVeil.cs:86-95 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Rendering/EmpressScreenRender.cs:93-102 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Rendering/EocFogRender.cs:65-74 | Content/NPCs/BrutalNPCs/BrutalGolem/Rendering/GolemScreenEffectRender.cs:51-60 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistVeilRender.cs:46-55 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordBlackFlashRender.cs:95-104 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordScreenRender.cs:80-89 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Rendering/SkeletronScreenRender.cs:69-78 | Content/Renders/PrimeScreenEffectRender.cs:53-62 | Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:2997-3006 | Content/Scenarios/Dungeonworld/NPCs/Elites/LampeaterWispRendering.cs:204-213 | Content/Scenarios/Dungeonworld/NPCs/OverseerVfx.cs:248-257 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 21 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 21 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Accessories/BrutalRelics/EyeOfCthulhu/BloodfogIrisRender.cs:60` calls `SetRenderTarget` and `Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:3007` 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.
D4 · Code Duplication · Duplicated block (11–12 lines × 19) · ×1
  • Duplicated block (11–12 lines × 19) Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:336 — Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs:336-346 | Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:391-401 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs:368-378 | Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:334-344 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerUI.cs:352-362 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:360-370 | Content/Industrials/ElectricPowers/Launchers/PlayerLauncherUI.cs:279-289 | Content/Industrials/ElectricPowers/MiningMachines/MiningMachineUI.cs:373-384 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerUI.cs:275-285 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconUI.cs:299-309 | Content/Industrials/ElectricPowers/Recyclers/RecyclerUI.cs:333-343 | Content/Industrials/ElectricPowers/Sensors/SensorUI.cs:275-285 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterUI.cs:344-354 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatUI.cs:309-319 | Content/Industrials/ElectricPowers/TeleportStations/TeleportStationUI.cs:378-388 | Content/Industrials/ElectricPowers/Turrets/TurretControlUI.cs:260-270 | Content/Industrials/Generator/Biomass/BiomassGeneratorUI.cs:237-247 | Content/Industrials/Generator/GeneratorReadout.cs:268-279 | Content/Industrials/Generator/Thermal/ThermalGeneratorUI.cs:350-361 — before extracting anything, compare `Content/Industrials/ElectricPowers/Apiaries/ApiaryUI.cs` and `Content/Industrials/ElectricPowers/AutoFishers/AutoFisherUI.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 188 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Industrials/Generator/Thermal/ThermalGeneratorUI.cs:346` calls `Clamp` and `Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:356` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (10 lines × 16) · ×1
  • Duplicated block (10 lines × 16) Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:460 — Content/GameModes/GodSmith/Weapons/Broadswords/GsBroadswordHeldBase.cs:460-469 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsDayBreak.cs:201-210 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT1.cs:319-328 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT2.cs:250-259 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsMonkStaffT3.cs:198-207 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsOdditiesFlurryHeldBase.cs:181-190 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsScourgeoftheCorruptor.cs:183-192 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsSolarEruption.cs:231-240 | Content/GameModes/GodSmith/Weapons/MeleeOddities/GsVampireKnives.cs:267-276 | Content/GameModes/GodSmith/Weapons/Shortswords/GsThrustHeldBase.cs:534-543 | Content/GameModes/GodSmith/Weapons/Spears/GsJoustingLances.cs:247-256 | Content/Items/Melee/Shatterfangs/ShatterfangHeld.cs:353-362 | Content/Items/Modifys/RBloodButcherer.cs:387-396 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1155-1164 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:974-983 | Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs:1161-1170 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 16 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 16 times.
D4 · Code Duplication · Duplicated block (9–10 lines × 13) · ×1
  • Duplicated block (9–10 lines × 13) Content/Items/Accessories/ArcaneThroneOfEternity.cs:185 — Content/Items/Accessories/ArcaneThroneOfEternity.cs:185-194 | Content/Items/Accessories/ArcaneThroneOfEternity.cs:332-340 | Content/Items/Accessories/ArcaneThroneOfEternity.cs:463-471 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDetonationProj.cs:212-221 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberShockwaveProj.cs:99-108 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberFreezeWaveProj.cs:93-102 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberPixelDecomposeProj.cs:92-101 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberReformProj.cs:98-107 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/HeavyBarrelModule.cs:324-332 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/HypersonicBarrelModule.cs:217-225 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/ScattershotBarrelModule.cs:390-398 | Content/LegendWeapon/SHPCLegend/Modules/Power/PlasmaInjectorModule.cs:174-182 | Content/LegendWeapon/SHPCLegend/Modules/Stock/ExtenderStockModule.cs:442-450 — before extracting anything, compare `Content/Items/Accessories/ArcaneThroneOfEternity.cs` and `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDetonationProj.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 112 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/ArcaneThroneOfEternity.cs:185` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberShockwaveProj.cs:110` calls `ShouldUpdatePosition` and `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDetonationProj.cs:222` 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.
D4 · Code Duplication · Duplicated block (10 lines × 13) · ×1
  • Duplicated block (10 lines × 13) Content/Items/Ranged/Pallbearer.cs:1246 — Content/Items/Ranged/Pallbearer.cs:1246-1255 | Content/LegendWeapon/HalibutLegend/FishSkills/FishAmanita.cs:670-679 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBloodyManowar.cs:441-450 | Content/LegendWeapon/HalibutLegend/FishSkills/FishFrostMinnowVFX.cs:342-351 | Content/LegendWeapon/HalibutLegend/FishSkills/FishHoney.cs:259-268 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBellWave.cs:198-207 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBellWave.cs:276-285 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiMirrorStand.cs:225-234 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiSandGarden.cs:207-216 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiSenjuArm.cs:211-220 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronBoneSpike.cs:137-146 | Content/Scenarios/Dungeonworld/NPCs/Elites/BoneStitcherRendering.cs:73-82 | Content/Wraiths/VFX/ScapeArmRenderer.cs:131-140 — there are 13 copies across 12 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 13 sites; resolving a subset leaves the remainder to drift apart. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/HalibutLegend/FishSkills/FishFrostMinnowVFX.cs:354` calls `SetValue`, `Clamp` and `Content/Items/Ranged/Pallbearer.cs:1258` 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.
D4 · Code Duplication · Duplicated block (9–10 lines × 8) · ×1
  • Duplicated block (9–10 lines × 8) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:471 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:471-480 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:393-401 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:416-425 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:410-419 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:524-532 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:531-539 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:394-402 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:461-470 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 8 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 8 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:471` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:524` calls `BloodBurst` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:471` does not — after which the two agree again for 5 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.
D4 · Code Duplication · Duplicated block (9–10 lines × 6) · ×1
  • Duplicated block (9–10 lines × 6) Content/Cyberwares/Implementation/Sandevistans/SandevistanRender.cs:71 — Content/Cyberwares/Implementation/Sandevistans/SandevistanRender.cs:71-80 | Content/GameModes/BrutalMobs/Ambience/Ashreign/AshreignHeatHazeRender.cs:77-86 | Content/HackTimes/HackTimeRender.cs:101-110 | Content/Industrials/Generator/Thermal/ThermalHeatHazeRender.cs:148-157 | Content/Scenarios/Dungeonworld/Gen/BossRooms/ProofingHallScene.cs:341-349 | Content/Scenarios/OldNet/Renders/OldNetGradeRender.cs:80-88 — before extracting anything, compare `Content/Cyberwares/Implementation/Sandevistans/SandevistanRender.cs` and `Content/HackTimes/HackTimeRender.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Cyberwares/Implementation/Sandevistans/SandevistanRender.cs:71` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/BrutalMobs/Ambience/Ashreign/AshreignHeatHazeRender.cs:76` calls `SetValue` and `Content/Scenarios/OldNet/Renders/OldNetGradeRender.cs:80` 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.
D4 · Code Duplication · Duplicated block (7–10 lines × 4) · ×1
  • Duplicated block (7–10 lines × 4) Content/GameModes/BrutalMobs/Ambience/Tidecall/Projectiles/TidecallRogueWaveProj.cs:367 — Content/GameModes/BrutalMobs/Ambience/Tidecall/Projectiles/TidecallRogueWaveProj.cs:367-373 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpLeapVortex.cs:142-151 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpMiniVortex.cs:141-150 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpVortexWall.cs:143-152 — before extracting anything, compare `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpLeapVortex.cs` and `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpMiniVortex.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 99 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpLeapVortex.cs:142` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (8–10 lines × 4) · ×1
  • Duplicated block (8–10 lines × 4) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1179 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1179-1187 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1532-1541 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:1002-1009 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:960-968 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs` as WHOLE FILES: this scan already matched 68 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1179` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7–10 lines × 3) · ×1
  • Duplicated block (7–10 lines × 3) Content/Items/Magic/Pandemoniums/PandemoniumLightning.cs:173 — Content/Items/Magic/Pandemoniums/PandemoniumLightning.cs:173-180 | Content/Items/Magic/Pandemoniums/PandemoniumRainDrop.cs:104-113 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/States/Arms/PrimeViceStates.cs:198-204 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/Pandemoniums/PandemoniumLightning.cs:173` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (7–10 lines × 2) · ×1
  • Duplicated block (7–10 lines × 2) Content/Cyberwares/UIs/CyberInventoryPanel.cs:344 — Content/Cyberwares/UIs/CyberInventoryPanel.cs:344-353 | Content/NPCs/Victors/UIs/VictorClinicPanel.cs:417-423 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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.
D4 · Code Duplication · Duplicated block (2–10 lines × 3) · ×1
  • Duplicated block (2–10 lines × 3) Content/HackTimes/PvP/Protocols/MapBlackoutRenderer.cs:111 — Content/HackTimes/PvP/Protocols/MapBlackoutRenderer.cs:111-120 | Content/HackTimes/PvP/UI/PlayerHackHud.cs:747-756 | Content/HackTimes/ScanInfoRenderer.cs:367-368 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/HackTimes/PvP/Protocols/MapBlackoutRenderer.cs:111` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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.
D4 · Code Duplication · Duplicated block (4–10 lines × 4) · ×1
  • Duplicated block (4–10 lines × 4) Content/LegendWeapon/OnikiriLegend/UI/OniMeiRenderer.cs:151 — Content/LegendWeapon/OnikiriLegend/UI/OniMeiRenderer.cs:151-159 | Content/LegendWeapon/OnikiriLegend/UI/OniMeiRenderer.cs:415-418 | Content/LegendWeapon/OnikiriLegend/UI/OniMeiRenderer.cs:474-483 | Content/LegendWeapon/OnikiriLegend/UI/OniMeiRenderer.cs:798-801 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/UI/OniMeiRenderer.cs:151` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/OnikiriLegend/UI/OniMeiRenderer.cs:149` calls `Vector2`, `Draw` and `Content/LegendWeapon/OnikiriLegend/UI/OniMeiRenderer.cs:415` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (6–10 lines × 2) · ×1
  • Duplicated block (6–10 lines × 2) Content/PRTTypes/PRT_ToxicMist.cs:28 — Content/PRTTypes/PRT_ToxicMist.cs:28-37 | Content/PRTTypes/PRT_ToxicMist.cs:40-45 — 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.
D4 · Code Duplication · Duplicated block (6 lines × 64) · ×1
  • Duplicated block (6 lines × 64) Content/Industrials/ElectricPowers/Apiaries/Apiary.cs:33 — Content/Industrials/ElectricPowers/Apiaries/Apiary.cs:33-38 | Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafter.cs:19-24 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisher.cs:35-40 | Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachine.cs:18-23 | Content/Industrials/ElectricPowers/Collectors/Collector.cs:33-38 | Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs:30-35 | Content/Industrials/ElectricPowers/Crushers/Crusher.cs:19-24 | Content/Industrials/ElectricPowers/ElectricMinRocket.cs:39-44 | Content/Industrials/ElectricPowers/FluidInjectors/FluidInjector.cs:18-23 | Content/Industrials/ElectricPowers/FluidPumps/FluidPump.cs:18-23 | Content/Industrials/ElectricPowers/GridSwitches/GridSwitch.cs:31-36 | Content/Industrials/ElectricPowers/HealingStations/HealStation.cs:33-38 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmer.cs:31-36 | Content/Industrials/ElectricPowers/Incinerators/Incinerator.cs:18-23 | Content/Industrials/ElectricPowers/Launchers/PlayerLauncher.cs:29-34 | Content/Industrials/ElectricPowers/LifeWeavers/LifeWeaver.cs:26-31 | Content/Industrials/ElectricPowers/LifeWeavers/WGGLifeWeaver.cs:35-40 | Content/Industrials/ElectricPowers/Lumberjacks/Lumberjack.cs:30-35 | Content/Industrials/ElectricPowers/Lumberjacks/WGGLumberjack.cs:30-35 | Content/Industrials/ElectricPowers/MiningMachines/MiningMachine.cs:31-36 | Content/Industrials/ElectricPowers/MiningMachines/MiningMachineMk2.cs:31-36 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmer.cs:31-36 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeacon.cs:29-34 | Content/Industrials/ElectricPowers/Recyclers/Recycler.cs:18-23 | Content/Industrials/ElectricPowers/Sensors/Sensor.cs:72-77 | Content/Industrials/ElectricPowers/ShieldGenerators/ShieldGenerator.cs:33-38 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuter.cs:18-23 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVat.cs:35-40 | Content/Industrials/ElectricPowers/Spectrometers/Spectrometer.cs:28-33 | Content/Industrials/ElectricPowers/Sundials/ElectricSundial.cs:33-38 | Content/Industrials/ElectricPowers/Suppressors/PacifierTower.cs:33-38 | Content/Industrials/ElectricPowers/TeleportStations/TeleportStation.cs:33-38 | Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:35-40 | Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:81-86 | Content/Industrials/ElectricPowers/Throwers/Thrower.cs:37-42 | Content/Industrials/ElectricPowers/Turrets/CryoTurrets/CryoTurret.cs:33-38 | Content/Industrials/ElectricPowers/Turrets/FlameTurrets/FlameTurret.cs:37-42 | Content/Industrials/ElectricPowers/Turrets/LaserTurrets/LaserTurret.cs:33-38 | Content/Industrials/ElectricPowers/WeatherControllers/WeatherController.cs:33-38 | Content/Industrials/ElectricPowers/WireInterfaces/WireInterface.cs:37-42 | Content/Industrials/Generator/Biomass/BiomassGenerator.cs:39-44 | Content/Industrials/Generator/Hydroelectrics/Hydroelectric.cs:29-34 | Content/Industrials/Generator/Hydroelectrics/HydroelectricMK2.cs:28-33 | Content/Industrials/Generator/MagmaThermal/MagmaThermalGenerator.cs:33-38 | Content/Industrials/Generator/SolarPanels/SolarPanel.cs:167-172 | Content/Industrials/Generator/SolarPanels/SolarPanelMK2.cs:27-32 | Content/Industrials/Generator/Thermal/ThermalGenerator.cs:25-30 | Content/Industrials/Generator/Thermal/ThermalGeneratorMK2.cs:24-29 | Content/Industrials/Generator/WindGriven/WGGMK2Wilderness.cs:23-28 | Content/Industrials/Generator/WindGriven/WGGWilderness.cs:23-28 | Content/Industrials/Generator/WindGriven/WindGrivenGenerator.cs:35-40 | Content/Industrials/Generator/WindGriven/WindGrivenGeneratorMk2.cs:35-40 | Content/Industrials/MaterialFlow/Batterys/CapacitorMatrix.cs:33-38 | Content/Industrials/MaterialFlow/Batterys/ThermalBattery.cs:22-27 | Content/Industrials/MaterialFlow/Fluids/FluidTank.cs:26-31 | Content/Industrials/MaterialFlow/Fluids/LargeFluidTank.cs:21-26 | Content/Industrials/MaterialFlow/LaserEnergyTrans.cs:30-35 | Content/Industrials/MaterialFlow/Pipelines/BasePipelineItem.cs:18-23 | Content/Items/Painting/CalSelfPortrait.cs:16-21 | Content/Items/Painting/WUTIVSelfPortrait.cs:16-21 | Content/Items/Tools/SirenMusicalBox.cs:40-45 | Content/Scenarios/OldDuke/MermanRod.cs:25-30 | Content/Scenarios/OldDuke/OceanRaiderses/OceanRaiders.cs:31-36 | Content/Scenarios/OldDuke/OldDuchests/OldDuchest.cs:30-35 — before extracting anything, compare `Content/Industrials/ElectricPowers/Collectors/Collector.cs` and `Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 49 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.
D4 · Code Duplication · Duplicated block (7–9 lines × 27) · ×1
  • Duplicated block (7–9 lines × 27) Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineTile.cs:24 — Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineTile.cs:24-31 | Content/Industrials/ElectricPowers/ElectricMinRocket.cs:248-256 | Content/Industrials/ElectricPowers/FluidInjectors/FluidInjectorTile.cs:22-29 | Content/Industrials/ElectricPowers/FluidPumps/FluidPumpTile.cs:22-29 | Content/Industrials/ElectricPowers/HealingStations/HealStationTile.cs:33-41 | Content/Industrials/ElectricPowers/MiningMachines/MiningMachine.cs:67-75 | Content/Industrials/ElectricPowers/MiningMachines/MiningMachineMk2.cs:67-75 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconTile.cs:30-38 | Content/Industrials/ElectricPowers/Recyclers/RecyclerTile.cs:27-35 | Content/Industrials/ElectricPowers/ShieldGenerators/ShieldGeneratorTile.cs:33-41 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterTile.cs:24-31 | Content/Industrials/ElectricPowers/Suppressors/PacifierTowerTile.cs:33-41 | Content/Industrials/ElectricPowers/TeleportStations/TeleportStationTile.cs:30-36 | Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:133-141 | Content/Industrials/ElectricPowers/Turrets/CryoTurrets/CryoTurretTile.cs:33-41 | Content/Industrials/ElectricPowers/Turrets/FlameTurrets/FlameTurretTile.cs:33-41 | Content/Industrials/ElectricPowers/Turrets/LaserTurrets/LaserTurretTile.cs:33-41 | Content/Industrials/ElectricPowers/WeatherControllers/WeatherControllerTile.cs:37-43 | Content/Industrials/Generator/Biomass/BiomassGenerator.cs:81-88 | Content/Industrials/Generator/MagmaThermal/MagmaThermalGenerator.cs:73-80 | Content/Industrials/Generator/Thermal/ThermalGenerator.cs:65-72 | Content/Industrials/MaterialFlow/Batterys/CapacitorMatrix.cs:72-78 | Content/Industrials/MaterialFlow/Batterys/ThermalBattery.cs:62-68 | Content/Industrials/MaterialFlow/Fluids/FluidTank.cs:61-67 | Content/Industrials/MaterialFlow/Fluids/LargeFluidTank.cs:56-62 | Content/Items/Placeable/HoChaMeditatorItem.cs:49-55 | Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersTile.cs:28-36 — before extracting anything, compare `Content/Industrials/ElectricPowers/ElectricMinRocket.cs` and `Content/Industrials/ElectricPowers/MiningMachines/MiningMachine.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (7 lines × 22) · ×1
  • Duplicated block (7 lines × 22) Content/Items/Accessories/BrutalRelics/Deerclops/WhiteoutVeilRender.cs:58 — Content/Items/Accessories/BrutalRelics/Deerclops/WhiteoutVeilRender.cs:58-64 | Content/Items/Accessories/BrutalRelics/EyeOfCthulhu/BloodfogIrisRender.cs:47-53 | Content/Items/Melee/HeartcarverCore.cs:263-269 | Content/Items/Melee/OniMacheteHands.cs:1608-1614 | Content/Items/Melee/SpearOfLonginuses/LonginusAssets.cs:106-112 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonImpactFX.cs:206-212 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleFX.cs:216-222 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleShatter.cs:272-278 | Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Core/BrainScreenRender.cs:43-49 | Content/NPCs/BrutalNPCs/BrutalDeerclops/Rendering/DeerclopsVeilRender.cs:57-63 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Rendering/FishronGrabVeil.cs:85-91 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Rendering/EmpressScreenRender.cs:92-98 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Rendering/EocFogRender.cs:64-70 | Content/NPCs/BrutalNPCs/BrutalGolem/Rendering/GolemScreenEffectRender.cs:50-56 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Rendering/CultistVeilRender.cs:45-51 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordBlackFlashRender.cs:94-100 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Rendering/MLordScreenRender.cs:79-85 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Rendering/SkeletronScreenRender.cs:68-74 | Content/Renders/PrimeScreenEffectRender.cs:52-58 | Content/Scenarios/Dungeonworld/NPCs/DeepGaolWraith.cs:2996-3002 | Content/Scenarios/Dungeonworld/NPCs/Elites/LampeaterWispRendering.cs:203-209 | Content/Scenarios/Dungeonworld/NPCs/OverseerVfx.cs:247-253 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 22 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 22 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleShatter.cs:280` calls `SetValue` and `Content/Items/Accessories/BrutalRelics/Deerclops/WhiteoutVeilRender.cs:66` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (8–9 lines × 20) · ×1
  • Duplicated block (8–9 lines × 20) Content/Items/Accessories/ArcaneThroneOfEternity.cs:453 — Content/Items/Accessories/ArcaneThroneOfEternity.cs:453-460 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDetonationProj.cs:202-209 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberShockwaveProj.cs:88-95 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberFreezeWaveProj.cs:81-88 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Restart/CyberRestartProj.cs:208-216 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberPixelDecomposeProj.cs:82-89 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberReformProj.cs:88-95 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/HeavyBarrelModule.cs:314-321 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/HypersonicBarrelModule.cs:207-214 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/RapidBarrelModule.cs:655-662 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/ScattershotBarrelModule.cs:380-387 | Content/LegendWeapon/SHPCLegend/Modules/Frame/ResonanceFrameModule.cs:692-700 | Content/LegendWeapon/SHPCLegend/Modules/Optic/HoloOpticModule.cs:192-199 | Content/LegendWeapon/SHPCLegend/Modules/Optic/PrecisionOpticModule.cs:235-242 | Content/LegendWeapon/SHPCLegend/Modules/Optic/SniperOpticModule.cs:401-408 | Content/LegendWeapon/SHPCLegend/Modules/Optic/SniperOpticModule.cs:614-621 | Content/LegendWeapon/SHPCLegend/Modules/Power/PlasmaInjectorModule.cs:164-171 | Content/LegendWeapon/SHPCLegend/Modules/Stock/BraceStockModule.cs:486-493 | Content/LegendWeapon/SHPCLegend/Modules/Stock/ExtenderStockModule.cs:432-439 | Content/LegendWeapon/SHPCLegend/Modules/Stock/SteadyStockModule.cs:562-570 — before extracting anything, compare `Content/Items/Accessories/ArcaneThroneOfEternity.cs` and `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDetonationProj.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 112 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/SHPCLegend/Modules/Optic/HoloOpticModule.cs:187` calls `SetValue`, `ToVector3` and `Content/LegendWeapon/SHPCLegend/Modules/Barrel/RapidBarrelModule.cs:651` 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.
D4 · Code Duplication · Duplicated block (8–9 lines × 19) · ×1
  • Duplicated block (8–9 lines × 19) Content/Items/Accessories/ArcaneThroneOfEternity.cs:177 — Content/Items/Accessories/ArcaneThroneOfEternity.cs:177-185 | Content/Items/Accessories/ArcaneThroneOfEternity.cs:324-332 | Content/Items/Accessories/ArcaneThroneOfEternity.cs:455-463 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDetonationProj.cs:204-211 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Restart/CyberRestartProj.cs:211-218 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberPixelDecomposeProj.cs:84-91 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberReformProj.cs:90-97 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/HeavyBarrelModule.cs:316-323 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/HypersonicBarrelModule.cs:209-216 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/RapidBarrelModule.cs:657-664 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/ScattershotBarrelModule.cs:382-389 | Content/LegendWeapon/SHPCLegend/Modules/Frame/ResonanceFrameModule.cs:694-701 | Content/LegendWeapon/SHPCLegend/Modules/Optic/HoloOpticModule.cs:194-202 | Content/LegendWeapon/SHPCLegend/Modules/Optic/PrecisionOpticModule.cs:237-244 | Content/LegendWeapon/SHPCLegend/Modules/Optic/SniperOpticModule.cs:403-410 | Content/LegendWeapon/SHPCLegend/Modules/Optic/SniperOpticModule.cs:616-623 | Content/LegendWeapon/SHPCLegend/Modules/Power/PlasmaInjectorModule.cs:166-173 | Content/LegendWeapon/SHPCLegend/Modules/Stock/BraceStockModule.cs:488-495 | Content/LegendWeapon/SHPCLegend/Modules/Stock/ExtenderStockModule.cs:434-441 — before extracting anything, compare `Content/Items/Accessories/ArcaneThroneOfEternity.cs` and `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDetonationProj.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 112 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/ArcaneThroneOfEternity.cs:177` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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.
D4 · Code Duplication · Duplicated block (8–9 lines × 14) · ×1
  • Duplicated block (8–9 lines × 14) Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainDeco.cs:500 — Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainDeco.cs:500-508 | Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallMeltFX.cs:397-405 | Content/Scenarios/Kiame/KasaOnis/KasaOniActor.cs:890-898 | Content/Scenarios/Kiame/KiameAmbience.cs:228-236 | Content/Scenarios/Kiame/Overlay/OniRainWorldState.cs:320-328 | Content/Scenarios/Kiyume/Ambience/KiyumeCrowFlight.cs:375-382 | Content/Scenarios/Kiyume/Ambience/KiyumeTraces.cs:254-261 | Content/Scenarios/Kiyume/Fog/KiyumeGroundFogRender.cs:236-243 | Content/Scenarios/Kiyume/Fog/KiyumeHoundShade.cs:222-229 | Content/Scenarios/Kiyume/NPCs/FuneralCortegeYokai.cs:1100-1107 | Content/Scenarios/Kiyume/NPCs/KiyumeWhiteHound.cs:368-376 | Content/Scenarios/Kiyume/NPCs/LanternGuideYokai.cs:360-367 | Content/Scenarios/Kiyume/NPCs/ScarecrowWatcherYokai.cs:502-509 | Content/Wraiths/Abilities/GhostRains/GhostRainFx.cs:283-291 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 14 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 14 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainDeco.cs:500` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (7–9 lines × 12) · ×1
  • Duplicated block (7–9 lines × 12) Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs:204 — Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs:204-211 | Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTsunamiProj.cs:283-290 | Content/Items/Magic/Everdeeps/EverdeepMaelstrom.cs:329-335 | Content/Items/Magic/Everdeeps/EverdeepRing.cs:356-363 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronSharkTornadoProj.cs:320-328 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronTsunamiWallProj.cs:172-180 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpGeyserSpout.cs:185-191 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpJetBeam.cs:202-208 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpLeapVortex.cs:137-143 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpMiniVortex.cs:136-142 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpVortexWall.cs:138-144 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpWaveCrest.cs:175-181 — before extracting anything, compare `Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs` and `Content/Items/Magic/Everdeeps/EverdeepMaelstrom.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTornadoProj.cs:212` calls `Apply` and `Content/Items/Accessories/BrutalRelics/DukeFishron/TidalFinTsunamiProj.cs:292` 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.
D4 · Code Duplication · Duplicated block (8–9 lines × 11) · ×1
  • Duplicated block (8–9 lines × 11) Content/Industrials/ElectricPowers/Apiaries/ApiaryTile.cs:26 — Content/Industrials/ElectricPowers/Apiaries/ApiaryTile.cs:26-34 | Content/Industrials/ElectricPowers/AutoFishers/AutoFisherTile.cs:26-34 | Content/Industrials/ElectricPowers/GridSwitches/GridSwitchTile.cs:25-33 | Content/Industrials/ElectricPowers/HerbFarmers/HerbFarmerTile.cs:26-34 | Content/Industrials/ElectricPowers/Launchers/PlayerLauncherTile.cs:26-34 | Content/Industrials/ElectricPowers/MushroomFarmers/MushroomFarmerTile.cs:26-34 | Content/Industrials/ElectricPowers/Sensors/SensorTile.cs:27-35 | Content/Industrials/Generator/SolarPanels/SolarPanel.cs:206-214 | Content/Industrials/Generator/SolarPanels/SolarPanelMK2.cs:66-74 | Content/Scenarios/Draedon/Quest/DeploySignaltowers/CQETConstructor.cs:70-78 | Content/Scenarios/Draedon/Quest/DeploySignaltowers/DeploySignaltower.cs:49-56 — before extracting anything, compare `Content/Industrials/Generator/SolarPanels/SolarPanel.cs` and `Content/Industrials/Generator/SolarPanels/SolarPanelMK2.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 45 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Launchers/PlayerLauncherTile.cs:26` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (7–9 lines × 11) · ×1
  • Duplicated block (7–9 lines × 11) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:426 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:426-433 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:396-402 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:443-450 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:427-434 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:413-420 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:352-358 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:388-394 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:429-436 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:342-350 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:412-420 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:439-446 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs` as WHOLE FILES: this scan already matched 55 separate duplicated blocks between them, totalling at least 611 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:426` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:442` calls `RippleAt`, `Vector2` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:425` does not — after which the two agree again for 4 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.
D4 · Code Duplication · Duplicated block (6–9 lines × 10) · ×1
  • Duplicated block (6–9 lines × 10) Content/Items/Accessories/ArcaneThroneOfEternity.cs:332 — Content/Items/Accessories/ArcaneThroneOfEternity.cs:332-337 | Content/Items/Accessories/ArcaneThroneOfEternity.cs:463-468 | Content/LegendWeapon/HalibutLegend/DomainSkills/SeaDomain.cs:680-688 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutDomain.cs:321-328 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDetonationProj.cs:211-218 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberShockwaveProj.cs:98-105 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberFreezeWaveProj.cs:92-99 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberPixelDecomposeProj.cs:91-98 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberReformProj.cs:97-104 | Content/LegendWeapon/SHPCLegend/Modules/Power/PlasmaInjectorModule.cs:173-180 — there are 10 copies across 9 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 10 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/ArcaneThroneOfEternity.cs:332` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberShockwaveProj.cs:110` calls `ShouldUpdatePosition` and `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDetonationProj.cs:222` 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.
D4 · Code Duplication · Duplicated block (8–9 lines × 9) · ×1
  • Duplicated block (8–9 lines × 9) Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMoonFlare.cs:275 — Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMoonFlare.cs:275-283 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteStarSurge.cs:189-197 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistCoronaLance.cs:130-137 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistGazeBeam.cs:278-285 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistGazeBeam.cs:340-347 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistPlanetProj.cs:851-859 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistUmbraShade.cs:508-515 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistZodiacRing.cs:179-186 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordOrbProj.cs:296-304 — there are 9 copies across 8 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 9 sites; resolving a subset leaves the remainder to drift apart. 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.
D4 · Code Duplication · Duplicated block (8–9 lines × 8) · ×1
  • Duplicated block (8–9 lines × 8) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:467 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:467-475 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:438-446 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:430-438 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:545-553 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:551-558 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:478-485 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:415-423 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:483-491 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 8 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 8 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:467` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (8–9 lines × 6) · ×1
  • Duplicated block (8–9 lines × 6) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:971 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:971-978 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:1142-1149 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1358-1365 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:969-976 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:1017-1025 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:1079-1086 — there are 6 copies across 5 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 6 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:971` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8–9 lines × 5) · ×1
  • Duplicated block (8–9 lines × 5) Content/GameModes/GodSmith/Accessories/Offense/GodSmithEmblems.cs:258 — Content/GameModes/GodSmith/Accessories/Offense/GodSmithEmblems.cs:258-266 | Content/GameModes/GodSmith/Accessories/Offense/GodSmithManaFlowerChain.cs:233-241 | Content/GameModes/GodSmith/Accessories/Offense/GodSmithQuiverChain.cs:119-127 | Content/GameModes/GodSmith/Armors/Endgame/GsHuntressArmor.cs:164-171 | Content/GameModes/GodSmith/Weapons/SummonSentries/Projectiles/GsSentryChainLightningProj.cs:43-51 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Accessories/Offense/GodSmithEmblems.cs:258` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7–9 lines × 5) · ×1
  • Duplicated block (7–9 lines × 5) Content/Items/Ranged/Starships/StarshipComet.cs:70 — Content/Items/Ranged/Starships/StarshipComet.cs:70-78 | Content/Items/Ranged/Starships/StarshipMeteor.cs:132-140 | Content/Items/Ranged/Starships/StarshipMicroStar.cs:46-53 | Content/Items/Ranged/Starships/StarshipPlanet.cs:145-151 | Content/Items/Ranged/Starships/StarshipPlasmaBolt.cs:62-70 — 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 5 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Ranged/Starships/StarshipComet.cs:70` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Ranged/Starships/StarshipComet.cs:70` calls `Sin` and `Content/Items/Ranged/Starships/StarshipMicroStar.cs:46` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (3–9 lines × 7) · ×1
  • Duplicated block (3–9 lines × 7) Content/HackTimes/Protocols/MachineShortCircuit.cs:74 — Content/HackTimes/Protocols/MachineShortCircuit.cs:74-82 | Content/HackTimes/Protocols/SynapseBurn.cs:64-66 | Content/HackTimes/Protocols/TileDetonate.cs:145-148 | Content/HackTimes/Protocols/TurretCircuitOverload.cs:36-44 | Content/HackTimes/Protocols/TurretMesh.cs:256-260 | Content/HackTimes/Protocols/TurretShortCircuit.cs:36-44 | Content/HackTimes/Protocols/VirusBroadcast.cs:41-49 — 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 7 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Content/HackTimes/Protocols/MachineShortCircuit.cs:74` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/HackTimes/Protocols/TurretCircuitOverload.cs:44` calls `NextFloat`, `ToRotationVector2`, `Color` and `Content/HackTimes/Protocols/SynapseBurn.cs:66` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (5–9 lines × 4) · ×1
  • Duplicated block (5–9 lines × 4) Content/Items/Melee/OniMachete.cs:631 — Content/Items/Melee/OniMachete.cs:631-635 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs:1396-1402 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs:1110-1116 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleRing.cs:176-184 — before extracting anything, compare `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs` and `Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSweepSlash.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 896 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Melee/OniMachete.cs:631` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (6–9 lines × 3) · ×1
  • Duplicated block (6–9 lines × 3) Content/Items/Magic/AriaofTheCosmoses/AccretionDisk.cs:481 — Content/Items/Magic/AriaofTheCosmoses/AccretionDisk.cs:481-487 | Content/Items/Magic/NeutronWands/NeutronPulsar.cs:495-500 | Content/LegendWeapon/OnikiriLegend/OniDomains/OniDomainRender.cs:461-469 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/AriaofTheCosmoses/AccretionDisk.cs:481` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (2–9 lines × 4) · ×1
  • Duplicated block (2–9 lines × 4) Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:395 — Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:395-396 | Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:402-411 | Content/Industrials/Modifys/ChargingStationUI.cs:249-250 | Content/Industrials/Modifys/ChargingStationUI.cs:256-264 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:402` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (5 lines × 43) · ×1
  • Duplicated block (5 lines × 43) Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:548 — Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:548-552 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1019-1023 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:822-826 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1061-1065 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:838-842 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1361-1365 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:953-957 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1059-1063 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:866-870 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:675-679 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:927-931 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:878-882 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:784-788 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:810-814 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:816-820 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1135-1139 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:867-871 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1118-1122 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:874-878 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:953-957 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:919-923 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1235-1239 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:740-744 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:684-688 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:860-864 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1012-1016 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1070-1074 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1189-1193 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaMiniBloodSlime.cs:195-199 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1006-1010 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1248-1252 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1202-1206 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeBloodBee.cs:122-126 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:992-996 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenGelMine.cs:263-267 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:970-974 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:1015-1019 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1241-1245 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsFlameBreath.cs:193-197 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1311-1315 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshLeech.cs:128-132 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:740-744 | Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallProj.cs:872-876 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 43 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 43 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:548` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaMiniBloodSlime.cs:192` calls `FindTarget` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1016` 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.
D4 · Code Duplication · Duplicated block (8 lines × 29) · ×1
  • Duplicated block (8 lines × 29) Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineTile.cs:15 — Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineTile.cs:15-22 | Content/Industrials/ElectricPowers/FluidInjectors/FluidInjectorTile.cs:13-20 | Content/Industrials/ElectricPowers/FluidPumps/FluidPumpTile.cs:13-20 | Content/Industrials/ElectricPowers/HealingStations/HealStationTile.cs:23-31 | Content/Industrials/ElectricPowers/PotionBeacons/PotionBeaconTile.cs:20-28 | Content/Industrials/ElectricPowers/ShieldGenerators/ShieldGeneratorTile.cs:23-31 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterTile.cs:15-22 | Content/Industrials/ElectricPowers/Suppressors/PacifierTowerTile.cs:23-31 | Content/Industrials/ElectricPowers/TeleportStations/TeleportStationTile.cs:20-28 | Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:123-131 | Content/Industrials/ElectricPowers/Turrets/CryoTurrets/CryoTurretTile.cs:23-31 | Content/Industrials/ElectricPowers/Turrets/FlameTurrets/FlameTurretTile.cs:23-31 | Content/Industrials/ElectricPowers/Turrets/LaserTurrets/LaserTurretTile.cs:23-31 | Content/Industrials/Generator/Biomass/BiomassGenerator.cs:72-79 | Content/Industrials/Generator/Hydroelectrics/Hydroelectric.cs:71-78 | Content/Industrials/Generator/Hydroelectrics/HydroelectricMK2.cs:61-68 | Content/Industrials/Generator/MagmaThermal/MagmaThermalGenerator.cs:64-71 | Content/Industrials/Generator/SolarPanels/SolarPanel.cs:199-206 | Content/Industrials/Generator/SolarPanels/SolarPanelMK2.cs:59-66 | Content/Industrials/Generator/Thermal/ThermalGenerator.cs:56-63 | Content/Industrials/Generator/Thermal/ThermalGeneratorMK2.cs:55-62 | Content/Industrials/Generator/WindGriven/WGGMK2Wilderness.cs:44-51 | Content/Industrials/Generator/WindGriven/WGGWilderness.cs:44-51 | Content/Industrials/Generator/WindGriven/WindGrivenGenerator.cs:80-87 | Content/Industrials/Generator/WindGriven/WindGrivenGeneratorMk2.cs:81-88 | Content/Industrials/MaterialFlow/Batterys/CapacitorMatrix.cs:62-70 | Content/Industrials/MaterialFlow/Batterys/ThermalBattery.cs:52-60 | Content/Industrials/MaterialFlow/Fluids/FluidTank.cs:51-59 | Content/Industrials/MaterialFlow/Fluids/LargeFluidTank.cs:46-54 — before extracting anything, compare `Content/Industrials/ElectricPowers/HealingStations/HealStationTile.cs` and `Content/Industrials/ElectricPowers/ShieldGenerators/ShieldGeneratorTile.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineTile.cs:15` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Industrials/ElectricPowers/HealingStations/HealStationTile.cs:20` calls `VaultLoaden` and `Content/Industrials/ElectricPowers/BottlingMachines/BottlingMachineTile.cs:14` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (7–8 lines × 29) · ×1
  • Duplicated block (7–8 lines × 29) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1159 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1159-1165 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:919-925 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1178-1184 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:976-982 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1512-1518 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1100-1106 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1241-1247 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:986-992 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:812-818 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:1055-1061 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:981-987 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:880-886 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:940-946 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:913-919 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1381-1387 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:932-938 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1271-1277 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:1111-1117 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1319-1325 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:959-966 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:932-938 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1447-1453 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1368-1374 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:1404-1410 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:1109-1115 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:1164-1170 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1536-1542 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1560-1566 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:969-975 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1159` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:1107` calls `Lerp` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1157` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (8 lines × 19) · ×1
  • Duplicated block (8 lines × 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1201 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1201-1210 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:959-966 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1222-1229 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:1017-1024 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1555-1564 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1139-1148 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1281-1290 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:1024-1031 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:851-858 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:1093-1100 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:1023-1030 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:920-927 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:982-991 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:953-960 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1421-1430 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1286-1295 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1300-1309 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1495-1502 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1588-1597 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1201` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (8 lines × 14) · ×1
  • Duplicated block (8 lines × 14) Content/Items/Ranged/Pallbearer.cs:1248 — Content/Items/Ranged/Pallbearer.cs:1248-1255 | Content/LegendWeapon/HalibutLegend/FishSkills/FishAmanita.cs:672-679 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBloodyManowar.cs:443-450 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDrizzle.cs:99-106 | Content/LegendWeapon/HalibutLegend/FishSkills/FishFrostMinnowVFX.cs:344-351 | Content/LegendWeapon/HalibutLegend/FishSkills/FishHoney.cs:261-268 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBellWave.cs:200-207 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBellWave.cs:278-285 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiMirrorStand.cs:227-234 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiSandGarden.cs:209-216 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiSenjuArm.cs:213-220 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronBoneSpike.cs:139-146 | Content/Scenarios/Dungeonworld/NPCs/Elites/BoneStitcherRendering.cs:75-82 | Content/Wraiths/VFX/ScapeArmRenderer.cs:133-140 — there are 14 copies across 13 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 14 sites; resolving a subset leaves the remainder to drift apart. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/HalibutLegend/FishSkills/FishFrostMinnowVFX.cs:354` calls `SetValue`, `Clamp` and `Content/Items/Ranged/Pallbearer.cs:1258` 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.
D4 · Code Duplication · Duplicated block (7–8 lines × 12) · ×1
  • Duplicated block (7–8 lines × 12) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:491 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:491-498 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:468-475 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:390-396 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:346-353 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:339-346 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:413-420 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:407-414 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:528-534 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:456-462 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:391-397 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:409-416 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:458-465 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 12 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 12 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:491` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:476` calls `NextFloat` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:499` 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.
D4 · Code Duplication · Duplicated block (7 lines × 11) · ×1
  • Duplicated block (7 lines × 11) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunBullet.cs:122 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunBullet.cs:122-128 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistIceShard.cs:106-112 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsHail.cs:87-93 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressPetal.cs:113-119 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:100-106 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeLaserBolt.cs:74-80 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeStinger.cs:155-161 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenCrystalShard.cs:89-95 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronBloodSkull.cs:116-122 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsPulseShot.cs:100-106 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshLeech.cs:106-112 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 11 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 11 times.
D4 · Code Duplication · Duplicated block (8 lines × 11) · ×1
  • Duplicated block (8 lines × 11) Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryRoom.cs:474 — Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryRoom.cs:474-481 | Content/Scenarios/Dungeonworld/Gen/BossRooms/GaolBossRoom.cs:323-330 | Content/Scenarios/Dungeonworld/Gen/Infill/InfillRooms.cs:295-302 | Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2Palette.cs:102-109 | Content/Scenarios/Dungeonworld/Gen/Layers/L3/L3Palette.cs:79-86 | Content/Scenarios/Dungeonworld/Gen/Layers/L4/L4Palette.cs:92-99 | Content/Scenarios/Dungeonworld/Gen/Layers/L5/L5Palette.cs:187-194 | Content/Scenarios/Dungeonworld/Gen/Layers/L6/L6Palette.cs:150-157 | Content/Scenarios/Dungeonworld/Gen/Layers/L7/L7Style.cs:143-150 | Content/Scenarios/Kiame/Gen/KiameTileBrush.cs:115-122 | Content/Scenarios/Kiyume/Gen/KiyumeTileBrush.cs:149-156 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 11 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 11 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Scenarios/Dungeonworld/Gen/Layers/L2/L2Palette.cs:112` calls `TryPlaceTile`, `PlaceTile` and `Content/Scenarios/Dungeonworld/Gen/Infill/InfillRooms.cs:303` 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.
D4 · Code Duplication · Duplicated block (7–8 lines × 10) · ×1
  • Duplicated block (7–8 lines × 10) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1319 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1319-1326 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:983-990 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1338-1345 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:1041-1048 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1702-1709 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:1047-1054 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:944-951 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:1070-1077 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:977-984 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1677-1683 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1319` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (5–8 lines × 9) · ×1
  • Duplicated block (5–8 lines × 9) Content/Items/Accessories/Proverbs.cs:259 — Content/Items/Accessories/Proverbs.cs:259-266 | Content/Items/Magic/Pandemoniums/PandemoniumBlastWave.cs:94-101 | Content/Items/Magic/Pandemoniums/PandemoniumChannel.cs:840-847 | Content/Items/Magic/Pandemoniums/PandemoniumCircle.cs:337-344 | Content/Items/Magic/Pandemoniums/PandemoniumRSkill.cs:471-478 | Content/Items/Ranged/BarrenBow.cs:480-486 | Content/Items/Ranged/NeutronBows/NeutronBow.cs:465-471 | Content/Items/Tools/EncyclopediaofOceanicKnowledge.cs:477-481 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumCircle.cs:358-364 — before extracting anything, compare `Content/Items/Accessories/Proverbs.cs` and `Content/Items/Magic/Pandemoniums/PandemoniumBlastWave.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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.
D4 · Code Duplication · Duplicated block (8 lines × 9) · ×1
  • Duplicated block (8 lines × 9) Content/Items/Magic/Elysiums/Serpents/HolySerpent.cs:387 — Content/Items/Magic/Elysiums/Serpents/HolySerpent.cs:387-394 | Content/Items/Melee/DestroyersBlade.cs:523-531 | Content/Items/Melee/DragonsScaleGreatsword.cs:546-554 | Content/Items/Melee/EnergySword.cs:562-570 | Content/Items/Melee/RebelBlade.cs:593-601 | Content/Items/Melee/StormGoddessSpears/StormGoddessSpearHeld.cs:533-541 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:528-536 | Content/Items/Stones/Marbles/MarbleClub.cs:595-603 | Content/Items/Stones/Marbles/MarbleHuntingKnife.cs:412-420 — before extracting anything, compare `Content/Items/Melee/DestroyersBlade.cs` and `Content/Items/Melee/DragonsScaleGreatsword.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 419 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Magic/Elysiums/Serpents/HolySerpent.cs:387` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7–8 lines × 8) · ×1
  • Duplicated block (7–8 lines × 8) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:480 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:480-487 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:401-407 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:425-431 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:532-538 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:539-545 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:466-472 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:402-408 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:470-476 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 8 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 8 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:480` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (7–8 lines × 5) · ×1
  • Duplicated block (7–8 lines × 5) Content/LegendWeapon/HalibutLegend/FishSkills/FishMud.cs:628 — Content/LegendWeapon/HalibutLegend/FishSkills/FishMud.cs:628-634 | Content/LegendWeapon/HalibutLegend/FishSkills/FishPeng.cs:393-399 | Content/LegendWeapon/HalibutLegend/FishSkills/FishSlime.cs:455-461 | Content/LegendWeapon/HalibutLegend/FishSkills/FishSlime.cs:728-735 | Content/LegendWeapon/HalibutLegend/FishSkills/FishVariegatedLard.cs:394-400 — there are 5 copies across 4 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishMud.cs:628` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/HalibutLegend/FishSkills/FishMud.cs:625` calls `FindTarget`, `GetDomainLayer` and `Content/LegendWeapon/HalibutLegend/FishSkills/FishSlime.cs:451` 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.
D4 · Code Duplication · Duplicated block (4–8 lines × 6) · ×1
  • Duplicated block (4–8 lines × 6) Content/PRTTypes/PRT_HeavenfallStar.cs:36 — Content/PRTTypes/PRT_HeavenfallStar.cs:36-43 | Content/PRTTypes/PRT_Line.cs:45-48 | Content/PRTTypes/PRT_Line_FormPlayer.cs:37-42 | Content/PRTTypes/PRT_LonginusStar.cs:57-64 | Content/PRTTypes/PRT_Spark.cs:47-53 | Content/PRTTypes/PRT_SparkAlpha.cs:43-50 — before extracting anything, compare `Content/PRTTypes/PRT_Spark.cs` and `Content/PRTTypes/PRT_SparkAlpha.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/PRTTypes/PRT_HeavenfallStar.cs:36` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/PRTTypes/PRT_Line.cs:44` calls `Vector2` and `Content/PRTTypes/PRT_HeavenfallStar.cs:36` does not — after which the two agree again for 4 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.
D4 · Code Duplication · Duplicated block (6–8 lines × 4) · ×1
  • Duplicated block (6–8 lines × 4) Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingPanel.cs:410 — Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingPanel.cs:410-415 | Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingPanel.cs:514-520 | Content/LegendWeapon/SHPCLegend/UI/SHPCModPanel.cs:448-453 | Content/LegendWeapon/SHPCLegend/UI/SHPCModuleSelectPanel.cs:316-323 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/SHPCLegend/MoldProcessingTables/UI/MoldProcessingPanel.cs:410` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (3–8 lines × 3) · ×1
  • Duplicated block (3–8 lines × 3) Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkEmberProj.cs:136 — Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkEmberProj.cs:136-138 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkMortarMarkerProj.cs:96-103 | Content/GameModes/BrutalMobs/Temple/Projectiles/TempleEmberProj.cs:90-97 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkEmberProj.cs:136` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (2–8 lines × 5) · ×1
  • Duplicated block (2–8 lines × 5) Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:552 — Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:552-559 | Content/Industrials/ElectricPowers/Throwers/ThrowerUI.cs:560-561 | Content/Industrials/Modifys/ChargingStationUI.cs:397-403 | Content/Industrials/Modifys/ChargingStationUI.cs:404-405 | Content/Narrative/Presentation/Skins/Sea/SeaPanelState.cs:155-156 — 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. 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.
D4 · Code Duplication · Duplicated block (5–8 lines × 3) · ×1
  • Duplicated block (5–8 lines × 3) Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadCommandCore.cs:394 — Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadCommandCore.cs:394-398 | Content/Items/Accessories/GodslayerScabbard.cs:167-174 | Content/Items/Accessories/GodslayerScabbard.cs:194-201 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadCommandCore.cs:394` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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.
D4 · Code Duplication · Duplicated block (7 lines × 62) · ×1
  • Duplicated block (7 lines × 62) Content/GameModes/BrutalMobs/Ambience/Ashreign/Projectiles/AshreignMagmaBeadProj.cs:159 — Content/GameModes/BrutalMobs/Ambience/Ashreign/Projectiles/AshreignMagmaBeadProj.cs:159-165 | Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdBoltProj.cs:164-172 | Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclEyezorOrbProj.cs:99-107 | Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclNailheadNailProj.cs:89-97 | Content/GameModes/BrutalMobs/EliteMove/Projectiles/EMScatterBoltProj.cs:87-95 | Content/GameModes/BrutalMobs/EvilBiome/Projectiles/ErosionCloudSeed.cs:85-93 | Content/GameModes/BrutalMobs/EvilBiome/Projectiles/MummyWrapProj.cs:96-104 | Content/GameModes/BrutalMobs/EvilBiome/Projectiles/VileLanceProj.cs:93-101 | Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs:82-90 | Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgSnowShardProj.cs:84-92 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmIceShardProj.cs:69-77 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmNutShellProj.cs:102-110 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmOrnamentProj.cs:81-89 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmPineNeedleProj.cs:63-71 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmPresentShellProj.cs:77-85 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmSnowballProj.cs:114-122 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmStrafeBulletProj.cs:64-72 | Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyMaggotBolt.cs:116-124 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhImpFireBolt.cs:75-83 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhScytheBolt.cs:76-84 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhShellSpike.cs:67-75 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhStingerBolt.cs:76-84 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhTridentBolt.cs:75-83 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionInkGlob.cs:83-91 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionScoutBolt.cs:82-90 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionVolleyArrow.cs:86-94 | Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserBoltProj.cs:110-118 | Content/GameModes/BrutalMobs/Martians/Projectiles/MrtScutlixHeavyBolt.cs:95-103 | Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteMoltenGlob.cs:142-150 | Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomSporeBoltProj.cs:110-118 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtBroadsideBall.cs:92-100 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtFanShot.cs:78-86 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtRicochetShot.cs:272-278 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkEmberSeedProj.cs:93-101 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkMortarShellProj.cs:95-103 | Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilCursedBeadProj.cs:73-81 | Content/GameModes/BrutalMobs/Sky/Projectiles/SkyFeatherBolt.cs:69-77 | Content/GameModes/BrutalMobs/SlimeKin/Projectiles/SlimeGelBomb.cs:193-201 | Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornJavelinProj.cs:87-95 | Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornQuakeWave.cs:151-159 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesIceShardProj.cs:70-78 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandPelletProj.cs:77-85 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMirrorPhantom.cs:291-299 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteStarSurge.cs:277-285 | Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadArmProj.cs:568-576 | Content/Items/Accessories/BrutalRelics/Twins/TwinPupilShots.cs:82-90 | Content/Items/BloomArsenal.cs:118-125 | Content/Items/BloomArsenal.cs:195-202 | Content/Items/Magic/BloomTomes/BloomTome.cs:125-131 | Content/Items/Ranged/Thornstrings/ThornstringArrow.cs:98-104 | Content/LegendWeapon/HalibutLegend/FishSkills/FishotroningVFX.cs:172-180 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomNeedle.cs:95-103 | Content/NPCs/BloomsandSerpents/Projectiles/BssNeedleProj.cs:60-67 | Content/NPCs/BloomsandSerpents/Projectiles/BssPetalProj.cs:79-85 | Content/NPCs/BloomsandSerpents/Projectiles/BssSandGlob.cs:65-73 | Content/NPCs/BloomsandSerpents/Projectiles/BssWindPetalProj.cs:98-104 | Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Projectiles/BrainBloodShard.cs:119-127 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerBolt.cs:89-97 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Projectiles/EocBloodShot.cs:93-101 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Projectiles/BrutalBeeStinger.cs:80-88 | Content/NPCs/FestersandSerpents/Projectiles/FssMortarShard.cs:62-70 | Content/NPCs/FestersandSerpents/Projectiles/FssMortarShell.cs:123-131 — before extracting anything, compare `Content/GameModes/BrutalMobs/Ambience/Ashreign/Projectiles/AshreignMagmaBeadProj.cs` and `Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhShellSpike.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/Ashreign/Projectiles/AshreignMagmaBeadProj.cs:159` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclEyezorOrbProj.cs:99` calls `Sin` and `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclNailheadNailProj.cs:89` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (5 lines × 50) · ×1
  • Duplicated block (5 lines × 50) Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamHound.cs:674 — Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamHound.cs:674-678 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkDrop.cs:548-552 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:849-853 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:1344-1348 | Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:1476-1480 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1019-1023 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:822-826 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1061-1065 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:838-842 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1361-1365 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:953-957 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1059-1063 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumCircle.cs:243-247 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:866-870 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:675-679 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:927-931 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:878-882 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:784-788 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:810-814 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoProj.cs:163-167 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:816-820 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1135-1139 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:867-871 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1118-1122 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:874-878 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistThunderOrb.cs:177-181 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:953-957 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:919-923 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1235-1239 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:740-744 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:684-688 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:860-864 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1012-1016 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1070-1074 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1189-1193 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaMiniBloodSlime.cs:195-199 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1006-1010 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1248-1252 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1202-1206 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeBloodBee.cs:122-126 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:992-996 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenGelMine.cs:263-267 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:970-974 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:1015-1019 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1241-1245 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsFlameBreath.cs:193-197 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1311-1315 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshLeech.cs:128-132 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:740-744 | Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallProj.cs:872-876 — there are 50 copies across 48 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 50 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDreams/KikasaDreamHound.cs:674` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumCircle.cs:240` calls `FindNearest` and `Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs:846` 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.
D4 · Code Duplication · Duplicated block (7 lines × 47) · ×1
  • Duplicated block (7 lines × 47) Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdBoltProj.cs:167 — Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdBoltProj.cs:167-173 | Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclEyezorOrbProj.cs:102-108 | Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclManFlyFlaskProj.cs:165-171 | Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclNailheadNailProj.cs:92-98 | Content/GameModes/BrutalMobs/EliteMove/Projectiles/EMScatterBoltProj.cs:90-96 | Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs:85-91 | Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgSnowShardProj.cs:87-93 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmIceShardProj.cs:72-78 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmNutShellProj.cs:105-111 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmOrnamentProj.cs:84-90 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmPineNeedleProj.cs:66-72 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmPresentShellProj.cs:80-86 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmSnowballProj.cs:117-123 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmStrafeBulletProj.cs:67-73 | Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyMaggotBolt.cs:119-125 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionClownBomb.cs:208-214 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionInkGlob.cs:86-92 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionScoutBolt.cs:85-91 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionVolleyArrow.cs:89-95 | Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserBoltProj.cs:113-119 | Content/GameModes/BrutalMobs/Martians/Projectiles/MrtScutlixHeavyBolt.cs:98-104 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtBroadsideBall.cs:95-101 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtFanShot.cs:81-87 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtRicochetShot.cs:273-279 | Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornJavelinProj.cs:90-96 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesIceShardProj.cs:73-79 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandPelletProj.cs:80-86 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMirrorPhantom.cs:294-300 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteStarSurge.cs:280-286 | Content/Items/Accessories/BrutalRelics/Twins/TwinPupilShots.cs:85-91 | Content/Items/BloomArsenal.cs:120-126 | Content/Items/BloomArsenal.cs:197-203 | Content/Items/Magic/BloomTomes/BloomTome.cs:126-132 | Content/Items/Melee/DestroyersBladeEXs/DestroyerShadowBolt.cs:234-240 | Content/Items/Ranged/Thornstrings/ThornstringArrow.cs:99-105 | Content/Items/Summon/BloomCallers/BloomCallerSprout.cs:381-387 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomNeedle.cs:98-104 | Content/NPCs/BloomsandSerpents/Projectiles/BssNeedleProj.cs:62-68 | Content/NPCs/BloomsandSerpents/Projectiles/BssPetalProj.cs:80-86 | Content/NPCs/BloomsandSerpents/Projectiles/BssWindPetalProj.cs:99-105 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerBolt.cs:92-98 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs:154-160 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Projectiles/EocBloodSpike.cs:72-78 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordBoltProj.cs:122-128 | Content/NPCs/FestersandSerpents/Projectiles/FssIchorGlob.cs:152-158 | Content/NPCs/FestersandSerpents/Projectiles/FssMortarShard.cs:65-71 | Content/NPCs/FestersandSerpents/Projectiles/FssMortarShell.cs:126-132 — there are 47 copies across 46 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 47 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdBoltProj.cs:167` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclEyezorOrbProj.cs:99` calls `Sin` and `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclNailheadNailProj.cs:89` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (7 lines × 33) · ×1
  • Duplicated block (7 lines × 33) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1155 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1155-1161 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:915-921 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1174-1180 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:972-978 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1508-1514 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1096-1102 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1237-1243 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:982-988 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:808-814 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:1051-1057 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:977-983 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:876-882 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:936-942 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:909-915 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1377-1383 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:928-934 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:266-272 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1267-1273 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:1048-1054 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:1107-1113 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1315-1321 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:955-961 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:928-934 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1279-1285 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1329-1335 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1419-1425 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1443-1449 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1364-1370 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1222-1228 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:1400-1406 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1532-1538 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1556-1562 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:965-971 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1339` calls `Clamp` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:274` 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.
D4 · Code Duplication · Duplicated block (7 lines × 21) · ×1
  • Duplicated block (7 lines × 21) Content/Items/Melee/OniMachete.cs:379 — Content/Items/Melee/OniMachete.cs:379-385 | Content/Items/Ranged/Pallbearer.cs:1249-1255 | Content/LegendWeapon/HalibutLegend/FishSkills/FishAmanita.cs:673-679 | Content/LegendWeapon/HalibutLegend/FishSkills/FishBloodyManowar.cs:444-450 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDrizzle.cs:100-106 | Content/LegendWeapon/HalibutLegend/FishSkills/FishFrostMinnowVFX.cs:345-351 | Content/LegendWeapon/HalibutLegend/FishSkills/FishHoney.cs:262-268 | Content/LegendWeapon/HalibutLegend/FishSkills/FishTunabeardVFX.cs:174-180 | Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonSlashRenderer.cs:323-329 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBellWave.cs:201-207 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiBellWave.cs:279-285 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiMirrorStand.cs:228-234 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiSandGarden.cs:210-216 | Content/LegendWeapon/OnikiriLegend/Inscriptions/OniMeiSenjuArm.cs:214-220 | Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilateRenderer.cs:33-39 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleRenderer.cs:228-234 | Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniKamuiFlowRenderer.cs:46-52 | Content/LegendWeapon/OnikiriLegend/OniSakuraFlights/OniSakuraFlowRenderer.cs:60-66 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronBoneSpike.cs:140-146 | Content/Scenarios/Dungeonworld/NPCs/Elites/BoneStitcherRendering.cs:76-82 | Content/Wraiths/VFX/ScapeArmRenderer.cs:134-140 — there are 21 copies across 20 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 21 sites; resolving a subset leaves the remainder to drift apart. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilateRenderer.cs:40` calls `SetValue` and `Content/Items/Melee/OniMachete.cs:386` does not — after which the two agree again for 4 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.
D4 · Code Duplication · Duplicated block (7 lines × 19) · ×1
  • Duplicated block (7 lines × 19) Content/Items/Accessories/ArcaneThroneOfEternity.cs:176 — Content/Items/Accessories/ArcaneThroneOfEternity.cs:176-182 | Content/Items/Accessories/ArcaneThroneOfEternity.cs:323-329 | Content/Items/Accessories/ArcaneThroneOfEternity.cs:454-460 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDetonationProj.cs:203-209 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberShockwaveProj.cs:89-95 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberFreezeWaveProj.cs:82-88 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberPixelDecomposeProj.cs:83-89 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberReformProj.cs:89-95 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/HeavyBarrelModule.cs:315-321 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/HypersonicBarrelModule.cs:208-214 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/RapidBarrelModule.cs:656-662 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/ScattershotBarrelModule.cs:381-387 | Content/LegendWeapon/SHPCLegend/Modules/Frame/ResonanceFrameModule.cs:693-700 | Content/LegendWeapon/SHPCLegend/Modules/Optic/HoloOpticModule.cs:193-199 | Content/LegendWeapon/SHPCLegend/Modules/Optic/PrecisionOpticModule.cs:236-242 | Content/LegendWeapon/SHPCLegend/Modules/Optic/SniperOpticModule.cs:402-408 | Content/LegendWeapon/SHPCLegend/Modules/Optic/SniperOpticModule.cs:615-621 | Content/LegendWeapon/SHPCLegend/Modules/Power/PlasmaInjectorModule.cs:165-171 | Content/LegendWeapon/SHPCLegend/Modules/Stock/ExtenderStockModule.cs:433-439 — before extracting anything, compare `Content/Items/Accessories/ArcaneThroneOfEternity.cs` and `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDetonationProj.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 112 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (7 lines × 17) · ×1
  • Duplicated block (7 lines × 17) Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawWormProj.cs:582 — Content/Items/Accessories/BrutalRelics/EaterOfWorlds/MawWormProj.cs:582-588 | Content/Items/Melee/DawnshatterAzures/DawnshatterDash.cs:471-477 | Content/LegendWeapon/OnikiriLegend/OniFlashSteps/OniFlashStep.cs:1132-1138 | Content/LegendWeapon/OnikiriLegend/OniSakuraFlights/OniSakuraFlight.cs:1257-1264 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Rendering/DestroyerMotionFX.cs:111-117 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs:127-133 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidPool.cs:102-108 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowBreachOmen.cs:83-89 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowGeyserProj.cs:158-164 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowGeyserProj.cs:190-196 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowLungeOmen.cs:177-183 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Projectiles/HoneyPuddleZone.cs:131-137 | Content/NPCs/FestersandSerpents/Projectiles/FssCascadeDrop.cs:86-92 | Content/NPCs/FestersandSerpents/Projectiles/FssGeyserColumn.cs:162-168 | Content/NPCs/FestersandSerpents/Projectiles/FssGeyserColumn.cs:194-200 | Content/NPCs/FestersandSerpents/Projectiles/FssIchorGlob.cs:125-131 | Content/NPCs/FestersandSerpents/Projectiles/FssIchorPool.cs:222-228 — there are 17 copies across 15 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 17 sites; resolving a subset leaves the remainder to drift apart. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowGeyserProj.cs:156` calls `SetValue` and `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs:125` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (7 lines × 15) · ×1
  • Duplicated block (7 lines × 15) Content/GameModes/GodSmith/Armors/GsArmorTerrainProbe.cs:35 — Content/GameModes/GodSmith/Armors/GsArmorTerrainProbe.cs:35-42 | Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainDeco.cs:501-508 | Content/LegendWeapon/KikasaLegend/KikasaThralls/KikasaThrallMeltFX.cs:398-405 | Content/Scenarios/Kiame/KasaOnis/KasaOniActor.cs:891-898 | Content/Scenarios/Kiame/KiameAmbience.cs:229-236 | Content/Scenarios/Kiame/Overlay/OniRainWorldState.cs:321-328 | Content/Scenarios/Kiyume/Ambience/KiyumeCrowFlight.cs:376-382 | Content/Scenarios/Kiyume/Ambience/KiyumeTraces.cs:255-261 | Content/Scenarios/Kiyume/Fog/KiyumeGroundFogRender.cs:237-243 | Content/Scenarios/Kiyume/Fog/KiyumeHoundShade.cs:223-229 | Content/Scenarios/Kiyume/NPCs/FuneralCortegeYokai.cs:1101-1107 | Content/Scenarios/Kiyume/NPCs/KiyumeWhiteHound.cs:369-376 | Content/Scenarios/Kiyume/NPCs/LanternGuideYokai.cs:361-367 | Content/Scenarios/Kiyume/NPCs/ScarecrowWatcherYokai.cs:503-509 | Content/Wraiths/Abilities/GhostRains/GhostRainFx.cs:284-291 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 15 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 15 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/GodSmith/Armors/GsArmorTerrainProbe.cs:35` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (5–7 lines × 14) · ×1
  • Duplicated block (5–7 lines × 14) Content/GameModes/BrutalMobs/Ambience/Frostveil/FrostveilPRT.cs:63 — Content/GameModes/BrutalMobs/Ambience/Frostveil/FrostveilPRT.cs:63-69 | Content/LegendWeapon/HalibutLegend/FishSkills/FishDoubleCodVFX.cs:144-149 | Content/LegendWeapon/HalibutLegend/FishSkills/FishIchornVFX.cs:184-189 | Content/LegendWeapon/HalibutLegend/FishSkills/FishSwarmVFX.cs:316-321 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:324-328 | Content/LegendWeapon/KikasaLegend/KikasaWisps/KikasaWispPRT.cs:58-62 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Rendering/BKSParticles.cs:64-69 | Content/PRTTypes/PRT_GhostRainYank.cs:68-73 | Content/PRTTypes/PRT_HeartcarverDroplet.cs:49-54 | Content/PRTTypes/PRT_KikasaInkBead.cs:61-65 | Content/PRTTypes/PRT_KikasaTwinsFlame.cs:72-76 | Content/Scenarios/Dungeonworld/NPCs/GaolFireBolt.cs:274-278 | Content/Scenarios/Dungeonworld/NPCs/OverseerSlagGlob.cs:252-256 | Content/Scenarios/Dungeonworld/NPCs/UndrownedTideWave.cs:244-248 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 14 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 14 times. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/HalibutLegend/FishSkills/FishIchornVFX.cs:192` calls `Lerp`, `Draw`, `Vector2` and `Content/LegendWeapon/HalibutLegend/FishSkills/FishDoubleCodVFX.cs:152` 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.
D4 · Code Duplication · Duplicated block (6–7 lines × 14) · ×1
  • Duplicated block (6–7 lines × 14) Content/Industrials/ElectricPowers/Collectors/Collector.cs:110 — Content/Industrials/ElectricPowers/Collectors/Collector.cs:110-115 | Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs:107-112 | Content/Industrials/ElectricPowers/Incinerators/IncineratorTile.cs:98-104 | Content/Industrials/ElectricPowers/LifeWeavers/LifeWeaverTile.cs:59-65 | Content/Industrials/ElectricPowers/LifeWeavers/WGGLifeWeaver.cs:111-117 | Content/Industrials/ElectricPowers/Lumberjacks/LumberjackTile.cs:58-64 | Content/Industrials/ElectricPowers/Lumberjacks/WGGLumberjack.cs:106-112 | Content/Industrials/ElectricPowers/Spectrometers/Spectrometer.cs:103-108 | Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:182-188 | Content/Industrials/Generator/Thermal/ThermalGenerator.cs:97-103 | Content/Industrials/Generator/Thermal/ThermalGeneratorMK2.cs:97-103 | Content/Items/Placeable/HoChaMeditatorItem.cs:75-81 | Content/Items/Placeable/StarflowPlatedBlock.cs:75-80 | Content/Scenarios/Draedon/Quest/DeploySignaltowers/CQETConstructor.cs:110-115 — before extracting anything, compare `Content/Industrials/ElectricPowers/Collectors/Collector.cs` and `Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 49 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Collectors/Collector.cs:110` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/Industrials/ElectricPowers/Collectors/Collector.cs:116` calls `Draw`, `Rectangle` and `Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs:113` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (7 lines × 13) · ×1
  • Duplicated block (7 lines × 13) Content/Scenarios/Helen/FirstMet.cs:18 — Content/Scenarios/Helen/FirstMet.cs:18-24 | Content/Scenarios/Helen/ResurrectionWarn.cs:16-22 | Content/Scenarios/Himayo/FirstMetHimayo.cs:17-23 | Content/Scenarios/SupCal/End/EternalBlazingNow/EternalBlazingNow.cs:20-26 | Content/Scenarios/SupCal/End/EternalBlazingNow/EternalBlazingNowNoHelen.cs:14-20 | Content/Scenarios/SupCal/FirstMetSupCal.cs:23-29 | Content/Scenarios/SupCal/Quest/DoGQuest/SupCalDoGQuestReward.cs:18-24 | Content/Scenarios/SupCal/Quest/PallbearerQuest/SupCalMoonLordReward.cs:15-21 | Content/Scenarios/SupCal/Quest/PallbearerQuest/SupCalQuestReward.cs:18-24 | Content/Scenarios/SupCal/Quest/YharonQuest/SupCalYharonQuestReward.cs:18-24 | Content/Scenarios/SupCal/SupCalDefeat.cs:13-19 | Content/Scenarios/SupCal/SupCalPlayerDefeat.cs:14-20 | Content/Scenarios/SupCal/SupCalVictory.cs:15-21 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 13 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 13 times.
D4 · Code Duplication · Duplicated block (6–7 lines × 7) · ×1
  • Duplicated block (6–7 lines × 7) Content/Industrials/ElectricPowers/HealingStations/HealStationTile.cs:98 — Content/Industrials/ElectricPowers/HealingStations/HealStationTile.cs:98-104 | Content/Industrials/ElectricPowers/ShieldGenerators/ShieldGeneratorTile.cs:98-104 | Content/Industrials/ElectricPowers/Suppressors/PacifierTowerTile.cs:98-104 | Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:179-184 | Content/Industrials/ElectricPowers/Turrets/CryoTurrets/CryoTurretTile.cs:98-104 | Content/Industrials/ElectricPowers/Turrets/FlameTurrets/FlameTurretTile.cs:98-104 | Content/Industrials/ElectricPowers/Turrets/LaserTurrets/LaserTurretTile.cs:98-104 — before extracting anything, compare `Content/Industrials/ElectricPowers/HealingStations/HealStationTile.cs` and `Content/Industrials/ElectricPowers/ShieldGenerators/ShieldGeneratorTile.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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.
D4 · Code Duplication · Duplicated block (6–7 lines × 6) · ×1
  • Duplicated block (6–7 lines × 6) Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFistProj.cs:392 — Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFistProj.cs:392-398 | Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFistProj.cs:551-557 | Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemSunCore.cs:303-309 | Content/NPCs/BrutalNPCs/BrutalGolem/Projectiles/GolemTelegraph.cs:114-119 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Rendering/SkeletronRenderHelper.cs:508-514 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/HeadPrimeAI.cs:813-819 — there are 6 copies across 5 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 6 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFistProj.cs:392` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (6–7 lines × 5) · ×1
  • Duplicated block (6–7 lines × 5) Content/LegendWeapon/HalibutLegend/FishSkills/FishHungerVFX.cs:94 — Content/LegendWeapon/HalibutLegend/FishSkills/FishHungerVFX.cs:94-99 | Content/LegendWeapon/HalibutLegend/FishSkills/FishIchornVFX.cs:115-120 | Content/LegendWeapon/HalibutLegend/FishSkills/FishTropicalBarracudaVFX.cs:113-118 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:165-171 | Content/LegendWeapon/OnikiriLegend/OniZanshinSlashs/OniZanshinSlash.cs:344-349 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/HalibutLegend/FishSkills/FishHungerVFX.cs:94` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (5–7 lines × 5) · ×1
  • Duplicated block (5–7 lines × 5) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:461 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:461-467 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:459-465 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:417-421 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:424-430 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:456-462 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs` as WHOLE FILES: this scan already matched 75 separate duplicated blocks between them, totalling at least 912 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:461` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (4–7 lines × 6) · ×1
  • Duplicated block (4–7 lines × 6) Content/Items/Melee/HeartcarverHeart.cs:242 — Content/Items/Melee/HeartcarverHeart.cs:242-246 | Content/Items/Melee/OniMacheteHands.cs:1487-1493 | Content/Items/Melee/WeaverGrievanceses/WeaverGrievances.cs:772-775 | Content/Items/Ranged/UniversalFrost.cs:387-391 | Content/LegendWeapon/HalibutLegend/FishSkills/FishMud.cs:767-774 | Content/LegendWeapon/HalibutLegend/FishSkills/FishRock.cs:754-760 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times.
D4 · Code Duplication · Duplicated block (3–7 lines × 5) · ×1
  • Duplicated block (3–7 lines × 5) Content/LegendWeapon/OnikiriLegend/OniDismembers/OniDismember.cs:834 — Content/LegendWeapon/OnikiriLegend/OniDismembers/OniDismember.cs:834-836 | Content/LegendWeapon/OnikiriLegend/OniDismembers/OniPlayerDismember.cs:274-276 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleCut.cs:287-293 | Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleScar.cs:223-229 | Content/LegendWeapon/OnikiriLegend/OniOmokages/OniOmokage.cs:538-540 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleCut.cs:287` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/OnikiriLegend/OniDismembers/OniDismember.cs:836` calls `NextFloat`, `Configure`, `Next` and `Content/LegendWeapon/OnikiriLegend/OniFinaleSlashs/OniFinaleScar.cs:229` 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.
D4 · Code Duplication · Duplicated block (4–7 lines × 5) · ×1
  • Duplicated block (4–7 lines × 5) Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:150 — Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:150-156 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowApexFrenzyState.cs:229-232 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowBurrowAmbushState.cs:135-141 | Content/NPCs/BrutalNPCs/BrutalKingSlime/States/KingSlimePursuitBurrowState.cs:93-97 | Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraIntroState.cs:198-201 — before extracting anything, compare `Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs` and `Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/States/EowBurrowAmbushState.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 70 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:150` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/NPCs/BrutalNPCs/BrutalDestroyer/States/DestroyerBurrowAmbushState.cs:157` calls `CameraPunch` and `Content/NPCs/BrutalNPCs/BrutalPlantera/States/PlanteraIntroState.cs:201` 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.
D4 · Code Duplication · Duplicated block (2–7 lines × 5) · ×1
  • Duplicated block (2–7 lines × 5) Content/Items/Accessories/BrutalRelics/KingSlime/KingsVerdictWave.cs:155 — Content/Items/Accessories/BrutalRelics/KingSlime/KingsVerdictWave.cs:155-156 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSRoyalPillarProj.cs:137-138 | Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSRoyalPillarProj.cs:139-145 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenCrystalSpireProj.cs:138-139 | Content/NPCs/BrutalNPCs/BrutalQueenSlime/Projectiles/QueenCrystalSpireProj.cs:140-146 — 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. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/BrutalNPCs/BrutalKingSlime/Projectiles/BKSRoyalPillarProj.cs:139` calls `VertexPositionColorTexture`, `Vector3`, `Vector2` and `Content/Items/Accessories/BrutalRelics/KingSlime/KingsVerdictWave.cs:155` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (3–7 lines × 3) · ×1
  • Duplicated block (3–7 lines × 3) Content/LegendWeapon/HalibutLegend/FishSkills/FishVoodooRitual.cs:266 — Content/LegendWeapon/HalibutLegend/FishSkills/FishVoodooRitual.cs:266-268 | Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronBoneSpike.cs:72-78 | Content/NPCs/BrutalNPCs/BrutalSkeletron/States/SkeletronPhaseTransitionState.cs:65-71 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/NPCs/BrutalNPCs/BrutalSkeletron/Projectiles/SkeletronBoneSpike.cs:72` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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.
D4 · Code Duplication · Duplicated block (6 lines × 70) · ×1
  • Duplicated block (6 lines × 70) Content/GameModes/BrutalMobs/Ambience/Ashreign/Projectiles/AshreignMagmaBeadProj.cs:160 — Content/GameModes/BrutalMobs/Ambience/Ashreign/Projectiles/AshreignMagmaBeadProj.cs:160-165 | Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdBoltProj.cs:167-172 | Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclEyezorOrbProj.cs:102-107 | Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclManFlyFlaskProj.cs:165-170 | Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclNailheadNailProj.cs:92-97 | Content/GameModes/BrutalMobs/EliteMove/Projectiles/EMScatterBoltProj.cs:90-95 | Content/GameModes/BrutalMobs/EvilBiome/Projectiles/ErosionCloudSeed.cs:88-93 | Content/GameModes/BrutalMobs/EvilBiome/Projectiles/MummyWrapProj.cs:99-104 | Content/GameModes/BrutalMobs/EvilBiome/Projectiles/VileLanceProj.cs:96-101 | Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs:85-90 | Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgSnowShardProj.cs:87-92 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmIceShardProj.cs:72-77 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmNutShellProj.cs:105-110 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmOrnamentProj.cs:84-89 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmPineNeedleProj.cs:66-71 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmPresentShellProj.cs:80-85 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmSnowballProj.cs:117-122 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmStrafeBulletProj.cs:67-72 | Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyMaggotBolt.cs:119-124 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhImpFireBolt.cs:78-83 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhScytheBolt.cs:79-84 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhShellSpike.cs:70-75 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhStingerBolt.cs:79-84 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhTridentBolt.cs:78-83 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionClownBomb.cs:208-213 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionInkGlob.cs:86-91 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionScoutBolt.cs:85-90 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionVolleyArrow.cs:89-94 | Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserBoltProj.cs:113-118 | Content/GameModes/BrutalMobs/Martians/Projectiles/MrtScutlixHeavyBolt.cs:98-103 | Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteMoltenGlob.cs:145-150 | Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomSporeBoltProj.cs:113-118 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtBroadsideBall.cs:95-100 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtFanShot.cs:81-86 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtRicochetShot.cs:273-278 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkEmberSeedProj.cs:96-101 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkMortarShellProj.cs:98-103 | Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilCursedBeadProj.cs:76-81 | Content/GameModes/BrutalMobs/Sky/Projectiles/SkyFeatherBolt.cs:72-77 | Content/GameModes/BrutalMobs/SlimeKin/Projectiles/SlimeGelBomb.cs:196-201 | Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornJavelinProj.cs:90-95 | Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornQuakeWave.cs:154-159 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesIceShardProj.cs:73-78 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandPelletProj.cs:80-85 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMirrorPhantom.cs:294-299 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteStarSurge.cs:280-285 | Content/Items/Accessories/BrutalRelics/SkeletronPrime/OverloadArmProj.cs:571-576 | Content/Items/Accessories/BrutalRelics/Twins/TwinPupilShots.cs:85-90 | Content/Items/BloomArsenal.cs:120-125 | Content/Items/BloomArsenal.cs:197-202 | Content/Items/Magic/BloomTomes/BloomTome.cs:126-131 | Content/Items/Melee/DestroyersBladeEXs/DestroyerHeadMissile.cs:155-160 | Content/Items/Melee/DestroyersBladeEXs/DestroyerShadowBolt.cs:234-239 | Content/Items/Ranged/Thornstrings/ThornstringArrow.cs:99-104 | Content/Items/Summon/BloomCallers/BloomCallerSprout.cs:381-386 | Content/LegendWeapon/HalibutLegend/FishSkills/FishotroningVFX.cs:175-180 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomNeedle.cs:98-103 | Content/NPCs/BloomsandSerpents/Projectiles/BssNeedleProj.cs:62-67 | Content/NPCs/BloomsandSerpents/Projectiles/BssPetalProj.cs:80-85 | Content/NPCs/BloomsandSerpents/Projectiles/BssSandGlob.cs:68-73 | Content/NPCs/BloomsandSerpents/Projectiles/BssWindPetalProj.cs:99-104 | Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Projectiles/BrainBloodShard.cs:122-127 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerBolt.cs:92-97 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Projectiles/EocBloodShot.cs:96-101 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistSeekerStar.cs:183-188 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistStarBead.cs:174-179 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordBoltProj.cs:122-127 | Content/NPCs/BrutalNPCs/BrutalQueenBee/Projectiles/BrutalBeeStinger.cs:83-88 | Content/NPCs/FestersandSerpents/Projectiles/FssMortarShard.cs:65-70 | Content/NPCs/FestersandSerpents/Projectiles/FssMortarShell.cs:126-131 — before extracting anything, compare `Content/GameModes/BrutalMobs/Ambience/Ashreign/Projectiles/AshreignMagmaBeadProj.cs` and `Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhShellSpike.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Ambience/Ashreign/Projectiles/AshreignMagmaBeadProj.cs:160` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclEyezorOrbProj.cs:99` calls `Sin` and `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclNailheadNailProj.cs:89` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (6 lines × 59) · ×1
  • Duplicated block (6 lines × 59) Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdBoltProj.cs:167 — Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdBoltProj.cs:167-172 | Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclEyezorOrbProj.cs:102-107 | Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclManFlyFlaskProj.cs:165-170 | Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclNailheadNailProj.cs:92-97 | Content/GameModes/BrutalMobs/EliteMove/Projectiles/EMScatterBoltProj.cs:90-95 | Content/GameModes/BrutalMobs/EvilBiome/Projectiles/ErosionCloudSeed.cs:88-93 | Content/GameModes/BrutalMobs/EvilBiome/Projectiles/MummyWrapProj.cs:99-104 | Content/GameModes/BrutalMobs/EvilBiome/Projectiles/VileLanceProj.cs:96-101 | Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgMortarShellProj.cs:85-90 | Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgSnowShardProj.cs:87-92 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmIceShardProj.cs:72-77 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmNutShellProj.cs:105-110 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmOrnamentProj.cs:84-89 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmPineNeedleProj.cs:66-71 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmPresentShellProj.cs:80-85 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmSnowballProj.cs:117-122 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmStrafeBulletProj.cs:67-72 | Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyMaggotBolt.cs:119-124 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionClownBomb.cs:208-213 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionInkGlob.cs:86-91 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionScoutBolt.cs:85-90 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionVolleyArrow.cs:89-94 | Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserBoltProj.cs:113-118 | Content/GameModes/BrutalMobs/Martians/Projectiles/MrtScutlixHeavyBolt.cs:98-103 | Content/GameModes/BrutalMobs/Meteorite/Projectiles/MeteoriteMoltenGlob.cs:145-150 | Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomSporeBoltProj.cs:113-118 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtBroadsideBall.cs:95-100 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtFanShot.cs:81-86 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtRicochetShot.cs:273-278 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkEmberSeedProj.cs:96-101 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkMortarShellProj.cs:98-103 | Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilCursedBeadProj.cs:76-81 | Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornJavelinProj.cs:90-95 | Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornQuakeWave.cs:154-159 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesIceShardProj.cs:73-78 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandPelletProj.cs:80-85 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMirrorPhantom.cs:294-299 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteStarSurge.cs:280-285 | Content/Items/Accessories/BrutalRelics/Twins/TwinPupilShots.cs:85-90 | Content/Items/BloomArsenal.cs:120-125 | Content/Items/BloomArsenal.cs:197-202 | Content/Items/Magic/BloomTomes/BloomTome.cs:126-131 | Content/Items/Melee/DestroyersBladeEXs/DestroyerHeadMissile.cs:155-160 | Content/Items/Melee/DestroyersBladeEXs/DestroyerShadowBolt.cs:234-239 | Content/Items/Ranged/Thornstrings/ThornstringArrow.cs:99-104 | Content/Items/Summon/BloomCallers/BloomCallerSprout.cs:381-386 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomNeedle.cs:98-103 | Content/NPCs/BloomsandSerpents/Projectiles/BssNeedleProj.cs:62-67 | Content/NPCs/BloomsandSerpents/Projectiles/BssPetalProj.cs:80-85 | Content/NPCs/BloomsandSerpents/Projectiles/BssSandGlob.cs:68-73 | Content/NPCs/BloomsandSerpents/Projectiles/BssWindPetalProj.cs:99-104 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerBolt.cs:92-97 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs:154-159 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Projectiles/EocBloodShot.cs:96-101 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordBoltProj.cs:122-127 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordOrbProj.cs:375-380 | Content/NPCs/FestersandSerpents/Projectiles/FssIchorGlob.cs:152-157 | Content/NPCs/FestersandSerpents/Projectiles/FssMortarShard.cs:65-70 | Content/NPCs/FestersandSerpents/Projectiles/FssMortarShell.cs:126-131 — there are 59 copies across 58 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 59 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdBoltProj.cs:167` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclEyezorOrbProj.cs:99` calls `Sin` and `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclNailheadNailProj.cs:89` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (6 lines × 34) · ×1
  • Duplicated block (6 lines × 34) Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclEyezorOrbProj.cs:103 — Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclEyezorOrbProj.cs:103-108 | Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclManFlyFlaskProj.cs:166-171 | Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclNailheadNailProj.cs:93-98 | Content/GameModes/BrutalMobs/EliteMove/Projectiles/EMScatterBoltProj.cs:91-96 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmIceShardProj.cs:73-78 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmPresentShellProj.cs:81-86 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionClownBomb.cs:209-214 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionInkGlob.cs:87-92 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionScoutBolt.cs:86-91 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionVolleyArrow.cs:90-95 | Content/GameModes/BrutalMobs/Martians/Projectiles/MrtScutlixHeavyBolt.cs:99-104 | Content/GameModes/BrutalMobs/NightPack/Projectiles/NightBoneProj.cs:171-176 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtBroadsideBall.cs:96-101 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtFanShot.cs:82-87 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtRicochetShot.cs:274-279 | Content/GameModes/BrutalMobs/Stoneborn/Projectiles/StonebornJavelinProj.cs:91-96 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesIceShardProj.cs:74-79 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesSandPelletProj.cs:81-86 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMirrorPhantom.cs:295-300 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteStarSurge.cs:281-286 | Content/Items/Accessories/BrutalRelics/Twins/TwinPupilShots.cs:86-91 | Content/Items/BloomArsenal.cs:198-203 | Content/Items/Magic/BloomTomes/BloomTome.cs:127-132 | Content/Items/Melee/DestroyersBladeEXs/DestroyerShadowBolt.cs:235-240 | Content/Items/Ranged/Thornstrings/ThornstringArrow.cs:100-105 | Content/Items/Summon/BloomCallers/BloomCallerSprout.cs:382-387 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomNeedle.cs:99-104 | Content/NPCs/BloomsandSerpents/Projectiles/BssNeedleProj.cs:63-68 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerBolt.cs:93-98 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs:155-160 | Content/NPCs/BrutalNPCs/BrutalEyeOfCthulhu/Projectiles/EocBloodSpike.cs:73-78 | Content/NPCs/FestersandSerpents/Projectiles/FssIchorGlob.cs:153-158 | Content/NPCs/FestersandSerpents/Projectiles/FssMortarShard.cs:66-71 | Content/NPCs/FestersandSerpents/Projectiles/FssMortarShell.cs:127-132 — before extracting anything, compare `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclEyezorOrbProj.cs` and `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclManFlyFlaskProj.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 30 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclEyezorOrbProj.cs:103` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclEyezorOrbProj.cs:99` calls `Sin` and `Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclNailheadNailProj.cs:89` 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.
D4 · Code Duplication · Duplicated block (6 lines × 31) · ×1
  • Duplicated block (6 lines × 31) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1090 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1090-1097 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1159-1164 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:919-924 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1178-1183 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:976-981 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1512-1517 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:1100-1105 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1241-1246 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:986-991 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:812-817 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:1055-1060 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:981-986 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:880-885 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:940-945 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:913-918 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1381-1386 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:932-937 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1271-1276 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:1111-1116 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:1319-1324 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:959-965 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:932-937 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:1447-1452 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1368-1373 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:1404-1409 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:1109-1114 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:1164-1169 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1536-1541 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1560-1565 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:969-974 | Content/LegendWeapon/KikasaLegend/KikasaVaults/KikasaLakeFX.cs:637-644 — there are 31 copies across 30 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 31 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1090` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1159` calls `End` and `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1090` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (6 lines × 28) · ×1
  • Duplicated block (6 lines × 28) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:528 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:528-533 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:467-472 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:548-553 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:475-480 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:629-634 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:716-721 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:465-470 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:554-559 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:560-565 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:757-762 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:839-844 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:513-518 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:593-598 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:521-526 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:421-426 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:499-504 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:468-473 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:548-553 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:440-445 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:430-435 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:511-516 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:483-488 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:462-467 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:544-549 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:504-509 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:559-564 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:388-393 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:687-692 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (6 lines × 16) · ×1
  • Duplicated block (6 lines × 16) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:410 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:410-415 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:489-494 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:409-414 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:368-373 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:362-367 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:433-438 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemMagmaBall.cs:224-229 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:425-430 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:474-479 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:540-545 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:546-551 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:473-478 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:410-415 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:440-445 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:478-483 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:457-462 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 16 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 16 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:410` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (4–6 lines × 16) · ×1
  • Duplicated block (4–6 lines × 16) Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1160 — Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1160-1165 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainClot.cs:284-289 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:1068-1073 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:1285-1290 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:1299-1304 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1353-1358 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:1396-1399 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:1439-1444 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1447-1452 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1493-1498 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:1523-1528 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1560-1565 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:1585-1590 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:1587-1592 | Content/LegendWeapon/KikasaLegend/KikasaVaults/KikasaLakeFX.cs:687-692 | Content/LegendWeapon/KikasaLegend/KikasaVaults/KikasaVaultRenderer.cs:128-133 — there are 16 copies across 12 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 16 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaDrowns/KikasaDrownFX.cs:1160` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (6 lines × 14) · ×1
  • Duplicated block (6 lines × 14) Common/ShockRingDraw.cs:60 — Common/ShockRingDraw.cs:60-65 | Content/GameModes/BrutalMobs/Ambience/Tidecall/Projectiles/TidecallRogueWaveProj.cs:363-369 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteMoonFlare.cs:278-283 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteRingRender.cs:131-136 | Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteStarSurge.cs:192-197 | Content/Items/Accessories/BrutalRelics/QueenBee/SwarmVortexProj.cs:367-372 | Content/Items/Armor/Deepcrystals/DeepcrystalPayloads.cs:180-185 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistGazeBeam.cs:280-285 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistGazeBeam.cs:342-347 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistPlanetProj.cs:854-859 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistUmbraShade.cs:510-515 | Content/NPCs/BrutalNPCs/BrutalLunaticCultist/Projectiles/CultistZodiacRing.cs:181-186 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordOrbProj.cs:299-304 | Content/Scenarios/Dungeonworld/NPCs/UndrownedTideWave.cs:158-164 — before extracting anything, compare `Common/ShockRingDraw.cs` and `Content/Items/Accessories/BrutalRelics/LunaticCultist/RiteRingRender.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (6 lines × 12) · ×1
  • Duplicated block (6 lines × 12) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:996 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:996-1002 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1124-1130 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:903-909 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:712-718 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:966-972 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1190-1196 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1177-1182 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:980-985 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:788-793 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:758-763 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:1093-1098 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:1162-1167 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs` as WHOLE FILES: this scan already matched 51 separate duplicated blocks between them, totalling at least 598 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:996` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:750` calls `StartPulse` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:1172` 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.
D4 · Code Duplication · Duplicated block (5–6 lines × 5) · ×1
  • Duplicated block (5–6 lines × 5) Content/Items/Accessories/EyeOfSingularity.cs:98 — Content/Items/Accessories/EyeOfSingularity.cs:98-102 | Content/Items/Melee/NeutronGlaive.cs:1254-1258 | Content/Items/Melee/NeutronGlaive.cs:1320-1324 | Content/Items/Melee/SpearOfLonginuses/PilgrimsFury.cs:125-130 | Content/Items/Ranged/NeutronBows/EXNeutronExplosionRanged.cs:31-35 — before extracting anything, compare `Content/Items/Melee/NeutronGlaive.cs` and `Content/Items/Ranged/NeutronBows/EXNeutronExplosionRanged.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Items/Accessories/EyeOfSingularity.cs:98` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Items/Melee/NeutronGlaive.cs:1319` calls `PlaySound` and `Content/Items/Melee/NeutronGlaive.cs:1253` does not — after which the two agree again for 4 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.
D4 · Code Duplication · Duplicated block (2–6 lines × 4) · ×1
  • Duplicated block (2–6 lines × 4) Content/Industrials/Modifys/ChargingStationUI.cs:415 — Content/Industrials/Modifys/ChargingStationUI.cs:415-420 | Content/Narrative/Presentation/Skins/Sea/SeaChoiceSkin.cs:60-61 | Content/Narrative/Presentation/Skins/StarStream/StarStreamPanelDraw.cs:261-266 | Content/Scenarios/OldDuke/OceanRaiderses/OceanRaidersUIs/OceanRaidersRenderer.cs:213-218 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/Modifys/ChargingStationUI.cs:415` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (5 lines × 25) · ×1
  • Duplicated block (5 lines × 25) Content/Industrials/ElectricPowers/Collectors/Collector.cs:117 — Content/Industrials/ElectricPowers/Collectors/Collector.cs:117-121 | Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs:112-116 | Content/Industrials/ElectricPowers/HealingStations/HealStationTile.cs:119-123 | Content/Industrials/ElectricPowers/Incinerators/IncineratorTile.cs:104-108 | Content/Industrials/ElectricPowers/LifeWeavers/LifeWeaverTile.cs:65-69 | Content/Industrials/ElectricPowers/LifeWeavers/WGGLifeWeaver.cs:117-121 | Content/Industrials/ElectricPowers/Lumberjacks/LumberjackTile.cs:64-68 | Content/Industrials/ElectricPowers/Lumberjacks/WGGLumberjack.cs:112-116 | Content/Industrials/ElectricPowers/MiningMachines/BaseMiningMachineTP.cs:432-436 | Content/Industrials/ElectricPowers/ShieldGenerators/ShieldGeneratorTile.cs:119-123 | Content/Industrials/ElectricPowers/SlimeVats/SlimeVatTile.cs:118-122 | Content/Industrials/ElectricPowers/Spectrometers/Spectrometer.cs:108-112 | Content/Industrials/ElectricPowers/Suppressors/PacifierTowerTile.cs:119-123 | Content/Industrials/ElectricPowers/TeslaElectromagneticTower.cs:190-194 | Content/Industrials/ElectricPowers/Turrets/CryoTurrets/CryoTurretTile.cs:119-123 | Content/Industrials/ElectricPowers/Turrets/FlameTurrets/FlameTurretTile.cs:119-123 | Content/Industrials/ElectricPowers/Turrets/LaserTurrets/LaserTurretTile.cs:119-123 | Content/Industrials/ElectricPowers/WeatherControllers/WeatherControllerTile.cs:128-132 | Content/Industrials/Generator/Biomass/BiomassGenerator.cs:137-141 | Content/Industrials/Generator/Thermal/ThermalGenerator.cs:103-107 | Content/Industrials/Generator/Thermal/ThermalGeneratorMK2.cs:103-107 | Content/Items/Placeable/HoChaMeditatorItem.cs:81-85 | Content/Items/Placeable/StarflowPlatedBlock.cs:80-84 | Content/Scenarios/Draedon/Quest/DeploySignaltowers/CQETConstructor.cs:115-119 | Content/Tiles/NeutronStarIngotTile.cs:49-53 — before extracting anything, compare `Content/Industrials/ElectricPowers/Collectors/Collector.cs` and `Content/Industrials/ElectricPowers/Collectors/WGGCollector.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 49 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Collectors/Collector.cs:117` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Industrials/ElectricPowers/Collectors/Collector.cs:116` calls `Draw`, `Rectangle` and `Content/Industrials/ElectricPowers/HealingStations/HealStationTile.cs:119` 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.
D4 · Code Duplication · Duplicated block (5 lines × 21) · ×1
  • Duplicated block (5 lines × 21) Content/Items/Accessories/ArcaneThroneOfEternity.cs:454 — Content/Items/Accessories/ArcaneThroneOfEternity.cs:454-459 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDetonationProj.cs:203-208 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberShockwaveProj.cs:89-94 | Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberspaceRender.cs:474-478 | Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberFreezeWaveProj.cs:82-87 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Restart/CyberRestartProj.cs:210-215 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberPixelDecomposeProj.cs:83-88 | Content/LegendWeapon/SHPCLegend/Cyberspaces/Teleport/CyberReformProj.cs:89-94 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/HeavyBarrelModule.cs:315-320 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/HypersonicBarrelModule.cs:208-213 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/RapidBarrelModule.cs:656-661 | Content/LegendWeapon/SHPCLegend/Modules/Barrel/ScattershotBarrelModule.cs:381-386 | Content/LegendWeapon/SHPCLegend/Modules/Frame/ResonanceFrameModule.cs:693-699 | Content/LegendWeapon/SHPCLegend/Modules/Optic/HoloOpticModule.cs:193-198 | Content/LegendWeapon/SHPCLegend/Modules/Optic/PrecisionOpticModule.cs:236-241 | Content/LegendWeapon/SHPCLegend/Modules/Optic/SniperOpticModule.cs:402-407 | Content/LegendWeapon/SHPCLegend/Modules/Optic/SniperOpticModule.cs:615-620 | Content/LegendWeapon/SHPCLegend/Modules/Power/PlasmaInjectorModule.cs:165-170 | Content/LegendWeapon/SHPCLegend/Modules/Stock/BraceStockModule.cs:487-492 | Content/LegendWeapon/SHPCLegend/Modules/Stock/ExtenderStockModule.cs:433-438 | Content/LegendWeapon/SHPCLegend/Modules/Stock/SteadyStockModule.cs:563-567 — before extracting anything, compare `Content/Items/Accessories/ArcaneThroneOfEternity.cs` and `Content/LegendWeapon/SHPCLegend/Cyberspaces/CyberDetonationProj.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 112 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (5 lines × 19) · ×1
  • Duplicated block (5 lines × 19) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:514 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:514-518 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:411-415 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:490-494 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:410-414 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:463-467 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:369-373 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeServant.cs:363-367 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFishron/KikasaFishronServant.cs:434-438 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemMagmaBall.cs:225-229 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:426-430 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:475-479 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaKingSlime/KikasaKingSlimeServant.cs:753-757 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:541-545 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:547-551 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:474-478 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenBee/KikasaQueenBeeServant.cs:411-415 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaQueenSlime/KikasaQueenSlimeServant.cs:441-445 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSkeletron/KikasaSkeletronServant.cs:479-483 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:458-462 — there are 19 copies across 18 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 19 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:514` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:424` calls `SpawnChip`, `Vector2`, `NextFloat` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:462` 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.
D4 · Code Duplication · Duplicated block (5 lines × 17) · ×1
  • Duplicated block (5 lines × 17) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:382 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:382-386 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:388-392 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:354-358 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:386-390 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:395-399 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:385-389 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:375-379 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:318-322 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:301-305 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:349-353 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:341-345 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:351-355 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:350-354 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:383-387 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:391-395 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:462-466 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:402-406 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:382` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:469` calls `UpdateVesselRaise` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:392` 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.
D4 · Code Duplication · Duplicated block (5 lines × 13) · ×1
  • Duplicated block (5 lines × 13) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1000 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1000-1004 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:803-807 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:1043-1047 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:819-823 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:1342-1346 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:935-939 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:1041-1045 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:860-864 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:765-769 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:791-795 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:797-801 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:1117-1121 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:814-819 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:1000` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (5 lines × 12) · ×1
  • Duplicated block (5 lines × 12) Content/Items/Accessories/BrutalRelics/MoonLord/BlackFlashSigilRender.cs:142 — Content/Items/Accessories/BrutalRelics/MoonLord/BlackFlashSigilRender.cs:142-147 | Content/Scenarios/Dungeonworld/Gen/BossRooms/FloodGalleryRender.cs:221-226 | Content/Scenarios/Dungeonworld/NPCs/Elites/LampeaterWisp.cs:576-580 | Content/Scenarios/Dungeonworld/NPCs/Elites/TurnkeyRendering.cs:62-67 | Content/Scenarios/Kiyume/NPCs/FacelessOneYokai.cs:494-499 | Content/Scenarios/Kiyume/NPCs/FuneralCortegeYokai.cs:1207-1212 | Content/Scenarios/Kiyume/NPCs/KiyumeHound.cs:1051-1056 | Content/Scenarios/Kiyume/NPCs/KiyumeWhiteHound.cs:474-479 | Content/Scenarios/Kiyume/NPCs/LanternGuideYokai.cs:592-597 | Content/Scenarios/Kiyume/NPCs/RidgeWalkerYokai.cs:594-599 | Content/Scenarios/Kiyume/NPCs/ShallowHandsYokai.cs:395-400 | Content/Scenarios/Kiyume/NPCs/WellHandYokai.cs:407-412 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 12 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 12 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Scenarios/Kiyume/NPCs/FacelessOneYokai.cs:493` calls `End` and `Content/Scenarios/Dungeonworld/NPCs/Elites/TurnkeyRendering.cs:60` 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.
D4 · Code Duplication · Duplicated block (4–5 lines × 10) · ×1
  • Duplicated block (4–5 lines × 10) Content/HackTimes/Protocols/Contagion.cs:37 — Content/HackTimes/Protocols/Contagion.cs:37-41 | Content/HackTimes/Protocols/Contagion.cs:117-121 | Content/HackTimes/Protocols/Cyberpsychosis.cs:80-84 | Content/HackTimes/Protocols/Cyberpsychosis.cs:88-92 | Content/HackTimes/Protocols/MemoryWipe.cs:90-94 | Content/HackTimes/Protocols/OpticOverload.cs:83-87 | Content/HackTimes/Protocols/ShortCircuit.cs:38-41 | Content/HackTimes/Protocols/SynapseBurn.cs:34-38 | Content/HackTimes/Protocols/SystemReset.cs:47-51 | Content/HackTimes/Protocols/SystemReset.cs:106-109 — before extracting anything, compare `Content/HackTimes/Protocols/Cyberpsychosis.cs` and `Content/HackTimes/Protocols/MemoryWipe.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 39 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. Read the line range as the matched WINDOW rather than a finished unit: at `Content/HackTimes/Protocols/ShortCircuit.cs:38` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/HackTimes/Protocols/SystemReset.cs:109` calls `Color`, `Configure`, `NewText` and `Content/HackTimes/Protocols/Contagion.cs:121` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (4–5 lines × 6) · ×1
  • Duplicated block (4–5 lines × 6) Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:445 — Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:445-448 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:476-479 | Content/Scenarios/OldNet/Tiles/OldNetEchoNodeTile.cs:143-147 | Content/Scenarios/OldNet/Tiles/OldNetEncryptedNodeTile.cs:184-188 | Content/Scenarios/OldNet/Tiles/OldNetEventNodeTile.cs:132-136 | Content/Scenarios/OldNet/Tiles/OldNetSentryMineTile.cs:150-155 — before extracting anything, compare `Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs` and `Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 303 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:445` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (2–5 lines × 4) · ×1
  • Duplicated block (2–5 lines × 4) Content/Scenarios/Himayo/ToriiShrines/ToriiShrineActor.cs:140 — Content/Scenarios/Himayo/ToriiShrines/ToriiShrineActor.cs:140-141 | Content/Scenarios/OldDuke/Campsites/CampsitePotActor.cs:122-126 | Content/Scenarios/OldDuke/Campsites/CampsitePotActor.cs:130-132 | Content/Scenarios/OldDuke/OldDuchests/OldDuchestTP.cs:350-360 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Content/Scenarios/OldDuke/OldDuchests/OldDuchestTP.cs:350` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (25 lines × 4) · ×1
  • Duplicated block (25 lines × 4) Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterTP.cs:531 — Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterTP.cs:531-555 | Content/Industrials/ElectricPowers/Crushers/CrusherTP.cs:398-422 | Content/Industrials/ElectricPowers/Incinerators/IncineratorTP.cs:286-310 | Content/Industrials/ElectricPowers/Recyclers/RecyclerTP.cs:444-468 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
D4 · Code Duplication · Duplicated block (42 lines × 2) · ×1
  • Duplicated block (42 lines × 2) Content/Industrials/ElectricPowers/Crushers/CrusherTP.cs:109 — Content/Industrials/ElectricPowers/Crushers/CrusherTP.cs:109-150 | Content/Industrials/ElectricPowers/Recyclers/RecyclerTP.cs:116-157 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (3–13 lines × 5) · ×1
  • Duplicated block (3–13 lines × 5) Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:237 — Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:237-250 | Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs:243-256 | Content/Industrials/ElectricPowers/Recyclers/RecyclerUI.cs:238-250 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterUI.cs:241-244 | Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterUI.cs:256-258 — before extracting anything, compare `Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs` and `Content/Industrials/ElectricPowers/Incinerators/IncineratorUI.cs` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 303 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/Industrials/ElectricPowers/ShimmerTransmuters/ShimmerTransmuterUI.cs:241` calls `Vector2` and `Content/Industrials/ElectricPowers/Crushers/CrusherUI.cs:237` 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.
D4 · Code Duplication · Duplicated block (44 lines × 2) · ×1
  • Duplicated block (44 lines × 2) Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs:136 — Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs:136-179 | Content/Items/Melee/WeaverGrievanceses/WGManifestationNet.cs:137-180 — before extracting anything, compare `Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs` and `Content/Items/Melee/WeaverGrievanceses/WGManifestationNet.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 145 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (32 lines × 2) · ×1
  • Duplicated block (32 lines × 2) Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs:219 — Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs:219-250 | Content/Items/Melee/WeaverGrievanceses/WGManifestationNet.cs:220-251 — before extracting anything, compare `Content/Items/Melee/Arbiters/ArbiterManifestationNet.cs` and `Content/Items/Melee/WeaverGrievanceses/WGManifestationNet.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 145 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (17 lines × 9) · ×1
  • Duplicated block (17 lines × 9) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:164 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:164-181 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:125-141 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:145-161 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:125-141 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:171-188 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:136-152 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:136-152 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:139-156 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:123-139 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (8 lines × 28) · ×1
  • Duplicated block (8 lines × 28) Content/GameModes/BrutalMobs/Ambience/Aetherglim/AetherglimFX.cs:64 — Content/GameModes/BrutalMobs/Ambience/Aetherglim/AetherglimFX.cs:64-71 | Content/GameModes/BrutalMobs/Ambience/Ashreign/Ashreign.cs:98-105 | Content/GameModes/BrutalMobs/Ambience/Astralveil/AstralveilSpearDirector.cs:180-187 | Content/GameModes/BrutalMobs/Ambience/Brinefume/BrinefumeAmbience.cs:318-325 | Content/GameModes/BrutalMobs/Ambience/Cindercrag/CindercragAmbience.cs:68-75 | Content/GameModes/BrutalMobs/Ambience/DuneStorm/DuneStorm.cs:97-104 | Content/GameModes/BrutalMobs/Ambience/Hollowdeep/HollowdeepAmbience.cs:152-159 | Content/GameModes/BrutalMobs/Ambience/Mireheart/MireheartPlayer.cs:81-88 | Content/GameModes/BrutalMobs/Ambience/Nyxdepth/NyxdepthPlayer.cs:85-92 | Content/GameModes/BrutalMobs/Ambience/Rimehollow/RimehollowDirector.cs:67-74 | Content/GameModes/BrutalMobs/Ambience/Silkcrypt/SilkcryptPlayer.cs:171-178 | Content/GameModes/BrutalMobs/Ambience/Sporeshine/SporeshinePlayer.cs:227-234 | Content/GameModes/BrutalMobs/Ambience/Stonewake/StonewakeFX.cs:50-57 | Content/GameModes/BrutalMobs/Ambience/Stratos/StratosAmbience.cs:142-149 | Content/GameModes/BrutalMobs/Ambience/Sunkendune/SunkendunePlayer.cs:226-233 | Content/GameModes/BrutalMobs/Ambience/Tidecall/TidecallAmbience.cs:307-314 | Content/GameModes/BrutalMobs/Ambience/Verdant/VerdantAmbience.cs:73-80 | Content/GameModes/BrutalMobs/DungeonDeep/DungeonDeepNPC.cs:243-250 | Content/GameModes/BrutalMobs/FrostLegion/FrostLegionNPC.cs:241-248 | Content/GameModes/BrutalMobs/Graveyard/GraveyardBrutalNPC.cs:169-176 | Content/GameModes/BrutalMobs/Meteorite/MeteoriteBrutalNPC.cs:112-119 | Content/GameModes/BrutalMobs/Mushroom/MushroomBrutalNPC.cs:216-223 | Content/GameModes/BrutalMobs/Ocean/OceanBrutalNPC.cs:259-266 | Content/GameModes/BrutalMobs/Sandveil/SandveilBrutalNPC.cs:218-225 | Content/GameModes/BrutalMobs/Sky/SkyBrutalNPC.cs:120-127 | Content/GameModes/BrutalMobs/Stoneborn/StonebornBrutalNPC.cs:201-208 | Content/GameModes/BrutalMobs/Temple/TempleBrutalNPC.cs:231-238 | Content/GameModes/BrutalMobs/Wastes/WastesBrutalNPC.cs:172-179 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 28 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 28 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/GameModes/BrutalMobs/Ambience/Aetherglim/AetherglimFX.cs:59` calls `MechanicsAllowed`, `NearTownNPC` and `Content/GameModes/BrutalMobs/Ambience/Astralveil/AstralveilSpearDirector.cs:176` 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.
D4 · Code Duplication · Duplicated block (11 lines × 45) · ×1
  • Duplicated block (11 lines × 45) Content/GameModes/BrutalMobs/Ambience/Astralveil/Projectiles/AstralveilBloomProj.cs:52 — Content/GameModes/BrutalMobs/Ambience/Astralveil/Projectiles/AstralveilBloomProj.cs:52-63 | Content/GameModes/BrutalMobs/Ambience/Fleshfen/Projectiles/FleshfenDewRainProj.cs:63-73 | Content/GameModes/BrutalMobs/Ambience/Lumindepth/Projectiles/LumindepthVortexProj.cs:43-53 | Content/GameModes/BrutalMobs/Ambience/Mournfog/Projectiles/MournfogGrudgeRingProj.cs:67-77 | Content/GameModes/BrutalMobs/Ambience/Nyxdepth/Projectiles/NyxdepthSinkColumnProj.cs:40-50 | Content/GameModes/BrutalMobs/Ambience/Rimehollow/Projectiles/RimehollowMistPoolProj.cs:51-61 | Content/GameModes/BrutalMobs/Ambience/Stratos/Projectiles/StratosUpdraftProj.cs:52-62 | Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdChargeOmen.cs:133-143 | Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdGuardStanceProj.cs:38-48 | Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdMarksmanOmen.cs:64-74 | Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdRocketProj.cs:43-53 | Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclOpeningProj.cs:33-44 | Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclStrikeOmen.cs:58-69 | Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs:50-60 | Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgStabGlintOmen.cs:45-55 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmAimLaneOmen.cs:69-79 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmBlizzardFrontProj.cs:43-53 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmFlockoBurstOmen.cs:55-65 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmIcingPatchProj.cs:42-52 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmMortarBlastProj.cs:43-53 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmPoseTelegraphProj.cs:55-65 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmStrafeLaneProj.cs:46-56 | Content/GameModes/BrutalMobs/FrostMoon/Projectiles/FrmWaltzRingProj.cs:69-79 | Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyGhostNameThread.cs:55-65 | Content/GameModes/BrutalMobs/Graveyard/Projectiles/GyRavenSwoopOmen.cs:60-70 | Content/GameModes/BrutalMobs/JungleHell/Projectiles/JhVolleyOmen.cs:68-78 | Content/GameModes/BrutalMobs/Legion/Projectiles/LegionPoseOmen.cs:55-65 | Content/GameModes/BrutalMobs/Martians/Projectiles/MrtLaserMarkLine.cs:107-117 | Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomChargeGlowProj.cs:42-52 | Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomSporeMistTelegraph.cs:71-81 | Content/GameModes/BrutalMobs/Mushroom/Projectiles/MushroomSporePatchZone.cs:45-55 | Content/GameModes/BrutalMobs/Ocean/Projectiles/OceanInkCloud.cs:41-51 | Content/GameModes/BrutalMobs/Ocean/Projectiles/OceanSandMound.cs:43-53 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkEmberFlareProj.cs:40-50 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkEmberProj.cs:52-62 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkEmberSeedProj.cs:35-45 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkMortarMarkerProj.cs:65-75 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkRitualWispProj.cs:66-76 | Content/GameModes/BrutalMobs/PumpkinMoon/Projectiles/PmkRootSpikeProj.cs:73-83 | Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilBounceMarkOmen.cs:48-58 | Content/GameModes/BrutalMobs/Sandveil/Projectiles/SandveilSurgeColumnProj.cs:79-89 | Content/GameModes/BrutalMobs/SlimeKin/Projectiles/SlimeGooPatch.cs:48-58 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesElementRing.cs:37-47 | Content/GameModes/BrutalMobs/Wastes/Projectiles/WastesIceSlickZone.cs:44-54 | Content/NPCs/BrutalNPCs/BrutalDukeFishron/Projectiles/FishronVortexProj.cs:32-43 — before extracting anything, compare `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgAimLineOmen.cs` and `Content/GameModes/BrutalMobs/FrostLegion/Projectiles/FlgStabGlintOmen.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 89 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdChargeOmen.cs:146` calls `CanDamage` and `Content/GameModes/BrutalMobs/Ambience/Lumindepth/Projectiles/LumindepthVortexProj.cs:55` does not — after which the two agree again for 4 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.
D4 · Code Duplication · Duplicated block (9 lines × 22) · ×1
  • Duplicated block (9 lines × 22) Content/GameModes/BrutalMobs/Ambience/Bloodveil/PRT_BloodveilMist.cs:43 — Content/GameModes/BrutalMobs/Ambience/Bloodveil/PRT_BloodveilMist.cs:43-51 | Content/GameModes/BrutalMobs/Ambience/Duskwatch/PRT_DuskwatchAsh.cs:37-45 | Content/GameModes/BrutalMobs/Ambience/Fleshfen/FleshfenPRT_BloodDrop.cs:53-61 | Content/GameModes/BrutalMobs/Ambience/Frostveil/FrostveilPRT.cs:37-45 | Content/GameModes/BrutalMobs/Ambience/Frostveil/FrostveilPRT.cs:113-121 | Content/GameModes/BrutalMobs/Ambience/Frostveil/FrostveilPRT.cs:179-187 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressPetal.cs:249-257 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEye/KikasaEyeBloodShot.cs:301-309 | Content/PRTTypes/PRT_GhostRainDrop.cs:69-77 | Content/PRTTypes/PRT_GhostRainYank.cs:32-40 | Content/PRTTypes/PRT_KikasaBloodSpray.cs:68-76 | Content/PRTTypes/PRT_KikasaInkBead.cs:38-46 | Content/PRTTypes/PRT_KikasaInkDrip.cs:32-40 | Content/PRTTypes/PRT_OniPuddleRise.cs:43-51 | Content/PRTTypes/PRT_SewageGlob.cs:54-62 | Content/PRTTypes/PRT_TurnkeyDrip.cs:35-43 | Content/PRTTypes/PRT_TurnkeyFoam.cs:40-48 | Content/Scenarios/Dungeonworld/NPCs/GaolFireBolt.cs:250-258 | Content/Scenarios/Dungeonworld/NPCs/OverseerSlagGlob.cs:231-239 | Content/Scenarios/Dungeonworld/NPCs/OverseerVfx.cs:286-294 | Content/Scenarios/Dungeonworld/NPCs/UndrownedAnchor.cs:248-256 | Content/Scenarios/Dungeonworld/NPCs/UndrownedTideWave.cs:222-230 — there are 22 copies across 20 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 22 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (5 lines × 22) · ×1
  • Duplicated block (5 lines × 22) Content/GameModes/BrutalMobs/Ambience/DuneStorm/Projectiles/DuneStormSandLashProj.cs:32 — Content/GameModes/BrutalMobs/Ambience/DuneStorm/Projectiles/DuneStormSandLashProj.cs:32-36 | Content/GameModes/BrutalMobs/DungeonDeep/Projectiles/DdBoltProj.cs:69-73 | Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclEyezorOrbProj.cs:30-34 | Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclManFlyFlaskProj.cs:39-43 | Content/GameModes/BrutalMobs/Eclipse/Projectiles/EclNailheadNailProj.cs:29-33 | Content/GameModes/BrutalMobs/NightPack/Projectiles/NightBoneProj.cs:49-53 | Content/GameModes/BrutalMobs/Pirates/Projectiles/PrtRicochetShot.cs:65-69 | Content/Items/Accessories/BrutalRelics/Golem/SolarCoreFistProj.cs:40-44 | Content/Items/Ranged/Starships/StarshipComet.cs:16-20 | Content/Items/Ranged/Starships/StarshipMeteor.cs:19-23 | Content/Items/Ranged/Starships/StarshipPlanet.cs:73-77 | Content/Items/Ranged/Starships/StarshipPlasmaBolt.cs:14-18 | Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Projectiles/BrainBloodShard.cs:23-27 | Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Projectiles/BrainMirrorImage.cs:52-56 | Content/NPCs/BrutalNPCs/BrutalDestroyer/Projectiles/DestroyerBolt.cs:19-23 | Content/NPCs/BrutalNPCs/BrutalEaterOfWorlds/Projectiles/EowAcidGlob.cs:25-29 | Content/NPCs/BrutalNPCs/BrutalEmpressOfLight/Projectiles/EmpressLightBolt.cs:52-56 | Content/NPCs/BrutalNPCs/BrutalMoonLord/Projectiles/MLordCometProj.cs:31-35 | Content/NPCs/BrutalNPCs/BrutalSkeletronPrime/Projectiles/PrimeSeekerMissile.cs:28-32 | Content/NPCs/FestersandSerpents/Projectiles/FssCascadeDrop.cs:21-25 | Content/NPCs/FestersandSerpents/Projectiles/FssIchorGlob.cs:25-29 | Content/NPCs/FestersandSerpents/Projectiles/FssMortarShell.cs:24-28 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 22 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 22 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Content/NPCs/BrutalNPCs/BrutalBrainOfCthulhu/Projectiles/BrainMirrorImage.cs:50` calls `PackMode` and `Content/Items/Ranged/Starships/StarshipMeteor.cs:17` 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.
D4 · Code Duplication · Duplicated block (5 lines × 30) · ×1
  • Duplicated block (5 lines × 30) Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:185 — Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs:185-190 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs:145-149 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBows/KikasaBowServant.cs:165-169 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaFlails/KikasaFlailServant.cs:145-149 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs:192-197 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaHalibut/KikasaHalibutServant.cs:194-198 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaOnikiri/KikasaOnikiriServant.cs:197-202 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaPandemonium/KikasaPandemoniumServant.cs:131-135 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaRods/KikasaRodServant.cs:136-140 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSHPC/KikasaSHPCServant.cs:176-180 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaSpears/KikasaSpearServant.cs:156-160 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaThrows/KikasaThrowServant.cs:156-160 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaWhips/KikasaWhipServant.cs:160-165 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaYoyos/KikasaYoyoServant.cs:143-147 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaZenith/KikasaZenithServant.cs:206-211 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBloomSerpent/KikasaBloomSerpentServant.cs:148-152 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaBrain/KikasaBrainServant.cs:182-187 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaCultist/KikasaCultistServant.cs:162-167 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDeerclops/KikasaDeerclopsServant.cs:169-174 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaDestroyer/KikasaDestroyerServant.cs:159-164 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEater/KikasaEaterServant.cs:182-187 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaEmpress/KikasaEmpressServant.cs:131-136 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaFesterSerpent/KikasaFesterSerpentServant.cs:151-155 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaGolem/KikasaGolemServant.cs:165-170 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaMoonLord/KikasaMoonLordServant.cs:173-178 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPlantera/KikasaPlanteraServant.cs:178-183 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaPrime/KikasaPrimeServant.cs:181-186 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaSeaShrimp/KikasaSeaShrimpServant.cs:199-203 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaTwins/KikasaTwinsServant.cs:193-198 | Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaWallOfFlesh/KikasaWallOfFleshServant.cs:140-145 — before extracting anything, compare `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBlades/KikasaBladeServant.cs` and `Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaBoomerangs/KikasaBoomerangServant.cs` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 423 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (11 lines × 14) · ×1
  • Duplicated block (11 lines × 14) Content/NPCs/ScrapCommanders/Projectiles/ScrapArmHitbox.cs:18 — Content/NPCs/ScrapCommanders/Projectiles/ScrapArmHitbox.cs:18-28 | Content/NPCs/ScrapCommanders/Projectiles/ScrapDebris.cs:29-39 | Content/NPCs/ScrapCommanders/Projectiles/ScrapFlungTool.cs:31-41 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpBubble.cs:41-52 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpCavitationBubble.cs:43-53 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpClawHitbox.cs:18-28 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpCrystalSpike.cs:36-46 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpGeyserSpout.cs:47-57 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpJetBeam.cs:65-75 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpSparkBubble.cs:78-88 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpSwarmBubble.cs:34-44 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpVoltBubble.cs:59-69 | Content/NPCs/SeaShrimp/Projectiles/SeaShrimpWaveCrest.cs:54-64 | Content/Scenarios/Dungeonworld/NPCs/GaolCuffHitbox.cs:17-27 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 14 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 14 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpWaveCrest.cs:66` calls `ShouldUpdatePosition` and `Content/NPCs/SeaShrimp/Projectiles/SeaShrimpCrystalSpike.cs:49` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (6 lines × 13) · ×1
  • Duplicated block (6 lines × 13) Content/Scenarios/Dungeonworld/NPCs/GaolDormantSkull.cs:48 — Content/Scenarios/Dungeonworld/NPCs/GaolDormantSkull.cs:48-53 | Content/Scenarios/Dungeonworld/NPCs/OverseerDormantRig.cs:69-74 | Content/Scenarios/Dungeonworld/NPCs/UndrownedThrone.cs:75-80 | Content/Scenarios/Kiyume/NPCs/KiyumeWhiteHound.cs:80-86 | Content/Scenarios/OldNet/NPCs/OldNetBlackICE.cs:46-51 | Content/Scenarios/OldNet/NPCs/OldNetLurkerICE.cs:45-50 | Content/Scenarios/OldNet/NPCs/OldNetPatrolICE.cs:41-46 | Content/Scenarios/OldNet/NPCs/OldNetSweepEye.cs:41-46 | Content/Scenarios/OldNet/NPCs/OldNetTaggerICE.cs:45-50 | Content/Scenarios/OldNet/NPCs/OldNetTracerICE.cs:51-56 | Content/Scenarios/OldNet/NPCs/OldNetTurretICE.cs:30-35 | Content/Scenarios/OldNet/NPCs/OldNetWardenICE.cs:122-127 | Content/Scenarios/Shepel/CybCourses/CybTrainingDummy.cs:34-39 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 13 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 13 times.
IC1 · Incompleteness & stubs · Condition was already decided · ×1
  • Condition was already decided — an earlier guard makes this test constant Content/Scenarios/OldDuke/Campsites/OldDuchestLootGenerator.cs:85 — Control only reaches here when `qualityDrops.Count == 0` is false, because the guard on line 79 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test.
P1 · CI/CD gates · No CI pipeline · ×1
  • No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
Minor — 70 finding(s)
X7 · Silent fallback defaults · Silent fallback default in catch · ×30
  • Silent fallback default in catch Common/RenderQualitySafety.cs:121 — `IsLowQualityValue` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Content/HackTimes/HackTimeNetSync.cs:1099 — `ReadSnapshot` swallows `EndOfStreamException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterRecipeId.cs:145 — `SatisfiesConditions` swallows every exception and sets `met = false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Content/Industrials/ElectricPowers/AutoCrafters/AutoCrafterUI.cs:336 — `RecipeConditionsMetLocal` swallows every exception and sets `met = false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Content/LegendWeapon/OnikiriLegend/OniBladeProfile.cs:64 — `SmearTexture` swallows every exception and sets `smearTex = null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Content/LegendWeapon/OnikiriLegend/OniDismembers/OniDismember.cs:852 — `EnsureSnapshotRT` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Content/LegendWeapon/OnikiriLegend/OniDismembers/OniPlayerDismember.cs:313 — `EnsureSnapshotRT` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBanish.Net.cs:233 — `WriteSnapshot` swallows `IOException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBanish.Net.cs:286 — `ReadSnapshot` swallows `EndOfStreamException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBossExecution.Net.cs:173 — `WriteSnapshot` swallows `IOException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Content/LegendWeapon/SHPCLegend/Cyberspaces/Banish/CyberBossExecution.Net.cs:211 — `ReadSnapshot` swallows `EndOfStreamException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.Net.cs:875 — `WriteSnapshot` swallows `IOException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Content/LegendWeapon/SHPCLegend/Cyberspaces/DomainFreeze/CyberDomainFreeze.Net.cs:943 — `ReadSnapshot` swallows `EndOfStreamException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Content/Scenarios/Himayo/HimayoPortraitAssemblyRenderer.cs:534 — `BuildPetals` swallows every exception and sets `pixels = null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Content/Scenarios/OldDuke/FirstMetOldDuke.cs:131 — `HasHalibut` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Content/Scenarios/Shenyo/ShenyoPortraitRainRenderer.cs:525 — `BuildDrops` swallows every exception and sets `pixels = null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Content/Scenarios/SupCal/FirstMetSupCal.cs:116 — `HasHalibut` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Content/Scenarios/SupCal/Quest/DoGQuest/SupCalDoGQuestReward.cs:66 — `HasHalibut` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Content/Scenarios/SupCal/Quest/PallbearerQuest/SupCalMoonLordReward.cs:63 — `HasHalibut` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Content/Scenarios/SupCal/Quest/PallbearerQuest/SupCalQuestReward.cs:64 — `HasHalibut` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Content/Scenarios/SupCal/Quest/YharonQuest/SupCalYharonQuestReward.cs:64 — `HasHalibut` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Content/Scenarios/SupCal/SupCalPlayerDefeat.cs:57 — `HasHalibut` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Content/Scenarios/SupCal/SupCalVictory.cs:66 — `HasHalibut` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Content/UIs/HudStack/BottomLeftHudStack.cs:85 — `Layout` swallows every exception and sets `wants = false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Content/UIs/RadialWheels/RadialWheelHub.cs:189 — `OpenEligible` swallows every exception and sets `eligible = false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • + 5 more in this group — see findings.md.
IC1 · Incompleteness & stubs · Commented-out code · ×27
  • Commented-out code CWRUtils.cs:52 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code CWRUtils.cs:58 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code CWRUtils.cs:453 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Content/Industrials/ElectricPowers/Turrets/CryoTurrets/CryoTurretTP.cs:147 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Content/Items/Melee/Cloudwalking.cs:119 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Content/Items/Melee/SpearOfLonginuses/PilgrimsFury.cs:137 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Content/Items/Melee/StormGoddessSpears/AncientStormGoddessSpear.cs:26 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaInkPour.cs:338 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:205 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Content/LegendWeapon/OnikiriLegend/OniAnnihilates/OniAnnihilate.cs:207 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismFlameStormState.cs:225 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismSoloRageState.cs:251 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Content/NPCs/BrutalNPCs/BrutalMechanicalEye/States/Spazmatism/SpazmatismSoloRageState.cs:253 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Content/PRTTypes/PRT_LonginusWave.cs:60 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Content/PRTTypes/PRT_LonginusWave.cs:62 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Content/Scenarios/Dungeonworld/Dungeonworld.cs:59 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Content/Scenarios/Dungeonworld/Dungeonworld.cs:114 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Content/Scenarios/Dungeonworld/Gen/Passes/GuideTrailPass.cs:200 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Content/Scenarios/Dungeonworld/Gen/VerticalLinks.cs:92 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Content/Scenarios/Hadalworld/Hadalworld.cs:94 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Content/Scenarios/Himayo/ToriiShrines/ToriiShrine.cs:237 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Content/Scenarios/Kiame/Overlay/OniRainWorldTransition.cs:447 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Content/UIs/OverhaulSettings/OverhaulSettingsButton.cs:23 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Content/UIs/OverhaulSettings/OverhaulSettingsButton.cs:24 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Content/UIs/OverhaulSettings/OverhaulSettingsButton.cs:25 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • + 2 more in this group — see findings.md.
D16 · Bus Factor · Off-boarding risk · ×2
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 370 significant file(s) lose their only recent owner: Content/LegendWeapon/OnikiriLegend/OnikiriPlayer.cs, Content/LegendWeapon/KikasaLegend/UI/Panorama/KikasaPanoramaUI.cs, Content/LegendWeapon/OnikiriLegend/CrimsonRendSlashs/CrimsonRendSlash.cs, Content/LegendWeapon/OnikiriLegend/OniSlashs/OniSlash.cs, Content/LegendWeapon/KikasaLegend/KikasaRains/KikasaRainUmbrella.cs, Content/LegendWeapon/KikasaLegend/KikasaDomains/KikasaDomainPlayer.cs, Content/LegendWeapon/KikasaLegend/KikasaServants/KikasaArms/KikasaGuns/KikasaGunServant.cs, Content/LegendWeapon/OnikiriLegend/UI/OniMeiRenderer.cs (+362 more). Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 151 significant file(s) lose their only recent owner: CWRRef.cs, Content/Items/Melee/Heartcarver.cs, Content/Cyberwares/UIs/CyberBodyRenderer.cs, Content/UIs/OverhaulSettings/OverhaulSettingsUI.cs, Content/Items/Melee/Arbiters/Arbiter.cs, Content/LegendWeapon/HalibutLegend/DomainSkills/SeaDomain.cs, Content/NPCs/BrutalNPCs/BrutalMechanicalEye/Rendering/TwinsRenderHelper.cs, Content/LegendWeapon/SHPCLegend/UI/SHPCCyberPanel.cs (+143 more). Pair on, review, or document these before any departure.
AX6 · Interface segregation · Fat interface · ×1
  • Fat interface: IQuestLogStyle (24 members) Content/QuestLogs/Core/IQuestLogStyle.cs:6 — `IQuestLogStyle` declares 24 members: `UpdateStyle`, `DrawBackground`, `DrawNode`, `DrawConnection`, `GetPadding`, `DrawQuestDetail`, `GetCloseButtonRect`, `GetRewardButtonRect`, `DrawProgressBar`, `GetClaimAllButtonRect`, `DrawClaimAllButton`, `GetResetViewButtonRect`, `DrawResetViewButton`, `GetStyleSwitchButtonRect`, `DrawStyleSwitchButton`, `GetNightModeButtonRect`, `DrawNightModeButton`, `DisplayName`, `SupportsNightMode`, `DrawsOwnChrome`, `DrawChrome`, `SyncLayout`, `DrawDetail`, `MeasureDetailHeight`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
C2 · Access Controls · Thin authorization enforcement · ×1
  • Thin authorization enforcement — Authorization machinery exists but no [Authorize] usage and no imperative guard calls were found at handlers.
IC1 · Incompleteness & stubs · Empty method body · ×1
  • Empty method body Content/Scenarios/Kiame/Overlay/OniRainWorldTransition.cs:445 — `StopOwnCutscene` has an empty body — confirm it's an intentional no-op and not an unfinished method.
M1 · Documentation (README) · Thin README · ×1
  • Thin README README.md:1 — The root README is 25 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, 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.
M2 · Architecture documentation · No ADRs · ×1
  • 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.
M3 · Folder & project structure · No src/ separation · ×1
  • No src/ separation — Most of the production code is in directories of its own, but 12 application file(s) sit at the repository root beside the build and tooling files (`CWRAsset.cs`, `CWRConstant.cs`, `CWRID.cs`, `CWRLoad.cs`, `CWRMod.cs` and 7 more).
M3 · Folder & project structure · No tests/ separation · ×1
  • No tests/ separation — Tests aren't grouped in a dedicated test folder — the test surface isn't separable from production code at a glance.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets — this tree has no MSBuild project file, so CodeQL's csharp pack (which traces a build) and NuGet security analyzers (which are referenced from a project) have nothing to attach to — 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.
X5 · Nullable reference types · Nullable reference types not enabled everywhere · ×1
  • Nullable reference types not enabled everywhere — 0/4735 C# file(s) are in a nullable-enabled context. This repository commits no project file, so nothing sets <Nullable>enable</Nullable> for it: a file is enabled only by its own `#nullable enable`, by a Unity `csc.rsp` with `-nullable:enable` for its assembly, or as a file-based app (`#:` directives) whose `#:property Nullable` does not turn it off. NRTs catch a whole class of null-deref bugs at compile time.
X7 · Silent fallback defaults · Silent fallback default on unknown code · ×1
  • Silent fallback default on unknown code Content/UIs/OverhaulSettings/WorldGenSettingsCategory.cs:58 — `GetDefaultDensity` maps every unrecognised code to `StructureDensity.Normal`, one of the real values, with no log or throw — a malformed or new code silently reads as a known one. Throw on the unknown code, or log it. If that member is the correct answer for any other code, say so in a comment on the member and the row stops firing.

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.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-5cc905c5ee0e454a9575a688252a881f/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=699" --report-format json --report-path /tmp/watchdog-gitleaks-5cc905c5ee0e454a9575a688252a881f/history-1.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-1.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=899 --max-count=1264" --report-format json --report-path /tmp/watchdog-gitleaks-5cc905c5ee0e454a9575a688252a881f/history-2.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-2.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=2163 --max-count=2315" --report-format json --report-path /tmp/watchdog-gitleaks-5cc905c5ee0e454a9575a688252a881f/history-3.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-3.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=4478 --max-count=1644" --report-format json --report-path /tmp/watchdog-gitleaks-5cc905c5ee0e454a9575a688252a881f/history-4.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-4.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-5cc905c5ee0e454a9575a688252a881f/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .0artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesnuget—nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan0—
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—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. semgrep could not parse 327 file(s) — `CWRLoad.cs`, `Content/CWRCrafted.cs`, `Content/Cyberwares/Implementation/SCCA32CRPs/SCCA32CRPPlayer.cs`, `Content/Cyberwares/Implementation/Sandevistans/SandevistanPlayer.cs`, `Content/Cyberwares/Implementation/SelfHackCrystals/SelfHackCrystalPlayer.cs`, … (+322 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D36 · Supply-chain Provenance & Signingprovenance—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.0—
D37 · Vulnerability-disclosure Policydisclosure—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.0—
D40 · Network Egress Confinementruntime-hardening—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.0—
D41 · Kernel & Syscall Confinementruntime-hardening—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.0—
D42 · Runtime Threat Enforcementruntime-hardening—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.0—
D43 · Malicious Dependenciesnone (no readable dependency manifest)—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 01a1e64f-d4ae-7eb9-99ce-4e0aa8e8ac0b · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

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.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md