Public report of AetherRadar/operation-steel-tide, published 17 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, 17 November 2026, 03:27 UTC · Survey ID cd_25c0a9e8ae824cfabc56a1229456210e

AetherRadar/operation-steel-tide

Measured 17 November 2026, 03:25 UTC, at code version d6a33b9

First survey, so nothing to compare with yet Supply-chain provenance & signing: not measured

Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.

CAI score 60.3out of 100 Adequate
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 large codebase: 227,299 lines of product code in 1 project, tests not counted · Estimated rebuild effort: about 13.9 person-years · Weakest lens: Code Health, 52.5

Findings by how serious they are

14 critical 1868 serious 58 minor

5 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
17 November 2026, 03:25 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 ▸

57of 57 dimensions measured by tools.
1934of 1940 findings point to an exact file and line, so you can open each one in the code. The other 6 concern the repository as a whole, such as missing documentation.
57dimensions across 6 lenses, read from 227,299 lines of product code in 1 project.
Chapters

Executive summary

AetherRadar/operation-steel-tide falls short of our standard for production, held back most by its Code Health lens, the quality of the code itself. It scores 60.3 out of 100 and is rated Adequate, and three of its 14 critical findings are security problems.

Code Health, at 52.5, is the weakest lens and counts most in the score. The best first step is handling the discarded errors, worth about 5.4 points. Fixing the asynchronous event handlers comes next, worth about 4.5 points. Raising Code Health to 70 would lift the score to about 65.3.

Two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Six errors are caught and ignored, so failures can go unnoticed, and five sets of files in separate parts keep changing together, which points to hidden dependencies. Pinning each tool to an exact version, handling or logging the ignored errors and making the hidden dependencies explicit would close these risks. The check for vulnerable packages switched off needs switching back on.

The product code is 227,299 lines, about €2,000,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.
Code Health 52.5 · counts for 46%Architecture 56.5 · counts for 25%Production Readiness 67.9 · counts for 14%Maturity 74.3 · counts for 8%Security and Compliance 95.0 · counts for 4%Performance 100.0 · counts for 2%

If Code Health rose from 52.5 to 70, the lowest score rated Strong, the score would rise from 60.3 to about 65.3.

Code composition: what the lines of code are
Business logic 70%Supporting code 30%Tests 0%
Rebuild cost: about €2,000,000 · Estimate
Cost to rebuild€650,000 to €3,400,000, for 10,876 to 35,836 hours of work, about 13.9 person-years for 8 to 27 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.8 at a score of 60. 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.
SizeLarge: 227,299 lines of product code
Comment linesThe estimate prices 223,925 lines. Comment lines count towards the size of 227,299 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
Resolve the 6 EmptyCatchBlock finding(s) in Explicit Debt — start with CombatModelLibrary.PreviewDiagnostics.cs (3), ResidentialAuthoredPropLibrary.cs (2), ZombieNpc.cs.
Raises the score by about 5.4 points · Low effort · Explicit Debt
2
async void method: _Ready
Raises the score by about 4.5 points · Medium effort · Async correctness
3
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.
Raises the score by about 4.1 points · Medium effort · Stateful singletons

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,000,000 to build again, about 13.9 person-years of work. Its weakest lens is Code Health, at 52.5 (Adequate). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Resolve the 6 EmptyCatchBlock finding(s) in Explicit Debt. Of all the actions in this report, it raises the score most for the work it takes: about 5.4 points for low effort, because it clears the 6 Explicit Debt findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 4.8 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 8% to 18% on every change. The history of the code shows how much it changes: about 329,220 lines over the last 90 days, which is about 1,335,170 lines a year. At that pace, the extra work comes to an estimated 264.4 to 1586.6 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: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

21 modules, with 13 dependencies between them. Every module uses only modules listed above it, so there are no loops.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 OperationSteelTide2 operation-steel-tide/backend/cmd/server3 operation-steel-tide/backend/internal/game4 scripts.audio5 scripts.blender.build_animated_reload_arms6 scripts.blender.build_authored_optics7 scripts.blender.build_bazaar_crossing8 scripts.blender.build_melee_weapons9 scripts.blender.build_operations_office_set10 scripts.blender.build_orbital_complex11 scripts.blender.build_quaternius_buildings_pack12 scripts.blender.build_reloadable_quaternius_weapons13 scripts.blender.build_supplemental_reload_mechanisms14 scripts.blender.build_tideglass_map_assets15 scripts.blender.build_trey_modular_industrial16 scripts.blender.jianghai_density_color017 scripts.blender.jianghai_enterable_interior_liners18 scripts.blender.jianghai_enterable_residences19 source_art.third_party.quaternius_buildings_pack20 tools21 scripts.blender
1 OperationSteelTide
2 operation-steel-tide/backend/cmd/server
3 operation-steel-tide/backend/internal/game
4 scripts.audio
5 scripts.blender.build_animated_reload_arms
6 scripts.blender.build_authored_optics
7 scripts.blender.build_bazaar_crossing
8 scripts.blender.build_melee_weapons
9 scripts.blender.build_operations_office_set
10 scripts.blender.build_orbital_complex
11 scripts.blender.build_quaternius_buildings_pack
12 scripts.blender.build_reloadable_quaternius_weapons
13 scripts.blender.build_supplemental_reload_mechanisms
14 scripts.blender.build_tideglass_map_assets
15 scripts.blender.build_trey_modular_industrial
16 scripts.blender.jianghai_density_color0
17 scripts.blender.jianghai_enterable_interior_liners
18 scripts.blender.jianghai_enterable_residences
19 source_art.third_party.quaternius_buildings_pack
20 tools
21 scripts.blender4221224112211
Uses a module listed above itPart of a loopThe module itself
1 OperationSteelTide2 operation-steel-tide/backend/cmd/server3 operation-steel-tide/backend/internal/game4 scripts.audio5 scripts.blender.build_animated_reload_arms6 scripts.blender.build_authored_optics7 scripts.blender.build_bazaar_crossing8 scripts.blender.build_melee_weapons9 scripts.blender.build_operations_office_set10 scripts.blender.build_orbital_complex11 scripts.blender.build_quaternius_buildings_pack12 scripts.blender.build_reloadable_quaternius_weapons13 scripts.blender.build_supplemental_reload_mechanisms14 scripts.blender.build_tideglass_map_assets15 scripts.blender.build_trey_modular_industrial16 scripts.blender.jianghai_density_color017 scripts.blender.jianghai_enterable_interior_liners18 scripts.blender.jianghai_enterable_residences19 source_art.third_party.quaternius_buildings_pack20 tools21 scripts.blenderOperationSteelTide1operation-steel-tide/backend/cmd/server2operation-steel-tide/backend/internal/game3scripts.audio4scripts.blender.build_animated_reload_arms5scripts.blender.build_authored_optics6scripts.blender.build_bazaar_crossing7scripts.blender.build_melee_weapons8scripts.blender.build_operations_office_set9scripts.blender.build_orbital_complex10scripts.blender.build_quaternius_buildings_pack11scripts.blender.build_reloadable_quaternius_weapons12scripts.blender.build_supplemental_reload_mechanisms13scripts.blender.build_tideglass_map_assets14scripts.blender.build_trey_modular_industrial15scripts.blender.jianghai_density_color016scripts.blender.jianghai_enterable_interior_liners17scripts.blender.jianghai_enterable_residences18source_art.third_party.quaternius_buildings_pack19tools20scripts.blender214221224112211

At a glance — Code Health · 52.5 · Adequate · gated by D1, D2, X1 ·

At a glance — Architecture · 56.5 · Adequate · gated by AX2, AX5 ·

At a glance — Maturity · 74.3 · Strong ·

At a glance — Readiness · 67.9 · Adequate · gated by P3 ·

At a glance — Security · 95.0 · Exemplary ·

At a glance — Performance · 100.0 · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A05:2025 — Injection3High / Critical
A01:2025 — Broken Access Control1Medium

Roadmap

Top priorities: Resolve the 6 EmptyCatchBlock finding(s) in Explicit Debt — start with CombatModelLibrary.PreviewDiagnostics.cs (3), ResidentialAuthoredPropLibrary.cs (2), ZombieNpc.cs; async void method: _Ready; 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.

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

Do thisHelpsEffortDimension
Resolve the 6 EmptyCatchBlock finding(s) in Explicit Debt — start with CombatModelLibrary.PreviewDiagnostics.cs (3), ResidentialAuthoredPropLibrary.cs (2), ZombieNpc.cs.+5.4 ptsLowExplicit Debt
async void method: _Ready+4.5 ptsMediumAsync correctness
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.+4.1 ptsMediumStateful singletons
Resolve the 5 Boundary-crossing change coupling finding(s) in Change Coupling — start with FreightTerminalWorld.CombatModels.cs (2), CombatModelLibrary.cs, CombatModelLibrary.FirstPerson.cs.+1.0 ptsLowChange Coupling
Introduce deliberate module boundaries — by feature (vertical slices) if your team prefers, or by layer (domain/application/infrastructure). Even splitting into a few cohesive projects with a clear dependency direction would help.+3.5 ptsMediumArchitecture & structure
Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.+2.5 ptsMediumSecurity & performance tooling
Resolve the 146 MethodTooLong finding(s) in God Classes — start with FreightTerminalWorld.cs (10), FreightTerminalWorld.Demolition.Diagnostics.cs (6), FreightTerminalWorld.Residential.cs (5).+2.2 ptsHighGod Classes
Thread a CancellationToken through async methods so work stops promptly on cancellation.+2.1 ptsMediumCancellation propagation

File quality

Per-file score 0–10 — a quality signature. Of 338 files carrying findings, judged against the Production bar: 1% slop · 72% mixed · 27% near-clean.

FileScoreBandWorst signal
csharp/TacticalPlayer.AuthoredVisuals.cs1.9SlopChange Coupling: Boundary-crossing change coupling: TacticalPlayer.AuthoredVisuals.cs ↔ build_djmaesen_smg45.py
csharp/CombatModelLibrary.cs1.9SlopChange Coupling: Boundary-crossing change coupling: CombatModelLibrary.cs ↔ build_animated_bamen_operator.py
csharp/FreightTerminalWorld.CombatModels.cs4.0MixedChange Coupling: Boundary-crossing change coupling: FreightTerminalWorld.CombatModels.cs ↔ build_animated_bamen_operator.py
csharp/ResidentialAuthoredPropLibrary.cs4.2MixedExplicit Debt: EmptyCatchBlock
csharp/CombatModelLibrary.PreviewDiagnostics.cs4.3MixedExplicit Debt: EmptyCatchBlock
REDACTED4.9MixedData Compliance (PII/GDPR): Medium: REDACTED
csharp/CombatModelLibrary.FirstPerson.cs5.1MixedChange Coupling: Boundary-crossing change coupling: CombatModelLibrary.FirstPerson.cs ↔ build_djmaesen_smg45.py
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
csharp/LootDragControls.cs5.9MixedCognitive Complexity: LootDragCard.Configure (cognitive 23)
csharp/FreightTerminalWorld.Melee.Diagnostics.cs6.0MixedExplicit Debt: Dead code: WaitForMeleeAttack
csharp/TacticalPlayer.ReloadPresentation.ViewDiagnostics.cs6.0MixedExplicit Debt: Dead code: InspectAuthoredPlatformReloadForDiagnostics
csharp/FreightTerminalWorld.TrainingRange.cs6.0MixedExplicit Debt: Dead code: ReviveTrainingRangeBot
csharp/FreightTerminalWorld.SurvivalZombies.cs6.0MixedExplicit Debt: Dead code: HandleSurvivalHits
csharp/TacticalPlayer.AnimatedReloadArms.cs6.0MixedExplicit Debt: Dead code: InspectAnimatedReloadLeftArmPoseForDiagnostics
REDACTED6.4MixedStatic Analysis (SAST): Medium: REDACTED
csharp/FreightTerminalWorld.Squad.cs7.0MixedCyclomatic Complexity: FreightTerminalWorld.ValidateSquadFlow (cyclomatic 390)
csharp/FreightTerminalWorld.Demolition.Diagnostics.cs7.0MixedCyclomatic Complexity: FreightTerminalWorld.ValidateDemolitionTacticalAi (cyclomatic 301)
csharp/FreightTerminalWorld.Residential.cs7.0MixedCyclomatic Complexity: FreightTerminalWorld.ValidateResidentialGameplay (cyclomatic 186)
csharp/FreightTerminalWorld.cs7.0MixedCyclomatic Complexity: FreightTerminalWorld.ValidateLootFlow (cyclomatic 178)
csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Diagnostics.cs7.0MixedCyclomatic Complexity: FreightTerminalWorld.ValidateOrbitalComplexIntegration (cyclomatic 95)

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

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

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

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

Could not be resolved — 5

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 57 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, 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 — 57 dimensions across the health lenses
D1D2D3D4D5D6D11D12D13D15D17D18D19D21D24D26D27D29D30D32D34D35D43D44AX10AX2AX3AX4AX5AX6GD1IC1M1M2M3M4P1P3P6P7PF3X1X12X14X15X16X18X2X20X21X25X27X28X29X3X30X5

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, 1934 of 1940 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 01a1e78a-1fc2-7cc6-8cc6-193b1dbab15c.

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: test source is present (.go) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
  • 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.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (2 contributor(s) across 578 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 1 hold 1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
  • D17 Explicit Debt — measured, with a gap in what it reached — 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. The 8 deducted marker(s) and the 0.1/KLoC density on this row were taken over this repository's .NET projects ALONE: .py (55,686 lines, 25% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
  • D19 Documentation Quality — 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. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
  • D19 Documentation Quality — 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. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — 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. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
  • D21 Naming Consistency — 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D21 Naming Consistency — 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
  • D24 Comment Value — 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
  • D27 Navigability — 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. Tracing effort is measured over resolved call sites, and all 2525 sampled here came from .cs files. This repository's .py source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
  • D28 Secrets (history) — 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. `gitleaks` TIMED OUT after 75.1s against a 75s budget, so we killed its process tree. The budget is ours; the work may simply be larger than it allows. Nothing about this repository is asserted by the absence of a result; the budget is ours to raise, and raising it is our backlog item, not an action for this repository's owner.
  • D32 Data Compliance (PII/GDPR) — 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. `csharp/CombatModelLibrary.cs` 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.
  • IC1 Incompleteness & stubs — 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • M4 Documentation accuracy — 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. M4 reads a prose claim (a path, a setting, a variable, a route, a version, a project, an install, a bare project name in a command) only in text identified as English: the cues that tell a claim from an absence, the past, a plan or an example are an English lexicon, and on other text they would let a false claim through. Links, image targets, fenced commands with an explicit path or a package-manager script, and env-fence variables are checked in every language. 'und' is text the identifier could not name (too short, mixed script, no function words).
  • M4 Documentation accuracy — 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • P1 CI/CD gates — 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. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
  • X1 Async correctness — 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X1 Async correctness — 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. 155 further occurrence(s) are not listed individually; the score already reflects all 195.
  • 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. 130 further occurrence(s) are not listed individually; the score already reflects all 170.
  • X12 Unreachable branch — 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X14 Bypassable address classification — 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X15 Unvalidated length from an untrusted reader — 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X16 Unfloored truncation loop — 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X18 Disposal-pattern correctness — 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X18 Disposal-pattern correctness — 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. 3 further occurrence(s) are not listed individually; the score already reflects all 43.
  • X2 Cancellation propagation — 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X21 Side-effecting pattern guard — 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X25 Inert configuration knob — 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X27 Collection changed while being enumerated — 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X28 Index access outside its own emptiness guard — 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X29 Per-element action decided by a fixed element — 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X30 Support guard that admits what it rejects — 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.

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.
  • D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • 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").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
  • 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.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • 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.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity2.0 / 10Critical✓ 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 2.0 / 10 · rule-coverage 100% · ceiling Prevented

297 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was FreightTerminalWorld.ValidateSquadFlow at 390. A further 78 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 FreightTerminalWorld.ValidateRefineryMap at 149 — they are counted neither in the figure above nor in this dimension's score. 34 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: csharp/FreightTerminalWorld.Refinery.Validation.cs (FreightTerminalWorld.ValidateRefineryMap at 149), csharp/FreightTerminalWorld.Demolition.Buy.Diagnostics.cs (FreightTerminalWorld.ValidateDemolitionBuy at 86), csharp/FreightTerminalWorld.FieldUseLifecycle.Diagnostics.cs (FreightTerminalWorld.ValidateFieldUseLifecycle at 75), csharp/FreightTerminalWorld.Economy.cs (FreightTerminalWorld.ValidateDeploymentUi at 71), csharp/FreightTerminalWorld.OperationsOffice.cs (FreightTerminalWorld.ValidateOperationsOffice at 61), and 29 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.

FreightTerminalWorld.ValidateSquadFlow (cyclomatic 390)csharp/FreightTerminalWorld.Squad.cs:3137
FreightTerminalWorld.ValidateDemolitionTacticalAi (cyclomatic 301)csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:865
FreightTerminalWorld.ValidateDemolitionMode (cyclomatic 222)csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:495
FreightTerminalWorld.ValidateDemolitionNetworkSession (cyclomatic 187)csharp/FreightTerminalWorld.Demolition.Network.Diagnostics.cs:83
FreightTerminalWorld.ValidateResidentialGameplay (cyclomatic 186)csharp/FreightTerminalWorld.Residential.cs:1778

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

What to do

  1. Bring the 2 bodies over 240 down to 240 or less in Cyclomatic Complexity — start with FreightTerminalWorld.ValidateSquadFlow (cyclomatic 390), FreightTerminalWorld.ValidateDemolitionTacticalAi (cyclomatic 301). — 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 2 together lifts Cyclomatic Complexity from 2.0 to about 2.5/10, projected with the scoring formula itself and assuming each lands exactly at 240; a cleaner split scores higher.

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

D2 · Cognitive Complexity2.0 / 10Critical✓ 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 2.0 / 10 · rule-coverage 100% · ceiling Prevented

318 method(s) exceeded the cognitive complexity threshold of 15; the worst was FreightTerminalWorld.ValidateSquadFlow at 282.

FreightTerminalWorld.ValidateSquadFlow (cognitive 282)csharp/FreightTerminalWorld.Squad.cs:3137
FreightTerminalWorld.ValidateDemolitionTacticalAi (cognitive 182)csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:865
FreightTerminalWorld.ValidateResidentialGameplay (cognitive 172)csharp/FreightTerminalWorld.Residential.cs:1778
FreightTerminalWorld.ValidateDemolitionNetworkSession (cognitive 139)csharp/FreightTerminalWorld.Demolition.Network.Diagnostics.cs:83
FreightTerminalWorld.ValidateStairsClimb (cognitive 126)csharp/FreightTerminalWorld.cs:6031

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

What to do

  1. Bring the 5 bodies over 120 down to 120 or less in Cognitive Complexity — start with FreightTerminalWorld.ValidateSquadFlow (cognitive 282), FreightTerminalWorld.ValidateDemolitionTacticalAi (cognitive 182), FreightTerminalWorld.ValidateResidentialGameplay (cognitive 172). — 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 5 together lifts Cognitive Complexity from 2.0 to about 3.6/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 Classes5.9 / 10Adequate✓ 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 5.9 / 10 · rule-coverage 100% · ceiling Prevented

225 god class(es) detected.

MethodTooLong: FreightTerminalWorld.ValidateDemolitionTacticalAi · ×146csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:865
FileTooLong: csharp/FreightTerminalWorld.cs · ×51csharp/FreightTerminalWorld.cs
TooManyMethods: FreightTerminalWorld · ×19csharp/FreightTerminalWorld.cs
ClassTooLong: GameLocalization · ×9csharp/GameLocalization.cs

What to do

  1. Resolve the 146 MethodTooLong finding(s) in God Classes — start with FreightTerminalWorld.cs (10), FreightTerminalWorld.Demolition.Diagnostics.cs (6), FreightTerminalWorld.Residential.cs (5). — One of this dimension's main actionable groups (146 warning-level).
  2. Resolve the 51 FileTooLong finding(s) in God Classes — start with FreightTerminalWorld.cs, FreightTerminalWorld.Squad.cs, FreightTerminalWorld.Demolition.Diagnostics.cs. — One of this dimension's main actionable groups (51 warning-level).
  3. Resolve the 19 TooManyMethods finding(s) in God Classes — start with FreightTerminalWorld.cs, TacticalPlayer.cs, CombatHUD.cs. — One of this dimension's main actionable groups (19 warning-level).

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

D4 · Code Duplication5.4 / 10Adequate✓ 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 5.4 / 10 · rule-coverage 100% · ceiling Verified

537 duplicated block group(s) detected. 11.4 % of the production lines (19,430 of 170,714) are in a reported copy. A further 256 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 371 of the 793 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.

Duplicated block (5 lines × 2) · ×46csharp/JianghaiEnterableCollisionShellBuilder.cs:107
Duplicated block (8 lines × 2) · ×40csharp/TacticalPlayer.AuthoredVisuals.cs:1329
Duplicated block (6 lines × 2) · ×35csharp/FreightTerminalWorld.ResidentialStairs.Diagnostics.cs:50
Duplicated block (7 lines × 2) · ×33csharp/FreightTerminalWorld.AiNavigation.Diagnostics.cs:71
Duplicated block (10 lines × 2) · ×28csharp/FragGrenade.cs:90

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

What to do

  1. Resolve the 46 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with DemolitionArenaLayout.cs (5), build_melee_weapons.py (3), JianghaiEnterableCollisionShellBuilder.cs (2). — One of this dimension's main actionable groups (46 warning-level).
  2. Resolve the 40 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with JianghaiEnterableCollisionShellBuilder.cs (4), FreightTerminalWorld.Refinery.NavigationValidation.cs (2), DemolitionArenaLayout.cs (2). — One of this dimension's main actionable groups (40 warning-level).
  3. Resolve the 35 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with build_bazaar_crossing.py (3), build_orbital_complex.py (3), build_tideglass_map_assets.py (2). — One of this dimension's main actionable groups (35 warning-level).

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

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

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

1 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D6 · Cohesion (LCOM4)9.9 / 10Stronggated by 1 serious finding✓ 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 9.9 / 10 · rule-coverage 100% · ceiling Verified

1 of 98 classes have LCOM4 above 3.

Low cohesion: TrainingRangeArenaRuntime (LCOM4 4)csharp/TrainingRangeArenaRuntime.cs:13

What to do

  1. Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with TrainingRangeArenaRuntime.cs. — One of this dimension's main actionable groups (1 warning-level).

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

D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the tests pass reliably, with no flakiness.

Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.

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

0 flaky across 1 measured tier(s). Go (operation-steel-tide/backend): measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

D12 · Dependency Hygiene10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.

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

0 outdated, 0 vulnerable, 0 deprecated packages.

✓ On the Gold path — maintain.

Detailed fixes: d12_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 Hotspots6.3 / 10Adequate✓ 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 6.3 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: csharp/FreightTerminalWorld.Squad.cs (76×390=29640); csharp/FreightTerminalWorld.cs (150×178=26700); csharp/FreightTerminalWorld.Demolition.Diagnostics.cs (37×301=11137)

Hotspot: csharp/FreightTerminalWorld.Squad.cs · ×93csharp/FreightTerminalWorld.Squad.cs:3137

What to do

  1. Resolve the 93 Hotspot finding(s) in Churn × Complexity Hotspots — start with FreightTerminalWorld.Squad.cs, FreightTerminalWorld.cs, FreightTerminalWorld.Demolition.Diagnostics.cs. — One of this dimension's main actionable groups (93 warning-level).

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

D17 · Explicit Debt9.9 / 10Adequategated by 6 critical findings✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

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

8 deducted debt markers + 15 dead symbols across 170714 LoC in the .NET projects (0.1/KLoC) → score 9.9. Measured on the .NET source only: .py (25% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).

EmptyCatchBlock · ×6csharp/CombatModelLibrary.PreviewDiagnostics.cs:39
Dead code: RemoveStagingNode · ×15csharp/CombatModelLibrary.cs:2596
BarePragmaDisable · ×2csharp/CombatModelLibrary.cs:635

What to do

  1. Resolve the 6 EmptyCatchBlock finding(s) in Explicit Debt — start with CombatModelLibrary.PreviewDiagnostics.cs (3), ResidentialAuthoredPropLibrary.cs (2), ZombieNpc.cs. — One of this dimension's main actionable groups (6 issue-level).
  2. Resolve the 15 Dead code finding(s) in Explicit Debt — start with TacticalPlayer.AuthoredVisuals.cs (3), TacticalPlayer.AnimatedReloadArms.cs (2), TacticalPlayer.ReloadPresentation.ViewDiagnostics.cs (2). — One of this dimension's main actionable groups (15 warning-level).
  3. Resolve the 2 BarePragmaDisable finding(s) in Explicit Debt — start with CombatModelLibrary.cs (2). — One of this dimension's main actionable groups (2 warning-level).

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

D18 · Solution Shape10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the solution is laid out in a sensible, conventional structure.

Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.

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

1 projects, 519 source files, 170714 hand-written lines of code (170714 production / 0 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), 0 inter-project edges.

✓ On the Gold path — maintain.

Detailed fixes: d18_recommendation.md.

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

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

1 of 1 documentation facets pass in full. 40 document(s) read across 1 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D21 · Naming Consistency8.7 / 10Strong✓ Tool-verified

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.

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

1 naming inconsistencies among 75 declarations measured against a convention their peers follow.

`CombatHUD` spells `HUD` where 74 names in the project spell it `Hud`csharp/CombatHUD.Boss.cs:5

What to do

  1. Resolve the 1 `CombatHUD` spells `HUD` where 74 names in the project spell it `Hud` finding(s) in Naming Consistency — start with CombatHUD.Boss.cs. — One of this dimension's main actionable groups (1 recommendation-level).

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

D24 · Comment Value10.0 9.7 / 10Exemplary○ Nothing flagged

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 9.7 / 10 · rule-coverage 97% · ceiling Documented

0 of 841 judged comments only repeat the code they sit on (0.0 %). 28 comment(s) in another language or script were not judged.

✓ On the Gold path — maintain.

Detailed fixes: d24_recommendation.md.

D26 · Project Cohesion10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic.

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

One project, `OperationSteelTide` (170714 LoC, 370 public types across 1 namespaces): over its size bounds, but its parts reference each other, so it reads as one coherent unit.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

D27 · Navigability10.0 / 10Exemplary✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

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

65 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality expected. Measured over the .cs source only — this repository's .py was not sampled for call sites, so this score covers part of the tree, not all of it.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

D29 · Static Analysis (SAST)9.5 / 10Adequategated by 2 critical findings✓ Tool-verified

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 9.5 / 10 · rule-coverage 100% · ceiling Documented

3 finding(s): 0 critical, 2 high, 1 medium, 0 low. 2 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 16 file(s) — `assets/models/quaternius_ultimate_guns/ak74.glb`, `assets/models/quaternius_ultimate_guns/awm.glb`, `assets/models/quaternius_ultimate_guns/axmc.glb`, `assets/models/quaternius_ultimate_guns/m1911.glb`, `assets/models/quaternius_ultimate_guns/m24.glb`, … (+11 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.

REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
  2. No action in Static Analysis (SAST) — all 2 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (2 issue-level, 0 of them charged here).

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

D30 · Dependency Vulnerabilities10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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

No known-vulnerable dependencies in any ecosystem this repository declares.

✓ On the Gold path — maintain.

Detailed fixes: d30_recommendation.md.

D32 · Data Compliance (PII/GDPR)9.0 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.

Method: Heuristic PII/GDPR LEAK scan via semgrep across the repo, using our own ruleset: personal data crossing a boundary it should not — reaching a log/console sink, a URL or query string, or unprotected browser storage. Matches map to severity and a 0-10 wide normalizer. A clean sweep is unscored rather than an unearned 10, and is a statement about the leak paths checked only — this dimension does not inventory the personal data a repository holds (the personal-data map and the C1-C5 compliance cards do that), so it never reports that a repository has no personal-data surface. Reported LOUDLY as a measurement gap if the ruleset is missing from the analyzer image. Exhaustive over the leak paths, advisory-leaning; degrades on parse failure.

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

1 finding(s): 0 critical, 0 high, 1 medium, 0 low. semgrep could not parse 1 file(s) — `csharp/CombatModelLibrary.cs` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.

REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d32_recommendation.md · top locations in Appendix A, every location in findings.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 462 of the 519 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 Coupling9.8 / 10Adequategated by 5 critical findings✓ 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 9.8 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: FreightTerminalWorld.CombatModels.cs↔build_animated_bamen_operator.py 82%; CombatModelLibrary.cs↔build_animated_bamen_operator.py 64%; CombatModelLibrary.FirstPerson.cs↔build_djmaesen_smg45.py 55%

Boundary-crossing change coupling: FreightTerminalWorld.CombatModels.cs ↔ build_animated_bamen_operator.py · ×5csharp/FreightTerminalWorld.CombatModels.cs:1
Change coupling: LootDragControls.cs ↔ TacticalPlayer.cs · ×2csharp/LootDragControls.cs:1

What to do

  1. Resolve the 5 Boundary-crossing change coupling finding(s) in Change Coupling — start with FreightTerminalWorld.CombatModels.cs (2), CombatModelLibrary.cs, CombatModelLibrary.FirstPerson.cs. — One of this dimension's main actionable groups (5 issue-level).
  2. Resolve the 2 Change coupling finding(s) in Change Coupling — start with LootDragControls.cs, DeploymentMapRuntime.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.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

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

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.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.

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.

  • `BreakableGlassField` 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 (_unitBox, _unitPane, _glassBreakSound; e.g. `_unitBox` at line 22). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — csharp/BreakableGlassField.cs:10
  • `DeploymentMapRuntime` 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 (_selectedWorldSeed, _pendingDeployment, _selectedMapId; e.g. `_selectedWorldSeed` at line 94). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — csharp/DeploymentMapRuntime.cs:18
  • `EnemyOperator` 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 (SharedBoxMeshes, SharedCapsuleMeshes, SharedCylinderMeshes; e.g. `SharedBoxMeshes` at line 357). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — csharp/EnemyOperator.AirborneCombat.cs:17
  • `FreightTerminalWorld` 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 (_extractionNetworkDiagnosticRuntimeId, _extractionNetworkDiagnosticLobbyWaited, _extractionNetworkDiagnosticMutationApplied, _extractionNetworkDiagnosticTombstoneGuarded, _extractionNetworkDiagnosticDownMotionGuarded, _extractionNetworkDiagnosticDownPeerId; e.g. `_extractionNetworkDiagnosticRuntimeId` at line 35). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Diagnostics.cs:10
  • `JianghaiLoadingDiagnosticRuntime` 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 (PreloadWaitMilliseconds, PreloadSnapshot, ReloadStartedAtMilliseconds, ReloadPending; e.g. `PreloadWaitMilliseconds` at line 19). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — csharp/FreightTerminalWorld.Refinery.LoadingDiagnostics.cs:8
  • `GeneratedInventoryArt` 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 (TextureCache, ImageCache, RegionCache; e.g. `TextureCache` at line 68). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — csharp/GeneratedInventoryArt.cs:11
  • `HudPackedSceneCache` 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 (Scenes; e.g. `Scenes` at line 31). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — csharp/HudPackedSceneCache.cs:13
  • `InventoryModelPreview` 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 (_operatorSky, _compactSky; e.g. `_operatorSky` at line 168). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — csharp/InventoryModelPreview.cs:16
  • `JianghaiMapPreloadCache` 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 (_releaseWhenLoaded, _packedScene, _error, _progress, _pollCount, _lastElapsedMilliseconds; e.g. `_releaseWhenLoaded` at line 65). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — csharp/JianghaiMapPreloadCache.cs:33
  • `LanternCanalPreloadCache` 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 (Requested, Ready, YieldedFrames, LoadMilliseconds; e.g. `Requested` at line 28). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — csharp/LanternCanalPreloadCache.cs:10
  • `LootBackpackVisual` 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 (SharedBoxMeshes; e.g. `SharedBoxMeshes` at line 127). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — csharp/LootBackpackVisual.cs:7
  • `ResidentialAuthoredPropLibrary` 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 (Scenes, FailedScenePaths; e.g. `Scenes` at line 189). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — csharp/ResidentialAuthoredPropLibrary.cs:11
  • `ResidentialRelayStation` 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 (SharedBoxes; e.g. `SharedBoxes` at line 26). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — csharp/ResidentialRelayStation.cs:19
  • `ResidentialSearchableFurniture` 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 (SharedBoxMeshes; e.g. `SharedBoxMeshes` at line 22). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — csharp/ResidentialSearchableFurniture.cs:15
  • `ResidentialSupplyCache` 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 (SharedFallbackMeshes, _sharedChestScene, _sharedClosedMesh, _sharedOpenedMesh, _sharedOpenAnimationMeshes, _sharedVisiblePartCount; e.g. `SharedFallbackMeshes` at line 79). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — csharp/ResidentialSupplyCache.cs:18
  • `SoundLab` 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 (WeaponShotCache, MeleeSwingCache, MeleeSurfaceImpactCache, _openingCombatTheme; e.g. `WeaponShotCache` at line 105). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — csharp/SoundLab.cs:6
  • `TacticalSurfaceLibrary` 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 (_fabricWeaveTexture, _weaponFinishTexture; e.g. `_fabricWeaveTexture` at line 62). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — csharp/TacticalSurfaceLibrary.cs:5

What to do

  • 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 cycles10.0 / 10Exemplary✓ 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.

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.

AX5 · Architecture & structure3.0 / 10Weak✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

  • ~170.7k production LoC (1032 types) across 1 project(s) / 22 namespace(s) with no recognised architectural style or layering — at this size, deliberate module boundaries would help. No DDD/clean/vertical-slice/CQRS/transaction-script organisation was detected — code is likely organised ad hoc, which makes change and onboarding harder as it grows.

What to do

  • Introduce deliberate module boundaries — by feature (vertical slices) if your team prefers, or by layer (domain/application/infrastructure). Even splitting into a few cohesive projects with a clear dependency direction would help.
AX6 · Interface segregation10.0 / 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.

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 & stubs8.0 / 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.

  • Control only reaches here when `budget.IsExhausted` is false, because the guard on line 504 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test. — csharp/FreightTerminalWorld.Squad.NavGrid.cs:522
  • Control only reaches here when `budget is not null && !budget.CanProbe` is false, because the guard on line 991 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test. — csharp/FreightTerminalWorld.Squad.Navigation.cs:1013
  • Control only reaches here when `budget.CanProbe` is true, because the guard on line 307 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test. — csharp/FreightTerminalWorld.Squad.Traversal.Connectors.cs:329
  • Control only reaches here when `budget.IsExhausted` is false, because the guard on line 501 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test. — csharp/FreightTerminalWorld.Squad.Traversal.cs:509

What to do

  • Remove the dead code that looks live: delete dead if(false) / #if false branches, which read as logic that runs, and either do the real async work or drop the async keyword from fake-async methods, which promise work they never wait for.
M1 · Documentation (README)9.3 / 10Exemplary✓ 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.

What to do

  • 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 documentation5.0 / 10Adequate✓ 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.

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.
M3 · Folder & project structure8.0 / 10Strong✓ 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.

  • Tests aren't where this ecosystem separates them — a `_test.go` file beside the code it tests is the convention, and none is present.
M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

P1 · CI/CD gates8.5 / 10Strong✓ 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.

What to do

  • Run the test suite in CI via an explicit runner step (`dotnet test` for the toolchain this pipeline already uses) and gate merges on it.
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.

  • <NuGetAudit>false</NuGetAudit> in MSBuild suppresses NuGet's vulnerability audit project-wide. — OperationSteelTide.csproj:7
  • No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 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. — REDACTED:5

What to do

  • Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

P7 · Outbound HTTP resilience10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.

Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.

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.

X1 · Async correctness2.2 / 10Critical✓ Tool-verified

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

  • `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained. (×40) — csharp/EnemyDeathLifecycleDiagnostics.cs:10, csharp/EnemyOperator.Squad.cs:12, csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Diagnostics.cs:73, …

What to do

  • async void method: _Ready
X12 · Unreachable branch8.0 / 10Strong✓ Tool-verified

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.

  • `mode == SquadSessionMode.Join` can never be true where it stands: the guard on line 171 (`mode == SquadSessionMode.Host`) left this block when it was true; the guard on line 181 (`mode == SquadSessionMode.Join`) left this block when it was true. No value of `mode` satisfies all of that, so the true arm of this conditional expression never runs. Reorder the tests, drop the dead branch, or fix the bound that was meant. — csharp/FreightTerminalWorld.Demolition.cs:185

What to do

  • Each finding names the span that makes the branch dead and the span it is dead because of. Confirm from the two, then delete the dead arm or fix the predicate that was meant to be reachable.
X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. 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 correctness7.1 / 10Strong✓ Tool-verified

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.

  • `bannerTween` is a `Tween`, which implements `IDisposable`, and it is created here (line 558). Every use of it in `BuildHud` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var bannerTween = …;`), which releases it at the end of the scope on every path including a throw. — csharp/CombatHUD.cs:558
  • `_hitTween` is a `Tween` this type creates itself, and here (line 1609) a new instance is written over it — but `ShowHit` itself reads through `_hitTween` before replacing it, so it expects an instance to be there, and nothing earlier in `ShowHit` disposes, closes, saves or hands on the instance being replaced. The assignment makes it unreachable while it still holds what it holds (a timer that keeps firing, a callback registered on a longer-lived token, a socket, a handle), and no later `Dispose` can reach it: the type's own disposal releases only the CURRENT instance. The cost accumulates once per overwrite. Release the previous instance first (`_hitTween?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back. — csharp/CombatHUD.cs:1609
  • `_damageTween` is a `Tween` this type creates itself, and here (line 1620) a new instance is written over it — but `ShowDamage` itself reads through `_damageTween` before replacing it, so it expects an instance to be there, and nothing earlier in `ShowDamage` disposes, closes, saves or hands on the instance being replaced. The assignment makes it unreachable while it still holds what it holds (a timer that keeps firing, a callback registered on a longer-lived token, a socket, a handle), and no later `Dispose` can reach it: the type's own disposal releases only the CURRENT instance. The cost accumulates once per overwrite. Release the previous instance first (`_damageTween?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back. — csharp/CombatHUD.cs:1620
  • `_radioTween` is a `Tween` this type creates itself, and here (line 1640) a new instance is written over it — but `ShowRadioMessage` itself reads through `_radioTween` before replacing it, so it expects an instance to be there, and nothing earlier in `ShowRadioMessage` disposes, closes, saves or hands on the instance being replaced. The assignment makes it unreachable while it still holds what it holds (a timer that keeps firing, a callback registered on a longer-lived token, a socket, a handle), and no later `Dispose` can reach it: the type's own disposal releases only the CURRENT instance. The cost accumulates once per overwrite. Release the previous instance first (`_radioTween?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back. — csharp/CombatHUD.cs:1640
  • `tween` is a `Tween`, which implements `IDisposable`, and it is created here (line 106). Every use of it in `ShowKnockdown` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var tween = …;`), which releases it at the end of the scope on every path including a throw. — csharp/CombatHUD.Tactical.cs:106
  • `meshData` is a `MeshDataTool`, which implements `IDisposable`, and it is created here (line 139). Every use of it in `InspectIntegratedScope` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var meshData = …;`), which releases it at the end of the scope on every path including a throw. — csharp/CombatModelLibrary.IntegratedOptics.cs:139
  • `flash` is a `Tween`, which implements `IDisposable`, and it is created here (line 2114). Every use of it in `BeginMuzzleFlash` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var flash = …;`), which releases it at the end of the scope on every path including a throw. — csharp/EnemyOperator.cs:2114
  • `cleanup` is a `Tween`, which implements `IDisposable`, and it is created here (line 216). Every use of it in `SpawnWorldBossPulseEffect` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var cleanup = …;`), which releases it at the end of the scope on every path including a throw. — csharp/FreightTerminalWorld.Boss.cs:216
  • `tween` is a `Tween`, which implements `IDisposable`, and it is created here (line 763). Every use of it in `SpawnTracer` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var tween = …;`), which releases it at the end of the scope on every path including a throw. — csharp/FreightTerminalWorld.cs:763
  • `tween` is a `Tween`, which implements `IDisposable`, and it is created here (line 779). Every use of it in `SpawnImpact` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var tween = …;`), which releases it at the end of the scope on every path including a throw. — csharp/FreightTerminalWorld.cs:779
  • `cleanup` is a `Tween`, which implements `IDisposable`, and it is created here (line 947). Every use of it in `SpawnExplosionEffect` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var cleanup = …;`), which releases it at the end of the scope on every path including a throw. — csharp/FreightTerminalWorld.cs:947
  • `config` is a `ConfigFile`, which implements `IDisposable`, and it is created here (line 3291). Every use of it in `LoadSettings` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var config = …;`), which releases it at the end of the scope on every path including a throw. — csharp/FreightTerminalWorld.cs:3291
  • `config` is a `ConfigFile`, which implements `IDisposable`, and it is created here (line 3314). Every use of it in `SaveSettings` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var config = …;`), which releases it at the end of the scope on every path including a throw. — csharp/FreightTerminalWorld.cs:3314
  • `dragProbe` is a `LootDropZone`, which implements `IDisposable`, and it is created here (line 4133). Every use of it in `ValidateLootFlow` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var dragProbe = …;`), which releases it at the end of the scope on every path including a throw. — csharp/FreightTerminalWorld.cs:4133
  • `groundProbe` is a `LootDropZone`, which implements `IDisposable`, and it is created here (line 4156). Every use of it in `ValidateLootFlow` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var groundProbe = …;`), which releases it at the end of the scope on every path including a throw. — csharp/FreightTerminalWorld.cs:4156
  • `platform` is a `StaticBody3D`, which implements `IDisposable`, and it is created here (line 45). Every use of it in `ValidateDemolitionEnemyResponse` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var platform = …;`), which releases it at the end of the scope on every path including a throw. — csharp/FreightTerminalWorld.Demolition.EnemyResponse.Diagnostics.cs:45
  • `roof` is a `StaticBody3D`, which implements `IDisposable`, and it is created here (line 69). Every use of it in `ValidateExplosionCover` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var roof = …;`), which releases it at the end of the scope on every path including a throw. — csharp/FreightTerminalWorld.ExplosionOcclusion.Diagnostics.cs:69
  • `wall` is a `StaticBody3D`, which implements `IDisposable`, and it is created here (line 88). Every use of it in `ValidateExplosionCover` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var wall = …;`), which releases it at the end of the scope on every path including a throw. — csharp/FreightTerminalWorld.ExplosionOcclusion.Diagnostics.cs:88
  • `lowerWall` is a `StaticBody3D`, which implements `IDisposable`, and it is created here (line 113). Every use of it in `ValidateExplosionCover` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var lowerWall = …;`), which releases it at the end of the scope on every path including a throw. — csharp/FreightTerminalWorld.ExplosionOcclusion.Diagnostics.cs:113
  • `upperWall` is a `StaticBody3D`, which implements `IDisposable`, and it is created here (line 117). Every use of it in `ValidateExplosionCover` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var upperWall = …;`), which releases it at the end of the scope on every path including a throw. — csharp/FreightTerminalWorld.ExplosionOcclusion.Diagnostics.cs:117
  • `shellFloor` is a `StaticBody3D`, which implements `IDisposable`, and it is created here (line 172). Every use of it in `ValidateExplosionCover` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var shellFloor = …;`), which releases it at the end of the scope on every path including a throw. — csharp/FreightTerminalWorld.ExplosionOcclusion.Diagnostics.cs:172
  • `platform` is a `StaticBody3D`, which implements `IDisposable`, and it is created here (line 31). Every use of it in `ValidateIncendiaryAiAvoidance` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var platform = …;`), which releases it at the end of the scope on every path including a throw. — csharp/FreightTerminalWorld.Incendiary.Diagnostics.cs:31
  • `mateFire` is a `IncendiaryGrenade`, which implements `IDisposable`, and it is created here (line 82). Every use of it in `ValidateIncendiaryAiAvoidance` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var mateFire = …;`), which releases it at the end of the scope on every path including a throw. — csharp/FreightTerminalWorld.Incendiary.Diagnostics.cs:82
  • `permissionReceiver` is a `PacketPeerUdp`, which implements `IDisposable`, and it is created here (line 12). Every use of it in `ValidateLanRoomDiscovery` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var permissionReceiver = …;`), which releases it at the end of the scope on every path including a throw. — csharp/FreightTerminalWorld.LanRoomDiscovery.Diagnostics.cs:12
  • `tween` is a `Tween`, which implements `IDisposable`, and it is created here (line 219). Every use of it in `ScheduleMeleeSurfaceMarkFade` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var tween = …;`), which releases it at the end of the scope on every path including a throw. — csharp/FreightTerminalWorld.Melee.Impact.cs:219
  • `cleanup` is a `Tween`, which implements `IDisposable`, and it is created here (line 2368). Every use of it in `ShowSquadMoveMarker` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var cleanup = …;`), which releases it at the end of the scope on every path including a throw. — csharp/FreightTerminalWorld.Squad.cs:2368
  • `jetTween` is a `Tween`, which implements `IDisposable`, and it is created here (line 2750). Every use of it in `SpawnMedicSprayEffect` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var jetTween = …;`), which releases it at the end of the scope on every path including a throw. — csharp/FreightTerminalWorld.Squad.cs:2750
  • `cleanup` is a `Tween`, which implements `IDisposable`, and it is created here (line 2773). Every use of it in `SpawnMedicSprayEffect` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var cleanup = …;`), which releases it at the end of the scope on every path including a throw. — csharp/FreightTerminalWorld.Squad.cs:2773
  • `probe` is a `PacketPeerUdp`, which implements `IDisposable`, and it is created here (line 411). Every use of it in `SendLocalNetworkPermissionProbe` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var probe = …;`), which releases it at the end of the scope on every path including a throw. — csharp/LanRoomDiscovery.cs:411
  • `tween` is a `Tween`, which implements `IDisposable`, and it is created here (line 107). Every use of it in `AddSignal` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var tween = …;`), which releases it at the end of the scope on every path including a throw. — csharp/OperatorLootSignalService.cs:107
  • `cleanup` is a `SceneTreeTimer`, which implements `IDisposable`, and it is created here (line 113). Every use of it in `AddSignal` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var cleanup = …;`), which releases it at the end of the scope on every path including a throw. — csharp/OperatorLootSignalService.cs:113
  • `furniture` is a `ResidentialSearchableFurniture`, which implements `IDisposable`, and it is created here (line 211). Every use of it in `InspectMissingAuthoredVisualForDiagnostics` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var furniture = …;`), which releases it at the end of the scope on every path including a throw. — csharp/ResidentialSearchableFurniture.cs:211
  • `rng` is a `RandomNumberGenerator`, which implements `IDisposable`, and it is created here (line 273). Every use of it in `BuildWeaponShot` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var rng = …;`), which releases it at the end of the scope on every path including a throw. — csharp/SoundLab.cs:273
  • `rng` is a `RandomNumberGenerator`, which implements `IDisposable`, and it is created here (line 377). Every use of it in `MeleeSwing` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var rng = …;`), which releases it at the end of the scope on every path including a throw. — csharp/SoundLab.cs:377
  • `rng` is a `RandomNumberGenerator`, which implements `IDisposable`, and it is created here (line 475). Every use of it in `BuildMeleeSurfaceImpact` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var rng = …;`), which releases it at the end of the scope on every path including a throw. — csharp/SoundLab.cs:475
  • `rng` is a `RandomNumberGenerator`, which implements `IDisposable`, and it is created here (line 629). Every use of it in `ReloadClick` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var rng = …;`), which releases it at the end of the scope on every path including a throw. — csharp/SoundLab.cs:629
  • `rng` is a `RandomNumberGenerator`, which implements `IDisposable`, and it is created here (line 645). Every use of it in `Explosion` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var rng = …;`), which releases it at the end of the scope on every path including a throw. — csharp/SoundLab.cs:645
  • `rng` is a `RandomNumberGenerator`, which implements `IDisposable`, and it is created here (line 662). Every use of it in `WorldBossPulse` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var rng = …;`), which releases it at the end of the scope on every path including a throw. — csharp/SoundLab.cs:662
  • `rng` is a `RandomNumberGenerator`, which implements `IDisposable`, and it is created here (line 698). Every use of it in `Footstep` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var rng = …;`), which releases it at the end of the scope on every path including a throw. — csharp/SoundLab.cs:698
  • `rng` is a `RandomNumberGenerator`, which implements `IDisposable`, and it is created here (line 715). Every use of it in `PlayerHit` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var rng = …;`), which releases it at the end of the scope on every path including a throw. — csharp/SoundLab.cs:715

What to do

  • Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X2 · Cancellation propagation5.5 / 10Adequate✓ Tool-verified

Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).

Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. 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 question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.

  • Only 3/12 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
  • No CancellationToken parameter — this work can't be stopped early once started. (×6) — REDACTED:21, csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Diagnostics.cs:17, csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Diagnostics.cs:45, …
  • Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one. (×3) — csharp/FreightTerminalWorld.WeaponPoseDiagnostics.cs:299, csharp/FreightTerminalWorld.WeaponPoseDiagnostics.cs:309, csharp/FreightTerminalWorld.WeaponPoseDiagnostics.cs:340

What to do

  • Thread a CancellationToken through async methods so work stops promptly on cancellation.
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.

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 handling6.3 / 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. (×6) — csharp/CombatModelLibrary.PreviewDiagnostics.cs:39, csharp/CombatModelLibrary.PreviewDiagnostics.cs:70, csharp/CombatModelLibrary.PreviewDiagnostics.cs:103, …

What to do

  • Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects6.6 / 10Adequate✓ Tool-verified

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.

  • `opponent.LossStreak == 2 && opponent.RecordRound(won: true, objectiveComplete...` can never be true: it asks `opponent.LossStreak` to equal both `2` and `0` at once. Whatever this condition guards never runs, so every value it was written to refuse passes. Join the two equalities with `||` (either value) or test the second one on the value it was meant for. — csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:3277

What to do

  • Each finding expands the condition by De Morgan and names the two terms that disagree — a capability the body needs, and a value the guard refuses. Confirm from the expansion, then decide where the parentheses belong. Almost always the fault term was meant to be conjoined with the capabilities rather than listed beside them: `!((a || b) && x == k)` rejects anything that is neither a nor b, AND anything whose x is not k, which is what a support guard is for. Leaving it as written is the one arrangement that admits exactly the values the guard names.
X5 · Nullable reference types9.2 / 10Exemplary✓ 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 `item`: line 3978 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 4179 then dereferences `item` as `item.Id` AFTER the block has closed, where the guard no longer applies. A null `item` 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 `item` truly cannot be null by then, the guard above is misleading and should go. — csharp/FreightTerminalWorld.cs:4179
  • ~0.9 `!` suppressions per 1k syntax nodes — 946 suppression(s) across the 1000568 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.

What to do

  • 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.
  • Enable <Nullable>enable</Nullable> across all projects 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 Health52.5Adequate — gated by D1, D2, X1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture56.5Adequate — gated by AX2, AX5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity74.3StrongSolid.
Readiness67.9Adequate — gated by P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security95.0ExemplarySolid.
Performance100.0ExemplaryStrongest area.
Unscored — 3 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.

  • X10 Duplicated predicate — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 9 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X9 Subsumed condition operand — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 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
Not included — 53 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
  • 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.
  • C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
  • 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 — ~281 lines of test source are present (.go) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
  • D14 License Compliance — Licence collector did not produce a result
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D23 Boundary Type-Coupling — single shared-core project — no cross-context coupling to assess
  • D25 ADR Conformance — no ADRs to check
  • D28 Secrets (history) — gitleaks killed before it finished — this repository's working tree not scanned
  • 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.
  • D36 Supply-chain Provenance & Signing — The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
  • 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.
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • D8 Code Coverage — Coverage not included — suite not readable by the collector
  • DM1 Domain Modelling — applicable but not scored (1 of 2 signals for this style — below the bar we score at): 40 value object(s)
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
  • P8 Schema migrations — no EF Core usage detected
  • 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.
  • 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
  • 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
  • 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
  • X23 Unguarded diagnostic materialisation — 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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 — 14 finding(s)
D17 · Explicit Debt · EmptyCatchBlock · ×6
  • EmptyCatchBlock csharp/CombatModelLibrary.PreviewDiagnostics.cs:39 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock csharp/CombatModelLibrary.PreviewDiagnostics.cs:70 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock csharp/CombatModelLibrary.PreviewDiagnostics.cs:103 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock csharp/ResidentialAuthoredPropLibrary.cs:251 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock csharp/ResidentialAuthoredPropLibrary.cs:278 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock csharp/ZombieNpc.cs:31 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
D35 · Change Coupling · Boundary-crossing change coupling · ×5
  • Boundary-crossing change coupling: FreightTerminalWorld.CombatModels.cs ↔ build_animated_bamen_operator.py csharp/FreightTerminalWorld.CombatModels.cs:1 — `csharp/FreightTerminalWorld.CombatModels.cs` (context csharp) and `scripts/blender/build_animated_bamen_operator.py` (context scripts) sit in DIFFERENT parts of the tree yet change together 82% of the time (9 of the 11 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 9 shared commits counted here, the most recent 3 are `38100a46` Add authored operator finger rigs; `da15ca56` Complete third-person operator animation set; `878d07bf` Fix GSh and AWM weapon presentation — run `git show` on any of them.
  • Boundary-crossing change coupling: CombatModelLibrary.cs ↔ build_animated_bamen_operator.py csharp/CombatModelLibrary.cs:1 — `csharp/CombatModelLibrary.cs` (context csharp) and `scripts/blender/build_animated_bamen_operator.py` (context scripts) sit in DIFFERENT parts of the tree yet change together 64% of the time (7 of the 11 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 7 shared commits counted here, the most recent 3 are `38100a46` Add authored operator finger rigs; `a240d0d4` Fix rifle carry and indoor blast protection; `878d07bf` Fix GSh and AWM weapon presentation — run `git show` on any of them.
  • Boundary-crossing change coupling: CombatModelLibrary.FirstPerson.cs ↔ build_djmaesen_smg45.py csharp/CombatModelLibrary.FirstPerson.cs:1 — `csharp/CombatModelLibrary.FirstPerson.cs` (context csharp) and `scripts/blender/build_djmaesen_smg45.py` (context scripts) sit in DIFFERENT parts of the tree yet change together 55% of the time (6 of the 11 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 `b6271b4f` Improve first-person SMG scale and firing audio; `f19b23c0` Fix SMG first-person sleeve framing; `3c882482` Standardize first-person weapon presentation — run `git show` on any of them.
  • Boundary-crossing change coupling: FreightTerminalWorld.CombatModels.cs ↔ build_djmaesen_smg45.py csharp/FreightTerminalWorld.CombatModels.cs:1 — `csharp/FreightTerminalWorld.CombatModels.cs` (context csharp) and `scripts/blender/build_djmaesen_smg45.py` (context scripts) 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 `b6271b4f` Improve first-person SMG scale and firing audio; `79bd8044` Fill out SMG first-person upper arms; `f19b23c0` Fix SMG first-person sleeve framing — run `git show` on any of them.
  • Boundary-crossing change coupling: TacticalPlayer.AuthoredVisuals.cs ↔ build_djmaesen_smg45.py csharp/TacticalPlayer.AuthoredVisuals.cs:1 — `csharp/TacticalPlayer.AuthoredVisuals.cs` (context csharp) and `scripts/blender/build_djmaesen_smg45.py` (context scripts) 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 `b6271b4f` Improve first-person SMG scale and firing audio; `f19b23c0` Fix SMG first-person sleeve framing; `3c882482` Standardize first-person weapon presentation — run `git show` on any of them.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
P3 · Security & performance tooling · NuGet vulnerability audit disabled (csproj) · ×1
  • NuGet vulnerability audit disabled (csproj) OperationSteelTide.csproj:7 — <NuGetAudit>false</NuGetAudit> in MSBuild suppresses NuGet's vulnerability audit project-wide.
Serious — 1868 finding(s)
D3 · God Classes · MethodTooLong · ×146
  • MethodTooLong: FreightTerminalWorld.ValidateDemolitionTacticalAi csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:865 — MethodTooLong — ValidateDemolitionTacticalAi runs 1676 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1576 over it, 16.76× 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: FreightTerminalWorld.ValidateSquadFlow csharp/FreightTerminalWorld.Squad.cs:3137 — MethodTooLong — ValidateSquadFlow runs 1161 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1061 over it, 11.61× 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: GameLocalization.GameLocalization(…) csharp/GameLocalization.cs:131 — MethodTooLong — GameLocalization(…) runs 748 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 648 over it, 7.48× 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: FreightTerminalWorld.ValidateResidentialGameplay csharp/FreightTerminalWorld.Residential.cs:1778 — MethodTooLong — ValidateResidentialGameplay runs 649 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 549 over it, 6.49× 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: FreightTerminalWorld.ValidateDemolitionEnemyResponse csharp/FreightTerminalWorld.Demolition.EnemyResponse.Diagnostics.cs:8 — MethodTooLong — ValidateDemolitionEnemyResponse runs 560 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 460 over it, 5.60× 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: FreightTerminalWorld.ValidateLootFlow csharp/FreightTerminalWorld.cs:3788 — MethodTooLong — ValidateLootFlow runs 555 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 455 over it, 5.55× 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: FreightTerminalWorld.ValidateTideglassReactor csharp/FreightTerminalWorld.Demolition.TideglassReactor.Diagnostics.cs:10 — MethodTooLong — ValidateTideglassReactor runs 545 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 445 over it, 5.45× 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: FreightTerminalWorld.ValidateQuickSlots csharp/FreightTerminalWorld.QuickSlots.Diagnostics.cs:8 — MethodTooLong — ValidateQuickSlots runs 451 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 351 over it, 4.51× 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: FreightTerminalWorld.ValidateDemolitionUtility csharp/FreightTerminalWorld.Demolition.Utility.Diagnostics.cs:8 — MethodTooLong — ValidateDemolitionUtility runs 422 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 322 over it, 4.22× 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: FreightTerminalWorld.ValidateDemolitionNetworkSession csharp/FreightTerminalWorld.Demolition.Network.Diagnostics.cs:83 — MethodTooLong — ValidateDemolitionNetworkSession runs 386 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 286 over it, 3.86× 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: FreightTerminalWorld.ValidateTideglassReactorDensityCore csharp/FreightTerminalWorld.Demolition.TideglassReactor.DensityDiagnostics.cs:111 — MethodTooLong — ValidateTideglassReactorDensityCore runs 381 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 281 over it, 3.81× 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: FreightTerminalWorld.ValidateSquadSustainment csharp/FreightTerminalWorld.Squad.Sustainment.Diagnostics.cs:10 — MethodTooLong — ValidateSquadSustainment runs 376 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 276 over it, 3.76× 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: FreightTerminalWorld.ValidateSquadTraversal csharp/FreightTerminalWorld.Squad.Traversal.Diagnostics.cs:11 — MethodTooLong — ValidateSquadTraversal runs 362 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 262 over it, 3.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: FreightTerminalWorld.ValidateSkybridgeAccess csharp/FreightTerminalWorld.Residential.Access.cs:625 — MethodTooLong — ValidateSkybridgeAccess runs 347 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 247 over it, 3.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: FreightTerminalWorld.ValidateBazaarCrossingCore csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Diagnostics.cs:45 — MethodTooLong — ValidateBazaarCrossingCore runs 333 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 233 over it, 3.33× 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: FreightTerminalWorld.ValidateDemolitionMode csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:495 — MethodTooLong — ValidateDemolitionMode runs 330 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 230 over it, 3.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: FreightTerminalWorld.ValidateSquadPerformance csharp/FreightTerminalWorld.Squad.Performance.Diagnostics.cs:35 — MethodTooLong — ValidateSquadPerformance runs 329 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 229 over it, 3.29× 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: FreightTerminalWorld.ValidateJianghaiInteriors csharp/FreightTerminalWorld.Refinery.Interiors.Diagnostics.cs:9 — MethodTooLong — ValidateJianghaiInteriors runs 324 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 224 over it, 3.24× 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: FreightTerminalWorld.ValidateRefineryMap csharp/FreightTerminalWorld.Refinery.Validation.cs:15 — MethodTooLong — ValidateRefineryMap runs 322 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 222 over it, 3.22× 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: JianghaiEnterableCollisionShellBuilder.Build csharp/JianghaiEnterableCollisionShellBuilder.cs:11 — MethodTooLong — Build runs 322 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 222 over it, 3.22× 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: FreightTerminalWorld.ValidateMeleeCombatSemantics csharp/FreightTerminalWorld.Melee.Combat.Diagnostics.cs:71 — MethodTooLong — ValidateMeleeCombatSemantics runs 319 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 219 over it, 3.19× 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: FreightTerminalWorld.ValidateAdsAlignment csharp/FreightTerminalWorld.WeaponPoseDiagnostics.cs:9 — MethodTooLong — ValidateAdsAlignment runs 318 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 218 over it, 3.18× 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: FreightTerminalWorld.ValidateDemolitionWeapons csharp/FreightTerminalWorld.Demolition.WeaponDrops.Diagnostics.cs:8 — MethodTooLong — ValidateDemolitionWeapons runs 305 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 205 over it, 3.05× 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: FreightTerminalWorld.ValidateDemolitionRules csharp/FreightTerminalWorld.Demolition.Rules.Diagnostics.cs:8 — MethodTooLong — ValidateDemolitionRules runs 302 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 202 over it, 3.02× 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: FreightTerminalWorld.ValidateExtractionSurvivors csharp/FreightTerminalWorld.Extraction.Survivors.Diagnostics.cs:9 — MethodTooLong — ValidateExtractionSurvivors runs 273 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 173 over it, 2.73× 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.
  • + 121 more in this group — see findings.md.
D15 · Churn × Complexity Hotspots · Hotspot · ×93
  • Hotspot: csharp/FreightTerminalWorld.Squad.cs csharp/FreightTerminalWorld.Squad.cs:3137 — csharp/FreightTerminalWorld.Squad.cs changed 76 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 390 in FreightTerminalWorld.ValidateSquadFlow at line 3137. 14 of those changes were fix/bug commits, and the other 62 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-08..2026-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-08 21:52:54 +08:00' --until='2026-10-06 21:52:54 +08:00' --full-history --no-merges -- csharp/FreightTerminalWorld.Squad.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: csharp/FreightTerminalWorld.cs csharp/FreightTerminalWorld.cs:3788 — csharp/FreightTerminalWorld.cs changed 150 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 178 in FreightTerminalWorld.ValidateLootFlow at line 3788. 15 of those changes were fix/bug commits, and the other 135 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-08..2026-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-08 21:52:54 +08:00' --until='2026-10-06 21:52:54 +08:00' --full-history --no-merges -- csharp/FreightTerminalWorld.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: csharp/FreightTerminalWorld.Demolition.Diagnostics.cs csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:865 — csharp/FreightTerminalWorld.Demolition.Diagnostics.cs changed 37 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 301 in FreightTerminalWorld.ValidateDemolitionTacticalAi at line 865. 6 of those changes were fix/bug commits, and the other 31 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-08..2026-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-08 21:52:54 +08:00' --until='2026-10-06 21:52:54 +08:00' --full-history --no-merges -- csharp/FreightTerminalWorld.Demolition.Diagnostics.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: csharp/FreightTerminalWorld.Residential.cs csharp/FreightTerminalWorld.Residential.cs:1778 — csharp/FreightTerminalWorld.Residential.cs changed 41 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 186 in FreightTerminalWorld.ValidateResidentialGameplay at line 1778. 4 of those changes were fix/bug commits, and the other 37 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-08..2026-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-08 21:52:54 +08:00' --until='2026-10-06 21:52:54 +08:00' --full-history --no-merges -- csharp/FreightTerminalWorld.Residential.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: csharp/TacticalPlayer.cs csharp/TacticalPlayer.cs:1235 — csharp/TacticalPlayer.cs changed 77 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 92 in TacticalPlayer.RunAuthoritativePhysicsStep at line 1235. 17 of those changes were fix/bug commits, and the other 60 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-08..2026-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-08 21:52:54 +08:00' --until='2026-10-06 21:52:54 +08:00' --full-history --no-merges -- csharp/TacticalPlayer.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: csharp/EnemyOperator.cs csharp/EnemyOperator.cs:588 — csharp/EnemyOperator.cs changed 49 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 67 in EnemyOperator._PhysicsProcess at line 588. 7 of those changes were fix/bug commits, and the other 42 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-08..2026-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-08 21:52:54 +08:00' --until='2026-10-06 21:52:54 +08:00' --full-history --no-merges -- csharp/EnemyOperator.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: csharp/SquadMate.cs csharp/SquadMate.cs:496 — csharp/SquadMate.cs changed 55 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 45 in SquadMate._PhysicsProcess at line 496. 15 of those changes were fix/bug commits, and the other 40 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-08..2026-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-08 21:52:54 +08:00' --until='2026-10-06 21:52:54 +08:00' --full-history --no-merges -- csharp/SquadMate.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: csharp/FreightTerminalWorld.QuickSlots.Diagnostics.cs csharp/FreightTerminalWorld.QuickSlots.Diagnostics.cs:8 — csharp/FreightTerminalWorld.QuickSlots.Diagnostics.cs changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 174 in FreightTerminalWorld.ValidateQuickSlots at line 8. 2 of those changes were fix/bug commits, and the other 9 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-08..2026-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-08 21:52:54 +08:00' --until='2026-10-06 21:52:54 +08:00' --full-history --no-merges -- csharp/FreightTerminalWorld.QuickSlots.Diagnostics.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: csharp/TacticalPlayer.AuthoredVisuals.cs csharp/TacticalPlayer.AuthoredVisuals.cs:1195 — csharp/TacticalPlayer.AuthoredVisuals.cs changed 43 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in TacticalPlayer.RawReloadSupportTargetGlobal at line 1195. 13 of those changes were fix/bug commits, and the other 30 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-08..2026-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-08 21:52:54 +08:00' --until='2026-10-06 21:52:54 +08:00' --full-history --no-merges -- csharp/TacticalPlayer.AuthoredVisuals.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: csharp/FreightTerminalWorld.CombatModels.cs csharp/FreightTerminalWorld.CombatModels.cs:519 — csharp/FreightTerminalWorld.CombatModels.cs changed 41 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in FreightTerminalWorld.CaptureFirstPersonWeaponViews at line 519. 9 of those changes were fix/bug commits, and the other 32 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-08..2026-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-08 21:52:54 +08:00' --until='2026-10-06 21:52:54 +08:00' --full-history --no-merges -- csharp/FreightTerminalWorld.CombatModels.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: csharp/FreightTerminalWorld.Demolition.Rules.Diagnostics.cs csharp/FreightTerminalWorld.Demolition.Rules.Diagnostics.cs:8 — csharp/FreightTerminalWorld.Demolition.Rules.Diagnostics.cs changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 143 in FreightTerminalWorld.ValidateDemolitionRules at line 8. 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-08..2026-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-08 21:52:54 +08:00' --until='2026-10-06 21:52:54 +08:00' --full-history --no-merges -- csharp/FreightTerminalWorld.Demolition.Rules.Diagnostics.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: csharp/CombatModelLibrary.cs csharp/CombatModelLibrary.cs:1440 — csharp/CombatModelLibrary.cs changed 70 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in CombatModelLibrary.InstantiateAdaptedWeapon at line 1440. 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-08..2026-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-08 21:52:54 +08:00' --until='2026-10-06 21:52:54 +08:00' --full-history --no-merges -- csharp/CombatModelLibrary.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: csharp/CombatHUD.cs csharp/CombatHUD.cs:1033 — csharp/CombatHUD.cs changed 63 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in CombatHUD.RefreshLootOverlay at line 1033. 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-08..2026-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-08 21:52:54 +08:00' --until='2026-10-06 21:52:54 +08:00' --full-history --no-merges -- csharp/CombatHUD.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: csharp/TacticalPlayer.WeaponPose.cs csharp/TacticalPlayer.WeaponPose.cs:398 — csharp/TacticalPlayer.WeaponPose.cs changed 27 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 51 in TacticalPlayer.InspectOpticClearanceForDiagnostics at line 398. 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-08..2026-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-08 21:52:54 +08:00' --until='2026-10-06 21:52:54 +08:00' --full-history --no-merges -- csharp/TacticalPlayer.WeaponPose.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: scripts/blender/build_bazaar_crossing.py scripts/blender/build_bazaar_crossing.py:5959 — scripts/blender/build_bazaar_crossing.py changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 162 in build_bazaar_crossing.validate_authored_scene at line 5959. 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-08..2026-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-08 21:52:54 +08:00' --until='2026-10-06 21:52:54 +08:00' --full-history --no-merges -- scripts/blender/build_bazaar_crossing.py`: 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: csharp/FreightTerminalWorld.Squad.Navigation.cs csharp/FreightTerminalWorld.Squad.Navigation.cs:183 — csharp/FreightTerminalWorld.Squad.Navigation.cs changed 22 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 44 in FreightTerminalWorld.ResolveSquadNavigationDestination at line 183. 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-08..2026-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-08 21:52:54 +08:00' --until='2026-10-06 21:52:54 +08:00' --full-history --no-merges -- csharp/FreightTerminalWorld.Squad.Navigation.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: csharp/WeaponSystem.cs csharp/WeaponSystem.cs:790 — csharp/WeaponSystem.cs changed 27 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in WeaponCatalog.Build at line 790. 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-08..2026-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-08 21:52:54 +08:00' --until='2026-10-06 21:52:54 +08:00' --full-history --no-merges -- csharp/WeaponSystem.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: csharp/FreightTerminalWorld.Level.cs csharp/FreightTerminalWorld.Level.cs:194 — csharp/FreightTerminalWorld.Level.cs changed 36 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in FreightTerminalWorld.ApplyTimeOfDay at line 194. 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-08..2026-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-08 21:52:54 +08:00' --until='2026-10-06 21:52:54 +08:00' --full-history --no-merges -- csharp/FreightTerminalWorld.Level.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: csharp/FreightTerminalWorld.Demolition.TideglassReactor.Diagnostics.cs csharp/FreightTerminalWorld.Demolition.TideglassReactor.Diagnostics.cs:10 — csharp/FreightTerminalWorld.Demolition.TideglassReactor.Diagnostics.cs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 173 in FreightTerminalWorld.ValidateTideglassReactor at line 10. 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-08..2026-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-08 21:52:54 +08:00' --until='2026-10-06 21:52:54 +08:00' --full-history --no-merges -- csharp/FreightTerminalWorld.Demolition.TideglassReactor.Diagnostics.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: csharp/DemolitionArenaLayout.cs csharp/DemolitionArenaLayout.cs:134 — csharp/DemolitionArenaLayout.cs changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 50 in DemolitionArenaLayout.DemolitionArenaLayout.ctor at line 134. 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-08..2026-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-08 21:52:54 +08:00' --until='2026-10-06 21:52:54 +08:00' --full-history --no-merges -- csharp/DemolitionArenaLayout.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: csharp/FreightTerminalWorld.OperatorRoster.Diagnostics.cs csharp/FreightTerminalWorld.OperatorRoster.Diagnostics.cs:10 — csharp/FreightTerminalWorld.OperatorRoster.Diagnostics.cs changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 77 in FreightTerminalWorld.ValidateOperatorRoster at line 10. 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-08..2026-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-08 21:52:54 +08:00' --until='2026-10-06 21:52:54 +08:00' --full-history --no-merges -- csharp/FreightTerminalWorld.OperatorRoster.Diagnostics.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: csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Diagnostics.cs csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Diagnostics.cs:45 — csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Diagnostics.cs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 121 in FreightTerminalWorld.ValidateBazaarCrossingCore at line 45. 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-08..2026-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-08 21:52:54 +08:00' --until='2026-10-06 21:52:54 +08:00' --full-history --no-merges -- csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Diagnostics.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: csharp/FreightTerminalWorld.OperatorCarry.Diagnostics.cs csharp/FreightTerminalWorld.OperatorCarry.Diagnostics.cs:242 — csharp/FreightTerminalWorld.OperatorCarry.Diagnostics.cs changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 47 in FreightTerminalWorld.OperatorCarrySampleValid at line 242. 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-08..2026-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-08 21:52:54 +08:00' --until='2026-10-06 21:52:54 +08:00' --full-history --no-merges -- csharp/FreightTerminalWorld.OperatorCarry.Diagnostics.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: csharp/FreightTerminalWorld.Extraction.cs csharp/FreightTerminalWorld.Extraction.cs:493 — csharp/FreightTerminalWorld.Extraction.cs changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 68 in FreightTerminalWorld.ValidateExtractionSequence at line 493. 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-08..2026-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-08 21:52:54 +08:00' --until='2026-10-06 21:52:54 +08:00' --full-history --no-merges -- csharp/FreightTerminalWorld.Extraction.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: csharp/FreightTerminalWorld.TrainingRange.Diagnostics.cs csharp/FreightTerminalWorld.TrainingRange.Diagnostics.cs:8 — csharp/FreightTerminalWorld.TrainingRange.Diagnostics.cs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 133 in FreightTerminalWorld.ValidateTrainingRange at line 8. 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-08..2026-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-08 21:52:54 +08:00' --until='2026-10-06 21:52:54 +08:00' --full-history --no-merges -- csharp/FreightTerminalWorld.TrainingRange.Diagnostics.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.
  • + 68 more in this group — see findings.md.
D3 · God Classes · FileTooLong · ×51
  • FileTooLong: csharp/FreightTerminalWorld.cs csharp/FreightTerminalWorld.cs — FileTooLong — 4940 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 4440 over it, 9.88× 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: csharp/FreightTerminalWorld.Squad.cs csharp/FreightTerminalWorld.Squad.cs — FileTooLong — 3414 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2914 over it, 6.83× 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: csharp/FreightTerminalWorld.Demolition.Diagnostics.cs csharp/FreightTerminalWorld.Demolition.Diagnostics.cs — FileTooLong — 2855 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2355 over it, 5.71× 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: csharp/FreightTerminalWorld.Residential.cs csharp/FreightTerminalWorld.Residential.cs — FileTooLong — 2409 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1909 over it, 4.82× 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: csharp/TacticalPlayer.cs csharp/TacticalPlayer.cs — FileTooLong — 2135 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1635 over it, 4.27× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: csharp/CombatModelLibrary.cs csharp/CombatModelLibrary.cs — FileTooLong — 1732 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1232 over it, 3.46× 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: csharp/EnemyOperator.cs csharp/EnemyOperator.cs — FileTooLong — 1460 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 960 over it, 2.92× 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: csharp/CombatHUD.cs csharp/CombatHUD.cs — FileTooLong — 1264 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 764 over it, 2.53× 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: csharp/TacticalPlayer.AuthoredVisuals.cs csharp/TacticalPlayer.AuthoredVisuals.cs — FileTooLong — 1162 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 662 over it, 2.32× 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: csharp/FreightTerminalWorld.Level.cs csharp/FreightTerminalWorld.Level.cs — FileTooLong — 1067 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 567 over it, 2.13× 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: csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs — FileTooLong — 1043 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 543 over it, 2.09× 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: csharp/SquadMate.cs csharp/SquadMate.cs — FileTooLong — 1022 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 522 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: csharp/FreightTerminalWorld.Residential.Access.cs csharp/FreightTerminalWorld.Residential.Access.cs — FileTooLong — 909 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 409 over it, 1.82× 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: csharp/FreightTerminalWorld.Squad.Navigation.cs csharp/FreightTerminalWorld.Squad.Navigation.cs — FileTooLong — 904 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 404 over it, 1.81× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: csharp/GameLocalization.cs csharp/GameLocalization.cs — FileTooLong — 896 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 396 over it, 1.79× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: csharp/FreightTerminalWorld.Expansion.cs csharp/FreightTerminalWorld.Expansion.cs — FileTooLong — 869 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 369 over it, 1.74× 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: csharp/FreightTerminalWorld.Demolition.Strategy.cs csharp/FreightTerminalWorld.Demolition.Strategy.cs — FileTooLong — 826 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 326 over it, 1.65× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: csharp/FreightTerminalWorld.Demolition.cs csharp/FreightTerminalWorld.Demolition.cs — FileTooLong — 798 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 298 over it, 1.60× 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: csharp/FreightTerminalWorld.Squad.NavGrid.cs csharp/FreightTerminalWorld.Squad.NavGrid.cs — FileTooLong — 774 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 274 over it, 1.55× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: csharp/CombatHUD.Deployment.cs csharp/CombatHUD.Deployment.cs — FileTooLong — 751 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 251 over it, 1.50× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: csharp/FreightTerminalWorld.Demolition.TideglassReactor.DensityDiagnostics.cs csharp/FreightTerminalWorld.Demolition.TideglassReactor.DensityDiagnostics.cs — FileTooLong — 749 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 249 over it, 1.50× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Runtime.cs csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Runtime.cs — FileTooLong — 716 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 216 over it, 1.43× 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: csharp/CombatHUD.Squad.cs csharp/CombatHUD.Squad.cs — FileTooLong — 715 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 215 over it, 1.43× 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: csharp/DemolitionArenaLayout.cs csharp/DemolitionArenaLayout.cs — FileTooLong — 711 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 211 over it, 1.42× 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: csharp/SquadMate.Combat.cs csharp/SquadMate.Combat.cs — FileTooLong — 694 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 194 over it, 1.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.
  • + 26 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×46
  • Duplicated block (5 lines × 2) csharp/JianghaiEnterableCollisionShellBuilder.cs:107 — csharp/JianghaiEnterableCollisionShellBuilder.cs:107-111 | csharp/JianghaiEnterableCollisionShellBuilder.cs:195-199 — 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 `csharp/JianghaiEnterableCollisionShellBuilder.cs:107` 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) csharp/JianghaiEnterableCollisionShellBuilder.cs:122 — csharp/JianghaiEnterableCollisionShellBuilder.cs:122-126 | csharp/JianghaiEnterableCollisionShellBuilder.cs:210-214 — 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 `csharp/JianghaiEnterableCollisionShellBuilder.cs:122` 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) csharp/FreightTerminalWorld.Squad.IndoorRevive.Diagnostics.cs:193 — csharp/FreightTerminalWorld.Squad.IndoorRevive.Diagnostics.cs:193-197 | csharp/FreightTerminalWorld.Squad.Traversal.Diagnostics.cs:243-247 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/FreightTerminalWorld.Squad.IndoorRevive.Diagnostics.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 (5 lines × 2) csharp/GeneratedInventoryArt.cs:96 — csharp/GeneratedInventoryArt.cs:96-100 | csharp/GeneratedInventoryArt.cs:112-116 — 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 `csharp/GeneratedInventoryArt.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 × 2) csharp/DemolitionArenaLayout.cs:532 — csharp/DemolitionArenaLayout.cs:532-536 | csharp/DemolitionArenaLayout.cs:845-849 — 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 `csharp/DemolitionArenaLayout.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 (5 lines × 2) csharp/FreightTerminalWorld.ReadmeCapture.cs:234 — csharp/FreightTerminalWorld.ReadmeCapture.cs:234-238 | csharp/FreightTerminalWorld.cs:4573-4577 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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, `csharp/FreightTerminalWorld.cs:4579` calls `TryStoreInBackpack` and `csharp/FreightTerminalWorld.ReadmeCapture.cs:240` 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) csharp/DemolitionArenaLayout.BazaarCrossing.cs:285 — csharp/DemolitionArenaLayout.BazaarCrossing.cs:285-289 | csharp/DemolitionArenaLayout.BazaarCrossing.cs:325-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. Read the line range as the matched WINDOW rather than a finished unit: at `csharp/DemolitionArenaLayout.BazaarCrossing.cs:285` it does not close everything it opens, so those exact lines 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) csharp/FreightTerminalWorld.Demolition.Strategy.cs:1058 — csharp/FreightTerminalWorld.Demolition.Strategy.cs:1058-1062 | csharp/FreightTerminalWorld.Demolition.Strategy.cs:1117-1121 — 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) csharp/FreightTerminalWorld.ExplosionOcclusion.Diagnostics.cs:92 — csharp/FreightTerminalWorld.ExplosionOcclusion.Diagnostics.cs:92-96 | csharp/FreightTerminalWorld.ExplosionOcclusion.Diagnostics.cs:121-125 — 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) csharp/FreightTerminalWorld.IndustrialDoors.cs:122 — csharp/FreightTerminalWorld.IndustrialDoors.cs:122-126 | csharp/FreightTerminalWorld.IndustrialDoors.cs:161-165 — 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) csharp/FreightTerminalWorld.cs:4231 — csharp/FreightTerminalWorld.cs:4231-4235 | csharp/FreightTerminalWorld.cs:4521-4525 — 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) csharp/FreightTerminalWorld.Demolition.HarborLocks.Diagnostics.cs:231 — csharp/FreightTerminalWorld.Demolition.HarborLocks.Diagnostics.cs:231-235 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:988-992 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/FreightTerminalWorld.Demolition.HarborLocks.Diagnostics.cs:231` it does not close everything it opens, so those exact lines 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) csharp/DemolitionArenaLayout.cs:871 — csharp/DemolitionArenaLayout.cs:871-875 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:567-571 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (5 lines × 2) csharp/FreightTerminalWorld.LanternCanal.Diagnostics.cs:357 — csharp/FreightTerminalWorld.LanternCanal.Diagnostics.cs:357-361 | csharp/FreightTerminalWorld.Refinery.Capture.cs:331-335 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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) csharp/DemolitionArenaLayout.cs:149 — csharp/DemolitionArenaLayout.cs:149-153 | csharp/DemolitionArenaLayout.cs:242-246 — 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 `csharp/DemolitionArenaLayout.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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different 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 × 2) csharp/DemolitionArenaLayout.cs:212 — csharp/DemolitionArenaLayout.cs:212-216 | csharp/DemolitionArenaLayout.cs:261-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 `csharp/DemolitionArenaLayout.cs:212` 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) csharp/DemolitionArenaLayout.cs:320 — csharp/DemolitionArenaLayout.cs:320-324 | csharp/DemolitionArenaLayout.cs:335-339 — 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 `csharp/DemolitionArenaLayout.cs:320` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different 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 × 2) csharp/DemolitionArenaLayout.HarborLocks.cs:168 — csharp/DemolitionArenaLayout.HarborLocks.cs:168-172 | csharp/DemolitionArenaLayout.cs:465-469 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (5 lines × 2) csharp/FirstPersonFieldUsePresentation.cs:236 — csharp/FirstPersonFieldUsePresentation.cs:236-240 | csharp/FirstPersonFieldUsePresentation.cs:269-273 — 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) csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:370 — csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:370-374 | csharp/FreightTerminalWorld.Demolition.HarborLocks.Diagnostics.cs:139-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 `csharp/FreightTerminalWorld.Demolition.Diagnostics.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 (5 lines × 2) csharp/FreightTerminalWorld.IndustrialDoors.cs:105 — csharp/FreightTerminalWorld.IndustrialDoors.cs:105-109 | csharp/FreightTerminalWorld.Refinery.Doors.Diagnostics.cs:29-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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different 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 × 2) csharp/FreightTerminalWorld.Level.cs:737 — csharp/FreightTerminalWorld.Level.cs:737-741 | csharp/FreightTerminalWorld.Level.cs:776-780 — 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) csharp/FreightTerminalWorld.Residential.cs:968 — csharp/FreightTerminalWorld.Residential.cs:968-972 | csharp/FreightTerminalWorld.Residential.cs:976-980 — 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) csharp/FreightTerminalWorld.VaultHouse.cs:84 — csharp/FreightTerminalWorld.VaultHouse.cs:84-89 | csharp/FreightTerminalWorld.VaultHouse.cs:94-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.
  • Duplicated block (5 lines × 2) csharp/InventoryModelPreview.cs:459 — csharp/InventoryModelPreview.cs:459-463 | csharp/InventoryModelPreview.cs:468-472 — 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 `csharp/InventoryModelPreview.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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • + 21 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×40
  • Duplicated block (8 lines × 2) csharp/TacticalPlayer.AuthoredVisuals.cs:1329 — csharp/TacticalPlayer.AuthoredVisuals.cs:1329-1336 | csharp/TacticalPlayer.ReloadPresentation.cs:409-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 both call sites, so a change lands once.
  • Duplicated block (8 lines × 2) csharp/JianghaiEnterableCollisionShellBuilder.cs:107 — csharp/JianghaiEnterableCollisionShellBuilder.cs:107-114 | csharp/JianghaiEnterableCollisionShellBuilder.cs:158-165 — 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 `csharp/JianghaiEnterableCollisionShellBuilder.cs:107` 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) csharp/JianghaiEnterableCollisionShellBuilder.cs:122 — csharp/JianghaiEnterableCollisionShellBuilder.cs:122-129 | csharp/JianghaiEnterableCollisionShellBuilder.cs:173-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. Read the line range as the matched WINDOW rather than a finished unit: at `csharp/JianghaiEnterableCollisionShellBuilder.cs:122` 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) csharp/JianghaiEnterableCollisionShellBuilder.cs:195 — csharp/JianghaiEnterableCollisionShellBuilder.cs:195-202 | csharp/JianghaiEnterableCollisionShellBuilder.cs:231-238 — 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 `csharp/JianghaiEnterableCollisionShellBuilder.cs:195` 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) csharp/JianghaiEnterableCollisionShellBuilder.cs:210 — csharp/JianghaiEnterableCollisionShellBuilder.cs:210-217 | csharp/JianghaiEnterableCollisionShellBuilder.cs:246-253 — 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 `csharp/JianghaiEnterableCollisionShellBuilder.cs:210` 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) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.RouteDiagnostics.cs:250 — csharp/FreightTerminalWorld.Demolition.BazaarCrossing.RouteDiagnostics.cs:250-257 | csharp/FreightTerminalWorld.Demolition.BazaarCrossing.RouteDiagnostics.cs:306-313 — 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 `csharp/FreightTerminalWorld.Demolition.BazaarCrossing.RouteDiagnostics.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 (8 lines × 2) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs:494 — csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs:494-501 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:278-285 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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) csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:412 — csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:412-419 | csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:486-493 — 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 `csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:412` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those 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, `csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:483` calls `QueueFree` and `csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:409` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared 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) csharp/FreightTerminalWorld.Refinery.NavigationValidation.cs:66 — csharp/FreightTerminalWorld.Refinery.NavigationValidation.cs:66-73 | csharp/FreightTerminalWorld.Refinery.NavigationValidation.cs:317-324 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) csharp/DemolitionArenaLayout.cs:151 — csharp/DemolitionArenaLayout.cs:151-158 | csharp/DemolitionArenaLayout.cs:191-198 — 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 `csharp/DemolitionArenaLayout.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 (8 lines × 2) csharp/DemolitionArenaLayout.cs:771 — csharp/DemolitionArenaLayout.cs:771-778 | csharp/DemolitionArenaLayout.cs:805-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 `csharp/DemolitionArenaLayout.cs:771` it does not close everything it opens, so those exact lines 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) csharp/DemolitionArenaLayout.BazaarCrossing.cs:249 — csharp/DemolitionArenaLayout.BazaarCrossing.cs:249-256 | csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GuardRailDiagnostics.cs:283-290 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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) csharp/FreightTerminalWorld.Refinery.Doors.Diagnostics.cs:104 — csharp/FreightTerminalWorld.Refinery.Doors.Diagnostics.cs:104-111 | csharp/FreightTerminalWorld.Refinery.Doors.Diagnostics.cs:166-173 — 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 `csharp/FreightTerminalWorld.Refinery.Doors.Diagnostics.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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `csharp/FreightTerminalWorld.Refinery.Doors.Diagnostics.cs:102` calls `SetProcess`, `SetPhysicsProcess` and `csharp/FreightTerminalWorld.Refinery.Doors.Diagnostics.cs:165` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared 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) csharp/FirstPersonFieldUsePresentation.cs:206 — csharp/FirstPersonFieldUsePresentation.cs:206-213 | csharp/FirstPersonFieldUsePresentation.cs:237-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 `csharp/FirstPersonFieldUsePresentation.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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code 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, `csharp/FirstPersonFieldUsePresentation.cs:237` calls `Ease`, `Range` and `csharp/FirstPersonFieldUsePresentation.cs:206` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared 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) csharp/FreightTerminalWorld.Demolition.EnemyResponse.Diagnostics.cs:159 — csharp/FreightTerminalWorld.Demolition.EnemyResponse.Diagnostics.cs:159-166 | csharp/FreightTerminalWorld.Demolition.EnemyResponse.Diagnostics.cs:173-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.
  • Duplicated block (8 lines × 2) csharp/FreightTerminalWorld.Demolition.TideglassReactor.AssetDiagnostics.cs:174 — csharp/FreightTerminalWorld.Demolition.TideglassReactor.AssetDiagnostics.cs:174-181 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.AssetDiagnostics.cs:221-228 — 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 `csharp/FreightTerminalWorld.Demolition.TideglassReactor.AssetDiagnostics.cs:174` 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) csharp/FreightTerminalWorld.Melee.Combat.Diagnostics.cs:114 — csharp/FreightTerminalWorld.Melee.Combat.Diagnostics.cs:114-121 | csharp/FreightTerminalWorld.Melee.Combat.Diagnostics.cs:145-152 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) csharp/FreightTerminalWorld.Refinery.NavigationValidation.cs:208 — csharp/FreightTerminalWorld.Refinery.NavigationValidation.cs:208-216 | csharp/FreightTerminalWorld.Refinery.NavigationValidation.cs:247-254 — 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 `csharp/FreightTerminalWorld.Refinery.NavigationValidation.cs:247` it begins part-way through the construct above it, so those exact lines 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) csharp/FreightTerminalWorld.TrainingRange.Diagnostics.cs:88 — csharp/FreightTerminalWorld.TrainingRange.Diagnostics.cs:88-99 | csharp/FreightTerminalWorld.TrainingRange.Diagnostics.cs:195-202 — 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 `csharp/FreightTerminalWorld.TrainingRange.Diagnostics.cs:88` it does not close everything it opens, so those exact lines 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) csharp/TacticalSurfaceLibrary.cs:45 — csharp/TacticalSurfaceLibrary.cs:45-52 | csharp/TacticalSurfaceLibrary.cs:70-77 — 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 `csharp/TacticalSurfaceLibrary.cs:45` 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) csharp/EnemyOperator.Utility.cs:43 — csharp/EnemyOperator.Utility.cs:43-50 | csharp/SquadMate.Utility.cs:45-52 — before extracting anything, compare `csharp/EnemyOperator.Utility.cs` and `csharp/SquadMate.Utility.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. 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 × 2) REDACTED:470 — REDACTED:470-477 | scripts/blender/export_jianghai_old_city.py:1216-1223 — before extracting anything, compare `REDACTED` and `scripts/blender/export_jianghai_old_city.py` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 507 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 `REDACTED: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. 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) scripts/blender/build_animated_reload_arms.py:1009 — scripts/blender/build_animated_reload_arms.py:1009-1016 | scripts/blender/build_animated_reload_arms.py:1018-1025 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) scripts/blender/build_authored_optics.py:217 — scripts/blender/build_authored_optics.py:217-224 | scripts/blender/build_nisu_m4a1.py:957-964 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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) scripts/blender/build_authored_optics.py:1270 — scripts/blender/build_authored_optics.py:1270-1277 | scripts/blender/build_nisu_m4a1.py:1820-1827 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `scripts/blender/build_authored_optics.py:1270` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • + 15 more in this group — see findings.md.
X1 · Async correctness · async void method · ×40
  • async void method: _Ready csharp/EnemyDeathLifecycleDiagnostics.cs:10 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: SetScanned csharp/EnemyOperator.Squad.cs:12 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: ValidateOrbitalMap csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Diagnostics.cs:73 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: ValidateOrbitalCollision csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Diagnostics.cs:76 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: ValidateOrbitalGameplay csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Diagnostics.cs:79 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: ValidateOrbitalSpawns csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Diagnostics.cs:82 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: ValidateOrbitalLoading csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Diagnostics.cs:85 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: ValidateOrbitalAtmosphere csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Diagnostics.cs:88 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: ValidateOrbitalWater csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Diagnostics.cs:91 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: ValidateOrbitalComplexIntegration csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Diagnostics.cs:354 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: CaptureOrbitalMap csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Diagnostics.cs:650 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: CaptureOrbitalCoast csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Diagnostics.cs:717 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: ValidateAiLadders csharp/FreightTerminalWorld.AiLadder.Diagnostics.cs:48 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: ValidateAiNavigation csharp/FreightTerminalWorld.AiNavigation.Diagnostics.cs:10 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: ValidateAircraftBehavior csharp/FreightTerminalWorld.AircraftBehavior.Diagnostics.cs:8 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: ValidateBackendClient REDACTED:21 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: ValidateWorldBoss csharp/FreightTerminalWorld.Boss.cs:221 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: CaptureWorldBoss csharp/FreightTerminalWorld.Boss.cs:338 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: ValidateCanalAccess csharp/FreightTerminalWorld.CanalAccess.Diagnostics.cs:9 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: ValidateOperatorAnimations csharp/FreightTerminalWorld.CombatModels.cs:9 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: ValidateCombatModels csharp/FreightTerminalWorld.CombatModels.cs:220 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: ValidateCrowdPerformance csharp/FreightTerminalWorld.CrowdPerformance.Diagnostics.cs:16 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: _Ready csharp/FreightTerminalWorld.cs:163 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: CaptureValidationFrame csharp/FreightTerminalWorld.cs:3322 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: CapturePauseFrame csharp/FreightTerminalWorld.cs:3331 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • + 15 more in this group — see findings.md.
X18 · Disposal-pattern correctness · Disposable created and abandoned in the method that made it · ×37
  • Disposable created and abandoned in the method that made it csharp/CombatHUD.cs:558 — `bannerTween` is a `Tween`, which implements `IDisposable`, and it is created here (line 558). Every use of it in `BuildHud` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var bannerTween = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it csharp/CombatHUD.Tactical.cs:106 — `tween` is a `Tween`, which implements `IDisposable`, and it is created here (line 106). Every use of it in `ShowKnockdown` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var tween = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it csharp/CombatModelLibrary.IntegratedOptics.cs:139 — `meshData` is a `MeshDataTool`, which implements `IDisposable`, and it is created here (line 139). Every use of it in `InspectIntegratedScope` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var meshData = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it csharp/EnemyOperator.cs:2114 — `flash` is a `Tween`, which implements `IDisposable`, and it is created here (line 2114). Every use of it in `BeginMuzzleFlash` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var flash = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it csharp/FreightTerminalWorld.Boss.cs:216 — `cleanup` is a `Tween`, which implements `IDisposable`, and it is created here (line 216). Every use of it in `SpawnWorldBossPulseEffect` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var cleanup = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it csharp/FreightTerminalWorld.cs:763 — `tween` is a `Tween`, which implements `IDisposable`, and it is created here (line 763). Every use of it in `SpawnTracer` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var tween = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it csharp/FreightTerminalWorld.cs:779 — `tween` is a `Tween`, which implements `IDisposable`, and it is created here (line 779). Every use of it in `SpawnImpact` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var tween = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it csharp/FreightTerminalWorld.cs:947 — `cleanup` is a `Tween`, which implements `IDisposable`, and it is created here (line 947). Every use of it in `SpawnExplosionEffect` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var cleanup = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it csharp/FreightTerminalWorld.cs:3291 — `config` is a `ConfigFile`, which implements `IDisposable`, and it is created here (line 3291). Every use of it in `LoadSettings` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var config = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it csharp/FreightTerminalWorld.cs:3314 — `config` is a `ConfigFile`, which implements `IDisposable`, and it is created here (line 3314). Every use of it in `SaveSettings` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var config = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it csharp/FreightTerminalWorld.cs:4133 — `dragProbe` is a `LootDropZone`, which implements `IDisposable`, and it is created here (line 4133). Every use of it in `ValidateLootFlow` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var dragProbe = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it csharp/FreightTerminalWorld.cs:4156 — `groundProbe` is a `LootDropZone`, which implements `IDisposable`, and it is created here (line 4156). Every use of it in `ValidateLootFlow` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var groundProbe = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it csharp/FreightTerminalWorld.Demolition.EnemyResponse.Diagnostics.cs:45 — `platform` is a `StaticBody3D`, which implements `IDisposable`, and it is created here (line 45). Every use of it in `ValidateDemolitionEnemyResponse` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var platform = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it csharp/FreightTerminalWorld.ExplosionOcclusion.Diagnostics.cs:69 — `roof` is a `StaticBody3D`, which implements `IDisposable`, and it is created here (line 69). Every use of it in `ValidateExplosionCover` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var roof = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it csharp/FreightTerminalWorld.ExplosionOcclusion.Diagnostics.cs:88 — `wall` is a `StaticBody3D`, which implements `IDisposable`, and it is created here (line 88). Every use of it in `ValidateExplosionCover` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var wall = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it csharp/FreightTerminalWorld.ExplosionOcclusion.Diagnostics.cs:113 — `lowerWall` is a `StaticBody3D`, which implements `IDisposable`, and it is created here (line 113). Every use of it in `ValidateExplosionCover` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var lowerWall = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it csharp/FreightTerminalWorld.ExplosionOcclusion.Diagnostics.cs:117 — `upperWall` is a `StaticBody3D`, which implements `IDisposable`, and it is created here (line 117). Every use of it in `ValidateExplosionCover` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var upperWall = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it csharp/FreightTerminalWorld.ExplosionOcclusion.Diagnostics.cs:172 — `shellFloor` is a `StaticBody3D`, which implements `IDisposable`, and it is created here (line 172). Every use of it in `ValidateExplosionCover` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var shellFloor = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it csharp/FreightTerminalWorld.Incendiary.Diagnostics.cs:31 — `platform` is a `StaticBody3D`, which implements `IDisposable`, and it is created here (line 31). Every use of it in `ValidateIncendiaryAiAvoidance` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var platform = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it csharp/FreightTerminalWorld.Incendiary.Diagnostics.cs:82 — `mateFire` is a `IncendiaryGrenade`, which implements `IDisposable`, and it is created here (line 82). Every use of it in `ValidateIncendiaryAiAvoidance` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var mateFire = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it csharp/FreightTerminalWorld.LanRoomDiscovery.Diagnostics.cs:12 — `permissionReceiver` is a `PacketPeerUdp`, which implements `IDisposable`, and it is created here (line 12). Every use of it in `ValidateLanRoomDiscovery` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var permissionReceiver = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it csharp/FreightTerminalWorld.Melee.Impact.cs:219 — `tween` is a `Tween`, which implements `IDisposable`, and it is created here (line 219). Every use of it in `ScheduleMeleeSurfaceMarkFade` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var tween = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it csharp/FreightTerminalWorld.Squad.cs:2368 — `cleanup` is a `Tween`, which implements `IDisposable`, and it is created here (line 2368). Every use of it in `ShowSquadMoveMarker` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var cleanup = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it csharp/FreightTerminalWorld.Squad.cs:2750 — `jetTween` is a `Tween`, which implements `IDisposable`, and it is created here (line 2750). Every use of it in `SpawnMedicSprayEffect` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var jetTween = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it csharp/FreightTerminalWorld.Squad.cs:2773 — `cleanup` is a `Tween`, which implements `IDisposable`, and it is created here (line 2773). Every use of it in `SpawnMedicSprayEffect` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var cleanup = …;`), which releases it at the end of the scope on every path including a throw.
  • + 12 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×35
  • Duplicated block (6 lines × 2) csharp/FreightTerminalWorld.ResidentialStairs.Diagnostics.cs:50 — csharp/FreightTerminalWorld.ResidentialStairs.Diagnostics.cs:50-55 | csharp/FreightTerminalWorld.Squad.cs:3276-3281 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/FreightTerminalWorld.ResidentialStairs.Diagnostics.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 (6 lines × 2) csharp/FreightTerminalWorld.Residential.Access.cs:605 — csharp/FreightTerminalWorld.Residential.Access.cs:605-610 | csharp/FreightTerminalWorld.cs:6591-6596 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/FreightTerminalWorld.Residential.Access.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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `csharp/FreightTerminalWorld.cs:6597` calls `GetPosition` and `csharp/FreightTerminalWorld.Residential.Access.cs:611` 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) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GlassDiagnostics.cs:392 — csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GlassDiagnostics.cs:392-397 | csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GlassDiagnostics.cs:480-485 — 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 `csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GlassDiagnostics.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.
  • Duplicated block (6 lines × 2) csharp/FreightTerminalWorld.cs:3918 — csharp/FreightTerminalWorld.cs:3918-3923 | csharp/FreightTerminalWorld.cs:4469-4474 — 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 lines × 2) csharp/CombatHUD.cs:11 — csharp/CombatHUD.cs:11-16 | csharp/PauseMenuView.cs:14-19 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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) csharp/FreightTerminalWorld.Squad.Traversal.Diagnostics.cs:191 — csharp/FreightTerminalWorld.Squad.Traversal.Diagnostics.cs:191-196 | csharp/FreightTerminalWorld.Squad.Traversal.Diagnostics.cs:234-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.
  • Duplicated block (6 lines × 2) csharp/DemolitionArenaLayout.TideglassReactor.cs:418 — csharp/DemolitionArenaLayout.TideglassReactor.cs:418-423 | csharp/DemolitionArenaLayout.cs:457-462 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/DemolitionArenaLayout.TideglassReactor.cs:418` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different 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 × 2) csharp/FirstPersonReloadProfileCatalog.cs:64 — csharp/FirstPersonReloadProfileCatalog.cs:64-69 | csharp/FirstPersonReloadProfileCatalog.cs:86-91 — 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 `csharp/FirstPersonReloadProfileCatalog.cs:64` 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 × 2) csharp/FreightTerminalWorld.Demolition.Network.cs:600 — csharp/FreightTerminalWorld.Demolition.Network.cs:600-605 | csharp/FreightTerminalWorld.Demolition.cs:565-570 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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) csharp/FreightTerminalWorld.Demolition.TideglassReactor.AssetDiagnostics.cs:335 — csharp/FreightTerminalWorld.Demolition.TideglassReactor.AssetDiagnostics.cs:335-340 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.Capture.cs:411-418 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/FreightTerminalWorld.Demolition.TideglassReactor.AssetDiagnostics.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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different 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 × 2) csharp/LowPolyBuildingArtBuilder.Architecture.cs:299 — csharp/LowPolyBuildingArtBuilder.Architecture.cs:299-304 | csharp/LowPolyBuildingArtBuilder.Architecture.cs:335-340 — 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 `csharp/LowPolyBuildingArtBuilder.Architecture.cs:299` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different 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 × 2) csharp/TacticalPlayer.cs:2182 — csharp/TacticalPlayer.cs:2182-2187 | csharp/TacticalPlayer.cs:2190-2195 — 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 (6 lines × 2) csharp/CombatModelLibrary.cs:2589 — csharp/CombatModelLibrary.cs:2589-2594 | csharp/ExtractionAircraftVisualRig.cs:54-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. 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 (6 lines × 2) scripts/blender/build_bazaar_crossing.py:2851 — scripts/blender/build_bazaar_crossing.py:2851-2856 | scripts/blender/build_bazaar_crossing.py:2888-2893 — 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 `scripts/blender/build_bazaar_crossing.py:2851` it begins part-way through the construct above it, so those exact lines 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) scripts/blender/build_bazaar_crossing.py:4953 — scripts/blender/build_bazaar_crossing.py:4953-4958 | scripts/blender/build_bazaar_crossing.py:5031-5036 — 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 `scripts/blender/build_bazaar_crossing.py:4953` it does not close everything it opens, so those exact lines 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) scripts/blender/build_hy3d_operator.py:493 — scripts/blender/build_hy3d_operator.py:493-498 | scripts/blender/build_hy3d_operator.py:504-509 — 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 lines × 2) scripts/blender/build_orbital_complex.py:297 — scripts/blender/build_orbital_complex.py:297-302 | scripts/blender/build_supplemental_reload_mechanisms.py:848-853 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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) scripts/blender/build_orbital_complex.py:519 — scripts/blender/build_orbital_complex.py:519-524 | scripts/blender/build_taradavies_ak47.py:806-811 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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) scripts/blender/build_orbital_complex.py:1254 — scripts/blender/build_orbital_complex.py:1254-1259 | scripts/blender/build_orbital_complex.py:1345-1350 — 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 lines × 2) scripts/blender/build_reloadable_quaternius_weapons.py:722 — scripts/blender/build_reloadable_quaternius_weapons.py:722-728 | scripts/blender/build_supplemental_reload_mechanisms.py:1023-1028 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `scripts/blender/build_reloadable_quaternius_weapons.py:722` it begins part-way through the construct above it, so those exact lines 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) scripts/blender/build_supplemental_reload_mechanisms.py:920 — scripts/blender/build_supplemental_reload_mechanisms.py:920-925 | scripts/blender/build_supplemental_reload_mechanisms.py:1024-1029 — 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, `scripts/blender/build_supplemental_reload_mechanisms.py:926` calls `tuple`, `reversed` and `scripts/blender/build_supplemental_reload_mechanisms.py:1030` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared 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) scripts/blender/build_tideglass_map_assets.py:404 — scripts/blender/build_tideglass_map_assets.py:404-409 | scripts/blender/build_tideglass_map_assets.py:505-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 `scripts/blender/build_tideglass_map_assets.py:404` it begins part-way through the construct above it, so those exact lines 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) scripts/blender/export_jianghai_old_city.py:723 — scripts/blender/export_jianghai_old_city.py:723-729 | scripts/blender/jianghai_enterable_interior_liners.py:117-122 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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) scripts/blender/build_demolition_device.py:490 — scripts/blender/build_demolition_device.py:490-495 | scripts/blender/build_field_use_props.py:850-855 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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) scripts/blender/build_extraction_aircraft.py:29 — scripts/blender/build_extraction_aircraft.py:29-34 | scripts/blender/generate_combat_models.py:27-32 — before extracting anything, compare `scripts/blender/build_extraction_aircraft.py` and `scripts/blender/generate_combat_models.py` 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. 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.
  • + 10 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×33
  • Duplicated block (7 lines × 2) csharp/FreightTerminalWorld.AiNavigation.Diagnostics.cs:71 — csharp/FreightTerminalWorld.AiNavigation.Diagnostics.cs:71-77 | csharp/FreightTerminalWorld.AiNavigation.Diagnostics.cs:93-99 — 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 (7 lines × 2) csharp/FreightTerminalWorld.cs:1921 — csharp/FreightTerminalWorld.cs:1921-1927 | csharp/FreightTerminalWorld.cs:1977-1983 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs:79 — csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs:79-85 | csharp/FreightTerminalWorld.Squad.GlassRescue.Diagnostics.cs:76-82 — before extracting anything, compare `csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs` and `csharp/FreightTerminalWorld.Squad.GlassRescue.Diagnostics.cs` as WHOLE FILES: this scan already matched 6 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 before the matched lines, `csharp/FreightTerminalWorld.Squad.GlassRescue.Diagnostics.cs:74` calls `SetProcess`, `SetPhysicsProcess` and `csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.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 (7 lines × 2) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Diagnostics.cs:246 — csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Diagnostics.cs:246-252 | csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:332-338 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Diagnostics.cs:246` 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 × 2) csharp/FreightTerminalWorld.AkModelDiagnostics.cs:343 — csharp/FreightTerminalWorld.AkModelDiagnostics.cs:343-349 | csharp/FreightTerminalWorld.AkModelDiagnostics.cs:374-380 — 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 `csharp/FreightTerminalWorld.AkModelDiagnostics.cs:343` it does not close everything it opens, so those 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, `csharp/FreightTerminalWorld.AkModelDiagnostics.cs:350` calls `Max` and `csharp/FreightTerminalWorld.AkModelDiagnostics.cs:381` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared 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) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs:777 — csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs:777-783 | csharp/FreightTerminalWorld.Residential.StreetArt.Diagnostics.cs:379-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. Read the line range as the matched WINDOW rather than a finished unit: at `csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs:777` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines 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) csharp/FreightTerminalWorld.Interdistrict.cs:802 — csharp/FreightTerminalWorld.Interdistrict.cs:802-808 | csharp/FreightTerminalWorld.RelayStations.cs:515-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 `csharp/FreightTerminalWorld.Interdistrict.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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different 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 × 2) csharp/FreightTerminalWorld.Level.cs:377 — csharp/FreightTerminalWorld.Level.cs:377-383 | csharp/FreightTerminalWorld.Level.cs:391-397 — 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) csharp/FreightTerminalWorld.Melee.Combat.Diagnostics.cs:534 — csharp/FreightTerminalWorld.Melee.Combat.Diagnostics.cs:534-540 | csharp/TacticalPlayer.AuthoredVisuals.cs:352-358 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/FreightTerminalWorld.Melee.Combat.Diagnostics.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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different 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 × 2) csharp/FreightTerminalWorld.Residential.cs:1516 — csharp/FreightTerminalWorld.Residential.cs:1516-1522 | csharp/FreightTerminalWorld.Residential.cs:1543-1549 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) csharp/GrenadeVisualFactory.cs:8 — csharp/GrenadeVisualFactory.cs:8-14 | csharp/GrenadeVisualFactory.cs:58-64 — 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 `csharp/GrenadeVisualFactory.cs:8` it does not close everything it opens, so those exact lines 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) csharp/LowPolyBuildingArtBuilder.Profiles.cs:89 — csharp/LowPolyBuildingArtBuilder.Profiles.cs:89-95 | csharp/LowPolyBuildingArtBuilder.Profiles.cs:107-113 — 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 `csharp/LowPolyBuildingArtBuilder.Profiles.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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different 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 × 2) csharp/InventoryModelPreview.cs:517 — csharp/InventoryModelPreview.cs:517-523 | csharp/InventoryModelPreview.cs:557-563 — 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 `csharp/InventoryModelPreview.cs:517` 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 × 2) csharp/SoundLab.cs:668 — csharp/SoundLab.cs:668-674 | csharp/SoundLab.cs:721-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 `csharp/SoundLab.cs:668` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those 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) csharp/DemolitionArenaLayout.cs:746 — csharp/DemolitionArenaLayout.cs:746-752 | csharp/DemolitionRetakeDistribution.Diagnostics.cs:417-423 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (7 lines × 2) csharp/FreightTerminalWorld.Residential.Access.cs:1059 — csharp/FreightTerminalWorld.Residential.Access.cs:1059-1065 | csharp/FreightTerminalWorld.RoofAccess.cs:578-584 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (7 lines × 2) scripts/blender/add_hy3d_palm_markers.py:202 — scripts/blender/add_hy3d_palm_markers.py:202-208 | scripts/blender/author_hy3d_rifle_carry.py:114-120 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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) scripts/blender/build_djmaesen_smg45.py:356 — scripts/blender/build_djmaesen_smg45.py:356-362 | scripts/blender/build_djmaesen_smg45.py:536-542 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) scripts/blender/build_field_use_props.py:180 — scripts/blender/build_field_use_props.py:180-186 | scripts/blender/build_melee_weapons.py:117-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. Note first that the copies are not typed on the same thing: the declarations holding them bind `parent` to `bpy.types.Object | None` in one and `bpy.types.Object` 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 lines × 2) scripts/blender/build_orbital_complex_underground.py:818 — scripts/blender/build_orbital_complex_underground.py:818-824 | scripts/blender/build_orbital_complex_underground.py:1153-1160 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) scripts/blender/build_reloadable_gsh18.py:933 — scripts/blender/build_reloadable_gsh18.py:933-939 | scripts/blender/build_reloadable_quaternius_weapons.py:1075-1081 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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) scripts/blender/build_taradavies_ak47.py:544 — scripts/blender/build_taradavies_ak47.py:544-550 | scripts/blender/build_taradavies_ak47.py:585-591 — 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 `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) scripts/blender/build_tideglass_map_assets.py:211 — scripts/blender/build_tideglass_map_assets.py:211-217 | scripts/blender/build_trey_modular_industrial.py:1622-1628 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `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) scripts/blender/build_tideglass_map_assets.py:750 — scripts/blender/build_tideglass_map_assets.py:750-756 | scripts/blender/build_trey_modular_industrial.py:2285-2291 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `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) scripts/blender/rebind_hy3d_hands.py:567 — scripts/blender/rebind_hy3d_hands.py:567-573 | scripts/blender/repair_magpie_right_hand.py:127-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 both call sites, so a change lands once.
  • + 8 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×28
  • Duplicated block (10 lines × 2) csharp/FragGrenade.cs:90 — csharp/FragGrenade.cs:90-99 | csharp/SmokeGrenade.cs:127-136 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/FragGrenade.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 (10 lines × 2) csharp/FreightTerminalWorld.Squad.Tactics.Diagnostics.cs:62 — csharp/FreightTerminalWorld.Squad.Tactics.Diagnostics.cs:62-71 | csharp/FreightTerminalWorld.Squad.Tactics.Diagnostics.cs:83-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.
  • Duplicated block (10 lines × 2) csharp/EnemyOperator.AuthoredVisuals.cs:105 — csharp/EnemyOperator.AuthoredVisuals.cs:105-114 | csharp/SquadMate.AuthoredVisuals.cs:107-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 both call sites, so a change lands once.
  • Duplicated block (10 lines × 2) csharp/FreightTerminalWorld.Demolition.HarborLocks.Diagnostics.cs:167 — csharp/FreightTerminalWorld.Demolition.HarborLocks.Diagnostics.cs:167-176 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.Diagnostics.cs:582-591 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/FreightTerminalWorld.Demolition.HarborLocks.Diagnostics.cs:167` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines 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) csharp/FreightTerminalWorld.Residential.Access.cs:576 — csharp/FreightTerminalWorld.Residential.Access.cs:576-585 | csharp/FreightTerminalWorld.Residential.Access.cs:799-808 — 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, `csharp/FreightTerminalWorld.Residential.Access.cs:572` calls `ToSignal`, `GetTree`, `Min` and `csharp/FreightTerminalWorld.Residential.Access.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 (10 lines × 2) csharp/FreightTerminalWorld.SurvivalZombies.cs:94 — csharp/FreightTerminalWorld.SurvivalZombies.cs:94-103 | csharp/FreightTerminalWorld.cs:2178-2187 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/FreightTerminalWorld.SurvivalZombies.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.
  • Duplicated block (10 lines × 2) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.DensityDiagnostics.cs:517 — csharp/FreightTerminalWorld.Demolition.BazaarCrossing.DensityDiagnostics.cs:517-526 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.DensityDiagnostics.cs:939-948 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 lines × 2) csharp/FreightTerminalWorld.Extraction.Network.Authority.cs:57 — csharp/FreightTerminalWorld.Extraction.Network.Authority.cs:57-66 | csharp/FreightTerminalWorld.Melee.Geometry.cs:121-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.
  • Duplicated block (10 lines × 2) csharp/FreightTerminalWorld.OpticsCapture.cs:58 — csharp/FreightTerminalWorld.OpticsCapture.cs:58-67 | csharp/FreightTerminalWorld.WeaponPoseDiagnostics.cs:11-20 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (10 lines × 2) csharp/LowPolyBuildingArtBuilder.Architecture.cs:155 — csharp/LowPolyBuildingArtBuilder.Architecture.cs:155-164 | csharp/LowPolyBuildingArtBuilder.Architecture.cs:204-213 — 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 (10 lines × 2) csharp/EnemyOperator.cs:1770 — csharp/EnemyOperator.cs:1770-1779 | csharp/EnemyOperator.cs:1817-1826 — 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 `csharp/EnemyOperator.cs:1770` 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 × 2) csharp/FreightTerminalWorld.Demolition.Device.cs:793 — csharp/FreightTerminalWorld.Demolition.Device.cs:793-802 | csharp/FreightTerminalWorld.Demolition.Strategy.cs:598-607 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/FreightTerminalWorld.Demolition.Device.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 (10 lines × 2) csharp/FreightTerminalWorld.Demolition.TideglassReactor.Diagnostics.cs:437 — csharp/FreightTerminalWorld.Demolition.TideglassReactor.Diagnostics.cs:437-447 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.Diagnostics.cs:450-459 — 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 `csharp/FreightTerminalWorld.Demolition.TideglassReactor.Diagnostics.cs:437` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different 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 × 2) csharp/FreightTerminalWorld.ExplosionOcclusion.Diagnostics.cs:71 — csharp/FreightTerminalWorld.ExplosionOcclusion.Diagnostics.cs:71-80 | csharp/FreightTerminalWorld.ExplosionOcclusion.Diagnostics.cs:90-99 — 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 `csharp/FreightTerminalWorld.ExplosionOcclusion.Diagnostics.cs:71` 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, `csharp/FreightTerminalWorld.ExplosionOcclusion.Diagnostics.cs:81` calls `ApplyAircraftStrike` and `csharp/FreightTerminalWorld.ExplosionOcclusion.Diagnostics.cs:100` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared 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) csharp/FreightTerminalWorld.Survival.cs:203 — csharp/FreightTerminalWorld.Survival.cs:203-212 | csharp/FreightTerminalWorld.Survival.cs:216-225 — 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 `csharp/FreightTerminalWorld.Survival.cs:203` it does not close everything it opens, so those exact lines 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) csharp/TacticalPlayer.Melee.Combat.cs:495 — csharp/TacticalPlayer.Melee.Combat.cs:495-504 | csharp/TacticalPlayer.Melee.Combat.cs:513-522 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (10 lines × 2) csharp/FreightTerminalWorld.Residential.Access.cs:827 — csharp/FreightTerminalWorld.Residential.Access.cs:827-836 | csharp/FreightTerminalWorld.cs:6591-6600 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (10 lines × 2) csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:1216 — csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:1216-1225 | csharp/FreightTerminalWorld.Demolition.Strategy.cs:434-443 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (10 lines × 2) scripts/blender/author_hy3d_pistol_carry.py:113 — scripts/blender/author_hy3d_pistol_carry.py:113-122 | scripts/blender/author_hy3d_rifle_prone.py:100-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 both call sites, so a change lands once.
  • Duplicated block (10 lines × 2) scripts/blender/build_animated_bamen_operator.py:453 — scripts/blender/build_animated_bamen_operator.py:453-462 | scripts/blender/build_animated_bamen_operator.py:479-488 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (10 lines × 2) scripts/blender/build_animated_reload_arms.py:2632 — scripts/blender/build_animated_reload_arms.py:2632-2641 | scripts/blender/build_tide_hunter_monster.py:221-230 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `scripts/blender/build_animated_reload_arms.py:2632` it does not close everything it opens, so those exact lines 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) scripts/blender/build_djmaesen_smg45.py:418 — scripts/blender/build_djmaesen_smg45.py:418-427 | scripts/blender/build_operator_hand_kits.py:293-302 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (10 lines × 2) scripts/blender/build_djmaesen_smg45.py:454 — scripts/blender/build_djmaesen_smg45.py:454-463 | scripts/blender/build_first_person_arms.py:442-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 both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `scripts/blender/build_djmaesen_smg45.py:454` it does not close everything it opens, so those exact lines 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) scripts/blender/build_melee_weapons.py:360 — scripts/blender/build_melee_weapons.py:360-369 | scripts/blender/build_orbital_complex_underground.py:223-232 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (10 lines × 2) scripts/blender/build_quaternius_buildings_pack.py:127 — scripts/blender/build_quaternius_buildings_pack.py:127-136 | scripts/blender/build_tideglass_map_assets.py:92-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. 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.
  • + 3 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×26
  • Duplicated block (9 lines × 2) csharp/FreightTerminalWorld.Demolition.Network.Diagnostics.cs:229 — csharp/FreightTerminalWorld.Demolition.Network.Diagnostics.cs:229-237 | csharp/FreightTerminalWorld.Demolition.Network.Diagnostics.cs:257-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.
  • Duplicated block (9 lines × 2) csharp/FreightTerminalWorld.Interdistrict.cs:718 — csharp/FreightTerminalWorld.Interdistrict.cs:718-726 | csharp/TacticalPlayer.Traversal.cs:374-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 both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `csharp/FreightTerminalWorld.Interdistrict.cs:718` 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) csharp/FreightIndustrialInteriorBuilder.cs:365 — csharp/FreightIndustrialInteriorBuilder.cs:365-373 | csharp/TrainingRangeArenaBuilder.cs:550-558 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/FreightIndustrialInteriorBuilder.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.
  • Duplicated block (9 lines × 2) csharp/FreightIndustrialInteriorBuilder.cs:376 — csharp/FreightIndustrialInteriorBuilder.cs:376-384 | csharp/InteractiveBuildingDoor.cs:505-513 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/FreightIndustrialInteriorBuilder.cs:376` 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) csharp/FreightTerminalWorld.Demolition.cs:146 — csharp/FreightTerminalWorld.Demolition.cs:146-154 | csharp/FreightTerminalWorld.Squad.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. Read the line range as the matched WINDOW rather than a finished unit: at `csharp/FreightTerminalWorld.Demolition.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 (9 lines × 2) csharp/FreightTerminalWorld.Residential.Access.cs:498 — csharp/FreightTerminalWorld.Residential.Access.cs:498-506 | csharp/FreightTerminalWorld.Residential.Access.cs:526-534 — 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) csharp/LowPolyBuildingArtBuilder.Architecture.cs:309 — csharp/LowPolyBuildingArtBuilder.Architecture.cs:309-317 | csharp/LowPolyBuildingArtBuilder.Architecture.cs:356-364 — 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 lines × 2) csharp/FreightTerminalWorld.Melee.Combat.Diagnostics.cs:185 — csharp/FreightTerminalWorld.Melee.Combat.Diagnostics.cs:185-193 | csharp/FreightTerminalWorld.Melee.Combat.Diagnostics.cs:227-235 — 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, `csharp/FreightTerminalWorld.Melee.Combat.Diagnostics.cs:194` calls `IsEqualApprox` and `csharp/FreightTerminalWorld.Melee.Combat.Diagnostics.cs:236` 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 × 2) csharp/FreightTerminalWorld.Demolition.TideglassReactor.Capture.cs:281 — csharp/FreightTerminalWorld.Demolition.TideglassReactor.Capture.cs:281-289 | csharp/FreightTerminalWorld.OperatorCarry.Diagnostics.cs:504-512 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 lines × 2) csharp/ResidentialSearchableFurniture.cs:152 — csharp/ResidentialSearchableFurniture.cs:152-160 | csharp/ResidentialSearchableFurniture.cs:164-172 — 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 `csharp/ResidentialSearchableFurniture.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 × 2) csharp/SquadMate.Traversal.cs:452 — csharp/SquadMate.Traversal.cs:452-460 | csharp/TacticalPlayer.MovementInput.cs:265-273 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/SquadMate.Traversal.cs:452` it does not close everything it opens, so those exact lines 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) csharp/TacticalPlayer.AnimatedReloadArms.cs:201 — csharp/TacticalPlayer.AnimatedReloadArms.cs:201-209 | csharp/TacticalPlayer.AuthoredVisuals.cs:1082-1090 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 lines × 2) csharp/TacticalPlayer.cs:1037 — csharp/TacticalPlayer.cs:1037-1045 | csharp/TacticalPlayer.cs:1121-1129 — 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 before the matched lines, `csharp/TacticalPlayer.cs:1121` calls `Vector3` and `csharp/TacticalPlayer.cs:1037` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared 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) csharp/TacticalPlayer.ReloadPresentation.cs:372 — csharp/TacticalPlayer.ReloadPresentation.cs:372-382 | csharp/TacticalPlayer.ReloadPresentation.cs:420-428 — 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 `csharp/TacticalPlayer.ReloadPresentation.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 (9 lines × 2) csharp/CombatModelLibrary.cs:312 — csharp/CombatModelLibrary.cs:312-320 | csharp/TacticalPlayer.WeaponPose.cs:647-655 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (9 lines × 2) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Diagnostics.cs:409 — csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Diagnostics.cs:409-417 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.DensityDiagnostics.cs:560-568 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (9 lines × 2) REDACTED:788 — REDACTED:788-796 | scripts/blender/build_jianghai_valley_environment.py:2192-2200 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 lines × 2) scripts/blender/build_authored_optics.py:169 — scripts/blender/build_authored_optics.py:169-177 | scripts/blender/build_nisu_m4a1.py:207-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 `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) scripts/blender/build_bazaar_crossing.py:7008 — scripts/blender/build_bazaar_crossing.py:7008-7016 | scripts/blender/build_bazaar_crossing.py:7118-7126 — 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 `scripts/blender/build_bazaar_crossing.py:7008` it does not close everything it opens, so those 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) scripts/blender/build_demolition_device.py:385 — scripts/blender/build_demolition_device.py:385-393 | scripts/blender/build_field_use_props.py:719-727 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 lines × 2) scripts/blender/build_extraction_aircraft.py:460 — scripts/blender/build_extraction_aircraft.py:460-468 | scripts/blender/build_extraction_aircraft.py:469-477 — 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) scripts/blender/build_hy3d_operator.py:352 — scripts/blender/build_hy3d_operator.py:352-360 | scripts/blender/rebind_hy3d_hands.py:102-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. 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: `Iterable` names `collections.abc` in one and `typing` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (9 lines × 2) scripts/blender/build_operations_office_set.py:637 — scripts/blender/build_operations_office_set.py:637-645 | scripts/blender/build_orbital_complex.py:1719-1727 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `scripts/blender/build_operations_office_set.py:637` it does not close everything it opens, so those exact lines 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) scripts/blender/build_operator_hand_kits.py:453 — scripts/blender/build_operator_hand_kits.py:453-461 | scripts/blender/build_operator_hand_kits.py:626-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.
  • Duplicated block (9 lines × 2) scripts/blender/build_reloadable_gsh18.py:428 — scripts/blender/build_reloadable_gsh18.py:428-436 | scripts/blender/build_supplemental_reload_mechanisms.py:893-901 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `scripts/blender/build_reloadable_gsh18.py:428` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • + 1 more in this group — see findings.md.
D3 · God Classes · TooManyMethods · ×19
  • TooManyMethods: FreightTerminalWorld csharp/FreightTerminalWorld.cs — TooManyMethods — 59758 significant lines (blank, comment-only and punctuation-only lines excluded), 1785 methods, declared across 180 files: csharp/FreightTerminalWorld.cs (129), csharp/FreightTerminalWorld.Squad.cs (107), csharp/FreightTerminalWorld.Level.cs (45), csharp/FreightTerminalWorld.Residential.cs (43), +176 more file(s). The bar is 30 methods; this is 1755 over it, 59.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: TacticalPlayer csharp/TacticalPlayer.cs — TooManyMethods — 9796 significant lines (blank, comment-only and punctuation-only lines excluded), 466 methods, declared across 34 files: csharp/TacticalPlayer.cs (88), csharp/TacticalPlayer.AuthoredVisuals.cs (37), csharp/TacticalPlayer.RenderPresentation.cs (29), csharp/TacticalPlayer.WeaponSlots.cs (27), +30 more file(s). The bar is 30 methods; this is 436 over it, 15.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: CombatHUD csharp/CombatHUD.cs — TooManyMethods — 5488 significant lines (blank, comment-only and punctuation-only lines excluded), 331 methods, declared across 22 files: csharp/CombatHUD.cs (57), csharp/CombatHUD.Deployment.cs (40), csharp/CombatHUD.OperationsOffice.cs (35), csharp/CombatHUD.Squad.cs (33), +18 more file(s). The bar is 30 methods; this is 301 over it, 11.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: EnemyOperator csharp/EnemyOperator.cs — TooManyMethods — 4109 significant lines (blank, comment-only and punctuation-only lines excluded), 243 methods, declared across 23 files: csharp/EnemyOperator.cs (64), csharp/EnemyOperator.Pursuit.cs (29), csharp/EnemyOperator.Pursuit.Navigation.cs (20), csharp/EnemyOperator.Pursuit.Motor.cs (13), +19 more file(s). The bar is 30 methods; this is 213 over it, 8.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: SquadMate csharp/SquadMate.cs — TooManyMethods — 3817 significant lines (blank, comment-only and punctuation-only lines excluded), 205 methods, declared across 17 files: csharp/SquadMate.cs (53), csharp/SquadMate.Combat.cs (35), csharp/SquadMate.Traversal.cs (24), csharp/SquadMate.Sustainment.Inventory.cs (22), +13 more file(s). The bar is 30 methods; this is 175 over it, 6.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: SquadNetwork csharp/SquadNetwork.Demolition.cs — TooManyMethods — 2366 significant lines (blank, comment-only and punctuation-only lines excluded), 165 methods, declared across 13 files: csharp/SquadNetwork.Demolition.cs (32), csharp/SquadNetwork.cs (27), csharp/SquadNetwork.Extraction.World.cs (19), csharp/SquadNetwork.Extraction.cs (18), +9 more file(s). The bar is 30 methods; this is 135 over it, 5.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: DemolitionArenaLayout csharp/DemolitionArenaLayout.BazaarCrossing.cs — TooManyMethods — 1996 significant lines (blank, comment-only and punctuation-only lines excluded), 110 methods, declared across 6 files: csharp/DemolitionArenaLayout.BazaarCrossing.cs (39), csharp/DemolitionArenaLayout.TideglassReactor.cs (25), csharp/DemolitionArenaLayout.cs (22), csharp/DemolitionArenaLayout.HarborLocks.cs (11), +2 more file(s). The bar is 30 methods; this is 80 over it, 3.67× 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: CombatModelLibrary csharp/CombatModelLibrary.cs — TooManyMethods — 1600 significant lines (blank, comment-only and punctuation-only lines excluded), 95 methods, declared across 10 files: csharp/CombatModelLibrary.cs (56), csharp/CombatModelLibrary.FirstPerson.cs (14), csharp/CombatModelLibrary.IntegratedOptics.cs (5), csharp/CombatModelLibrary.DemolitionDevice.cs (4), +6 more file(s). The bar is 30 methods; this is 65 over it, 3.17× 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: SoundLab csharp/SoundLab.cs — TooManyMethods — 798 significant lines (blank, comment-only and punctuation-only lines excluded), 52 methods, declared across 3 files: csharp/SoundLab.cs (39), csharp/SoundLab.Recordings.cs (12), csharp/SoundLab.Music.cs (1). The bar is 30 methods; this is 22 over it, 1.73× 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: DestructibleAircraft csharp/DestructibleAircraft.Combat.cs — TooManyMethods — 559 significant lines (blank, comment-only and punctuation-only lines excluded), 47 methods, declared across 2 files: csharp/DestructibleAircraft.Combat.cs (28), csharp/DestructibleAircraft.cs (19). The bar is 30 methods; this is 17 over it, 1.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: BreakableGlassField csharp/BreakableGlassField.cs — TooManyMethods — 718 significant lines (blank, comment-only and punctuation-only lines excluded), 44 methods, declared across 4 files: csharp/BreakableGlassField.cs (22), csharp/BreakableGlassField.Network.cs (10), csharp/BreakableGlassField.Movement.cs (9), csharp/BreakableGlassField.Diagnostics.cs (3). The bar is 30 methods; this is 14 over it, 1.47× 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: TrainingRangeArmoryView csharp/TrainingRangeArmoryView.cs — TooManyMethods — 390 significant lines (blank, comment-only and punctuation-only lines excluded), 37 methods, declared across 3 files: csharp/TrainingRangeArmoryView.cs (19), csharp/TrainingRangeArmoryView.Catalog.cs (13), csharp/TrainingRangeArmoryView.Presentation.cs (5). The bar is 30 methods; this is 7 over it, 1.23× 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: OrbitalComplexLayoutValidator csharp/ExtractionMaps/OrbitalComplex/OrbitalComplexLayoutValidator.cs — TooManyMethods — 510 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. 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: InteractiveBuildingDoor csharp/InteractiveBuildingDoor.cs — TooManyMethods — 616 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods, declared across 3 files: csharp/InteractiveBuildingDoor.cs (18), csharp/InteractiveBuildingDoor.DoubleHinged.cs (12), csharp/InteractiveBuildingDoor.Visibility.cs (5). The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: LowPolyBuildingArtBuilder csharp/LowPolyBuildingArtBuilder.Architecture.cs — TooManyMethods — 922 significant lines (blank, comment-only and punctuation-only lines excluded), 34 methods, declared across 3 files: csharp/LowPolyBuildingArtBuilder.Architecture.cs (16), csharp/LowPolyBuildingArtBuilder.cs (11), csharp/LowPolyBuildingArtBuilder.Profiles.cs (7). The bar is 30 methods; this is 4 over it, 1.13× 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: DemolitionArenaBuilder csharp/DemolitionArenaBuilder.cs — TooManyMethods — 743 significant lines (blank, comment-only and punctuation-only lines excluded), 34 methods, declared across 5 files: csharp/DemolitionArenaBuilder.cs (16), csharp/DemolitionArenaBuilder.BazaarCrossing.cs (6), csharp/DemolitionArenaBuilder.TideglassReactor.cs (5), csharp/DemolitionArenaBuilder.PropCollision.cs (4), +1 more file(s). The bar is 30 methods; this is 4 over it, 1.13× 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: OperationsOfficeBackdrop csharp/OperationsOfficeBackdrop.cs — TooManyMethods — 485 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods, declared across 3 files: csharp/OperationsOfficeBackdrop.cs (20), csharp/OperationsOfficeBackdrop.Environment.cs (8), csharp/OperationsOfficeBackdrop.Diagnostics.cs (5). The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: DemolitionRoutePlanner csharp/DemolitionRoutePlanner.cs — TooManyMethods — 596 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods, declared across 2 files: csharp/DemolitionRoutePlanner.cs (28), csharp/DemolitionRoutePlanner.Retake.cs (3). The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: DemolitionBriefingView csharp/DemolitionBriefingView.cs — TooManyMethods — 402 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
AX2 · Stateful singletons · Process-global static state · ×17
  • Process-global static state: BreakableGlassField csharp/BreakableGlassField.cs:10 — `BreakableGlassField` 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 (_unitBox, _unitPane, _glassBreakSound; e.g. `_unitBox` at line 22). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: DeploymentMapRuntime csharp/DeploymentMapRuntime.cs:18 — `DeploymentMapRuntime` 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 (_selectedWorldSeed, _pendingDeployment, _selectedMapId; e.g. `_selectedWorldSeed` at line 94). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: EnemyOperator csharp/EnemyOperator.AirborneCombat.cs:17 — `EnemyOperator` 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 (SharedBoxMeshes, SharedCapsuleMeshes, SharedCylinderMeshes; e.g. `SharedBoxMeshes` at line 357). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: FreightTerminalWorld csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Diagnostics.cs:10 — `FreightTerminalWorld` 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 (_extractionNetworkDiagnosticRuntimeId, _extractionNetworkDiagnosticLobbyWaited, _extractionNetworkDiagnosticMutationApplied, _extractionNetworkDiagnosticTombstoneGuarded, _extractionNetworkDiagnosticDownMotionGuarded, _extractionNetworkDiagnosticDownPeerId; e.g. `_extractionNetworkDiagnosticRuntimeId` at line 35). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: JianghaiLoadingDiagnosticRuntime csharp/FreightTerminalWorld.Refinery.LoadingDiagnostics.cs:8 — `JianghaiLoadingDiagnosticRuntime` 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 (PreloadWaitMilliseconds, PreloadSnapshot, ReloadStartedAtMilliseconds, ReloadPending; e.g. `PreloadWaitMilliseconds` at line 19). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: GeneratedInventoryArt csharp/GeneratedInventoryArt.cs:11 — `GeneratedInventoryArt` 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 (TextureCache, ImageCache, RegionCache; e.g. `TextureCache` at line 68). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: HudPackedSceneCache csharp/HudPackedSceneCache.cs:13 — `HudPackedSceneCache` 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 (Scenes; e.g. `Scenes` at line 31). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: InventoryModelPreview csharp/InventoryModelPreview.cs:16 — `InventoryModelPreview` 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 (_operatorSky, _compactSky; e.g. `_operatorSky` at line 168). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: JianghaiMapPreloadCache csharp/JianghaiMapPreloadCache.cs:33 — `JianghaiMapPreloadCache` 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 (_releaseWhenLoaded, _packedScene, _error, _progress, _pollCount, _lastElapsedMilliseconds; e.g. `_releaseWhenLoaded` at line 65). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: LanternCanalPreloadCache csharp/LanternCanalPreloadCache.cs:10 — `LanternCanalPreloadCache` 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 (Requested, Ready, YieldedFrames, LoadMilliseconds; e.g. `Requested` at line 28). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: LootBackpackVisual csharp/LootBackpackVisual.cs:7 — `LootBackpackVisual` 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 (SharedBoxMeshes; e.g. `SharedBoxMeshes` at line 127). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: ResidentialAuthoredPropLibrary csharp/ResidentialAuthoredPropLibrary.cs:11 — `ResidentialAuthoredPropLibrary` 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 (Scenes, FailedScenePaths; e.g. `Scenes` at line 189). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: ResidentialRelayStation csharp/ResidentialRelayStation.cs:19 — `ResidentialRelayStation` 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 (SharedBoxes; e.g. `SharedBoxes` at line 26). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: ResidentialSearchableFurniture csharp/ResidentialSearchableFurniture.cs:15 — `ResidentialSearchableFurniture` 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 (SharedBoxMeshes; e.g. `SharedBoxMeshes` at line 22). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: ResidentialSupplyCache csharp/ResidentialSupplyCache.cs:18 — `ResidentialSupplyCache` 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 (SharedFallbackMeshes, _sharedChestScene, _sharedClosedMesh, _sharedOpenedMesh, _sharedOpenAnimationMeshes, _sharedVisiblePartCount; e.g. `SharedFallbackMeshes` at line 79). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: SoundLab csharp/SoundLab.cs:6 — `SoundLab` 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 (WeaponShotCache, MeleeSwingCache, MeleeSurfaceImpactCache, _openingCombatTheme; e.g. `WeaponShotCache` at line 105). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: TacticalSurfaceLibrary csharp/TacticalSurfaceLibrary.cs:5 — `TacticalSurfaceLibrary` 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 (_fabricWeaveTexture, _weaponFinishTexture; e.g. `_fabricWeaveTexture` at line 62). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×17
  • Duplicated block (13 lines × 2) csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs:94 — csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs:94-106 | csharp/FreightTerminalWorld.Squad.GlassRescue.Diagnostics.cs:91-103 — before extracting anything, compare `csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs` and `csharp/FreightTerminalWorld.Squad.GlassRescue.Diagnostics.cs` as WHOLE FILES: this scan already matched 6 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.
  • Duplicated block (13 lines × 2) csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Diagnostics.cs:626 — csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Diagnostics.cs:626-638 | csharp/MissionDirector.cs:450-462 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, 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 (13 lines × 2) csharp/FreightTerminalWorld.Demolition.Buy.Diagnostics.cs:279 — csharp/FreightTerminalWorld.Demolition.Buy.Diagnostics.cs:279-291 | csharp/FreightTerminalWorld.ReadmeCapture.cs:95-107 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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) csharp/FreightTerminalWorld.Demolition.HarborLocks.Diagnostics.cs:244 — csharp/FreightTerminalWorld.Demolition.HarborLocks.Diagnostics.cs:244-256 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:1057-1069 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/FreightTerminalWorld.Demolition.HarborLocks.Diagnostics.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 (13 lines × 2) csharp/TacticalPlayer.Demolition.cs:57 — csharp/TacticalPlayer.Demolition.cs:57-69 | csharp/TacticalPlayer.TrainingRange.cs:74-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 both call sites, so a change lands once.
  • Duplicated block (13 lines × 2) csharp/DemolitionArenaLayout.TideglassReactor.cs:431 — csharp/DemolitionArenaLayout.TideglassReactor.cs:431-443 | csharp/DemolitionArenaLayout.cs:470-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 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 (13 lines × 2) csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Diagnostics.cs:362 — csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Diagnostics.cs:362-374 | csharp/FreightTerminalWorld.AiNavigation.Diagnostics.cs:13-25 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, 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) csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Diagnostics.cs:360 — csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Diagnostics.cs:360-372 | csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs:11-23 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, 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) csharp/FreightTerminalWorld.Residential.StreetArt.Diagnostics.cs:161 — csharp/FreightTerminalWorld.Residential.StreetArt.Diagnostics.cs:161-174 | csharp/FreightTerminalWorld.ResidentialSurvival.Diagnostics.cs:19-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 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 (13 lines × 2) csharp/TacticalPlayer.AuthoredVisuals.cs:621 — csharp/TacticalPlayer.AuthoredVisuals.cs:621-633 | csharp/TacticalPlayer.AuthoredVisuals.cs:636-648 — 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 `csharp/TacticalPlayer.AuthoredVisuals.cs:621` 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 (13 lines × 2) REDACTED:434 — REDACTED:434-446 | scripts/blender/export_jianghai_old_city.py:1181-1193 — before extracting anything, compare `REDACTED` and `scripts/blender/export_jianghai_old_city.py` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 507 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 `REDACTED:434` it begins part-way through the construct above it, so those 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) scripts/blender/build_bazaar_crossing.py:6005 — scripts/blender/build_bazaar_crossing.py:6005-6017 | scripts/blender/build_bazaar_crossing.py:6794-6806 — 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) scripts/blender/build_bazaar_crossing.py:7694 — scripts/blender/build_bazaar_crossing.py:7694-7706 | scripts/blender/build_bazaar_crossing.py:7801-7813 — 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) scripts/blender/build_jianghai_valley_environment.py:2943 — scripts/blender/build_jianghai_valley_environment.py:2943-2955 | scripts/blender/export_jianghai_old_city.py:2374-2386 — before extracting anything, compare `scripts/blender/build_jianghai_valley_environment.py` and `scripts/blender/export_jianghai_old_city.py` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 759 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) scripts/blender/build_orbital_complex_underground.py:233 — scripts/blender/build_orbital_complex_underground.py:233-245 | scripts/blender/build_orbital_complex_underground.py:282-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. 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 (13 lines × 2) scripts/blender/build_reloadable_quaternius_weapons.py:675 — scripts/blender/build_reloadable_quaternius_weapons.py:675-687 | scripts/blender/build_reloadable_scarl.py:250-262 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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) scripts/blender/build_tideglass_map_assets.py:222 — scripts/blender/build_tideglass_map_assets.py:222-234 | scripts/blender/build_trey_modular_industrial.py:1632-1644 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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.
D17 · Explicit Debt · Dead code · ×15
  • Dead code: RemoveStagingNode csharp/CombatModelLibrary.cs:2596 — Method RemoveStagingNode — Roslyn's SymbolFinder walked every project the solution loads, including OperationSteelTide, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: FirstPersonArmRigSnapshot csharp/FirstPersonArmPoseCatalog.cs:18 — NamedType FirstPersonArmRigSnapshot — Roslyn's SymbolFinder walked every project the solution loads, including OperationSteelTide, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: WaitForMeleeAttack csharp/FreightTerminalWorld.Melee.Diagnostics.cs:237 — Method WaitForMeleeAttack — Roslyn's SymbolFinder walked every project the solution loads, including OperationSteelTide, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: HandleSurvivalHits csharp/FreightTerminalWorld.SurvivalZombies.cs:161 — Method HandleSurvivalHits — Roslyn's SymbolFinder walked every project the solution loads, including OperationSteelTide, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: ReviveTrainingRangeBot csharp/FreightTerminalWorld.TrainingRange.cs:489 — Method ReviveTrainingRangeBot — Roslyn's SymbolFinder walked every project the solution loads, including OperationSteelTide, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: InspectAnimatedReloadLeftArmPoseForDiagnostics csharp/TacticalPlayer.AnimatedReloadArms.cs:32 — Method InspectAnimatedReloadLeftArmPoseForDiagnostics — Roslyn's SymbolFinder walked every project the solution loads, including OperationSteelTide, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: InspectSidearmReloadEndpointPoseForDiagnostics csharp/TacticalPlayer.AnimatedReloadArms.cs:54 — Method InspectSidearmReloadEndpointPoseForDiagnostics — Roslyn's SymbolFinder walked every project the solution loads, including OperationSteelTide, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: InspectSidearmPresentationForDiagnostics csharp/TacticalPlayer.AuthoredVisuals.cs:232 — Method InspectSidearmPresentationForDiagnostics — Roslyn's SymbolFinder walked every project the solution loads, including OperationSteelTide, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: InspectWeaponPresentationForDiagnostics csharp/TacticalPlayer.AuthoredVisuals.cs:268 — Method InspectWeaponPresentationForDiagnostics — Roslyn's SymbolFinder walked every project the solution loads, including OperationSteelTide, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: InspectAuthoredM4ReloadArmForDiagnostics csharp/TacticalPlayer.AuthoredVisuals.cs:486 — Method InspectAuthoredM4ReloadArmForDiagnostics — Roslyn's SymbolFinder walked every project the solution loads, including OperationSteelTide, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: InspectAuthoredPlatformReloadForDiagnostics csharp/TacticalPlayer.ReloadPresentation.ViewDiagnostics.cs:70 — Method InspectAuthoredPlatformReloadForDiagnostics — Roslyn's SymbolFinder walked every project the solution loads, including OperationSteelTide, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: InspectSidearmReloadForDiagnostics csharp/TacticalPlayer.ReloadPresentation.ViewDiagnostics.cs:178 — Method InspectSidearmReloadForDiagnostics — Roslyn's SymbolFinder walked every project the solution loads, including OperationSteelTide, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: InspectReloadRenderFrameForDiagnostics csharp/TacticalPlayer.RenderPresentation.cs:651 — Method InspectReloadRenderFrameForDiagnostics — Roslyn's SymbolFinder walked every project the solution loads, including OperationSteelTide, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: InspectStandardReloadRenderCadencesForDiagnostics csharp/TacticalPlayer.RenderPresentation.cs:667 — Method InspectStandardReloadRenderCadencesForDiagnostics — Roslyn's SymbolFinder walked every project the solution loads, including OperationSteelTide, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: MajadroidRoot csharp/TrainingRangeArenaBuilder.cs:16 — Field MajadroidRoot — Roslyn's SymbolFinder walked every project the solution loads, including OperationSteelTide, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×14
  • Edited copy of a member (8 corresponding lines) csharp/LowPolyBuildingArtBuilder.Architecture.cs:418 — csharp/LowPolyBuildingArtBuilder.Architecture.cs:418-427 | csharp/LowPolyBuildingArtBuilder.Architecture.cs:435-443 — 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) csharp/DemolitionArenaLayout.HarborLocks.cs:132 — csharp/DemolitionArenaLayout.HarborLocks.cs:132-139 | csharp/DemolitionArenaLayout.TideglassReactor.cs:330-338 — 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) csharp/DemolitionArenaLayout.BazaarCrossing.cs:658 — csharp/DemolitionArenaLayout.BazaarCrossing.cs:658-666 | csharp/DemolitionArenaLayout.BazaarCrossing.cs:669-676 — 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) csharp/CivilianNpc.cs:601 — csharp/CivilianNpc.cs:601-608 | csharp/CivilianNpc.cs:610-617 — 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) csharp/OldTownLandmarksBuilder.cs:285 — csharp/OldTownLandmarksBuilder.cs:285-292 | csharp/OldTownLandmarksBuilder.cs:324-335 — 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) csharp/FreightTerminalWorld.WeaponPoseDiagnostics.cs:451 — csharp/FreightTerminalWorld.WeaponPoseDiagnostics.cs:451-458 | csharp/FreightTerminalWorld.WeaponPoseDiagnostics.cs:466-474 — 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) csharp/FreightTerminalWorld.OperatorCarry.Diagnostics.cs:340 — csharp/FreightTerminalWorld.OperatorCarry.Diagnostics.cs:340-348 | csharp/FreightTerminalWorld.OperatorDeformation.Diagnostics.cs:268-275 — 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) csharp/EnemyOperator.Network.cs:138 — csharp/EnemyOperator.Network.cs:138-145 | csharp/SquadMate.cs:486-494 — 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) csharp/FreightTerminalWorld.Residential.Access.cs:1058 — csharp/FreightTerminalWorld.Residential.Access.cs:1058-1065 | csharp/FreightTerminalWorld.RoofAccess.cs:577-584 — 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) csharp/FreightTerminalWorld.Residential.Access.cs:1048 — csharp/FreightTerminalWorld.Residential.Access.cs:1048-1055 | csharp/FreightTerminalWorld.RoofAccess.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) scripts/blender/build_authored_optics.py:831 — scripts/blender/build_authored_optics.py:831-838 | scripts/blender/build_nisu_m4a1.py:986-993 — 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) scripts/blender/build_orbital_complex_underground.py:299 — scripts/blender/build_orbital_complex_underground.py:299-306 | scripts/blender/build_orbital_complex_underground.py:385-393 — 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) scripts/blender/build_hy3d_operator.py:493 — scripts/blender/build_hy3d_operator.py:493-500 | scripts/blender/build_hy3d_operator.py:504-511 — 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) scripts/blender/build_animated_reload_arms.py:1912 — scripts/blender/build_animated_reload_arms.py:1912-1919 | scripts/blender/build_animated_reload_arms.py:1928-1938 — 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.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×14
  • Members sharing a duplicated core (4 members, 50+ identical tokens) csharp/EnemyOperator.VehicleCombat.cs:61 — csharp/EnemyOperator.VehicleCombat.cs:61-121 | csharp/EnemyOperator.cs:1884-1961 | csharp/EnemyOperator.cs:1964-2050 | csharp/EnemyOperator.cs:2053-2101 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 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.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) csharp/FreightTerminalWorld.Demolition.HarborLocks.Diagnostics.cs:230 — csharp/FreightTerminalWorld.Demolition.HarborLocks.Diagnostics.cs:230-285 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.AssetDiagnostics.cs:333-358 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:1053-1084 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.StructureDiagnostics.cs:208-231 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 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.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs:10 — csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs:10-221 | csharp/FreightTerminalWorld.Squad.GlassRescue.Diagnostics.cs:10-171 | csharp/FreightTerminalWorld.Squad.Spectator.cs:443-500 | csharp/FreightTerminalWorld.Squad.cs:3138-4545 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 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.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) csharp/TacticalPlayer.Demolition.cs:162 — csharp/TacticalPlayer.Demolition.cs:162-190 | csharp/TacticalPlayer.Demolition.cs:193-225 | csharp/TacticalPlayer.Demolition.cs:228-260 | csharp/TacticalPlayer.cs:2887-2913 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 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.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) scripts/blender/build_animated_reload_arms.py:249 — scripts/blender/build_animated_reload_arms.py:249-261 | scripts/blender/build_djmaesen_smg45.py:63-75 | scripts/blender/build_first_person_arms.py:41-53 | scripts/blender/build_operator_hand_kits.py:103-115 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 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.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) scripts/blender/build_authored_optics.py:512 — scripts/blender/build_authored_optics.py:512-596 | scripts/blender/build_hy3d_operator.py:364-436 | scripts/blender/build_nisu_m4a1.py:467-531 | scripts/blender/build_nisu_m4a1.py:712-757 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 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.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) scripts/blender/build_authored_optics.py:1153 — scripts/blender/build_authored_optics.py:1153-1168 | scripts/blender/build_reloadable_gsh18.py:951-976 | scripts/blender/build_reloadable_quaternius_weapons.py:1101-1126 | scripts/blender/build_reloadable_scarl.py:672-690 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 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.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) scripts/blender/build_authored_optics.py:1257 — scripts/blender/build_authored_optics.py:1257-1338 | scripts/blender/build_melee_weapons.py:770-833 | scripts/blender/build_nisu_m4a1.py:1803-1875 | scripts/blender/generate_combat_models.py:355-397 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 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.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) scripts/blender/build_bazaar_crossing.py:1364 — scripts/blender/build_bazaar_crossing.py:1364-1431 | scripts/blender/build_bazaar_crossing.py:1580-1663 | scripts/blender/build_bazaar_crossing.py:1674-1739 | scripts/blender/build_bazaar_crossing.py:1750-1785 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 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.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) scripts/blender/build_djmaesen_smg45.py:87 — scripts/blender/build_djmaesen_smg45.py:87-157 | scripts/blender/build_djmaesen_smg45.py:161-224 | scripts/blender/build_djmaesen_smg45.py:327-352 | scripts/blender/build_first_person_arms.py:199-231 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 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.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) scripts/blender/build_operations_office_set.py:119 — scripts/blender/build_operations_office_set.py:119-153 | scripts/blender/build_quaternius_buildings_pack.py:173-192 | scripts/blender/build_tideglass_map_assets.py:139-158 | scripts/blender/build_trey_modular_industrial.py:1581-1618 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 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.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) scripts/blender/build_orbital_complex.py:665 — scripts/blender/build_orbital_complex.py:665-691 | scripts/blender/build_orbital_complex.py:703-730 | scripts/blender/build_orbital_complex.py:756-773 | scripts/blender/build_orbital_complex.py:785-828 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 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.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) scripts/blender/build_reloadable_gsh18.py:408 — scripts/blender/build_reloadable_gsh18.py:408-416 | scripts/blender/build_reloadable_quaternius_weapons.py:774-782 | scripts/blender/build_reloadable_scarl.py:405-413 | scripts/blender/build_supplemental_reload_mechanisms.py:877-885 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 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.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) scripts/blender/build_reloadable_gsh18.py:986 — scripts/blender/build_reloadable_gsh18.py:986-1039 | scripts/blender/build_reloadable_quaternius_weapons.py:1136-1191 | scripts/blender/build_reloadable_scarl.py:700-745 | scripts/blender/build_supplemental_reload_mechanisms.py:1228-1285 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 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 · Duplicated block (11 lines × 2) · ×13
  • Duplicated block (11 lines × 2) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.DensityDiagnostics.cs:234 — csharp/FreightTerminalWorld.Demolition.BazaarCrossing.DensityDiagnostics.cs:234-244 | csharp/FreightTerminalWorld.Demolition.BazaarCrossing.DensityDiagnostics.cs:279-289 — 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 `csharp/FreightTerminalWorld.Demolition.BazaarCrossing.DensityDiagnostics.cs:234` 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) csharp/FreightTerminalWorld.VehicleCombat.Diagnostics.cs:139 — csharp/FreightTerminalWorld.VehicleCombat.Diagnostics.cs:139-149 | csharp/FreightTerminalWorld.VehicleCombat.Diagnostics.cs:177-187 — 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) csharp/FreightTerminalWorld.Residential.Access.cs:979 — csharp/FreightTerminalWorld.Residential.Access.cs:979-989 | csharp/FreightTerminalWorld.Residential.Access.cs:1003-1013 — 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) csharp/JianghaiEnterableCollisionShellBuilder.cs:379 — csharp/JianghaiEnterableCollisionShellBuilder.cs:379-389 | csharp/JianghaiGameplayCollisionBuilder.cs:289-299 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (11 lines × 2) REDACTED:728 — REDACTED:728-738 | scripts/blender/build_jianghai_valley_environment.py:2107-2117 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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) scripts/blender/build_bazaar_crossing.py:719 — scripts/blender/build_bazaar_crossing.py:719-729 | scripts/blender/build_orbital_complex.py:261-271 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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) scripts/blender/build_bazaar_crossing.py:1265 — scripts/blender/build_bazaar_crossing.py:1265-1275 | scripts/blender/build_bazaar_crossing.py:1857-1867 — 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 `scripts/blender/build_bazaar_crossing.py:1265` it does not close everything it opens, so those exact lines 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) scripts/blender/build_operator_hand_kits.py:590 — scripts/blender/build_operator_hand_kits.py:590-600 | scripts/blender/build_operator_hand_kits.py:637-647 — 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) scripts/blender/build_orbital_complex.py:1657 — scripts/blender/build_orbital_complex.py:1657-1667 | scripts/blender/build_orbital_complex_underground.py:1678-1688 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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) scripts/blender/build_reloadable_quaternius_weapons.py:881 — scripts/blender/build_reloadable_quaternius_weapons.py:881-891 | scripts/blender/build_supplemental_reload_mechanisms.py:487-497 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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) tools/build_enterable_industrial_buildings.py:149 — tools/build_enterable_industrial_buildings.py:149-159 | tools/build_enterable_industrial_buildings.py:193-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.
  • Duplicated block (11 lines × 2) scripts/blender/build_field_use_props.py:657 — scripts/blender/build_field_use_props.py:657-667 | scripts/blender/build_melee_weapons.py:718-728 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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) scripts/blender/build_orbital_complex.py:1629 — scripts/blender/build_orbital_complex.py:1629-1639 | scripts/blender/build_orbital_complex_underground.py:1601-1611 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `scripts/blender/build_orbital_complex.py:1629` it begins part-way through the construct above it, so those 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 × 2) · ×12
  • Duplicated block (15 lines × 2) csharp/FreightTerminalWorld.Residential.cs:2925 — csharp/FreightTerminalWorld.Residential.cs:2925-2939 | csharp/FreightTerminalWorld.cs:6532-6546 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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) csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:245 — csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:245-259 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.Diagnostics.cs:19-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 `csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:245` 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, `csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:244` calls `GetTree` and `csharp/FreightTerminalWorld.Demolition.TideglassReactor.Diagnostics.cs:18` 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 lines × 2) csharp/FreightTerminalWorld.Demolition.TideglassReactor.Capture.cs:417 — csharp/FreightTerminalWorld.Demolition.TideglassReactor.Capture.cs:417-431 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:1261-1275 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/FreightTerminalWorld.Demolition.TideglassReactor.Capture.cs:417` 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 × 2) csharp/FreightTerminalWorld.Refinery.ClanHallValidation.cs:166 — csharp/FreightTerminalWorld.Refinery.ClanHallValidation.cs:166-180 | csharp/OldTownLandmarksBuilder.Collision.cs:227-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 both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `csharp/FreightTerminalWorld.Refinery.ClanHallValidation.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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `csharp/OldTownLandmarksBuilder.Collision.cs:242` calls `Dot` and `csharp/FreightTerminalWorld.Refinery.ClanHallValidation.cs:181` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared 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) csharp/FreightTerminalWorld.Squad.cs:4138 — csharp/FreightTerminalWorld.Squad.cs:4138-4152 | csharp/FreightTerminalWorld.Squad.cs:4259-4273 — 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 lines × 2) csharp/ResidentialRelayStation.cs:380 — csharp/ResidentialRelayStation.cs:380-394 | csharp/ResidentialRelayStation.cs:398-412 — 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 (15 lines × 2) csharp/FreightTerminalWorld.Refinery.NavigationValidation.cs:202 — csharp/FreightTerminalWorld.Refinery.NavigationValidation.cs:202-216 | csharp/FreightTerminalWorld.Refinery.NavigationValidation.cs:217-232 — 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 (15 lines × 2) csharp/SquadNetwork.Extraction.World.cs:67 — csharp/SquadNetwork.Extraction.World.cs:67-81 | csharp/SquadNetwork.Extraction.World.cs:94-108 — 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 `csharp/SquadNetwork.Extraction.World.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 (15 lines × 2) csharp/DestructibleAircraft.cs:349 — csharp/DestructibleAircraft.cs:349-363 | csharp/DriveableVehicle.cs:681-695 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (15 lines × 2) csharp/EnemyOperator.Utility.cs:26 — csharp/EnemyOperator.Utility.cs:26-40 | csharp/SquadMate.Utility.cs:28-42 — before extracting anything, compare `csharp/EnemyOperator.Utility.cs` and `csharp/SquadMate.Utility.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. 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.
  • Duplicated block (15 lines × 2) scripts/blender/build_bazaar_crossing.py:2983 — scripts/blender/build_bazaar_crossing.py:2983-2997 | scripts/blender/build_bazaar_crossing.py:5674-5688 — 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 `scripts/blender/build_bazaar_crossing.py:2983` it begins part-way through the construct above it, so those exact lines 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) scripts/blender/build_bazaar_crossing.py:5497 — scripts/blender/build_bazaar_crossing.py:5497-5511 | scripts/blender/build_bazaar_crossing.py:5537-5551 — 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 `scripts/blender/build_bazaar_crossing.py:5497` it begins part-way through the construct above it, so those 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 copy of a member (4 corresponding lines) · ×11
  • Edited copy of a member (4 corresponding lines) csharp/FreightTerminalWorld.Squad.EmergencyEgress.cs:243 — csharp/FreightTerminalWorld.Squad.EmergencyEgress.cs:243-246 | csharp/FreightTerminalWorld.Squad.Navigation.cs:939-942 — 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) scripts/blender/build_polyhaven_metal_trash_cans.py:52 — scripts/blender/build_polyhaven_metal_trash_cans.py:52-59 | scripts/blender/build_tideglass_map_assets.py:289-292 — 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) scripts/blender/import_bamen_military_soldier.py:48 — scripts/blender/import_bamen_military_soldier.py:48-51 | scripts/blender/rebuild_pawnshop_frontage.py:85-88 — 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) scripts/blender/rebind_hy3d_hands.py:148 — scripts/blender/rebind_hy3d_hands.py:148-155 | scripts/blender/build_hy3d_operator.py:334-337 — 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) scripts/blender/build_jianghai_lattice_door.py:581 — scripts/blender/build_jianghai_lattice_door.py:581-585 | scripts/blender/build_operations_office_set.py:629-632 — 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) scripts/blender/build_demolition_device.py:378 — scripts/blender/build_demolition_device.py:378-381 | scripts/blender/build_field_use_props.py:712-715 — 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) scripts/blender/build_djmaesen_smg45.py:79 — scripts/blender/build_djmaesen_smg45.py:79-83 | scripts/blender/build_first_person_arms.py: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) scripts/blender/build_reloadable_quaternius_weapons.py:653 — scripts/blender/build_reloadable_quaternius_weapons.py:653-656 | scripts/blender/build_reloadable_scarl.py:242-245 — 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) scripts/blender/bake_hy3d_carry_pose.py:109 — scripts/blender/bake_hy3d_carry_pose.py:109-112 | scripts/blender/build_hy3d_operator.py:327-330 — 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) scripts/blender/author_hy3d_rifle_carry.py:69 — scripts/blender/author_hy3d_rifle_carry.py:69-72 | scripts/blender/bake_hy3d_carry_pose.py:157-160 — 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) scripts/blender/build_animated_reload_arms.py:804 — scripts/blender/build_animated_reload_arms.py:804-808 | scripts/blender/import_bamen_military_soldier.py:134-137 — 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.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×10
  • Edited copy of a member (9 corresponding lines) csharp/ExtractionMaps/OrbitalComplex/OrbitalComplexLayoutValidator.cs:590 — csharp/ExtractionMaps/OrbitalComplex/OrbitalComplexLayoutValidator.cs:590-598 | csharp/ExtractionMaps/OrbitalComplex/OrbitalComplexLayoutValidator.cs:603-611 — 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) csharp/ExtractionMaps/OrbitalComplex/OrbitalComplexLayoutValidator.cs:616 — csharp/ExtractionMaps/OrbitalComplex/OrbitalComplexLayoutValidator.cs:616-624 | csharp/ExtractionMaps/OrbitalComplex/OrbitalComplexLayoutValidator.cs:629-637 — 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) csharp/CombatModelLibrary.cs:2497 — csharp/CombatModelLibrary.cs:2497-2505 | csharp/InventoryModelPreview.cs:316-342 — 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) csharp/FreightTerminalWorld.PromotionCapture.cs:226 — csharp/FreightTerminalWorld.PromotionCapture.cs:226-234 | csharp/FreightTerminalWorld.ReadmeCapture.cs:248-256 — 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) csharp/SquadNetwork.Demolition.Lobby.cs:33 — csharp/SquadNetwork.Demolition.Lobby.cs:33-49 | csharp/SquadNetwork.Extraction.cs:272-280 — 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) csharp/DemolitionArenaLayout.BazaarCrossing.cs:306 — csharp/DemolitionArenaLayout.BazaarCrossing.cs:306-314 | csharp/DemolitionArenaLayout.BazaarCrossing.cs:346-354 — 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) csharp/SquadMate.AuthoredVisuals.cs:214 — csharp/SquadMate.AuthoredVisuals.cs:214-223 | csharp/EnemyOperator.AuthoredVisuals.cs:209-217 — 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) csharp/FreightTerminalWorld.Squad.NavGrid.cs:910 — csharp/FreightTerminalWorld.Squad.NavGrid.cs:910-918 | csharp/FreightTerminalWorld.Squad.Navigation.cs:975-983 — 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) csharp/FreightTerminalWorld.cs:540 — csharp/FreightTerminalWorld.cs:540-548 | csharp/FreightTerminalWorld.Residential.Interactions.cs:303-311 — 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) scripts/blender/build_tideglass_map_assets.py:738 — scripts/blender/build_tideglass_map_assets.py:738-746 | scripts/blender/build_trey_modular_industrial.py:2092-2100 — 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.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×10
  • Duplicated block (8 lines × 3) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs:554 — csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs:554-561 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:338-345 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:387-394 — 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 (8 lines × 3) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs:771 — csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs:771-778 | csharp/FreightTerminalWorld.Demolition.HarborLocks.Diagnostics.cs:249-256 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:1062-1069 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs:771` 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 × 3) REDACTED:679 — REDACTED:679-686 | scripts/blender/build_jianghai_valley_environment.py:2041-2048 | scripts/blender/export_jianghai_old_city.py:1421-1428 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 lines × 3) scripts/blender/author_hy3d_pistol_carry.py:118 — scripts/blender/author_hy3d_pistol_carry.py:118-125 | scripts/blender/author_hy3d_rifle_prone.py:105-112 | scripts/blender/stabilize_operator_rifle.py:74-81 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 lines × 3) scripts/blender/build_authored_optics.py:1315 — scripts/blender/build_authored_optics.py:1315-1323 | scripts/blender/build_nisu_m4a1.py:1850-1858 | scripts/blender/generate_combat_models.py:388-395 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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, `scripts/blender/build_nisu_m4a1.py:1859` calls `str` and `scripts/blender/build_authored_optics.py:1324` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared 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) scripts/blender/build_reloadable_gsh18.py:329 — scripts/blender/build_reloadable_gsh18.py:329-336 | scripts/blender/build_reloadable_scarl.py:231-238 | scripts/blender/build_supplemental_reload_mechanisms.py:305-312 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (8 lines × 3) scripts/blender/build_tideglass_map_assets.py:239 — scripts/blender/build_tideglass_map_assets.py:239-246 | scripts/blender/build_tideglass_map_assets.py:599-606 | scripts/blender/build_trey_modular_industrial.py:1648-1655 — 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 (8 lines × 3) scripts/blender/build_trey_modular_industrial.py:1395 — scripts/blender/build_trey_modular_industrial.py:1395-1402 | scripts/blender/build_trey_modular_industrial.py:1442-1449 | scripts/blender/build_trey_modular_industrial.py:1451-1458 — 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 `scripts/blender/build_trey_modular_industrial.py:1395` it begins part-way through the construct above it, so those exact lines 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) scripts/blender/build_bazaar_crossing.py:6227 — scripts/blender/build_bazaar_crossing.py:6227-6234 | scripts/blender/build_bazaar_crossing.py:6249-6256 | scripts/blender/build_bazaar_crossing.py:6270-6277 — 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 (8 lines × 3) scripts/blender/build_quaternius_buildings_pack.py:523 — scripts/blender/build_quaternius_buildings_pack.py:523-530 | scripts/blender/build_tideglass_map_assets.py:738-745 | scripts/blender/build_trey_modular_industrial.py:2092-2099 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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.
D3 · God Classes · ClassTooLong · ×9
  • ClassTooLong: GameLocalization csharp/GameLocalization.cs — ClassTooLong — 893 significant lines (blank, comment-only and punctuation-only lines excluded), 6 methods. The bar is 400 significant lines; this is 493 over it, 2.23× 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: OldTownLandmarksBuilder csharp/OldTownLandmarksBuilder.cs — ClassTooLong — 660 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods, declared across 2 files: csharp/OldTownLandmarksBuilder.cs (17), csharp/OldTownLandmarksBuilder.Collision.cs (7). The bar is 400 significant lines; this is 260 over it, 1.65× 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: InventoryModelPreview csharp/InventoryModelPreview.cs — ClassTooLong — 498 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 98 over it, 1.25× 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: DemolitionStrategyPlanner csharp/DemolitionStrategyPlanner.cs — ClassTooLong — 470 significant lines (blank, comment-only and punctuation-only lines excluded), 18 methods. The bar is 400 significant lines; this is 70 over it, 1.18× 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: TrainingRangeSetupView csharp/TrainingRangeSetupView.cs — ClassTooLong — 468 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. The bar is 400 significant lines; this is 68 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: AuthoredAnimatedReloadArmsVisual csharp/CombatModelLibrary.AnimatedReloadArms.cs — ClassTooLong — 454 significant lines (blank, comment-only and punctuation-only lines excluded), 22 methods. The bar is 400 significant lines; this is 54 over it, 1.14× 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: DriveableVehicle csharp/DriveableVehicle.cs — ClassTooLong — 441 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods, declared across 2 files: csharp/DriveableVehicle.cs (21), csharp/DriveableVehicle.Combat.cs (2). The bar is 400 significant lines; this is 41 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: CivilianNpc csharp/CivilianNpc.cs — ClassTooLong — 437 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 37 over it, 1.09× 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: JianghaiOldCitySceneLoader csharp/JianghaiOldCitySceneLoader.cs — ClassTooLong — 428 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 28 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×9
  • Members sharing a duplicated core (5 members, 50+ identical tokens) csharp/CombatModelLibrary.FirstPerson.cs:61 — csharp/CombatModelLibrary.FirstPerson.cs:61-100 | csharp/CombatModelLibrary.Melee.cs:111-173 | csharp/CombatModelLibrary.cs:2553-2585 | csharp/JianghaiOldCitySceneLoader.cs:672-716 | csharp/JianghaiOldCityValleyInspector.cs:490-521 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 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.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) csharp/DemolitionArenaDressingBuilder.cs:300 — csharp/DemolitionArenaDressingBuilder.cs:300-316 | csharp/FreightTerminalArtDressingBuilder.cs:103-119 | csharp/ResidentialAuthoredPropLibrary.cs:285-302 | csharp/ResidentialStreetArtBuilder.cs:402-418 | csharp/ResidentialTowerArtBuilder.cs:239-255 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 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.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs:465 — csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs:465-531 | csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs:537-580 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:264-310 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:320-361 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:370-410 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 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.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GlassDiagnostics.cs:674 — csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GlassDiagnostics.cs:674-712 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:15-58 | csharp/FreightTerminalWorld.Interdistrict.cs:564-799 | csharp/FreightTerminalWorld.Refinery.NavigationValidation.cs:12-83 | csharp/FreightTerminalWorld.Refinery.NavigationValidation.cs:285-332 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 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.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) csharp/FreightTerminalWorld.Residential.Diversity.Diagnostics.cs:10 — csharp/FreightTerminalWorld.Residential.Diversity.Diagnostics.cs:10-61 | csharp/FreightTerminalWorld.Residential.StreetArt.Diagnostics.cs:182-206 | csharp/FreightTerminalWorld.Residential.cs:2764-2821 | csharp/FreightTerminalWorld.Residential.cs:2824-2904 | csharp/FreightTerminalWorld.Residential.cs:2907-2963 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 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.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) csharp/FreightTerminalWorld.ResidentialStairs.Diagnostics.cs:11 — csharp/FreightTerminalWorld.ResidentialStairs.Diagnostics.cs:11-154 | csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs:10-221 | csharp/FreightTerminalWorld.Squad.GlassRescue.Diagnostics.cs:10-171 | csharp/FreightTerminalWorld.Squad.IndoorRevive.Diagnostics.cs:11-261 | csharp/FreightTerminalWorld.Squad.Traversal.Diagnostics.cs:12-435 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 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.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) scripts/blender/build_animated_bamen_operator.py:183 — scripts/blender/build_animated_bamen_operator.py:183-194 | scripts/blender/build_field_use_props.py:657-679 | scripts/blender/build_melee_weapons.py:718-740 | scripts/blender/import_bamen_military_soldier.py:81-94 | scripts/blender/inspect_animated_bamen_operator.py:45-56 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 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.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) scripts/blender/build_bazaar_crossing.py:702 — scripts/blender/build_bazaar_crossing.py:702-737 | scripts/blender/build_demolition_device.py:39-49 | scripts/blender/build_field_use_props.py:51-61 | scripts/blender/build_jianghai_lattice_door.py:67-81 | scripts/blender/build_orbital_complex.py:260-284 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 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.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) scripts/blender/build_operations_office_set.py:78 — scripts/blender/build_operations_office_set.py:78-90 | scripts/blender/build_orbital_complex.py:241-256 | scripts/blender/build_quaternius_buildings_pack.py:157-169 | scripts/blender/build_tideglass_map_assets.py:123-135 | scripts/blender/build_trey_modular_industrial.py:1510-1522 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 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 · Duplicated block (19 lines × 2) · ×9
  • Duplicated block (19 lines × 2) csharp/EnemyOperator.Utility.cs:68 — csharp/EnemyOperator.Utility.cs:68-86 | csharp/SquadMate.Utility.cs:73-91 — before extracting anything, compare `csharp/EnemyOperator.Utility.cs` and `csharp/SquadMate.Utility.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. 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 (19 lines × 2) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.RouteDiagnostics.cs:421 — csharp/FreightTerminalWorld.Demolition.BazaarCrossing.RouteDiagnostics.cs:421-439 | csharp/FreightTerminalWorld.Demolition.BazaarCrossing.RouteDiagnostics.cs:466-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 `csharp/FreightTerminalWorld.Demolition.BazaarCrossing.RouteDiagnostics.cs:421` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those 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 (19 lines × 2) csharp/JianghaiOldCitySceneLoader.cs:678 — csharp/JianghaiOldCitySceneLoader.cs:678-696 | csharp/JianghaiOldCityValleyInspector.cs:497-515 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/JianghaiOldCitySceneLoader.cs:678` it does not close everything it opens, so those exact lines 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) scripts/blender/build_animated_bamen_operator.py:743 — scripts/blender/build_animated_bamen_operator.py:743-761 | scripts/blender/build_tide_hunter_monster.py:223-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 both call sites, so a change lands once.
  • Duplicated block (19 lines × 2) scripts/blender/build_jianghai_valley_environment.py:2830 — scripts/blender/build_jianghai_valley_environment.py:2830-2848 | scripts/blender/export_jianghai_old_city.py:2207-2225 — before extracting anything, compare `scripts/blender/build_jianghai_valley_environment.py` and `scripts/blender/export_jianghai_old_city.py` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 759 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) scripts/blender/build_jianghai_valley_environment.py:2878 — scripts/blender/build_jianghai_valley_environment.py:2878-2896 | scripts/blender/export_jianghai_old_city.py:2286-2304 — before extracting anything, compare `scripts/blender/build_jianghai_valley_environment.py` and `scripts/blender/export_jianghai_old_city.py` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 759 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) scripts/blender/build_orbital_complex_underground.py:923 — scripts/blender/build_orbital_complex_underground.py:923-941 | scripts/blender/build_orbital_complex_underground.py:1022-1040 — 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 `scripts/blender/build_orbital_complex_underground.py:923` it begins part-way through the construct above it, so those exact lines 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) scripts/blender/build_quaternius_buildings_pack.py:174 — scripts/blender/build_quaternius_buildings_pack.py:174-192 | scripts/blender/build_tideglass_map_assets.py:140-158 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `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 (19 lines × 2) scripts/blender/build_demolition_device.py:503 — scripts/blender/build_demolition_device.py:503-521 | scripts/blender/build_field_use_props.py:873-891 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 lines × 2) · ×9
  • Duplicated block (16 lines × 2) csharp/FreightTerminalWorld.cs:6032 — csharp/FreightTerminalWorld.cs:6032-6048 | csharp/FreightTerminalWorld.cs:6448-6463 — 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 `csharp/FreightTerminalWorld.cs:6032` it does not close everything it opens, so those exact lines 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) csharp/FreightTerminalWorld.Squad.NavGrid.cs:1060 — csharp/FreightTerminalWorld.Squad.NavGrid.cs:1060-1075 | csharp/SquadMate.Stairs.cs:131-146 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (16 lines × 2) scripts/blender/build_bazaar_crossing.py:2828 — scripts/blender/build_bazaar_crossing.py:2828-2843 | scripts/blender/build_bazaar_crossing.py:2865-2880 — 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 `scripts/blender/build_bazaar_crossing.py:2828` it does not close everything it opens, so those exact lines 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) scripts/blender/build_demolition_device.py:397 — scripts/blender/build_demolition_device.py:397-412 | scripts/blender/build_field_use_props.py:731-746 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (16 lines × 2) scripts/blender/build_djmaesen_smg45.py:123 — scripts/blender/build_djmaesen_smg45.py:123-138 | scripts/blender/build_djmaesen_smg45.py:188-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.
  • Duplicated block (16 lines × 2) scripts/blender/build_extraction_aircraft.py:81 — scripts/blender/build_extraction_aircraft.py:81-96 | scripts/blender/generate_combat_models.py:79-94 — before extracting anything, compare `scripts/blender/build_extraction_aircraft.py` and `scripts/blender/generate_combat_models.py` 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. 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 `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 (16 lines × 2) scripts/blender/build_jianghai_valley_environment.py:3007 — scripts/blender/build_jianghai_valley_environment.py:3007-3022 | scripts/blender/export_jianghai_old_city.py:2407-2422 — before extracting anything, compare `scripts/blender/build_jianghai_valley_environment.py` and `scripts/blender/export_jianghai_old_city.py` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 759 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 (16 lines × 2) scripts/blender/build_bazaar_crossing.py:6231 — scripts/blender/build_bazaar_crossing.py:6231-6246 | scripts/blender/build_bazaar_crossing.py:6253-6268 — 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 `scripts/blender/build_bazaar_crossing.py:6231` it begins part-way through the construct above it, so those exact lines 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) scripts/blender/build_demolition_device.py:458 — scripts/blender/build_demolition_device.py:458-473 | scripts/blender/build_field_use_props.py:815-830 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (12 lines × 2) · ×9
  • Duplicated block (12 lines × 2) csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Diagnostics.cs:362 — csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Diagnostics.cs:362-373 | csharp/FreightTerminalWorld.Squad.GlassRescue.Diagnostics.cs:11-22 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, 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) csharp/FreightTerminalWorld.ExplosionOcclusion.Diagnostics.cs:55 — csharp/FreightTerminalWorld.ExplosionOcclusion.Diagnostics.cs:55-66 | csharp/FreightTerminalWorld.ExplosionOcclusion.Diagnostics.cs:121-132 — 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) csharp/FreightTerminalWorld.PromotionCapture.cs:58 — csharp/FreightTerminalWorld.PromotionCapture.cs:58-69 | csharp/FreightTerminalWorld.ReadmeCapture.cs:130-141 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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) csharp/FreightTerminalWorld.TrainingRange.Diagnostics.cs:120 — csharp/FreightTerminalWorld.TrainingRange.Diagnostics.cs:120-137 | csharp/FreightTerminalWorld.TrainingRange.Diagnostics.cs:205-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.
  • Duplicated block (12 lines × 2) REDACTED:717 — REDACTED:717-728 | scripts/blender/export_jianghai_old_city.py:1459-1470 — before extracting anything, compare `REDACTED` and `scripts/blender/export_jianghai_old_city.py` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 507 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 × 2) scripts/blender/build_orbital_complex.py:680 — scripts/blender/build_orbital_complex.py:680-691 | scripts/blender/build_orbital_complex.py:817-828 — 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 `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) scripts/blender/build_reloadable_gsh18.py:289 — scripts/blender/build_reloadable_gsh18.py:289-300 | scripts/blender/build_reloadable_quaternius_weapons.py:446-457 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `scripts/blender/build_reloadable_gsh18.py: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.
  • Duplicated block (12 lines × 2) scripts/blender/build_tideglass_map_assets.py:237 — scripts/blender/build_tideglass_map_assets.py:237-248 | scripts/blender/build_trey_modular_industrial.py:1646-1657 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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) scripts/blender/build_authored_optics.py:1310 — scripts/blender/build_authored_optics.py:1310-1321 | scripts/blender/build_nisu_m4a1.py:1845-1856 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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, `scripts/blender/build_nisu_m4a1.py:1859` calls `str` and `scripts/blender/build_authored_optics.py:1324` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting 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 (19 corresponding lines) · ×8
  • Edited copy of a member (19 corresponding lines) csharp/FreightTerminalWorld.cs:6448 — csharp/FreightTerminalWorld.cs:6448-6662 | csharp/FreightTerminalWorld.Residential.cs:2907-2963 — 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) csharp/OperatorRosterRules.cs:19 — csharp/OperatorRosterRules.cs:19-37 | csharp/OperatorRosterRules.cs:47-66 — 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) csharp/FreightTerminalWorld.Expansion.cs:985 — csharp/FreightTerminalWorld.Expansion.cs:985-1010 | csharp/FreightTerminalWorld.Level.cs:1442-1460 — 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) csharp/DemolitionRoutePlanner.cs:550 — csharp/DemolitionRoutePlanner.cs:550-569 | csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:2830-2848 — 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) csharp/FreightTerminalWorld.ReadmeCapture.cs:178 — csharp/FreightTerminalWorld.ReadmeCapture.cs:178-196 | csharp/FreightTerminalWorld.ReadmeCapture.cs:201-220 — 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) csharp/SquadSustainmentService.cs:351 — csharp/SquadSustainmentService.cs:351-369 | csharp/SquadSustainmentService.cs:438-457 — 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) csharp/SquadNetwork.Demolition.cs:607 — csharp/SquadNetwork.Demolition.cs:607-625 | csharp/SquadNetwork.Demolition.cs:637-656 — 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) csharp/FreightTerminalWorld.Extraction.Launch.cs:91 — csharp/FreightTerminalWorld.Extraction.Launch.cs:91-111 | csharp/FreightTerminalWorld.Extraction.Launch.cs:114-132 — 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.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×8
  • Edited copy of a member (12 corresponding lines) csharp/LowPolyBuildingArtBuilder.Architecture.cs:453 — csharp/LowPolyBuildingArtBuilder.Architecture.cs:453-464 | csharp/LowPolyBuildingArtBuilder.Profiles.cs:271-282 — 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) csharp/SoundLab.cs:626 — csharp/SoundLab.cs:626-639 | csharp/SoundLab.cs:730-741 — 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) csharp/EnemyOperator.Pursuit.cs:443 — csharp/EnemyOperator.Pursuit.cs:443-454 | csharp/SquadMate.Combat.cs:806-818 — 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) scripts/blender/build_field_use_props.py:236 — scripts/blender/build_field_use_props.py:236-247 | scripts/blender/build_field_use_props.py:260-271 — 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) scripts/blender/build_field_use_props.py:212 — scripts/blender/build_field_use_props.py:212-223 | scripts/blender/build_orbital_complex.py:623-636 — 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) scripts/blender/add_hy3d_palm_markers.py:201 — scripts/blender/add_hy3d_palm_markers.py:201-214 | scripts/blender/author_hy3d_rifle_carry.py:113-124 — 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) scripts/blender/build_djmaesen_smg45.py:385 — scripts/blender/build_djmaesen_smg45.py:385-396 | scripts/blender/build_tastytony_gsh18.py:27-41 — 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) scripts/blender/build_orbital_complex.py:1133 — scripts/blender/build_orbital_complex.py:1133-1144 | scripts/blender/build_orbital_complex_underground.py:1435-1452 — 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.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×8
  • Edited copy of a member (15 corresponding lines) csharp/FreightTerminalWorld.Residential.Access.cs:497 — csharp/FreightTerminalWorld.Residential.Access.cs:497-518 | csharp/FreightTerminalWorld.Residential.Access.cs:525-539 — 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) csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:2855 — csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:2855-2870 | csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:2876-2890 — 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) csharp/FreightTerminalWorld.SurvivalZombies.cs:73 — csharp/FreightTerminalWorld.SurvivalZombies.cs:73-88 | csharp/FreightTerminalWorld.SurvivalZombies.cs:91-105 — 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) csharp/FreightTerminalWorld.Performance.cs:80 — csharp/FreightTerminalWorld.Performance.cs:80-94 | csharp/FreightTerminalWorld.Performance.cs:111-125 — 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) csharp/JianghaiInteriorFurnitureBatcher.cs:171 — csharp/JianghaiInteriorFurnitureBatcher.cs:171-186 | csharp/InteractiveBuildingDoor.Visibility.cs:50-64 — 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) csharp/FreightTerminalWorld.Refinery.cs:272 — csharp/FreightTerminalWorld.Refinery.cs:272-287 | csharp/FreightTerminalWorld.Refinery.cs:296-310 — 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) csharp/ExtractionAircraft.cs:494 — csharp/ExtractionAircraft.cs:494-508 | csharp/SquadMate.cs:1478-1492 — 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) scripts/blender/build_nisu_m4a1.py:1601 — scripts/blender/build_nisu_m4a1.py:1601-1615 | scripts/blender/build_taradavies_ak47.py:1035-1049 — 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.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×8
  • Duplicated block (7 lines × 3) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Diagnostics.cs:235 — csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Diagnostics.cs:235-241 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.DensityDiagnostics.cs:456-462 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.Diagnostics.cs:355-361 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
  • Duplicated block (7 lines × 3) csharp/SoundLab.cs:643 — csharp/SoundLab.cs:643-649 | csharp/SoundLab.cs:660-666 | csharp/SoundLab.cs:713-719 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `csharp/SoundLab.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.
  • Duplicated block (7 lines × 3) csharp/FreightTerminalWorld.Refinery.CollisionDiagnostics.cs:20 — csharp/FreightTerminalWorld.Refinery.CollisionDiagnostics.cs:20-26 | csharp/FreightTerminalWorld.Refinery.LoadingDiagnostics.cs:96-102 | csharp/FreightTerminalWorld.Refinery.Validation.cs:107-113 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/FreightTerminalWorld.Refinery.CollisionDiagnostics.cs:20` it begins part-way through the construct above it, so those exact lines 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) REDACTED:733 — REDACTED:733-739 | scripts/blender/build_jianghai_valley_environment.py:2112-2118 | scripts/blender/export_jianghai_old_city.py:1475-1481 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
  • Duplicated block (7 lines × 3) scripts/blender/build_field_use_props.py:319 — scripts/blender/build_field_use_props.py:319-325 | scripts/blender/build_melee_weapons.py:163-169 | scripts/blender/build_orbital_complex.py:878-884 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
  • Duplicated block (7 lines × 3) scripts/blender/build_melee_weapons.py:470 — scripts/blender/build_melee_weapons.py:470-476 | scripts/blender/build_melee_weapons.py:546-552 | scripts/blender/build_melee_weapons.py:644-650 — 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 `scripts/blender/build_melee_weapons.py:470` it begins part-way through the construct above it, so those exact lines 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) scripts/blender/build_reloadable_gsh18.py:241 — scripts/blender/build_reloadable_gsh18.py:241-249 | scripts/blender/build_reloadable_quaternius_weapons.py:352-358 | scripts/blender/build_supplemental_reload_mechanisms.py:345-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 all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `scripts/blender/build_reloadable_gsh18.py:241` it begins part-way through the construct above it, so those exact lines 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) scripts/blender/build_reloadable_gsh18.py:1060 — scripts/blender/build_reloadable_gsh18.py:1060-1067 | scripts/blender/build_reloadable_quaternius_weapons.py:1205-1212 | scripts/blender/build_reloadable_scarl.py:759-765 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×7
  • Edited copy of a member (10 corresponding lines) csharp/DemolitionArenaLayout.BazaarCrossing.cs:548 — csharp/DemolitionArenaLayout.BazaarCrossing.cs:548-557 | csharp/DemolitionArenaLayout.BazaarCrossing.cs:579-589 — 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) csharp/EnemyOperator.cs:2224 — csharp/EnemyOperator.cs:2224-2235 | csharp/TacticalPlayer.cs:3029-3038 — 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) csharp/DemolitionArenaLayout.RetakeRoutes.cs:43 — csharp/DemolitionArenaLayout.RetakeRoutes.cs:43-52 | csharp/DemolitionArenaLayout.RetakeRoutes.cs:57-69 — 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) csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Runtime.cs:427 — csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Runtime.cs:427-436 | csharp/ExtractionMaps/OrbitalComplex/OrbitalComplexLayoutValidator.cs:203-212 — 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) csharp/CombatModelLibrary.Melee.cs:184 — csharp/CombatModelLibrary.Melee.cs:184-198 | csharp/FreightTerminalWorld.AkModelDiagnostics.cs:387-396 — 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) csharp/FreightTerminalWorld.Level.cs:530 — csharp/FreightTerminalWorld.Level.cs:530-539 | csharp/JianghaiOldCityAtmosphere.cs:240-251 — 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) csharp/DemolitionMapCatalog.cs:136 — csharp/DemolitionMapCatalog.cs:136-145 | csharp/OperatorProgression.cs:231-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.
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×7
  • Edited copy of a member (20 corresponding lines) csharp/FreightTerminalWorld.ResidentialSurvival.Diagnostics.cs:10 — csharp/FreightTerminalWorld.ResidentialSurvival.Diagnostics.cs:10-39 | csharp/FreightTerminalWorld.RoofAccess.cs:587-606 — 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) csharp/SquadNavigationContracts.cs:107 — csharp/SquadNavigationContracts.cs:107-128 | csharp/TacticalPlayer.Traversal.cs:255-274 — 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) csharp/EnemyOperator.AuthoredVisuals.cs:160 — csharp/EnemyOperator.AuthoredVisuals.cs:160-184 | csharp/SquadMate.AuthoredVisuals.cs:137-156 — 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) csharp/CombatContactRelay.cs:43 — csharp/CombatContactRelay.cs:43-62 | csharp/CombatContactRelay.cs:65-84 — 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) csharp/CombatModelLibrary.cs:2293 — csharp/CombatModelLibrary.cs:2293-2312 | csharp/CombatModelLibrary.cs:2315-2334 — 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) scripts/blender/build_demolition_device.py:499 — scripts/blender/build_demolition_device.py:499-521 | scripts/blender/build_field_use_props.py:859-891 — 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) scripts/blender/build_field_use_props.py:312 — scripts/blender/build_field_use_props.py:312-332 | scripts/blender/build_melee_weapons.py:154-173 — 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.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×7
  • Duplicated block (20 lines × 2) csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:328 — csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:328-347 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:377-396 — 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 `csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.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 (20 lines × 2) csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:2584 — csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:2584-2603 | csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:2624-2652 — 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 (20 lines × 2) csharp/FreightTerminalWorld.Demolition.EnemyResponse.Diagnostics.cs:50 — csharp/FreightTerminalWorld.Demolition.EnemyResponse.Diagnostics.cs:50-69 | csharp/FreightTerminalWorld.Incendiary.Diagnostics.cs:37-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 both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `csharp/FreightTerminalWorld.Demolition.EnemyResponse.Diagnostics.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.
  • Duplicated block (20 lines × 2) csharp/FreightTerminalWorld.LootExpansion.cs:43 — csharp/FreightTerminalWorld.LootExpansion.cs:43-62 | csharp/FreightTerminalWorld.Refinery.Gameplay.cs:144-163 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/FreightTerminalWorld.LootExpansion.cs:43` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines 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) scripts/blender/build_bazaar_crossing.py:2959 — scripts/blender/build_bazaar_crossing.py:2959-2978 | scripts/blender/build_bazaar_crossing.py:5639-5658 — 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 `scripts/blender/build_bazaar_crossing.py:2959` it begins part-way through the construct above it, so those exact lines 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) scripts/blender/build_field_use_props.py:189 — scripts/blender/build_field_use_props.py:189-208 | scripts/blender/build_melee_weapons.py:124-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. 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) scripts/blender/build_reloadable_quaternius_weapons.py:808 — scripts/blender/build_reloadable_quaternius_weapons.py:808-827 | scripts/blender/build_supplemental_reload_mechanisms.py:412-431 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (18 lines × 2) · ×7
  • Duplicated block (18 lines × 2) csharp/LowPolyBuildingArtBuilder.cs:135 — csharp/LowPolyBuildingArtBuilder.cs:135-152 | csharp/LowPolyBuildingArtBuilder.cs:271-288 — 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 `csharp/LowPolyBuildingArtBuilder.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 (18 lines × 2) csharp/SquadMate.Combat.cs:682 — csharp/SquadMate.Combat.cs:682-699 | csharp/SquadMate.cs:902-919 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/SquadMate.Combat.cs:682` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those 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) csharp/FreightTerminalWorld.cs:2715 — csharp/FreightTerminalWorld.cs:2715-2732 | csharp/FreightTerminalWorld.cs:2784-2801 — 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 (18 lines × 2) csharp/GrenadeVisualFactory.cs:38 — csharp/GrenadeVisualFactory.cs:38-55 | csharp/GrenadeVisualFactory.cs:81-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 `csharp/GrenadeVisualFactory.cs:38` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those 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 (18 lines × 2) REDACTED:587 — REDACTED:587-604 | scripts/blender/export_jianghai_old_city.py:1327-1344 — before extracting anything, compare `REDACTED` and `scripts/blender/export_jianghai_old_city.py` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 507 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 (18 lines × 2) scripts/blender/build_bazaar_crossing.py:7364 — scripts/blender/build_bazaar_crossing.py:7364-7381 | scripts/blender/build_bazaar_crossing.py:7518-7535 — 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 (18 lines × 2) scripts/blender/build_extraction_aircraft.py:45 — scripts/blender/build_extraction_aircraft.py:45-62 | scripts/blender/generate_combat_models.py:43-60 — before extracting anything, compare `scripts/blender/build_extraction_aircraft.py` and `scripts/blender/generate_combat_models.py` 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. 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 `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 (14 lines × 2) · ×7
  • Duplicated block (14 lines × 2) csharp/FreightTerminalWorld.Demolition.Utility.cs:109 — csharp/FreightTerminalWorld.Demolition.Utility.cs:109-122 | csharp/FreightTerminalWorld.Demolition.Utility.cs:167-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. Read the line range as the matched WINDOW rather than a finished unit: at `csharp/FreightTerminalWorld.Demolition.Utility.cs:109` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines 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) csharp/FreightTerminalWorld.Squad.cs:3336 — csharp/FreightTerminalWorld.Squad.cs:3336-3349 | csharp/FreightTerminalWorld.Squad.cs:3580-3593 — 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 `csharp/FreightTerminalWorld.Squad.cs:3336` it does not close everything it opens, so those exact lines 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) csharp/TacticalPlayer.ReloadBodyDiagnostics.cs:30 — csharp/TacticalPlayer.ReloadBodyDiagnostics.cs:30-43 | csharp/TacticalPlayer.ReloadDiagnostics.cs:322-335 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/TacticalPlayer.ReloadBodyDiagnostics.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.
  • Duplicated block (14 lines × 2) csharp/TacticalPlayer.ReloadPresentation.cs:75 — csharp/TacticalPlayer.ReloadPresentation.cs:75-88 | csharp/TacticalPlayer.ReloadPresentation.cs:187-200 — 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 `csharp/TacticalPlayer.ReloadPresentation.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 (14 lines × 2) csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:1368 — csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:1368-1381 | csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:1399-1415 — 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 `csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:1368` 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 (14 lines × 2) scripts/blender/build_nisu_m4a1.py:580 — scripts/blender/build_nisu_m4a1.py:580-593 | scripts/blender/build_nisu_m4a1.py:721-734 — 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 `scripts/blender/build_nisu_m4a1.py:580` it begins part-way through the construct above it, so those exact lines 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) scripts/blender/build_supplemental_reload_mechanisms.py:929 — scripts/blender/build_supplemental_reload_mechanisms.py:929-942 | scripts/blender/build_supplemental_reload_mechanisms.py:1030-1043 — 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, `scripts/blender/build_supplemental_reload_mechanisms.py:926` calls `tuple`, `reversed` and `scripts/blender/build_supplemental_reload_mechanisms.py:1029` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting 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 × 2) · ×7
  • Duplicated block (12–13 lines × 2) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Capture.cs:304 — csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Capture.cs:304-316 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.Capture.cs:266-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 both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Capture.cs:304` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines 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) csharp/FreightTerminalWorld.Extraction.cs:566 — csharp/FreightTerminalWorld.Extraction.cs:566-577 | csharp/FreightTerminalWorld.Extraction.cs:656-668 — 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 (12–13 lines × 2) csharp/FreightTerminalWorld.Refinery.CollisionDiagnostics.cs:17 — csharp/FreightTerminalWorld.Refinery.CollisionDiagnostics.cs:17-28 | csharp/FreightTerminalWorld.Refinery.Validation.cs:103-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 both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `csharp/FreightTerminalWorld.Refinery.CollisionDiagnostics.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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different 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) csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs:66 — csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs:66-78 | csharp/FreightTerminalWorld.Squad.GlassRescue.Diagnostics.cs:62-73 — before extracting anything, compare `csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs` and `csharp/FreightTerminalWorld.Squad.GlassRescue.Diagnostics.cs` as WHOLE FILES: this scan already matched 6 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 `csharp/FreightTerminalWorld.Squad.GlassRescue.Diagnostics.cs:62` 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, `csharp/FreightTerminalWorld.Squad.GlassRescue.Diagnostics.cs:74` calls `SetProcess`, `SetPhysicsProcess` and `csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs:79` 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) csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs:70 — csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs:70-81 | csharp/FreightTerminalWorld.Squad.IndoorRevive.Diagnostics.cs:99-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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code 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, `csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs:81` calls `RestoreHealth` and `csharp/FreightTerminalWorld.Squad.IndoorRevive.Diagnostics.cs:111` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared 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) scripts/blender/build_bazaar_crossing.py:6381 — scripts/blender/build_bazaar_crossing.py:6381-6393 | scripts/blender/build_bazaar_crossing.py:7215-7226 — 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 `scripts/blender/build_bazaar_crossing.py:6381` it begins part-way through the construct above it, so those exact lines 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) scripts/blender/build_orbital_complex_underground.py:624 — scripts/blender/build_orbital_complex_underground.py:624-636 | scripts/blender/build_orbital_complex_underground.py:652-663 — 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 `scripts/blender/build_orbital_complex_underground.py:624` it begins part-way through the construct above it, so those 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 lines × 3) · ×7
  • Duplicated block (6 lines × 3) csharp/GrenadeVisualFactory.cs:38 — csharp/GrenadeVisualFactory.cs:38-43 | csharp/GrenadeVisualFactory.cs:81-86 | csharp/GrenadeVisualFactory.cs:127-132 — 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 `csharp/GrenadeVisualFactory.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.
  • Duplicated block (6 lines × 3) csharp/FreightTerminalWorld.Residential.Access.cs:605 — csharp/FreightTerminalWorld.Residential.Access.cs:605-610 | csharp/FreightTerminalWorld.Residential.Access.cs:827-832 | csharp/FreightTerminalWorld.cs:6591-6596 — 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 `csharp/FreightTerminalWorld.Residential.Access.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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `csharp/FreightTerminalWorld.Residential.Access.cs:833` calls `GetPosition` and `csharp/FreightTerminalWorld.Residential.Access.cs:611` 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 × 3) csharp/FreightTerminalWorld.Residential.Diversity.Diagnostics.cs:34 — csharp/FreightTerminalWorld.Residential.Diversity.Diagnostics.cs:34-39 | csharp/FreightTerminalWorld.Residential.Diversity.Diagnostics.cs:41-46 | csharp/FreightTerminalWorld.Residential.Diversity.Diagnostics.cs:48-53 — 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) scripts/blender/add_hy3d_palm_markers.py:201 — scripts/blender/add_hy3d_palm_markers.py:201-206 | scripts/blender/author_hy3d_pistol_carry.py:262-267 | scripts/blender/author_hy3d_rifle_carry.py:113-118 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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) scripts/blender/build_authored_optics.py:1262 — scripts/blender/build_authored_optics.py:1262-1267 | scripts/blender/build_nisu_m4a1.py:1812-1817 | scripts/blender/generate_combat_models.py:356-361 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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) scripts/blender/build_demolition_device.py:67 — scripts/blender/build_demolition_device.py:67-72 | scripts/blender/build_field_use_props.py:79-84 | scripts/blender/build_jianghai_lattice_door.py:149-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 (6 lines × 3) scripts/blender/build_jianghai_lattice_door.py:455 — scripts/blender/build_jianghai_lattice_door.py:455-460 | scripts/blender/build_operations_office_set.py:534-539 | scripts/blender/build_reloadable_scarl.py:160-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 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.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×7
  • Duplicated block (5 lines × 3) csharp/JianghaiEnterableCollisionShellBuilder.cs:107 — csharp/JianghaiEnterableCollisionShellBuilder.cs:107-111 | csharp/JianghaiEnterableCollisionShellBuilder.cs:195-199 | csharp/JianghaiEnterableCollisionShellBuilder.cs:231-235 — 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 `csharp/JianghaiEnterableCollisionShellBuilder.cs:107` 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 × 3) csharp/JianghaiEnterableCollisionShellBuilder.cs:122 — csharp/JianghaiEnterableCollisionShellBuilder.cs:122-126 | csharp/JianghaiEnterableCollisionShellBuilder.cs:210-214 | csharp/JianghaiEnterableCollisionShellBuilder.cs:246-250 — 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 `csharp/JianghaiEnterableCollisionShellBuilder.cs:122` 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 × 3) csharp/DemolitionRoutePlanner.cs:790 — csharp/DemolitionRoutePlanner.cs:790-794 | csharp/FreightTerminalWorld.Squad.EmergencyEgress.Planning.cs:333-337 | csharp/SquadMate.RescueTraversal.cs:321-325 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (5 lines × 3) csharp/FragGrenade.cs:46 — csharp/FragGrenade.cs:46-50 | csharp/IncendiaryGrenade.cs:95-99 | csharp/SmokeGrenade.cs:77-81 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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) scripts/blender/build_authored_optics.py:1298 — scripts/blender/build_authored_optics.py:1298-1302 | scripts/blender/generate_combat_models.py:371-375 | scripts/blender/inspect_operator_rifle_fit.py:80-84 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `scripts/blender/build_authored_optics.py:1298` it begins part-way through the construct above it, so those exact lines 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) REDACTED:612 — REDACTED:612-616 | scripts/blender/build_jianghai_valley_environment.py:1054-1058 | scripts/blender/export_jianghai_old_city.py:1352-1356 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (5 lines × 3) scripts/audio/build_opening_combat_theme.py:68 — scripts/audio/build_opening_combat_theme.py:68-72 | scripts/audio/build_opening_combat_theme.py:80-84 | scripts/audio/build_opening_combat_theme.py:108-112 — 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.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×6
  • Edited copy of a member (7 corresponding lines) csharp/RefineryExtractionMapBuilder.cs:365 — csharp/RefineryExtractionMapBuilder.cs:365-371 | csharp/RefineryExtractionMapBuilder.cs:379-385 — 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) csharp/EnemyOperator.Pursuit.Motor.cs:113 — csharp/EnemyOperator.Pursuit.Motor.cs:113-121 | csharp/SquadMate.Traversal.cs:570-576 — 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) csharp/CombatModelLibrary.cs:2588 — csharp/CombatModelLibrary.cs:2588-2594 | csharp/ExtractionAircraftVisualRig.cs:53-59 — 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) scripts/blender/build_orbital_complex.py:1478 — scripts/blender/build_orbital_complex.py:1478-1484 | scripts/blender/build_orbital_complex_underground.py:1571-1578 — 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) scripts/blender/build_jianghai_lattice_door.py:464 — scripts/blender/build_jianghai_lattice_door.py:464-470 | scripts/blender/build_operations_office_set.py:543-555 — 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) scripts/blender/build_field_use_props.py:643 — scripts/blender/build_field_use_props.py:643-649 | scripts/blender/build_melee_weapons.py:707-714 — 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.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×6
  • Duplicated block (22 lines × 2) csharp/FreightTerminalWorld.Demolition.Strategy.cs:72 — csharp/FreightTerminalWorld.Demolition.Strategy.cs:72-93 | csharp/FreightTerminalWorld.Demolition.Strategy.cs:115-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. Read the line range as the matched WINDOW rather than a finished unit: at `csharp/FreightTerminalWorld.Demolition.Strategy.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.
  • Duplicated block (22 lines × 2) csharp/FreightTerminalWorld.Residential.Diversity.Diagnostics.cs:13 — csharp/FreightTerminalWorld.Residential.Diversity.Diagnostics.cs:13-34 | csharp/FreightTerminalWorld.Residential.cs:2767-2788 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/FreightTerminalWorld.Residential.Diversity.Diagnostics.cs:13` 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 (22 lines × 2) csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Runtime.cs:1070 — csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Runtime.cs:1070-1091 | csharp/FreightTerminalWorld.Boss.cs:41-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 (22 lines × 2) csharp/FreightTerminalWorld.Melee.Impact.cs:570 — csharp/FreightTerminalWorld.Melee.Impact.cs:570-591 | csharp/FreightTerminalWorld.Melee.Impact.cs:601-622 — 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 `csharp/FreightTerminalWorld.Melee.Impact.cs:570` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (22 lines × 2) scripts/blender/build_bazaar_crossing.py:7753 — scripts/blender/build_bazaar_crossing.py:7753-7774 | scripts/blender/build_bazaar_crossing.py:7885-7906 — 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 `scripts/blender/build_bazaar_crossing.py:7885` it begins part-way through the construct above it, so those exact lines 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) scripts/blender/build_melee_weapons.py:523 — scripts/blender/build_melee_weapons.py:523-544 | scripts/blender/build_melee_weapons.py:612-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 `scripts/blender/build_melee_weapons.py:523` it does not close everything it opens, so those 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 lines × 3) · ×6
  • Duplicated block (9 lines × 3) REDACTED:590 — REDACTED:590-598 | scripts/blender/build_jianghai_valley_environment.py:1143-1151 | scripts/blender/export_jianghai_old_city.py:1330-1338 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (9 lines × 3) scripts/blender/build_bazaar_crossing.py:720 — scripts/blender/build_bazaar_crossing.py:720-728 | scripts/blender/build_jianghai_lattice_door.py:70-78 | scripts/blender/build_orbital_complex.py:262-270 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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) scripts/blender/build_djmaesen_smg45.py:455 — scripts/blender/build_djmaesen_smg45.py:455-463 | scripts/blender/build_first_person_arms.py:443-451 | scripts/blender/clean_hy3d_operator_exports.py:40-48 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `scripts/blender/build_djmaesen_smg45.py:455` it does not close everything it opens, so those exact lines 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) scripts/blender/build_extraction_aircraft.py:46 — scripts/blender/build_extraction_aircraft.py:46-54 | scripts/blender/generate_combat_models.py:44-52 | scripts/blender/import_bamen_military_soldier.py:69-77 — before extracting anything, compare `scripts/blender/build_extraction_aircraft.py` and `scripts/blender/generate_combat_models.py` 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. 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) scripts/blender/build_orbital_complex.py:720 — scripts/blender/build_orbital_complex.py:720-728 | scripts/blender/build_orbital_complex.py:763-771 | scripts/blender/build_orbital_complex.py:810-818 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (9 lines × 3) scripts/blender/export_jianghai_old_city.py:607 — scripts/blender/export_jianghai_old_city.py:607-615 | scripts/blender/export_jianghai_old_city.py:739-747 | scripts/blender/jianghai_enterable_interior_liners.py:132-140 — 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.
X2 · Cancellation propagation · Async method without CancellationToken · ×6
  • Async method without CancellationToken: ValidateBackendClient REDACTED:21 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ValidateBazaarCrossing csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Diagnostics.cs:17 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ValidateBazaarCrossingCore csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Diagnostics.cs:45 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ValidateVehicleCombat csharp/FreightTerminalWorld.VehicleCombat.Diagnostics.cs:8 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ValidateAdsAlignment csharp/FreightTerminalWorld.WeaponPoseDiagnostics.cs:9 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: StartMissionAsync csharp/MissionDirector.cs:265 — No CancellationToken parameter — this work can't be stopped early once started.
X3 · Exception handling · Swallowed exception (empty catch) · ×6
  • Swallowed exception (empty catch) csharp/CombatModelLibrary.PreviewDiagnostics.cs:39 — 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) csharp/CombatModelLibrary.PreviewDiagnostics.cs:70 — 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) csharp/CombatModelLibrary.PreviewDiagnostics.cs:103 — 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) csharp/ResidentialAuthoredPropLibrary.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) csharp/ResidentialAuthoredPropLibrary.cs:278 — 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) csharp/ZombieNpc.cs:31 — 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.
D4 · Code Duplication · Edited copy of a member (27 corresponding lines) · ×5
  • Edited copy of a member (27 corresponding lines) csharp/EnemyOperator.Pursuit.Motor.cs:230 — csharp/EnemyOperator.Pursuit.Motor.cs:230-268 | csharp/SquadMate.Stairs.cs:81-107 — 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) csharp/SquadMate.Traversal.cs:449 — csharp/SquadMate.Traversal.cs:449-475 | csharp/TacticalPlayer.MovementInput.cs:257-287 — 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) scripts/blender/build_field_use_props.py:180 — scripts/blender/build_field_use_props.py:180-208 | scripts/blender/build_melee_weapons.py:117-143 — 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) REDACTED:470 — REDACTED:470-496 | scripts/blender/export_jianghai_old_city.py:1216-1242 — 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) scripts/blender/build_taradavies_ak47.py:524 — scripts/blender/build_taradavies_ak47.py:524-550 | scripts/blender/build_taradavies_ak47.py:563-591 — 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 (14 corresponding lines) · ×5
  • Edited copy of a member (14 corresponding lines) csharp/OldTownLandmarksBuilder.Collision.cs:303 — csharp/OldTownLandmarksBuilder.Collision.cs:303-340 | csharp/OldTownLandmarksBuilder.cs:206-219 — 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) csharp/FirstPersonMeshFactory.cs:15 — csharp/FirstPersonMeshFactory.cs:15-28 | csharp/FirstPersonMeshFactory.cs:47-60 — 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) csharp/JianghaiClanHallGateContract.cs:208 — csharp/JianghaiClanHallGateContract.cs:208-221 | csharp/JianghaiClanHallGateContract.cs:224-237 — 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) scripts/blender/build_bazaar_crossing.py:999 — scripts/blender/build_bazaar_crossing.py:999-1014 | scripts/blender/build_orbital_complex.py:640-653 — 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) scripts/blender/export_jianghai_old_city.py:341 — scripts/blender/export_jianghai_old_city.py:341-354 | scripts/blender/export_jianghai_old_city.py:358-372 — 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.
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×5
  • Edited copy of a member (13 corresponding lines) csharp/DemolitionArenaLayout.BazaarCrossing.cs:284 — csharp/DemolitionArenaLayout.BazaarCrossing.cs:284-296 | csharp/DemolitionArenaLayout.BazaarCrossing.cs:324-336 — 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) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs:355 — csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs:355-367 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.TopologyDiagnostics.cs:46-58 — 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) csharp/SquadSustainmentService.cs:180 — csharp/SquadSustainmentService.cs:180-193 | csharp/SquadSustainmentService.cs:460-472 — 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) csharp/DemolitionTeamMemberCard.cs:60 — csharp/DemolitionTeamMemberCard.cs:60-72 | csharp/DemolitionTeamStatusView.cs:93-107 — 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) scripts/blender/build_reloadable_quaternius_weapons.py:881 — scripts/blender/build_reloadable_quaternius_weapons.py:881-893 | scripts/blender/build_supplemental_reload_mechanisms.py:487-504 — 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.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×5
  • Edited copy of a member (17 corresponding lines) csharp/FreightIndustrialInteriorBuilder.cs:410 — csharp/FreightIndustrialInteriorBuilder.cs:410-426 | csharp/FreightTerminalWorld.Level.cs:1587-1608 — 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) csharp/FreightTerminalWorld.Economy.cs:54 — csharp/FreightTerminalWorld.Economy.cs:54-73 | csharp/FreightTerminalWorld.Refinery.cs:366-382 — 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) csharp/SquadNetwork.Demolition.Glass.cs:39 — csharp/SquadNetwork.Demolition.Glass.cs:39-55 | csharp/SquadNetwork.Demolition.Utility.cs:224-247 — 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) scripts/blender/build_field_use_props.py:283 — scripts/blender/build_field_use_props.py:283-299 | scripts/blender/build_melee_weapons.py:359-375 — 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) scripts/blender/build_orbital_complex.py:295 — scripts/blender/build_orbital_complex.py:295-311 | scripts/blender/rebuild_pawnshop_frontage.py:111-130 — 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.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×5
  • Edited copy of a member (6 corresponding lines) csharp/DemolitionArenaLayout.cs:870 — csharp/DemolitionArenaLayout.cs:870-875 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:566-571 — 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) csharp/TrainingRangeArmoryView.cs:331 — csharp/TrainingRangeArmoryView.cs:331-336 | csharp/TrainingRangeSetupView.cs:640-645 — 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) scripts/blender/bake_hy3d_carry_pose.py:583 — scripts/blender/bake_hy3d_carry_pose.py:583-590 | scripts/blender/add_hy3d_palm_markers.py:73-78 — 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) scripts/blender/build_melee_weapons.py:91 — scripts/blender/build_melee_weapons.py:91-96 | scripts/blender/build_orbital_complex.py:575-581 — 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) scripts/blender/build_quaternius_buildings_pack.py:732 — scripts/blender/build_quaternius_buildings_pack.py:732-737 | scripts/blender/build_tideglass_map_assets.py:867-872 — 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.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×5
  • Duplicated block (10 lines × 3) csharp/FreightTerminalWorld.Refinery.EnterableCollisionValidation.cs:138 — csharp/FreightTerminalWorld.Refinery.EnterableCollisionValidation.cs:138-147 | csharp/FreightTerminalWorld.Refinery.EnterableCollisionValidation.cs:178-187 | csharp/FreightTerminalWorld.Refinery.EnterableCollisionValidation.cs:224-233 — 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 `csharp/FreightTerminalWorld.Refinery.EnterableCollisionValidation.cs:138` 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) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs:474 — csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs:474-484 | csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs:538-548 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:238-247 — 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 (10 lines × 3) REDACTED:159 — REDACTED:159-168 | scripts/blender/build_jianghai_valley_environment.py:1751-1760 | scripts/blender/export_jianghai_old_city.py:1027-1036 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (10 lines × 3) scripts/blender/build_demolition_device.py:39 — scripts/blender/build_demolition_device.py:39-48 | scripts/blender/build_field_use_props.py:51-60 | scripts/blender/build_jianghai_lattice_door.py:67-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 all 3 call sites, so a change lands once.
  • Duplicated block (10 lines × 3) scripts/blender/build_quaternius_buildings_pack.py:173 — scripts/blender/build_quaternius_buildings_pack.py:173-182 | scripts/blender/build_tideglass_map_assets.py:139-148 | scripts/blender/build_trey_modular_industrial.py:1582-1591 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 · Members sharing a duplicated core (6 members, 50+ identical tokens) · ×4
  • Members sharing a duplicated core (6 members, 50+ identical tokens) csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:496 — csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:496-858 | csharp/FreightTerminalWorld.Demolition.EnemyResponse.Diagnostics.cs:9-657 | csharp/FreightTerminalWorld.Economy.cs:237-365 | csharp/FreightTerminalWorld.QuickSlots.Diagnostics.cs:9-512 | csharp/FreightTerminalWorld.Refinery.Doors.Diagnostics.cs:9-310 | csharp/FreightTerminalWorld.cs:3789-4435 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 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.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) csharp/FreightTerminalWorld.Demolition.TideglassReactor.WalkwayPhysicsDiagnostics.cs:10 — csharp/FreightTerminalWorld.Demolition.TideglassReactor.WalkwayPhysicsDiagnostics.cs:10-63 | csharp/FreightTerminalWorld.Demolition.cs:961-984 | csharp/FreightTerminalWorld.ExtractionSpawns.Diagnostics.cs:61-86 | csharp/FreightTerminalWorld.IndustrialInteriors.Diagnostics.cs:281-312 | csharp/FreightTerminalWorld.Interdistrict.cs:564-799 | csharp/TacticalPlayer.Traversal.cs:335-392 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 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.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) scripts/blender/add_hy3d_palm_markers.py:236 — scripts/blender/add_hy3d_palm_markers.py:236-262 | scripts/blender/author_hy3d_preview_stand.py:148-181 | scripts/blender/author_hy3d_rifle_carry.py:167-182 | scripts/blender/bake_hy3d_carry_pose.py:594-636 | scripts/blender/rebind_hy3d_hands.py:533-563 | scripts/blender/repair_magpie_right_hand.py:127-173 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 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.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) REDACTED:511 — REDACTED:511-553 | REDACTED:562-578 | scripts/blender/build_jianghai_valley_environment.py:1876-1916 | scripts/blender/build_jianghai_valley_environment.py:1925-1941 | scripts/blender/export_jianghai_old_city.py:1257-1293 | scripts/blender/export_jianghai_old_city.py:1302-1318 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 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 · Edited copy of a member (22 corresponding lines) · ×4
  • Edited copy of a member (22 corresponding lines) csharp/DemolitionArenaLayout.BazaarCrossing.cs:66 — csharp/DemolitionArenaLayout.BazaarCrossing.cs:66-87 | csharp/DemolitionArenaLayout.BazaarCrossing.cs:633-655 — 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) csharp/TacticalSurfaceLibrary.cs:42 — csharp/TacticalSurfaceLibrary.cs:42-64 | csharp/TacticalSurfaceLibrary.cs:67-88 — 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) csharp/SquadNetwork.Demolition.Utility.cs:153 — csharp/SquadNetwork.Demolition.Utility.cs:153-178 | csharp/SquadNetwork.Demolition.WeaponDrops.cs:184-205 — 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) scripts/blender/build_demolition_device.py:61 — scripts/blender/build_demolition_device.py:61-82 | scripts/blender/build_field_use_props.py:73-94 — 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.
D4 · Code Duplication · Edited copy of a member (31 corresponding lines) · ×4
  • Edited copy of a member (31 corresponding lines) csharp/DemolitionArenaLayout.BazaarCrossing.cs:244 — csharp/DemolitionArenaLayout.BazaarCrossing.cs:244-274 | csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GuardRailDiagnostics.cs:275-314 — 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) csharp/FreightTerminalWorld.cs:2667 — csharp/FreightTerminalWorld.cs:2667-2697 | csharp/FreightTerminalWorld.cs:2703-2734 — 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) csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Runtime.cs:1062 — csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Runtime.cs:1062-1092 | csharp/FreightTerminalWorld.Boss.cs:33-69 — 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) scripts/blender/build_bazaar_crossing.py:1449 — scripts/blender/build_bazaar_crossing.py:1449-1479 | scripts/blender/build_bazaar_crossing.py:1494-1533 — 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 · Edited copy of a member (29 corresponding lines) · ×4
  • Edited copy of a member (29 corresponding lines) csharp/FreightTerminalWorld.Melee.Impact.cs:570 — csharp/FreightTerminalWorld.Melee.Impact.cs:570-598 | csharp/FreightTerminalWorld.Melee.Impact.cs:601-632 — 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) csharp/EnemyOperator.AuthoredVisuals.cs:104 — csharp/EnemyOperator.AuthoredVisuals.cs:104-138 | csharp/SquadMate.AuthoredVisuals.cs:106-134 — 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) REDACTED:432 — REDACTED:432-460 | scripts/blender/export_jianghai_old_city.py:1179-1207 — 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) scripts/blender/build_orbital_complex.py:901 — scripts/blender/build_orbital_complex.py:901-929 | scripts/blender/build_orbital_complex_underground.py:163-204 — 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 copy of a member (21 corresponding lines) · ×4
  • Edited copy of a member (21 corresponding lines) csharp/TrainingRangeArmoryView.Catalog.cs:23 — csharp/TrainingRangeArmoryView.Catalog.cs:23-58 | csharp/TrainingRangeSetupView.cs:547-567 — 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) csharp/SquadMate.Combat.cs:679 — csharp/SquadMate.Combat.cs:679-699 | csharp/SquadMate.cs:899-919 — 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) csharp/FreightTerminalWorld.Demolition.Network.Lobby.cs:50 — csharp/FreightTerminalWorld.Demolition.Network.Lobby.cs:50-80 | csharp/FreightTerminalWorld.Squad.cs:498-518 — 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) scripts/blender/build_animated_bamen_operator.py:739 — scripts/blender/build_animated_bamen_operator.py:739-761 | scripts/blender/build_tide_hunter_monster.py:221-241 — 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.
D4 · Code Duplication · Edited copy of a member (25 corresponding lines) · ×4
  • Edited copy of a member (25 corresponding lines) csharp/SquadNetwork.Extraction.World.cs:61 — csharp/SquadNetwork.Extraction.World.cs:61-85 | csharp/SquadNetwork.Extraction.World.cs:88-112 — 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) csharp/SquadNetwork.cs:287 — csharp/SquadNetwork.cs:287-312 | csharp/SquadNetwork.cs:315-339 — 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) csharp/CombatModelLibrary.DemolitionDevice.cs:85 — csharp/CombatModelLibrary.DemolitionDevice.cs:85-109 | csharp/CombatModelLibrary.FieldUse.cs:148-181 — 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) scripts/blender/build_jianghai_valley_environment.py:1026 — scripts/blender/build_jianghai_valley_environment.py:1026-1050 | scripts/blender/build_jianghai_valley_environment.py:1712-1742 — 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.
D4 · Code Duplication · Edited copy of a member (24 corresponding lines) · ×4
  • Edited copy of a member (24 corresponding lines) csharp/FreightTerminalWorld.Refinery.ClanHallValidation.cs:163 — csharp/FreightTerminalWorld.Refinery.ClanHallValidation.cs:163-186 | csharp/OldTownLandmarksBuilder.Collision.cs:223-249 — 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) csharp/EnemyOperator.Pursuit.Motor.cs:201 — csharp/EnemyOperator.Pursuit.Motor.cs:201-224 | csharp/SquadMate.Stairs.cs:48-73 — 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) csharp/EnemyOperator.Utility.cs:67 — csharp/EnemyOperator.Utility.cs:67-90 | csharp/SquadMate.Utility.cs:72-96 — 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) scripts/blender/build_authored_optics.py:214 — scripts/blender/build_authored_optics.py:214-237 | scripts/blender/build_nisu_m4a1.py:956-982 — 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.
D4 · Code Duplication · Edited copies of one member (3 members, 23+ corresponding lines) · ×4
  • Edited copies of one member (3 members, 23+ corresponding lines) csharp/FreightTerminalWorld.Flashbang.cs:82 — csharp/FreightTerminalWorld.Flashbang.cs:82-104 | csharp/FreightTerminalWorld.Incendiary.cs:47-69 | csharp/FreightTerminalWorld.Smoke.cs:91-113 — 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) scripts/blender/build_quaternius_buildings_pack.py:488 — scripts/blender/build_quaternius_buildings_pack.py:488-519 | scripts/blender/build_tideglass_map_assets.py:325-347 | scripts/blender/build_trey_modular_industrial.py:2065-2088 — 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) scripts/blender/build_trey_modular_industrial.py:2104 — scripts/blender/build_trey_modular_industrial.py:2104-2138 | scripts/blender/build_trey_modular_industrial.py:2212-2234 | scripts/blender/build_trey_modular_industrial.py:2238-2262 — 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) scripts/blender/build_authored_optics.py:268 — scripts/blender/build_authored_optics.py:268-293 | scripts/blender/build_nisu_m4a1.py:377-406 | scripts/blender/build_reloadable_quaternius_weapons.py:348-370 — 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 copy of a member (5 corresponding lines) · ×4
  • Edited copy of a member (5 corresponding lines) csharp/DemolitionArenaLayout.HarborLocks.cs:119 — csharp/DemolitionArenaLayout.HarborLocks.cs:119-123 | csharp/DemolitionArenaLayout.HarborLocks.cs:125-130 — 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) csharp/LowPolyBuildingArtBuilder.Architecture.cs:93 — csharp/LowPolyBuildingArtBuilder.Architecture.cs:93-100 | csharp/LowPolyBuildingArtBuilder.Architecture.cs:103-107 — 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) csharp/LootDragControls.cs:176 — csharp/LootDragControls.cs:176-180 | csharp/LootWeaponSlotView.cs:51-59 — 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) scripts/blender/build_jianghai_valley_environment.py:191 — scripts/blender/build_jianghai_valley_environment.py:191-195 | scripts/blender/build_trey_modular_industrial.py:1467-1471 — 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.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×4
  • Duplicated block (17 lines × 2) csharp/FreightTerminalWorld.Demolition.SquadNavigation.cs:457 — csharp/FreightTerminalWorld.Demolition.SquadNavigation.cs:457-473 | csharp/FreightTerminalWorld.Demolition.SquadNavigation.cs:509-525 — 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 `csharp/FreightTerminalWorld.Demolition.SquadNavigation.cs:457` 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 `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 (17 lines × 2) csharp/TacticalPlayer.OrbitalComplexSwimming.cs:45 — csharp/TacticalPlayer.OrbitalComplexSwimming.cs:45-61 | csharp/TacticalPlayer.cs:1657-1673 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/TacticalPlayer.OrbitalComplexSwimming.cs:45` 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 (17 lines × 2) scripts/blender/build_tideglass_map_assets.py:379 — scripts/blender/build_tideglass_map_assets.py:379-395 | scripts/blender/build_tideglass_map_assets.py:479-495 — 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 `scripts/blender/build_tideglass_map_assets.py: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.
  • Duplicated block (17 lines × 2) REDACTED:773 — REDACTED:773-789 | scripts/blender/export_jianghai_old_city.py:1518-1534 — before extracting anything, compare `REDACTED` and `scripts/blender/export_jianghai_old_city.py` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 507 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 (14 lines × 3) · ×4
  • Duplicated block (14 lines × 3) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Diagnostics.cs:56 — csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Diagnostics.cs:56-69 | csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:246-259 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.Diagnostics.cs:20-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 `csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Diagnostics.cs:56` 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, `csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:244` calls `GetTree` and `csharp/FreightTerminalWorld.Demolition.TideglassReactor.Diagnostics.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 (14 lines × 3) scripts/blender/build_authored_optics.py:280 — scripts/blender/build_authored_optics.py:280-293 | scripts/blender/build_nisu_m4a1.py:393-406 | scripts/blender/build_reloadable_quaternius_weapons.py:357-370 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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) scripts/blender/build_demolition_device.py:69 — scripts/blender/build_demolition_device.py:69-82 | scripts/blender/build_field_use_props.py:81-94 | scripts/blender/build_melee_weapons.py:67-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 `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 (14 lines × 3) scripts/blender/build_reloadable_gsh18.py:281 — scripts/blender/build_reloadable_gsh18.py:281-294 | scripts/blender/build_reloadable_quaternius_weapons.py:531-544 | scripts/blender/build_supplemental_reload_mechanisms.py:792-805 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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, `scripts/blender/build_reloadable_gsh18.py:277` calls `set`, `union` and `scripts/blender/build_supplemental_reload_mechanisms.py:788` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting 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 × 4) · ×4
  • Duplicated block (7 lines × 4) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GlassDiagnostics.cs:698 — csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GlassDiagnostics.cs:698-704 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:44-50 | csharp/FreightTerminalWorld.Refinery.NavigationValidation.cs:67-73 | csharp/FreightTerminalWorld.Refinery.NavigationValidation.cs:318-324 — 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.
  • Duplicated block (7 lines × 4) csharp/JianghaiOldCityAtmosphere.cs:161 — csharp/JianghaiOldCityAtmosphere.cs:161-167 | csharp/JianghaiOldCityAtmosphere.cs:180-186 | csharp/JianghaiOldCityAtmosphere.cs:199-205 | csharp/JianghaiOldCityAtmosphere.cs:218-224 — 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 `csharp/JianghaiOldCityAtmosphere.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.
  • Duplicated block (7 lines × 4) csharp/EnemyOperator.cs:364 — csharp/EnemyOperator.cs:364-370 | csharp/FreightTerminalWorld.Level.cs:19-25 | csharp/LootBackpackVisual.cs:124-130 | csharp/ResidentialSearchableFurniture.cs:264-270 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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. 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 × 4) scripts/blender/build_jianghai_valley_environment.py:2576 — scripts/blender/build_jianghai_valley_environment.py:2576-2582 | scripts/blender/export_jianghai_old_city.py:1917-1923 | scripts/blender/export_jianghai_old_city.py:2314-2320 | scripts/blender/export_jianghai_old_city.py:2874-2880 — before extracting anything, compare `scripts/blender/build_jianghai_valley_environment.py` and `scripts/blender/export_jianghai_old_city.py` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 759 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.
IC1 · Incompleteness & stubs · Condition was already decided · ×4
  • Condition was already decided — an earlier guard makes this test constant csharp/FreightTerminalWorld.Squad.NavGrid.cs:522 — Control only reaches here when `budget.IsExhausted` is false, because the guard on line 504 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test.
  • Condition was already decided — an earlier guard makes this test constant csharp/FreightTerminalWorld.Squad.Navigation.cs:1013 — Control only reaches here when `budget is not null && !budget.CanProbe` is false, because the guard on line 991 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test.
  • Condition was already decided — an earlier guard makes this test constant csharp/FreightTerminalWorld.Squad.Traversal.Connectors.cs:329 — Control only reaches here when `budget.CanProbe` is true, because the guard on line 307 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test.
  • Condition was already decided — an earlier guard makes this test constant csharp/FreightTerminalWorld.Squad.Traversal.cs:509 — Control only reaches here when `budget.IsExhausted` is false, because the guard on line 501 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test.
D4 · Code Duplication · Edited copy of a member (34 corresponding lines) · ×3
  • Edited copy of a member (34 corresponding lines) csharp/InventoryModelPreview.cs:498 — csharp/InventoryModelPreview.cs:498-537 | csharp/InventoryModelPreview.cs:540-573 — 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) csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Runtime.cs:996 — csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Runtime.cs:996-1029 | csharp/FreightTerminalWorld.cs:1534-1579 — 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) csharp/EnemyOperator.Squad.cs:39 — csharp/EnemyOperator.Squad.cs:39-72 | csharp/FreightTerminalWorld.RelayStations.cs:349-383 — 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 (38 corresponding lines) · ×3
  • Edited copy of a member (38 corresponding lines) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.RouteDiagnostics.cs:402 — csharp/FreightTerminalWorld.Demolition.BazaarCrossing.RouteDiagnostics.cs:402-439 | csharp/FreightTerminalWorld.Demolition.BazaarCrossing.RouteDiagnostics.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) REDACTED:673 — REDACTED:673-710 | scripts/blender/export_jianghai_old_city.py:1415-1452 — 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) scripts/blender/build_reloadable_quaternius_weapons.py:837 — scripts/blender/build_reloadable_quaternius_weapons.py:837-874 | scripts/blender/build_supplemental_reload_mechanisms.py:442-479 — 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) · ×3
  • Edited copy of a member (28 corresponding lines) csharp/FreightTerminalWorld.Demolition.TideglassReactor.Capture.cs:280 — csharp/FreightTerminalWorld.Demolition.TideglassReactor.Capture.cs:280-307 | csharp/FreightTerminalWorld.OperatorCarry.Diagnostics.cs:501-537 — 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) csharp/FirstPersonFieldUsePresentation.cs:205 — csharp/FirstPersonFieldUsePresentation.cs:205-232 | csharp/FirstPersonFieldUsePresentation.cs:235-264 — 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) csharp/FirstPersonReloadProfileCatalog.cs:199 — csharp/FirstPersonReloadProfileCatalog.cs:199-226 | csharp/FirstPersonReloadProfileCatalog.cs:234-267 — 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 · Edited copy of a member (54 corresponding lines) · ×3
  • Edited copy of a member (54 corresponding lines) csharp/FreightTerminalWorld.Demolition.Utility.cs:69 — csharp/FreightTerminalWorld.Demolition.Utility.cs:69-122 | csharp/FreightTerminalWorld.Demolition.Utility.cs:125-180 — 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) scripts/blender/build_orbital_complex.py:1269 — scripts/blender/build_orbital_complex.py:1269-1327 | scripts/blender/build_orbital_complex_underground.py:1456-1509 — 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) scripts/blender/build_nisu_m4a1.py:230 — scripts/blender/build_nisu_m4a1.py:230-285 | scripts/blender/build_tide_hunter_monster.py:141-194 — 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 (36 corresponding lines) · ×3
  • Edited copy of a member (36 corresponding lines) csharp/CombatHUD.LootActions.cs:40 — csharp/CombatHUD.LootActions.cs:40-75 | csharp/CombatHUD.LootActions.cs:78-124 — 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) csharp/FreightTerminalWorld.Demolition.SquadNavigation.cs:239 — csharp/FreightTerminalWorld.Demolition.SquadNavigation.cs:239-286 | csharp/FreightTerminalWorld.Demolition.SquadNavigation.cs:343-378 — 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) scripts/blender/author_hy3d_rifle_carry.py:128 — scripts/blender/author_hy3d_rifle_carry.py:128-163 | scripts/blender/bake_hy3d_carry_pose.py:376-430 — 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 copy of a member (11 corresponding lines) · ×3
  • Edited copy of a member (11 corresponding lines) csharp/FreightTerminalWorld.Residential.StreetArt.Diagnostics.cs:422 — csharp/FreightTerminalWorld.Residential.StreetArt.Diagnostics.cs:422-434 | csharp/ResidentialStreetArtBuilder.cs:336-346 — 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) csharp/CombatHUD.Squad.cs:61 — csharp/CombatHUD.Squad.cs:61-71 | csharp/QuickSlotBarView.cs:89-99 — 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) scripts/blender/build_extraction_aircraft.py:337 — scripts/blender/build_extraction_aircraft.py:337-347 | scripts/blender/generate_combat_models.py:202-213 — 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.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×3
  • Edited copy of a member (16 corresponding lines) csharp/JianghaiOldCitySceneLoader.cs:635 — csharp/JianghaiOldCitySceneLoader.cs:635-651 | csharp/ResidentialStreetArtBuilder.cs:384-399 — 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) csharp/FreightTerminalWorld.Refinery.cs:313 — csharp/FreightTerminalWorld.Refinery.cs:313-332 | csharp/ResidentialAuthoredPropLibrary.cs:170-185 — 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) csharp/TacticalPlayer.cs:2447 — csharp/TacticalPlayer.cs:2447-2462 | csharp/TacticalPlayer.Medical.cs:242-258 — 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.
D4 · Code Duplication · Edited copies of one member (4 members, 8+ corresponding lines) · ×3
  • Edited copies of one member (4 members, 8+ corresponding lines) csharp/DemolitionArenaLayout.BazaarCrossing.cs:702 — csharp/DemolitionArenaLayout.BazaarCrossing.cs:702-709 | csharp/DemolitionRouteCursor.cs:127-134 | csharp/ExtractionLootNetworkCodec.cs:10-17 | csharp/FreightTerminalWorld.Squad.Traversal.cs:634-641 — 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) csharp/EnemyOperator.cs:363 — csharp/EnemyOperator.cs:363-370 | csharp/FreightTerminalWorld.Level.cs:18-25 | csharp/LootBackpackVisual.cs:123-130 | csharp/ResidentialSearchableFurniture.cs:263-270 — 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) scripts/blender/build_reloadable_gsh18.py:164 — scripts/blender/build_reloadable_gsh18.py:164-171 | scripts/blender/build_reloadable_quaternius_weapons.py:254-263 | scripts/blender/build_reloadable_scarl.py:173-180 | scripts/blender/build_supplemental_reload_mechanisms.py:513-521 — 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 · Edited copies of one member (3 members, 16+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 16+ corresponding lines) csharp/FreightTerminalWorld.Incendiary.cs:29 — csharp/FreightTerminalWorld.Incendiary.cs:29-44 | csharp/FreightTerminalWorld.Smoke.cs:20-35 | csharp/FreightTerminalWorld.cs:636-652 — 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) scripts/blender/build_jianghai_lattice_door.py:589 — scripts/blender/build_jianghai_lattice_door.py:589-604 | scripts/blender/build_operations_office_set.py:636-656 | scripts/blender/build_orbital_complex.py:1717-1738 — 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) scripts/blender/build_djmaesen_smg45.py:563 — scripts/blender/build_djmaesen_smg45.py:563-578 | scripts/blender/build_tastytony_gsh18.py:51-66 | scripts/blender/build_trey_modular_industrial.py:1693-1709 — 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 · Duplicated block (18 lines × 3) · ×3
  • Duplicated block (18 lines × 3) csharp/FreightTerminalWorld.Extraction.cs:495 — csharp/FreightTerminalWorld.Extraction.cs:495-512 | csharp/FreightTerminalWorld.Extraction.cs:627-644 | csharp/FreightTerminalWorld.cs:3608-3625 — 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 (18 lines × 3) csharp/FreightTerminalWorld.cs:3355 — csharp/FreightTerminalWorld.cs:3355-3372 | csharp/FreightTerminalWorld.cs:6869-6886 | csharp/FreightTerminalWorld.cs:6911-6928 — 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 (18 lines × 3) REDACTED:936 — REDACTED:936-953 | scripts/blender/build_jianghai_valley_environment.py:2337-2354 | scripts/blender/export_jianghai_old_city.py:1655-1672 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `REDACTED: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.
D4 · Code Duplication · Duplicated block (18–19 lines × 2) · ×3
  • Duplicated block (18–19 lines × 2) csharp/FreightTerminalWorld.Squad.NavGrid.cs:1016 — csharp/FreightTerminalWorld.Squad.NavGrid.cs:1016-1033 | csharp/FreightTerminalWorld.Squad.NavGrid.cs:1087-1105 — 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 (18–19 lines × 2) csharp/TacticalPlayer.Demolition.cs:39 — csharp/TacticalPlayer.Demolition.cs:39-56 | csharp/TacticalPlayer.TrainingRange.cs:43-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 `csharp/TacticalPlayer.Demolition.cs:39` 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–19 lines × 2) scripts/blender/build_bazaar_crossing.py:7712 — scripts/blender/build_bazaar_crossing.py:7712-7730 | scripts/blender/build_bazaar_crossing.py:7854-7871 — 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 `scripts/blender/build_bazaar_crossing.py:7712` it begins part-way through the construct above it, so those 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 × 3) · ×3
  • Duplicated block (12 lines × 3) csharp/FreightTerminalWorld.Demolition.TideglassReactor.AssetDiagnostics.cs:347 — csharp/FreightTerminalWorld.Demolition.TideglassReactor.AssetDiagnostics.cs:347-358 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:1073-1084 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.StructureDiagnostics.cs:220-231 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/FreightTerminalWorld.Demolition.TideglassReactor.AssetDiagnostics.cs:347` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those 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) REDACTED:628 — REDACTED:628-639 | scripts/blender/build_jianghai_valley_environment.py:1988-1999 | scripts/blender/export_jianghai_old_city.py:1369-1380 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `REDACTED: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.
  • Duplicated block (12 lines × 3) REDACTED:902 — REDACTED:902-913 | scripts/blender/build_jianghai_valley_environment.py:2303-2314 | scripts/blender/export_jianghai_old_city.py:1621-1632 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `REDACTED:902` it does not close everything it opens, so those 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–12 lines × 2) · ×3
  • Duplicated block (11–12 lines × 2) csharp/FreightTerminalWorld.Melee.Combat.Diagnostics.cs:118 — csharp/FreightTerminalWorld.Melee.Combat.Diagnostics.cs:118-129 | csharp/FreightTerminalWorld.Melee.Combat.Diagnostics.cs:132-142 — 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–12 lines × 2) csharp/FreightTerminalWorld.Refinery.Capture.cs:263 — csharp/FreightTerminalWorld.Refinery.Capture.cs:263-274 | csharp/FreightTerminalWorld.Refinery.Capture.cs:301-311 — 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 (11–12 lines × 2) scripts/blender/build_bazaar_crossing.py:1214 — scripts/blender/build_bazaar_crossing.py:1214-1224 | scripts/blender/build_bazaar_crossing.py:2178-2189 — 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 `scripts/blender/build_bazaar_crossing.py:1214` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code 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 × 3) · ×3
  • Duplicated block (11 lines × 3) csharp/CombatModelLibrary.FirstPerson.cs:75 — csharp/CombatModelLibrary.FirstPerson.cs:75-85 | csharp/CombatModelLibrary.Melee.cs:136-146 | csharp/CombatModelLibrary.cs:2561-2571 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/CombatModelLibrary.FirstPerson.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 (11 lines × 3) scripts/blender/build_animated_reload_arms.py:939 — scripts/blender/build_animated_reload_arms.py:939-949 | scripts/blender/build_animated_reload_arms.py:951-961 | scripts/blender/build_animated_reload_arms.py:962-972 — 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. 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) scripts/blender/build_jianghai_valley_environment.py:2493 — scripts/blender/build_jianghai_valley_environment.py:2493-2503 | scripts/blender/export_jianghai_old_city.py:1831-1841 | scripts/blender/export_jianghai_old_city.py:2817-2827 — before extracting anything, compare `scripts/blender/build_jianghai_valley_environment.py` and `scripts/blender/export_jianghai_old_city.py` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 759 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 (8–11 lines × 2) · ×3
  • Duplicated block (8–11 lines × 2) csharp/FreightTerminalWorld.cs:5133 — csharp/FreightTerminalWorld.cs:5133-5143 | csharp/FreightTerminalWorld.cs:6825-6832 — 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 `csharp/FreightTerminalWorld.cs:5133` 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–11 lines × 2) scripts/blender/author_hy3d_pistol_carry.py:110 — scripts/blender/author_hy3d_pistol_carry.py:110-117 | scripts/blender/author_hy3d_pistol_carry.py:230-240 — 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) scripts/blender/build_orbital_complex_underground.py:544 — scripts/blender/build_orbital_complex_underground.py:544-554 | scripts/blender/build_orbital_complex_underground.py:649-656 — 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 `scripts/blender/build_orbital_complex_underground.py: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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code 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 × 2) · ×3
  • Duplicated block (9–10 lines × 2) csharp/CombatModelLibrary.cs:974 — csharp/CombatModelLibrary.cs:974-983 | csharp/FreightTerminalWorld.RelayStations.cs:519-527 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/FreightTerminalWorld.RelayStations.cs:519` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those 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) csharp/ResidentialTowerArtBuilder.cs:97 — csharp/ResidentialTowerArtBuilder.cs:97-105 | csharp/ResidentialTowerArtBuilder.cs:117-126 — 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 `csharp/ResidentialTowerArtBuilder.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 (9–10 lines × 2) scripts/blender/build_jianghai_valley_environment.py:2725 — scripts/blender/build_jianghai_valley_environment.py:2725-2734 | scripts/blender/export_jianghai_old_city.py:2088-2096 — before extracting anything, compare `scripts/blender/build_jianghai_valley_environment.py` and `scripts/blender/export_jianghai_old_city.py` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 759 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 `scripts/blender/build_jianghai_valley_environment.py:2725` it begins part-way through the construct above it, so those 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 × 4) · ×3
  • Duplicated block (5 lines × 4) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GlassDiagnostics.cs:691 — csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GlassDiagnostics.cs:691-695 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:37-41 | csharp/FreightTerminalWorld.Refinery.NavigationValidation.cs:60-64 | csharp/FreightTerminalWorld.Refinery.NavigationValidation.cs:311-315 — 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 `csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GlassDiagnostics.cs:691` it does not close everything it opens, so those exact lines 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) csharp/FreightTerminalWorld.Demolition.TideglassReactor.WalkwayPhysicsDiagnostics.cs:43 — csharp/FreightTerminalWorld.Demolition.TideglassReactor.WalkwayPhysicsDiagnostics.cs:43-47 | csharp/FreightTerminalWorld.Demolition.cs:972-976 | csharp/FreightTerminalWorld.ExtractionSpawns.Diagnostics.cs:72-76 | csharp/FreightTerminalWorld.IndustrialInteriors.Diagnostics.cs:301-305 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/FreightTerminalWorld.Demolition.TideglassReactor.WalkwayPhysicsDiagnostics.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 (5 lines × 4) REDACTED:728 — REDACTED:728-732 | REDACTED:788-792 | scripts/blender/build_jianghai_valley_environment.py:2107-2111 | scripts/blender/build_jianghai_valley_environment.py:2192-2196 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `REDACTED:733` calls `inverted_safe` and `REDACTED:793` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting 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 × 4) · ×3
  • Duplicated block (6 lines × 4) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GlassDiagnostics.cs:689 — csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GlassDiagnostics.cs:689-694 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:35-40 | csharp/FreightTerminalWorld.Interdistrict.cs:711-716 | csharp/FreightTerminalWorld.Refinery.NavigationValidation.cs:309-314 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GlassDiagnostics.cs:689` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different 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) scripts/blender/build_operations_office_set.py:135 — scripts/blender/build_operations_office_set.py:135-140 | scripts/blender/build_quaternius_buildings_pack.py:185-190 | scripts/blender/build_tideglass_map_assets.py:151-156 | scripts/blender/build_trey_modular_industrial.py:1594-1599 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (6 lines × 4) scripts/blender/build_operations_office_set.py:637 — scripts/blender/build_operations_office_set.py:637-642 | scripts/blender/build_quaternius_buildings_pack.py:540-545 | scripts/blender/build_tideglass_map_assets.py:761-766 | scripts/blender/build_trey_modular_industrial.py:2368-2373 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `scripts/blender/build_operations_office_set.py:637` it does not close everything it opens, so those 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) · ×3
  • Duplicated block (30 lines × 2) REDACTED:623 — REDACTED:623-652 | scripts/blender/build_jianghai_valley_environment.py:1983-2012 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (30 lines × 2) scripts/blender/build_jianghai_valley_environment.py:2425 — scripts/blender/build_jianghai_valley_environment.py:2425-2454 | scripts/blender/export_jianghai_old_city.py:1760-1789 — before extracting anything, compare `scripts/blender/build_jianghai_valley_environment.py` and `scripts/blender/export_jianghai_old_city.py` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 759 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 (30 lines × 2) scripts/blender/build_jianghai_valley_environment.py:2683 — scripts/blender/build_jianghai_valley_environment.py:2683-2712 | scripts/blender/export_jianghai_old_city.py:2027-2056 — before extracting anything, compare `scripts/blender/build_jianghai_valley_environment.py` and `scripts/blender/export_jianghai_old_city.py` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 759 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 `scripts/blender/build_jianghai_valley_environment.py:2683` it begins part-way through the construct above it, so those 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 lines × 2) · ×3
  • Duplicated block (25 lines × 2) REDACTED:513 — REDACTED:513-537 | scripts/blender/build_jianghai_valley_environment.py:1876-1900 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 first that the copies are not typed on the same thing: the declarations holding them bind `foundation` to `bpy.types.Object | None` in one and `bpy.types.Object` 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 (25 lines × 2) scripts/blender/build_jianghai_valley_environment.py:2525 — scripts/blender/build_jianghai_valley_environment.py:2525-2549 | scripts/blender/export_jianghai_old_city.py:1866-1890 — before extracting anything, compare `scripts/blender/build_jianghai_valley_environment.py` and `scripts/blender/export_jianghai_old_city.py` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 759 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 `scripts/blender/build_jianghai_valley_environment.py:2525` it begins part-way through the construct above it, so those exact lines 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) scripts/blender/build_authored_optics.py:993 — scripts/blender/build_authored_optics.py:993-1017 | scripts/blender/build_nisu_m4a1.py:175-199 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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.
D4 · Code Duplication · Duplicated block (7–10 lines × 2) · ×3
  • Duplicated block (7–10 lines × 2) scripts/blender/author_hy3d_rifle_carry.py:154 — scripts/blender/author_hy3d_rifle_carry.py:154-160 | scripts/blender/bake_hy3d_carry_pose.py:414-423 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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–10 lines × 2) scripts/blender/build_jianghai_valley_environment.py:2393 — scripts/blender/build_jianghai_valley_environment.py:2393-2399 | scripts/blender/export_jianghai_old_city.py:1186-1195 — before extracting anything, compare `scripts/blender/build_jianghai_valley_environment.py` and `scripts/blender/export_jianghai_old_city.py` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 759 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 (7–10 lines × 2) scripts/blender/export_jianghai_old_city.py:1704 — scripts/blender/export_jianghai_old_city.py:1704-1710 | scripts/blender/export_jianghai_old_city.py:2609-2618 — 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 `scripts/blender/export_jianghai_old_city.py:1704` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code 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 × 5) · ×3
  • Duplicated block (6 lines × 5) scripts/blender/build_animated_reload_arms.py:2633 — scripts/blender/build_animated_reload_arms.py:2633-2638 | scripts/blender/build_djmaesen_smg45.py:455-460 | scripts/blender/build_first_person_arms.py:443-448 | scripts/blender/build_tastytony_gsh18.py:71-76 | scripts/blender/build_tide_hunter_monster.py:222-227 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `scripts/blender/build_animated_reload_arms.py:2633` it does not close everything it opens, so those exact lines 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) scripts/blender/build_authored_optics.py:530 — scripts/blender/build_authored_optics.py:530-535 | scripts/blender/build_hy3d_operator.py:429-434 | scripts/blender/build_nisu_m4a1.py:489-494 | scripts/blender/build_nisu_m4a1.py:501-506 | scripts/blender/build_nisu_m4a1.py:743-748 — 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 (6 lines × 5) scripts/blender/build_reloadable_gsh18.py:279 — scripts/blender/build_reloadable_gsh18.py:279-284 | scripts/blender/build_reloadable_quaternius_weapons.py:422-427 | scripts/blender/build_reloadable_quaternius_weapons.py:529-534 | scripts/blender/build_supplemental_reload_mechanisms.py:790-795 | scripts/blender/build_taradavies_ak47.py:658-663 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `scripts/blender/build_reloadable_quaternius_weapons.py:429` calls `mp5a5_magazine_face_indices` and `scripts/blender/build_reloadable_gsh18.py: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.
X18 · Disposal-pattern correctness · Owned disposable field overwritten without releasing the previous instance · ×3
  • Owned disposable field overwritten without releasing the previous instance csharp/CombatHUD.cs:1609 — `_hitTween` is a `Tween` this type creates itself, and here (line 1609) a new instance is written over it — but `ShowHit` itself reads through `_hitTween` before replacing it, so it expects an instance to be there, and nothing earlier in `ShowHit` disposes, closes, saves or hands on the instance being replaced. The assignment makes it unreachable while it still holds what it holds (a timer that keeps firing, a callback registered on a longer-lived token, a socket, a handle), and no later `Dispose` can reach it: the type's own disposal releases only the CURRENT instance. The cost accumulates once per overwrite. Release the previous instance first (`_hitTween?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back.
  • Owned disposable field overwritten without releasing the previous instance csharp/CombatHUD.cs:1620 — `_damageTween` is a `Tween` this type creates itself, and here (line 1620) a new instance is written over it — but `ShowDamage` itself reads through `_damageTween` before replacing it, so it expects an instance to be there, and nothing earlier in `ShowDamage` disposes, closes, saves or hands on the instance being replaced. The assignment makes it unreachable while it still holds what it holds (a timer that keeps firing, a callback registered on a longer-lived token, a socket, a handle), and no later `Dispose` can reach it: the type's own disposal releases only the CURRENT instance. The cost accumulates once per overwrite. Release the previous instance first (`_damageTween?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back.
  • Owned disposable field overwritten without releasing the previous instance csharp/CombatHUD.cs:1640 — `_radioTween` is a `Tween` this type creates itself, and here (line 1640) a new instance is written over it — but `ShowRadioMessage` itself reads through `_radioTween` before replacing it, so it expects an instance to be there, and nothing earlier in `ShowRadioMessage` disposes, closes, saves or hands on the instance being replaced. The assignment makes it unreachable while it still holds what it holds (a timer that keeps firing, a callback registered on a longer-lived token, a socket, a handle), and no later `Dispose` can reach it: the type's own disposal releases only the CURRENT instance. The cost accumulates once per overwrite. Release the previous instance first (`_radioTween?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back.
X2 · Cancellation propagation · Async local function without CancellationToken · ×3
  • Async local function without CancellationToken: MeasureAfterInheritedPose csharp/FreightTerminalWorld.WeaponPoseDiagnostics.cs:299 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
  • Async local function without CancellationToken: MeasureCurrentPose csharp/FreightTerminalWorld.WeaponPoseDiagnostics.cs:309 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
  • Async local function without CancellationToken: MeasureOpticClearance csharp/FreightTerminalWorld.WeaponPoseDiagnostics.cs:340 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
D17 · Explicit Debt · BarePragmaDisable · ×2
  • BarePragmaDisable csharp/CombatModelLibrary.cs:635 — #pragma warning disable CS0618 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • BarePragmaDisable csharp/CombatModelLibrary.cs:1039 — #pragma warning disable CS0618 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
D35 · Change Coupling · Change coupling · ×2
  • Change coupling: LootDragControls.cs ↔ TacticalPlayer.cs csharp/LootDragControls.cs:1 — `csharp/LootDragControls.cs` and `csharp/TacticalPlayer.cs` change together 53% of the time (9 of the 17 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 9 shared commits counted here, the most recent 3 are `5ead0616` Fix targeted weapon slot replacement; `486bdd4f` Link backpack ammunition to weapon reserves; `818010dd` Add loot comparison and preserve item grades — run `git show` on any of them.
  • Change coupling: DeploymentMapRuntime.cs ↔ GameLocalization.cs csharp/DeploymentMapRuntime.cs:1 — `csharp/DeploymentMapRuntime.cs` and `csharp/GameLocalization.cs` change together 50% of the time (7 of the 14 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 `81fe341f` Add authored ladders for Lantern Canal river egress; `02964cbd` Remove Lastlight Survival from the extraction map selector; `d10bfa6f` Add Lantern Canal extraction map — run `git show` on any of them.
D4 · Code Duplication · Members sharing a duplicated core (7 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (7 members, 50+ identical tokens) csharp/FreightIndustrialPalette.cs:224 — csharp/FreightIndustrialPalette.cs:224-249 | csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs:766-785 | csharp/FreightTerminalWorld.Demolition.HarborLocks.Diagnostics.cs:230-285 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:1053-1084 | csharp/FreightTerminalWorld.Residential.StreetArt.Diagnostics.cs:365-401 | csharp/FreightTerminalWorld.Residential.StreetArt.Diagnostics.cs:442-473 | csharp/ResidentialStreetArtBuilder.cs:354-381 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 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.
  • Members sharing a duplicated core (7 members, 50+ identical tokens) scripts/blender/build_authored_optics.py:150 — scripts/blender/build_authored_optics.py:150-161 | scripts/blender/build_nisu_m4a1.py:133-144 | scripts/blender/build_reloadable_gsh18.py:137-148 | scripts/blender/build_reloadable_quaternius_weapons.py:223-234 | scripts/blender/build_reloadable_scarl.py:141-152 | scripts/blender/build_supplemental_reload_mechanisms.py:258-269 | tools/build_enterable_industrial_buildings.py:32-43 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 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 · Edited copy of a member (46 corresponding lines) · ×2
  • Edited copy of a member (46 corresponding lines) csharp/LowPolyBuildingArtBuilder.Profiles.cs:16 — csharp/LowPolyBuildingArtBuilder.Profiles.cs:16-61 | csharp/LowPolyBuildingArtBuilder.Profiles.cs:138-193 — 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) csharp/CombatHUD.Deployment.cs:380 — csharp/CombatHUD.Deployment.cs:380-430 | csharp/CombatHUD.Deployment.cs:433-478 — 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 copy of a member (55 corresponding lines) · ×2
  • Edited copy of a member (55 corresponding lines) csharp/FreightTerminalWorld.Expansion.cs:915 — csharp/FreightTerminalWorld.Expansion.cs:915-982 | csharp/FreightTerminalWorld.Level.cs:1182-1236 — 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.
  • Edited copy of a member (55 corresponding lines) scripts/blender/build_orbital_complex.py:1404 — scripts/blender/build_orbital_complex.py:1404-1474 | scripts/blender/build_orbital_complex_underground.py:1513-1567 — 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 (32 corresponding lines) · ×2
  • Edited copy of a member (32 corresponding lines) csharp/CombatHUD.Squad.cs:493 — csharp/CombatHUD.Squad.cs:493-533 | csharp/DemolitionBriefingView.cs:414-445 — 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) csharp/FreightTerminalWorld.Demolition.Utility.cs:298 — csharp/FreightTerminalWorld.Demolition.Utility.cs:298-329 | csharp/FreightTerminalWorld.Demolition.Utility.cs:335-375 — 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 copies of one member (3 members, 19+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 19+ corresponding lines) csharp/SoundLab.cs:549 — csharp/SoundLab.cs:549-569 | csharp/SoundLab.cs:576-596 | csharp/SoundLab.cs:605-623 — 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) csharp/FreightTerminalWorld.LanternCanal.Diagnostics.cs:366 — csharp/FreightTerminalWorld.LanternCanal.Diagnostics.cs:366-384 | csharp/FreightTerminalWorld.LanternCanal.Diagnostics.cs:387-405 | csharp/FreightTerminalWorld.LanternCanal.Diagnostics.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.
D4 · Code Duplication · Edited copy of a member (40 corresponding lines) · ×2
  • Edited copy of a member (40 corresponding lines) csharp/FreightTerminalWorld.Squad.EmergencyEgress.Planning.cs:194 — csharp/FreightTerminalWorld.Squad.EmergencyEgress.Planning.cs:194-243 | csharp/FreightTerminalWorld.Squad.EmergencyEgress.Planning.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) scripts/blender/build_tideglass_map_assets.py:221 — scripts/blender/build_tideglass_map_assets.py:221-267 | scripts/blender/build_trey_modular_industrial.py:1632-1671 — 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 copy of a member (18 corresponding lines) · ×2
  • Edited copy of a member (18 corresponding lines) csharp/FreightTerminalWorld.cs:559 — csharp/FreightTerminalWorld.cs:559-577 | csharp/FreightTerminalWorld.Squad.cs:2420-2437 — 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) scripts/blender/build_demolition_device.py:145 — scripts/blender/build_demolition_device.py:145-162 | scripts/blender/build_demolition_device.py:176-194 — 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.
D4 · Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 13+ corresponding lines) csharp/FreightTerminalWorld.Residential.cs:1790 — csharp/FreightTerminalWorld.Residential.cs:1790-1803 | csharp/JianghaiInteriorPopulationService.cs:433-445 | csharp/ResidentialAuthoredPropLibrary.cs:350-363 — 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) csharp/SquadNetwork.Extraction.Doors.cs:12 — csharp/SquadNetwork.Extraction.Doors.cs:12-24 | csharp/SquadNetwork.Extraction.Loot.cs:15-27 | csharp/SquadNetwork.Extraction.World.cs:151-163 — 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 (4 members, 4+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 4+ corresponding lines) csharp/CombatHUD.LootComparison.cs:385 — csharp/CombatHUD.LootComparison.cs:385-390 | csharp/LootDragControls.cs:557-562 | csharp/LootWeaponSlotView.cs:172-175 | csharp/OperationsOfficeBackdrop.Environment.cs:181-184 — 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) scripts/blender/build_nisu_m4a1.py:1511 — scripts/blender/build_nisu_m4a1.py:1511-1514 | scripts/blender/build_reloadable_gsh18.py:1043-1046 | scripts/blender/build_reloadable_quaternius_weapons.py:1195-1198 | scripts/blender/build_reloadable_scarl.py:749-752 — 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 · Edited copies of one member (3 members, 8+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 8+ corresponding lines) csharp/DemolitionArenaLayout.cs:745 — csharp/DemolitionArenaLayout.cs:745-752 | csharp/DemolitionRetakeDistribution.Diagnostics.cs:416-423 | csharp/DemolitionRoutePlanner.cs:304-311 — 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) scripts/blender/build_demolition_device.py:416 — scripts/blender/build_demolition_device.py:416-423 | scripts/blender/build_field_use_props.py:750-757 | scripts/blender/build_orbital_complex.py:1742-1749 — 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.
D4 · Code Duplication · Edited copies of one member (3 members, 18+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 18+ corresponding lines) csharp/DemolitionArenaBuilder.cs:150 — csharp/DemolitionArenaBuilder.cs:150-183 | csharp/FreightTerminalWorld.Expansion.cs:1174-1191 | csharp/FreightTerminalWorld.Level.cs:1491-1508 — 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) scripts/blender/build_authored_optics.py:192 — scripts/blender/build_authored_optics.py:192-210 | scripts/blender/build_nisu_m4a1.py:295-312 | scripts/blender/build_taradavies_ak47.py:499-520 — 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 · Duplicated block (24–25 lines × 2) · ×2
  • Duplicated block (24–25 lines × 2) csharp/EnemyOperator.cs:1937 — csharp/EnemyOperator.cs:1937-1961 | csharp/EnemyOperator.cs:2027-2050 — 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 `csharp/EnemyOperator.cs:1937` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines 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) csharp/FreightTerminalWorld.Expansion.cs:939 — csharp/FreightTerminalWorld.Expansion.cs:939-963 | csharp/FreightTerminalWorld.Level.cs:1201-1224 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/FreightTerminalWorld.Expansion.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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code 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 × 2) · ×2
  • Duplicated block (21 lines × 2) csharp/CombatModelLibrary.cs:2160 — csharp/CombatModelLibrary.cs:2160-2180 | csharp/CombatModelLibrary.cs:2191-2211 — 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 `csharp/CombatModelLibrary.cs:2160` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines 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) csharp/FreightTerminalWorld.Extraction.cs:496 — csharp/FreightTerminalWorld.Extraction.cs:496-516 | csharp/FreightTerminalWorld.Extraction.cs:628-648 — 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 (17–18 lines × 3) · ×2
  • Duplicated block (17–18 lines × 3) csharp/EnemyOperator.cs:1439 — csharp/EnemyOperator.cs:1439-1455 | csharp/SquadMate.Combat.cs:681-698 | csharp/SquadMate.cs:901-918 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different 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) REDACTED:642 — REDACTED:642-659 | scripts/blender/build_jianghai_valley_environment.py:2002-2018 | scripts/blender/export_jianghai_old_city.py:1383-1399 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `REDACTED:642` it does not close everything it opens, so those 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 (11–15 lines × 3) · ×2
  • Duplicated block (11–15 lines × 3) csharp/FreightTerminalWorld.Demolition.EnemyResponse.Diagnostics.cs:288 — csharp/FreightTerminalWorld.Demolition.EnemyResponse.Diagnostics.cs:288-298 | csharp/FreightTerminalWorld.Demolition.EnemyResponse.Diagnostics.cs:386-399 | csharp/FreightTerminalWorld.Demolition.EnemyResponse.Diagnostics.cs:527-541 — 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–15 lines × 3) scripts/blender/build_djmaesen_smg45.py:568 — scripts/blender/build_djmaesen_smg45.py:568-578 | scripts/blender/build_quaternius_buildings_pack.py:204-218 | scripts/blender/build_tastytony_gsh18.py:56-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 all 3 call sites, so a change lands once. 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 (9 lines × 4) · ×2
  • Duplicated block (9 lines × 4) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs:495 — csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs:495-503 | csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs:554-562 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:338-346 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:387-395 — 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.
  • Duplicated block (9 lines × 4) scripts/blender/build_reloadable_gsh18.py:408 — scripts/blender/build_reloadable_gsh18.py:408-416 | scripts/blender/build_reloadable_quaternius_weapons.py:774-782 | scripts/blender/build_reloadable_scarl.py:405-413 | scripts/blender/build_supplemental_reload_mechanisms.py:877-885 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `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–8 lines × 3) · ×2
  • Duplicated block (7–8 lines × 3) csharp/DriveableVehicle.cs:605 — csharp/DriveableVehicle.cs:605-612 | csharp/DriveableVehicle.cs:631-638 | csharp/DriveableVehicle.cs:642-648 — 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 (7–8 lines × 3) scripts/blender/build_demolition_device.py:67 — scripts/blender/build_demolition_device.py:67-73 | scripts/blender/build_field_use_props.py:79-85 | scripts/blender/rebuild_pawnshop_frontage.py:118-125 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `scripts/blender/rebuild_pawnshop_frontage.py:118` it begins part-way through the construct above it, so those 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 (4 members, 5+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 5+ corresponding lines) scripts/blender/build_authored_optics.py:259 — scripts/blender/build_authored_optics.py:259-264 | scripts/blender/build_reloadable_gsh18.py:152-156 | scripts/blender/build_reloadable_quaternius_weapons.py:242-246 | scripts/blender/jianghai_enterable_residences.py:81-86 — 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) REDACTED:277 — REDACTED:277-281 | scripts/blender/build_jianghai_lattice_door.py:237-243 | scripts/blender/build_jianghai_lattice_door.py:454-460 | scripts/blender/build_operations_office_set.py:528-539 — 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 · Duplicated block (23 lines × 2) · ×2
  • Duplicated block (23 lines × 2) REDACTED:688 — REDACTED:688-710 | scripts/blender/export_jianghai_old_city.py:1430-1452 — before extracting anything, compare `REDACTED` and `scripts/blender/export_jianghai_old_city.py` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 507 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 `REDACTED: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. 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) scripts/blender/build_demolition_device.py:427 — scripts/blender/build_demolition_device.py:427-449 | scripts/blender/build_field_use_props.py:761-783 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `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 (19–20 lines × 2) · ×2
  • Duplicated block (19–20 lines × 2) scripts/blender/build_bazaar_crossing.py:2428 — scripts/blender/build_bazaar_crossing.py:2428-2446 | scripts/blender/build_bazaar_crossing.py:3126-3145 — 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 (19–20 lines × 2) scripts/blender/build_jianghai_valley_environment.py:2801 — scripts/blender/build_jianghai_valley_environment.py:2801-2819 | scripts/blender/export_jianghai_old_city.py:2178-2197 — before extracting anything, compare `scripts/blender/build_jianghai_valley_environment.py` and `scripts/blender/export_jianghai_old_city.py` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 759 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 `scripts/blender/export_jianghai_old_city.py:2178` it begins part-way through the construct above it, so those 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–12 lines × 2) · ×2
  • Duplicated block (10–12 lines × 2) scripts/blender/author_hy3d_rifle_carry.py:131 — scripts/blender/author_hy3d_rifle_carry.py:131-140 | scripts/blender/bake_hy3d_carry_pose.py:384-395 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `scripts/blender/bake_hy3d_carry_pose.py: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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different 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) scripts/blender/export_jianghai_old_city.py:607 — scripts/blender/export_jianghai_old_city.py:607-616 | scripts/blender/export_jianghai_old_city.py:737-748 — 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 `scripts/blender/export_jianghai_old_city.py: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 `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 (8–9 lines × 2) · ×2
  • Duplicated block (8–9 lines × 2) scripts/blender/build_authored_optics.py:202 — scripts/blender/build_authored_optics.py:202-210 | scripts/blender/build_nisu_m4a1.py:305-312 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `scripts/blender/build_authored_optics.py:202` it begins part-way through the construct above it, so those 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) scripts/blender/build_field_use_props.py:833 — scripts/blender/build_field_use_props.py:833-840 | scripts/blender/build_melee_weapons.py:802-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.
D4 · Code Duplication · Duplicated block (8 lines × 4) · ×2
  • Duplicated block (8 lines × 4) REDACTED:633 — REDACTED:633-640 | scripts/blender/build_jianghai_valley_environment.py:1993-2000 | scripts/blender/build_jianghai_valley_environment.py:2116-2123 | scripts/blender/export_jianghai_old_city.py:1374-1381 — 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.
  • Duplicated block (8 lines × 4) scripts/blender/build_orbital_complex.py:671 — scripts/blender/build_orbital_complex.py:671-678 | scripts/blender/build_orbital_complex.py:718-725 | scripts/blender/build_orbital_complex.py:761-768 | scripts/blender/build_orbital_complex.py:808-815 — 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.
D4 · Code Duplication · Duplicated block (6–7 lines × 2) · ×2
  • Duplicated block (6–7 lines × 2) scripts/blender/build_bazaar_crossing.py:5960 — scripts/blender/build_bazaar_crossing.py:5960-5965 | scripts/blender/build_bazaar_crossing.py:6512-6518 — 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 `scripts/blender/build_bazaar_crossing.py:6512` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different 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) scripts/blender/build_nisu_m4a1.py:487 — scripts/blender/build_nisu_m4a1.py:487-493 | scripts/blender/build_nisu_m4a1.py:500-505 — 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 `scripts/blender/build_nisu_m4a1.py: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.
AX5 · Architecture & structure · Appears unstructured (no recognised architecture) · ×1
  • Appears unstructured (no recognised architecture) — ~170.7k production LoC (1032 types) across 1 project(s) / 22 namespace(s) with no recognised architectural style or layering — at this size, deliberate module boundaries would help. No DDD/clean/vertical-slice/CQRS/transaction-script organisation was detected — code is likely organised ad hoc, which makes change and onboarding harder as it grows.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateSquadFlow (cyclomatic 390) · ×1
  • FreightTerminalWorld.ValidateSquadFlow (cyclomatic 390) csharp/FreightTerminalWorld.Squad.cs:3137 — FreightTerminalWorld.ValidateSquadFlow has cyclomatic complexity 390 (threshold 15). Of this number, 367 points are the body's own statements and 23 belong to 16 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateDemolitionTacticalAi (cyclomatic 301) · ×1
  • FreightTerminalWorld.ValidateDemolitionTacticalAi (cyclomatic 301) csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:865 — FreightTerminalWorld.ValidateDemolitionTacticalAi has cyclomatic complexity 301 (threshold 15). Of this number, 253 points are the body's own statements and 48 belong to 25 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateDemolitionMode (cyclomatic 222) · ×1
  • FreightTerminalWorld.ValidateDemolitionMode (cyclomatic 222) csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:495 — FreightTerminalWorld.ValidateDemolitionMode has cyclomatic complexity 222 (threshold 15). Of this number, 210 points are the body's own statements and 12 belong to 7 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateDemolitionNetworkSession (cyclomatic 187) · ×1
  • FreightTerminalWorld.ValidateDemolitionNetworkSession (cyclomatic 187) csharp/FreightTerminalWorld.Demolition.Network.Diagnostics.cs:83 — FreightTerminalWorld.ValidateDemolitionNetworkSession has cyclomatic complexity 187 (threshold 15). Of this number, 178 points are the body's own statements and 9 belong to 5 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateResidentialGameplay (cyclomatic 186) · ×1
  • FreightTerminalWorld.ValidateResidentialGameplay (cyclomatic 186) csharp/FreightTerminalWorld.Residential.cs:1778 — FreightTerminalWorld.ValidateResidentialGameplay has cyclomatic complexity 186 (threshold 15). Of this number, 169 points are the body's own statements and 17 belong to 14 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateLootFlow (cyclomatic 178) · ×1
  • FreightTerminalWorld.ValidateLootFlow (cyclomatic 178) csharp/FreightTerminalWorld.cs:3788 — FreightTerminalWorld.ValidateLootFlow has cyclomatic complexity 178 (threshold 15). Of this number, 176 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateQuickSlots (cyclomatic 174) · ×1
  • FreightTerminalWorld.ValidateQuickSlots (cyclomatic 174) csharp/FreightTerminalWorld.QuickSlots.Diagnostics.cs:8 — FreightTerminalWorld.ValidateQuickSlots has cyclomatic complexity 174 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateTideglassReactor (cyclomatic 173) · ×1
  • FreightTerminalWorld.ValidateTideglassReactor (cyclomatic 173) csharp/FreightTerminalWorld.Demolition.TideglassReactor.Diagnostics.cs:10 — FreightTerminalWorld.ValidateTideglassReactor has cyclomatic complexity 173 (threshold 15). Of this number, 146 points are the body's own statements and 27 belong to 11 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateDemolitionEnemyResponse (cyclomatic 148) · ×1
  • FreightTerminalWorld.ValidateDemolitionEnemyResponse (cyclomatic 148) csharp/FreightTerminalWorld.Demolition.EnemyResponse.Diagnostics.cs:8 — FreightTerminalWorld.ValidateDemolitionEnemyResponse has cyclomatic complexity 148 (threshold 15). Of this number, 146 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateDemolitionRules (cyclomatic 143) · ×1
  • FreightTerminalWorld.ValidateDemolitionRules (cyclomatic 143) csharp/FreightTerminalWorld.Demolition.Rules.Diagnostics.cs:8 — FreightTerminalWorld.ValidateDemolitionRules has cyclomatic complexity 143 (threshold 15). Of this number, 138 points are the body's own statements and 5 belong to 4 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateTrainingRange (cyclomatic 133) · ×1
  • FreightTerminalWorld.ValidateTrainingRange (cyclomatic 133) csharp/FreightTerminalWorld.TrainingRange.Diagnostics.cs:8 — FreightTerminalWorld.ValidateTrainingRange has cyclomatic complexity 133 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateBazaarCrossingCore (cyclomatic 121) · ×1
  • FreightTerminalWorld.ValidateBazaarCrossingCore (cyclomatic 121) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Diagnostics.cs:45 — FreightTerminalWorld.ValidateBazaarCrossingCore has cyclomatic complexity 121 (threshold 15). Of this number, 102 points are the body's own statements and 19 belong to 10 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateJianghaiInteriors (cyclomatic 115) · ×1
  • FreightTerminalWorld.ValidateJianghaiInteriors (cyclomatic 115) csharp/FreightTerminalWorld.Refinery.Interiors.Diagnostics.cs:9 — FreightTerminalWorld.ValidateJianghaiInteriors has cyclomatic complexity 115 (threshold 15). Of this number, 83 points are the body's own statements and 32 belong to 11 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateSquadTraversal (cyclomatic 115) · ×1
  • FreightTerminalWorld.ValidateSquadTraversal (cyclomatic 115) csharp/FreightTerminalWorld.Squad.Traversal.Diagnostics.cs:11 — FreightTerminalWorld.ValidateSquadTraversal has cyclomatic complexity 115 (threshold 15). Of this number, 102 points are the body's own statements and 13 belong to 8 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateExtractionSurvivors (cyclomatic 107) · ×1
  • FreightTerminalWorld.ValidateExtractionSurvivors (cyclomatic 107) csharp/FreightTerminalWorld.Extraction.Survivors.Diagnostics.cs:9 — FreightTerminalWorld.ValidateExtractionSurvivors has cyclomatic complexity 107 (threshold 15). Of this number, 102 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateTideglassReactorDensityCore (cyclomatic 105) · ×1
  • FreightTerminalWorld.ValidateTideglassReactorDensityCore (cyclomatic 105) csharp/FreightTerminalWorld.Demolition.TideglassReactor.DensityDiagnostics.cs:111 — FreightTerminalWorld.ValidateTideglassReactorDensityCore has cyclomatic complexity 105 (threshold 15). Of this number, 75 points are the body's own statements and 30 belong to 9 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateRefineryDoors (cyclomatic 105) · ×1
  • FreightTerminalWorld.ValidateRefineryDoors (cyclomatic 105) csharp/FreightTerminalWorld.Refinery.Doors.Diagnostics.cs:8 — FreightTerminalWorld.ValidateRefineryDoors has cyclomatic complexity 105 (threshold 15). Of this number, 89 points are the body's own statements and 16 belong to 6 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateSquadSustainment (cyclomatic 103) · ×1
  • FreightTerminalWorld.ValidateSquadSustainment (cyclomatic 103) csharp/FreightTerminalWorld.Squad.Sustainment.Diagnostics.cs:10 — FreightTerminalWorld.ValidateSquadSustainment has cyclomatic complexity 103 (threshold 15). Of this number, 77 points are the body's own statements and 26 belong to 14 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateDemolitionWeapons (cyclomatic 96) · ×1
  • FreightTerminalWorld.ValidateDemolitionWeapons (cyclomatic 96) csharp/FreightTerminalWorld.Demolition.WeaponDrops.Diagnostics.cs:8 — FreightTerminalWorld.ValidateDemolitionWeapons has cyclomatic complexity 96 (threshold 15). Of this number, 95 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateOrbitalComplexIntegration (cyclomatic 95) · ×1
  • FreightTerminalWorld.ValidateOrbitalComplexIntegration (cyclomatic 95) csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Diagnostics.cs:354 — FreightTerminalWorld.ValidateOrbitalComplexIntegration has cyclomatic complexity 95 (threshold 15). Of this number, 89 points are the body's own statements and 6 belong to 4 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateExtractionAi (cyclomatic 95) · ×1
  • FreightTerminalWorld.ValidateExtractionAi (cyclomatic 95) csharp/FreightTerminalWorld.cs:5433 — FreightTerminalWorld.ValidateExtractionAi has cyclomatic complexity 95 (threshold 15). Of this number, 89 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateDemolitionUtility (cyclomatic 92) · ×1
  • FreightTerminalWorld.ValidateDemolitionUtility (cyclomatic 92) csharp/FreightTerminalWorld.Demolition.Utility.Diagnostics.cs:8 — FreightTerminalWorld.ValidateDemolitionUtility has cyclomatic complexity 92 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · TacticalPlayer.RunAuthoritativePhysicsStep (cyclomatic 92) · ×1
  • TacticalPlayer.RunAuthoritativePhysicsStep (cyclomatic 92) csharp/TacticalPlayer.cs:1235 — TacticalPlayer.RunAuthoritativePhysicsStep has cyclomatic complexity 92 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateSkybridgeAccess (cyclomatic 82) · ×1
  • FreightTerminalWorld.ValidateSkybridgeAccess (cyclomatic 82) csharp/FreightTerminalWorld.Residential.Access.cs:625 — FreightTerminalWorld.ValidateSkybridgeAccess has cyclomatic complexity 82 (threshold 15). Of this number, 78 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateDemolitionArena (cyclomatic 81) · ×1
  • FreightTerminalWorld.ValidateDemolitionArena (cyclomatic 81) csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:236 — FreightTerminalWorld.ValidateDemolitionArena has cyclomatic complexity 81 (threshold 15). Of this number, 61 points are the body's own statements and 20 belong to 6 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This is NOT this file's highest cyclomatic complexity: FreightTerminalWorld.ValidateDemolitionBriefing (cyclomatic 112) 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 · FreightTerminalWorld.DemolitionPostPatrolTargetKey (cyclomatic 80) · ×1
  • FreightTerminalWorld.DemolitionPostPatrolTargetKey (cyclomatic 80) csharp/FreightTerminalWorld.Demolition.Posts.cs:161 — FreightTerminalWorld.DemolitionPostPatrolTargetKey has cyclomatic complexity 80 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateOperatorRoster (cyclomatic 77) · ×1
  • FreightTerminalWorld.ValidateOperatorRoster (cyclomatic 77) csharp/FreightTerminalWorld.OperatorRoster.Diagnostics.cs:10 — FreightTerminalWorld.ValidateOperatorRoster has cyclomatic complexity 77 (threshold 15). Of this number, 58 points are the body's own statements and 19 belong to 10 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateStairsClimb (cyclomatic 76) · ×1
  • FreightTerminalWorld.ValidateStairsClimb (cyclomatic 76) csharp/FreightTerminalWorld.cs:6031 — FreightTerminalWorld.ValidateStairsClimb has cyclomatic complexity 76 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateFieldUsePresentation (cyclomatic 74) · ×1
  • FreightTerminalWorld.ValidateFieldUsePresentation (cyclomatic 74) csharp/FreightTerminalWorld.FieldUsePresentation.Diagnostics.cs:7 — FreightTerminalWorld.ValidateFieldUsePresentation has cyclomatic complexity 74 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateSquadPerformance (cyclomatic 74) · ×1
  • FreightTerminalWorld.ValidateSquadPerformance (cyclomatic 74) csharp/FreightTerminalWorld.Squad.Performance.Diagnostics.cs:35 — FreightTerminalWorld.ValidateSquadPerformance has cyclomatic complexity 74 (threshold 15). Of this number, 72 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateAircraftCombat (cyclomatic 70) · ×1
  • FreightTerminalWorld.ValidateAircraftCombat (cyclomatic 70) csharp/FreightTerminalWorld.cs:5023 — FreightTerminalWorld.ValidateAircraftCombat has cyclomatic complexity 70 (threshold 15). Of this number, 67 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateAdsAlignment (cyclomatic 70) · ×1
  • FreightTerminalWorld.ValidateAdsAlignment (cyclomatic 70) csharp/FreightTerminalWorld.WeaponPoseDiagnostics.cs:9 — FreightTerminalWorld.ValidateAdsAlignment has cyclomatic complexity 70 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateExtractionSequence (cyclomatic 68) · ×1
  • FreightTerminalWorld.ValidateExtractionSequence (cyclomatic 68) csharp/FreightTerminalWorld.Extraction.cs:493 — FreightTerminalWorld.ValidateExtractionSequence has cyclomatic complexity 68 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · EnemyOperator._PhysicsProcess (cyclomatic 67) · ×1
  • EnemyOperator._PhysicsProcess (cyclomatic 67) csharp/EnemyOperator.cs:588 — EnemyOperator._PhysicsProcess has cyclomatic complexity 67 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateWeaponUiFlow (cyclomatic 66) · ×1
  • FreightTerminalWorld.ValidateWeaponUiFlow (cyclomatic 66) csharp/FreightTerminalWorld.cs:4596 — FreightTerminalWorld.ValidateWeaponUiFlow has cyclomatic complexity 66 (threshold 15). Of this number, 62 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · EnemyOperator.Engage (cyclomatic 64) · ×1
  • EnemyOperator.Engage (cyclomatic 64) csharp/EnemyOperator.cs:1549 — EnemyOperator.Engage has cyclomatic complexity 64 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateWorldBoss (cyclomatic 60) · ×1
  • FreightTerminalWorld.ValidateWorldBoss (cyclomatic 60) csharp/FreightTerminalWorld.Boss.cs:221 — FreightTerminalWorld.ValidateWorldBoss has cyclomatic complexity 60 (threshold 15). Of this number, 51 points are the body's own statements and 9 belong to 7 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateIndustrialInteriors (cyclomatic 59) · ×1
  • FreightTerminalWorld.ValidateIndustrialInteriors (cyclomatic 59) csharp/FreightTerminalWorld.IndustrialInteriors.Diagnostics.cs:10 — FreightTerminalWorld.ValidateIndustrialInteriors has cyclomatic complexity 59 (threshold 15). Of this number, 49 points are the body's own statements and 10 belong to 5 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateDistrictNetwork (cyclomatic 59) · ×1
  • FreightTerminalWorld.ValidateDistrictNetwork (cyclomatic 59) csharp/FreightTerminalWorld.Interdistrict.cs:563 — FreightTerminalWorld.ValidateDistrictNetwork has cyclomatic complexity 59 (threshold 15). Of this number, 56 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateEnterableDoorways (cyclomatic 59) · ×1
  • FreightTerminalWorld.ValidateEnterableDoorways (cyclomatic 59) csharp/FreightTerminalWorld.Refinery.EnterableCollisionValidation.cs:9 — FreightTerminalWorld.ValidateEnterableDoorways has cyclomatic complexity 59 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateDemolitionDefenseRound (cyclomatic 58) · ×1
  • FreightTerminalWorld.ValidateDemolitionDefenseRound (cyclomatic 58) csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:3030 — FreightTerminalWorld.ValidateDemolitionDefenseRound has cyclomatic complexity 58 (threshold 15). Of this number, 55 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This is NOT this file's highest cyclomatic complexity: FreightTerminalWorld.ValidateDemolitionBriefing (cyclomatic 112) 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 · FreightTerminalWorld.ValidateMedicalSystem (cyclomatic 57) · ×1
  • FreightTerminalWorld.ValidateMedicalSystem (cyclomatic 57) csharp/FreightTerminalWorld.Survival.cs:9 — FreightTerminalWorld.ValidateMedicalSystem has cyclomatic complexity 57 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateBackpackTab (cyclomatic 56) · ×1
  • FreightTerminalWorld.ValidateBackpackTab (cyclomatic 56) csharp/FreightTerminalWorld.cs:6298 — FreightTerminalWorld.ValidateBackpackTab has cyclomatic complexity 56 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateMeleeCombatSemantics (cyclomatic 56) · ×1
  • FreightTerminalWorld.ValidateMeleeCombatSemantics (cyclomatic 56) csharp/FreightTerminalWorld.Melee.Combat.Diagnostics.cs:71 — FreightTerminalWorld.ValidateMeleeCombatSemantics has cyclomatic complexity 56 (threshold 15). Of this number, 52 points are the body's own statements and 4 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateArsenalFlow (cyclomatic 54) · ×1
  • FreightTerminalWorld.ValidateArsenalFlow (cyclomatic 54) csharp/FreightTerminalWorld.cs:4790 — FreightTerminalWorld.ValidateArsenalFlow has cyclomatic complexity 54 (threshold 15). Of this number, 52 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · TacticalPlayer.ApplyWeaponBuildVisuals (cyclomatic 54) · ×1
  • TacticalPlayer.ApplyWeaponBuildVisuals (cyclomatic 54) csharp/TacticalPlayer.cs:1004 — TacticalPlayer.ApplyWeaponBuildVisuals has cyclomatic complexity 54 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateAircraftBehavior (cyclomatic 53) · ×1
  • FreightTerminalWorld.ValidateAircraftBehavior (cyclomatic 53) csharp/FreightTerminalWorld.AircraftBehavior.Diagnostics.cs:8 — FreightTerminalWorld.ValidateAircraftBehavior has cyclomatic complexity 53 (threshold 15). Of this number, 52 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateResidentialCommunity (cyclomatic 52) · ×1
  • FreightTerminalWorld.ValidateResidentialCommunity (cyclomatic 52) csharp/FreightTerminalWorld.Residential.cs:1493 — FreightTerminalWorld.ValidateResidentialCommunity has cyclomatic complexity 52 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · TacticalPlayer.InspectAllWeaponReloadForDiagnostics (cyclomatic 51) · ×1
  • TacticalPlayer.InspectAllWeaponReloadForDiagnostics (cyclomatic 51) csharp/TacticalPlayer.ReloadDiagnostics.cs:9 — TacticalPlayer.InspectAllWeaponReloadForDiagnostics has cyclomatic complexity 51 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · TacticalPlayer.InspectOpticClearanceForDiagnostics (cyclomatic 51) · ×1
  • TacticalPlayer.InspectOpticClearanceForDiagnostics (cyclomatic 51) csharp/TacticalPlayer.WeaponPose.cs:398 — TacticalPlayer.InspectOpticClearanceForDiagnostics has cyclomatic complexity 51 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · DemolitionArenaLayout.DemolitionArenaLayout.ctor (cyclomatic 50) · ×1
  • DemolitionArenaLayout.DemolitionArenaLayout.ctor (cyclomatic 50) csharp/DemolitionArenaLayout.cs:134 — DemolitionArenaLayout.DemolitionArenaLayout.ctor has cyclomatic complexity 50 (threshold 15). Of this number, 49 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.TideglassWalkwayCollisionReady (cyclomatic 48) · ×1
  • FreightTerminalWorld.TideglassWalkwayCollisionReady (cyclomatic 48) csharp/FreightTerminalWorld.Demolition.TideglassReactor.StructureDiagnostics.cs:10 — FreightTerminalWorld.TideglassWalkwayCollisionReady has cyclomatic complexity 48 (threshold 15). Of this number, 45 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.OperatorCarrySampleValid (cyclomatic 47) · ×1
  • FreightTerminalWorld.OperatorCarrySampleValid (cyclomatic 47) csharp/FreightTerminalWorld.OperatorCarry.Diagnostics.cs:242 — FreightTerminalWorld.OperatorCarrySampleValid has cyclomatic complexity 47 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateRoofAccess (cyclomatic 47) · ×1
  • FreightTerminalWorld.ValidateRoofAccess (cyclomatic 47) csharp/FreightTerminalWorld.RoofAccess.cs:372 — FreightTerminalWorld.ValidateRoofAccess has cyclomatic complexity 47 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateSkyLinks (cyclomatic 46) · ×1
  • FreightTerminalWorld.ValidateSkyLinks (cyclomatic 46) csharp/FreightTerminalWorld.cs:6447 — FreightTerminalWorld.ValidateSkyLinks has cyclomatic complexity 46 (threshold 15). Of this number, 42 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.BuildSquadSystem (cyclomatic 46) · ×1
  • FreightTerminalWorld.BuildSquadSystem (cyclomatic 46) csharp/FreightTerminalWorld.Squad.cs:116 — FreightTerminalWorld.BuildSquadSystem has cyclomatic complexity 46 (threshold 15). Most of this is not in the body itself: 14 of the 46 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 193, 226). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest. This is NOT this file's highest cyclomatic complexity: FreightTerminalWorld.ValidateNetworkEndpoint (cyclomatic 64) 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 · DemolitionUtilityPlanner.Plan (cyclomatic 45) · ×1
  • DemolitionUtilityPlanner.Plan (cyclomatic 45) csharp/DemolitionUtilityPlanner.cs:47 — DemolitionUtilityPlanner.Plan has cyclomatic complexity 45 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.UpdateInteraction (cyclomatic 45) · ×1
  • FreightTerminalWorld.UpdateInteraction (cyclomatic 45) csharp/FreightTerminalWorld.cs:2275 — FreightTerminalWorld.UpdateInteraction has cyclomatic complexity 45 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.BazaarAuthoredVisualsReady (cyclomatic 45) · ×1
  • FreightTerminalWorld.BazaarAuthoredVisualsReady (cyclomatic 45) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs:582 — FreightTerminalWorld.BazaarAuthoredVisualsReady has cyclomatic complexity 45 (threshold 15). Of this number, 44 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateBreakableGlass (cyclomatic 45) · ×1
  • FreightTerminalWorld.ValidateBreakableGlass (cyclomatic 45) csharp/FreightTerminalWorld.Glass.cs:50 — FreightTerminalWorld.ValidateBreakableGlass has cyclomatic complexity 45 (threshold 15). Of this number, 35 points are the body's own statements and 10 belong to 4 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateSquadIndoorRevive (cyclomatic 45) · ×1
  • FreightTerminalWorld.ValidateSquadIndoorRevive (cyclomatic 45) csharp/FreightTerminalWorld.Squad.IndoorRevive.Diagnostics.cs:10 — FreightTerminalWorld.ValidateSquadIndoorRevive has cyclomatic complexity 45 (threshold 15). Of this number, 39 points are the body's own statements and 6 belong to 5 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · SquadMate._PhysicsProcess (cyclomatic 45) · ×1
  • SquadMate._PhysicsProcess (cyclomatic 45) csharp/SquadMate.cs:496 — SquadMate._PhysicsProcess has cyclomatic complexity 45 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateAiNavigation (cyclomatic 44) · ×1
  • FreightTerminalWorld.ValidateAiNavigation (cyclomatic 44) csharp/FreightTerminalWorld.AiNavigation.Diagnostics.cs:10 — FreightTerminalWorld.ValidateAiNavigation has cyclomatic complexity 44 (threshold 15). Of this number, 39 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidatePauseUi (cyclomatic 44) · ×1
  • FreightTerminalWorld.ValidatePauseUi (cyclomatic 44) csharp/FreightTerminalWorld.PauseDiagnostics.cs:9 — FreightTerminalWorld.ValidatePauseUi has cyclomatic complexity 44 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ResolveSquadNavigationDestination (cyclomatic 44) · ×1
  • FreightTerminalWorld.ResolveSquadNavigationDestination (cyclomatic 44) csharp/FreightTerminalWorld.Squad.Navigation.cs:183 — FreightTerminalWorld.ResolveSquadNavigationDestination has cyclomatic complexity 44 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateWeaponImpact (cyclomatic 44) · ×1
  • FreightTerminalWorld.ValidateWeaponImpact (cyclomatic 44) csharp/FreightTerminalWorld.WeaponAudioDiagnostics.cs:169 — FreightTerminalWorld.ValidateWeaponImpact has cyclomatic complexity 44 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.RunAiLadderDiagnostics (cyclomatic 43) · ×1
  • FreightTerminalWorld.RunAiLadderDiagnostics (cyclomatic 43) csharp/FreightTerminalWorld.AiLadder.Diagnostics.cs:71 — FreightTerminalWorld.RunAiLadderDiagnostics has cyclomatic complexity 43 (threshold 15). Of this number, 36 points are the body's own statements and 7 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.CaptureFirstPersonWeaponViews (cyclomatic 43) · ×1
  • FreightTerminalWorld.CaptureFirstPersonWeaponViews (cyclomatic 43) csharp/FreightTerminalWorld.CombatModels.cs:519 — FreightTerminalWorld.CaptureFirstPersonWeaponViews has cyclomatic complexity 43 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This is NOT this file's highest cyclomatic complexity: FreightTerminalWorld.ValidateCombatModels (cyclomatic 75) 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 · FreightTerminalWorld.ValidateCorpseLootFlow (cyclomatic 43) · ×1
  • FreightTerminalWorld.ValidateCorpseLootFlow (cyclomatic 43) csharp/FreightTerminalWorld.cs:4437 — FreightTerminalWorld.ValidateCorpseLootFlow has cyclomatic complexity 43 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateSquadDoorRescue (cyclomatic 43) · ×1
  • FreightTerminalWorld.ValidateSquadDoorRescue (cyclomatic 43) csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs:9 — FreightTerminalWorld.ValidateSquadDoorRescue has cyclomatic complexity 43 (threshold 15). Of this number, 40 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · OperatorPresentationDiagnostics._Ready (cyclomatic 43) · ×1
  • OperatorPresentationDiagnostics._Ready (cyclomatic 43) csharp/OperatorPresentationDiagnostics.cs:33 — OperatorPresentationDiagnostics._Ready 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 · TacticalPlayer.RawReloadSupportTargetGlobal (cyclomatic 43) · ×1
  • TacticalPlayer.RawReloadSupportTargetGlobal (cyclomatic 43) csharp/TacticalPlayer.AuthoredVisuals.cs:1195 — TacticalPlayer.RawReloadSupportTargetGlobal has cyclomatic complexity 43 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateIncendiaryAiAvoidance (cyclomatic 42) · ×1
  • FreightTerminalWorld.ValidateIncendiaryAiAvoidance (cyclomatic 42) csharp/FreightTerminalWorld.Incendiary.Diagnostics.cs:8 — FreightTerminalWorld.ValidateIncendiaryAiAvoidance has cyclomatic complexity 42 (threshold 15). Of this number, 37 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateAmmoInventoryFlow (cyclomatic 41) · ×1
  • FreightTerminalWorld.ValidateAmmoInventoryFlow (cyclomatic 41) csharp/FreightTerminalWorld.cs:3606 — FreightTerminalWorld.ValidateAmmoInventoryFlow has cyclomatic complexity 41 (threshold 15). Of this number, 30 points are the body's own statements and 11 belong to 4 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.BazaarPortalGlassReady (cyclomatic 41) · ×1
  • FreightTerminalWorld.BazaarPortalGlassReady (cyclomatic 41) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GlassDiagnostics.cs:22 — FreightTerminalWorld.BazaarPortalGlassReady has cyclomatic complexity 41 (threshold 15). Of this number, 39 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateResidentialStreetArt (cyclomatic 41) · ×1
  • FreightTerminalWorld.ValidateResidentialStreetArt (cyclomatic 41) csharp/FreightTerminalWorld.Residential.StreetArt.Diagnostics.cs:10 — FreightTerminalWorld.ValidateResidentialStreetArt has cyclomatic complexity 41 (threshold 15). Of this number, 34 points are the body's own statements and 7 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateVehicleCombat (cyclomatic 41) · ×1
  • FreightTerminalWorld.ValidateVehicleCombat (cyclomatic 41) csharp/FreightTerminalWorld.VehicleCombat.Diagnostics.cs:8 — FreightTerminalWorld.ValidateVehicleCombat has cyclomatic complexity 41 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.BazaarGuardRailPhysicsReady (cyclomatic 40) · ×1
  • FreightTerminalWorld.BazaarGuardRailPhysicsReady (cyclomatic 40) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GuardRailDiagnostics.cs:31 — FreightTerminalWorld.BazaarGuardRailPhysicsReady has cyclomatic complexity 40 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.TideglassPropCollisionMatchesDefinition (cyclomatic 40) · ×1
  • FreightTerminalWorld.TideglassPropCollisionMatchesDefinition (cyclomatic 40) csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:573 — FreightTerminalWorld.TideglassPropCollisionMatchesDefinition has cyclomatic complexity 40 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateExplosionCover (cyclomatic 40) · ×1
  • FreightTerminalWorld.ValidateExplosionCover (cyclomatic 40) csharp/FreightTerminalWorld.ExplosionOcclusion.Diagnostics.cs:8 — FreightTerminalWorld.ValidateExplosionCover has cyclomatic complexity 40 (threshold 15). Of this number, 37 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · ResidentialRoomLootRules.CreateItem (cyclomatic 40) · ×1
  • ResidentialRoomLootRules.CreateItem (cyclomatic 40) csharp/ResidentialRoomLootRules.cs:131 — ResidentialRoomLootRules.CreateItem has cyclomatic complexity 40 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TacticalPlayer.MovePlayer (cyclomatic 40) · ×1
  • TacticalPlayer.MovePlayer (cyclomatic 40) csharp/TacticalPlayer.cs:1654 — TacticalPlayer.MovePlayer has cyclomatic complexity 40 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.UpdateSquadReviveAi (cyclomatic 39) · ×1
  • FreightTerminalWorld.UpdateSquadReviveAi (cyclomatic 39) csharp/FreightTerminalWorld.Squad.cs:1436 — FreightTerminalWorld.UpdateSquadReviveAi has cyclomatic complexity 39 (threshold 15). Of this number, 38 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: FreightTerminalWorld.ValidateNetworkEndpoint (cyclomatic 64) 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 · AuthoredOperatorAnimator.Update (cyclomatic 38) · ×1
  • AuthoredOperatorAnimator.Update (cyclomatic 38) csharp/AuthoredOperatorAnimator.cs:89 — AuthoredOperatorAnimator.Update has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · DemolitionRetakeDistributionDiagnostics.Run (cyclomatic 38) · ×1
  • DemolitionRetakeDistributionDiagnostics.Run (cyclomatic 38) csharp/DemolitionRetakeDistribution.Diagnostics.cs:44 — DemolitionRetakeDistributionDiagnostics.Run has cyclomatic complexity 38 (threshold 15). Of this number, 36 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.UpdateOrbitalComplexTacticalSignals (cyclomatic 38) · ×1
  • FreightTerminalWorld.UpdateOrbitalComplexTacticalSignals (cyclomatic 38) csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.TacticalSignals.cs:173 — FreightTerminalWorld.UpdateOrbitalComplexTacticalSignals 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 · FreightTerminalWorld.ValidateResidentialDensity (cyclomatic 38) · ×1
  • FreightTerminalWorld.ValidateResidentialDensity (cyclomatic 38) csharp/FreightTerminalWorld.Survival.cs:422 — FreightTerminalWorld.ValidateResidentialDensity has cyclomatic complexity 38 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · SquadMate.UpdateTacticalMovement (cyclomatic 38) · ×1
  • SquadMate.UpdateTacticalMovement (cyclomatic 38) csharp/SquadMate.Combat.cs:397 — SquadMate.UpdateTacticalMovement has cyclomatic complexity 38 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · FreightTerminalWorld.RefreshDemolitionStrategies (cyclomatic 37) · ×1
  • FreightTerminalWorld.RefreshDemolitionStrategies (cyclomatic 37) csharp/FreightTerminalWorld.Demolition.Strategy.cs:12 — FreightTerminalWorld.RefreshDemolitionStrategies has cyclomatic complexity 37 (threshold 15). Of this number, 35 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · JianghaiInteriorShellValidator.Validate (cyclomatic 37) · ×1
  • JianghaiInteriorShellValidator.Validate (cyclomatic 37) csharp/JianghaiInteriorShellValidator.cs:34 — JianghaiInteriorShellValidator.Validate has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateSquadGlassRescue (cyclomatic 36) · ×1
  • FreightTerminalWorld.ValidateSquadGlassRescue (cyclomatic 36) csharp/FreightTerminalWorld.Squad.GlassRescue.Diagnostics.cs:9 — FreightTerminalWorld.ValidateSquadGlassRescue has cyclomatic complexity 36 (threshold 15). Of this number, 33 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateSquadTactics (cyclomatic 36) · ×1
  • FreightTerminalWorld.ValidateSquadTactics (cyclomatic 36) csharp/FreightTerminalWorld.Squad.Tactics.Diagnostics.cs:8 — FreightTerminalWorld.ValidateSquadTactics has cyclomatic complexity 36 (threshold 15). Of this number, 28 points are the body's own statements and 8 belong to 6 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateExtractionSpawns (cyclomatic 35) · ×1
  • FreightTerminalWorld.ValidateExtractionSpawns (cyclomatic 35) csharp/FreightTerminalWorld.cs:5347 — FreightTerminalWorld.ValidateExtractionSpawns has cyclomatic complexity 35 (threshold 15). Of this number, 33 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.TideglassPerimeterGatesReady (cyclomatic 35) · ×1
  • FreightTerminalWorld.TideglassPerimeterGatesReady (cyclomatic 35) csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:1115 — FreightTerminalWorld.TideglassPerimeterGatesReady has cyclomatic complexity 35 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateExtractionNetworkWorld (cyclomatic 35) · ×1
  • FreightTerminalWorld.ValidateExtractionNetworkWorld (cyclomatic 35) csharp/FreightTerminalWorld.Extraction.Network.Diagnostics.cs:120 — FreightTerminalWorld.ValidateExtractionNetworkWorld has cyclomatic complexity 35 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateLootVariety (cyclomatic 35) · ×1
  • FreightTerminalWorld.ValidateLootVariety (cyclomatic 35) csharp/FreightTerminalWorld.Survival.cs:248 — FreightTerminalWorld.ValidateLootVariety 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 · FreightTerminalWorld.ValidateHudPerformance (cyclomatic 34) · ×1
  • FreightTerminalWorld.ValidateHudPerformance (cyclomatic 34) csharp/FreightTerminalWorld.HudPerformance.Diagnostics.cs:13 — FreightTerminalWorld.ValidateHudPerformance has cyclomatic complexity 34 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateFreightTerminalDoors (cyclomatic 34) · ×1
  • FreightTerminalWorld.ValidateFreightTerminalDoors (cyclomatic 34) csharp/FreightTerminalWorld.IndustrialDoors.cs:80 — FreightTerminalWorld.ValidateFreightTerminalDoors has cyclomatic complexity 34 (threshold 15). Of this number, 27 points are the body's own statements and 7 belong to 5 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateSpecialLandmarks (cyclomatic 34) · ×1
  • FreightTerminalWorld.ValidateSpecialLandmarks (cyclomatic 34) csharp/FreightTerminalWorld.SpecialLandmarks.cs:674 — FreightTerminalWorld.ValidateSpecialLandmarks has cyclomatic complexity 34 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · SquadMate.UpdateSustainment (cyclomatic 34) · ×1
  • SquadMate.UpdateSustainment (cyclomatic 34) csharp/SquadMate.Sustainment.cs:126 — SquadMate.UpdateSustainment has cyclomatic complexity 34 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · SquadNavGrid.FindPath (cyclomatic 34) · ×1
  • SquadNavGrid.FindPath (cyclomatic 34) csharp/SquadNavGrid.cs:165 — SquadNavGrid.FindPath has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · WeaponCatalog.Build (cyclomatic 34) · ×1
  • WeaponCatalog.Build (cyclomatic 34) csharp/WeaponSystem.cs:790 — WeaponCatalog.Build has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateExtractionLoadout (cyclomatic 33) · ×1
  • FreightTerminalWorld.ValidateExtractionLoadout (cyclomatic 33) csharp/FreightTerminalWorld.cs:5812 — FreightTerminalWorld.ValidateExtractionLoadout has cyclomatic complexity 33 (threshold 15). Of this number, 29 points are the body's own statements and 4 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · JianghaiClanHallGateContract.TryResolve (cyclomatic 33) · ×1
  • JianghaiClanHallGateContract.TryResolve (cyclomatic 33) csharp/JianghaiClanHallGateContract.cs:47 — JianghaiClanHallGateContract.TryResolve has cyclomatic complexity 33 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateMapDensity (cyclomatic 32) · ×1
  • FreightTerminalWorld.ValidateMapDensity (cyclomatic 32) csharp/FreightTerminalWorld.cs:5264 — FreightTerminalWorld.ValidateMapDensity has cyclomatic complexity 32 (threshold 15). Of this number, 28 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateDemolitionMatchRules (cyclomatic 32) · ×1
  • FreightTerminalWorld.ValidateDemolitionMatchRules (cyclomatic 32) csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:3191 — FreightTerminalWorld.ValidateDemolitionMatchRules has cyclomatic complexity 32 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This is NOT this file's highest cyclomatic complexity: FreightTerminalWorld.ValidateDemolitionBriefing (cyclomatic 112) 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 · FreightTerminalWorld.ValidateLanternCanal (cyclomatic 32) · ×1
  • FreightTerminalWorld.ValidateLanternCanal (cyclomatic 32) csharp/FreightTerminalWorld.LanternCanal.Diagnostics.cs:38 — FreightTerminalWorld.ValidateLanternCanal has cyclomatic complexity 32 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateWeaponAudio (cyclomatic 32) · ×1
  • FreightTerminalWorld.ValidateWeaponAudio (cyclomatic 32) csharp/FreightTerminalWorld.WeaponAudioDiagnostics.cs:8 — FreightTerminalWorld.ValidateWeaponAudio has cyclomatic complexity 32 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · LowPolyBuildingArtValidation.IsRenderable (cyclomatic 32) · ×1
  • LowPolyBuildingArtValidation.IsRenderable (cyclomatic 32) csharp/LowPolyBuildingArtValidation.cs:8 — LowPolyBuildingArtValidation.IsRenderable has cyclomatic complexity 32 (threshold 15). Of this number, 31 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · OperatorPresentationDiagnostics.CheckPistols (cyclomatic 32) · ×1
  • OperatorPresentationDiagnostics.CheckPistols (cyclomatic 32) csharp/OperatorPresentationDiagnostics.cs:214 — OperatorPresentationDiagnostics.CheckPistols 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 · CombatHUD.RefreshDeploymentStore (cyclomatic 31) · ×1
  • CombatHUD.RefreshDeploymentStore (cyclomatic 31) csharp/CombatHUD.Deployment.cs:689 — CombatHUD.RefreshDeploymentStore has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · EnemyOperator.UpdateStance (cyclomatic 31) · ×1
  • EnemyOperator.UpdateStance (cyclomatic 31) csharp/EnemyOperator.cs:1306 — EnemyOperator.UpdateStance has cyclomatic complexity 31 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.BuildResidentialLayoutFurnishings (cyclomatic 31) · ×1
  • FreightTerminalWorld.BuildResidentialLayoutFurnishings (cyclomatic 31) csharp/FreightTerminalWorld.Residential.Diversity.cs:138 — FreightTerminalWorld.BuildResidentialLayoutFurnishings has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.EnsureAiSquadFill (cyclomatic 31) · ×1
  • FreightTerminalWorld.EnsureAiSquadFill (cyclomatic 31) csharp/FreightTerminalWorld.Squad.cs:1025 — FreightTerminalWorld.EnsureAiSquadFill has cyclomatic complexity 31 (threshold 15). Of this number, 30 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: FreightTerminalWorld.ValidateNetworkEndpoint (cyclomatic 64) 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 · JianghaiGameplayCollisionBuilder.BuildInternal (cyclomatic 31) · ×1
  • JianghaiGameplayCollisionBuilder.BuildInternal (cyclomatic 31) csharp/JianghaiGameplayCollisionBuilder.cs:28 — JianghaiGameplayCollisionBuilder.BuildInternal has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SquadSustainmentService.TryTakeLoot (cyclomatic 31) · ×1
  • SquadSustainmentService.TryTakeLoot (cyclomatic 31) csharp/SquadSustainmentService.cs:199 — SquadSustainmentService.TryTakeLoot has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.CreateGradedLootItem (cyclomatic 30) · ×1
  • FreightTerminalWorld.CreateGradedLootItem (cyclomatic 30) csharp/FreightTerminalWorld.cs:1367 — FreightTerminalWorld.CreateGradedLootItem has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateExtractionNetworkLobby (cyclomatic 30) · ×1
  • FreightTerminalWorld.ValidateExtractionNetworkLobby (cyclomatic 30) csharp/FreightTerminalWorld.Extraction.Network.Diagnostics.cs:33 — FreightTerminalWorld.ValidateExtractionNetworkLobby has cyclomatic complexity 30 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateMapPerformance (cyclomatic 30) · ×1
  • FreightTerminalWorld.ValidateMapPerformance (cyclomatic 30) csharp/FreightTerminalWorld.Performance.cs:217 — FreightTerminalWorld.ValidateMapPerformance has cyclomatic complexity 30 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.TryPlanSquadLayeredRoute (cyclomatic 30) · ×1
  • FreightTerminalWorld.TryPlanSquadLayeredRoute (cyclomatic 30) csharp/FreightTerminalWorld.Squad.Traversal.cs:141 — FreightTerminalWorld.TryPlanSquadLayeredRoute has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TacticalPlayer.ApplyProceduralHandPose (cyclomatic 30) · ×1
  • TacticalPlayer.ApplyProceduralHandPose (cyclomatic 30) csharp/TacticalPlayer.AuthoredVisuals.cs:801 — TacticalPlayer.ApplyProceduralHandPose has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This is NOT this file's highest cyclomatic complexity: TacticalPlayer.InspectAuthoredHandPoseForDiagnostics (cyclomatic 31) 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 · DemolitionStrategyPlanner.ChooseAttackerSite (cyclomatic 29) · ×1
  • DemolitionStrategyPlanner.ChooseAttackerSite (cyclomatic 29) csharp/DemolitionStrategyPlanner.cs:193 — DemolitionStrategyPlanner.ChooseAttackerSite has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TacticalPlayer.Fire (cyclomatic 29) · ×1
  • TacticalPlayer.Fire (cyclomatic 29) csharp/TacticalPlayer.cs:1997 — TacticalPlayer.Fire has cyclomatic complexity 29 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · EnemyOperator.PlanCombatPosture (cyclomatic 28) · ×1
  • EnemyOperator.PlanCombatPosture (cyclomatic 28) csharp/EnemyOperator.CombatMovement.cs:92 — EnemyOperator.PlanCombatPosture has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.UpdateSquad (cyclomatic 28) · ×1
  • FreightTerminalWorld.UpdateSquad (cyclomatic 28) csharp/FreightTerminalWorld.Squad.cs:1311 — FreightTerminalWorld.UpdateSquad has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: FreightTerminalWorld.ValidateNetworkEndpoint (cyclomatic 64) 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 · FreightTerminalWorld.UpdateManualRevive (cyclomatic 28) · ×1
  • FreightTerminalWorld.UpdateManualRevive (cyclomatic 28) csharp/FreightTerminalWorld.Squad.cs:1898 — FreightTerminalWorld.UpdateManualRevive has cyclomatic complexity 28 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: FreightTerminalWorld.ValidateNetworkEndpoint (cyclomatic 64) 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 · TacticalPlayer.InspectVisibleMeshScreenProjection (cyclomatic 28) · ×1
  • TacticalPlayer.InspectVisibleMeshScreenProjection (cyclomatic 28) csharp/TacticalPlayer.AuthoredVisuals.cs:278 — TacticalPlayer.InspectVisibleMeshScreenProjection has cyclomatic complexity 28 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This is NOT this file's highest cyclomatic complexity: TacticalPlayer.InspectAuthoredHandPoseForDiagnostics (cyclomatic 31) 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 · TacticalPlayer.EquipFromLoot (cyclomatic 28) · ×1
  • TacticalPlayer.EquipFromLoot (cyclomatic 28) csharp/TacticalPlayer.cs:2563 — TacticalPlayer.EquipFromLoot has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · EnemyOperator.TakeDamage (cyclomatic 27) · ×1
  • EnemyOperator.TakeDamage (cyclomatic 27) csharp/EnemyOperator.cs:2138 — EnemyOperator.TakeDamage 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 · FreightTerminalWorld.UpdateOrbitalComplexBleedValvePresentation (cyclomatic 27) · ×1
  • FreightTerminalWorld.UpdateOrbitalComplexBleedValvePresentation (cyclomatic 27) csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Interactions.cs:194 — FreightTerminalWorld.UpdateOrbitalComplexBleedValvePresentation has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.UpdateOrbitalComplexUndertowPresentation (cyclomatic 27) · ×1
  • FreightTerminalWorld.UpdateOrbitalComplexUndertowPresentation (cyclomatic 27) csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Undertow.cs:270 — FreightTerminalWorld.UpdateOrbitalComplexUndertowPresentation has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.CreateAircraftSupplyDropLoot (cyclomatic 27) · ×1
  • FreightTerminalWorld.CreateAircraftSupplyDropLoot (cyclomatic 27) csharp/FreightTerminalWorld.AircraftDrop.cs:59 — FreightTerminalWorld.CreateAircraftSupplyDropLoot has cyclomatic complexity 27 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · FreightTerminalWorld._Process (cyclomatic 27) · ×1
  • FreightTerminalWorld._Process (cyclomatic 27) csharp/FreightTerminalWorld.cs:305 — FreightTerminalWorld._Process has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.UpdateDemolitionRound (cyclomatic 27) · ×1
  • FreightTerminalWorld.UpdateDemolitionRound (cyclomatic 27) csharp/FreightTerminalWorld.Demolition.cs:819 — FreightTerminalWorld.UpdateDemolitionRound has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · FreightTerminalWorld.UpdateDemolitionSquadObjectiveRelay (cyclomatic 27) · ×1
  • FreightTerminalWorld.UpdateDemolitionSquadObjectiveRelay (cyclomatic 27) csharp/FreightTerminalWorld.Demolition.Strategy.cs:536 — FreightTerminalWorld.UpdateDemolitionSquadObjectiveRelay has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateResidentialCover (cyclomatic 27) · ×1
  • FreightTerminalWorld.ValidateResidentialCover (cyclomatic 27) csharp/FreightTerminalWorld.Residential.cs:2584 — FreightTerminalWorld.ValidateResidentialCover has cyclomatic complexity 27 (threshold 15). Of this number, 26 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.OnRemoteSquadShot (cyclomatic 27) · ×1
  • FreightTerminalWorld.OnRemoteSquadShot (cyclomatic 27) csharp/FreightTerminalWorld.Squad.cs:1246 — FreightTerminalWorld.OnRemoteSquadShot has cyclomatic complexity 27 (threshold 15). Of this number, 24 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: FreightTerminalWorld.ValidateNetworkEndpoint (cyclomatic 64) 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 · FreightTerminalWorld.UpdateDemolitionSquadPosts (cyclomatic 26) · ×1
  • FreightTerminalWorld.UpdateDemolitionSquadPosts (cyclomatic 26) csharp/FreightTerminalWorld.Demolition.Posts.cs:19 — FreightTerminalWorld.UpdateDemolitionSquadPosts has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.TryResolveValidatedDemolitionEscortFallback (cyclomatic 26) · ×1
  • FreightTerminalWorld.TryResolveValidatedDemolitionEscortFallback (cyclomatic 26) csharp/FreightTerminalWorld.Demolition.SquadNavigation.cs:444 — FreightTerminalWorld.TryResolveValidatedDemolitionEscortFallback has cyclomatic complexity 26 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.CaptureRefineryMap (cyclomatic 26) · ×1
  • FreightTerminalWorld.CaptureRefineryMap (cyclomatic 26) csharp/FreightTerminalWorld.Refinery.Capture.cs:8 — FreightTerminalWorld.CaptureRefineryMap has cyclomatic complexity 26 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This is NOT this file's highest cyclomatic complexity: FreightTerminalWorld.CaptureClanHallGate (cyclomatic 28) 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 · CombatHUD.ApplyEquipmentPresentation (cyclomatic 25) · ×1
  • CombatHUD.ApplyEquipmentPresentation (cyclomatic 25) csharp/CombatHUD.Performance.cs:166 — CombatHUD.ApplyEquipmentPresentation has cyclomatic complexity 25 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · EnemyOperator.UpdatePursuitNavigationMovement (cyclomatic 25) · ×1
  • EnemyOperator.UpdatePursuitNavigationMovement (cyclomatic 25) csharp/EnemyOperator.Pursuit.Navigation.cs:56 — EnemyOperator.UpdatePursuitNavigationMovement has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateCrowdPerformance (cyclomatic 25) · ×1
  • FreightTerminalWorld.ValidateCrowdPerformance (cyclomatic 25) csharp/FreightTerminalWorld.CrowdPerformance.Diagnostics.cs:16 — FreightTerminalWorld.ValidateCrowdPerformance has cyclomatic complexity 25 (threshold 15). Of this number, 24 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateReinforcementFlow (cyclomatic 25) · ×1
  • FreightTerminalWorld.ValidateReinforcementFlow (cyclomatic 25) csharp/FreightTerminalWorld.cs:3391 — FreightTerminalWorld.ValidateReinforcementFlow has cyclomatic complexity 25 (threshold 15). Of this number, 23 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.CaptureTideglassReactor (cyclomatic 25) · ×1
  • FreightTerminalWorld.CaptureTideglassReactor (cyclomatic 25) csharp/FreightTerminalWorld.Demolition.TideglassReactor.Capture.cs:9 — FreightTerminalWorld.CaptureTideglassReactor has cyclomatic complexity 25 (threshold 15). Of this number, 24 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ApplyTimeOfDay (cyclomatic 25) · ×1
  • FreightTerminalWorld.ApplyTimeOfDay (cyclomatic 25) csharp/FreightTerminalWorld.Level.cs:194 — FreightTerminalWorld.ApplyTimeOfDay has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ApplyMedicSpray (cyclomatic 25) · ×1
  • FreightTerminalWorld.ApplyMedicSpray (cyclomatic 25) csharp/FreightTerminalWorld.Squad.cs:2546 — FreightTerminalWorld.ApplyMedicSpray has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: FreightTerminalWorld.ValidateNetworkEndpoint (cyclomatic 64) 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 · FreightTerminalWorld.TryResolveSquadGridNavigation (cyclomatic 25) · ×1
  • FreightTerminalWorld.TryResolveSquadGridNavigation (cyclomatic 25) csharp/FreightTerminalWorld.Squad.NavGrid.cs:102 — FreightTerminalWorld.TryResolveSquadGridNavigation has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SquadMate.UpdateCombatTarget (cyclomatic 25) · ×1
  • SquadMate.UpdateCombatTarget (cyclomatic 25) csharp/SquadMate.Combat.cs:139 — SquadMate.UpdateCombatTarget has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AuthoredWeaponVisual.WorldExternalOpticMountMatches (cyclomatic 24) · ×1
  • AuthoredWeaponVisual.WorldExternalOpticMountMatches (cyclomatic 24) csharp/CombatModelLibrary.cs:230 — AuthoredWeaponVisual.WorldExternalOpticMountMatches has cyclomatic complexity 24 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · EnemyOperator.FireAtSquad (cyclomatic 24) · ×1
  • EnemyOperator.FireAtSquad (cyclomatic 24) csharp/EnemyOperator.cs:1963 — EnemyOperator.FireAtSquad has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateDemolitionNetworkRoster (cyclomatic 24) · ×1
  • FreightTerminalWorld.ValidateDemolitionNetworkRoster (cyclomatic 24) csharp/FreightTerminalWorld.Demolition.Network.Roster.Diagnostics.cs:7 — FreightTerminalWorld.ValidateDemolitionNetworkRoster has cyclomatic complexity 24 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.CountRefineryNodes (cyclomatic 24) · ×1
  • FreightTerminalWorld.CountRefineryNodes (cyclomatic 24) csharp/FreightTerminalWorld.Refinery.RuntimeCountValidation.cs:7 — FreightTerminalWorld.CountRefineryNodes has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.TryApplyRemoteSquadState (cyclomatic 24) · ×1
  • FreightTerminalWorld.TryApplyRemoteSquadState (cyclomatic 24) csharp/FreightTerminalWorld.Squad.cs:1141 — FreightTerminalWorld.TryApplyRemoteSquadState has cyclomatic complexity 24 (threshold 15). Of this number, 19 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: FreightTerminalWorld.ValidateNetworkEndpoint (cyclomatic 64) 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 · FreightTerminalWorld.TryPlanSquadGridRoute (cyclomatic 24) · ×1
  • FreightTerminalWorld.TryPlanSquadGridRoute (cyclomatic 24) csharp/FreightTerminalWorld.Squad.NavGrid.cs:250 — FreightTerminalWorld.TryPlanSquadGridRoute has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · OperatorPresentationDiagnostics.ReadSurfaces (cyclomatic 24) · ×1
  • OperatorPresentationDiagnostics.ReadSurfaces (cyclomatic 24) csharp/OperatorPresentationDiagnostics.cs:298 — OperatorPresentationDiagnostics.ReadSurfaces has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SquadMate.TryFire (cyclomatic 24) · ×1
  • SquadMate.TryFire (cyclomatic 24) csharp/SquadMate.cs:757 — SquadMate.TryFire has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · TacticalPlayer.TraceMeleeBladeSegment (cyclomatic 24) · ×1
  • TacticalPlayer.TraceMeleeBladeSegment (cyclomatic 24) csharp/TacticalPlayer.Melee.Combat.cs:249 — TacticalPlayer.TraceMeleeBladeSegment has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · CombatHUD.RefreshLootOverlay (cyclomatic 23) · ×1
  • CombatHUD.RefreshLootOverlay (cyclomatic 23) csharp/CombatHUD.cs:1033 — CombatHUD.RefreshLootOverlay has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · EnemyOperator.AcquireCombatTarget (cyclomatic 23) · ×1
  • EnemyOperator.AcquireCombatTarget (cyclomatic 23) csharp/EnemyOperator.cs:983 — EnemyOperator.AcquireCombatTarget has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateEquipmentFlow (cyclomatic 23) · ×1
  • FreightTerminalWorld.ValidateEquipmentFlow (cyclomatic 23) csharp/FreightTerminalWorld.cs:3487 — FreightTerminalWorld.ValidateEquipmentFlow has cyclomatic complexity 23 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateGoalPack (cyclomatic 23) · ×1
  • FreightTerminalWorld.ValidateGoalPack (cyclomatic 23) csharp/FreightTerminalWorld.cs:6810 — FreightTerminalWorld.ValidateGoalPack has cyclomatic complexity 23 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ResolveAndApplyDemolitionObjectiveChannels (cyclomatic 23) · ×1
  • FreightTerminalWorld.ResolveAndApplyDemolitionObjectiveChannels (cyclomatic 23) csharp/FreightTerminalWorld.Demolition.Strategy.cs:318 — FreightTerminalWorld.ResolveAndApplyDemolitionObjectiveChannels has cyclomatic complexity 23 (threshold 15). Of this number, 21 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateExtractionAiDeployment (cyclomatic 23) · ×1
  • FreightTerminalWorld.ValidateExtractionAiDeployment (cyclomatic 23) csharp/FreightTerminalWorld.ExtractionAi.Diagnostics.cs:9 — FreightTerminalWorld.ValidateExtractionAiDeployment has cyclomatic complexity 23 (threshold 15). Of this number, 19 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ApplyIncendiaryDamageTick (cyclomatic 23) · ×1
  • FreightTerminalWorld.ApplyIncendiaryDamageTick (cyclomatic 23) csharp/FreightTerminalWorld.Incendiary.cs:216 — FreightTerminalWorld.ApplyIncendiaryDamageTick has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.CountMapRuntimeNodes (cyclomatic 23) · ×1
  • FreightTerminalWorld.CountMapRuntimeNodes (cyclomatic 23) csharp/FreightTerminalWorld.Performance.cs:127 — FreightTerminalWorld.CountMapRuntimeNodes has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: FreightTerminalWorld.IsDistanceCulledBox (cyclomatic 26) 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 · FreightTerminalWorld.BuildResidentialFacadePattern (cyclomatic 23) · ×1
  • FreightTerminalWorld.BuildResidentialFacadePattern (cyclomatic 23) csharp/FreightTerminalWorld.Residential.Diversity.cs:294 — FreightTerminalWorld.BuildResidentialFacadePattern has cyclomatic complexity 23 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · FreightTerminalWorld.DeploySquad (cyclomatic 23) · ×1
  • FreightTerminalWorld.DeploySquad (cyclomatic 23) csharp/FreightTerminalWorld.Squad.cs:401 — FreightTerminalWorld.DeploySquad has cyclomatic complexity 23 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This is NOT this file's highest cyclomatic complexity: FreightTerminalWorld.ValidateNetworkEndpoint (cyclomatic 64) 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 · FreightTerminalWorld.AddSquadPortalConnectors (cyclomatic 23) · ×1
  • FreightTerminalWorld.AddSquadPortalConnectors (cyclomatic 23) csharp/FreightTerminalWorld.Squad.Traversal.cs:438 — FreightTerminalWorld.AddSquadPortalConnectors has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SquadNavigationGraph.FindShortestPath (cyclomatic 23) · ×1
  • SquadNavigationGraph.FindShortestPath (cyclomatic 23) csharp/SquadNavigationGraph.cs:16 — SquadNavigationGraph.FindShortestPath has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SquadSustainmentService.TryReserveBestSource (cyclomatic 23) · ×1
  • SquadSustainmentService.TryReserveBestSource (cyclomatic 23) csharp/SquadSustainmentService.cs:81 — SquadSustainmentService.TryReserveBestSource 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 · TacticalPlayer.UpdateProfiledReloadAnimation (cyclomatic 23) · ×1
  • TacticalPlayer.UpdateProfiledReloadAnimation (cyclomatic 23) csharp/TacticalPlayer.ReloadPresentation.cs:27 — TacticalPlayer.UpdateProfiledReloadAnimation has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · CombatModelLibrary.InstantiateAdaptedWeapon (cyclomatic 22) · ×1
  • CombatModelLibrary.InstantiateAdaptedWeapon (cyclomatic 22) csharp/CombatModelLibrary.cs:1440 — CombatModelLibrary.InstantiateAdaptedWeapon has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · FreightTerminalWorld.TryHandleDemolitionDefenderMovement (cyclomatic 22) · ×1
  • FreightTerminalWorld.TryHandleDemolitionDefenderMovement (cyclomatic 22) csharp/FreightTerminalWorld.Demolition.Strategy.cs:715 — FreightTerminalWorld.TryHandleDemolitionDefenderMovement has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · FreightTerminalWorld.TideglassAuthoredMeshCollisionReady (cyclomatic 22) · ×1
  • FreightTerminalWorld.TideglassAuthoredMeshCollisionReady (cyclomatic 22) csharp/FreightTerminalWorld.Demolition.TideglassReactor.AssetDiagnostics.cs:80 — FreightTerminalWorld.TideglassAuthoredMeshCollisionReady has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 90, 110). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · FreightTerminalWorld.InspectMeleeRuntime (cyclomatic 22) · ×1
  • FreightTerminalWorld.InspectMeleeRuntime (cyclomatic 22) csharp/FreightTerminalWorld.Melee.Diagnostics.cs:133 — FreightTerminalWorld.InspectMeleeRuntime has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateAuthoredCollisionSources (cyclomatic 22) · ×1
  • FreightTerminalWorld.ValidateAuthoredCollisionSources (cyclomatic 22) csharp/FreightTerminalWorld.Refinery.CollisionDiagnostics.cs:136 — FreightTerminalWorld.ValidateAuthoredCollisionSources has cyclomatic complexity 22 (threshold 15). Of this number, 17 points are the body's own statements and 5 belong to 4 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This is NOT this file's highest cyclomatic complexity: FreightTerminalWorld.ValidateRefineryCollision (cyclomatic 33) 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 · TacticalPlayer.UpdateCameraAndWeapon (cyclomatic 22) · ×1
  • TacticalPlayer.UpdateCameraAndWeapon (cyclomatic 22) csharp/TacticalPlayer.cs:1892 — TacticalPlayer.UpdateCameraAndWeapon has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · TacticalPlayer.TakeDamage (cyclomatic 22) · ×1
  • TacticalPlayer.TakeDamage (cyclomatic 22) csharp/TacticalPlayer.cs:2932 — TacticalPlayer.TakeDamage has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · TacticalPlayer.InspectOpticAxisProjectionForDiagnostics (cyclomatic 22) · ×1
  • TacticalPlayer.InspectOpticAxisProjectionForDiagnostics (cyclomatic 22) csharp/TacticalPlayer.WeaponPose.cs:543 — TacticalPlayer.InspectOpticAxisProjectionForDiagnostics has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · CombatModelLibrary.InspectPreviewOperatorOwnershipForDiagnostics (cyclomatic 21) · ×1
  • CombatModelLibrary.InspectPreviewOperatorOwnershipForDiagnostics (cyclomatic 21) csharp/CombatModelLibrary.PreviewDiagnostics.cs:16 — CombatModelLibrary.InspectPreviewOperatorOwnershipForDiagnostics has cyclomatic complexity 21 (threshold 15). Of this number, 18 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.OnDemolitionDeploymentRequested (cyclomatic 21) · ×1
  • FreightTerminalWorld.OnDemolitionDeploymentRequested (cyclomatic 21) csharp/FreightTerminalWorld.Demolition.cs:116 — FreightTerminalWorld.OnDemolitionDeploymentRequested has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · FreightTerminalWorld.OnDemolitionNetworkAction (cyclomatic 21) · ×1
  • FreightTerminalWorld.OnDemolitionNetworkAction (cyclomatic 21) csharp/FreightTerminalWorld.Demolition.Network.cs:676 — FreightTerminalWorld.OnDemolitionNetworkAction has cyclomatic complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.UpdateExtractionSequence (cyclomatic 21) · ×1
  • FreightTerminalWorld.UpdateExtractionSequence (cyclomatic 21) csharp/FreightTerminalWorld.Extraction.cs:88 — FreightTerminalWorld.UpdateExtractionSequence has cyclomatic complexity 21 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.BuildResidentialSkyLinks (cyclomatic 21) · ×1
  • FreightTerminalWorld.BuildResidentialSkyLinks (cyclomatic 21) csharp/FreightTerminalWorld.Residential.cs:2977 — FreightTerminalWorld.BuildResidentialSkyLinks has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateResidentialSquadStairs (cyclomatic 21) · ×1
  • FreightTerminalWorld.ValidateResidentialSquadStairs (cyclomatic 21) csharp/FreightTerminalWorld.ResidentialStairs.Diagnostics.cs:10 — FreightTerminalWorld.ValidateResidentialSquadStairs has cyclomatic complexity 21 (threshold 15). Of this number, 18 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · LowPolyBuildingArtBuilder.BuildResidentialMassing (cyclomatic 21) · ×1
  • LowPolyBuildingArtBuilder.BuildResidentialMassing (cyclomatic 21) csharp/LowPolyBuildingArtBuilder.Architecture.cs:257 — LowPolyBuildingArtBuilder.BuildResidentialMassing has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ResidentialAuthoredPropLibrary.PathForRoomProp (cyclomatic 21) · ×1
  • ResidentialAuthoredPropLibrary.PathForRoomProp (cyclomatic 21) csharp/ResidentialAuthoredPropLibrary.cs:26 — ResidentialAuthoredPropLibrary.PathForRoomProp has cyclomatic complexity 21 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · TacticalPlayer.RefreshAuthoredPrimaryWeapon (cyclomatic 21) · ×1
  • TacticalPlayer.RefreshAuthoredPrimaryWeapon (cyclomatic 21) csharp/TacticalPlayer.AuthoredVisuals.cs:704 — TacticalPlayer.RefreshAuthoredPrimaryWeapon has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: TacticalPlayer.InspectAuthoredHandPoseForDiagnostics (cyclomatic 31) 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 · TacticalPlayer.UpdateVehiclePassenger (cyclomatic 21) · ×1
  • TacticalPlayer.UpdateVehiclePassenger (cyclomatic 21) csharp/TacticalPlayer.cs:1470 — TacticalPlayer.UpdateVehiclePassenger has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TacticalPlayer.StartPlate (cyclomatic 21) · ×1
  • TacticalPlayer.StartPlate (cyclomatic 21) csharp/TacticalPlayer.cs:2356 — TacticalPlayer.StartPlate has cyclomatic complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · CombatHUD.SetInteraction (cyclomatic 20) · ×1
  • CombatHUD.SetInteraction (cyclomatic 20) csharp/CombatHUD.cs:1485 — CombatHUD.SetInteraction has cyclomatic complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · CombatHUD.RefreshDeploymentPreview (cyclomatic 20) · ×1
  • CombatHUD.RefreshDeploymentPreview (cyclomatic 20) csharp/CombatHUD.Deployment.cs:825 — CombatHUD.RefreshDeploymentPreview has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · DemolitionStrategyPlanner.DefenderOpeningPost (cyclomatic 20) · ×1
  • DemolitionStrategyPlanner.DefenderOpeningPost (cyclomatic 20) csharp/DemolitionStrategyPlanner.cs:547 — DemolitionStrategyPlanner.DefenderOpeningPost has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateCanalAccess (cyclomatic 20) · ×1
  • FreightTerminalWorld.ValidateCanalAccess (cyclomatic 20) csharp/FreightTerminalWorld.CanalAccess.Diagnostics.cs:9 — FreightTerminalWorld.ValidateCanalAccess has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.FindNearestWeaponLootSource (cyclomatic 20) · ×1
  • FreightTerminalWorld.FindNearestWeaponLootSource (cyclomatic 20) csharp/FreightTerminalWorld.cs:1825 — FreightTerminalWorld.FindNearestWeaponLootSource has cyclomatic complexity 20 (threshold 15). Of this number, 18 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateLargeMapFlow (cyclomatic 20) · ×1
  • FreightTerminalWorld.ValidateLargeMapFlow (cyclomatic 20) csharp/FreightTerminalWorld.cs:6909 — FreightTerminalWorld.ValidateLargeMapFlow 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 · FreightTerminalWorld.BazaarOpenApproachStairEntriesReady (cyclomatic 20) · ×1
  • FreightTerminalWorld.BazaarOpenApproachStairEntriesReady (cyclomatic 20) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs:105 — FreightTerminalWorld.BazaarOpenApproachStairEntriesReady has cyclomatic complexity 20 (threshold 15). Of this number, 13 points are the body's own statements and 7 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.TryResolveDemolitionEscortDestination (cyclomatic 20) · ×1
  • FreightTerminalWorld.TryResolveDemolitionEscortDestination (cyclomatic 20) csharp/FreightTerminalWorld.Demolition.SquadNavigation.cs:90 — FreightTerminalWorld.TryResolveDemolitionEscortDestination has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.TideglassGatewayCollisionReady (cyclomatic 20) · ×1
  • FreightTerminalWorld.TideglassGatewayCollisionReady (cyclomatic 20) csharp/FreightTerminalWorld.Demolition.TideglassReactor.StructureDiagnostics.cs:233 — FreightTerminalWorld.TideglassGatewayCollisionReady has cyclomatic complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.RecordRemoteMeleeSwingStart (cyclomatic 20) · ×1
  • FreightTerminalWorld.RecordRemoteMeleeSwingStart (cyclomatic 20) csharp/FreightTerminalWorld.Melee.Authority.cs:101 — FreightTerminalWorld.RecordRemoteMeleeSwingStart has cyclomatic complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.OnRemoteMeleeHitConfirmed (cyclomatic 20) · ×1
  • FreightTerminalWorld.OnRemoteMeleeHitConfirmed (cyclomatic 20) csharp/FreightTerminalWorld.Melee.Network.cs:241 — FreightTerminalWorld.OnRemoteMeleeHitConfirmed has cyclomatic complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.OnSquadDeploymentRequested (cyclomatic 20) · ×1
  • FreightTerminalWorld.OnSquadDeploymentRequested (cyclomatic 20) csharp/FreightTerminalWorld.Squad.cs:299 — FreightTerminalWorld.OnSquadDeploymentRequested has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: FreightTerminalWorld.ValidateNetworkEndpoint (cyclomatic 64) 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 · FreightTerminalWorld.TryValidateSquadSteppedDirectRoute (cyclomatic 20) · ×1
  • FreightTerminalWorld.TryValidateSquadSteppedDirectRoute (cyclomatic 20) csharp/FreightTerminalWorld.Squad.Navigation.cs:545 — FreightTerminalWorld.TryValidateSquadSteppedDirectRoute has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · LanternCanalLighting.Apply (cyclomatic 20) · ×1
  • LanternCanalLighting.Apply (cyclomatic 20) csharp/LanternCanalLighting.cs:55 — LanternCanalLighting.Apply has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · SoundLab.LoadRecordedPcmWav (cyclomatic 20) · ×1
  • SoundLab.LoadRecordedPcmWav (cyclomatic 20) csharp/SoundLab.Recordings.cs:123 — SoundLab.LoadRecordedPcmWav has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SquadMate.TryUpdateIncendiaryAvoidance (cyclomatic 20) · ×1
  • SquadMate.TryUpdateIncendiaryAvoidance (cyclomatic 20) csharp/SquadMate.IncendiaryAvoidance.cs:22 — SquadMate.TryUpdateIncendiaryAvoidance has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · SquadNetwork.AcceptExtractionWorldStateChunk (cyclomatic 20) · ×1
  • SquadNetwork.AcceptExtractionWorldStateChunk (cyclomatic 20) csharp/SquadNetwork.Extraction.World.cs:238 — SquadNetwork.AcceptExtractionWorldStateChunk has cyclomatic complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · TacticalPlayer.ClosestPointOnTriangle (cyclomatic 20) · ×1
  • TacticalPlayer.ClosestPointOnTriangle (cyclomatic 20) csharp/TacticalPlayer.AuthoredVisuals.cs:591 — TacticalPlayer.ClosestPointOnTriangle has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: TacticalPlayer.InspectAuthoredHandPoseForDiagnostics (cyclomatic 31) 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 · TacticalPlayer.TryUpdateOrbitalComplexSwimming (cyclomatic 20) · ×1
  • TacticalPlayer.TryUpdateOrbitalComplexSwimming (cyclomatic 20) csharp/TacticalPlayer.OrbitalComplexSwimming.cs:29 — TacticalPlayer.TryUpdateOrbitalComplexSwimming has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · TacticalPlayer.InspectReloadScreenContact (cyclomatic 20) · ×1
  • TacticalPlayer.InspectReloadScreenContact (cyclomatic 20) csharp/TacticalPlayer.ReloadDiagnostics.cs:303 — TacticalPlayer.InspectReloadScreenContact has cyclomatic complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · CombatHUD.ApplyMedicalPresentation (cyclomatic 19) · ×1
  • CombatHUD.ApplyMedicalPresentation (cyclomatic 19) csharp/CombatHUD.Performance.cs:256 — CombatHUD.ApplyMedicalPresentation has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateVehicleDrive (cyclomatic 19) · ×1
  • FreightTerminalWorld.ValidateVehicleDrive (cyclomatic 19) csharp/FreightTerminalWorld.cs:6664 — FreightTerminalWorld.ValidateVehicleDrive 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 · FreightTerminalWorld.BazaarAiRouteDirectivesReady (cyclomatic 19) · ×1
  • FreightTerminalWorld.BazaarAiRouteDirectivesReady (cyclomatic 19) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.RouteDiagnostics.cs:235 — FreightTerminalWorld.BazaarAiRouteDirectivesReady has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateDemolitionNetworkJoinRejection (cyclomatic 19) · ×1
  • FreightTerminalWorld.ValidateDemolitionNetworkJoinRejection (cyclomatic 19) csharp/FreightTerminalWorld.Demolition.Network.Diagnostics.cs:41 — FreightTerminalWorld.ValidateDemolitionNetworkJoinRejection has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.UpdateDemolitionCombatArbitration (cyclomatic 19) · ×1
  • FreightTerminalWorld.UpdateDemolitionCombatArbitration (cyclomatic 19) csharp/FreightTerminalWorld.Demolition.Strategy.cs:921 — FreightTerminalWorld.UpdateDemolitionCombatArbitration has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · FreightTerminalWorld.UpdateOrbitalComplexRuntimePresentationFX (cyclomatic 19) · ×1
  • FreightTerminalWorld.UpdateOrbitalComplexRuntimePresentationFX (cyclomatic 19) csharp/FreightTerminalWorld.OrbitalComplex.Presentation.cs:323 — FreightTerminalWorld.UpdateOrbitalComplexRuntimePresentationFX has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateClanHallCollision (cyclomatic 19) · ×1
  • FreightTerminalWorld.ValidateClanHallCollision (cyclomatic 19) csharp/FreightTerminalWorld.Refinery.ClanHallValidation.cs:10 — FreightTerminalWorld.ValidateClanHallCollision has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · JianghaiAuthoredRenderBatcher.ValidateBatches (cyclomatic 19) · ×1
  • JianghaiAuthoredRenderBatcher.ValidateBatches (cyclomatic 19) csharp/JianghaiAuthoredRenderBatcher.cs:135 — JianghaiAuthoredRenderBatcher.ValidateBatches has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · TacticalPlayer.InspectAuthoredM4ReloadArmForDiagnostics (cyclomatic 19) · ×1
  • TacticalPlayer.InspectAuthoredM4ReloadArmForDiagnostics (cyclomatic 19) csharp/TacticalPlayer.AuthoredVisuals.cs:486 — TacticalPlayer.InspectAuthoredM4ReloadArmForDiagnostics has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: TacticalPlayer.InspectAuthoredHandPoseForDiagnostics (cyclomatic 31) 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 · TacticalPlayer.TryVaultLowObstacle (cyclomatic 19) · ×1
  • TacticalPlayer.TryVaultLowObstacle (cyclomatic 19) csharp/TacticalPlayer.MovementInput.cs:97 — TacticalPlayer.TryVaultLowObstacle has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TacticalPlayer.ReloadMeshUsesSkeleton (cyclomatic 19) · ×1
  • TacticalPlayer.ReloadMeshUsesSkeleton (cyclomatic 19) csharp/TacticalPlayer.ReloadBodyDiagnostics.cs:466 — TacticalPlayer.ReloadMeshUsesSkeleton has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TacticalPlayer.InspectAuthoredPlatformReloadForDiagnostics (cyclomatic 19) · ×1
  • TacticalPlayer.InspectAuthoredPlatformReloadForDiagnostics (cyclomatic 19) csharp/TacticalPlayer.ReloadPresentation.ViewDiagnostics.cs:70 — TacticalPlayer.InspectAuthoredPlatformReloadForDiagnostics has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · TacticalPlayer.ActivateWeaponSlot (cyclomatic 19) · ×1
  • TacticalPlayer.ActivateWeaponSlot (cyclomatic 19) csharp/TacticalPlayer.WeaponSlots.cs:341 — TacticalPlayer.ActivateWeaponSlot 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 · DemolitionRoutePlanner.TacticalSegmentPenalty (cyclomatic 18) · ×1
  • DemolitionRoutePlanner.TacticalSegmentPenalty (cyclomatic 18) csharp/DemolitionRoutePlanner.cs:435 — DemolitionRoutePlanner.TacticalSegmentPenalty has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · DemolitionStrategyPlanner.PlanDefenderRetake (cyclomatic 18) · ×1
  • DemolitionStrategyPlanner.PlanDefenderRetake (cyclomatic 18) csharp/DemolitionStrategyPlanner.cs:584 — DemolitionStrategyPlanner.PlanDefenderRetake has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · OrbitalComplexLayoutValidator.GameplayPositions (cyclomatic 18) · ×1
  • OrbitalComplexLayoutValidator.GameplayPositions (cyclomatic 18) csharp/ExtractionMaps/OrbitalComplex/OrbitalComplexLayoutValidator.cs:172 — OrbitalComplexLayoutValidator.GameplayPositions has cyclomatic complexity 18 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This is NOT this file's highest cyclomatic complexity: OrbitalComplexLayoutValidator.ValidateCollision (cyclomatic 26) 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 · FreightTerminalWorld.Explode (cyclomatic 18) · ×1
  • FreightTerminalWorld.Explode (cyclomatic 18) csharp/FreightTerminalWorld.cs:812 — FreightTerminalWorld.Explode has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.BuildExtractionLootRanking (cyclomatic 18) · ×1
  • FreightTerminalWorld.BuildExtractionLootRanking (cyclomatic 18) csharp/FreightTerminalWorld.cs:2200 — FreightTerminalWorld.BuildExtractionLootRanking has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.BazaarTraversalGeometryReady (cyclomatic 18) · ×1
  • FreightTerminalWorld.BazaarTraversalGeometryReady (cyclomatic 18) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs:369 — FreightTerminalWorld.BazaarTraversalGeometryReady has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · FreightTerminalWorld.TryResolveDemolitionSquadNavigation (cyclomatic 18) · ×1
  • FreightTerminalWorld.TryResolveDemolitionSquadNavigation (cyclomatic 18) csharp/FreightTerminalWorld.Demolition.SquadNavigation.cs:587 — FreightTerminalWorld.TryResolveDemolitionSquadNavigation has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.IsFlashbangFriendlySafe (cyclomatic 18) · ×1
  • FreightTerminalWorld.IsFlashbangFriendlySafe (cyclomatic 18) csharp/FreightTerminalWorld.Demolition.Utility.cs:331 — FreightTerminalWorld.IsFlashbangFriendlySafe has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.BuildEnterableComplex (cyclomatic 18) · ×1
  • FreightTerminalWorld.BuildEnterableComplex (cyclomatic 18) csharp/FreightTerminalWorld.Expansion.cs:163 — FreightTerminalWorld.BuildEnterableComplex has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateLanternCanalPerformance (cyclomatic 18) · ×1
  • FreightTerminalWorld.ValidateLanternCanalPerformance (cyclomatic 18) csharp/FreightTerminalWorld.LanternCanal.PerformanceDiagnostics.cs:9 — FreightTerminalWorld.ValidateLanternCanalPerformance has cyclomatic complexity 18 (threshold 15). Of this number, 13 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.RunMeleeDiagnostic (cyclomatic 18) · ×1
  • FreightTerminalWorld.RunMeleeDiagnostic (cyclomatic 18) csharp/FreightTerminalWorld.Melee.Diagnostics.cs:27 — FreightTerminalWorld.RunMeleeDiagnostic has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This is NOT this file's highest cyclomatic complexity: FreightTerminalWorld.ValidateMeleeDefinitions (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 · FreightTerminalWorld.UpdateOrbitalComplexTelemetryInteraction (cyclomatic 18) · ×1
  • FreightTerminalWorld.UpdateOrbitalComplexTelemetryInteraction (cyclomatic 18) csharp/FreightTerminalWorld.OrbitalComplex.Presentation.cs:376 — FreightTerminalWorld.UpdateOrbitalComplexTelemetryInteraction has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · FreightTerminalWorld.TryHandleRoofAccessInteraction (cyclomatic 18) · ×1
  • FreightTerminalWorld.TryHandleRoofAccessInteraction (cyclomatic 18) csharp/FreightTerminalWorld.RoofAccess.cs:270 — FreightTerminalWorld.TryHandleRoofAccessInteraction has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.FindAiReviveTarget (cyclomatic 18) · ×1
  • FreightTerminalWorld.FindAiReviveTarget (cyclomatic 18) csharp/FreightTerminalWorld.Squad.cs:1610 — FreightTerminalWorld.FindAiReviveTarget has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This is NOT this file's highest cyclomatic complexity: FreightTerminalWorld.ValidateNetworkEndpoint (cyclomatic 64) 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 · FreightTerminalWorld.SquadNavigationDirectiveReached (cyclomatic 18) · ×1
  • FreightTerminalWorld.SquadNavigationDirectiveReached (cyclomatic 18) csharp/FreightTerminalWorld.Squad.NavGrid.cs:668 — FreightTerminalWorld.SquadNavigationDirectiveReached has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · FreightTerminalWorld.BuildSquadPortalComponentReachability (cyclomatic 18) · ×1
  • FreightTerminalWorld.BuildSquadPortalComponentReachability (cyclomatic 18) csharp/FreightTerminalWorld.Squad.Traversal.cs:570 — FreightTerminalWorld.BuildSquadPortalComponentReachability has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · JianghaiOldCityValleyInspector.InspectNode (cyclomatic 18) · ×1
  • JianghaiOldCityValleyInspector.InspectNode (cyclomatic 18) csharp/JianghaiOldCityValleyInspector.cs:114 — JianghaiOldCityValleyInspector.InspectNode has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: JianghaiOldCityValleyInspector.Inspect (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 · LowPolyBuildingArtBuilder.BuildResidentialRoofProfile (cyclomatic 18) · ×1
  • LowPolyBuildingArtBuilder.BuildResidentialRoofProfile (cyclomatic 18) csharp/LowPolyBuildingArtBuilder.Profiles.cs:129 — LowPolyBuildingArtBuilder.BuildResidentialRoofProfile has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SquadMate.UpdateSkillAction (cyclomatic 18) · ×1
  • SquadMate.UpdateSkillAction (cyclomatic 18) csharp/SquadMate.cs:1040 — SquadMate.UpdateSkillAction has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SquadNetwork.SubmitClientAbility (cyclomatic 18) · ×1
  • SquadNetwork.SubmitClientAbility (cyclomatic 18) csharp/SquadNetwork.cs:380 — SquadNetwork.SubmitClientAbility has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · CombatHUD.ApplyStatsPresentation (cyclomatic 17) · ×1
  • CombatHUD.ApplyStatsPresentation (cyclomatic 17) csharp/CombatHUD.Performance.cs:83 — CombatHUD.ApplyStatsPresentation has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · CombatHUD.RefreshSquadDeployAction (cyclomatic 17) · ×1
  • CombatHUD.RefreshSquadDeployAction (cyclomatic 17) csharp/CombatHUD.Squad.cs:558 — CombatHUD.RefreshSquadDeployAction has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AuthoredOpticsVisual.Configure (cyclomatic 17) · ×1
  • AuthoredOpticsVisual.Configure (cyclomatic 17) csharp/CombatModelLibrary.Optics.cs:81 — AuthoredOpticsVisual.Configure has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: AuthoredOpticsVisual.PresentationMatches (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 · DriveableVehicle.Drive (cyclomatic 17) · ×1
  • DriveableVehicle.Drive (cyclomatic 17) csharp/DriveableVehicle.cs:197 — DriveableVehicle.Drive has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · EnemyOperator.PrepareCombatMovementBeforeMove (cyclomatic 17) · ×1
  • EnemyOperator.PrepareCombatMovementBeforeMove (cyclomatic 17) csharp/EnemyOperator.AirborneCombat.cs:45 — EnemyOperator.PrepareCombatMovementBeforeMove has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.UpdateOrbitalComplexRuntimePresentation (cyclomatic 17) · ×1
  • FreightTerminalWorld.UpdateOrbitalComplexRuntimePresentation (cyclomatic 17) csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Runtime.cs:723 — FreightTerminalWorld.UpdateOrbitalComplexRuntimePresentation has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.BazaarV2DensityReady (cyclomatic 17) · ×1
  • FreightTerminalWorld.BazaarV2DensityReady (cyclomatic 17) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.DensityDiagnostics.cs:29 — FreightTerminalWorld.BazaarV2DensityReady has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: FreightTerminalWorld.BazaarInteriorContractReady (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 · FreightTerminalWorld.FinishDemolitionRound (cyclomatic 17) · ×1
  • FreightTerminalWorld.FinishDemolitionRound (cyclomatic 17) csharp/FreightTerminalWorld.Demolition.cs:986 — FreightTerminalWorld.FinishDemolitionRound has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · FreightTerminalWorld.HarborPropCollisionCoversModel (cyclomatic 17) · ×1
  • FreightTerminalWorld.HarborPropCollisionCoversModel (cyclomatic 17) csharp/FreightTerminalWorld.Demolition.HarborLocks.Diagnostics.cs:229 — FreightTerminalWorld.HarborPropCollisionCoversModel 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: FreightTerminalWorld.ValidateHarborLocks (cyclomatic 61) 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 · FreightTerminalWorld.OnDemolitionWeaponPickupRequested (cyclomatic 17) · ×1
  • FreightTerminalWorld.OnDemolitionWeaponPickupRequested (cyclomatic 17) csharp/FreightTerminalWorld.Demolition.WeaponDrops.Network.cs:215 — FreightTerminalWorld.OnDemolitionWeaponPickupRequested has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.TryAcceptRemoteMeleeTarget (cyclomatic 17) · ×1
  • FreightTerminalWorld.TryAcceptRemoteMeleeTarget (cyclomatic 17) csharp/FreightTerminalWorld.Melee.Authority.cs:16 — FreightTerminalWorld.TryAcceptRemoteMeleeTarget has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.BuildTowerStairDetails (cyclomatic 17) · ×1
  • FreightTerminalWorld.BuildTowerStairDetails (cyclomatic 17) csharp/FreightTerminalWorld.Residential.Density.cs:163 — FreightTerminalWorld.BuildTowerStairDetails has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.WarmSquadPortalWalkConnectorCache (cyclomatic 17) · ×1
  • FreightTerminalWorld.WarmSquadPortalWalkConnectorCache (cyclomatic 17) csharp/FreightTerminalWorld.Squad.Traversal.Connectors.cs:83 — FreightTerminalWorld.WarmSquadPortalWalkConnectorCache has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · JianghaiGameplayCollisionGeometry.ResolveEnterableRoom (cyclomatic 17) · ×1
  • JianghaiGameplayCollisionGeometry.ResolveEnterableRoom (cyclomatic 17) csharp/JianghaiGameplayCollisionGeometry.cs:42 — JianghaiGameplayCollisionGeometry.ResolveEnterableRoom has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · LowPolyBuildingArtBuilder.BuildResidentialFacadeProfile (cyclomatic 17) · ×1
  • LowPolyBuildingArtBuilder.BuildResidentialFacadeProfile (cyclomatic 17) csharp/LowPolyBuildingArtBuilder.Profiles.cs:63 — LowPolyBuildingArtBuilder.BuildResidentialFacadeProfile has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SquadMate.ConsiderRoleAbility (cyclomatic 17) · ×1
  • SquadMate.ConsiderRoleAbility (cyclomatic 17) csharp/SquadMate.cs:921 — SquadMate.ConsiderRoleAbility has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SquadMate.TakeCombatDamageInternal (cyclomatic 17) · ×1
  • SquadMate.TakeCombatDamageInternal (cyclomatic 17) csharp/SquadMate.cs:1146 — SquadMate.TakeCombatDamageInternal has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SquadNetwork.TryParseEndpoint (cyclomatic 17) · ×1
  • SquadNetwork.TryParseEndpoint (cyclomatic 17) csharp/SquadNetwork.cs:119 — SquadNetwork.TryParseEndpoint has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TacticalPlayer.SyncAuthoredPlatformWeapon (cyclomatic 17) · ×1
  • TacticalPlayer.SyncAuthoredPlatformWeapon (cyclomatic 17) csharp/TacticalPlayer.AuthoredVisuals.cs:1398 — TacticalPlayer.SyncAuthoredPlatformWeapon has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: TacticalPlayer.InspectAuthoredHandPoseForDiagnostics (cyclomatic 31) 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 · TacticalPlayer.ReloadSegmentTouchesBodyEdge (cyclomatic 17) · ×1
  • TacticalPlayer.ReloadSegmentTouchesBodyEdge (cyclomatic 17) csharp/TacticalPlayer.ReloadBodyDiagnostics.cs:319 — TacticalPlayer.ReloadSegmentTouchesBodyEdge has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · TrainingRangeArmoryView.Candidates (cyclomatic 17) · ×1
  • TrainingRangeArmoryView.Candidates (cyclomatic 17) csharp/TrainingRangeArmoryView.Catalog.cs:22 — TrainingRangeArmoryView.Candidates has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AttachmentDefinition.EffectDetail (cyclomatic 17) · ×1
  • AttachmentDefinition.EffectDetail (cyclomatic 17) csharp/WeaponSystem.cs:205 — AttachmentDefinition.EffectDetail has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · CombatHUD.BuildLootComparisons (cyclomatic 16) · ×1
  • CombatHUD.BuildLootComparisons (cyclomatic 16) csharp/CombatHUD.LootComparison.cs:263 — CombatHUD.BuildLootComparisons has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · CombatHUD.SelectSessionMode (cyclomatic 16) · ×1
  • CombatHUD.SelectSessionMode (cyclomatic 16) csharp/CombatHUD.Squad.cs:492 — CombatHUD.SelectSessionMode has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · DriveableVehicle.ApplyRamDamage (cyclomatic 16) · ×1
  • DriveableVehicle.ApplyRamDamage (cyclomatic 16) csharp/DriveableVehicle.cs:368 — DriveableVehicle.ApplyRamDamage has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · EnemyDeathLifecycleDiagnostics._Ready (cyclomatic 16) · ×1
  • EnemyDeathLifecycleDiagnostics._Ready (cyclomatic 16) csharp/EnemyDeathLifecycleDiagnostics.cs:10 — EnemyDeathLifecycleDiagnostics._Ready has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · EnemyOperator.BuildLootInventory (cyclomatic 16) · ×1
  • EnemyOperator.BuildLootInventory (cyclomatic 16) csharp/EnemyOperator.cs:284 — EnemyOperator.BuildLootInventory has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · EnemyOperator.FireAtRecentDamageThreat (cyclomatic 16) · ×1
  • EnemyOperator.FireAtRecentDamageThreat (cyclomatic 16) csharp/EnemyOperator.cs:1883 — EnemyOperator.FireAtRecentDamageThreat has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · FreightTerminalWorld.GetAircraftCombatants (cyclomatic 16) · ×1
  • FreightTerminalWorld.GetAircraftCombatants (cyclomatic 16) csharp/FreightTerminalWorld.AircraftCombat.cs:9 — FreightTerminalWorld.GetAircraftCombatants has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.TriggerWorldBossPulse (cyclomatic 16) · ×1
  • FreightTerminalWorld.TriggerWorldBossPulse (cyclomatic 16) csharp/FreightTerminalWorld.Boss.cs:117 — FreightTerminalWorld.TriggerWorldBossPulse has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.SpawnLootCases (cyclomatic 16) · ×1
  • FreightTerminalWorld.SpawnLootCases (cyclomatic 16) csharp/FreightTerminalWorld.cs:1060 — FreightTerminalWorld.SpawnLootCases has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: FreightTerminalWorld.ValidateStanceAndArmorFlow (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 · FreightTerminalWorld.CaptureBazaarCrossing (cyclomatic 16) · ×1
  • FreightTerminalWorld.CaptureBazaarCrossing (cyclomatic 16) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Capture.cs:36 — FreightTerminalWorld.CaptureBazaarCrossing has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.BazaarInteriorLightingReady (cyclomatic 16) · ×1
  • FreightTerminalWorld.BazaarInteriorLightingReady (cyclomatic 16) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.LightingDiagnostics.cs:14 — FreightTerminalWorld.BazaarInteriorLightingReady has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.TryUpdateDemolitionSquadDeviceObjective (cyclomatic 16) · ×1
  • FreightTerminalWorld.TryUpdateDemolitionSquadDeviceObjective (cyclomatic 16) csharp/FreightTerminalWorld.Demolition.Device.cs:753 — FreightTerminalWorld.TryUpdateDemolitionSquadDeviceObjective has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · FreightTerminalWorld.OnDemolitionPlayerState (cyclomatic 16) · ×1
  • FreightTerminalWorld.OnDemolitionPlayerState (cyclomatic 16) csharp/FreightTerminalWorld.Demolition.Network.cs:153 — FreightTerminalWorld.OnDemolitionPlayerState has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.TideglassSolidMaterialsReady (cyclomatic 16) · ×1
  • FreightTerminalWorld.TideglassSolidMaterialsReady (cyclomatic 16) csharp/FreightTerminalWorld.Demolition.TideglassReactor.AssetDiagnostics.cs:10 — FreightTerminalWorld.TideglassSolidMaterialsReady has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.TideglassCollisionSilhouettesReady (cyclomatic 16) · ×1
  • FreightTerminalWorld.TideglassCollisionSilhouettesReady (cyclomatic 16) csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:796 — FreightTerminalWorld.TideglassCollisionSilhouettesReady has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ValidateInventoryEquipment (cyclomatic 16) · ×1
  • FreightTerminalWorld.ValidateInventoryEquipment (cyclomatic 16) csharp/FreightTerminalWorld.InventoryEquipment.Diagnostics.cs:9 — FreightTerminalWorld.ValidateInventoryEquipment has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FreightTerminalWorld.RefreshOrbitalComplexLocalizedSignage (cyclomatic 16) · ×1
  • FreightTerminalWorld.RefreshOrbitalComplexLocalizedSignage (cyclomatic 16) csharp/FreightTerminalWorld.OrbitalComplex.Presentation.cs:23 — FreightTerminalWorld.RefreshOrbitalComplexLocalizedSignage 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 · FreightTerminalWorld.CapturePromotionMedia (cyclomatic 16) · ×1
  • FreightTerminalWorld.CapturePromotionMedia (cyclomatic 16) csharp/FreightTerminalWorld.PromotionCapture.cs:12 — FreightTerminalWorld.CapturePromotionMedia has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.BuildRefineryLaneExclusions (cyclomatic 16) · ×1
  • FreightTerminalWorld.BuildRefineryLaneExclusions (cyclomatic 16) csharp/FreightTerminalWorld.Refinery.NavigationValidation.cs:334 — FreightTerminalWorld.BuildRefineryLaneExclusions has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: FreightTerminalWorld.ValidateOldTownLandmarks (cyclomatic 23) 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 · FreightTerminalWorld.SelectSquadLadderTerminalComponents (cyclomatic 16) · ×1
  • FreightTerminalWorld.SelectSquadLadderTerminalComponents (cyclomatic 16) csharp/FreightTerminalWorld.Squad.LadderNavigation.cs:38 — FreightTerminalWorld.SelectSquadLadderTerminalComponents has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.TryBuildSquadGridSegment (cyclomatic 16) · ×1
  • FreightTerminalWorld.TryBuildSquadGridSegment (cyclomatic 16) csharp/FreightTerminalWorld.Squad.NavGrid.cs:481 — FreightTerminalWorld.TryBuildSquadGridSegment has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FreightTerminalWorld.ChooseTrainingRangeRespawnPosition (cyclomatic 16) · ×1
  • FreightTerminalWorld.ChooseTrainingRangeRespawnPosition (cyclomatic 16) csharp/FreightTerminalWorld.TrainingRange.cs:564 — FreightTerminalWorld.ChooseTrainingRangeRespawnPosition has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · InteractiveBuildingDoor.ValidateAuthoredVisualPanelLayout (cyclomatic 16) · ×1
  • InteractiveBuildingDoor.ValidateAuthoredVisualPanelLayout (cyclomatic 16) csharp/InteractiveBuildingDoor.cs:429 — InteractiveBuildingDoor.ValidateAuthoredVisualPanelLayout has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · InventoryModelPreview.RebuildModel (cyclomatic 16) · ×1
  • InventoryModelPreview.RebuildModel (cyclomatic 16) csharp/InventoryModelPreview.cs:224 — InventoryModelPreview.RebuildModel has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · OperatorLocomotionDiagnostics.CheckCase (cyclomatic 16) · ×1
  • OperatorLocomotionDiagnostics.CheckCase (cyclomatic 16) csharp/OperatorLocomotionDiagnostics.cs:69 — OperatorLocomotionDiagnostics.CheckCase has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SoundLab.BuildWeaponShot (cyclomatic 16) · ×1
  • SoundLab.BuildWeaponShot (cyclomatic 16) csharp/SoundLab.cs:265 — SoundLab.BuildWeaponShot has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: SoundLab.BuildMeleeSurfaceImpact (cyclomatic 20) 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 · SquadMate.ResolveCombatDestination (cyclomatic 16) · ×1
  • SquadMate.ResolveCombatDestination (cyclomatic 16) csharp/SquadMate.Combat.cs:518 — SquadMate.ResolveCombatDestination has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SquadMate.SetExtractionRemoteState (cyclomatic 16) · ×1
  • SquadMate.SetExtractionRemoteState (cyclomatic 16) csharp/SquadMate.Network.cs:30 — SquadMate.SetExtractionRemoteState has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · SquadMate.TryBuildRescueGlassEgressPlanAlongDirection (cyclomatic 16) · ×1
  • SquadMate.TryBuildRescueGlassEgressPlanAlongDirection (cyclomatic 16) csharp/SquadMate.RescueTraversal.cs:159 — SquadMate.TryBuildRescueGlassEgressPlanAlongDirection has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · TrainingRangeSetupView.AttachmentCandidates (cyclomatic 16) · ×1
  • TrainingRangeSetupView.AttachmentCandidates (cyclomatic 16) csharp/TrainingRangeSetupView.cs:546 — TrainingRangeSetupView.AttachmentCandidates 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 · LootItem.Detail (cyclomatic 16) · ×1
  • LootItem.Detail (cyclomatic 16) csharp/WeaponSystem.cs:405 — LootItem.Detail has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateSquadFlow (cognitive 282) · ×1
  • FreightTerminalWorld.ValidateSquadFlow (cognitive 282) csharp/FreightTerminalWorld.Squad.cs:3137 — FreightTerminalWorld.ValidateSquadFlow has cognitive complexity 282 (threshold 15). Of this number, 266 points are the body's own statements and 16 belong to 16 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateDemolitionTacticalAi (cognitive 182) · ×1
  • FreightTerminalWorld.ValidateDemolitionTacticalAi (cognitive 182) csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:865 — FreightTerminalWorld.ValidateDemolitionTacticalAi has cognitive complexity 182 (threshold 15). Of this number, 149 points are the body's own statements and 33 belong to 25 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateResidentialGameplay (cognitive 172) · ×1
  • FreightTerminalWorld.ValidateResidentialGameplay (cognitive 172) csharp/FreightTerminalWorld.Residential.cs:1778 — FreightTerminalWorld.ValidateResidentialGameplay has cognitive complexity 172 (threshold 15). Of this number, 154 points are the body's own statements and 18 belong to 14 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateDemolitionNetworkSession (cognitive 139) · ×1
  • FreightTerminalWorld.ValidateDemolitionNetworkSession (cognitive 139) csharp/FreightTerminalWorld.Demolition.Network.Diagnostics.cs:83 — FreightTerminalWorld.ValidateDemolitionNetworkSession has cognitive complexity 139 (threshold 15). Of this number, 134 points are the body's own statements and 5 belong to 5 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateStairsClimb (cognitive 126) · ×1
  • FreightTerminalWorld.ValidateStairsClimb (cognitive 126) csharp/FreightTerminalWorld.cs:6031 — FreightTerminalWorld.ValidateStairsClimb has cognitive complexity 126 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EnemyOperator.Engage (cognitive 89) · ×1
  • EnemyOperator.Engage (cognitive 89) csharp/EnemyOperator.cs:1549 — EnemyOperator.Engage 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 · FreightTerminalWorld.ValidateExtractionAi (cognitive 87) · ×1
  • FreightTerminalWorld.ValidateExtractionAi (cognitive 87) csharp/FreightTerminalWorld.cs:5433 — FreightTerminalWorld.ValidateExtractionAi has cognitive complexity 87 (threshold 15). Of this number, 84 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DemolitionArenaLayout.DemolitionArenaLayout.ctor (cognitive 84) · ×1
  • DemolitionArenaLayout.DemolitionArenaLayout.ctor (cognitive 84) csharp/DemolitionArenaLayout.cs:134 — DemolitionArenaLayout.DemolitionArenaLayout.ctor has cognitive complexity 84 (threshold 15). Of this number, 83 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TacticalPlayer.RunAuthoritativePhysicsStep (cognitive 84) · ×1
  • TacticalPlayer.RunAuthoritativePhysicsStep (cognitive 84) csharp/TacticalPlayer.cs:1235 — TacticalPlayer.RunAuthoritativePhysicsStep has cognitive complexity 84 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EnemyOperator._PhysicsProcess (cognitive 77) · ×1
  • EnemyOperator._PhysicsProcess (cognitive 77) csharp/EnemyOperator.cs:588 — EnemyOperator._PhysicsProcess 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 · FreightTerminalWorld.ValidateLootFlow (cognitive 74) · ×1
  • FreightTerminalWorld.ValidateLootFlow (cognitive 74) csharp/FreightTerminalWorld.cs:3788 — FreightTerminalWorld.ValidateLootFlow has cognitive complexity 74 (threshold 15). Of this number, 72 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateEnterableDoorways (cognitive 74) · ×1
  • FreightTerminalWorld.ValidateEnterableDoorways (cognitive 74) csharp/FreightTerminalWorld.Refinery.EnterableCollisionValidation.cs:9 — FreightTerminalWorld.ValidateEnterableDoorways has cognitive complexity 74 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateDistrictNetwork (cognitive 73) · ×1
  • FreightTerminalWorld.ValidateDistrictNetwork (cognitive 73) csharp/FreightTerminalWorld.Interdistrict.cs:563 — FreightTerminalWorld.ValidateDistrictNetwork has cognitive complexity 73 (threshold 15). Of this number, 71 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateDemolitionEnemyResponse (cognitive 71) · ×1
  • FreightTerminalWorld.ValidateDemolitionEnemyResponse (cognitive 71) csharp/FreightTerminalWorld.Demolition.EnemyResponse.Diagnostics.cs:8 — FreightTerminalWorld.ValidateDemolitionEnemyResponse has cognitive complexity 71 (threshold 15). Of this number, 70 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateJianghaiInteriors (cognitive 69) · ×1
  • FreightTerminalWorld.ValidateJianghaiInteriors (cognitive 69) csharp/FreightTerminalWorld.Refinery.Interiors.Diagnostics.cs:9 — FreightTerminalWorld.ValidateJianghaiInteriors has cognitive complexity 69 (threshold 15). Of this number, 58 points are the body's own statements and 11 belong to 11 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateSkyLinks (cognitive 68) · ×1
  • FreightTerminalWorld.ValidateSkyLinks (cognitive 68) csharp/FreightTerminalWorld.cs:6447 — FreightTerminalWorld.ValidateSkyLinks has cognitive complexity 68 (threshold 15). Of this number, 64 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DemolitionRetakeDistributionDiagnostics.Run (cognitive 67) · ×1
  • DemolitionRetakeDistributionDiagnostics.Run (cognitive 67) csharp/DemolitionRetakeDistribution.Diagnostics.cs:44 — DemolitionRetakeDistributionDiagnostics.Run has cognitive complexity 67 (threshold 15). Of this number, 66 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateSkybridgeAccess (cognitive 65) · ×1
  • FreightTerminalWorld.ValidateSkybridgeAccess (cognitive 65) csharp/FreightTerminalWorld.Residential.Access.cs:625 — FreightTerminalWorld.ValidateSkybridgeAccess has cognitive complexity 65 (threshold 15). Of this number, 63 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OperatorPresentationDiagnostics._Ready (cognitive 65) · ×1
  • OperatorPresentationDiagnostics._Ready (cognitive 65) csharp/OperatorPresentationDiagnostics.cs:33 — OperatorPresentationDiagnostics._Ready has cognitive complexity 65 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateSquadTraversal (cognitive 64) · ×1
  • FreightTerminalWorld.ValidateSquadTraversal (cognitive 64) csharp/FreightTerminalWorld.Squad.Traversal.Diagnostics.cs:11 — FreightTerminalWorld.ValidateSquadTraversal has cognitive complexity 64 (threshold 15). Of this number, 56 points are the body's own statements and 8 belong to 8 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.UpdateInteraction (cognitive 63) · ×1
  • FreightTerminalWorld.UpdateInteraction (cognitive 63) csharp/FreightTerminalWorld.cs:2275 — FreightTerminalWorld.UpdateInteraction 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 · FreightTerminalWorld.ValidateRefineryDoors (cognitive 62) · ×1
  • FreightTerminalWorld.ValidateRefineryDoors (cognitive 62) csharp/FreightTerminalWorld.Refinery.Doors.Diagnostics.cs:8 — FreightTerminalWorld.ValidateRefineryDoors has cognitive complexity 62 (threshold 15). Of this number, 56 points are the body's own statements and 6 belong to 6 function literals inside it that branch. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateSquadPerformance (cognitive 62) · ×1
  • FreightTerminalWorld.ValidateSquadPerformance (cognitive 62) csharp/FreightTerminalWorld.Squad.Performance.Diagnostics.cs:35 — FreightTerminalWorld.ValidateSquadPerformance has cognitive complexity 62 (threshold 15). Of this number, 61 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateQuickSlots (cognitive 60) · ×1
  • FreightTerminalWorld.ValidateQuickSlots (cognitive 60) csharp/FreightTerminalWorld.QuickSlots.Diagnostics.cs:8 — FreightTerminalWorld.ValidateQuickSlots has cognitive complexity 60 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · OperatorPresentationDiagnostics.ReadSurfaces (cognitive 60) · ×1
  • OperatorPresentationDiagnostics.ReadSurfaces (cognitive 60) csharp/OperatorPresentationDiagnostics.cs:298 — OperatorPresentationDiagnostics.ReadSurfaces has cognitive complexity 60 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.BazaarAuthoredVisualsReady (cognitive 59) · ×1
  • FreightTerminalWorld.BazaarAuthoredVisualsReady (cognitive 59) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs:582 — FreightTerminalWorld.BazaarAuthoredVisualsReady has cognitive complexity 59 (threshold 15). Of this number, 58 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateDemolitionMode (cognitive 59) · ×1
  • FreightTerminalWorld.ValidateDemolitionMode (cognitive 59) csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:495 — FreightTerminalWorld.ValidateDemolitionMode has cognitive complexity 59 (threshold 15). Of this number, 52 points are the body's own statements and 7 belong to 7 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateTrainingRange (cognitive 57) · ×1
  • FreightTerminalWorld.ValidateTrainingRange (cognitive 57) csharp/FreightTerminalWorld.TrainingRange.Diagnostics.cs:8 — FreightTerminalWorld.ValidateTrainingRange has cognitive complexity 57 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · WeaponCatalog.Build (cognitive 57) · ×1
  • WeaponCatalog.Build (cognitive 57) csharp/WeaponSystem.cs:790 — WeaponCatalog.Build has cognitive complexity 57 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateAdsAlignment (cognitive 56) · ×1
  • FreightTerminalWorld.ValidateAdsAlignment (cognitive 56) csharp/FreightTerminalWorld.WeaponPoseDiagnostics.cs:9 — FreightTerminalWorld.ValidateAdsAlignment 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 · FreightTerminalWorld.ValidateSquadSustainment (cognitive 53) · ×1
  • FreightTerminalWorld.ValidateSquadSustainment (cognitive 53) csharp/FreightTerminalWorld.Squad.Sustainment.Diagnostics.cs:10 — FreightTerminalWorld.ValidateSquadSustainment has cognitive complexity 53 (threshold 15). Of this number, 39 points are the body's own statements and 14 belong to 14 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · ResidentialRoomLootRules.CreateItem (cognitive 52) · ×1
  • ResidentialRoomLootRules.CreateItem (cognitive 52) csharp/ResidentialRoomLootRules.cs:131 — ResidentialRoomLootRules.CreateItem 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 · TacticalPlayer.RawReloadSupportTargetGlobal (cognitive 52) · ×1
  • TacticalPlayer.RawReloadSupportTargetGlobal (cognitive 52) csharp/TacticalPlayer.AuthoredVisuals.cs:1195 — TacticalPlayer.RawReloadSupportTargetGlobal has cognitive complexity 52 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TacticalPlayer.InspectAllWeaponReloadForDiagnostics (cognitive 52) · ×1
  • TacticalPlayer.InspectAllWeaponReloadForDiagnostics (cognitive 52) csharp/TacticalPlayer.ReloadDiagnostics.cs:9 — TacticalPlayer.InspectAllWeaponReloadForDiagnostics has cognitive complexity 52 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · TacticalPlayer.InspectOpticClearanceForDiagnostics (cognitive 47) · ×1
  • TacticalPlayer.InspectOpticClearanceForDiagnostics (cognitive 47) csharp/TacticalPlayer.WeaponPose.cs:398 — TacticalPlayer.InspectOpticClearanceForDiagnostics has cognitive complexity 47 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.UpdateSquadReviveAi (cognitive 46) · ×1
  • FreightTerminalWorld.UpdateSquadReviveAi (cognitive 46) csharp/FreightTerminalWorld.Squad.cs:1436 — FreightTerminalWorld.UpdateSquadReviveAi has cognitive complexity 46 (threshold 15). Of this number, 45 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · JianghaiInteriorShellValidator.Validate (cognitive 46) · ×1
  • JianghaiInteriorShellValidator.Validate (cognitive 46) csharp/JianghaiInteriorShellValidator.cs:34 — JianghaiInteriorShellValidator.Validate has cognitive complexity 46 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SquadMate._PhysicsProcess (cognitive 46) · ×1
  • SquadMate._PhysicsProcess (cognitive 46) csharp/SquadMate.cs:496 — SquadMate._PhysicsProcess has cognitive complexity 46 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · CombatHUD.RefreshDeploymentStore (cognitive 45) · ×1
  • CombatHUD.RefreshDeploymentStore (cognitive 45) csharp/CombatHUD.Deployment.cs:689 — CombatHUD.RefreshDeploymentStore has cognitive complexity 45 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.BuildEnterableComplex (cognitive 45) · ×1
  • FreightTerminalWorld.BuildEnterableComplex (cognitive 45) csharp/FreightTerminalWorld.Expansion.cs:163 — FreightTerminalWorld.BuildEnterableComplex has cognitive complexity 45 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.BuildResidentialLayoutFurnishings (cognitive 45) · ×1
  • FreightTerminalWorld.BuildResidentialLayoutFurnishings (cognitive 45) csharp/FreightTerminalWorld.Residential.Diversity.cs:138 — FreightTerminalWorld.BuildResidentialLayoutFurnishings has cognitive complexity 45 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateTideglassReactorDensityCore (cognitive 44) · ×1
  • FreightTerminalWorld.ValidateTideglassReactorDensityCore (cognitive 44) csharp/FreightTerminalWorld.Demolition.TideglassReactor.DensityDiagnostics.cs:111 — FreightTerminalWorld.ValidateTideglassReactorDensityCore has cognitive complexity 44 (threshold 15). Of this number, 32 points are the body's own statements and 12 belong to 9 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateAircraftCombat (cognitive 43) · ×1
  • FreightTerminalWorld.ValidateAircraftCombat (cognitive 43) csharp/FreightTerminalWorld.cs:5023 — FreightTerminalWorld.ValidateAircraftCombat has cognitive complexity 43 (threshold 15). Of this number, 40 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateResidentialCommunity (cognitive 43) · ×1
  • FreightTerminalWorld.ValidateResidentialCommunity (cognitive 43) csharp/FreightTerminalWorld.Residential.cs:1493 — FreightTerminalWorld.ValidateResidentialCommunity has cognitive complexity 43 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.TryPlanSquadLayeredRoute (cognitive 43) · ×1
  • FreightTerminalWorld.TryPlanSquadLayeredRoute (cognitive 43) csharp/FreightTerminalWorld.Squad.Traversal.cs:141 — FreightTerminalWorld.TryPlanSquadLayeredRoute has cognitive complexity 43 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.AddSquadPortalConnectors (cognitive 43) · ×1
  • FreightTerminalWorld.AddSquadPortalConnectors (cognitive 43) csharp/FreightTerminalWorld.Squad.Traversal.cs:438 — FreightTerminalWorld.AddSquadPortalConnectors has cognitive complexity 43 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SquadSustainmentService.TryTakeLoot (cognitive 43) · ×1
  • SquadSustainmentService.TryTakeLoot (cognitive 43) csharp/SquadSustainmentService.cs:199 — SquadSustainmentService.TryTakeLoot 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 · FreightTerminalWorld.ValidateDemolitionRules (cognitive 42) · ×1
  • FreightTerminalWorld.ValidateDemolitionRules (cognitive 42) csharp/FreightTerminalWorld.Demolition.Rules.Diagnostics.cs:8 — FreightTerminalWorld.ValidateDemolitionRules has cognitive complexity 42 (threshold 15). Of this number, 38 points are the body's own statements and 4 belong to 4 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.BuildResidentialSkyLinks (cognitive 42) · ×1
  • FreightTerminalWorld.BuildResidentialSkyLinks (cognitive 42) csharp/FreightTerminalWorld.Residential.cs:2977 — FreightTerminalWorld.BuildResidentialSkyLinks has cognitive complexity 42 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ApplyMedicSpray (cognitive 42) · ×1
  • FreightTerminalWorld.ApplyMedicSpray (cognitive 42) csharp/FreightTerminalWorld.Squad.cs:2546 — FreightTerminalWorld.ApplyMedicSpray has cognitive complexity 42 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ResolveSquadNavigationDestination (cognitive 42) · ×1
  • FreightTerminalWorld.ResolveSquadNavigationDestination (cognitive 42) csharp/FreightTerminalWorld.Squad.Navigation.cs:183 — FreightTerminalWorld.ResolveSquadNavigationDestination has cognitive complexity 42 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · OperatorPresentationDiagnostics.CheckPistols (cognitive 42) · ×1
  • OperatorPresentationDiagnostics.CheckPistols (cognitive 42) csharp/OperatorPresentationDiagnostics.cs:214 — OperatorPresentationDiagnostics.CheckPistols has cognitive complexity 42 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · SquadNavGrid.FindPath (cognitive 42) · ×1
  • SquadNavGrid.FindPath (cognitive 42) csharp/SquadNavGrid.cs:165 — SquadNavGrid.FindPath has cognitive complexity 42 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.UpdateDemolitionSquadPosts (cognitive 41) · ×1
  • FreightTerminalWorld.UpdateDemolitionSquadPosts (cognitive 41) csharp/FreightTerminalWorld.Demolition.Posts.cs:19 — FreightTerminalWorld.UpdateDemolitionSquadPosts has cognitive complexity 41 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.RefreshDemolitionStrategies (cognitive 41) · ×1
  • FreightTerminalWorld.RefreshDemolitionStrategies (cognitive 41) csharp/FreightTerminalWorld.Demolition.Strategy.cs:12 — FreightTerminalWorld.RefreshDemolitionStrategies has cognitive complexity 41 (threshold 15). Of this number, 39 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · FreightTerminalWorld.CaptureFirstPersonWeaponViews (cognitive 40) · ×1
  • FreightTerminalWorld.CaptureFirstPersonWeaponViews (cognitive 40) csharp/FreightTerminalWorld.CombatModels.cs:519 — FreightTerminalWorld.CaptureFirstPersonWeaponViews has cognitive complexity 40 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.TideglassPropCollisionMatchesDefinition (cognitive 40) · ×1
  • FreightTerminalWorld.TideglassPropCollisionMatchesDefinition (cognitive 40) csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:573 — FreightTerminalWorld.TideglassPropCollisionMatchesDefinition has cognitive complexity 40 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.UpdateOrbitalComplexUndertowPresentation (cognitive 39) · ×1
  • FreightTerminalWorld.UpdateOrbitalComplexUndertowPresentation (cognitive 39) csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Undertow.cs:270 — FreightTerminalWorld.UpdateOrbitalComplexUndertowPresentation has cognitive complexity 39 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TacticalPlayer.MovePlayer (cognitive 39) · ×1
  • TacticalPlayer.MovePlayer (cognitive 39) csharp/TacticalPlayer.cs:1654 — TacticalPlayer.MovePlayer has cognitive complexity 39 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.RunAiLadderDiagnostics (cognitive 38) · ×1
  • FreightTerminalWorld.RunAiLadderDiagnostics (cognitive 38) csharp/FreightTerminalWorld.AiLadder.Diagnostics.cs:71 — FreightTerminalWorld.RunAiLadderDiagnostics has cognitive complexity 38 (threshold 15). Of this number, 37 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateTideglassReactor (cognitive 38) · ×1
  • FreightTerminalWorld.ValidateTideglassReactor (cognitive 38) csharp/FreightTerminalWorld.Demolition.TideglassReactor.Diagnostics.cs:10 — FreightTerminalWorld.ValidateTideglassReactor has cognitive complexity 38 (threshold 15). Of this number, 25 points are the body's own statements and 13 belong to 11 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateExtractionSurvivors (cognitive 38) · ×1
  • FreightTerminalWorld.ValidateExtractionSurvivors (cognitive 38) csharp/FreightTerminalWorld.Extraction.Survivors.Diagnostics.cs:9 — FreightTerminalWorld.ValidateExtractionSurvivors has cognitive complexity 38 (threshold 15). Of this number, 35 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.EnsureAiSquadFill (cognitive 38) · ×1
  • FreightTerminalWorld.EnsureAiSquadFill (cognitive 38) csharp/FreightTerminalWorld.Squad.cs:1025 — FreightTerminalWorld.EnsureAiSquadFill has cognitive complexity 38 (threshold 15). Of this number, 37 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AuthoredOperatorAnimator.Update (cognitive 37) · ×1
  • AuthoredOperatorAnimator.Update (cognitive 37) csharp/AuthoredOperatorAnimator.cs:89 — AuthoredOperatorAnimator.Update has cognitive complexity 37 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DemolitionStrategyPlanner.ChooseAttackerSite (cognitive 36) · ×1
  • DemolitionStrategyPlanner.ChooseAttackerSite (cognitive 36) csharp/DemolitionStrategyPlanner.cs:193 — DemolitionStrategyPlanner.ChooseAttackerSite has cognitive complexity 36 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateAircraftBehavior (cognitive 36) · ×1
  • FreightTerminalWorld.ValidateAircraftBehavior (cognitive 36) csharp/FreightTerminalWorld.AircraftBehavior.Diagnostics.cs:8 — FreightTerminalWorld.ValidateAircraftBehavior has cognitive complexity 36 (threshold 15). Of this number, 35 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld._Process (cognitive 36) · ×1
  • FreightTerminalWorld._Process (cognitive 36) csharp/FreightTerminalWorld.cs:305 — FreightTerminalWorld._Process has cognitive complexity 36 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateOrbitalComplexIntegration (cognitive 35) · ×1
  • FreightTerminalWorld.ValidateOrbitalComplexIntegration (cognitive 35) csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Diagnostics.cs:354 — FreightTerminalWorld.ValidateOrbitalComplexIntegration has cognitive complexity 35 (threshold 15). Of this number, 31 points are the body's own statements and 4 belong to 4 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.CreateGradedLootItem (cognitive 35) · ×1
  • FreightTerminalWorld.CreateGradedLootItem (cognitive 35) csharp/FreightTerminalWorld.cs:1367 — FreightTerminalWorld.CreateGradedLootItem has cognitive complexity 35 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.TideglassPerimeterGatesReady (cognitive 35) · ×1
  • FreightTerminalWorld.TideglassPerimeterGatesReady (cognitive 35) csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:1115 — FreightTerminalWorld.TideglassPerimeterGatesReady has cognitive complexity 35 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateIndustrialInteriors (cognitive 35) · ×1
  • FreightTerminalWorld.ValidateIndustrialInteriors (cognitive 35) csharp/FreightTerminalWorld.IndustrialInteriors.Diagnostics.cs:10 — FreightTerminalWorld.ValidateIndustrialInteriors has cognitive complexity 35 (threshold 15). Of this number, 29 points are the body's own statements and 6 belong to 5 function literals inside it that branch. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · JianghaiGameplayCollisionBuilder.BuildInternal (cognitive 35) · ×1
  • JianghaiGameplayCollisionBuilder.BuildInternal (cognitive 35) csharp/JianghaiGameplayCollisionBuilder.cs:28 — JianghaiGameplayCollisionBuilder.BuildInternal has cognitive complexity 35 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateBazaarCrossingCore (cognitive 34) · ×1
  • FreightTerminalWorld.ValidateBazaarCrossingCore (cognitive 34) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Diagnostics.cs:45 — FreightTerminalWorld.ValidateBazaarCrossingCore has cognitive complexity 34 (threshold 15). Of this number, 22 points are the body's own statements and 12 belong to 10 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateDemolitionDefenseRound (cognitive 34) · ×1
  • FreightTerminalWorld.ValidateDemolitionDefenseRound (cognitive 34) csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:3030 — FreightTerminalWorld.ValidateDemolitionDefenseRound has cognitive complexity 34 (threshold 15). Of this number, 32 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.UpdateSquad (cognitive 34) · ×1
  • FreightTerminalWorld.UpdateSquad (cognitive 34) csharp/FreightTerminalWorld.Squad.cs:1311 — FreightTerminalWorld.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 · FreightTerminalWorld.ValidateResidentialCover (cognitive 33) · ×1
  • FreightTerminalWorld.ValidateResidentialCover (cognitive 33) csharp/FreightTerminalWorld.Residential.cs:2584 — FreightTerminalWorld.ValidateResidentialCover has cognitive complexity 33 (threshold 15). Of this number, 32 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SquadMate.UpdateSkillAction (cognitive 33) · ×1
  • SquadMate.UpdateSkillAction (cognitive 33) csharp/SquadMate.cs:1040 — SquadMate.UpdateSkillAction 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 · FreightTerminalWorld.UpdateOrbitalComplexBleedValvePresentation (cognitive 32) · ×1
  • FreightTerminalWorld.UpdateOrbitalComplexBleedValvePresentation (cognitive 32) csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Interactions.cs:194 — FreightTerminalWorld.UpdateOrbitalComplexBleedValvePresentation has cognitive complexity 32 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateExtractionSequence (cognitive 32) · ×1
  • FreightTerminalWorld.ValidateExtractionSequence (cognitive 32) csharp/FreightTerminalWorld.Extraction.cs:493 — FreightTerminalWorld.ValidateExtractionSequence has cognitive complexity 32 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateOperatorRoster (cognitive 32) · ×1
  • FreightTerminalWorld.ValidateOperatorRoster (cognitive 32) csharp/FreightTerminalWorld.OperatorRoster.Diagnostics.cs:10 — FreightTerminalWorld.ValidateOperatorRoster has cognitive complexity 32 (threshold 15). Of this number, 21 points are the body's own statements and 11 belong to 10 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateResidentialSquadStairs (cognitive 32) · ×1
  • FreightTerminalWorld.ValidateResidentialSquadStairs (cognitive 32) csharp/FreightTerminalWorld.ResidentialStairs.Diagnostics.cs:10 — FreightTerminalWorld.ValidateResidentialSquadStairs has cognitive complexity 32 (threshold 15). Of this number, 30 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SquadMate.UpdateTacticalMovement (cognitive 32) · ×1
  • SquadMate.UpdateTacticalMovement (cognitive 32) csharp/SquadMate.Combat.cs:397 — SquadMate.UpdateTacticalMovement has cognitive complexity 32 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · EnemyOperator.FireAtSquad (cognitive 31) · ×1
  • EnemyOperator.FireAtSquad (cognitive 31) csharp/EnemyOperator.cs:1963 — EnemyOperator.FireAtSquad has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateExtractionLoadout (cognitive 31) · ×1
  • FreightTerminalWorld.ValidateExtractionLoadout (cognitive 31) csharp/FreightTerminalWorld.cs:5812 — FreightTerminalWorld.ValidateExtractionLoadout has cognitive complexity 31 (threshold 15). Of this number, 28 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.BazaarGuardRailPhysicsReady (cognitive 31) · ×1
  • FreightTerminalWorld.BazaarGuardRailPhysicsReady (cognitive 31) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GuardRailDiagnostics.cs:31 — FreightTerminalWorld.BazaarGuardRailPhysicsReady has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.UpdateDemolitionRound (cognitive 31) · ×1
  • FreightTerminalWorld.UpdateDemolitionRound (cognitive 31) csharp/FreightTerminalWorld.Demolition.cs:819 — FreightTerminalWorld.UpdateDemolitionRound has cognitive complexity 31 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateIncendiaryAiAvoidance (cognitive 31) · ×1
  • FreightTerminalWorld.ValidateIncendiaryAiAvoidance (cognitive 31) csharp/FreightTerminalWorld.Incendiary.Diagnostics.cs:8 — FreightTerminalWorld.ValidateIncendiaryAiAvoidance has cognitive complexity 31 (threshold 15). Of this number, 29 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.OperatorCarrySampleValid (cognitive 31) · ×1
  • FreightTerminalWorld.OperatorCarrySampleValid (cognitive 31) csharp/FreightTerminalWorld.OperatorCarry.Diagnostics.cs:242 — FreightTerminalWorld.OperatorCarrySampleValid 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 · FreightTerminalWorld.CountRefineryNodes (cognitive 31) · ×1
  • FreightTerminalWorld.CountRefineryNodes (cognitive 31) csharp/FreightTerminalWorld.Refinery.RuntimeCountValidation.cs:7 — FreightTerminalWorld.CountRefineryNodes has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateRoofAccess (cognitive 31) · ×1
  • FreightTerminalWorld.ValidateRoofAccess (cognitive 31) csharp/FreightTerminalWorld.RoofAccess.cs:372 — FreightTerminalWorld.ValidateRoofAccess 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 · FreightTerminalWorld.UpdateManualRevive (cognitive 31) · ×1
  • FreightTerminalWorld.UpdateManualRevive (cognitive 31) csharp/FreightTerminalWorld.Squad.cs:1898 — FreightTerminalWorld.UpdateManualRevive has cognitive complexity 31 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · FreightTerminalWorld.TryResolveSquadGridNavigation (cognitive 31) · ×1
  • FreightTerminalWorld.TryResolveSquadGridNavigation (cognitive 31) csharp/FreightTerminalWorld.Squad.NavGrid.cs:102 — FreightTerminalWorld.TryResolveSquadGridNavigation has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TacticalPlayer.EquipFromLoot (cognitive 31) · ×1
  • TacticalPlayer.EquipFromLoot (cognitive 31) csharp/TacticalPlayer.cs:2563 — TacticalPlayer.EquipFromLoot has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CombatHUD.SetSquadRoster (cognitive 30) · ×1
  • CombatHUD.SetSquadRoster (cognitive 30) csharp/CombatHUD.Squad.cs:740 — CombatHUD.SetSquadRoster has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateDemolitionArena (cognitive 30) · ×1
  • FreightTerminalWorld.ValidateDemolitionArena (cognitive 30) csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:236 — FreightTerminalWorld.ValidateDemolitionArena has cognitive complexity 30 (threshold 15). Of this number, 19 points are the body's own statements and 11 belong to 6 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateDemolitionUtility (cognitive 30) · ×1
  • FreightTerminalWorld.ValidateDemolitionUtility (cognitive 30) csharp/FreightTerminalWorld.Demolition.Utility.Diagnostics.cs:8 — FreightTerminalWorld.ValidateDemolitionUtility has cognitive complexity 30 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateFieldUseLifecycle (cognitive 30) · ×1
  • FreightTerminalWorld.ValidateFieldUseLifecycle (cognitive 30) csharp/FreightTerminalWorld.FieldUseLifecycle.Diagnostics.cs:7 — FreightTerminalWorld.ValidateFieldUseLifecycle has cognitive complexity 30 (threshold 15). Of this number, 29 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateMeleeCombatSemantics (cognitive 30) · ×1
  • FreightTerminalWorld.ValidateMeleeCombatSemantics (cognitive 30) csharp/FreightTerminalWorld.Melee.Combat.Diagnostics.cs:71 — FreightTerminalWorld.ValidateMeleeCombatSemantics has cognitive complexity 30 (threshold 15). Of this number, 27 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateMedicalSystem (cognitive 30) · ×1
  • FreightTerminalWorld.ValidateMedicalSystem (cognitive 30) csharp/FreightTerminalWorld.Survival.cs:9 — FreightTerminalWorld.ValidateMedicalSystem has cognitive complexity 30 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateWorldBoss (cognitive 29) · ×1
  • FreightTerminalWorld.ValidateWorldBoss (cognitive 29) csharp/FreightTerminalWorld.Boss.cs:221 — FreightTerminalWorld.ValidateWorldBoss has cognitive complexity 29 (threshold 15). Of this number, 22 points are the body's own statements and 7 belong to 7 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateDemolitionWeapons (cognitive 29) · ×1
  • FreightTerminalWorld.ValidateDemolitionWeapons (cognitive 29) csharp/FreightTerminalWorld.Demolition.WeaponDrops.Diagnostics.cs:8 — FreightTerminalWorld.ValidateDemolitionWeapons has cognitive complexity 29 (threshold 15). Of this number, 28 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.CountMapRuntimeNodes (cognitive 29) · ×1
  • FreightTerminalWorld.CountMapRuntimeNodes (cognitive 29) csharp/FreightTerminalWorld.Performance.cs:127 — FreightTerminalWorld.CountMapRuntimeNodes has cognitive complexity 29 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · FreightTerminalWorld.OnRemoteSquadShot (cognitive 29) · ×1
  • FreightTerminalWorld.OnRemoteSquadShot (cognitive 29) csharp/FreightTerminalWorld.Squad.cs:1246 — FreightTerminalWorld.OnRemoteSquadShot has cognitive complexity 29 (threshold 15). Of this number, 27 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SquadMate.UpdateSustainment (cognitive 29) · ×1
  • SquadMate.UpdateSustainment (cognitive 29) csharp/SquadMate.Sustainment.cs:126 — SquadMate.UpdateSustainment has cognitive complexity 29 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · TacticalPlayer.ReloadMeshUsesSkeleton (cognitive 29) · ×1
  • TacticalPlayer.ReloadMeshUsesSkeleton (cognitive 29) csharp/TacticalPlayer.ReloadBodyDiagnostics.cs:466 — TacticalPlayer.ReloadMeshUsesSkeleton has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EnemyOperator.PlanCombatPosture (cognitive 28) · ×1
  • EnemyOperator.PlanCombatPosture (cognitive 28) csharp/EnemyOperator.CombatMovement.cs:92 — EnemyOperator.PlanCombatPosture has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.UpdateOrbitalComplexRuntimePresentation (cognitive 28) · ×1
  • FreightTerminalWorld.UpdateOrbitalComplexRuntimePresentation (cognitive 28) csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Runtime.cs:723 — FreightTerminalWorld.UpdateOrbitalComplexRuntimePresentation has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateCanalAccess (cognitive 28) · ×1
  • FreightTerminalWorld.ValidateCanalAccess (cognitive 28) csharp/FreightTerminalWorld.CanalAccess.Diagnostics.cs:9 — FreightTerminalWorld.ValidateCanalAccess has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.Explode (cognitive 28) · ×1
  • FreightTerminalWorld.Explode (cognitive 28) csharp/FreightTerminalWorld.cs:812 — FreightTerminalWorld.Explode has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ResolveAndApplyDemolitionObjectiveChannels (cognitive 28) · ×1
  • FreightTerminalWorld.ResolveAndApplyDemolitionObjectiveChannels (cognitive 28) csharp/FreightTerminalWorld.Demolition.Strategy.cs:318 — FreightTerminalWorld.ResolveAndApplyDemolitionObjectiveChannels has cognitive complexity 28 (threshold 15). Of this number, 26 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateExtractionNetworkWorld (cognitive 28) · ×1
  • FreightTerminalWorld.ValidateExtractionNetworkWorld (cognitive 28) csharp/FreightTerminalWorld.Extraction.Network.Diagnostics.cs:120 — FreightTerminalWorld.ValidateExtractionNetworkWorld 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 · FreightTerminalWorld.ApplyIncendiaryDamageTick (cognitive 28) · ×1
  • FreightTerminalWorld.ApplyIncendiaryDamageTick (cognitive 28) csharp/FreightTerminalWorld.Incendiary.cs:216 — FreightTerminalWorld.ApplyIncendiaryDamageTick has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.AdvanceSquadPortalWalkConnectorCache (cognitive 28) · ×1
  • FreightTerminalWorld.AdvanceSquadPortalWalkConnectorCache (cognitive 28) csharp/FreightTerminalWorld.Squad.Traversal.Connectors.cs:271 — FreightTerminalWorld.AdvanceSquadPortalWalkConnectorCache has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · JianghaiClanHallGateContract.TryResolve (cognitive 28) · ×1
  • JianghaiClanHallGateContract.TryResolve (cognitive 28) csharp/JianghaiClanHallGateContract.cs:47 — JianghaiClanHallGateContract.TryResolve has cognitive complexity 28 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · LowPolyBuildingArtBuilder.BuildResidentialMassing (cognitive 28) · ×1
  • LowPolyBuildingArtBuilder.BuildResidentialMassing (cognitive 28) csharp/LowPolyBuildingArtBuilder.Architecture.cs:257 — LowPolyBuildingArtBuilder.BuildResidentialMassing has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LowPolyBuildingArtBuilder.BuildResidentialFacadeProfile (cognitive 28) · ×1
  • LowPolyBuildingArtBuilder.BuildResidentialFacadeProfile (cognitive 28) csharp/LowPolyBuildingArtBuilder.Profiles.cs:63 — LowPolyBuildingArtBuilder.BuildResidentialFacadeProfile has cognitive complexity 28 (threshold 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · TacticalPlayer.ApplyWeaponBuildVisuals (cognitive 28) · ×1
  • TacticalPlayer.ApplyWeaponBuildVisuals (cognitive 28) csharp/TacticalPlayer.cs:1004 — TacticalPlayer.ApplyWeaponBuildVisuals has cognitive complexity 28 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · TacticalPlayer.TraceMeleeBladeSegment (cognitive 28) · ×1
  • TacticalPlayer.TraceMeleeBladeSegment (cognitive 28) csharp/TacticalPlayer.Melee.Combat.cs:249 — TacticalPlayer.TraceMeleeBladeSegment has cognitive complexity 28 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · FreightTerminalWorld.UpdateDemolitionSquadObjectiveRelay (cognitive 27) · ×1
  • FreightTerminalWorld.UpdateDemolitionSquadObjectiveRelay (cognitive 27) csharp/FreightTerminalWorld.Demolition.Strategy.cs:536 — FreightTerminalWorld.UpdateDemolitionSquadObjectiveRelay has cognitive complexity 27 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateExtractionNetworkLobby (cognitive 27) · ×1
  • FreightTerminalWorld.ValidateExtractionNetworkLobby (cognitive 27) csharp/FreightTerminalWorld.Extraction.Network.Diagnostics.cs:33 — FreightTerminalWorld.ValidateExtractionNetworkLobby has cognitive complexity 27 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · FreightTerminalWorld.BuildTowerStairDetails (cognitive 27) · ×1
  • FreightTerminalWorld.BuildTowerStairDetails (cognitive 27) csharp/FreightTerminalWorld.Residential.Density.cs:163 — FreightTerminalWorld.BuildTowerStairDetails has cognitive complexity 27 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · FreightTerminalWorld.TryHandleRoofAccessInteraction (cognitive 27) · ×1
  • FreightTerminalWorld.TryHandleRoofAccessInteraction (cognitive 27) csharp/FreightTerminalWorld.RoofAccess.cs:270 — FreightTerminalWorld.TryHandleRoofAccessInteraction has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateSquadIndoorRevive (cognitive 27) · ×1
  • FreightTerminalWorld.ValidateSquadIndoorRevive (cognitive 27) csharp/FreightTerminalWorld.Squad.IndoorRevive.Diagnostics.cs:10 — FreightTerminalWorld.ValidateSquadIndoorRevive has cognitive complexity 27 (threshold 15). Of this number, 22 points are the body's own statements and 5 belong to 5 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.TryValidateSquadSteppedDirectRoute (cognitive 27) · ×1
  • FreightTerminalWorld.TryValidateSquadSteppedDirectRoute (cognitive 27) csharp/FreightTerminalWorld.Squad.Navigation.cs:545 — FreightTerminalWorld.TryValidateSquadSteppedDirectRoute has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SquadNavigationGraph.FindShortestPath (cognitive 27) · ×1
  • SquadNavigationGraph.FindShortestPath (cognitive 27) csharp/SquadNavigationGraph.cs:16 — SquadNavigationGraph.FindShortestPath has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CombatModelLibrary.InstantiateAdaptedWeapon (cognitive 26) · ×1
  • CombatModelLibrary.InstantiateAdaptedWeapon (cognitive 26) csharp/CombatModelLibrary.cs:1440 — CombatModelLibrary.InstantiateAdaptedWeapon has cognitive complexity 26 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · DemolitionStrategyPlanner.PlanDefenderRetake (cognitive 26) · ×1
  • DemolitionStrategyPlanner.PlanDefenderRetake (cognitive 26) csharp/DemolitionStrategyPlanner.cs:584 — DemolitionStrategyPlanner.PlanDefenderRetake has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.TryResolveDemolitionSquadNavigation (cognitive 26) · ×1
  • FreightTerminalWorld.TryResolveDemolitionSquadNavigation (cognitive 26) csharp/FreightTerminalWorld.Demolition.SquadNavigation.cs:587 — FreightTerminalWorld.TryResolveDemolitionSquadNavigation has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ApplyTimeOfDay (cognitive 26) · ×1
  • FreightTerminalWorld.ApplyTimeOfDay (cognitive 26) csharp/FreightTerminalWorld.Level.cs:194 — FreightTerminalWorld.ApplyTimeOfDay has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TacticalPlayer.RefreshAuthoredPrimaryWeapon (cognitive 26) · ×1
  • TacticalPlayer.RefreshAuthoredPrimaryWeapon (cognitive 26) csharp/TacticalPlayer.AuthoredVisuals.cs:704 — TacticalPlayer.RefreshAuthoredPrimaryWeapon has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EnemyOperator.UpdateStance (cognitive 25) · ×1
  • EnemyOperator.UpdateStance (cognitive 25) csharp/EnemyOperator.cs:1306 — EnemyOperator.UpdateStance has cognitive complexity 25 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · EnemyOperator.UpdatePursuitNavigationMovement (cognitive 25) · ×1
  • EnemyOperator.UpdatePursuitNavigationMovement (cognitive 25) csharp/EnemyOperator.Pursuit.Navigation.cs:56 — EnemyOperator.UpdatePursuitNavigationMovement has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateFieldUsePresentation (cognitive 25) · ×1
  • FreightTerminalWorld.ValidateFieldUsePresentation (cognitive 25) csharp/FreightTerminalWorld.FieldUsePresentation.Diagnostics.cs:7 — FreightTerminalWorld.ValidateFieldUsePresentation has cognitive complexity 25 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.OnSquadDeploymentRequested (cognitive 25) · ×1
  • FreightTerminalWorld.OnSquadDeploymentRequested (cognitive 25) csharp/FreightTerminalWorld.Squad.cs:299 — FreightTerminalWorld.OnSquadDeploymentRequested has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateLootVariety (cognitive 25) · ×1
  • FreightTerminalWorld.ValidateLootVariety (cognitive 25) csharp/FreightTerminalWorld.Survival.cs:248 — FreightTerminalWorld.ValidateLootVariety has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CombatHUD.RefreshLootOverlay (cognitive 24) · ×1
  • CombatHUD.RefreshLootOverlay (cognitive 24) csharp/CombatHUD.cs:1033 — CombatHUD.RefreshLootOverlay has cognitive complexity 24 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · AuthoredOpticsVisual.Configure (cognitive 24) · ×1
  • AuthoredOpticsVisual.Configure (cognitive 24) csharp/CombatModelLibrary.Optics.cs:81 — AuthoredOpticsVisual.Configure has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DemolitionUtilityPlanner.Plan (cognitive 24) · ×1
  • DemolitionUtilityPlanner.Plan (cognitive 24) csharp/DemolitionUtilityPlanner.cs:47 — DemolitionUtilityPlanner.Plan has cognitive complexity 24 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · FreightTerminalWorld.FindNearestWeaponLootSource (cognitive 24) · ×1
  • FreightTerminalWorld.FindNearestWeaponLootSource (cognitive 24) csharp/FreightTerminalWorld.cs:1825 — FreightTerminalWorld.FindNearestWeaponLootSource has cognitive complexity 24 (threshold 15). Of this number, 22 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateArsenalFlow (cognitive 24) · ×1
  • FreightTerminalWorld.ValidateArsenalFlow (cognitive 24) csharp/FreightTerminalWorld.cs:4790 — FreightTerminalWorld.ValidateArsenalFlow has cognitive complexity 24 (threshold 15). Of this number, 22 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateExtractionSpawns (cognitive 24) · ×1
  • FreightTerminalWorld.ValidateExtractionSpawns (cognitive 24) csharp/FreightTerminalWorld.cs:5347 — FreightTerminalWorld.ValidateExtractionSpawns has cognitive complexity 24 (threshold 15). Of this number, 22 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FreightTerminalWorld.TideglassSolidMaterialsReady (cognitive 24) · ×1
  • FreightTerminalWorld.TideglassSolidMaterialsReady (cognitive 24) csharp/FreightTerminalWorld.Demolition.TideglassReactor.AssetDiagnostics.cs:10 — FreightTerminalWorld.TideglassSolidMaterialsReady has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateOperatorDeformation (cognitive 24) · ×1
  • FreightTerminalWorld.ValidateOperatorDeformation (cognitive 24) csharp/FreightTerminalWorld.OperatorDeformation.Diagnostics.cs:50 — FreightTerminalWorld.ValidateOperatorDeformation has cognitive complexity 24 (threshold 15). Of this number, 23 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateHighValueLootAccess (cognitive 24) · ×1
  • FreightTerminalWorld.ValidateHighValueLootAccess (cognitive 24) csharp/FreightTerminalWorld.Refinery.NavigationValidation.cs:9 — FreightTerminalWorld.ValidateHighValueLootAccess has cognitive complexity 24 (threshold 15). Of this number, 22 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.BuildRefineryLaneExclusions (cognitive 24) · ×1
  • FreightTerminalWorld.BuildRefineryLaneExclusions (cognitive 24) csharp/FreightTerminalWorld.Refinery.NavigationValidation.cs:334 — FreightTerminalWorld.BuildRefineryLaneExclusions has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.TryApplyRemoteSquadState (cognitive 24) · ×1
  • FreightTerminalWorld.TryApplyRemoteSquadState (cognitive 24) csharp/FreightTerminalWorld.Squad.cs:1141 — FreightTerminalWorld.TryApplyRemoteSquadState has cognitive complexity 24 (threshold 15). Of this number, 21 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateSquadDoorRescue (cognitive 24) · ×1
  • FreightTerminalWorld.ValidateSquadDoorRescue (cognitive 24) csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs:9 — FreightTerminalWorld.ValidateSquadDoorRescue has cognitive complexity 24 (threshold 15). Of this number, 22 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.TryPlanSquadGridRoute (cognitive 24) · ×1
  • FreightTerminalWorld.TryPlanSquadGridRoute (cognitive 24) csharp/FreightTerminalWorld.Squad.NavGrid.cs:250 — FreightTerminalWorld.TryPlanSquadGridRoute has cognitive complexity 24 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · FreightTerminalWorld.ChooseTrainingRangeRespawnPosition (cognitive 24) · ×1
  • FreightTerminalWorld.ChooseTrainingRangeRespawnPosition (cognitive 24) csharp/FreightTerminalWorld.TrainingRange.cs:564 — FreightTerminalWorld.ChooseTrainingRangeRespawnPosition has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateVehicleCombat (cognitive 24) · ×1
  • FreightTerminalWorld.ValidateVehicleCombat (cognitive 24) csharp/FreightTerminalWorld.VehicleCombat.Diagnostics.cs:8 — FreightTerminalWorld.ValidateVehicleCombat 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 · MissionDirector.StartMissionAsync (cognitive 24) · ×1
  • MissionDirector.StartMissionAsync (cognitive 24) csharp/MissionDirector.cs:265 — MissionDirector.StartMissionAsync has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SquadMate.SelectBlockedSightFlank (cognitive 24) · ×1
  • SquadMate.SelectBlockedSightFlank (cognitive 24) csharp/SquadMate.Combat.cs:612 — SquadMate.SelectBlockedSightFlank has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TacticalPlayer.InspectVisibleMeshScreenProjection (cognitive 24) · ×1
  • TacticalPlayer.InspectVisibleMeshScreenProjection (cognitive 24) csharp/TacticalPlayer.AuthoredVisuals.cs:278 — TacticalPlayer.InspectVisibleMeshScreenProjection has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TacticalPlayer.TryVaultLowObstacle (cognitive 24) · ×1
  • TacticalPlayer.TryVaultLowObstacle (cognitive 24) csharp/TacticalPlayer.MovementInput.cs:97 — TacticalPlayer.TryVaultLowObstacle has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AttachmentDefinition.EffectDetail (cognitive 24) · ×1
  • AttachmentDefinition.EffectDetail (cognitive 24) csharp/WeaponSystem.cs:205 — AttachmentDefinition.EffectDetail has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.UpdateOrbitalComplexTacticalSignals (cognitive 23) · ×1
  • FreightTerminalWorld.UpdateOrbitalComplexTacticalSignals (cognitive 23) csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.TacticalSignals.cs:173 — FreightTerminalWorld.UpdateOrbitalComplexTacticalSignals has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateAiNavigation (cognitive 23) · ×1
  • FreightTerminalWorld.ValidateAiNavigation (cognitive 23) csharp/FreightTerminalWorld.AiNavigation.Diagnostics.cs:10 — FreightTerminalWorld.ValidateAiNavigation has cognitive complexity 23 (threshold 15). Of this number, 20 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.BuildExtractionLootRanking (cognitive 23) · ×1
  • FreightTerminalWorld.BuildExtractionLootRanking (cognitive 23) csharp/FreightTerminalWorld.cs:2200 — FreightTerminalWorld.BuildExtractionLootRanking has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateBreakableGlass (cognitive 23) · ×1
  • FreightTerminalWorld.ValidateBreakableGlass (cognitive 23) csharp/FreightTerminalWorld.Glass.cs:50 — FreightTerminalWorld.ValidateBreakableGlass has cognitive complexity 23 (threshold 15). Of this number, 18 points are the body's own statements and 5 belong to 4 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateFreightTerminalDoors (cognitive 23) · ×1
  • FreightTerminalWorld.ValidateFreightTerminalDoors (cognitive 23) csharp/FreightTerminalWorld.IndustrialDoors.cs:80 — FreightTerminalWorld.ValidateFreightTerminalDoors has cognitive complexity 23 (threshold 15). Of this number, 18 points are the body's own statements and 5 belong to 5 function literals inside it that branch. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FreightTerminalWorld.InspectMeleeRuntime (cognitive 23) · ×1
  • FreightTerminalWorld.InspectMeleeRuntime (cognitive 23) csharp/FreightTerminalWorld.Melee.Diagnostics.cs:133 — FreightTerminalWorld.InspectMeleeRuntime has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateSquadTactics (cognitive 23) · ×1
  • FreightTerminalWorld.ValidateSquadTactics (cognitive 23) csharp/FreightTerminalWorld.Squad.Tactics.Diagnostics.cs:8 — FreightTerminalWorld.ValidateSquadTactics has cognitive complexity 23 (threshold 15). Of this number, 17 points are the body's own statements and 6 belong to 6 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateWeaponAudio (cognitive 23) · ×1
  • FreightTerminalWorld.ValidateWeaponAudio (cognitive 23) csharp/FreightTerminalWorld.WeaponAudioDiagnostics.cs:8 — FreightTerminalWorld.ValidateWeaponAudio has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · JianghaiOldCitySceneLoader.InspectScene (cognitive 23) · ×1
  • JianghaiOldCitySceneLoader.InspectScene (cognitive 23) csharp/JianghaiOldCitySceneLoader.cs:494 — JianghaiOldCitySceneLoader.InspectScene has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LootDragCard.Configure (cognitive 23) · ×1
  • LootDragCard.Configure (cognitive 23) csharp/LootDragControls.cs:192 — LootDragCard.Configure 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 · SquadNavGrid.SnapToWalkable (cognitive 23) · ×1
  • SquadNavGrid.SnapToWalkable (cognitive 23) csharp/SquadNavGrid.cs:88 — SquadNavGrid.SnapToWalkable has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.TriggerWorldBossPulse (cognitive 22) · ×1
  • FreightTerminalWorld.TriggerWorldBossPulse (cognitive 22) csharp/FreightTerminalWorld.Boss.cs:117 — FreightTerminalWorld.TriggerWorldBossPulse 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 · FreightTerminalWorld.BazaarLongestSampledSightline (cognitive 22) · ×1
  • FreightTerminalWorld.BazaarLongestSampledSightline (cognitive 22) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.DensityDiagnostics.cs:220 — FreightTerminalWorld.BazaarLongestSampledSightline has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.BazaarOpenApproachStairEntriesReady (cognitive 22) · ×1
  • FreightTerminalWorld.BazaarOpenApproachStairEntriesReady (cognitive 22) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs:105 — FreightTerminalWorld.BazaarOpenApproachStairEntriesReady has cognitive complexity 22 (threshold 15). Of this number, 14 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.BazaarPortalGlassReady (cognitive 22) · ×1
  • FreightTerminalWorld.BazaarPortalGlassReady (cognitive 22) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GlassDiagnostics.cs:22 — FreightTerminalWorld.BazaarPortalGlassReady has cognitive complexity 22 (threshold 15). Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.SetDemolitionActorsFrozen (cognitive 22) · ×1
  • FreightTerminalWorld.SetDemolitionActorsFrozen (cognitive 22) csharp/FreightTerminalWorld.Demolition.Buy.cs:427 — FreightTerminalWorld.SetDemolitionActorsFrozen has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateDemolitionBriefing (cognitive 22) · ×1
  • FreightTerminalWorld.ValidateDemolitionBriefing (cognitive 22) csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:10 — FreightTerminalWorld.ValidateDemolitionBriefing has cognitive complexity 22 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateExplosionCover (cognitive 22) · ×1
  • FreightTerminalWorld.ValidateExplosionCover (cognitive 22) csharp/FreightTerminalWorld.ExplosionOcclusion.Diagnostics.cs:8 — FreightTerminalWorld.ValidateExplosionCover has cognitive complexity 22 (threshold 15). Of this number, 20 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateSquadGlassRescue (cognitive 22) · ×1
  • FreightTerminalWorld.ValidateSquadGlassRescue (cognitive 22) csharp/FreightTerminalWorld.Squad.GlassRescue.Diagnostics.cs:9 — FreightTerminalWorld.ValidateSquadGlassRescue has cognitive complexity 22 (threshold 15). Of this number, 20 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.SelectSquadLadderTerminalComponents (cognitive 22) · ×1
  • FreightTerminalWorld.SelectSquadLadderTerminalComponents (cognitive 22) csharp/FreightTerminalWorld.Squad.LadderNavigation.cs:38 — FreightTerminalWorld.SelectSquadLadderTerminalComponents has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.TryBuildSquadGridSegment (cognitive 22) · ×1
  • FreightTerminalWorld.TryBuildSquadGridSegment (cognitive 22) csharp/FreightTerminalWorld.Squad.NavGrid.cs:481 — FreightTerminalWorld.TryBuildSquadGridSegment has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.BuildSquadPortalComponentReachability (cognitive 22) · ×1
  • FreightTerminalWorld.BuildSquadPortalComponentReachability (cognitive 22) csharp/FreightTerminalWorld.Squad.Traversal.cs:570 — FreightTerminalWorld.BuildSquadPortalComponentReachability has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateResidentialDensity (cognitive 22) · ×1
  • FreightTerminalWorld.ValidateResidentialDensity (cognitive 22) csharp/FreightTerminalWorld.Survival.cs:422 — FreightTerminalWorld.ValidateResidentialDensity has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · JianghaiInteriorShellValidator.RayHitsMesh (cognitive 22) · ×1
  • JianghaiInteriorShellValidator.RayHitsMesh (cognitive 22) csharp/JianghaiInteriorShellValidator.cs:203 — JianghaiInteriorShellValidator.RayHitsMesh has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ResidentialStreetArtBuilder.CreatePlacements (cognitive 22) · ×1
  • ResidentialStreetArtBuilder.CreatePlacements (cognitive 22) csharp/ResidentialStreetArtBuilder.cs:428 — ResidentialStreetArtBuilder.CreatePlacements has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SquadMate.UpdateCombatTarget (cognitive 22) · ×1
  • SquadMate.UpdateCombatTarget (cognitive 22) csharp/SquadMate.Combat.cs:139 — SquadMate.UpdateCombatTarget has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TacticalPlayer.UpdateProfiledReloadAnimation (cognitive 22) · ×1
  • TacticalPlayer.UpdateProfiledReloadAnimation (cognitive 22) csharp/TacticalPlayer.ReloadPresentation.cs:27 — TacticalPlayer.UpdateProfiledReloadAnimation has cognitive complexity 22 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · CombatModelLibrary.InstantiateRoleFamily (cognitive 21) · ×1
  • CombatModelLibrary.InstantiateRoleFamily (cognitive 21) csharp/CombatModelLibrary.FirstPerson.cs:311 — CombatModelLibrary.InstantiateRoleFamily has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DemolitionRoutePlanner.TacticalSegmentPenalty (cognitive 21) · ×1
  • DemolitionRoutePlanner.TacticalSegmentPenalty (cognitive 21) csharp/DemolitionRoutePlanner.cs:435 — DemolitionRoutePlanner.TacticalSegmentPenalty has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EnemyOperator.AcquireCombatTarget (cognitive 21) · ×1
  • EnemyOperator.AcquireCombatTarget (cognitive 21) csharp/EnemyOperator.cs:983 — EnemyOperator.AcquireCombatTarget has cognitive complexity 21 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateAmmoInventoryFlow (cognitive 21) · ×1
  • FreightTerminalWorld.ValidateAmmoInventoryFlow (cognitive 21) csharp/FreightTerminalWorld.cs:3606 — FreightTerminalWorld.ValidateAmmoInventoryFlow has cognitive complexity 21 (threshold 15). Of this number, 17 points are the body's own statements and 4 belong to 4 function literals inside it that branch. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateWeaponUiFlow (cognitive 21) · ×1
  • FreightTerminalWorld.ValidateWeaponUiFlow (cognitive 21) csharp/FreightTerminalWorld.cs:4596 — FreightTerminalWorld.ValidateWeaponUiFlow has cognitive complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateSpecialLandmarks (cognitive 21) · ×1
  • FreightTerminalWorld.ValidateSpecialLandmarks (cognitive 21) csharp/FreightTerminalWorld.SpecialLandmarks.cs:674 — FreightTerminalWorld.ValidateSpecialLandmarks has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.FindLatestVisibleTrailIndex (cognitive 21) · ×1
  • FreightTerminalWorld.FindLatestVisibleTrailIndex (cognitive 21) csharp/FreightTerminalWorld.Squad.Navigation.cs:805 — FreightTerminalWorld.FindLatestVisibleTrailIndex has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LowPolyBuildingArtBuilder.BuildResidentialRoofProfile (cognitive 21) · ×1
  • LowPolyBuildingArtBuilder.BuildResidentialRoofProfile (cognitive 21) csharp/LowPolyBuildingArtBuilder.Profiles.cs:129 — LowPolyBuildingArtBuilder.BuildResidentialRoofProfile has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SquadNetwork.TryParseEndpoint (cognitive 21) · ×1
  • SquadNetwork.TryParseEndpoint (cognitive 21) csharp/SquadNetwork.cs:119 — SquadNetwork.TryParseEndpoint has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SquadSustainmentService.TryReserveBestSource (cognitive 21) · ×1
  • SquadSustainmentService.TryReserveBestSource (cognitive 21) csharp/SquadSustainmentService.cs:81 — SquadSustainmentService.TryReserveBestSource has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TacticalPlayer.InspectOpticAxisProjectionForDiagnostics (cognitive 21) · ×1
  • TacticalPlayer.InspectOpticAxisProjectionForDiagnostics (cognitive 21) csharp/TacticalPlayer.WeaponPose.cs:543 — TacticalPlayer.InspectOpticAxisProjectionForDiagnostics has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TrainingRangeSetupView.RefreshAttachmentOptions (cognitive 21) · ×1
  • TrainingRangeSetupView.RefreshAttachmentOptions (cognitive 21) csharp/TrainingRangeSetupView.cs:502 — TrainingRangeSetupView.RefreshAttachmentOptions has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AuthoredWeaponVisual.WorldExternalOpticMountMatches (cognitive 20) · ×1
  • AuthoredWeaponVisual.WorldExternalOpticMountMatches (cognitive 20) csharp/CombatModelLibrary.cs:230 — AuthoredWeaponVisual.WorldExternalOpticMountMatches 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 · AuthoredOperatorVisual.CountFingerBones (cognitive 20) · ×1
  • AuthoredOperatorVisual.CountFingerBones (cognitive 20) csharp/CombatModelLibrary.cs:726 — AuthoredOperatorVisual.CountFingerBones has cognitive complexity 20 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · DemolitionArenaLayout.TryFindCapsuleSegmentBlocker (cognitive 20) · ×1
  • DemolitionArenaLayout.TryFindCapsuleSegmentBlocker (cognitive 20) csharp/DemolitionArenaLayout.cs:754 — DemolitionArenaLayout.TryFindCapsuleSegmentBlocker has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DemolitionElevationTransitions.Create (cognitive 20) · ×1
  • DemolitionElevationTransitions.Create (cognitive 20) csharp/DemolitionElevationTransitions.cs:39 — DemolitionElevationTransitions.Create has cognitive complexity 20 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateCorpseLootFlow (cognitive 20) · ×1
  • FreightTerminalWorld.ValidateCorpseLootFlow (cognitive 20) csharp/FreightTerminalWorld.cs:4437 — FreightTerminalWorld.ValidateCorpseLootFlow has cognitive complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateBackpackTab (cognitive 20) · ×1
  • FreightTerminalWorld.ValidateBackpackTab (cognitive 20) csharp/FreightTerminalWorld.cs:6298 — FreightTerminalWorld.ValidateBackpackTab has cognitive complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.OnDemolitionDeploymentRequested (cognitive 20) · ×1
  • FreightTerminalWorld.OnDemolitionDeploymentRequested (cognitive 20) csharp/FreightTerminalWorld.Demolition.cs:116 — FreightTerminalWorld.OnDemolitionDeploymentRequested has cognitive complexity 20 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · FreightTerminalWorld.OnDemolitionPlayerState (cognitive 20) · ×1
  • FreightTerminalWorld.OnDemolitionPlayerState (cognitive 20) csharp/FreightTerminalWorld.Demolition.Network.cs:153 — FreightTerminalWorld.OnDemolitionPlayerState has cognitive complexity 20 (threshold 15). Of this number, 18 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.CaptureTideglassReactor (cognitive 20) · ×1
  • FreightTerminalWorld.CaptureTideglassReactor (cognitive 20) csharp/FreightTerminalWorld.Demolition.TideglassReactor.Capture.cs:9 — FreightTerminalWorld.CaptureTideglassReactor has cognitive complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.TideglassDensityMeasureSpatialMetrics (cognitive 20) · ×1
  • FreightTerminalWorld.TideglassDensityMeasureSpatialMetrics (cognitive 20) csharp/FreightTerminalWorld.Demolition.TideglassReactor.DensityDiagnostics.cs:628 — FreightTerminalWorld.TideglassDensityMeasureSpatialMetrics has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.AdvanceSquadTrailCursor (cognitive 20) · ×1
  • FreightTerminalWorld.AdvanceSquadTrailCursor (cognitive 20) csharp/FreightTerminalWorld.Squad.Navigation.cs:871 — FreightTerminalWorld.AdvanceSquadTrailCursor has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateWeaponImpact (cognitive 20) · ×1
  • FreightTerminalWorld.ValidateWeaponImpact (cognitive 20) csharp/FreightTerminalWorld.WeaponAudioDiagnostics.cs:169 — FreightTerminalWorld.ValidateWeaponImpact has cognitive complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · SquadMate.TrackTacticalMovement (cognitive 20) · ×1
  • SquadMate.TrackTacticalMovement (cognitive 20) csharp/SquadMate.Combat.cs:832 — SquadMate.TrackTacticalMovement has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SquadMate.TryUpdateIncendiaryAvoidance (cognitive 20) · ×1
  • SquadMate.TryUpdateIncendiaryAvoidance (cognitive 20) csharp/SquadMate.IncendiaryAvoidance.cs:22 — SquadMate.TryUpdateIncendiaryAvoidance has cognitive complexity 20 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · TacticalPlayer.AlignAuthoredArmsToWeapon (cognitive 20) · ×1
  • TacticalPlayer.AlignAuthoredArmsToWeapon (cognitive 20) csharp/TacticalPlayer.AuthoredVisuals.cs:1079 — TacticalPlayer.AlignAuthoredArmsToWeapon has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TacticalPlayer.UpdateKnifeAnimation (cognitive 20) · ×1
  • TacticalPlayer.UpdateKnifeAnimation (cognitive 20) csharp/TacticalPlayer.Melee.cs:244 — TacticalPlayer.UpdateKnifeAnimation has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EnemyOperator.BuildLootInventory (cognitive 19) · ×1
  • EnemyOperator.BuildLootInventory (cognitive 19) csharp/EnemyOperator.cs:284 — EnemyOperator.BuildLootInventory has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateCrowdPerformance (cognitive 19) · ×1
  • FreightTerminalWorld.ValidateCrowdPerformance (cognitive 19) csharp/FreightTerminalWorld.CrowdPerformance.Diagnostics.cs:16 — FreightTerminalWorld.ValidateCrowdPerformance has cognitive complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.TryResolveValidatedDemolitionEscortFallback (cognitive 19) · ×1
  • FreightTerminalWorld.TryResolveValidatedDemolitionEscortFallback (cognitive 19) csharp/FreightTerminalWorld.Demolition.SquadNavigation.cs:444 — FreightTerminalWorld.TryResolveValidatedDemolitionEscortFallback has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.TryHandleDemolitionDefenderMovement (cognitive 19) · ×1
  • FreightTerminalWorld.TryHandleDemolitionDefenderMovement (cognitive 19) csharp/FreightTerminalWorld.Demolition.Strategy.cs:715 — FreightTerminalWorld.TryHandleDemolitionDefenderMovement has cognitive complexity 19 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · FreightTerminalWorld.TideglassAuthoredMeshCollisionReady (cognitive 19) · ×1
  • FreightTerminalWorld.TideglassAuthoredMeshCollisionReady (cognitive 19) csharp/FreightTerminalWorld.Demolition.TideglassReactor.AssetDiagnostics.cs:80 — FreightTerminalWorld.TideglassAuthoredMeshCollisionReady has cognitive complexity 19 (threshold 15). None of this is in the body itself: all 19 points belong to 2 function literals inside it that branch (lines 90, 110). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateHudPerformance (cognitive 19) · ×1
  • FreightTerminalWorld.ValidateHudPerformance (cognitive 19) csharp/FreightTerminalWorld.HudPerformance.Diagnostics.cs:13 — FreightTerminalWorld.ValidateHudPerformance 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 · FreightTerminalWorld.CaptureRefineryMap (cognitive 19) · ×1
  • FreightTerminalWorld.CaptureRefineryMap (cognitive 19) csharp/FreightTerminalWorld.Refinery.Capture.cs:8 — FreightTerminalWorld.CaptureRefineryMap has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateAuthoredCollisionSources (cognitive 19) · ×1
  • FreightTerminalWorld.ValidateAuthoredCollisionSources (cognitive 19) csharp/FreightTerminalWorld.Refinery.CollisionDiagnostics.cs:136 — FreightTerminalWorld.ValidateAuthoredCollisionSources has cognitive complexity 19 (threshold 15). Of this number, 15 points are the body's own statements and 4 belong to 4 function literals inside it that branch. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FreightTerminalWorld.WalkSkybridgeAccessLeg (cognitive 19) · ×1
  • FreightTerminalWorld.WalkSkybridgeAccessLeg (cognitive 19) csharp/FreightTerminalWorld.Residential.Access.cs:541 — FreightTerminalWorld.WalkSkybridgeAccessLeg has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.HasActionableAiReviveForSurvivorExtraction (cognitive 19) · ×1
  • FreightTerminalWorld.HasActionableAiReviveForSurvivorExtraction (cognitive 19) csharp/FreightTerminalWorld.Squad.cs:1684 — FreightTerminalWorld.HasActionableAiReviveForSurvivorExtraction has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.TryBuildSquadEmergencyDoorPlan (cognitive 19) · ×1
  • FreightTerminalWorld.TryBuildSquadEmergencyDoorPlan (cognitive 19) csharp/FreightTerminalWorld.Squad.EmergencyEgress.Planning.cs:8 — FreightTerminalWorld.TryBuildSquadEmergencyDoorPlan has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.FindSquadGridGoalCells (cognitive 19) · ×1
  • FreightTerminalWorld.FindSquadGridGoalCells (cognitive 19) csharp/FreightTerminalWorld.Squad.NavGrid.cs:564 — FreightTerminalWorld.FindSquadGridGoalCells has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · JianghaiOldCitySceneLoader.AccumulateVisibleMeshWorldBounds (cognitive 19) · ×1
  • JianghaiOldCitySceneLoader.AccumulateVisibleMeshWorldBounds (cognitive 19) csharp/JianghaiOldCitySceneLoader.cs:667 — JianghaiOldCitySceneLoader.AccumulateVisibleMeshWorldBounds has cognitive complexity 19 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · SquadMate.TryFire (cognitive 19) · ×1
  • SquadMate.TryFire (cognitive 19) csharp/SquadMate.cs:757 — SquadMate.TryFire has cognitive complexity 19 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · SquadNetwork.SubmitClientAbility (cognitive 19) · ×1
  • SquadNetwork.SubmitClientAbility (cognitive 19) csharp/SquadNetwork.cs:380 — SquadNetwork.SubmitClientAbility has cognitive complexity 19 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · TacticalPlayer.UpdateVehiclePassenger (cognitive 19) · ×1
  • TacticalPlayer.UpdateVehiclePassenger (cognitive 19) csharp/TacticalPlayer.cs:1470 — TacticalPlayer.UpdateVehiclePassenger has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CombatHUD.RefreshClassSkillText (cognitive 18) · ×1
  • CombatHUD.RefreshClassSkillText (cognitive 18) csharp/CombatHUD.Squad.cs:881 — CombatHUD.RefreshClassSkillText 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 · CombatModelLibrary.InspectIntegratedScope (cognitive 18) · ×1
  • CombatModelLibrary.InspectIntegratedScope (cognitive 18) csharp/CombatModelLibrary.IntegratedOptics.cs:105 — CombatModelLibrary.InspectIntegratedScope has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TimeOfDayStyles.ResolveStartupTimeOfDay (cognitive 18) · ×1
  • TimeOfDayStyles.ResolveStartupTimeOfDay (cognitive 18) csharp/DeploymentTimeOfDay.cs:88 — TimeOfDayStyles.ResolveStartupTimeOfDay has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DriveableVehicle.Drive (cognitive 18) · ×1
  • DriveableVehicle.Drive (cognitive 18) csharp/DriveableVehicle.cs:197 — DriveableVehicle.Drive has cognitive complexity 18 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · EnemyOperator.ApplyIncendiaryAvoidanceDecision (cognitive 18) · ×1
  • EnemyOperator.ApplyIncendiaryAvoidanceDecision (cognitive 18) csharp/EnemyOperator.IncendiaryAvoidance.cs:70 — EnemyOperator.ApplyIncendiaryAvoidanceDecision has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · OrbitalComplexLayoutValidator.GameplayPositions (cognitive 18) · ×1
  • OrbitalComplexLayoutValidator.GameplayPositions (cognitive 18) csharp/ExtractionMaps/OrbitalComplex/OrbitalComplexLayoutValidator.cs:172 — OrbitalComplexLayoutValidator.GameplayPositions has cognitive complexity 18 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · FreightTerminalWorld.SpawnLootCases (cognitive 18) · ×1
  • FreightTerminalWorld.SpawnLootCases (cognitive 18) csharp/FreightTerminalWorld.cs:1060 — FreightTerminalWorld.SpawnLootCases has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateLargeMapFlow (cognitive 18) · ×1
  • FreightTerminalWorld.ValidateLargeMapFlow (cognitive 18) csharp/FreightTerminalWorld.cs:6909 — FreightTerminalWorld.ValidateLargeMapFlow 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 · FreightTerminalWorld.BazaarVerticalPlannerReady (cognitive 18) · ×1
  • FreightTerminalWorld.BazaarVerticalPlannerReady (cognitive 18) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.RouteDiagnostics.cs:47 — FreightTerminalWorld.BazaarVerticalPlannerReady has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ResolveDemolitionOpponentBuy (cognitive 18) · ×1
  • FreightTerminalWorld.ResolveDemolitionOpponentBuy (cognitive 18) csharp/FreightTerminalWorld.Demolition.Buy.cs:470 — FreightTerminalWorld.ResolveDemolitionOpponentBuy 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 · FreightTerminalWorld.ResolveDemolitionAttacker (cognitive 18) · ×1
  • FreightTerminalWorld.ResolveDemolitionAttacker (cognitive 18) csharp/FreightTerminalWorld.Demolition.Device.cs:473 — FreightTerminalWorld.ResolveDemolitionAttacker has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateHarborLocks (cognitive 18) · ×1
  • FreightTerminalWorld.ValidateHarborLocks (cognitive 18) csharp/FreightTerminalWorld.Demolition.HarborLocks.Diagnostics.cs:8 — FreightTerminalWorld.ValidateHarborLocks has cognitive complexity 18 (threshold 15). Of this number, 13 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.ApplyDemolitionOpponentMedicSpray (cognitive 18) · ×1
  • FreightTerminalWorld.ApplyDemolitionOpponentMedicSpray (cognitive 18) csharp/FreightTerminalWorld.Demolition.Network.Abilities.cs:53 — FreightTerminalWorld.ApplyDemolitionOpponentMedicSpray has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.UpdateDemolitionCombatArbitration (cognitive 18) · ×1
  • FreightTerminalWorld.UpdateDemolitionCombatArbitration (cognitive 18) csharp/FreightTerminalWorld.Demolition.Strategy.cs:921 — FreightTerminalWorld.UpdateDemolitionCombatArbitration has cognitive complexity 18 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · FreightTerminalWorld.TryHandleDemolitionAttackerMovement (cognitive 18) · ×1
  • FreightTerminalWorld.TryHandleDemolitionAttackerMovement (cognitive 18) csharp/FreightTerminalWorld.Demolition.Strategy.cs:986 — FreightTerminalWorld.TryHandleDemolitionAttackerMovement has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateExtractionAiDeployment (cognitive 18) · ×1
  • FreightTerminalWorld.ValidateExtractionAiDeployment (cognitive 18) csharp/FreightTerminalWorld.ExtractionAi.Diagnostics.cs:9 — FreightTerminalWorld.ValidateExtractionAiDeployment has cognitive complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FreightTerminalWorld.TryGetIncendiaryEscapeDirection (cognitive 18) · ×1
  • FreightTerminalWorld.TryGetIncendiaryEscapeDirection (cognitive 18) csharp/FreightTerminalWorld.Incendiary.cs:80 — FreightTerminalWorld.TryGetIncendiaryEscapeDirection has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateOperatorCarry (cognitive 18) · ×1
  • FreightTerminalWorld.ValidateOperatorCarry (cognitive 18) csharp/FreightTerminalWorld.OperatorCarry.Diagnostics.cs:94 — FreightTerminalWorld.ValidateOperatorCarry 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 · FreightTerminalWorld.CaptureOperatorCarry (cognitive 18) · ×1
  • FreightTerminalWorld.CaptureOperatorCarry (cognitive 18) csharp/FreightTerminalWorld.OperatorCarry.Diagnostics.cs:350 — FreightTerminalWorld.CaptureOperatorCarry 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 · FreightTerminalWorld.UpdateOrbitalComplexTelemetryInteraction (cognitive 18) · ×1
  • FreightTerminalWorld.UpdateOrbitalComplexTelemetryInteraction (cognitive 18) csharp/FreightTerminalWorld.OrbitalComplex.Presentation.cs:376 — FreightTerminalWorld.UpdateOrbitalComplexTelemetryInteraction has cognitive complexity 18 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateRelayStations (cognitive 18) · ×1
  • FreightTerminalWorld.ValidateRelayStations (cognitive 18) csharp/FreightTerminalWorld.RelayStations.cs:395 — FreightTerminalWorld.ValidateRelayStations has cognitive complexity 18 (threshold 15). Of this number, 15 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.BuildTowerInterior (cognitive 18) · ×1
  • FreightTerminalWorld.BuildTowerInterior (cognitive 18) csharp/FreightTerminalWorld.Residential.cs:612 — FreightTerminalWorld.BuildTowerInterior has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateNetworkEndpoint (cognitive 18) · ×1
  • FreightTerminalWorld.ValidateNetworkEndpoint (cognitive 18) csharp/FreightTerminalWorld.Squad.cs:888 — FreightTerminalWorld.ValidateNetworkEndpoint has cognitive complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.UpdateTrainingRange (cognitive 18) · ×1
  • FreightTerminalWorld.UpdateTrainingRange (cognitive 18) csharp/FreightTerminalWorld.TrainingRange.cs:410 — FreightTerminalWorld.UpdateTrainingRange has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · JianghaiOldCityValleyInspector.InspectNode (cognitive 18) · ×1
  • JianghaiOldCityValleyInspector.InspectNode (cognitive 18) csharp/JianghaiOldCityValleyInspector.cs:114 — JianghaiOldCityValleyInspector.InspectNode has cognitive complexity 18 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · SoundLab.TrimLeadingSilence (cognitive 18) · ×1
  • SoundLab.TrimLeadingSilence (cognitive 18) csharp/SoundLab.Recordings.cs:220 — SoundLab.TrimLeadingSilence has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TacticalPlayer.InspectAuthoredM4ReloadArmForDiagnostics (cognitive 18) · ×1
  • TacticalPlayer.InspectAuthoredM4ReloadArmForDiagnostics (cognitive 18) csharp/TacticalPlayer.AuthoredVisuals.cs:486 — TacticalPlayer.InspectAuthoredM4ReloadArmForDiagnostics has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TacticalPlayer.ClosestPointOnTriangle (cognitive 18) · ×1
  • TacticalPlayer.ClosestPointOnTriangle (cognitive 18) csharp/TacticalPlayer.AuthoredVisuals.cs:591 — TacticalPlayer.ClosestPointOnTriangle has cognitive complexity 18 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · TacticalPlayer.Fire (cognitive 18) · ×1
  • TacticalPlayer.Fire (cognitive 18) csharp/TacticalPlayer.cs:1997 — TacticalPlayer.Fire has cognitive complexity 18 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · LootItem.Detail (cognitive 18) · ×1
  • LootItem.Detail (cognitive 18) csharp/WeaponSystem.cs:405 — LootItem.Detail has cognitive complexity 18 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · CombatHUD.ApplyStatsPresentation (cognitive 17) · ×1
  • CombatHUD.ApplyStatsPresentation (cognitive 17) csharp/CombatHUD.Performance.cs:83 — CombatHUD.ApplyStatsPresentation has cognitive complexity 17 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · CombatHUD.ApplyMedicalPresentation (cognitive 17) · ×1
  • CombatHUD.ApplyMedicalPresentation (cognitive 17) csharp/CombatHUD.Performance.cs:256 — CombatHUD.ApplyMedicalPresentation has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CombatHUD.RefreshSquadDeployAction (cognitive 17) · ×1
  • CombatHUD.RefreshSquadDeployAction (cognitive 17) csharp/CombatHUD.Squad.cs:558 — CombatHUD.RefreshSquadDeployAction has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DemolitionArenaBuilder.BuildTideglassAuthoredCollision (cognitive 17) · ×1
  • DemolitionArenaBuilder.BuildTideglassAuthoredCollision (cognitive 17) csharp/DemolitionArenaBuilder.TideglassReactor.cs:7 — DemolitionArenaBuilder.BuildTideglassAuthoredCollision has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DemolitionArenaLayout.HasSpawnSightlineToSite (cognitive 17) · ×1
  • DemolitionArenaLayout.HasSpawnSightlineToSite (cognitive 17) csharp/DemolitionArenaLayout.cs:497 — DemolitionArenaLayout.HasSpawnSightlineToSite has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DemolitionRoutePlanner.TryPlanAuthoredAttackLane (cognitive 17) · ×1
  • DemolitionRoutePlanner.TryPlanAuthoredAttackLane (cognitive 17) csharp/DemolitionRoutePlanner.cs:211 — DemolitionRoutePlanner.TryPlanAuthoredAttackLane has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EnemyOperator.UpdateLootSearch (cognitive 17) · ×1
  • EnemyOperator.UpdateLootSearch (cognitive 17) csharp/EnemyOperator.cs:1257 — EnemyOperator.UpdateLootSearch has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.HasClearLootInteractionApproach (cognitive 17) · ×1
  • FreightTerminalWorld.HasClearLootInteractionApproach (cognitive 17) csharp/FreightTerminalWorld.cs:1702 — FreightTerminalWorld.HasClearLootInteractionApproach has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateReinforcementFlow (cognitive 17) · ×1
  • FreightTerminalWorld.ValidateReinforcementFlow (cognitive 17) csharp/FreightTerminalWorld.cs:3391 — FreightTerminalWorld.ValidateReinforcementFlow has cognitive complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateGoalPack (cognitive 17) · ×1
  • FreightTerminalWorld.ValidateGoalPack (cognitive 17) csharp/FreightTerminalWorld.cs:6810 — FreightTerminalWorld.ValidateGoalPack has cognitive complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.BazaarV2DensityReady (cognitive 17) · ×1
  • FreightTerminalWorld.BazaarV2DensityReady (cognitive 17) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.DensityDiagnostics.cs:29 — FreightTerminalWorld.BazaarV2DensityReady has cognitive complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · FreightTerminalWorld.BazaarLargestOpenDiameter (cognitive 17) · ×1
  • FreightTerminalWorld.BazaarLargestOpenDiameter (cognitive 17) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.DensityDiagnostics.cs:269 — FreightTerminalWorld.BazaarLargestOpenDiameter has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.BazaarTraversalGeometryReady (cognitive 17) · ×1
  • FreightTerminalWorld.BazaarTraversalGeometryReady (cognitive 17) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs:369 — FreightTerminalWorld.BazaarTraversalGeometryReady has cognitive complexity 17 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · FreightTerminalWorld.FinishDemolitionRound (cognitive 17) · ×1
  • FreightTerminalWorld.FinishDemolitionRound (cognitive 17) csharp/FreightTerminalWorld.Demolition.cs:986 — FreightTerminalWorld.FinishDemolitionRound has cognitive complexity 17 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · FreightTerminalWorld.TideglassDensityMeasureSiteCover (cognitive 17) · ×1
  • FreightTerminalWorld.TideglassDensityMeasureSiteCover (cognitive 17) csharp/FreightTerminalWorld.Demolition.TideglassReactor.DensityDiagnostics.cs:705 — FreightTerminalWorld.TideglassDensityMeasureSiteCover has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateProgressionFlow (cognitive 17) · ×1
  • FreightTerminalWorld.ValidateProgressionFlow (cognitive 17) csharp/FreightTerminalWorld.Economy.cs:124 — FreightTerminalWorld.ValidateProgressionFlow has cognitive complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.FindLanternCanalVisibleFloor (cognitive 17) · ×1
  • FreightTerminalWorld.FindLanternCanalVisibleFloor (cognitive 17) csharp/FreightTerminalWorld.LanternCanal.Diagnostics.cs:145 — FreightTerminalWorld.FindLanternCanalVisibleFloor has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateRefineryMap (cognitive 17) · ×1
  • FreightTerminalWorld.ValidateRefineryMap (cognitive 17) csharp/FreightTerminalWorld.Refinery.Validation.cs:15 — FreightTerminalWorld.ValidateRefineryMap has cognitive complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateResidentialStreetArt (cognitive 17) · ×1
  • FreightTerminalWorld.ValidateResidentialStreetArt (cognitive 17) csharp/FreightTerminalWorld.Residential.StreetArt.Diagnostics.cs:10 — FreightTerminalWorld.ValidateResidentialStreetArt has cognitive complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.BuildSquadSystem (cognitive 17) · ×1
  • FreightTerminalWorld.BuildSquadSystem (cognitive 17) csharp/FreightTerminalWorld.Squad.cs:116 — FreightTerminalWorld.BuildSquadSystem has cognitive complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.DeploySquad (cognitive 17) · ×1
  • FreightTerminalWorld.DeploySquad (cognitive 17) csharp/FreightTerminalWorld.Squad.cs:401 — FreightTerminalWorld.DeploySquad has cognitive complexity 17 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · FreightTerminalWorld.WarmSquadPortalWalkConnectorCache (cognitive 17) · ×1
  • FreightTerminalWorld.WarmSquadPortalWalkConnectorCache (cognitive 17) csharp/FreightTerminalWorld.Squad.Traversal.Connectors.cs:83 — FreightTerminalWorld.WarmSquadPortalWalkConnectorCache has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · IncendiaryGrenade._PhysicsProcess (cognitive 17) · ×1
  • IncendiaryGrenade._PhysicsProcess (cognitive 17) csharp/IncendiaryGrenade.cs:101 — IncendiaryGrenade._PhysicsProcess has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · InteractiveBuildingDoor.ConfigureVisuals (cognitive 17) · ×1
  • InteractiveBuildingDoor.ConfigureVisuals (cognitive 17) csharp/InteractiveBuildingDoor.cs:475 — InteractiveBuildingDoor.ConfigureVisuals has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LanternCanalCollisionBuilder.BuildFaces (cognitive 17) · ×1
  • LanternCanalCollisionBuilder.BuildFaces (cognitive 17) csharp/LanternCanalCollisionBuilder.cs:100 — LanternCanalCollisionBuilder.BuildFaces has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ResidentialAuthoredPropLibrary.PathForRoomProp (cognitive 17) · ×1
  • ResidentialAuthoredPropLibrary.PathForRoomProp (cognitive 17) csharp/ResidentialAuthoredPropLibrary.cs:26 — ResidentialAuthoredPropLibrary.PathForRoomProp has cognitive complexity 17 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · TacticalPlayer.SyncAuthoredPlatformWeapon (cognitive 17) · ×1
  • TacticalPlayer.SyncAuthoredPlatformWeapon (cognitive 17) csharp/TacticalPlayer.AuthoredVisuals.cs:1398 — TacticalPlayer.SyncAuthoredPlatformWeapon has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TacticalPlayer.InspectReloadScreenContact (cognitive 17) · ×1
  • TacticalPlayer.InspectReloadScreenContact (cognitive 17) csharp/TacticalPlayer.ReloadDiagnostics.cs:303 — TacticalPlayer.InspectReloadScreenContact has cognitive complexity 17 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · TacticalPlayer.UpdateRoleAbility (cognitive 17) · ×1
  • TacticalPlayer.UpdateRoleAbility (cognitive 17) csharp/TacticalPlayer.Squad.cs:158 — TacticalPlayer.UpdateRoleAbility has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TacticalPlayer.ShowTrainingRangeAttachmentStatus (cognitive 17) · ×1
  • TacticalPlayer.ShowTrainingRangeAttachmentStatus (cognitive 17) csharp/TacticalPlayer.TrainingRange.Attachments.cs:325 — TacticalPlayer.ShowTrainingRangeAttachmentStatus has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AuthoredFirstPersonSmgVisual.BoundsSizeInRoot (cognitive 16) · ×1
  • AuthoredFirstPersonSmgVisual.BoundsSizeInRoot (cognitive 16) csharp/CombatModelLibrary.FirstPerson.cs:46 — AuthoredFirstPersonSmgVisual.BoundsSizeInRoot has cognitive complexity 16 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · AuthoredMeleeVisual.ConfigureMaterials (cognitive 16) · ×1
  • AuthoredMeleeVisual.ConfigureMaterials (cognitive 16) csharp/CombatModelLibrary.Melee.cs:24 — AuthoredMeleeVisual.ConfigureMaterials has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DriveableVehicle.ApplyRamDamage (cognitive 16) · ×1
  • DriveableVehicle.ApplyRamDamage (cognitive 16) csharp/DriveableVehicle.cs:368 — DriveableVehicle.ApplyRamDamage has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EnemyOperator.TakeDamage (cognitive 16) · ×1
  • EnemyOperator.TakeDamage (cognitive 16) csharp/EnemyOperator.cs:2138 — EnemyOperator.TakeDamage has cognitive complexity 16 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · FreightTerminalWorld.ApplyQuality (cognitive 16) · ×1
  • FreightTerminalWorld.ApplyQuality (cognitive 16) csharp/FreightTerminalWorld.cs:3145 — FreightTerminalWorld.ApplyQuality has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.UpdateDemolitionNetworkClientLiveHud (cognitive 16) · ×1
  • FreightTerminalWorld.UpdateDemolitionNetworkClientLiveHud (cognitive 16) csharp/FreightTerminalWorld.Demolition.Network.cs:631 — FreightTerminalWorld.UpdateDemolitionNetworkClientLiveHud has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateDemolitionNetworkRoster (cognitive 16) · ×1
  • FreightTerminalWorld.ValidateDemolitionNetworkRoster (cognitive 16) csharp/FreightTerminalWorld.Demolition.Network.Roster.Diagnostics.cs:7 — FreightTerminalWorld.ValidateDemolitionNetworkRoster has cognitive complexity 16 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · FreightTerminalWorld.TideglassCollisionSilhouettesReady (cognitive 16) · ×1
  • FreightTerminalWorld.TideglassCollisionSilhouettesReady (cognitive 16) csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:796 — FreightTerminalWorld.TideglassCollisionSilhouettesReady has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.TideglassWalkwayCollisionReady (cognitive 16) · ×1
  • FreightTerminalWorld.TideglassWalkwayCollisionReady (cognitive 16) csharp/FreightTerminalWorld.Demolition.TideglassReactor.StructureDiagnostics.cs:10 — FreightTerminalWorld.TideglassWalkwayCollisionReady has cognitive complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateDeploymentUi (cognitive 16) · ×1
  • FreightTerminalWorld.ValidateDeploymentUi (cognitive 16) csharp/FreightTerminalWorld.Economy.cs:236 — FreightTerminalWorld.ValidateDeploymentUi has cognitive complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.CaptureExtractionFlight (cognitive 16) · ×1
  • FreightTerminalWorld.CaptureExtractionFlight (cognitive 16) csharp/FreightTerminalWorld.Extraction.cs:625 — FreightTerminalWorld.CaptureExtractionFlight has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.CaptureExtractionWorldState (cognitive 16) · ×1
  • FreightTerminalWorld.CaptureExtractionWorldState (cognitive 16) csharp/FreightTerminalWorld.Extraction.Network.cs:105 — FreightTerminalWorld.CaptureExtractionWorldState has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateLanternCanal (cognitive 16) · ×1
  • FreightTerminalWorld.ValidateLanternCanal (cognitive 16) csharp/FreightTerminalWorld.LanternCanal.Diagnostics.cs:38 — FreightTerminalWorld.ValidateLanternCanal has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.BuildSecureRoomProps (cognitive 16) · ×1
  • FreightTerminalWorld.BuildSecureRoomProps (cognitive 16) csharp/FreightTerminalWorld.Level.cs:725 — FreightTerminalWorld.BuildSecureRoomProps has cognitive complexity 16 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · FreightTerminalWorld.RecordRemoteMeleeSwingStart (cognitive 16) · ×1
  • FreightTerminalWorld.RecordRemoteMeleeSwingStart (cognitive 16) csharp/FreightTerminalWorld.Melee.Authority.cs:101 — FreightTerminalWorld.RecordRemoteMeleeSwingStart has cognitive complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · FreightTerminalWorld.UpdateOrbitalComplexRuntimePresentationFX (cognitive 16) · ×1
  • FreightTerminalWorld.UpdateOrbitalComplexRuntimePresentationFX (cognitive 16) csharp/FreightTerminalWorld.OrbitalComplex.Presentation.cs:323 — FreightTerminalWorld.UpdateOrbitalComplexRuntimePresentationFX has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.CapturePromotionMedia (cognitive 16) · ×1
  • FreightTerminalWorld.CapturePromotionMedia (cognitive 16) csharp/FreightTerminalWorld.PromotionCapture.cs:12 — FreightTerminalWorld.CapturePromotionMedia has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.ValidateClanHallCollision (cognitive 16) · ×1
  • FreightTerminalWorld.ValidateClanHallCollision (cognitive 16) csharp/FreightTerminalWorld.Refinery.ClanHallValidation.cs:10 — FreightTerminalWorld.ValidateClanHallCollision 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 · FreightTerminalWorld.AdvanceSquadGridCursor (cognitive 16) · ×1
  • FreightTerminalWorld.AdvanceSquadGridCursor (cognitive 16) csharp/FreightTerminalWorld.Squad.NavGrid.cs:609 — FreightTerminalWorld.AdvanceSquadGridCursor has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreightTerminalWorld.SquadNavigationDirectiveReached (cognitive 16) · ×1
  • FreightTerminalWorld.SquadNavigationDirectiveReached (cognitive 16) csharp/FreightTerminalWorld.Squad.NavGrid.cs:668 — FreightTerminalWorld.SquadNavigationDirectiveReached has cognitive complexity 16 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · JianghaiGameplayCollisionGeometry.ResolveEnterableRoom (cognitive 16) · ×1
  • JianghaiGameplayCollisionGeometry.ResolveEnterableRoom (cognitive 16) csharp/JianghaiGameplayCollisionGeometry.cs:42 — JianghaiGameplayCollisionGeometry.ResolveEnterableRoom has cognitive complexity 16 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · LanternCanalCollisionBuilder.Build (cognitive 16) · ×1
  • LanternCanalCollisionBuilder.Build (cognitive 16) csharp/LanternCanalCollisionBuilder.cs:23 — LanternCanalCollisionBuilder.Build has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MedicalWheelControl._Draw (cognitive 16) · ×1
  • MedicalWheelControl._Draw (cognitive 16) csharp/MedicalWheelControl.cs:90 — MedicalWheelControl._Draw has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · OperatorPresentationDiagnostics.CheckCombatPosture (cognitive 16) · ×1
  • OperatorPresentationDiagnostics.CheckCombatPosture (cognitive 16) csharp/OperatorPresentationDiagnostics.Coverage.cs:10 — OperatorPresentationDiagnostics.CheckCombatPosture has cognitive complexity 16 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · SoundLab.BuildWeaponShot (cognitive 16) · ×1
  • SoundLab.BuildWeaponShot (cognitive 16) csharp/SoundLab.cs:265 — SoundLab.BuildWeaponShot has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SoundLab.MeleeSwing (cognitive 16) · ×1
  • SoundLab.MeleeSwing (cognitive 16) csharp/SoundLab.cs:365 — SoundLab.MeleeSwing has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SoundLab.LoadRecordedPcmWav (cognitive 16) · ×1
  • SoundLab.LoadRecordedPcmWav (cognitive 16) csharp/SoundLab.Recordings.cs:123 — SoundLab.LoadRecordedPcmWav has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SquadMate.ConsiderRoleAbility (cognitive 16) · ×1
  • SquadMate.ConsiderRoleAbility (cognitive 16) csharp/SquadMate.cs:921 — SquadMate.ConsiderRoleAbility has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SquadMate.TryBuildNavigationVaultPath (cognitive 16) · ×1
  • SquadMate.TryBuildNavigationVaultPath (cognitive 16) csharp/SquadMate.Traversal.cs:277 — SquadMate.TryBuildNavigationVaultPath has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TacticalPlayer.UpdateCameraAndWeapon (cognitive 16) · ×1
  • TacticalPlayer.UpdateCameraAndWeapon (cognitive 16) csharp/TacticalPlayer.cs:1892 — TacticalPlayer.UpdateCameraAndWeapon has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TacticalPlayer.StartPlate (cognitive 16) · ×1
  • TacticalPlayer.StartPlate (cognitive 16) csharp/TacticalPlayer.cs:2356 — TacticalPlayer.StartPlate has cognitive complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TacticalPlayer.TryUpdateOrbitalComplexSwimming (cognitive 16) · ×1
  • TacticalPlayer.TryUpdateOrbitalComplexSwimming (cognitive 16) csharp/TacticalPlayer.OrbitalComplexSwimming.cs:29 — TacticalPlayer.TryUpdateOrbitalComplexSwimming has cognitive complexity 16 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D32 · Data Compliance (PII/GDPR) · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Edited copy of a member (113 corresponding lines) · ×1
  • Edited copy of a member (113 corresponding lines) csharp/LowPolyBuildingArtBuilder.cs:119 — csharp/LowPolyBuildingArtBuilder.cs:119-247 | csharp/LowPolyBuildingArtBuilder.cs:255-367 — These two members are one piece of code written twice and then edited apart: 113 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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, 30+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 30+ corresponding lines) csharp/DemolitionArenaLayout.BazaarCrossing.cs:718 — csharp/DemolitionArenaLayout.BazaarCrossing.cs:718-747 | csharp/DemolitionArenaLayout.HarborLocks.cs:160-189 | csharp/DemolitionArenaLayout.TideglassReactor.cs:418-447 | csharp/DemolitionArenaLayout.cs:444-487 — 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 (3 members, 12+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 12+ corresponding lines) csharp/DemolitionArenaLayout.BazaarCrossing.cs:605 — csharp/DemolitionArenaLayout.BazaarCrossing.cs:605-620 | csharp/DemolitionArenaLayout.TideglassReactor.cs:340-351 | csharp/DemolitionArenaLayout.TideglassReactor.cs:353-365 — 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.
D4 · Code Duplication · Edited copy of a member (43 corresponding lines) · ×1
  • Edited copy of a member (43 corresponding lines) csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs:227 — csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs:227-281 | csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs:286-328 — 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 (52 corresponding lines) · ×1
  • Edited copy of a member (52 corresponding lines) csharp/TacticalPlayer.Demolition.cs:22 — csharp/TacticalPlayer.Demolition.cs:22-73 | csharp/TacticalPlayer.TrainingRange.cs:33-89 — 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 copy of a member (50 corresponding lines) · ×1
  • Edited copy of a member (50 corresponding lines) csharp/FreightTerminalWorld.InteractionSelection.cs:33 — csharp/FreightTerminalWorld.InteractionSelection.cs:33-82 | csharp/FreightTerminalWorld.InteractionSelection.cs:89-138 — 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 copies of one member (3 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 7+ corresponding lines) csharp/DemolitionArenaBuilder.HarborLocks.cs:81 — csharp/DemolitionArenaBuilder.HarborLocks.cs:81-87 | csharp/DemolitionArenaBuilder.TideglassReactor.cs:104-110 | csharp/DemolitionArenaBuilder.cs:406-427 — 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.
D4 · Code Duplication · Edited copy of a member (42 corresponding lines) · ×1
  • Edited copy of a member (42 corresponding lines) csharp/DemolitionArenaLayout.BazaarCrossing.cs:196 — csharp/DemolitionArenaLayout.BazaarCrossing.cs:196-237 | csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GuardRailDiagnostics.cs:201-266 — 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 copy of a member (30 corresponding lines) · ×1
  • Edited copy of a member (30 corresponding lines) csharp/FreightTerminalWorld.Demolition.TideglassReactor.Capture.cs:409 — csharp/FreightTerminalWorld.Demolition.TideglassReactor.Capture.cs:409-446 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:1254-1283 — 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.
D4 · Code Duplication · Edited copy of a member (37 corresponding lines) · ×1
  • Edited copy of a member (37 corresponding lines) csharp/DemolitionArenaLayout.cs:673 — csharp/DemolitionArenaLayout.cs:673-709 | csharp/RefineryExtractionMapBuilder.cs:308-357 — 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 copy of a member (35 corresponding lines) · ×1
  • Edited copy of a member (35 corresponding lines) csharp/DemolitionArenaDressingBuilder.cs:32 — csharp/DemolitionArenaDressingBuilder.cs:32-73 | csharp/FreightTerminalArtDressingBuilder.cs:26-60 — 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 copies of one member (5 members, 15+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 15+ corresponding lines) csharp/SoundLab.cs:642 — csharp/SoundLab.cs:642-656 | csharp/SoundLab.cs:659-674 | csharp/SoundLab.cs:678-692 | csharp/SoundLab.cs:695-709 | csharp/SoundLab.cs:712-727 — 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 copy of a member (23 corresponding lines) · ×1
  • Edited copy of a member (23 corresponding lines) csharp/SquadNetwork.cs:63 — csharp/SquadNetwork.cs:63-92 | csharp/SquadNetwork.cs:95-117 — 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.
D4 · Code Duplication · Edited copy of a member (26 corresponding lines) · ×1
  • Edited copy of a member (26 corresponding lines) csharp/GradedLootPickup.cs:242 — csharp/GradedLootPickup.cs:242-282 | csharp/ResidentialSupplyCache.cs:473-498 — 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.
D4 · Code Duplication · Edited copies of one member (4 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 7+ corresponding lines) csharp/DemolitionArenaLayout.BazaarCrossing.cs:559 — csharp/DemolitionArenaLayout.BazaarCrossing.cs:559-566 | csharp/DemolitionArenaLayout.TideglassReactor.cs:306-312 | csharp/DemolitionArenaLayout.TideglassReactor.cs:314-320 | csharp/DemolitionArenaLayout.TideglassReactor.cs:322-328 — 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 copy of a member (39 corresponding lines) · ×1
  • Edited copy of a member (39 corresponding lines) csharp/FreightTerminalWorld.Squad.Navigation.cs:1303 — csharp/FreightTerminalWorld.Squad.Navigation.cs:1303-1355 | csharp/FreightTerminalWorld.Squad.Navigation.cs:1360-1398 — 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, 24+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 24+ corresponding lines) csharp/FlashbangGrenade.cs:105 — csharp/FlashbangGrenade.cs:105-128 | csharp/IncendiaryGrenade.cs:60-83 | csharp/SmokeGrenade.cs:41-65 — 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 (3 members, 21+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 21+ corresponding lines) csharp/ExtractionMaps/OrbitalComplex/OrbitalComplexWorldAssembler.cs:731 — csharp/ExtractionMaps/OrbitalComplex/OrbitalComplexWorldAssembler.cs:731-755 | csharp/ExtractionMaps/OrbitalComplex/OrbitalComplexWorldAssembler.cs:761-781 | csharp/FreightIndustrialInteriorBuilder.cs:241-262 — 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, 23+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 23+ corresponding lines) csharp/CombatModelLibrary.FirstPerson.cs:454 — csharp/CombatModelLibrary.FirstPerson.cs:454-476 | csharp/CombatModelLibrary.cs:2155-2180 | csharp/CombatModelLibrary.cs:2186-2211 | csharp/CombatModelLibrary.cs:2247-2272 — 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 (3 members, 15+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 15+ corresponding lines) csharp/FragGrenade.cs:85 — csharp/FragGrenade.cs:85-99 | csharp/IncendiaryGrenade.cs:157-174 | csharp/SmokeGrenade.cs:122-136 — 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 · Edited copies of one member (3 members, 4+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 4+ corresponding lines) csharp/DemolitionArenaLayout.HarborLocks.cs:102 — csharp/DemolitionArenaLayout.HarborLocks.cs:102-106 | csharp/DemolitionArenaLayout.HarborLocks.cs:108-112 | csharp/DemolitionArenaLayout.HarborLocks.cs:114-117 — 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 · Edited copies of one member (4 members, 21+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 21+ corresponding lines) csharp/FreightTerminalWorld.Interdistrict.cs:541 — csharp/FreightTerminalWorld.Interdistrict.cs:541-561 | csharp/FreightTerminalWorld.Residential.Density.cs:347-367 | csharp/FreightTerminalWorld.Residential.Polish.cs:89-118 | csharp/ResidentialRelayStation.cs:466-486 — 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 (4 members, 10+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 10+ corresponding lines) csharp/DemolitionArenaLayout.cs:826 — csharp/DemolitionArenaLayout.cs:826-835 | csharp/DemolitionObjectiveChannelCoordinator.cs:225-234 | csharp/MissionDirector.cs:465-474 | csharp/TacticalPlayer.TrainingRange.Attachments.cs:314-323 — 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 · Edited copies of one member (3 members, 6+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 6+ corresponding lines) csharp/FreightTerminalWorld.OpticsCapture.cs:33 — csharp/FreightTerminalWorld.OpticsCapture.cs:33-38 | csharp/FreightTerminalWorld.Squad.Traversal.Diagnostics.cs:495-500 | csharp/FreightTerminalWorld.cs:6993-6998 — 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.
D4 · Code Duplication · Duplicated block (53–62 lines × 2) · ×1
  • Duplicated block (53–62 lines × 2) csharp/FreightTerminalWorld.Refinery.Gameplay.cs:64 — csharp/FreightTerminalWorld.Refinery.Gameplay.cs:64-116 | csharp/FreightTerminalWorld.cs:1194-1255 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (36 lines × 2) · ×1
  • Duplicated block (36 lines × 2) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GlassDiagnostics.cs:677 — csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GlassDiagnostics.cs:677-712 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:23-58 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GlassDiagnostics.cs:677` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those 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 (30–34 lines × 2) · ×1
  • Duplicated block (30–34 lines × 2) csharp/EnemyOperator.VehicleCombat.cs:85 — csharp/EnemyOperator.VehicleCombat.cs:85-118 | csharp/EnemyOperator.cs:2069-2098 — before extracting anything, compare `csharp/EnemyOperator.VehicleCombat.cs` and `csharp/EnemyOperator.cs` as WHOLE FILES: this scan already matched 4 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. 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 `csharp/EnemyOperator.VehicleCombat.cs:85` 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 (10–33 lines × 6) · ×1
  • Duplicated block (10–33 lines × 6) csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:844 — csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:844-853 | csharp/FreightTerminalWorld.Demolition.EnemyResponse.Diagnostics.cs:598-630 | csharp/FreightTerminalWorld.Economy.cs:349-360 | csharp/FreightTerminalWorld.QuickSlots.Diagnostics.cs:459-491 | csharp/FreightTerminalWorld.Refinery.Doors.Diagnostics.cs:295-306 | csharp/FreightTerminalWorld.cs:4386-4417 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code 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 (31 lines × 3) · ×1
  • Duplicated block (31 lines × 3) csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs:29 — csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs:29-59 | csharp/FreightTerminalWorld.Squad.GlassRescue.Diagnostics.cs:27-57 | csharp/FreightTerminalWorld.Squad.IndoorRevive.Diagnostics.cs:45-75 — before extracting anything, compare `csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs` and `csharp/FreightTerminalWorld.Squad.GlassRescue.Diagnostics.cs` as WHOLE FILES: this scan already matched 6 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 `csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.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 (15–32 lines × 2) · ×1
  • Duplicated block (15–32 lines × 2) csharp/FreightTerminalWorld.Extraction.Survivors.Diagnostics.cs:267 — csharp/FreightTerminalWorld.Extraction.Survivors.Diagnostics.cs:267-298 | csharp/FreightTerminalWorld.Squad.Traversal.Diagnostics.cs:400-414 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/FreightTerminalWorld.Extraction.Survivors.Diagnostics.cs:267` 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 (29–30 lines × 2) · ×1
  • Duplicated block (29–30 lines × 2) csharp/FreightTerminalWorld.Refinery.CollisionDiagnostics.cs:43 — csharp/FreightTerminalWorld.Refinery.CollisionDiagnostics.cs:43-71 | csharp/FreightTerminalWorld.Refinery.Validation.cs:117-146 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (29 lines × 2) · ×1
  • Duplicated block (29 lines × 2) csharp/JianghaiEnterableCollisionShellBuilder.cs:347 — csharp/JianghaiEnterableCollisionShellBuilder.cs:347-375 | csharp/JianghaiGameplayCollisionBuilder.cs:418-446 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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.
D4 · Code Duplication · Duplicated block (26 lines × 2) · ×1
  • Duplicated block (26 lines × 2) csharp/GrenadeVisualFactory.cs:64 — csharp/GrenadeVisualFactory.cs:64-89 | csharp/GrenadeVisualFactory.cs:110-135 — 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 (27–28 lines × 2) · ×1
  • Duplicated block (27–28 lines × 2) csharp/ExtractionMaps/OrbitalComplex/OrbitalComplexWorldAssembler.cs:699 — csharp/ExtractionMaps/OrbitalComplex/OrbitalComplexWorldAssembler.cs:699-726 | csharp/JianghaiClanHallGateContract.cs:240-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. 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 (23–28 lines × 2) · ×1
  • Duplicated block (23–28 lines × 2) csharp/FreightTerminalWorld.Refinery.EnterableCollisionValidation.cs:126 — csharp/FreightTerminalWorld.Refinery.EnterableCollisionValidation.cs:126-148 | csharp/FreightTerminalWorld.Refinery.EnterableCollisionValidation.cs:161-188 — 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 `csharp/FreightTerminalWorld.Refinery.EnterableCollisionValidation.cs:126` 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 (24–26 lines × 2) · ×1
  • Duplicated block (24–26 lines × 2) csharp/CombatHUD.LootActions.cs:41 — csharp/CombatHUD.LootActions.cs:41-64 | csharp/CombatHUD.LootActions.cs:80-105 — 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 (23–25 lines × 2) · ×1
  • Duplicated block (23–25 lines × 2) csharp/CombatModelLibrary.cs:2523 — csharp/CombatModelLibrary.cs:2523-2545 | csharp/FreightTerminalWorld.AkModelDiagnostics.cs:247-271 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `meshInstances` to `int TriangleCount) CountGeometry( IEnumerable<MeshInstance3D>` in one and `int TriangleCount) CountAk47Geometry( IEnumerable<MeshInstance3D>` 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 (23–24 lines × 2) · ×1
  • Duplicated block (23–24 lines × 2) csharp/FreightTerminalWorld.Residential.StreetArt.Diagnostics.cs:442 — csharp/FreightTerminalWorld.Residential.StreetArt.Diagnostics.cs:442-464 | csharp/ResidentialStreetArtBuilder.cs:354-377 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/FreightTerminalWorld.Residential.StreetArt.Diagnostics.cs:442` it does not close everything it opens, so those 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–23 lines × 2) · ×1
  • Duplicated block (19–23 lines × 2) csharp/DemolitionStrategyPlanner.cs:466 — csharp/DemolitionStrategyPlanner.cs:466-484 | csharp/DemolitionStrategyPlanner.cs:600-622 — 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 `csharp/DemolitionStrategyPlanner.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.
D4 · Code Duplication · Duplicated block (22–23 lines × 2) · ×1
  • Duplicated block (22–23 lines × 2) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Capture.cs:53 — csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Capture.cs:53-75 | csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:440-461 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (20–22 lines × 3) · ×1
  • Duplicated block (20–22 lines × 3) csharp/EnemyOperator.VehicleCombat.cs:102 — csharp/EnemyOperator.VehicleCombat.cs:102-121 | csharp/EnemyOperator.cs:1942-1961 | csharp/EnemyOperator.cs:2029-2050 — before extracting anything, compare `csharp/EnemyOperator.VehicleCombat.cs` and `csharp/EnemyOperator.cs` as WHOLE FILES: this scan already matched 4 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. 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 `csharp/EnemyOperator.VehicleCombat.cs:102` it begins part-way through the construct above it, so those 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–22 lines × 3) · ×1
  • Duplicated block (18–22 lines × 3) csharp/FreightTerminalWorld.CrowdPerformance.Diagnostics.cs:22 — csharp/FreightTerminalWorld.CrowdPerformance.Diagnostics.cs:22-39 | csharp/FreightTerminalWorld.HudPerformance.Diagnostics.cs:16-33 | csharp/FreightTerminalWorld.Squad.Performance.Diagnostics.cs:88-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 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `csharp/FreightTerminalWorld.CrowdPerformance.Diagnostics.cs:22` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code 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–21 lines × 3) · ×1
  • Duplicated block (20–21 lines × 3) csharp/FreightTerminalWorld.Refinery.CollisionDiagnostics.cs:46 — csharp/FreightTerminalWorld.Refinery.CollisionDiagnostics.cs:46-65 | csharp/FreightTerminalWorld.Refinery.LoadingDiagnostics.cs:117-136 | csharp/FreightTerminalWorld.Refinery.Validation.cs:120-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 all 3 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 (12–20 lines × 5) · ×1
  • Duplicated block (12–20 lines × 5) csharp/FreightTerminalWorld.ResidentialStairs.Diagnostics.cs:23 — csharp/FreightTerminalWorld.ResidentialStairs.Diagnostics.cs:23-39 | csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs:35-54 | csharp/FreightTerminalWorld.Squad.GlassRescue.Diagnostics.cs:33-52 | csharp/FreightTerminalWorld.Squad.IndoorRevive.Diagnostics.cs:51-70 | csharp/FreightTerminalWorld.Squad.Traversal.Diagnostics.cs:86-97 — before extracting anything, compare `csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs` and `csharp/FreightTerminalWorld.Squad.GlassRescue.Diagnostics.cs` as WHOLE FILES: this scan already matched 6 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 `csharp/FreightTerminalWorld.ResidentialStairs.Diagnostics.cs:23` 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, `csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs:55` calls `foreach`, `Where` and `csharp/FreightTerminalWorld.ResidentialStairs.Diagnostics.cs:41` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting 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 lines × 3) · ×1
  • Duplicated block (19 lines × 3) csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Capture.cs:47 — csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Capture.cs:47-65 | csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:434-452 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.Capture.cs:20-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 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, `csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:432` calls `ApplyDemolitionLighting` and `csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Capture.cs:45` 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–19 lines × 2) · ×1
  • Duplicated block (17–19 lines × 2) csharp/LowPolyBuildingArtBuilder.Architecture.cs:131 — csharp/LowPolyBuildingArtBuilder.Architecture.cs:131-147 | csharp/LowPolyBuildingArtBuilder.Architecture.cs:272-290 — 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 `csharp/LowPolyBuildingArtBuilder.Architecture.cs:131` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code 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 × 5) · ×1
  • Duplicated block (17–18 lines × 5) csharp/DemolitionArenaDressingBuilder.cs:300 — csharp/DemolitionArenaDressingBuilder.cs:300-316 | csharp/FreightTerminalArtDressingBuilder.cs:103-119 | csharp/ResidentialAuthoredPropLibrary.cs:285-302 | csharp/ResidentialStreetArtBuilder.cs:402-418 | csharp/ResidentialTowerArtBuilder.cs:239-255 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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.
D4 · Code Duplication · Duplicated block (14–18 lines × 4) · ×1
  • Duplicated block (14–18 lines × 4) csharp/EnemyOperator.VehicleCombat.cs:81 — csharp/EnemyOperator.VehicleCombat.cs:81-95 | csharp/EnemyOperator.cs:1904-1921 | csharp/EnemyOperator.cs:2005-2018 | csharp/EnemyOperator.cs:2065-2078 — before extracting anything, compare `csharp/EnemyOperator.VehicleCombat.cs` and `csharp/EnemyOperator.cs` as WHOLE FILES: this scan already matched 4 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. 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 `csharp/EnemyOperator.cs:1904` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code 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 × 2) · ×1
  • Duplicated block (17–18 lines × 2) csharp/ExtractionMaps/OrbitalComplex/OrbitalComplexWorldAssembler.cs:761 — csharp/ExtractionMaps/OrbitalComplex/OrbitalComplexWorldAssembler.cs:761-777 | csharp/FreightIndustrialInteriorBuilder.cs:241-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. Read the line range as the matched WINDOW rather than a finished unit: at `csharp/ExtractionMaps/OrbitalComplex/OrbitalComplexWorldAssembler.cs:761` it does not close everything it opens, so those 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) · ×1
  • Duplicated block (16–17 lines × 2) csharp/FreightTerminalWorld.Demolition.cs:962 — csharp/FreightTerminalWorld.Demolition.cs:962-977 | csharp/FreightTerminalWorld.IndustrialInteriors.Diagnostics.cs:290-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 `csharp/FreightTerminalWorld.Demolition.cs:962` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code 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–17 lines × 2) · ×1
  • Duplicated block (15–17 lines × 2) csharp/OperatorPresentationDiagnostics.cs:87 — csharp/OperatorPresentationDiagnostics.cs:87-103 | csharp/OperatorPresentationDiagnostics.cs:241-255 — 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 `csharp/OperatorPresentationDiagnostics.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.
D4 · Code Duplication · Duplicated block (9–17 lines × 2) · ×1
  • Duplicated block (9–17 lines × 2) csharp/WeaponSystem.cs:826 — csharp/WeaponSystem.cs:826-842 | csharp/WeaponSystem.cs:891-899 — 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 `csharp/WeaponSystem.cs:826` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those 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 (12–16 lines × 4) · ×1
  • Duplicated block (12–16 lines × 4) csharp/TacticalPlayer.Demolition.cs:163 — csharp/TacticalPlayer.Demolition.cs:163-174 | csharp/TacticalPlayer.Demolition.cs:194-209 | csharp/TacticalPlayer.Demolition.cs:229-244 | csharp/TacticalPlayer.cs:2888-2899 — 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 `csharp/TacticalPlayer.Demolition.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.
D4 · Code Duplication · Duplicated block (15–16 lines × 3) · ×1
  • Duplicated block (15–16 lines × 3) csharp/FreightTerminalWorld.Demolition.cs:963 — csharp/FreightTerminalWorld.Demolition.cs:963-977 | csharp/FreightTerminalWorld.ExtractionSpawns.Diagnostics.cs:62-77 | csharp/FreightTerminalWorld.IndustrialInteriors.Diagnostics.cs:291-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 all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `csharp/FreightTerminalWorld.Demolition.cs:963` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code 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–16 lines × 2) · ×1
  • Duplicated block (14–16 lines × 2) csharp/FreightTerminalWorld.Residential.cs:1850 — csharp/FreightTerminalWorld.Residential.cs:1850-1863 | csharp/FreightTerminalWorld.cs:6058-6073 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (10–16 lines × 2) · ×1
  • Duplicated block (10–16 lines × 2) csharp/TrainingRangeArmoryView.Catalog.cs:31 — csharp/TrainingRangeArmoryView.Catalog.cs:31-46 | csharp/TrainingRangeSetupView.cs:555-564 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (15 lines × 3) · ×1
  • Duplicated block (15 lines × 3) csharp/FreightTerminalWorld.Residential.Diversity.Diagnostics.cs:11 — csharp/FreightTerminalWorld.Residential.Diversity.Diagnostics.cs:11-25 | csharp/FreightTerminalWorld.Residential.cs:2765-2779 | csharp/FreightTerminalWorld.Residential.cs:2908-2922 — 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.
D4 · Code Duplication · Duplicated block (12–15 lines × 2) · ×1
  • Duplicated block (12–15 lines × 2) csharp/FreightTerminalWorld.CombatModels.cs:521 — csharp/FreightTerminalWorld.CombatModels.cs:521-532 | csharp/FreightTerminalWorld.OpticsCapture.cs:10-24 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/FreightTerminalWorld.CombatModels.cs:521` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code 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–15 lines × 2) · ×1
  • Duplicated block (14–15 lines × 2) csharp/FreightTerminalWorld.Demolition.TideglassReactor.DensityDiagnostics.cs:160 — csharp/FreightTerminalWorld.Demolition.TideglassReactor.DensityDiagnostics.cs:160-173 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.Diagnostics.cs:424-438 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/FreightTerminalWorld.Demolition.TideglassReactor.Diagnostics.cs:424` 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 (13–14 lines × 9) · ×1
  • Duplicated block (13–14 lines × 9) csharp/FreightTerminalWorld.AircraftBehavior.Diagnostics.cs:66 — csharp/FreightTerminalWorld.AircraftBehavior.Diagnostics.cs:66-78 | csharp/FreightTerminalWorld.Extraction.Survivors.Diagnostics.cs:11-23 | csharp/FreightTerminalWorld.Extraction.Survivors.Diagnostics.cs:24-36 | csharp/FreightTerminalWorld.PauseDiagnostics.cs:21-34 | csharp/FreightTerminalWorld.Residential.cs:2064-2076 | csharp/FreightTerminalWorld.Squad.IndoorRevive.Diagnostics.cs:12-24 | csharp/FreightTerminalWorld.Squad.Sustainment.Diagnostics.cs:12-24 | csharp/FreightTerminalWorld.Squad.Traversal.Diagnostics.cs:42-54 | csharp/FreightTerminalWorld.Squad.cs:3935-3947 — 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.
D4 · Code Duplication · Duplicated block (13 lines × 5) · ×1
  • Duplicated block (13 lines × 5) csharp/FreightTerminalWorld.Residential.Diversity.Diagnostics.cs:11 — csharp/FreightTerminalWorld.Residential.Diversity.Diagnostics.cs:11-23 | csharp/FreightTerminalWorld.Residential.StreetArt.Diagnostics.cs:183-195 | csharp/FreightTerminalWorld.Residential.cs:2765-2777 | csharp/FreightTerminalWorld.Residential.cs:2825-2837 | csharp/FreightTerminalWorld.Residential.cs:2908-2920 — 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.
D4 · Code Duplication · Duplicated block (13 lines × 10) · ×1
  • Duplicated block (13 lines × 10) csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Diagnostics.cs:358 — csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Diagnostics.cs:358-370 | csharp/FreightTerminalWorld.AircraftBehavior.Diagnostics.cs:65-77 | csharp/FreightTerminalWorld.Extraction.Survivors.Diagnostics.cs:11-23 | csharp/FreightTerminalWorld.Extraction.Survivors.Diagnostics.cs:24-36 | csharp/FreightTerminalWorld.PauseDiagnostics.cs:20-33 | csharp/FreightTerminalWorld.Residential.cs:2063-2075 | csharp/FreightTerminalWorld.Squad.cs:3934-3946 | csharp/FreightTerminalWorld.Squad.IndoorRevive.Diagnostics.cs:12-24 | csharp/FreightTerminalWorld.Squad.Sustainment.Diagnostics.cs:12-24 | csharp/FreightTerminalWorld.Squad.Traversal.Diagnostics.cs:41-53 — 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.
D4 · Code Duplication · Duplicated block (11–13 lines × 2) · ×1
  • Duplicated block (11–13 lines × 2) csharp/EnemyOperator.VehicleCombat.cs:67 — csharp/EnemyOperator.VehicleCombat.cs:67-77 | csharp/EnemyOperator.cs:1984-1996 — before extracting anything, compare `csharp/EnemyOperator.VehicleCombat.cs` and `csharp/EnemyOperator.cs` as WHOLE FILES: this scan already matched 4 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. 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 `csharp/EnemyOperator.VehicleCombat.cs:67` 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 (10–12 lines × 3) · ×1
  • Duplicated block (10–12 lines × 3) csharp/CombatModelLibrary.Optics.cs:195 — csharp/CombatModelLibrary.Optics.cs:195-206 | csharp/CombatModelLibrary.cs:2530-2539 | csharp/FreightTerminalWorld.AkModelDiagnostics.cs:254-265 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/CombatModelLibrary.Optics.cs:195` 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 lines × 4) · ×1
  • Duplicated block (10 lines × 4) csharp/FreightTerminalWorld.Demolition.HarborLocks.Diagnostics.cs:259 — csharp/FreightTerminalWorld.Demolition.HarborLocks.Diagnostics.cs:259-268 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.AssetDiagnostics.cs:347-356 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:1073-1082 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.StructureDiagnostics.cs:220-229 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/FreightTerminalWorld.Demolition.HarborLocks.Diagnostics.cs:259` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those 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–11 lines × 2) · ×1
  • Duplicated block (6–11 lines × 2) csharp/FreightTerminalWorld.FieldUsePresentation.Diagnostics.cs:14 — csharp/FreightTerminalWorld.FieldUsePresentation.Diagnostics.cs:14-24 | csharp/FreightTerminalWorld.Survival.cs:545-550 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (8–9 lines × 9) · ×1
  • Duplicated block (8–9 lines × 9) csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs:94 — csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs:94-102 | csharp/FreightTerminalWorld.Squad.GlassRescue.Diagnostics.cs:91-99 | csharp/FreightTerminalWorld.Squad.Spectator.cs:482-489 | csharp/FreightTerminalWorld.Squad.cs:3854-3861 | csharp/FreightTerminalWorld.Squad.cs:3906-3913 | csharp/FreightTerminalWorld.Squad.cs:4017-4024 | csharp/FreightTerminalWorld.Squad.cs:4192-4200 | csharp/FreightTerminalWorld.Squad.cs:4284-4292 | csharp/FreightTerminalWorld.Squad.cs:4346-4353 — before extracting anything, compare `csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs` and `csharp/FreightTerminalWorld.Squad.GlassRescue.Diagnostics.cs` as WHOLE FILES: this scan already matched 6 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 (9 lines × 5) · ×1
  • Duplicated block (9 lines × 5) csharp/CombatModelLibrary.FirstPerson.cs:75 — csharp/CombatModelLibrary.FirstPerson.cs:75-83 | csharp/CombatModelLibrary.Melee.cs:136-144 | csharp/CombatModelLibrary.cs:2561-2569 | csharp/JianghaiOldCitySceneLoader.cs:678-686 | csharp/JianghaiOldCityValleyInspector.cs:497-505 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/CombatModelLibrary.FirstPerson.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 (4–9 lines × 3) · ×1
  • Duplicated block (4–9 lines × 3) csharp/DemolitionArenaLayout.cs:788 — csharp/DemolitionArenaLayout.cs:788-796 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:423-431 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:525-528 — 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.
D4 · Code Duplication · Duplicated block (7–8 lines × 2) · ×1
  • Duplicated block (7–8 lines × 2) csharp/FreightTerminalWorld.Demolition.HarborLocks.Diagnostics.cs:116 — csharp/FreightTerminalWorld.Demolition.HarborLocks.Diagnostics.cs:116-122 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.Diagnostics.cs:319-326 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (5 lines × 5) · ×1
  • Duplicated block (5 lines × 5) csharp/FreightTerminalWorld.Demolition.cs:972 — csharp/FreightTerminalWorld.Demolition.cs:972-976 | csharp/FreightTerminalWorld.ExtractionSpawns.Diagnostics.cs:72-76 | csharp/FreightTerminalWorld.IndustrialInteriors.Diagnostics.cs:301-305 | csharp/FreightTerminalWorld.Interdistrict.cs:721-725 | csharp/TacticalPlayer.Traversal.cs:377-381 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/FreightTerminalWorld.Demolition.cs:972` it does not close everything it opens, so those 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 lines × 7) · ×1
  • Duplicated block (6 lines × 7) csharp/FreightTerminalWorld.Level.cs:374 — csharp/FreightTerminalWorld.Level.cs:374-379 | csharp/FreightTerminalWorld.Level.cs:384-389 | csharp/FreightTerminalWorld.Level.cs:390-395 | csharp/FreightTerminalWorld.Level.cs:398-403 | csharp/FreightTerminalWorld.Level.cs:404-409 | csharp/FreightTerminalWorld.Level.cs:412-417 | csharp/FreightTerminalWorld.Level.cs:418-423 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (6 lines × 6) · ×1
  • Duplicated block (6 lines × 6) csharp/FreightIndustrialPalette.cs:227 — csharp/FreightIndustrialPalette.cs:227-232 | csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs:773-778 | csharp/FreightTerminalWorld.Demolition.HarborLocks.Diagnostics.cs:251-256 | csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs:1064-1069 | csharp/FreightTerminalWorld.Residential.StreetArt.Diagnostics.cs:447-452 | csharp/ResidentialStreetArtBuilder.cs:359-364 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `csharp/FreightIndustrialPalette.cs:227` it does not close everything it opens, so those 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–6 lines × 6) · ×1
  • Duplicated block (3–6 lines × 6) csharp/DriveableVehicle.cs:535 — csharp/DriveableVehicle.cs:535-543 | csharp/DriveableVehicle.cs:545-547 | csharp/DriveableVehicle.cs:548-551 | csharp/DriveableVehicle.cs:553-558 | csharp/DriveableVehicle.cs:559-565 | csharp/DriveableVehicle.cs:566-571 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code 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, `csharp/DriveableVehicle.cs:543` calls `MeshBox`, `Vector3` and `csharp/DriveableVehicle.cs:571` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting 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–5 lines × 3) · ×1
  • Duplicated block (2–5 lines × 3) csharp/LowPolyBuildingArtBuilder.Architecture.cs:418 — csharp/LowPolyBuildingArtBuilder.Architecture.cs:418-422 | csharp/LowPolyBuildingArtBuilder.Architecture.cs:435-439 | csharp/LowPolyBuildingArtBuilder.Architecture.cs:441-442 — 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 `csharp/LowPolyBuildingArtBuilder.Architecture.cs:418` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code 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, `csharp/LowPolyBuildingArtBuilder.Architecture.cs:439` calls `Add`, `Part`, `Vector3` and `csharp/LowPolyBuildingArtBuilder.Architecture.cs:442` 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 · Near-duplicate member family (5 members, 15 shared lines) · ×1
  • Near-duplicate member family (5 members, 15 shared lines) scripts/blender/build_reloadable_gsh18.py:269 — scripts/blender/build_reloadable_gsh18.py:269-312 | scripts/blender/build_reloadable_quaternius_weapons.py:419-474 | scripts/blender/build_reloadable_quaternius_weapons.py:529-552 | scripts/blender/build_supplemental_reload_mechanisms.py:764-837 | scripts/blender/build_taradavies_ak47.py:657-686 — 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 (3 members, 50 shared lines) · ×1
  • Near-duplicate member family (3 members, 50 shared lines) REDACTED:873 — REDACTED:873-979 | scripts/blender/build_jianghai_valley_environment.py:2300-2381 | scripts/blender/export_jianghai_old_city.py:1618-1700 — These 3 members are variants of one another: a block of 50 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, 35 shared lines) · ×1
  • Near-duplicate member family (3 members, 35 shared lines) REDACTED:717 — REDACTED:717-765 | scripts/blender/build_jianghai_valley_environment.py:2089-2148 | scripts/blender/export_jianghai_old_city.py:1459-1510 — 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 pair (367 shared lines) · ×1
  • Near-duplicate member pair (367 shared lines) scripts/blender/build_jianghai_valley_environment.py:2408 — scripts/blender/build_jianghai_valley_environment.py:2408-3051 | scripts/blender/export_jianghai_old_city.py:1704-2475 — These two members are variants of one another: 367 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) scripts/blender/build_bazaar_crossing.py:7692 — scripts/blender/build_bazaar_crossing.py:7692-7795 | scripts/blender/build_bazaar_crossing.py:7799-7925 — 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 (35 shared lines) · ×1
  • Near-duplicate member pair (35 shared lines) scripts/blender/build_jianghai_valley_environment.py:1981 — scripts/blender/build_jianghai_valley_environment.py:1981-2027 | scripts/blender/export_jianghai_old_city.py:1362-1408 — 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 (29 shared lines) · ×1
  • Near-duplicate member pair (29 shared lines) scripts/blender/build_tideglass_map_assets.py:351 — scripts/blender/build_tideglass_map_assets.py:351-435 | scripts/blender/build_tideglass_map_assets.py:442-546 — These two members are variants of one another: 29 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 (94 corresponding lines) · ×1
  • Edited copy of a member (94 corresponding lines) REDACTED:773 — REDACTED:773-866 | scripts/blender/export_jianghai_old_city.py:1518-1611 — These two members are one piece of code written twice and then edited apart: 94 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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) · ×1
  • Edited copy of a member (41 corresponding lines) scripts/blender/export_jianghai_old_city.py:706 — scripts/blender/export_jianghai_old_city.py:706-748 | scripts/blender/jianghai_enterable_interior_liners.py:104-144 — 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 copy of a member (45 corresponding lines) · ×1
  • Edited copy of a member (45 corresponding lines) REDACTED:622 — REDACTED:622-666 | scripts/blender/build_jianghai_valley_environment.py:2034-2082 — 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 copies of one member (3 members, 26+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 26+ corresponding lines) scripts/blender/build_orbital_complex_underground.py:220 — scripts/blender/build_orbital_complex_underground.py:220-245 | scripts/blender/build_orbital_complex_underground.py:263-294 | scripts/blender/build_orbital_complex_underground.py:329-358 — 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 (3 members, 11+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 11+ corresponding lines) scripts/blender/build_orbital_complex.py:466 — scripts/blender/build_orbital_complex.py:466-476 | scripts/blender/build_tideglass_map_assets.py:271-285 | scripts/blender/build_trey_modular_industrial.py:1675-1689 — 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.
D4 · Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 17+ corresponding lines) scripts/blender/build_animated_reload_arms.py:2632 — scripts/blender/build_animated_reload_arms.py:2632-2652 | scripts/blender/build_djmaesen_smg45.py:454-474 | scripts/blender/build_tastytony_gsh18.py:70-86 — 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 · Edited copies of one member (3 members, 9+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 9+ corresponding lines) scripts/audio/build_opening_combat_theme.py:68 — scripts/audio/build_opening_combat_theme.py:68-76 | scripts/audio/build_opening_combat_theme.py:80-89 | scripts/audio/build_opening_combat_theme.py:93-104 — 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.
D4 · Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 14+ corresponding lines) scripts/blender/build_reloadable_quaternius_weapons.py:627 — scripts/blender/build_reloadable_quaternius_weapons.py:627-649 | scripts/blender/build_reloadable_scarl.py:225-238 | scripts/blender/build_supplemental_reload_mechanisms.py:299-312 — 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 · Edited copies of one member (8 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 7+ corresponding lines) scripts/blender/add_hy3d_palm_markers.py:50 — scripts/blender/add_hy3d_palm_markers.py:50-58 | scripts/blender/bake_hy3d_carry_pose.py:85-93 | scripts/blender/bake_hy3d_carry_pose.py:97-105 | scripts/blender/build_hy3d_operator.py:72-78 | scripts/blender/build_hy3d_operator.py:82-90 | scripts/blender/build_hy3d_operator.py:94-102 | scripts/blender/rebind_hy3d_hands.py:57-71 | scripts/blender/rebind_hy3d_hands.py:75-85 — 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 (4 members, 6+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 6+ corresponding lines) scripts/blender/add_hy3d_palm_markers.py:62 — scripts/blender/add_hy3d_palm_markers.py:62-69 | scripts/blender/bake_hy3d_carry_pose.py:574-579 | scripts/blender/build_hy3d_operator.py:341-348 | scripts/blender/rebind_hy3d_hands.py:89-98 — 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 (7 members, 3+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 3+ corresponding lines) scripts/blender/build_animated_bamen_operator.py:765 — scripts/blender/build_animated_bamen_operator.py:765-767 | scripts/blender/build_authored_optics.py:1172-1174 | scripts/blender/build_nisu_m4a1.py:1775-1778 | scripts/blender/build_reloadable_gsh18.py:980-982 | scripts/blender/build_reloadable_quaternius_weapons.py:1130-1132 | scripts/blender/build_reloadable_scarl.py:694-696 | scripts/blender/build_tide_hunter_monster.py:245-248 — These 7 members are one piece of code written 7 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 7 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (70 lines × 3) · ×1
  • Duplicated block (70 lines × 3) REDACTED:172 — REDACTED:172-241 | scripts/blender/build_jianghai_valley_environment.py:1764-1833 | scripts/blender/export_jianghai_old_city.py:1040-1109 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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.
D4 · Code Duplication · Duplicated block (69 lines × 2) · ×1
  • Duplicated block (69 lines × 2) REDACTED:798 — REDACTED:798-866 | scripts/blender/export_jianghai_old_city.py:1543-1611 — before extracting anything, compare `REDACTED` and `scripts/blender/export_jianghai_old_city.py` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 507 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 `REDACTED:798` it begins part-way through the construct above it, so those 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 (66 lines × 2) · ×1
  • Duplicated block (66 lines × 2) scripts/blender/build_jianghai_valley_environment.py:2602 — scripts/blender/build_jianghai_valley_environment.py:2602-2667 | scripts/blender/export_jianghai_old_city.py:1943-2008 — before extracting anything, compare `scripts/blender/build_jianghai_valley_environment.py` and `scripts/blender/export_jianghai_old_city.py` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 759 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 `scripts/blender/build_jianghai_valley_environment.py:2602` it begins part-way through the construct above it, so those 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) scripts/blender/build_jianghai_valley_environment.py:2465 — scripts/blender/build_jianghai_valley_environment.py:2465-2521 | scripts/blender/export_jianghai_old_city.py:1803-1859 — before extracting anything, compare `scripts/blender/build_jianghai_valley_environment.py` and `scripts/blender/export_jianghai_old_city.py` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 759 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 `scripts/blender/build_jianghai_valley_environment.py:2465` it begins part-way through the construct above it, so those 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 lines × 2) · ×1
  • Duplicated block (33 lines × 2) scripts/blender/export_jianghai_old_city.py:2157 — scripts/blender/export_jianghai_old_city.py:2157-2189 | scripts/blender/export_jianghai_old_city.py:2742-2774 — 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 `scripts/blender/export_jianghai_old_city.py:2157` it does not close everything it opens, so those 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–42 lines × 3) · ×1
  • Duplicated block (37–42 lines × 3) scripts/blender/build_jianghai_valley_environment.py:2545 — scripts/blender/build_jianghai_valley_environment.py:2545-2586 | scripts/blender/export_jianghai_old_city.py:1886-1927 | scripts/blender/export_jianghai_old_city.py:2848-2884 — before extracting anything, compare `scripts/blender/build_jianghai_valley_environment.py` and `scripts/blender/export_jianghai_old_city.py` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 759 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, `scripts/blender/build_jianghai_valley_environment.py:2544` calls `get` and `scripts/blender/export_jianghai_old_city.py:2847` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting 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–29 lines × 2) · ×1
  • Duplicated block (22–29 lines × 2) scripts/blender/build_nisu_m4a1.py:245 — scripts/blender/build_nisu_m4a1.py:245-273 | scripts/blender/build_tide_hunter_monster.py:152-173 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (23–26 lines × 2) · ×1
  • Duplicated block (23–26 lines × 2) scripts/blender/build_bazaar_crossing.py:6354 — scripts/blender/build_bazaar_crossing.py:6354-6379 | scripts/blender/build_bazaar_crossing.py:7193-7215 — 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 `scripts/blender/build_bazaar_crossing.py:6354` it begins part-way through the construct above it, so those 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) · ×1
  • Duplicated block (28 lines × 2) scripts/blender/build_reloadable_gsh18.py:236 — scripts/blender/build_reloadable_gsh18.py:236-263 | scripts/blender/build_supplemental_reload_mechanisms.py:340-367 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (22–25 lines × 3) · ×1
  • Duplicated block (22–25 lines × 3) REDACTED:744 — REDACTED:744-765 | scripts/blender/build_jianghai_valley_environment.py:2125-2148 | scripts/blender/export_jianghai_old_city.py:1486-1510 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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.
D4 · Code Duplication · Duplicated block (16–25 lines × 3) · ×1
  • Duplicated block (16–25 lines × 3) scripts/blender/build_reloadable_gsh18.py:1000 — scripts/blender/build_reloadable_gsh18.py:1000-1024 | scripts/blender/build_reloadable_quaternius_weapons.py:1150-1174 | scripts/blender/build_reloadable_scarl.py:716-731 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (22–23 lines × 3) · ×1
  • Duplicated block (22–23 lines × 3) REDACTED:531 — REDACTED:531-553 | scripts/blender/build_jianghai_valley_environment.py:1894-1916 | scripts/blender/export_jianghai_old_city.py:1272-1293 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `REDACTED:531` it begins part-way through the construct above it, so those 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 (22 lines × 3) · ×1
  • Duplicated block (22 lines × 3) REDACTED:252 — REDACTED:252-273 | scripts/blender/build_jianghai_valley_environment.py:1837-1858 | scripts/blender/export_jianghai_old_city.py:1122-1143 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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.
D4 · Code Duplication · Duplicated block (19–21 lines × 3) · ×1
  • Duplicated block (19–21 lines × 3) REDACTED:839 — REDACTED:839-857 | scripts/blender/build_jianghai_valley_environment.py:2257-2277 | scripts/blender/export_jianghai_old_city.py:1584-1602 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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.
D4 · Code Duplication · Duplicated block (21 lines × 3) · ×1
  • Duplicated block (21 lines × 3) scripts/blender/build_quaternius_buildings_pack.py:539 — scripts/blender/build_quaternius_buildings_pack.py:539-559 | scripts/blender/build_tideglass_map_assets.py:760-780 | scripts/blender/build_trey_modular_industrial.py:2367-2387 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (20 lines × 3) · ×1
  • Duplicated block (20 lines × 3) REDACTED:915 — REDACTED:915-934 | scripts/blender/build_jianghai_valley_environment.py:2316-2335 | scripts/blender/export_jianghai_old_city.py:1634-1653 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `REDACTED:915` it begins part-way through the construct above it, so those 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–19 lines × 3) · ×1
  • Duplicated block (18–19 lines × 3) scripts/blender/build_jianghai_valley_environment.py:2779 — scripts/blender/build_jianghai_valley_environment.py:2779-2796 | scripts/blender/export_jianghai_old_city.py:2147-2165 | scripts/blender/export_jianghai_old_city.py:2732-2750 — before extracting anything, compare `scripts/blender/build_jianghai_valley_environment.py` and `scripts/blender/export_jianghai_old_city.py` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 759 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 `scripts/blender/export_jianghai_old_city.py:2147` it begins part-way through the construct above it, so those 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 (16–19 lines × 3) · ×1
  • Duplicated block (16–19 lines × 3) scripts/blender/build_quaternius_buildings_pack.py:635 — scripts/blender/build_quaternius_buildings_pack.py:635-650 | scripts/blender/build_tideglass_map_assets.py:797-815 | scripts/blender/build_trey_modular_industrial.py:2397-2412 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (18 lines × 4) · ×1
  • Duplicated block (18 lines × 4) scripts/blender/build_djmaesen_smg45.py:91 — scripts/blender/build_djmaesen_smg45.py:91-108 | scripts/blender/build_djmaesen_smg45.py:165-182 | scripts/blender/build_djmaesen_smg45.py:331-348 | scripts/blender/build_first_person_arms.py:204-221 — 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.
D4 · Code Duplication · Duplicated block (14–18 lines × 2) · ×1
  • Duplicated block (14–18 lines × 2) scripts/blender/add_hy3d_palm_markers.py:236 — scripts/blender/add_hy3d_palm_markers.py:236-249 | scripts/blender/rebind_hy3d_hands.py:533-550 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `scripts/blender/add_hy3d_palm_markers.py:236` it does not close everything it opens, so those 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) · ×1
  • Duplicated block (17 lines × 3) REDACTED:562 — REDACTED:562-578 | scripts/blender/build_jianghai_valley_environment.py:1925-1941 | scripts/blender/export_jianghai_old_city.py:1302-1318 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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.
D4 · Code Duplication · Duplicated block (11–17 lines × 3) · ×1
  • Duplicated block (11–17 lines × 3) scripts/blender/build_reloadable_gsh18.py:951 — scripts/blender/build_reloadable_gsh18.py:951-967 | scripts/blender/build_reloadable_quaternius_weapons.py:1101-1117 | scripts/blender/build_reloadable_scarl.py:672-682 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (13–17 lines × 2) · ×1
  • Duplicated block (13–17 lines × 2) scripts/blender/build_reloadable_gsh18.py:319 — scripts/blender/build_reloadable_gsh18.py:319-331 | scripts/blender/build_reloadable_quaternius_weapons.py:627-643 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `scripts/blender/build_reloadable_gsh18.py: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. 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 (6–16 lines × 6) · ×1
  • Duplicated block (6–16 lines × 6) scripts/blender/add_hy3d_palm_markers.py:247 — scripts/blender/add_hy3d_palm_markers.py:247-262 | scripts/blender/author_hy3d_preview_stand.py:175-180 | scripts/blender/author_hy3d_rifle_carry.py:177-182 | scripts/blender/bake_hy3d_carry_pose.py:621-636 | scripts/blender/rebind_hy3d_hands.py:548-563 | scripts/blender/repair_magpie_right_hand.py:156-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 6 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `scripts/blender/add_hy3d_palm_markers.py:247` it begins part-way through the construct above it, so those 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 × 3) · ×1
  • Duplicated block (16 lines × 3) REDACTED:635 — REDACTED:635-650 | scripts/blender/build_jianghai_valley_environment.py:1995-2010 | scripts/blender/build_jianghai_valley_environment.py:2048-2063 — 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. 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–16 lines × 3) · ×1
  • Duplicated block (14–16 lines × 3) scripts/blender/build_jianghai_valley_environment.py:2889 — scripts/blender/build_jianghai_valley_environment.py:2889-2904 | scripts/blender/export_jianghai_old_city.py:2297-2311 | scripts/blender/export_jianghai_old_city.py:2903-2916 — before extracting anything, compare `scripts/blender/build_jianghai_valley_environment.py` and `scripts/blender/export_jianghai_old_city.py` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 759 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 (11–15 lines × 2) · ×1
  • Duplicated block (11–15 lines × 2) scripts/blender/build_animated_reload_arms.py:496 — scripts/blender/build_animated_reload_arms.py:496-506 | scripts/blender/build_operator_hand_kits.py:663-677 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `scripts/blender/build_operator_hand_kits.py:663` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code 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 × 3) · ×1
  • Duplicated block (12–14 lines × 3) scripts/blender/build_quaternius_buildings_pack.py:494 — scripts/blender/build_quaternius_buildings_pack.py:494-507 | scripts/blender/build_tideglass_map_assets.py:327-338 | scripts/blender/build_trey_modular_industrial.py:2067-2078 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `scripts/blender/build_quaternius_buildings_pack.py:494` it begins part-way through the construct above it, so those 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–14 lines × 2) · ×1
  • Duplicated block (10–14 lines × 2) scripts/blender/build_orbital_complex.py:1297 — scripts/blender/build_orbital_complex.py:1297-1310 | scripts/blender/build_orbital_complex_underground.py:1491-1500 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (13–14 lines × 2) · ×1
  • Duplicated block (13–14 lines × 2) scripts/blender/build_taradavies_ak47.py:418 — scripts/blender/build_taradavies_ak47.py:418-431 | scripts/blender/build_taradavies_ak47.py:451-463 — 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 `scripts/blender/build_taradavies_ak47.py:418` it begins part-way through the construct above it, so those 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 × 4) · ×1
  • Duplicated block (13 lines × 4) scripts/blender/build_animated_reload_arms.py:249 — scripts/blender/build_animated_reload_arms.py:249-261 | scripts/blender/build_djmaesen_smg45.py:63-75 | scripts/blender/build_first_person_arms.py:41-53 | scripts/blender/build_operator_hand_kits.py:103-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 4 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (13 lines × 3) · ×1
  • Duplicated block (13 lines × 3) scripts/blender/sculpt_lynx_hair.py:78 — scripts/blender/sculpt_lynx_hair.py:78-90 | scripts/blender/sculpt_lynx_hair.py:265-277 | scripts/blender/sculpt_lynx_hair.py:341-353 — 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.
D4 · Code Duplication · Duplicated block (3–13 lines × 3) · ×1
  • Duplicated block (3–13 lines × 3) scripts/blender/build_bazaar_crossing.py:5996 — scripts/blender/build_bazaar_crossing.py:5996-5998 | scripts/blender/build_bazaar_crossing.py:6777-6786 | scripts/blender/build_bazaar_crossing.py:7735-7747 — 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 `scripts/blender/build_bazaar_crossing.py:7735` it begins part-way through the construct above it, so those 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–13 lines × 2) · ×1
  • Duplicated block (8–13 lines × 2) scripts/blender/build_jianghai_valley_environment.py:235 — scripts/blender/build_jianghai_valley_environment.py:235-247 | scripts/blender/build_orbital_complex.py:1508-1515 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 (10–13 lines × 2) · ×1
  • Duplicated block (10–13 lines × 2) scripts/blender/build_reloadable_gsh18.py:216 — scripts/blender/build_reloadable_gsh18.py:216-225 | scripts/blender/build_tastytony_gsh18.py:27-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 both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (12 lines × 7) · ×1
  • Duplicated block (12 lines × 7) scripts/blender/build_authored_optics.py:150 — scripts/blender/build_authored_optics.py:150-161 | scripts/blender/build_nisu_m4a1.py:133-144 | scripts/blender/build_reloadable_gsh18.py:137-148 | scripts/blender/build_reloadable_quaternius_weapons.py:223-234 | scripts/blender/build_reloadable_scarl.py:141-152 | scripts/blender/build_supplemental_reload_mechanisms.py:258-269 | tools/build_enterable_industrial_buildings.py:32-43 — 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, `scripts/blender/build_nisu_m4a1.py:147` calls `require_file`, `is_file`, `FileNotFoundError` and `scripts/blender/build_reloadable_quaternius_weapons.py: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 (12 lines × 6) · ×1
  • Duplicated block (12 lines × 6) REDACTED:533 — REDACTED:533-544 | REDACTED:564-575 | scripts/blender/build_jianghai_valley_environment.py:1896-1907 | scripts/blender/build_jianghai_valley_environment.py:1927-1938 | scripts/blender/export_jianghai_old_city.py:1273-1284 | scripts/blender/export_jianghai_old_city.py:1304-1315 — 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. 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–12 lines × 4) · ×1
  • Duplicated block (7–12 lines × 4) scripts/blender/build_authored_optics.py:1154 — scripts/blender/build_authored_optics.py:1154-1165 | scripts/blender/build_reloadable_gsh18.py:952-963 | scripts/blender/build_reloadable_quaternius_weapons.py:1102-1113 | scripts/blender/build_reloadable_scarl.py:673-679 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `scripts/blender/build_authored_optics.py:1154` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code 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 × 4) · ×1
  • Duplicated block (12 lines × 4) scripts/blender/build_operations_office_set.py:78 — scripts/blender/build_operations_office_set.py:78-89 | scripts/blender/build_quaternius_buildings_pack.py:157-168 | scripts/blender/build_tideglass_map_assets.py:123-134 | scripts/blender/build_trey_modular_industrial.py:1510-1521 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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.
D4 · Code Duplication · Duplicated block (1–12 lines × 9) · ×1
  • Duplicated block (1–12 lines × 9) scripts/blender/build_demolition_device.py:353 — scripts/blender/build_demolition_device.py:353-353 | scripts/blender/build_hy3d_operator.py:406-406 | scripts/blender/build_orbital_complex.py:466-473 | scripts/blender/build_orbital_complex.py:474-474 | scripts/blender/build_quaternius_buildings_pack.py:196-207 | scripts/blender/build_tideglass_map_assets.py:271-279 | scripts/blender/build_trey_modular_industrial.py:1675-1683 | scripts/blender/inspect_operator_bind.py:36-36 | scripts/blender/inspect_operator_bind.py:38-38 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `scripts/blender/build_quaternius_buildings_pack.py:196` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code 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 `objects` to `Iterable[bpy.types.Object]` in one and `list[bpy.types.Object]` 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, `scripts/blender/build_orbital_complex.py:473` calls `RuntimeError` and `scripts/blender/build_demolition_device.py:353` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting 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 × 4) · ×1
  • Duplicated block (11–12 lines × 4) scripts/blender/build_reloadable_gsh18.py:986 — scripts/blender/build_reloadable_gsh18.py:986-997 | scripts/blender/build_reloadable_quaternius_weapons.py:1136-1147 | scripts/blender/build_reloadable_scarl.py:700-710 | scripts/blender/build_supplemental_reload_mechanisms.py:1229-1239 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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.
D4 · Code Duplication · Duplicated block (4–12 lines × 3) · ×1
  • Duplicated block (4–12 lines × 3) REDACTED:674 — REDACTED:674-685 | scripts/blender/build_jianghai_valley_environment.py:2036-2047 | scripts/blender/export_jianghai_old_city.py:1415-1418 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code 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, `REDACTED:674` calls `cross`, `Vector`, `normalized` and `scripts/blender/export_jianghai_old_city.py:1415` 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 (11 lines × 5) · ×1
  • Duplicated block (11 lines × 5) scripts/blender/build_operations_office_set.py:80 — scripts/blender/build_operations_office_set.py:80-90 | scripts/blender/build_orbital_complex.py:246-256 | scripts/blender/build_quaternius_buildings_pack.py:159-169 | scripts/blender/build_tideglass_map_assets.py:125-135 | scripts/blender/build_trey_modular_industrial.py:1512-1522 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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, `scripts/blender/build_orbital_complex.py:243` calls `list`, `remove` and `scripts/blender/build_operations_office_set.py:79` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting 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 × 2) · ×1
  • Duplicated block (9–11 lines × 2) scripts/blender/build_reloadable_gsh18.py:323 — scripts/blender/build_reloadable_gsh18.py:323-333 | scripts/blender/build_reloadable_scarl.py:227-235 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `scripts/blender/build_reloadable_gsh18.py:323` it does not close everything it opens, so those 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 (10–11 lines × 2) · ×1
  • Duplicated block (10–11 lines × 2) scripts/blender/export_jianghai_old_city.py:2129 — scripts/blender/export_jianghai_old_city.py:2129-2139 | scripts/blender/export_jianghai_old_city.py:2715-2724 — 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 `scripts/blender/export_jianghai_old_city.py:2129` it begins part-way through the construct above it, so those 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 × 5) · ×1
  • Duplicated block (9–10 lines × 5) scripts/blender/build_reloadable_gsh18.py:287 — scripts/blender/build_reloadable_gsh18.py:287-296 | scripts/blender/build_reloadable_quaternius_weapons.py:444-453 | scripts/blender/build_reloadable_quaternius_weapons.py:537-546 | scripts/blender/build_supplemental_reload_mechanisms.py:798-807 | scripts/blender/build_taradavies_ak47.py:675-683 — 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 `scripts/blender/build_reloadable_gsh18.py: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.
D4 · Code Duplication · Duplicated block (8–10 lines × 2) · ×1
  • Duplicated block (8–10 lines × 2) scripts/blender/build_authored_optics.py:512 — scripts/blender/build_authored_optics.py:512-519 | scripts/blender/build_nisu_m4a1.py:467-476 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `scripts/blender/build_nisu_m4a1.py:467` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code 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 × 3) · ×1
  • Duplicated block (2–9 lines × 3) scripts/blender/build_bazaar_crossing.py:5987 — scripts/blender/build_bazaar_crossing.py:5987-5994 | scripts/blender/build_bazaar_crossing.py:6769-6777 | scripts/blender/build_bazaar_crossing.py:7749-7750 — 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 `scripts/blender/build_bazaar_crossing.py:5987` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code 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 × 7) · ×1
  • Duplicated block (8 lines × 7) scripts/blender/build_authored_optics.py:1300 — scripts/blender/build_authored_optics.py:1300-1307 | scripts/blender/build_demolition_device.py:472-479 | scripts/blender/build_field_use_props.py:829-836 | scripts/blender/build_melee_weapons.py:798-805 | scripts/blender/build_nisu_m4a1.py:1835-1842 | scripts/blender/build_taradavies_ak47.py:1273-1280 | scripts/blender/generate_combat_models.py:373-380 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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.
D4 · Code Duplication · Duplicated block (2–8 lines × 3) · ×1
  • Duplicated block (2–8 lines × 3) scripts/blender/build_authored_optics.py:1289 — scripts/blender/build_authored_optics.py:1289-1296 | scripts/blender/build_nisu_m4a1.py:1825-1831 | scripts/blender/generate_combat_models.py:368-369 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `scripts/blender/build_authored_optics.py:1289` it begins part-way through the construct above it, so those 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 × 3) · ×1
  • Duplicated block (6–7 lines × 3) REDACTED:724 — REDACTED:724-729 | scripts/blender/build_jianghai_valley_environment.py:2102-2108 | scripts/blender/export_jianghai_old_city.py:1466-1471 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `REDACTED:724` it begins part-way through the construct above it, so those 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–7 lines × 3) · ×1
  • Duplicated block (4–7 lines × 3) scripts/blender/build_demolition_device.py:416 — scripts/blender/build_demolition_device.py:416-422 | scripts/blender/build_field_use_props.py:750-756 | scripts/blender/build_orbital_complex.py:1746-1749 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `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 that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code 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–7 lines × 3) · ×1
  • Duplicated block (3–7 lines × 3) scripts/blender/export_jianghai_old_city.py:555 — scripts/blender/export_jianghai_old_city.py:555-561 | scripts/blender/export_jianghai_old_city.py:722-727 | scripts/blender/jianghai_enterable_interior_liners.py:113-115 — 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.
D4 · Code Duplication · Duplicated block (2–6 lines × 4) · ×1
  • Duplicated block (2–6 lines × 4) scripts/blender/build_bazaar_crossing.py:2930 — scripts/blender/build_bazaar_crossing.py:2930-2931 | scripts/blender/build_bazaar_crossing.py:2936-2937 | scripts/blender/build_bazaar_crossing.py:2946-2952 | scripts/blender/build_bazaar_crossing.py:5618-5623 — 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 `scripts/blender/build_bazaar_crossing.py:2946` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code 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 × 5) · ×1
  • Duplicated block (8 lines × 5) scripts/blender/build_animated_bamen_operator.py:186 — scripts/blender/build_animated_bamen_operator.py:186-193 | scripts/blender/build_field_use_props.py:664-671 | scripts/blender/build_melee_weapons.py:725-732 | scripts/blender/import_bamen_military_soldier.py:86-93 | scripts/blender/inspect_animated_bamen_operator.py:48-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 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, `scripts/blender/build_field_use_props.py:662` calls `calc_loop_triangles` and `scripts/blender/build_animated_bamen_operator.py:185` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting 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 × 4) · ×1
  • Duplicated block (4–5 lines × 4) scripts/blender/build_bazaar_crossing.py:1367 — scripts/blender/build_bazaar_crossing.py:1367-1370 | scripts/blender/build_bazaar_crossing.py:1580-1583 | scripts/blender/build_bazaar_crossing.py:1674-1678 | scripts/blender/build_bazaar_crossing.py:1750-1754 — 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, `scripts/blender/build_bazaar_crossing.py:1680` calls `Vector`, `normalized`, `cross` and `scripts/blender/build_bazaar_crossing.py:1756` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting 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) · ×1
  • Duplicated block (4–5 lines × 3) scripts/blender/build_trey_modular_industrial.py:2155 — scripts/blender/build_trey_modular_industrial.py:2155-2158 | scripts/blender/build_trey_modular_industrial.py:2238-2242 | scripts/blender/build_trey_modular_industrial.py:2266-2270 — 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 `scripts/blender/build_trey_modular_industrial.py:2155` it begins part-way through the construct above it, so those 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, `scripts/blender/build_trey_modular_industrial.py:2271` calls `any` and `scripts/blender/build_trey_modular_industrial.py:2158` 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.
D6 · Cohesion (LCOM4) · Low cohesion · ×1
  • Low cohesion: TrainingRangeArenaRuntime (LCOM4 4) csharp/TrainingRangeArenaRuntime.cs:13 — TrainingRangeArenaRuntime's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
X12 · Unreachable branch · Branch is unreachable · ×1
  • Branch is unreachable — its condition cannot hold here csharp/FreightTerminalWorld.Demolition.cs:185 — `mode == SquadSessionMode.Join` can never be true where it stands: the guard on line 171 (`mode == SquadSessionMode.Host`) left this block when it was true; the guard on line 181 (`mode == SquadSessionMode.Join`) left this block when it was true. No value of `mode` satisfies all of that, so the true arm of this conditional expression never runs. Reorder the tests, drop the dead branch, or fix the bound that was meant.
X30 · Support guard that admits what it rejects · Support guard that admits what it rejects · ×1
  • Support guard that admits what it rejects csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:3277 — `opponent.LossStreak == 2 && opponent.RecordRound(won: true, objectiveComplete...` can never be true: it asks `opponent.LossStreak` to equal both `2` and `0` at once. Whatever this condition guards never runs, so every value it was written to refuse passes. Join the two equalities with `||` (either value) or test the second one on the value it was meant for.
X5 · Nullable reference types · Null guard scopes only part of the work it protects · ×1
  • Null guard scopes only part of the work it protects csharp/FreightTerminalWorld.cs:4179 — This method contradicts itself about `item`: line 3978 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 4179 then dereferences `item` as `item.Id` AFTER the block has closed, where the guard no longer applies. A null `item` 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 `item` truly cannot be null by then, the guard above is misleading and should go.
Minor — 58 finding(s)
X10 · Duplicated predicate · Duplicated predicate · ×40
  • Duplicated predicate csharp/DemolitionArenaRuntime.cs:79 — `!GodotObject.IsInstanceValid(body) || body.CollisionLayer != expectedLayer || body.CollisionMask != 0` appears character-identically in 2 files — csharp/DemolitionArenaRuntime.cs, csharp/TrainingRangeArenaRuntime.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate csharp/TacticalPlayer.Melee.Clearance.cs:125 — `!IsInstanceValid(_authoredMelee?.BladeBase) || !IsInstanceValid(_authoredMelee?.BladeTip)` appears character-identically in 2 files — csharp/TacticalPlayer.Melee.Clearance.cs, csharp/TacticalPlayer.Melee.Combat.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate csharp/EnemyOperator.AuthoredVisuals.cs:210 — `!IsInstanceValid(_collider) || _collider.Shape is not CapsuleShape3D capsule` appears character-identically in 2 files — csharp/EnemyOperator.AuthoredVisuals.cs, csharp/SquadMate.AuthoredVisuals.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate csharp/FreightTerminalWorld.Demolition.HarborLocks.Diagnostics.cs:46 — `!IsInstanceValid(body) || !IsInstanceValid(model)` appears character-identically in 2 files — csharp/FreightTerminalWorld.Demolition.HarborLocks.Diagnostics.cs, csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate csharp/FreightTerminalWorld.Demolition.Device.cs:734 — `!IsInstanceValid(mate) || mate.IsDowned || mate.IsBodyBag` appears character-identically in 2 files — csharp/FreightTerminalWorld.Demolition.Device.cs, csharp/FreightTerminalWorld.Incendiary.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs:591 — `!IsInstanceValid(model) || !TideglassTryGetBounds(model!, null, out var minimum, out var maximum)` appears character-identically in 2 files — csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs, csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate csharp/FreightTerminalWorld.cs:2356 — `!IsInstanceValid(vehicle) || vehicle.IsDestroyed` appears character-identically in 2 files — csharp/FreightTerminalWorld.VehicleCombat.Diagnostics.cs, csharp/FreightTerminalWorld.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate csharp/SquadNetwork.Extraction.Doors.cs:13 — `!IsOnline || !IsExtractionSession || !ExtractionMatchStarted || !ExtractionWorldLaunchStarted` appears character-identically in 3 files — csharp/SquadNetwork.Extraction.Doors.cs, csharp/SquadNetwork.Extraction.Loot.cs, csharp/SquadNetwork.Extraction.World.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate csharp/SquadNetwork.Extraction.Doors.cs:28 — `!IsOnline || !IsHost || !IsExtractionSession || !ExtractionMatchStarted` appears character-identically in 3 files — csharp/SquadNetwork.Extraction.Doors.cs, csharp/SquadNetwork.Extraction.Loot.cs, csharp/SquadNetwork.Extraction.World.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate csharp/FreightTerminalWorld.Extraction.Survivors.Diagnostics.cs:117 — `!_hud.IsAiSquadCommandPresentationVisibleForDiagnostics && !_hud.AreSquadCommandControlsVisibleForDiagnostics && _hud.DownedFooterSuppressed…` appears character-identically in 2 files — csharp/FreightTerminalWorld.Extraction.Survivors.Diagnostics.cs, csharp/FreightTerminalWorld.Squad.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate csharp/FreightTerminalWorld.cs:376 — `!_interactReleaseRequired && Input.IsActionJustPressed(GameInputActions.Interact)` appears character-identically in 3 files — csharp/FreightTerminalWorld.RelayStations.cs, csharp/FreightTerminalWorld.RoofAccess.cs, csharp/FreightTerminalWorld.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs:555 — `!_player.HasMovementIntent && frames > 2` appears character-identically in 2 files — csharp/FreightTerminalWorld.Demolition.BazaarCrossing.GeometryDiagnostics.cs, csharp/FreightTerminalWorld.Demolition.TideglassReactor.GeometryDiagnostics.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs:144 — `!_player.IsDead && _player.ReviveUsed && !_localPlayerDowned` appears character-identically in 4 files — csharp/FreightTerminalWorld.Squad.DoorRescue.Diagnostics.cs, csharp/FreightTerminalWorld.Squad.GlassRescue.Diagnostics.cs, csharp/FreightTerminalWorld.Squad.IndoorRevive.Diagnostics.cs, csharp/FreightTerminalWorld.Squad.Traversal.Diagnostics.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Diagnostics.cs:61 — `!arena.Active && !arena.Root.Visible && arena.Root.ProcessMode == ProcessModeEnum.Disabled && arena.ActiveCollisionBodyCount == 0 && arena.A…` appears character-identically in 3 files — csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Diagnostics.cs, csharp/FreightTerminalWorld.Demolition.Diagnostics.cs, csharp/FreightTerminalWorld.Demolition.TideglassReactor.Diagnostics.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Diagnostics.cs:254 — `!check.OwnerKnown || !check.Route.ReachesDestination || !check.Clear` appears character-identically in 2 files — csharp/FreightTerminalWorld.Demolition.BazaarCrossing.Diagnostics.cs, csharp/FreightTerminalWorld.Demolition.Diagnostics.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate csharp/FreightTerminalWorld.Demolition.Diagnostics.cs:277 — `!layout.HasSpawnSightlineToSite(0) && !layout.HasSpawnSightlineToSite(1)` appears character-identically in 2 files — csharp/FreightTerminalWorld.Demolition.Diagnostics.cs, csharp/FreightTerminalWorld.Demolition.TideglassReactor.Diagnostics.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate csharp/FreightTerminalWorld.Demolition.Device.cs:730 — `!mate.IsHumanProxy && !mate.IsNetworkProxy` appears character-identically in 2 files — csharp/FreightTerminalWorld.Demolition.Device.cs, csharp/FreightTerminalWorld.Squad.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate csharp/TacticalPlayer.AuthoredVisuals.cs:1377 — `EquippedWeapon.Platform == WeaponPlatform.M4A1 && IsInstanceValid(_authoredPrimaryWeapon?.Root)` appears character-identically in 2 files — csharp/TacticalPlayer.AuthoredVisuals.cs, csharp/TacticalPlayer.ReloadPresentation.ViewDiagnostics.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate csharp/LootDragControls.cs:178 — `GetThemeStylebox("panel") is StyleBoxFlat style && ColorsMatch(style.BorderColor, expected)` appears character-identically in 2 files — csharp/LootDragControls.cs, csharp/LootWeaponSlotView.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate csharp/TacticalPlayer.cs:105 — `HasFireablePrimary && _primaryWeaponSlot is not null` appears character-identically in 2 files — csharp/TacticalPlayer.WeaponSlots.cs, csharp/TacticalPlayer.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Interactions.cs:135 — `Input.IsActionPressed(GameInputActions.Interact) && !_interactReleaseRequired` appears character-identically in 6 files — csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Interactions.cs, csharp/ExtractionMaps/OrbitalComplex/FreightTerminalWorld.OrbitalComplex.Undertow.cs, csharp/FreightTerminalWorld.Demolition.cs, csharp/FreightTerminalWorld.OrbitalComplex.Presentation.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate csharp/FreightTerminalWorld.cs:2859 — `IsExtractionNetworkMatch && _squadNetwork.IsHost` appears character-identically in 3 files — csharp/FreightTerminalWorld.Refinery.Doors.cs, csharp/FreightTerminalWorld.Squad.cs, csharp/FreightTerminalWorld.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate csharp/SquadNetwork.cs:259 — `IsExtractionSession && ExtractionMatchStarted` appears character-identically in 2 files — csharp/SquadNetwork.Melee.cs, csharp/SquadNetwork.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate csharp/TacticalPlayer.TrainingRange.Configuration.cs:119 — `IsFirearmQuickSlotSelected && !_knifeEquipped` appears character-identically in 2 files — csharp/TacticalPlayer.TrainingRange.Configuration.cs, csharp/TacticalPlayer.TrainingRange.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate csharp/SquadNetwork.Extraction.Doors.cs:51 — `IsHost && IsExtractionSession && ExtractionMatchStarted && ExtractionWorldLaunchStarted` appears character-identically in 3 files — csharp/SquadNetwork.Extraction.Doors.cs, csharp/SquadNetwork.Extraction.Loot.cs, csharp/SquadNetwork.Extraction.World.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • + 15 more in this group — see findings.md.
X7 · Silent fallback defaults · Silent fallback default in catch · ×7
  • Silent fallback default in catch csharp/BackendClient.cs:98 — `CompleteSessionAsync` swallows `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 csharp/BackendClient.cs:131 — `CanWriteAsync` swallows `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 csharp/CombatModelLibrary.cs:2048 — `InspectM4AttachmentConfiguration` swallows every exception into `return default;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch csharp/CombatModelLibrary.IntegratedOptics.cs:203 — `InspectIntegratedScope` swallows every exception into `return default;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch csharp/CombatModelLibrary.Optics.cs:332 — `InspectAuthoredOptics` swallows every exception into `return default;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch csharp/ExtractionLootNetworkCodec.cs:40 — `DeserializeItems` swallows `JsonException` into `return new List<LootItem>();` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch csharp/TacticalPlayer.TrainingRange.Attachments.cs:245 — `SetTrainingRangeAttachment` swallows `KeyNotFoundException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
X7 · Silent fallback defaults · Silent fallback default on parse failure · ×2
  • Silent fallback default on parse failure csharp/SquadNetwork.cs:64 — `Host` returns `Error.InvalidParameter` when `TryParseHostEndpoint(address, port, out var bindIp, out var endpointPort)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
  • Silent fallback default on parse failure csharp/SquadNetwork.cs:96 — `Join` returns `Error.InvalidParameter` when `TryParseEndpoint(address, port, out var host, out var endpointPort)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
X9 · Subsumed condition operand · Subsumed condition operand · ×2
  • Subsumed condition operand csharp/FreightTerminalWorld.Residential.cs:1537 — `stepName.Contains("StairStep", StringComparison.Ordinal)` can never decide this `||` — every value satisfying `stepName.Contains("StairStep", StringComparison.Ordinal)` also satisfies `stepName.Contains("Stair", StringComparison.Ordinal)`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
  • Subsumed condition operand csharp/FreightTerminalWorld.Residential.cs:1538 — `stepName.Contains("StairLanding", StringComparison.Ordinal)` can never decide this `||` — every value satisfying `stepName.Contains("StairLanding", StringComparison.Ordinal)` also satisfies `stepName.Contains("Stair", StringComparison.Ordinal)`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
D21 · Naming Consistency · `CombatHUD` spells `HUD` where 74 names in the project spell it `Hud` · ×1
  • `CombatHUD` spells `HUD` where 74 names in the project spell it `Hud` csharp/CombatHUD.Boss.cs:5 — 74 of 75 names in project OperationSteelTide spell the token `Hud` (74 of 75; unit: names in project OperationSteelTide containing `Hud`). Peers: CombatHUD.BuildIncomingDamageHud (csharp/CombatHUD.Damage.cs:20); CombatHUD.IsDemolitionSkillHudVisible (csharp/CombatHUD.Demolition.cs:115); CombatHUD.DemolitionUtilityHudText (csharp/CombatHUD.Demolition.cs:131); CombatHUD.BuildDemolitionHud (csharp/CombatHUD.Demolition.cs:154); CombatHUD.BuildDemolitionBuyHud (csharp/CombatHUD.Demolition.cs:165). Rename to `CombatHud`. [rule N6]
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
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.
M3 · Folder & project structure · No tests/ separation · ×1
  • No tests/ separation — Tests aren't where this ecosystem separates them — a `_test.go` file beside the code it tests is the convention, and none is present.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:5 — No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 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.
X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1
  • Not all async methods take a CancellationToken — Only 3/12 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
X5 · Nullable reference types · Null-forgiving operator (`!`) suppressions override nullable warnings · ×1
  • Null-forgiving operator (`!`) suppressions override nullable warnings — ~0.9 `!` suppressions per 1k syntax nodes — 946 suppression(s) across the 1000568 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.

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-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-c31c1ebcdf35402ab35c728bd21a96fb/tree.json --exit-code 0 --source .0—
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 .3artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesdotnet—dotnet list OperationSteelTide.sln package --vulnerable --include-transitive --format json0artifacts/raw/dotnet-vulnerable.json
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 --config /opt/semgrep-rules/gdpr.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 .1artifacts/raw/semgrep-gdpr.json
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 Dependenciesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-88347678b76c4848b69d4280e1b7ad260artifacts/raw/osv-scanner.json

Run 01a1e78a-1fc2-7cc6-8cc6-193b1dbab15c · 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