Public report of MuaCherish/Minecraft_By_Unity, 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, 12:10 UTC · Survey ID cd_82a4e1bae3bf411f9040f630d253109c

MuaCherish/Minecraft_By_Unity

Measured 17 November 2026, 12:09 UTC, at code version f0cf3ff

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

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

CAI score 43.0out of 100 Weak
CriticalWeakAdequateStrongExemplary

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A medium codebase: 24,996 lines of product code in 2 projects, tests not counted · Estimated rebuild effort: about 0.6 person-years · Weakest lens: Production Readiness, 25.7

Findings by how serious they are

0 critical 179 serious 43 minor

10 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, 12:09 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 ▸

35of 35 dimensions measured by tools.
215of 222 findings point to an exact file and line, so you can open each one in the code. The other 7 concern the repository as a whole, such as missing documentation.
35dimensions across 4 lenses, read from 24,996 lines of product code in 2 projects.
Chapters

Executive summary

MuaCherish/Minecraft_By_Unity falls short of our standard for production because we found no working pipeline that builds or tests changes to the code and no automated security scanning of the code, its secrets or its dependencies. It scores 43.0 out of 100 and is rated Weak, and it has no critical findings.

Production Readiness, at 25.7, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 9.1 points. Adding an automated build and test pipeline would lift Production Readiness itself, worth about 11.6 points. Raising Production Readiness to 70 would lift the score to about 58.8.

Most of the 179 serious findings are in Code Health.

The product code is 24,996 lines, about €83,000 to rebuild.

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Production Readiness 25.7 · counts for 50%Maturity 48.3 · counts for 27%Code Health 59.1 · counts for 15%Security and Compliance 100.0 · counts for 8%

If Production Readiness rose from 25.7 to 70, the lowest score rated Strong, the score would rise from 43.0 to about 58.8.

Code composition: what the lines of code are
Business logic 62%Supporting code 36%Tests 2%
Rebuild cost: about €83,000 · Estimate
Cost to rebuild€27,000 to €140,000, for 444 to 1,459 hours of work, about 0.6 person-years for 1 to 2 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 43. 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.
SizeMedium: 24,996 lines of product code, of which 21% is declarations and boilerplate, 16% straight logic and 63% logic with branches
Comment linesThe estimate prices 19,720 lines. Comment lines count towards the size of 24,996 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 1 No ADRs found finding(s) in ADR Quality — start with ProjectVersion.txt.
Raises the score by about 9.1 points · Low effort · ADR Quality
2
Add a CI workflow that builds and runs the test suite on every push/PR.
Raises the score by about 11.6 points · Medium effort · CI/CD gates
3
Record your significant design decisions.
Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Raises the score by about 6.1 points · Medium effort · Architecture documentation

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 €83,000 to build again, about 0.6 person-years of work. Its weakest lens is Production Readiness, at 25.7 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 9.1 points for low effort, because it clears the 1 ADR Quality 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 6.0 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 5% to 11% on every change. The history of the code shows how much it changes: about 8,880 lines over the last 90 days, which is about 36,013 lines a year. At that pace, the extra work comes to an estimated 4.4 to 26.3 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture — module dependency graph

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

arch Assembly-CSharp Assembly-CSharp Assembly-CSharp-Editor Assembly-CSharp-Editor Assembly-CSharp-Editor->Assembly-CSharp

At a glance — Code Health · 59.1 · Adequate · gated by D2, X5 ·

At a glance — Architecture · — · — ·

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

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

At a glance — Security · 100.0 · Exemplary ·

Roadmap

Top priorities: Add a CI workflow that builds and runs the test suite on every push/PR; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with ProjectVersion.txt; 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.

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

Do thisHelpsEffortDimension
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with ProjectVersion.txt.+9.1 ptsLowADR Quality
Add a CI workflow that builds and runs the test suite on every push/PR.+11.6 ptsMediumCI/CD gates
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.+6.1 ptsMediumArchitecture documentation
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.+5.1 ptsMediumRelease Hygiene
Put every file in a nullable-enabled context — `#nullable enable` at its top, or commit a project file with <Nullable>enable</Nullable> — and resolve warnings rather than suppressing with `!`.+3.2 ptsMediumNullable reference types
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.+2.6 ptsMediumDocumentation (README)
Resolve the 1 finding(s) in Folder & project structure.+1.1 ptsMediumFolder & project structure
Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.+0.7 ptsMediumIncompleteness & stubs

File quality

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

FileScoreBandWorst signal
Assets/_MC_/Cscript/Old/Chunk.cs5.5MixedCyclomatic Complexity: Chunk.CreateData (cyclomatic 51)
Assets/_MC_/Cscript/Component/MC_Component_Physics.cs5.7MixedCyclomatic Complexity: MC_Component_Physics.GetTargetBlockHeightAndWidth (cyclomatic 27)
Assets/_MC_/Cscript/UI/Old/CanvasManager.cs5.7MixedCyclomatic Complexity: CanvasManager.UpdateCanvasState (cyclomatic 21)
Assets/_MC_/Cscript/Old/Player.cs7.0MixedCyclomatic Complexity: Player.GetPlayerInputs (cyclomatic 85)
Assets/_MC_/Cscript/Debug/Debug_Navigate.cs7.0MixedCognitive Complexity: Debug_Navigate.OnDrawGizmos (cognitive 29)
Assets/_MC_/Cscript/Service/MC_Service_World.cs7.0MixedCyclomatic Complexity: MC_Service_World.AddtoCreateChunks (cyclomatic 19)
Assets/_MC_/Cscript/Service/MC_Service_Time.cs7.0MixedCyclomatic Complexity: MC_Service_Time.FromGameTimeToUpdateAll_Smooth (cyclomatic 18)
Assets/_MC_/Cscript/Component/MC_Component_AI.cs7.1MixedGod Classes: TooManyMethods: MC_Component_AI
Assets/_MC_/Cscript/AuxiliaryScripts/ScrollRectWithNoDrag.cs7.1MixedCyclomatic Complexity: MyCancelDragScrollRect.LateUpdate (cyclomatic 18)
Assets/_MC_/Cscript/UI/Old/BackPackManager.cs7.1MixedCyclomatic Complexity: BackPackManager.ChangeBlockInHand (cyclomatic 17)
Assets/Resources/Prefeb/Entity/TNT/Entity_TNT.cs7.1MixedCognitive Complexity: Entity_TNT.OnEndEntity (cognitive 20)
Assets/_MC_/Cscript/UI/Old/CommandManager.cs7.4MixedCyclomatic Complexity: CommandManager.CheckCommand (cyclomatic 54)
Assets/_MC_/Cscript/Static/MC_Static_Noise.cs7.4MixedCognitive Complexity: MC_Static_Noise.GetTotalNoiseHigh_Biome (cognitive 28)
Assets/_MC_/Cscript/Old/OldMusicManager.cs7.4MixedCognitive Complexity: OldMusicManager.Fade_FallInto_Water (cognitive 26)
Assets/_MC_/Cscript/Static/MC_Static_BlocksFunction.cs7.4MixedCognitive Complexity: MC_Static_BlocksFunction.Boom (cognitive 23)
Assets/_MC_/Cscript/UI/Old/LifeManager.cs7.4MixedCognitive Complexity: LifeManager.UpdatePlayerFood (cognitive 17)
Assets/_MC_/Scene/TestScene/test csharp/TerrainTest_Voxel.cs7.4MixedCode Duplication: Edited copy of a member (15 corresponding lines)
Assets/_MC_/Cscript/Static/MC_Static_Raycast.cs7.8MixedCyclomatic Complexity: MC_Static_Raycast.RayCast (cyclomatic 19)
Assets/Homebrew/DecorateFoldout/Editor/EditorOverride.cs7.8MixedCyclomatic Complexity: EditorOverride.OnInspectorGUI (cyclomatic 17)
Assets/_MC_/Cscript/Service/MC_Service_MeshBuilder.cs7.8MixedCode Duplication: Edited copy of a member (25 corresponding lines)

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

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

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

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

Could not be resolved — 10

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

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, 215 of 222 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 01a1e969-99a0-7be7-ba82-2ae605eebb5e.

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

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the test suite could not be built/run in-image (commonly external-service dependencies — a database, a broker — we won't provision). To have it measured, make the suite runnable without them. For context only, test code is ≈ 2% of production LoC (422 test / 24,996 production) — a rough proxy, NOT a coverage measurement, so it is excluded from the score. You can widen what we reach: optional: make the suite runnable without a database, broker or other service we do not provision, and real coverage is measured on the next scan.
  • D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: /usr/share/dotnet/sdk/10.0.400/NuGet.targets(521,5): error MSB3202: The project file "Assembly-CSharp-Editor.csproj" was not found. [Minecraft_By_Unity.slnx].
  • 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. Not scored — this repository declares its packages to Unity's package manager (UPM), in Packages/manifest.json and packages-lock.json, not to NuGet, so the .NET licence collector this dimension reads had no manifest to resolve. UPM package licences are not graded because the Unity package registry (packages.unity.com) publishes no licence field for the releases it serves and a packages-lock.json records none either — there is no licence metadata in this ecosystem to read, and packages resolved from a git URL have no registry behind them at all. A limit of what UPM publishes, NOT a finding that this repository's licences are compliant: this dimension asserts nothing about this repository's licensing in either direction.
  • 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-contributor repository — bus factor is not applicable (1 contributor(s) across 121 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository DOES commit C#/VB source and a project or solution file, so the conventions are there to read and the load still produced nothing. That is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and runs on C# constantly, and the remedy is to inspect the restore, the SDK band and the target resolution — not to build anything.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `Assets/Resources/Items/ItemScripts/Item_DataBase.cs`, `Assets/Resources/Prefeb/Entity/DropBlock/DropBlock.cs`, `Assets/_MC_/Cscript/Class/MC_Class_Chunk.cs`, `Assets/_MC_/Cscript/Class/MC_Class_Entity.cs`, `Assets/_MC_/Cscript/Class/MC_Class_Time.cs`, … (+11 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
  • 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. 746 further occurrence(s) are not listed individually; the score already reflects all 786.
  • P5 DR & Backup — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found. Whether there is anything here to recover could NOT be determined: persistence is detected from deployment/container manifests and from dependency manifests, and neither was readable by this pass, so a data store this code opens directly — a file, an embedded database — would not be visible to it. The blindness is this analyzer's, not a finding that the repository holds no data. You can widen what we reach: keep the deployment/container manifest or a dependency manifest in this repository — or a link to the ops repo that holds the DR evidence — so the persistence probe has something to read.
  • P8 Schema migrations — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads EF Core usage in C# and the schema tooling its file scan recognises only, and no .NET project was loaded, and this repository's language is not one the scan models, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X10 Duplicated predicate — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's C# was parsed (it ships no .sln or .csproj, so it was read as syntax-only projects), but this check proves its findings from resolved symbols and a reference-free parse resolves none. It abstained rather than report a clean bill it could not earn. That is a gap in this analyzer's reach into build-less repositories — not a finding that the repository is free of what this check looks for.
  • Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for one or more projects, so those projects were analysed with framework references only: every check keyed on a third-party type saw an error type there and reported nothing. Findings on those projects are a lower bound; run `dotnet restore` on them and rescan.

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

Limitations & what we did not check

We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

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

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

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

22 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Player.GetPlayerInputs at 85. A further 1 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 TerrainTest_Voxel.isValueChange at 17 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: Assets/_MC_/Scene/TestScene/test csharp/TerrainTest_Voxel.cs (TerrainTest_Voxel.isValueChange at 17). 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.

Player.GetPlayerInputs (cyclomatic 85)Assets/_MC_/Cscript/Old/Player.cs:717
CommandManager.CheckCommand (cyclomatic 54)Assets/_MC_/Cscript/UI/Old/CommandManager.cs:37
Chunk.CreateData (cyclomatic 51)Assets/_MC_/Cscript/Old/Chunk.cs:279
Chunk.CreateData_Forest (cyclomatic 50)Assets/_MC_/Cscript/Old/Chunk.cs:1182
Chunk.CreateData_Marsh (cyclomatic 45)Assets/_MC_/Cscript/Old/Chunk.cs:877

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

What to do

  1. Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with Player.GetPlayerInputs (cyclomatic 85). — Refactoring it lifts Cyclomatic Complexity from 6.4 to about 6.8/10.

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

D2 · Cognitive Complexity3.0 / 10Weak✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

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

51 method(s) exceeded the cognitive complexity threshold of 15; the worst was Chunk.CreateData at 129.

Chunk.GetBlock (cognitive 27) · ×2Assets/_MC_/Cscript/Old/Chunk.cs:3679
Chunk.CreateData (cognitive 129)Assets/_MC_/Cscript/Old/Chunk.cs:279
Player.GetPlayerInputs (cognitive 129)Assets/_MC_/Cscript/Old/Player.cs:717
CommandManager.CheckCommand (cognitive 127)Assets/_MC_/Cscript/UI/Old/CommandManager.cs:37
Chunk.CreateData_Forest (cognitive 119)Assets/_MC_/Cscript/Old/Chunk.cs:1182

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

What to do

  1. Bring the 8 bodies over 60 down to 60 or less in Cognitive Complexity — start with Chunk.CreateData (cognitive 129), Player.GetPlayerInputs (cognitive 129), CommandManager.CheckCommand (cognitive 127). — 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 8 together lifts Cognitive Complexity from 3.0 to about 4.8/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

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

D3 · God Classes8.9 / 10Strong✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

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

12 god class(es) detected.

TooManyMethods: Chunk · ×5Assets/_MC_/Cscript/Old/Chunk.cs
FileTooLong: Old/Chunk.cs · ×4Assets/_MC_/Cscript/Old/Chunk.cs
MethodTooLong: Chunk.UpdateMeshData · ×3Assets/_MC_/Cscript/Old/Chunk.cs:2403

What to do

  1. Resolve the 5 TooManyMethods finding(s) in God Classes — start with Chunk.cs, Player.cs, MC_Component_AI.cs. — One of this dimension's main actionable groups (5 warning-level).
  2. Resolve the 4 FileTooLong finding(s) in God Classes — start with Chunk.cs, Player.cs, MC_Component_AI.cs. — One of this dimension's main actionable groups (4 warning-level).
  3. Resolve the 3 MethodTooLong finding(s) in God Classes — start with Chunk.cs, CommandManager.cs, Player.cs. — One of this dimension's main actionable groups (3 warning-level).

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

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

51 duplicated block group(s) detected. 12.4 % of the production lines (3,095 of 24,996) are in a reported copy. A further 26 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 4 of the 77 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) · ×4Assets/_MC_/Cscript/Old/Chunk.cs:3418
Edited copy of a member (22 corresponding lines) · ×2Assets/_MC_/Cscript/Component/MC_Component_AI.cs:243
Edited copy of a member (21 corresponding lines) · ×2Assets/Resources/Prefeb/Entity/TNT/Entity_TNT.cs:163
Duplicated block (12 lines × 2) · ×2Assets/Resources/Prefeb/Entity/TNT/Entity_TNT.cs:277
Duplicated block (11 lines × 2) · ×2Assets/_MC_/Cscript/Old/Chunk.cs:82

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

What to do

  1. Resolve the 4 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with Chunk.cs, MC_Service_World.cs, MC_Static_Noise.cs. — One of this dimension's main actionable groups (4 warning-level).
  2. Resolve the 2 Edited copy of a member (22 corresponding lines) finding(s) in Code Duplication — start with MC_Component_AI.cs (2). — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 2 Edited copy of a member (21 corresponding lines) finding(s) in Code Duplication — start with Entity_TNT.cs, GenVoronoi.cs. — One of this dimension's main actionable groups (2 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

2 production modules (Unity), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations, and main-sequence distance (abstractness) is not computed for these modules yet.

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D6 · Cohesion (LCOM4)9.8 / 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.8 / 10 · rule-coverage 100% · ceiling Verified

1 of 55 classes have LCOM4 above 3.

Low cohesion: MC_Component_Physics (LCOM4 5)Assets/_MC_/Cscript/Component/MC_Component_Physics.cs:10

What to do

  1. Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with MC_Component_Physics.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.

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 Hotspots10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

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

No architecture decision records were found.

No ADRs foundProjectSettings/ProjectVersion.txt:1

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality — start with ProjectVersion.txt. — One of this dimension's main actionable groups (1 recommendation-level).

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

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

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

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

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

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

semgrep found no security issues. semgrep hit a parse error in 17 file(s) — `Assets/Resources/Items/ItemScripts/Item_DataBase.cs` (line 19), `Assets/Resources/Prefeb/Entity/DropBlock/DropBlock.cs` (line 395, line 396, line 397), `Assets/_MC_/Cscript/Class/MC_Class_Chunk.cs` (line 21, line 22, line 23, …), `Assets/_MC_/Cscript/Class/MC_Class_Entity.cs` (lines 165–169), `Assets/_MC_/Cscript/Class/MC_Class_Time.cs` (lines 7–31), … (+12 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 5 of those file(s) — `Assets/_MC_/Cscript/Component/MC_Component_Physics.cs`, `Assets/_MC_/Cscript/Old/Player.cs`, `Assets/_MC_/Cscript/UI/Old/BackPackManager.cs`, `Assets/_MC_/Cscript/UI/Old/CanvasManager.cs`, `Assets/_MC_/Scene/TestScene/test csharp/TerrainTest_Voxel.cs` — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything.

✓ On the Gold path — maintain.

Detailed fixes: d29_recommendation.md.

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

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

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

Every significant source file has living knowledge — recently and meaningfully worked. Counted over 63 of the 109 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.3 / 10Stronggated by 3 serious 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.3 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: MC_Service_Saving.cs↔CommandManager.cs 70%; Player.cs↔MC_Service_Saving.cs 68%; MC_Service_Saving.cs↔BackPackManager.cs 62%

Change coupling: Chunk.cs ↔ Player.cs · ×2Assets/_MC_/Cscript/Old/Chunk.cs:1
Change-coupling hub: MC_Service_Saving.cs → Player.cs, BackPackManager.cs, CanvasManager.cs, CommandManager.csAssets/_MC_/Cscript/Service/MC_Service_Saving.cs

What to do

  1. Resolve the 2 Change coupling finding(s) in Change Coupling — start with Chunk.cs, CanvasManager.cs. — One of this dimension's main actionable groups (2 warning-level).
  2. Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with MC_Service_Saving.cs. — One of this dimension's main actionable groups (1 warning-level).

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

Frontend & cross-cutting dimensions

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

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

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

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

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

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

  • `MC_Runtime_DynamicData` keeps one instance of itself in the static `_instance`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_game_state, _game_mode; e.g. `_game_state` at line 18). — Assets/_MC_/Cscript/RuntimeGameData/MC_Runtime_DynamicData.cs:5
  • `MC_Runtime_StaticData` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_instance; e.g. `_instance` at line 11). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Assets/_MC_/Cscript/RuntimeGameData/MC_Runtime_StaticData.cs:8
  • `MC_Static_BlocksFunction` 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 (managerhub; e.g. `managerhub` at line 20). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Assets/_MC_/Cscript/Static/MC_Static_BlocksFunction.cs:10
  • `MC_Static_Chunk` 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 (_managerhub, _Service_world; e.g. `_managerhub` at line 33). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Assets/_MC_/Cscript/Static/MC_Static_Chunk.cs:7
  • `MC_Static_Navigation` 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 (_Service_World; e.g. `_Service_World` at line 21). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Assets/_MC_/Cscript/Static/MC_Static_Navigation.cs:6
  • `MC_Chunk_Caculator` 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 (Chunk_Renderer, AllChunks; e.g. `Chunk_Renderer` at line 251). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Assets/_MC_/Scene/TestScene/ChunkMeshDataCaculator/MC_Chunk_Caculator.cs:110
  • `GenChunk` 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 (_chunkParent, _mainCamera, _gameManager, AllChunks; e.g. `_chunkParent` at line 20). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Assets/_MC_/Scene/TestScene/NoiseMapTest/GenChunk.cs:8

What to do

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

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 & stubs7.6 / 10Strong✓ Tool-verified

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

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

  • The first 2 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently. (×2) — Assets/Homebrew/DecorateFoldout/Editor/EditorOverride.cs:57, Assets/_MC_/Cscript/UI/Old/BackPackManager.cs:146
  • The `if` and its `else` contain the same 1 statement, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body. — Assets/_MC_/Cscript/Static/MC_Static_Name.cs:43
  • The first 1 statement of the `if` and of the `else` are identical, so it runs on both paths regardless of the condition. Lift it above the `if` — leaving it duplicated inside makes the branches read as though they handled this differently. (×2) — Assets/_MC_/Cscript/UI/Old/LifeManager.cs:185, Assets/_MC_/Cscript/UI/Old/LifeManager.cs:315
  • A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×35) — Assets/Resources/Prefeb/Entity/DropBlock/DropBlock.cs:33, Assets/Resources/Prefeb/Entity/DropBlock/DropBlock.cs:34, Assets/Resources/Prefeb/Entity/DropBlock/DropBlock.cs:44, …

What to do

  • Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)6.0 / 10Adequate✓ 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

  • Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project 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.

  • Nothing in the layout marks which files are the product and which are its tooling: no production source was found set apart in a directory of its own.
P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

  • No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.

What to do

  • Add a CI workflow that builds and runs the test suite on every push/PR.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

  • No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets — this tree has no MSBuild project file, so CodeQL's csharp pack (which traces a build) and NuGet security analyzers (which are referenced from a project) have nothing to attach to — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

What to do

  • Run what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets — this tree has no MSBuild project file, so CodeQL's csharp pack (which traces a build) and NuGet security analyzers (which are referenced from a project) have nothing to attach to — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene5.0 / 10Adequate✓ 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.

  • No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

What to do

  • Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

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

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

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.

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.

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 handling10.0 / 10Exemplary○ Nothing flagged

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.

X4 · Structured logging10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. 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 `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.

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

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

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

  • 0/109 C# file(s) are in a nullable-enabled context. This repository commits no project file, so nothing sets <Nullable>enable</Nullable> for it: a file is enabled only by its own `#nullable enable`, by a Unity `csc.rsp` with `-nullable:enable` for its assembly, or as a file-based app (`#:` directives) whose `#:property Nullable` does not turn it off. NRTs catch a whole class of null-deref bugs at compile time.

What to do

  • Put every file in a nullable-enabled context — `#nullable enable` at its top, or commit a project file with <Nullable>enable</Nullable> — and resolve warnings rather than suppressing with `!`.

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health59.1Adequate — gated by D2, X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity48.3Weak — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness25.7Weak — gated by P1, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security100.0ExemplaryStrongest area.
Unscored — 1 check(s) recorded observations but carry no score

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

  • X7 Silent fallback defaults — 1 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 — 76 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — no DI registrations detected
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
  • C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • 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 — ~422 lines of test code exist on disk but weren't loaded from the analyzed solution (excluded from the .sln, or co-located/using a test attribute not loaded here), so test quality couldn't be assessed. Include the tests in the analyzed solution to enable this check.
  • D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
  • D12 Dependency Hygiene — Dependency hygiene not measured
  • D14 License Compliance — UPM package licences not graded — the Unity registry publishes no licence metadata
  • D16 Bus Factor — single-contributor repository — bus factor is not applicable
  • D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
  • D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution; this repository's .NET projects are all F# (.fsproj), which the C#/VB workspace does not load, so the dimension does not apply.
  • D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
  • D21 Naming Consistency — N/A — no production declarations to compare.
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D23 Boundary Type-Coupling — Production source is present (.cs) but bounded contexts are resolved over the C#/VB project set, which exposed none, so context scope could not be assessed. Not scored — this is a gap in the analyzer, not a verdict about this repository. Declaring the codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed — see the recommendation on this dimension for where. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — No hand-written C#, Visual Basic, TypeScript or JavaScript source; comment value is not applicable here.
  • D25 ADR Conformance — no ADRs to check
  • D26 Project Cohesion — Project cohesion is assessed over the .NET project set; this target exposed no projects, so project size and spread could not be assessed. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
  • D27 Navigability — No calls could be sampled, so navigability was not assessed — tracing effort is measured over resolved call sites and this target exposed none. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
  • D30 Dependency Vulnerabilities — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — 16 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Unity UPM manifest (Packages/manifest.json or a package's package.json) — not scanned yet).
  • D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured
  • DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable (this repository commits no MSBuild project, so its C# was read as syntax-only projects — a handler marked ONLY by an interface from a package is not visible without a build)
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • M4 Documentation accuracy — Not applicable: the 2 current-state document(s) make no claim of a kind M4 checks.
  • P12 CI test-gate honesty — no CI workflow found
  • P2 Observability — Observability was not assessed: this check reads a source model that does not carry this repository's product — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of a logging idiom this check recognises is NOT evidence that this repo lacks structured logging (it may log through its own ecosystem's logger). This is a gap in the analyzer, not a finding about this repository.
  • P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
  • P8 Schema migrations — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
  • 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.
  • PF3 Async & latency hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
  • S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
  • X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X10 Duplicated predicate — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X2 Cancellation propagation — no async method does work a token could cancel
  • X20 Mistyped argument guard — 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 — This check needs a compiled C# program and this repository commits no project file to compile, so only its syntax could be read. That is a limit of the analyzer, not a finding about your code.
  • X25 Inert configuration knob — 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
  • X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X30 Support guard that admits what it rejects — 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
  • 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.

Serious — 179 finding(s)
AX2 · Stateful singletons · Process-global static state · ×6
  • Process-global static state: MC_Runtime_StaticData Assets/_MC_/Cscript/RuntimeGameData/MC_Runtime_StaticData.cs:8 — `MC_Runtime_StaticData` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_instance; e.g. `_instance` at line 11). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: MC_Static_BlocksFunction Assets/_MC_/Cscript/Static/MC_Static_BlocksFunction.cs:10 — `MC_Static_BlocksFunction` 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 (managerhub; e.g. `managerhub` at line 20). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: MC_Static_Chunk Assets/_MC_/Cscript/Static/MC_Static_Chunk.cs:7 — `MC_Static_Chunk` 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 (_managerhub, _Service_world; e.g. `_managerhub` at line 33). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: MC_Static_Navigation Assets/_MC_/Cscript/Static/MC_Static_Navigation.cs:6 — `MC_Static_Navigation` 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 (_Service_World; e.g. `_Service_World` at line 21). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: MC_Chunk_Caculator Assets/_MC_/Scene/TestScene/ChunkMeshDataCaculator/MC_Chunk_Caculator.cs:110 — `MC_Chunk_Caculator` 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 (Chunk_Renderer, AllChunks; e.g. `Chunk_Renderer` at line 251). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: GenChunk Assets/_MC_/Scene/TestScene/NoiseMapTest/GenChunk.cs:8 — `GenChunk` 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 (_chunkParent, _mainCamera, _gameManager, AllChunks; e.g. `_chunkParent` at line 20). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
D3 · God Classes · TooManyMethods · ×5
  • TooManyMethods: Chunk Assets/_MC_/Cscript/Old/Chunk.cs — TooManyMethods — 1388 significant lines (blank, comment-only and punctuation-only lines excluded), 58 methods. The bar is 30 methods; this is 28 over it, 1.93× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Player Assets/_MC_/Cscript/Old/Player.cs — TooManyMethods — 778 significant lines (blank, comment-only and punctuation-only lines excluded), 51 methods. The bar is 30 methods; this is 21 over it, 1.70× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: MC_Component_AI Assets/_MC_/Cscript/Component/MC_Component_AI.cs — TooManyMethods — 530 significant lines (blank, comment-only and punctuation-only lines excluded), 44 methods. 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: MC_Service_World Assets/_MC_/Cscript/Service/MC_Service_World.cs — TooManyMethods — 422 significant lines (blank, comment-only and punctuation-only lines excluded), 42 methods. The bar is 30 methods; this is 12 over it, 1.40× 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: MyCancelDragScrollRect Assets/_MC_/Cscript/AuxiliaryScripts/ScrollRectWithNoDrag.cs — TooManyMethods — 510 significant lines (blank, comment-only and punctuation-only lines excluded), 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D3 · God Classes · FileTooLong · ×4
  • FileTooLong: Old/Chunk.cs Assets/_MC_/Cscript/Old/Chunk.cs — FileTooLong — 1397 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 897 over it, 2.79× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Old/Player.cs Assets/_MC_/Cscript/Old/Player.cs — FileTooLong — 784 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 284 over it, 1.57× 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: Component/MC_Component_AI.cs Assets/_MC_/Cscript/Component/MC_Component_AI.cs — FileTooLong — 537 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 37 over it, 1.07× 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: AuxiliaryScripts/ScrollRectWithNoDrag.cs Assets/_MC_/Cscript/AuxiliaryScripts/ScrollRectWithNoDrag.cs — FileTooLong — 518 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 18 over it, 1.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.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×4
  • Duplicated block (5 lines × 2) Assets/_MC_/Cscript/Old/Chunk.cs:3418 — Assets/_MC_/Cscript/Old/Chunk.cs:3418-3422 | Assets/_MC_/Cscript/Old/Chunk.cs:3963-3967 — both copies are in the same file, so extract the 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 `Assets/_MC_/Cscript/Old/Chunk.cs:3418` it does not close everything it opens, so those exact lines 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) Assets/_MC_/Cscript/Service/MC_Service_World.cs:185 — Assets/_MC_/Cscript/Service/MC_Service_World.cs:185-189 | Assets/_MC_/Cscript/Service/MC_Service_World.cs:285-292 — both copies are in the same file, so extract the 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 `Assets/_MC_/Cscript/Service/MC_Service_World.cs:185` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Assets/_MC_/Cscript/Service/MC_Service_World.cs:192` calls `Lerp` and `Assets/_MC_/Cscript/Service/MC_Service_World.cs:294` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared 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) Assets/_MC_/Cscript/Static/MC_Static_Noise.cs:182 — Assets/_MC_/Cscript/Static/MC_Static_Noise.cs:182-186 | Assets/_MC_/Cscript/Static/MC_Static_Noise.cs:197-201 — both copies are in the same file, so extract the 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) Assets/_MC_/Scene/TestScene/test csharp/TerrainTest_Voxel.cs:156 — Assets/_MC_/Scene/TestScene/test csharp/TerrainTest_Voxel.cs:156-160 | Assets/_MC_/Scene/TestScene/test csharp/TerrainTest_Voxel.cs:172-178 — both copies are in the same file, so extract the 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 `Assets/_MC_/Scene/TestScene/test csharp/TerrainTest_Voxel.cs:156` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
IC1 · Incompleteness & stubs · Both branches open with the same statements · ×4
  • Both branches open with the same statements — the condition does not decide them Assets/Homebrew/DecorateFoldout/Editor/EditorOverride.cs:57 — The first 2 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
  • Both branches open with the same statements — the condition does not decide them Assets/_MC_/Cscript/UI/Old/BackPackManager.cs:146 — The first 2 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
  • Both branches open with the same statements — the condition does not decide them Assets/_MC_/Cscript/UI/Old/LifeManager.cs:185 — The first 1 statement of the `if` and of the `else` are identical, so it runs on both paths regardless of the condition. Lift it above the `if` — leaving it duplicated inside makes the branches read as though they handled this differently.
  • Both branches open with the same statements — the condition does not decide them Assets/_MC_/Cscript/UI/Old/LifeManager.cs:315 — The first 1 statement of the `if` and of the `else` are identical, so it runs on both paths regardless of the condition. Lift it above the `if` — leaving it duplicated inside makes the branches read as though they handled this differently.
D3 · God Classes · MethodTooLong · ×3
  • MethodTooLong: Chunk.UpdateMeshData Assets/_MC_/Cscript/Old/Chunk.cs:2403 — MethodTooLong — UpdateMeshData runs 216 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 116 over it, 2.16× 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: CommandManager.CheckCommand Assets/_MC_/Cscript/UI/Old/CommandManager.cs:37 — MethodTooLong — CheckCommand runs 203 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 103 over it, 2.03× 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: Player.GetPlayerInputs Assets/_MC_/Cscript/Old/Player.cs:717 — MethodTooLong — GetPlayerInputs runs 174 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 74 over it, 1.74× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D2 · Cognitive Complexity · Chunk.GetBlock (cognitive 27) · ×2
  • Chunk.GetBlock (cognitive 27) Assets/_MC_/Cscript/Old/Chunk.cs:3679 — Chunk.GetBlock has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: Assets/_MC_/Cscript/Old/Chunk.cs holds 14 of the 51 methods over the threshold — including the worst — and 553 of the 1137 points over it (49%), 3.7× the next-largest file (Assets/_MC_/Cscript/Old/Player.cs at 149). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
  • Chunk.GetBlock (cognitive 27) Assets/_MC_/Cscript/Old/Chunk.cs:3794 — Chunk.GetBlock has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: Assets/_MC_/Cscript/Old/Chunk.cs holds 14 of the 51 methods over the threshold — including the worst — and 553 of the 1137 points over it (49%), 3.7× the next-largest file (Assets/_MC_/Cscript/Old/Player.cs at 149). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D35 · Change Coupling · Change coupling · ×2
  • Change coupling: Chunk.cs ↔ Player.cs Assets/_MC_/Cscript/Old/Chunk.cs:1 — `Assets/_MC_/Cscript/Old/Chunk.cs` and `Assets/_MC_/Cscript/Old/Player.cs` change together 59% of the time (10 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 10 shared commits counted here, the most recent 3 are `aaac3ab2` 版本[3. 11. 10] —— 完善实体功能 [新增] 1. (at that commit the files were still `Assets/C scripts/Managers/Chunk.cs` and `Assets/C scripts/Managers/Player.cs`); `980be1d9` 版本[3. 11. 6] —— 优化碰撞 [新增] 1. 碰撞组件-完成了碰撞位置修正 (at that commit the files were still `Assets/C scripts/Managers/Chunk.cs` and `Assets/C scripts/Managers/Player.cs`); `3c3f718d` 版本[3. 10. 13] —— 优化 [新增] 1. Debug添加区块边界显示器 (F3自动触发) 2. 稍微降低了苹果的掉落率 (… (at that commit the files were still `Assets/C scripts/Managers/Chunk.cs` and `Assets/C scripts/Managers/Player.cs`) — run `git show` on any of them.
  • Change coupling: CanvasManager.cs ↔ CommandManager.cs Assets/_MC_/Cscript/UI/Old/CanvasManager.cs:1 — `Assets/_MC_/Cscript/UI/Old/CanvasManager.cs` and `Assets/_MC_/Cscript/UI/Old/CommandManager.cs` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in 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 5 shared commits counted here, the most recent 3 are `65e43756` ``` 版本[3. 10. 12] —— 添加旁观者模式,优化 [新增] 1. HandMoving动画会在玩家停止移动的时候立刻归位而不… (at that commit the files were still `Assets/C scripts/Managers/CanvasManager.cs` and `Assets/C scripts/Managers/CommandManager.cs`); `b6c04d63` 版本[3.8.6] —— 优化 [新增] 1. 更新指令集,"/give <byte> <int>"给与玩家一定数量的某物品 (at that commit the files were still `Assets/C scripts/Managers/CanvasManager.cs` and `Assets/C scripts/Managers/CommandManager.cs`); `3844ca2b` 版本[3.7.10]——优化 (at that commit the files were still `Assets/C scripts/Managers/CanvasManager.cs` and `Assets/C scripts/Managers/CommandManager.cs`) — run `git show` on any of them.
D4 · Code Duplication · Edited copy of a member (22 corresponding lines) · ×2
  • Edited copy of a member (22 corresponding lines) Assets/_MC_/Cscript/Component/MC_Component_AI.cs:243 — Assets/_MC_/Cscript/Component/MC_Component_AI.cs:243-264 | Assets/_MC_/Cscript/Component/MC_Component_AI.cs:613-634 — 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) Assets/_MC_/Cscript/Component/MC_Component_AI.cs:368 — Assets/_MC_/Cscript/Component/MC_Component_AI.cs:368-393 | Assets/_MC_/Cscript/Component/MC_Component_AI.cs:731-752 — 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 (21 corresponding lines) · ×2
  • Edited copy of a member (21 corresponding lines) Assets/Resources/Prefeb/Entity/TNT/Entity_TNT.cs:163 — Assets/Resources/Prefeb/Entity/TNT/Entity_TNT.cs:163-188 | Assets/_MC_/Cscript/Buffs/MC_Buff_SwellandExplore.cs:36-56 — 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) Assets/_MC_/Scene/TestScene/NoiseMapTest/GenVoronoi.cs:62 — Assets/_MC_/Scene/TestScene/NoiseMapTest/GenVoronoi.cs:62-82 | Assets/_MC_/Scene/TestScene/NoiseMapTest/GenVoronoi.cs:86-107 — 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 · Duplicated block (12 lines × 2) · ×2
  • Duplicated block (12 lines × 2) Assets/Resources/Prefeb/Entity/TNT/Entity_TNT.cs:277 — Assets/Resources/Prefeb/Entity/TNT/Entity_TNT.cs:277-288 | Assets/_MC_/Cscript/Buffs/MC_Buff_SwellandExplore.cs:142-153 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, 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 `Assets/Resources/Prefeb/Entity/TNT/Entity_TNT.cs:277` it begins part-way through the construct above it, so those exact lines 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) Assets/_MC_/Cscript/Old/Chunk.cs:4015 — Assets/_MC_/Cscript/Old/Chunk.cs:4015-4026 | Assets/_MC_/Scene/TestScene/test csharp/TerrainTest_Cube.cs:132-143 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×2
  • Duplicated block (11 lines × 2) Assets/_MC_/Cscript/Old/Chunk.cs:82 — Assets/_MC_/Cscript/Old/Chunk.cs:82-92 | Assets/_MC_/Cscript/Old/Chunk.cs:160-171 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Assets/_MC_/Cscript/Old/Chunk.cs:82` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:684 — Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:684-694 | Assets/_MC_/Cscript/Static/MC_Static_Chunk.cs:68-78 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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 (9 lines × 2) · ×2
  • Duplicated block (9 lines × 2) Assets/_MC_/Cscript/Service/MC_Service_Time.cs:258 — Assets/_MC_/Cscript/Service/MC_Service_Time.cs:258-267 | Assets/_MC_/Cscript/Service/MC_Service_Time.cs:269-277 — both copies are in the same file, so extract the 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 `Assets/_MC_/Cscript/Service/MC_Service_Time.cs:269` it begins part-way through the construct above it, so those exact lines 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) Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:154 — Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:154-162 | Assets/_MC_/Cscript/Static/MC_Static_Navigation.cs:251-259 — before extracting anything, compare `Assets/_MC_/Cscript/Debug/Debug_Navigate.cs` and `Assets/_MC_/Cscript/Static/MC_Static_Navigation.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 225 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×2
  • Duplicated block (15 lines × 2) Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:417 — Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:417-431 | Assets/_MC_/Cscript/Static/MC_Static_Navigation.cs:381-395 — before extracting anything, compare `Assets/_MC_/Cscript/Debug/Debug_Navigate.cs` and `Assets/_MC_/Cscript/Static/MC_Static_Navigation.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 225 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (15 lines × 2) Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:448 — Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:448-462 | Assets/_MC_/Cscript/Static/MC_Static_Navigation.cs:362-376 — before extracting anything, compare `Assets/_MC_/Cscript/Debug/Debug_Navigate.cs` and `Assets/_MC_/Cscript/Static/MC_Static_Navigation.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 225 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
AX2 · Stateful singletons · Stateful shared instance · ×1
  • Stateful shared instance: MC_Runtime_DynamicData Assets/_MC_/Cscript/RuntimeGameData/MC_Runtime_DynamicData.cs:5 — `MC_Runtime_DynamicData` keeps one instance of itself in the static `_instance`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_game_state, _game_mode; e.g. `_game_state` at line 18).
D1 · Cyclomatic Complexity · Player.GetPlayerInputs (cyclomatic 85) · ×1
  • Player.GetPlayerInputs (cyclomatic 85) Assets/_MC_/Cscript/Old/Player.cs:717 — Player.GetPlayerInputs has cyclomatic complexity 85 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CommandManager.CheckCommand (cyclomatic 54) · ×1
  • CommandManager.CheckCommand (cyclomatic 54) Assets/_MC_/Cscript/UI/Old/CommandManager.cs:37 — CommandManager.CheckCommand has cyclomatic complexity 54 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · Chunk.CreateData (cyclomatic 51) · ×1
  • Chunk.CreateData (cyclomatic 51) Assets/_MC_/Cscript/Old/Chunk.cs:279 — Chunk.CreateData has cyclomatic complexity 51 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · Chunk.CreateData_Forest (cyclomatic 50) · ×1
  • Chunk.CreateData_Forest (cyclomatic 50) Assets/_MC_/Cscript/Old/Chunk.cs:1182 — Chunk.CreateData_Forest has cyclomatic complexity 50 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · Chunk.CreateData_Marsh (cyclomatic 45) · ×1
  • Chunk.CreateData_Marsh (cyclomatic 45) Assets/_MC_/Cscript/Old/Chunk.cs:877 — Chunk.CreateData_Marsh has cyclomatic complexity 45 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · Chunk.UpdateMeshData (cyclomatic 34) · ×1
  • Chunk.UpdateMeshData (cyclomatic 34) Assets/_MC_/Cscript/Old/Chunk.cs:2403 — Chunk.UpdateMeshData has cyclomatic complexity 34 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · Chunk.CreateData_Dessert (cyclomatic 30) · ×1
  • Chunk.CreateData_Dessert (cyclomatic 30) Assets/_MC_/Cscript/Old/Chunk.cs:675 — Chunk.CreateData_Dessert has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MC_Component_Physics.GetTargetBlockHeightAndWidth (cyclomatic 27) · ×1
  • MC_Component_Physics.GetTargetBlockHeightAndWidth (cyclomatic 27) Assets/_MC_/Cscript/Component/MC_Component_Physics.cs:538 — MC_Component_Physics.GetTargetBlockHeightAndWidth 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 · Player.CalculateVelocity (cyclomatic 23) · ×1
  • Player.CalculateVelocity (cyclomatic 23) Assets/_MC_/Cscript/Old/Player.cs:540 — Player.CalculateVelocity 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 · Chunk.CheckSelfAndTarget (cyclomatic 21) · ×1
  • Chunk.CheckSelfAndTarget (cyclomatic 21) Assets/_MC_/Cscript/Old/Chunk.cs:4550 — Chunk.CheckSelfAndTarget has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CanvasManager.UpdateCanvasState (cyclomatic 21) · ×1
  • CanvasManager.UpdateCanvasState (cyclomatic 21) Assets/_MC_/Cscript/UI/Old/CanvasManager.cs:392 — CanvasManager.UpdateCanvasState has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · Chunk.UpdateChunkMesh_WithSurround (cyclomatic 20) · ×1
  • Chunk.UpdateChunkMesh_WithSurround (cyclomatic 20) Assets/_MC_/Cscript/Old/Chunk.cs:2235 — Chunk.UpdateChunkMesh_WithSurround 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 · Chunk.CheckVoxel (cyclomatic 20) · ×1
  • Chunk.CheckVoxel (cyclomatic 20) Assets/_MC_/Cscript/Old/Chunk.cs:4245 — Chunk.CheckVoxel 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 · MC_Service_World.AddtoCreateChunks (cyclomatic 19) · ×1
  • MC_Service_World.AddtoCreateChunks (cyclomatic 19) Assets/_MC_/Cscript/Service/MC_Service_World.cs:372 — MC_Service_World.AddtoCreateChunks 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 · MC_Static_Raycast.RayCast (cyclomatic 19) · ×1
  • MC_Static_Raycast.RayCast (cyclomatic 19) Assets/_MC_/Cscript/Static/MC_Static_Raycast.cs:20 — MC_Static_Raycast.RayCast 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 · MyCancelDragScrollRect.LateUpdate (cyclomatic 18) · ×1
  • MyCancelDragScrollRect.LateUpdate (cyclomatic 18) Assets/_MC_/Cscript/AuxiliaryScripts/ScrollRectWithNoDrag.cs:796 — MyCancelDragScrollRect.LateUpdate has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · Player.AchieveInput (cyclomatic 18) · ×1
  • Player.AchieveInput (cyclomatic 18) Assets/_MC_/Cscript/Old/Player.cs:1774 — Player.AchieveInput has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MC_Service_Time.FromGameTimeToUpdateAll_Smooth (cyclomatic 18) · ×1
  • MC_Service_Time.FromGameTimeToUpdateAll_Smooth (cyclomatic 18) Assets/_MC_/Cscript/Service/MC_Service_Time.cs:285 — MC_Service_Time.FromGameTimeToUpdateAll_Smooth has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MC_Service_Time.FromGameTimeToUpdateAll_Imediately (cyclomatic 18) · ×1
  • MC_Service_Time.FromGameTimeToUpdateAll_Imediately (cyclomatic 18) Assets/_MC_/Cscript/Service/MC_Service_Time.cs:350 — MC_Service_Time.FromGameTimeToUpdateAll_Imediately has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EditorOverride.OnInspectorGUI (cyclomatic 17) · ×1
  • EditorOverride.OnInspectorGUI (cyclomatic 17) Assets/Homebrew/DecorateFoldout/Editor/EditorOverride.cs:96 — EditorOverride.OnInspectorGUI has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BackPackManager.ChangeBlockInHand (cyclomatic 17) · ×1
  • BackPackManager.ChangeBlockInHand (cyclomatic 17) Assets/_MC_/Cscript/UI/Old/BackPackManager.cs:471 — BackPackManager.ChangeBlockInHand has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · Chunk.EditData (cyclomatic 16) · ×1
  • Chunk.EditData (cyclomatic 16) Assets/_MC_/Cscript/Old/Chunk.cs:3343 — Chunk.EditData has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D2 · Cognitive Complexity · Chunk.CreateData (cognitive 129) · ×1
  • Chunk.CreateData (cognitive 129) Assets/_MC_/Cscript/Old/Chunk.cs:279 — Chunk.CreateData has cognitive complexity 129 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: Assets/_MC_/Cscript/Old/Chunk.cs holds 14 of the 51 methods over the threshold — including the worst — and 553 of the 1137 points over it (49%), 3.7× the next-largest file (Assets/_MC_/Cscript/Old/Player.cs at 149). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · Player.GetPlayerInputs (cognitive 129) · ×1
  • Player.GetPlayerInputs (cognitive 129) Assets/_MC_/Cscript/Old/Player.cs:717 — Player.GetPlayerInputs has cognitive complexity 129 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CommandManager.CheckCommand (cognitive 127) · ×1
  • CommandManager.CheckCommand (cognitive 127) Assets/_MC_/Cscript/UI/Old/CommandManager.cs:37 — CommandManager.CheckCommand has cognitive complexity 127 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Chunk.CreateData_Forest (cognitive 119) · ×1
  • Chunk.CreateData_Forest (cognitive 119) Assets/_MC_/Cscript/Old/Chunk.cs:1182 — Chunk.CreateData_Forest has cognitive complexity 119 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: Assets/_MC_/Cscript/Old/Chunk.cs holds 14 of the 51 methods over the threshold — including the worst — and 553 of the 1137 points over it (49%), 3.7× the next-largest file (Assets/_MC_/Cscript/Old/Player.cs at 149). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · Chunk.CreateData_Marsh (cognitive 83) · ×1
  • Chunk.CreateData_Marsh (cognitive 83) Assets/_MC_/Cscript/Old/Chunk.cs:877 — Chunk.CreateData_Marsh has cognitive complexity 83 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: Assets/_MC_/Cscript/Old/Chunk.cs holds 14 of the 51 methods over the threshold — including the worst — and 553 of the 1137 points over it (49%), 3.7× the next-largest file (Assets/_MC_/Cscript/Old/Player.cs at 149). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · Chunk.CreateData_Dessert (cognitive 67) · ×1
  • Chunk.CreateData_Dessert (cognitive 67) Assets/_MC_/Cscript/Old/Chunk.cs:675 — Chunk.CreateData_Dessert has cognitive complexity 67 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: Assets/_MC_/Cscript/Old/Chunk.cs holds 14 of the 51 methods over the threshold — including the worst — and 553 of the 1137 points over it (49%), 3.7× the next-largest file (Assets/_MC_/Cscript/Old/Player.cs at 149). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MC_Component_Physics.GetTargetBlockHeightAndWidth (cognitive 66) · ×1
  • MC_Component_Physics.GetTargetBlockHeightAndWidth (cognitive 66) Assets/_MC_/Cscript/Component/MC_Component_Physics.cs:538 — MC_Component_Physics.GetTargetBlockHeightAndWidth has cognitive complexity 66 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Chunk.UpdateMeshData (cognitive 66) · ×1
  • Chunk.UpdateMeshData (cognitive 66) Assets/_MC_/Cscript/Old/Chunk.cs:2403 — Chunk.UpdateMeshData has cognitive complexity 66 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: Assets/_MC_/Cscript/Old/Chunk.cs holds 14 of the 51 methods over the threshold — including the worst — and 553 of the 1137 points over it (49%), 3.7× the next-largest file (Assets/_MC_/Cscript/Old/Player.cs at 149). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · Chunk.UpdateChunkMesh_WithSurround (cognitive 53) · ×1
  • Chunk.UpdateChunkMesh_WithSurround (cognitive 53) Assets/_MC_/Cscript/Old/Chunk.cs:2235 — Chunk.UpdateChunkMesh_WithSurround has cognitive complexity 53 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: Assets/_MC_/Cscript/Old/Chunk.cs holds 14 of the 51 methods over the threshold — including the worst — and 553 of the 1137 points over it (49%), 3.7× the next-largest file (Assets/_MC_/Cscript/Old/Player.cs at 149). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · BackPackManager.ChangeBlockInHand (cognitive 50) · ×1
  • BackPackManager.ChangeBlockInHand (cognitive 50) Assets/_MC_/Cscript/UI/Old/BackPackManager.cs:471 — BackPackManager.ChangeBlockInHand has cognitive complexity 50 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Chunk.CheckVoxel (cognitive 44) · ×1
  • Chunk.CheckVoxel (cognitive 44) Assets/_MC_/Cscript/Old/Chunk.cs:4245 — Chunk.CheckVoxel has cognitive complexity 44 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: Assets/_MC_/Cscript/Old/Chunk.cs holds 14 of the 51 methods over the threshold — including the worst — and 553 of the 1137 points over it (49%), 3.7× the next-largest file (Assets/_MC_/Cscript/Old/Player.cs at 149). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · EditorOverride.OnInspectorGUI (cognitive 40) · ×1
  • EditorOverride.OnInspectorGUI (cognitive 40) Assets/Homebrew/DecorateFoldout/Editor/EditorOverride.cs:96 — EditorOverride.OnInspectorGUI has cognitive complexity 40 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MC_Static_Raycast.RayCast (cognitive 39) · ×1
  • MC_Static_Raycast.RayCast (cognitive 39) Assets/_MC_/Cscript/Static/MC_Static_Raycast.cs:20 — MC_Static_Raycast.RayCast has cognitive complexity 39 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Chunk.EditData (cognitive 36) · ×1
  • Chunk.EditData (cognitive 36) Assets/_MC_/Cscript/Old/Chunk.cs:3343 — Chunk.EditData has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: Assets/_MC_/Cscript/Old/Chunk.cs holds 14 of the 51 methods over the threshold — including the worst — and 553 of the 1137 points over it (49%), 3.7× the next-largest file (Assets/_MC_/Cscript/Old/Player.cs at 149). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · Chunk.CheckSelfAndTarget (cognitive 34) · ×1
  • Chunk.CheckSelfAndTarget (cognitive 34) Assets/_MC_/Cscript/Old/Chunk.cs:4550 — Chunk.CheckSelfAndTarget 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. This file is where this pass's cognitive complexity CONCENTRATES: Assets/_MC_/Cscript/Old/Chunk.cs holds 14 of the 51 methods over the threshold — including the worst — and 553 of the 1137 points over it (49%), 3.7× the next-largest file (Assets/_MC_/Cscript/Old/Player.cs at 149). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MC_Service_World.AddtoCreateChunks (cognitive 34) · ×1
  • MC_Service_World.AddtoCreateChunks (cognitive 34) Assets/_MC_/Cscript/Service/MC_Service_World.cs:372 — MC_Service_World.AddtoCreateChunks 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 · Chunk.CreateTree (cognitive 32) · ×1
  • Chunk.CreateTree (cognitive 32) Assets/_MC_/Cscript/Old/Chunk.cs:1608 — Chunk.CreateTree has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: Assets/_MC_/Cscript/Old/Chunk.cs holds 14 of the 51 methods over the threshold — including the worst — and 553 of the 1137 points over it (49%), 3.7× the next-largest file (Assets/_MC_/Cscript/Old/Player.cs at 149). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · Player.CalculateVelocity (cognitive 32) · ×1
  • Player.CalculateVelocity (cognitive 32) Assets/_MC_/Cscript/Old/Player.cs:540 — Player.CalculateVelocity has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MyCancelDragScrollRect.LateUpdate (cognitive 30) · ×1
  • MyCancelDragScrollRect.LateUpdate (cognitive 30) Assets/_MC_/Cscript/AuxiliaryScripts/ScrollRectWithNoDrag.cs:796 — MyCancelDragScrollRect.LateUpdate has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Player.AchieveInput (cognitive 30) · ×1
  • Player.AchieveInput (cognitive 30) Assets/_MC_/Cscript/Old/Player.cs:1774 — Player.AchieveInput has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Debug_Navigate.OnDrawGizmos (cognitive 29) · ×1
  • Debug_Navigate.OnDrawGizmos (cognitive 29) Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:488 — Debug_Navigate.OnDrawGizmos has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MC_Static_Noise.GetTotalNoiseHigh_Biome (cognitive 28) · ×1
  • MC_Static_Noise.GetTotalNoiseHigh_Biome (cognitive 28) Assets/_MC_/Cscript/Static/MC_Static_Noise.cs:109 — MC_Static_Noise.GetTotalNoiseHigh_Biome 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 · HandShake.FixedUpdate (cognitive 27) · ×1
  • HandShake.FixedUpdate (cognitive 27) Assets/_MC_/Cscript/AnimationScripts/HandShake.cs:37 — HandShake.FixedUpdate has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Chunk.UpdateChunkMesh_WithSurround (cognitive 27) · ×1
  • Chunk.UpdateChunkMesh_WithSurround (cognitive 27) Assets/_MC_/Cscript/Old/Chunk.cs:2112 — Chunk.UpdateChunkMesh_WithSurround has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: Assets/_MC_/Cscript/Old/Chunk.cs holds 14 of the 51 methods over the threshold — including the worst — and 553 of the 1137 points over it (49%), 3.7× the next-largest file (Assets/_MC_/Cscript/Old/Player.cs at 149). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · OldMusicManager.Fade_FallInto_Water (cognitive 26) · ×1
  • OldMusicManager.Fade_FallInto_Water (cognitive 26) Assets/_MC_/Cscript/Old/OldMusicManager.cs:323 — OldMusicManager.Fade_FallInto_Water has cognitive complexity 26 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Debug_Navigate.Chase_Astar (cognitive 25) · ×1
  • Debug_Navigate.Chase_Astar (cognitive 25) Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:223 — Debug_Navigate.Chase_Astar has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Debug_Navigate.Chase_AstarCoroutine (cognitive 25) · ×1
  • Debug_Navigate.Chase_AstarCoroutine (cognitive 25) Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:321 — Debug_Navigate.Chase_AstarCoroutine has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · OldMusicManager.PlaySound_Foot (cognitive 25) · ×1
  • OldMusicManager.PlaySound_Foot (cognitive 25) Assets/_MC_/Cscript/Old/OldMusicManager.cs:411 — OldMusicManager.PlaySound_Foot has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CanvasManager.UpdateCanvasState (cognitive 24) · ×1
  • CanvasManager.UpdateCanvasState (cognitive 24) Assets/_MC_/Cscript/UI/Old/CanvasManager.cs:392 — CanvasManager.UpdateCanvasState 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 · CanvasManager.Compoments_SaveWorldSettings (cognitive 24) · ×1
  • CanvasManager.Compoments_SaveWorldSettings (cognitive 24) Assets/_MC_/Cscript/UI/Old/CanvasManager.cs:605 — CanvasManager.Compoments_SaveWorldSettings 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 · MC_Static_BlocksFunction.Boom (cognitive 23) · ×1
  • MC_Static_BlocksFunction.Boom (cognitive 23) Assets/_MC_/Cscript/Static/MC_Static_BlocksFunction.cs:18 — MC_Static_BlocksFunction.Boom 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 · MC_Static_Navigation.Algo_Astar (cognitive 21) · ×1
  • MC_Static_Navigation.Algo_Astar (cognitive 21) Assets/_MC_/Cscript/Static/MC_Static_Navigation.cs:270 — MC_Static_Navigation.Algo_Astar has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Entity_TNT.OnEndEntity (cognitive 20) · ×1
  • Entity_TNT.OnEndEntity (cognitive 20) Assets/Resources/Prefeb/Entity/TNT/Entity_TNT.cs:195 — Entity_TNT.OnEndEntity 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 · MC_Buff_SwellandExplore.Handle_Explore (cognitive 20) · ×1
  • MC_Buff_SwellandExplore.Handle_Explore (cognitive 20) Assets/_MC_/Cscript/Buffs/MC_Buff_SwellandExplore.cs:60 — MC_Buff_SwellandExplore.Handle_Explore 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 · BackPackManager.update_slots (cognitive 20) · ×1
  • BackPackManager.update_slots (cognitive 20) Assets/_MC_/Cscript/UI/Old/BackPackManager.cs:275 — BackPackManager.update_slots 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 · SlotBlockItem.OnPointerDown (cognitive 19) · ×1
  • SlotBlockItem.OnPointerDown (cognitive 19) Assets/_MC_/Cscript/AuxiliaryScripts/SlotBlockItem.cs:55 — SlotBlockItem.OnPointerDown 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 · Chunk.CanSetStump (cognitive 19) · ×1
  • Chunk.CanSetStump (cognitive 19) Assets/_MC_/Cscript/Old/Chunk.cs:1847 — Chunk.CanSetStump 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. This file is where this pass's cognitive complexity CONCENTRATES: Assets/_MC_/Cscript/Old/Chunk.cs holds 14 of the 51 methods over the threshold — including the worst — and 553 of the 1137 points over it (49%), 3.7× the next-largest file (Assets/_MC_/Cscript/Old/Player.cs at 149). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MC_Static_BlocksFunction.Smoke (cognitive 19) · ×1
  • MC_Static_BlocksFunction.Smoke (cognitive 19) Assets/_MC_/Cscript/Static/MC_Static_BlocksFunction.cs:74 — MC_Static_BlocksFunction.Smoke 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 · GenNoise.GenerateNoiseMap (cognitive 19) · ×1
  • GenNoise.GenerateNoiseMap (cognitive 19) Assets/_MC_/Scene/TestScene/NoiseMapTest/GenNoise.cs:27 — GenNoise.GenerateNoiseMap 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 · OldMusicManager.FUN_PlaceandBroke (cognitive 18) · ×1
  • OldMusicManager.FUN_PlaceandBroke (cognitive 18) Assets/_MC_/Cscript/Old/OldMusicManager.cs:181 — OldMusicManager.FUN_PlaceandBroke 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 · Player.GetDestroyTime (cognitive 18) · ×1
  • Player.GetDestroyTime (cognitive 18) Assets/_MC_/Cscript/Old/Player.cs:1420 — Player.GetDestroyTime 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 · MC_Service_Time.FromGameTimeToUpdateAll_Smooth (cognitive 17) · ×1
  • MC_Service_Time.FromGameTimeToUpdateAll_Smooth (cognitive 17) Assets/_MC_/Cscript/Service/MC_Service_Time.cs:285 — MC_Service_Time.FromGameTimeToUpdateAll_Smooth has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MC_Service_Time.FromGameTimeToUpdateAll_Imediately (cognitive 17) · ×1
  • MC_Service_Time.FromGameTimeToUpdateAll_Imediately (cognitive 17) Assets/_MC_/Cscript/Service/MC_Service_Time.cs:350 — MC_Service_Time.FromGameTimeToUpdateAll_Imediately has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DebugManager.CameraOnPreRender (cognitive 17) · ×1
  • DebugManager.CameraOnPreRender (cognitive 17) Assets/_MC_/Cscript/UI/Old/DebugManager.cs:252 — DebugManager.CameraOnPreRender has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LifeManager.UpdatePlayerFood (cognitive 17) · ×1
  • LifeManager.UpdatePlayerFood (cognitive 17) Assets/_MC_/Cscript/UI/Old/LifeManager.cs:278 — LifeManager.UpdatePlayerFood has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MyCancelDragScrollRect.UpdateBounds (cognitive 16) · ×1
  • MyCancelDragScrollRect.UpdateBounds (cognitive 16) Assets/_MC_/Cscript/AuxiliaryScripts/ScrollRectWithNoDrag.cs:1235 — MyCancelDragScrollRect.UpdateBounds 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 · MC_Static_Noise.GetBiomeType (cognitive 16) · ×1
  • MC_Static_Noise.GetBiomeType (cognitive 16) Assets/_MC_/Cscript/Static/MC_Static_Noise.cs:47 — MC_Static_Noise.GetBiomeType 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 · BackPackManager.CheckSlotsFull (cognitive 16) · ×1
  • BackPackManager.CheckSlotsFull (cognitive 16) Assets/_MC_/Cscript/UI/Old/BackPackManager.cs:635 — BackPackManager.CheckSlotsFull 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 · LifeManager.UpdatePlayerBlood (cognitive 16) · ×1
  • LifeManager.UpdatePlayerBlood (cognitive 16) Assets/_MC_/Cscript/UI/Old/LifeManager.cs:149 — LifeManager.UpdatePlayerBlood 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.
D35 · Change Coupling · Change-coupling hub · ×1
  • Change-coupling hub: MC_Service_Saving.cs → Player.cs, BackPackManager.cs, CanvasManager.cs, CommandManager.cs Assets/_MC_/Cscript/Service/MC_Service_Saving.cs — `Assets/_MC_/Cscript/Service/MC_Service_Saving.cs` changes together with 4 other files — `Assets/_MC_/Cscript/Old/Player.cs`, `Assets/_MC_/Cscript/UI/Old/BackPackManager.cs`, `Assets/_MC_/Cscript/UI/Old/CanvasManager.cs`, `Assets/_MC_/Cscript/UI/Old/CommandManager.cs` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
D4 · Code Duplication · Near-duplicate member family (4 members, 112 shared lines) · ×1
  • Near-duplicate member family (4 members, 112 shared lines) Assets/_MC_/Cscript/Old/Chunk.cs:280 — Assets/_MC_/Cscript/Old/Chunk.cs:280-631 | Assets/_MC_/Cscript/Old/Chunk.cs:676-874 | Assets/_MC_/Cscript/Old/Chunk.cs:878-1179 | Assets/_MC_/Cscript/Old/Chunk.cs:1183-1550 — These 4 members are variants of one another: a block of 112 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Edited copy of a member (83 corresponding lines) · ×1
  • Edited copy of a member (83 corresponding lines) Assets/_MC_/Cscript/Old/Chunk.cs:3680 — Assets/_MC_/Cscript/Old/Chunk.cs:3680-3791 | Assets/_MC_/Cscript/Old/Chunk.cs:3795-3892 — These two members are one piece of code written twice and then edited apart: 83 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (97 corresponding lines) · ×1
  • Edited copy of a member (97 corresponding lines) Assets/Resources/Prefeb/Entity/TNT/Entity_TNT.cs:196 — Assets/Resources/Prefeb/Entity/TNT/Entity_TNT.cs:196-293 | Assets/_MC_/Cscript/Buffs/MC_Buff_SwellandExplore.cs:61-157 — These two members are one piece of code written twice and then edited apart: 97 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (120 corresponding lines) · ×1
  • Edited copy of a member (120 corresponding lines) Assets/_MC_/Cscript/Old/Chunk.cs:2113 — Assets/_MC_/Cscript/Old/Chunk.cs:2113-2232 | Assets/_MC_/Cscript/Old/Chunk.cs:2236-2397 — These two members are one piece of code written twice and then edited apart: 120 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (74 corresponding lines) · ×1
  • Edited copy of a member (74 corresponding lines) Assets/_MC_/Cscript/Old/Chunk.cs:82 — Assets/_MC_/Cscript/Old/Chunk.cs:82-155 | Assets/_MC_/Cscript/Old/Chunk.cs:160-235 — These two members are one piece of code written twice and then edited apart: 74 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 87+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 87+ corresponding lines) Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:224 — Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:224-316 | Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:322-412 | Assets/_MC_/Cscript/Static/MC_Static_Navigation.cs:271-357 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 87 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (55 corresponding lines) · ×1
  • Edited copy of a member (55 corresponding lines) Assets/_MC_/Cscript/Service/MC_Service_Time.cs:286 — Assets/_MC_/Cscript/Service/MC_Service_Time.cs:286-345 | Assets/_MC_/Cscript/Service/MC_Service_Time.cs:351-405 — 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 (39 corresponding lines) · ×1
  • Edited copy of a member (39 corresponding lines) Assets/_MC_/Cscript/Static/MC_Static_BlocksFunction.cs:19 — Assets/_MC_/Cscript/Static/MC_Static_BlocksFunction.cs:19-70 | Assets/_MC_/Cscript/Static/MC_Static_BlocksFunction.cs:137-175 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (34 corresponding lines) · ×1
  • Edited copy of a member (34 corresponding lines) Assets/_MC_/Cscript/Service/MC_Service_World.cs:1089 — Assets/_MC_/Cscript/Service/MC_Service_World.cs:1089-1122 | Assets/_MC_/Cscript/Service/MC_Service_World.cs:1165-1202 — 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 (25 corresponding lines) · ×1
  • Edited copy of a member (25 corresponding lines) Assets/_MC_/Cscript/Service/MC_Service_MeshBuilder.cs:9 — Assets/_MC_/Cscript/Service/MC_Service_MeshBuilder.cs:9-33 | Assets/_MC_/Scene/TestScene/ChunkMeshDataCaculator/MC_Chunk_Renderer.cs:9-45 — 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 copies of one member (4 members, 36+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 36+ corresponding lines) Assets/_MC_/Cscript/Component/MC_Component_Physics.cs:233 — Assets/_MC_/Cscript/Component/MC_Component_Physics.cs:233-270 | Assets/_MC_/Cscript/Component/MC_Component_Physics.cs:277-314 | Assets/_MC_/Cscript/Component/MC_Component_Physics.cs:321-362 | Assets/_MC_/Cscript/Component/MC_Component_Physics.cs:369-404 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 36 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (31 corresponding lines) · ×1
  • Edited copy of a member (31 corresponding lines) Assets/_MC_/Cscript/Component/MC_Component_AI.cs:267 — Assets/_MC_/Cscript/Component/MC_Component_AI.cs:267-299 | Assets/_MC_/Cscript/Component/MC_Component_AI.cs:637-667 — 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 copies of one member (3 members, 20+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 20+ corresponding lines) Assets/_MC_/Cscript/Old/Chunk.cs:3505 — Assets/_MC_/Cscript/Old/Chunk.cs:3505-3524 | Assets/_MC_/Cscript/Old/Chunk.cs:3546-3565 | Assets/_MC_/Cscript/Old/Chunk.cs:3569-3593 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×1
  • Edited copy of a member (14 corresponding lines) Assets/_MC_/Cscript/Old/Chunk.cs:4013 — Assets/_MC_/Cscript/Old/Chunk.cs:4013-4026 | Assets/_MC_/Scene/TestScene/test csharp/TerrainTest_Cube.cs:130-143 — 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 (23 corresponding lines) · ×1
  • Edited copy of a member (23 corresponding lines) Assets/_MC_/Cscript/Service/MC_Service_Entity.cs:422 — Assets/_MC_/Cscript/Service/MC_Service_Entity.cs:422-444 | Assets/_MC_/Cscript/Service/MC_Service_Entity.cs:455-477 — 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 (20 corresponding lines) · ×1
  • Edited copy of a member (20 corresponding lines) Assets/_MC_/Cscript/UI/Old/LifeManager.cs:235 — Assets/_MC_/Cscript/UI/Old/LifeManager.cs:235-254 | Assets/_MC_/Cscript/UI/Old/LifeManager.cs:365-384 — 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 · Edited copy of a member (41 corresponding lines) · ×1
  • Edited copy of a member (41 corresponding lines) Assets/_MC_/Cscript/AuxiliaryScripts/TextureTo3D.cs:131 — Assets/_MC_/Cscript/AuxiliaryScripts/TextureTo3D.cs:131-171 | Assets/_MC_/Cscript/AuxiliaryScripts/TextureTo3D.cs:176-246 — 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 (12 corresponding lines) · ×1
  • Edited copy of a member (12 corresponding lines) Assets/_MC_/Cscript/Old/Chunk.cs:239 — Assets/_MC_/Cscript/Old/Chunk.cs:239-256 | Assets/_MC_/Cscript/Old/Chunk.cs:259-270 — 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 (7 corresponding lines) · ×1
  • Edited copy of a member (7 corresponding lines) Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:466 — Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:466-472 | Assets/_MC_/Cscript/Static/MC_Static_Math.cs:129-135 — 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 · Edited copy of a member (8 corresponding lines) · ×1
  • Edited copy of a member (8 corresponding lines) Assets/_MC_/Cscript/Old/Chunk.cs:4210 — Assets/_MC_/Cscript/Old/Chunk.cs:4210-4221 | Assets/_MC_/Cscript/Static/MC_Static_Chunk.cs:115-122 — 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 · Edited copy of a member (11 corresponding lines) · ×1
  • Edited copy of a member (11 corresponding lines) Assets/_MC_/Cscript/AuxiliaryScripts/CloudManager.cs:33 — Assets/_MC_/Cscript/AuxiliaryScripts/CloudManager.cs:33-52 | Assets/_MC_/Cscript/Service/MC_Service_Entity.cs:31-41 — 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 · Duplicated block (83–95 lines × 2) · ×1
  • Duplicated block (83–95 lines × 2) Assets/_MC_/Cscript/Old/Chunk.cs:3687 — Assets/_MC_/Cscript/Old/Chunk.cs:3687-3781 | Assets/_MC_/Cscript/Old/Chunk.cs:3798-3880 — both copies are in the same file, so extract the 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 `Assets/_MC_/Cscript/Old/Chunk.cs:3687` it does not close everything it opens, so those 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 (75–76 lines × 2) · ×1
  • Duplicated block (75–76 lines × 2) Assets/Resources/Prefeb/Entity/TNT/Entity_TNT.cs:196 — Assets/Resources/Prefeb/Entity/TNT/Entity_TNT.cs:196-270 | Assets/_MC_/Cscript/Buffs/MC_Buff_SwellandExplore.cs:61-136 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Assets/Resources/Prefeb/Entity/TNT/Entity_TNT.cs: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.
D4 · Code Duplication · Duplicated block (65–70 lines × 4) · ×1
  • Duplicated block (65–70 lines × 4) Assets/_MC_/Cscript/Old/Chunk.cs:532 — Assets/_MC_/Cscript/Old/Chunk.cs:532-601 | Assets/_MC_/Cscript/Old/Chunk.cs:781-845 | Assets/_MC_/Cscript/Old/Chunk.cs:1048-1117 | Assets/_MC_/Cscript/Old/Chunk.cs:1409-1478 — 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 `Assets/_MC_/Cscript/Old/Chunk.cs:532` it begins part-way through the construct above it, so those 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, `Assets/_MC_/Cscript/Old/Chunk.cs:605` calls `CreateTree` and `Assets/_MC_/Cscript/Old/Chunk.cs:852` 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 (66–68 lines × 3) · ×1
  • Duplicated block (66–68 lines × 3) Assets/_MC_/Cscript/Old/Chunk.cs:337 — Assets/_MC_/Cscript/Old/Chunk.cs:337-404 | Assets/_MC_/Cscript/Old/Chunk.cs:925-992 | Assets/_MC_/Cscript/Old/Chunk.cs:1243-1308 — 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 `Assets/_MC_/Cscript/Old/Chunk.cs:337` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code 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 (62–64 lines × 2) · ×1
  • Duplicated block (62–64 lines × 2) Assets/_MC_/Cscript/Old/Chunk.cs:92 — Assets/_MC_/Cscript/Old/Chunk.cs:92-155 | Assets/_MC_/Cscript/Old/Chunk.cs:174-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. Read the line range as the matched WINDOW rather than a finished unit: at `Assets/_MC_/Cscript/Old/Chunk.cs:92` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those 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 (48–60 lines × 3) · ×1
  • Duplicated block (48–60 lines × 3) Assets/_MC_/Cscript/Old/Chunk.cs:286 — Assets/_MC_/Cscript/Old/Chunk.cs:286-345 | Assets/_MC_/Cscript/Old/Chunk.cs:682-729 | Assets/_MC_/Cscript/Old/Chunk.cs:884-933 — 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 `Assets/_MC_/Cscript/Old/Chunk.cs:286` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code 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 (42–43 lines × 2) · ×1
  • Duplicated block (42–43 lines × 2) Assets/_MC_/Cscript/Old/Chunk.cs:482 — Assets/_MC_/Cscript/Old/Chunk.cs:482-524 | Assets/_MC_/Cscript/Old/Chunk.cs:1360-1401 — both copies are in the same file, so extract the 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 `Assets/_MC_/Cscript/Old/Chunk.cs:482` it begins part-way through the construct above it, so those 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 (42 lines × 2) · ×1
  • Duplicated block (42 lines × 2) Assets/_MC_/Cscript/Old/Chunk.cs:1614 — Assets/_MC_/Cscript/Old/Chunk.cs:1614-1655 | Assets/_MC_/Cscript/Old/Chunk.cs:1661-1702 — both copies are in the same file, so extract the 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 `Assets/_MC_/Cscript/Old/Chunk.cs:1661` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those 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 (41–42 lines × 2) · ×1
  • Duplicated block (41–42 lines × 2) Assets/_MC_/Cscript/Old/Chunk.cs:2119 — Assets/_MC_/Cscript/Old/Chunk.cs:2119-2160 | Assets/_MC_/Cscript/Old/Chunk.cs:2243-2283 — both copies are in the same file, so extract the 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 `Assets/_MC_/Cscript/Old/Chunk.cs:2119` it does not close everything it opens, so those 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 (38–40 lines × 2) · ×1
  • Duplicated block (38–40 lines × 2) Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:234 — Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:234-273 | Assets/_MC_/Cscript/Static/MC_Static_Navigation.cs:282-319 — before extracting anything, compare `Assets/_MC_/Cscript/Debug/Debug_Navigate.cs` and `Assets/_MC_/Cscript/Static/MC_Static_Navigation.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 225 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:234` it does not close everything it opens, so those 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, `Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:275` calls `Log` and `Assets/_MC_/Cscript/Static/MC_Static_Navigation.cs:323` 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 (47–61 lines × 4) · ×1
  • Duplicated block (47–61 lines × 4) Assets/_MC_/Cscript/Old/Chunk.cs:280 — Assets/_MC_/Cscript/Old/Chunk.cs:280-337 | Assets/_MC_/Cscript/Old/Chunk.cs:676-722 | Assets/_MC_/Cscript/Old/Chunk.cs:878-925 | Assets/_MC_/Cscript/Old/Chunk.cs:1183-1243 — 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 `Assets/_MC_/Cscript/Old/Chunk.cs:280` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code 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 (35 lines × 2) · ×1
  • Duplicated block (35 lines × 2) Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:115 — Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:115-149 | Assets/_MC_/Cscript/Static/MC_Static_Navigation.cs:212-246 — before extracting anything, compare `Assets/_MC_/Cscript/Debug/Debug_Navigate.cs` and `Assets/_MC_/Cscript/Static/MC_Static_Navigation.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 225 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (34–37 lines × 2) · ×1
  • Duplicated block (34–37 lines × 2) Assets/_MC_/Cscript/Service/MC_Service_World.cs:584 — Assets/_MC_/Cscript/Service/MC_Service_World.cs:584-620 | Assets/_MC_/Cscript/Service/MC_Service_World.cs:624-657 — both copies are in the same file, so extract the 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 (29–34 lines × 2) · ×1
  • Duplicated block (29–34 lines × 2) Assets/_MC_/Cscript/Old/Chunk.cs:1761 — Assets/_MC_/Cscript/Old/Chunk.cs:1761-1789 | Assets/_MC_/Cscript/Old/Chunk.cs:1809-1842 — both copies are in the same file, so extract the 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 `Assets/_MC_/Cscript/Old/Chunk.cs:1761` 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 (28–33 lines × 2) · ×1
  • Duplicated block (28–33 lines × 2) Assets/_MC_/Cscript/Service/MC_Service_Music.cs:31 — Assets/_MC_/Cscript/Service/MC_Service_Music.cs:31-58 | Assets/_MC_/Cscript/Service/MC_Service_Time.cs:30-62 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — 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 (29 lines × 2) · ×1
  • Duplicated block (29 lines × 2) Assets/Resources/Items/ItemScripts/Item_Base.cs:66 — Assets/Resources/Items/ItemScripts/Item_Base.cs:66-94 | Assets/_MC_/Cscript/Class/MC_Class_Chunk.cs:182-210 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (28–29 lines × 2) · ×1
  • Duplicated block (28–29 lines × 2) Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:80 — Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:80-108 | Assets/_MC_/Cscript/Static/MC_Static_Navigation.cs:178-205 — before extracting anything, compare `Assets/_MC_/Cscript/Debug/Debug_Navigate.cs` and `Assets/_MC_/Cscript/Static/MC_Static_Navigation.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 225 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (28 lines × 2) · ×1
  • Duplicated block (28 lines × 2) Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:594 — Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:594-621 | Assets/_MC_/Cscript/Static/MC_Static_Navigation.cs:44-71 — before extracting anything, compare `Assets/_MC_/Cscript/Debug/Debug_Navigate.cs` and `Assets/_MC_/Cscript/Static/MC_Static_Navigation.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 225 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (17–27 lines × 3) · ×1
  • Duplicated block (17–27 lines × 3) Assets/_MC_/Cscript/Component/MC_Component_Physics.cs:612 — Assets/_MC_/Cscript/Component/MC_Component_Physics.cs:612-638 | Assets/_MC_/Cscript/Component/MC_Component_Physics.cs:650-674 | Assets/_MC_/Cscript/Component/MC_Component_Physics.cs:691-707 — 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 `Assets/_MC_/Cscript/Component/MC_Component_Physics.cs:612` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (26 lines × 2) · ×1
  • Duplicated block (26 lines × 2) Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:650 — Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:650-675 | Assets/_MC_/Cscript/Static/MC_Static_Math.cs:145-170 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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 (25 lines × 2) · ×1
  • Duplicated block (25 lines × 2) Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:277 — Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:277-301 | Assets/_MC_/Cscript/Static/MC_Static_Navigation.cs:323-347 — before extracting anything, compare `Assets/_MC_/Cscript/Debug/Debug_Navigate.cs` and `Assets/_MC_/Cscript/Static/MC_Static_Navigation.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 225 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:277` 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, `Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:275` calls `Log` and `Assets/_MC_/Cscript/Static/MC_Static_Navigation.cs:320` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (23–25 lines × 3) · ×1
  • Duplicated block (23–25 lines × 3) Assets/_MC_/Cscript/Old/Chunk.cs:404 — Assets/_MC_/Cscript/Old/Chunk.cs:404-428 | Assets/_MC_/Cscript/Old/Chunk.cs:729-751 | Assets/_MC_/Cscript/Old/Chunk.cs:992-1016 — 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 `Assets/_MC_/Cscript/Old/Chunk.cs: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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code 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–24 lines × 3) · ×1
  • Duplicated block (23–24 lines × 3) Assets/_MC_/Cscript/Old/Chunk.cs:608 — Assets/_MC_/Cscript/Old/Chunk.cs:608-631 | Assets/_MC_/Cscript/Old/Chunk.cs:852-874 | Assets/_MC_/Cscript/Old/Chunk.cs:1156-1179 — 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 `Assets/_MC_/Cscript/Old/Chunk.cs:608` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those 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, `Assets/_MC_/Cscript/Old/Chunk.cs:605` calls `CreateTree` and `Assets/_MC_/Cscript/Old/Chunk.cs:845` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×1
  • Duplicated block (22 lines × 2) Assets/_MC_/Cscript/Component/MC_Component_AI.cs:268 — Assets/_MC_/Cscript/Component/MC_Component_AI.cs:268-289 | Assets/_MC_/Cscript/Component/MC_Component_AI.cs:638-659 — both copies are in the same file, so extract the 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 `Assets/_MC_/Cscript/Component/MC_Component_AI.cs:268` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (21–22 lines × 2) · ×1
  • Duplicated block (21–22 lines × 2) Assets/_MC_/Cscript/Service/MC_Service_MeshBuilder.cs:13 — Assets/_MC_/Cscript/Service/MC_Service_MeshBuilder.cs:13-33 | Assets/_MC_/Scene/TestScene/ChunkMeshDataCaculator/MC_Chunk_Renderer.cs:24-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, 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 `Assets/_MC_/Cscript/Service/MC_Service_MeshBuilder.cs:13` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×1
  • Duplicated block (21 lines × 2) Assets/_MC_/Cscript/UI/Old/BackPackManager.cs:486 — Assets/_MC_/Cscript/UI/Old/BackPackManager.cs:486-507 | Assets/_MC_/Cscript/UI/Old/BackPackManager.cs:520-540 — both copies are in the same file, so extract the 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 `Assets/_MC_/Cscript/UI/Old/BackPackManager.cs:486` it does not close everything it opens, so those 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 lines × 2) · ×1
  • Duplicated block (19 lines × 2) Assets/_MC_/Cscript/Service/MC_Service_World.cs:449 — Assets/_MC_/Cscript/Service/MC_Service_World.cs:449-467 | Assets/_MC_/Cscript/Service/MC_Service_World.cs:484-503 — both copies are in the same file, so extract the 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 `Assets/_MC_/Cscript/Service/MC_Service_World.cs:449` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code 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) Assets/_MC_/Cscript/Old/Chunk.cs:453 — Assets/_MC_/Cscript/Old/Chunk.cs:453-469 | Assets/_MC_/Cscript/Old/Chunk.cs:1338-1355 — both copies are in the same file, so extract the 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 `Assets/_MC_/Cscript/Old/Chunk.cs:453` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×1
  • Duplicated block (18 lines × 2) Assets/_MC_/Cscript/Service/MC_Service_World.cs:379 — Assets/_MC_/Cscript/Service/MC_Service_World.cs:379-399 | Assets/_MC_/Cscript/Service/MC_Service_World.cs:416-433 — both copies are in the same file, so extract the 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 `Assets/_MC_/Cscript/Service/MC_Service_World.cs:379` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code 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 lines × 2) · ×1
  • Duplicated block (17 lines × 2) Assets/_MC_/Cscript/Service/MC_Service_World.cs:1104 — Assets/_MC_/Cscript/Service/MC_Service_World.cs:1104-1120 | Assets/_MC_/Cscript/Service/MC_Service_World.cs:1184-1200 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (14 lines × 3) · ×1
  • Duplicated block (14 lines × 3) Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:288 — Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:288-301 | Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:382-395 | Assets/_MC_/Cscript/Static/MC_Static_Navigation.cs:334-347 — before extracting anything, compare `Assets/_MC_/Cscript/Debug/Debug_Navigate.cs` and `Assets/_MC_/Cscript/Static/MC_Static_Navigation.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 225 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:288` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (13–16 lines × 3) · ×1
  • Duplicated block (13–16 lines × 3) Assets/_MC_/Cscript/Old/Chunk.cs:1129 — Assets/_MC_/Cscript/Old/Chunk.cs:1129-1144 | Assets/_MC_/Cscript/Old/Chunk.cs:1614-1626 | Assets/_MC_/Cscript/Old/Chunk.cs:1661-1673 — 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 `Assets/_MC_/Cscript/Old/Chunk.cs:1129` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (15 lines × 3) · ×1
  • Duplicated block (15 lines × 3) Assets/_MC_/Cscript/Old/Chunk.cs:3506 — Assets/_MC_/Cscript/Old/Chunk.cs:3506-3520 | Assets/_MC_/Cscript/Old/Chunk.cs:3547-3561 | Assets/_MC_/Cscript/Old/Chunk.cs:3570-3584 — 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 `Assets/_MC_/Cscript/Old/Chunk.cs:3506` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (14–15 lines × 3) · ×1
  • Duplicated block (14–15 lines × 3) Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:84 — Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:84-98 | Assets/_MC_/Cscript/Static/MC_Static_Navigation.cs:141-154 | Assets/_MC_/Cscript/Static/MC_Static_Navigation.cs:182-195 — before extracting anything, compare `Assets/_MC_/Cscript/Debug/Debug_Navigate.cs` and `Assets/_MC_/Cscript/Static/MC_Static_Navigation.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 225 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:84` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 lines × 2) · ×1
  • Duplicated block (14 lines × 2) Assets/_MC_/Cscript/Service/MC_Service_Time.cs:287 — Assets/_MC_/Cscript/Service/MC_Service_Time.cs:287-300 | Assets/_MC_/Cscript/Service/MC_Service_Time.cs:352-365 — both copies are in the same file, so extract the 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 (14 lines × 5) · ×1
  • Duplicated block (14 lines × 5) Assets/_MC_/Cscript/Old/Chunk.cs:506 — Assets/_MC_/Cscript/Old/Chunk.cs:506-519 | Assets/_MC_/Cscript/Old/Chunk.cs:520-539 | Assets/_MC_/Cscript/Old/Chunk.cs:769-783 | Assets/_MC_/Cscript/Old/Chunk.cs:1383-1396 | Assets/_MC_/Cscript/Old/Chunk.cs:1397-1416 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code 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 × 2) · ×1
  • Duplicated block (8 lines × 2) Assets/_MC_/Cscript/UI/Old/CanvasManager.cs:427 — Assets/_MC_/Cscript/UI/Old/CanvasManager.cs:427-434 | Assets/_MC_/Cscript/UI/Old/CanvasManager.cs:446-453 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×1
  • Duplicated block (6 lines × 2) Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:467 — Assets/_MC_/Cscript/Debug/Debug_Navigate.cs:467-472 | Assets/_MC_/Cscript/Static/MC_Static_Math.cs:130-135 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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 · Edited copy of a member (15 corresponding lines) · ×1
  • Edited copy of a member (15 corresponding lines) Assets/_MC_/Scene/TestScene/test csharp/TerrainTest_Voxel.cs:144 — Assets/_MC_/Scene/TestScene/test csharp/TerrainTest_Voxel.cs:144-160 | Assets/_MC_/Scene/TestScene/test csharp/TerrainTest_Voxel.cs:164-178 — 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 × 2) · ×1
  • Duplicated block (7 lines × 2) Assets/_MC_/Scene/TestScene/test csharp/TerrainTest_Voxel.cs:108 — Assets/_MC_/Scene/TestScene/test csharp/TerrainTest_Voxel.cs:108-114 | Assets/_MC_/Scene/TestScene/test csharp/TerrainTest_Voxel.cs:123-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. Read the line range as the matched WINDOW rather than a finished unit: at `Assets/_MC_/Scene/TestScene/test csharp/TerrainTest_Voxel.cs:108` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D6 · Cohesion (LCOM4) · Low cohesion · ×1
  • Low cohesion: MC_Component_Physics (LCOM4 5) Assets/_MC_/Cscript/Component/MC_Component_Physics.cs:10 — MC_Component_Physics's methods fall into 5 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 5 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.
IC1 · Incompleteness & stubs · Both branches are identical · ×1
  • Both branches are identical — the condition decides nothing Assets/_MC_/Cscript/Static/MC_Static_Name.cs:43 — The `if` and its `else` contain the same 1 statement, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.
P1 · CI/CD gates · No CI pipeline · ×1
  • No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
Minor — 43 finding(s)
IC1 · Incompleteness & stubs · Commented-out code · ×35
  • Commented-out code Assets/Resources/Prefeb/Entity/DropBlock/DropBlock.cs:33 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Assets/Resources/Prefeb/Entity/DropBlock/DropBlock.cs:34 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Assets/Resources/Prefeb/Entity/DropBlock/DropBlock.cs:44 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Assets/Resources/Prefeb/Entity/DropBlock/DropBlock.cs:250 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Assets/Resources/Prefeb/Entity/DropBlock/DropBlock.cs:252 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Assets/Resources/Prefeb/Entity/TNT/Entity_TNT.cs:26 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Assets/Resources/Prefeb/Entity/TNT/Entity_TNT.cs:76 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Assets/Resources/Prefeb/Entity/TNT/Entity_TNT.cs:77 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Assets/Resources/Prefeb/Entity/TNT/Entity_TNT.cs:78 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Assets/Resources/Prefeb/Entity/TNT/Entity_TNT.cs:79 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Assets/Resources/Prefeb/Entity/TNT/Entity_TNT.cs:148 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Assets/Resources/Prefeb/Entity/TNT/Entity_TNT.cs:227 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Assets/Resources/Prefeb/Entity/TNT/Entity_TNT.cs:306 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Assets/_MC_/Cscript/AnimationScripts/FlashLightMoving.cs:15 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Assets/_MC_/Cscript/AnimationScripts/SunMoving.cs:52 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Assets/_MC_/Cscript/AnimationScripts/SunMoving.cs:140 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Assets/_MC_/Cscript/AuxiliaryScripts/ButtomColor.cs:71 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Assets/_MC_/Cscript/AuxiliaryScripts/CloudManager.cs:102 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Assets/_MC_/Cscript/AuxiliaryScripts/CloudManager.cs:173 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Assets/_MC_/Cscript/AuxiliaryScripts/CloudManager.cs:176 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Assets/_MC_/Cscript/AuxiliaryScripts/CloudManager.cs:177 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Assets/_MC_/Cscript/AuxiliaryScripts/CloudManager.cs:180 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Assets/_MC_/Cscript/AuxiliaryScripts/CloudManager.cs:181 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Assets/_MC_/Cscript/AuxiliaryScripts/CloudManager.cs:184 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Assets/_MC_/Cscript/AuxiliaryScripts/CloudManager.cs:204 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • + 10 more in this group — see findings.md.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found ProjectSettings/ProjectVersion.txt:1 — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `ProjectSettings/ProjectVersion.txt` makes this repository a deployable product (line 1).
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
M3 · Folder & project structure · No src/ separation · ×1
  • No src/ separation — Nothing in the layout marks which files are the product and which are its tooling: no production source was found set apart in a directory of its own.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets — this tree has no MSBuild project file, so CodeQL's csharp pack (which traces a build) and NuGet security analyzers (which are referenced from a project) have nothing to attach to — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
X5 · Nullable reference types · Nullable reference types not enabled everywhere · ×1
  • Nullable reference types not enabled everywhere — 0/109 C# file(s) are in a nullable-enabled context. This repository commits no project file, so nothing sets <Nullable>enable</Nullable> for it: a file is enabled only by its own `#nullable enable`, by a Unity `csc.rsp` with `-nullable:enable` for its assembly, or as a file-based app (`#:` directives) whose `#:property Nullable` does not turn it off. NRTs catch a whole class of null-deref bugs at compile time.
X7 · Silent fallback defaults · Silent fallback default on parse failure · ×1
  • Silent fallback default on parse failure Assets/_MC_/Cscript/UI/Old/CommandManager.cs:123 — `CheckCommand` falls back to `"1"` when `match.Groups[2].Success` 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.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-f65692a85c364d8886dbbe706cf329dc/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-f65692a85c364d8886dbbe706cf329dc/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .0artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesnuget—nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan0—
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 16 file(s) — `Assets/Resources/Items/ItemScripts/Item_DataBase.cs`, `Assets/Resources/Prefeb/Entity/DropBlock/DropBlock.cs`, `Assets/_MC_/Cscript/Class/MC_Class_Chunk.cs`, `Assets/_MC_/Cscript/Class/MC_Class_Entity.cs`, `Assets/_MC_/Cscript/Class/MC_Class_Time.cs`, … (+11 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D36 · Supply-chain Provenance & Signingprovenance—provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciesnone (dependency manifest found, not scanned for vulnerabilities here)—none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Unity UPM manifest (Packages/manifest.json or a package's package.json) — not scanned yet).0—

Run 01a1e969-99a0-7be7-ba82-2ae605eebb5e · 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