Public report of CloudNetService/CloudNet, published 16 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 16 November 2026, 17:13 UTC · Survey ID cd_0913a788ad6349e3a65a6633e4a1fff2
CloudNetService/CloudNet
Measured 16 November 2026, 17:12 UTC, at code version 4aa3d7f
First survey, so nothing to compare with yet
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 114,550 lines of product code in 53 projects, tests not counted · Estimated rebuild effort: about 1.1 person-years · Weakest lens: Production Readiness, 56.7
Findings by how serious they are
30 critical370 serious62 minor
16 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
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
16 November 2026, 17:12 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 ▸
54of 54 dimensions measured by tools.
445of 462 findings point to an exact file and line, so you can open each one in the code. The other 17 concern the repository as a whole, such as missing documentation.
54dimensions across 6 lenses, read from 114,550 lines of product code in 53 projects.
CloudNetService/CloudNet falls short of our standard for production, in part because it has packages under a licence on your banned list. It scores 61.7 out of 100 and is rated Adequate, and 26 of its 30 critical findings are security problems.
Production Readiness, at 56.7, is the weakest lens and counts most in the score. The best first step is replacing the four packages under a banned licence, worth about 5.0 points. Recording design decisions comes next, worth about 4.1 points. Raising Production Readiness to 70 would lift the score to about 64.9.
Seventeen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Eight secrets can leak from the build pipeline, and four packages carry licence risk. Pinning each tool to an exact version, limiting each secret to its own step and replacing or clearing the banned-licence packages would close these risks. The password or key in the code's history needs replacing, with the old one switched off.
The product code is 114,550 lines, about €160,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 56.7 to 70, the lowest score rated Strong, the score would rise from 61.7 to about 64.9.
Code composition: what the lines of code are
Product code 93%Tests 7%
Rebuild cost: about €160,000 · Estimate
Cost to rebuild
€54,000 to €270,000, for 905 to 2,871 hours of work, about 1.1 person-years for 1 to 3 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.8 at a score of 62. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 114,550 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: 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. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 4 Banned license finding(s) in License Compliance.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts.
Raises the score by about 4.1 points · Low effort · ADR Quality
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.
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 €160,000 to build again, about 1.1 person-years of work. Its weakest lens is Production Readiness, at 56.7 (Adequate). 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 4 Banned license finding(s) in License Compliance. Of all the actions in this report, it raises the score most for the work it takes: about 5.0 points for low effort, because it clears the 4 License Compliance findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
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.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
354 modules, with 1389 dependencies between them. 14 loops run through 36 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 314 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
driver.document uses driver.network.buffer, so a change to driver.network.buffer can break driver.document, while a change to driver.document can't break driver.network.buffer.
Position
Below the diagonal: driver.document uses a module listed above it, which is the healthy direction.
driver.network.protocol uses driver.network.buffer, so a change to driver.network.buffer can break driver.network.protocol, while a change to driver.network.protocol can't break driver.network.buffer.
Position
Below the diagonal: driver.network.protocol uses a module listed above it, which is the healthy direction.
7→10 driver.network.protocol uses driver.networkpart of a loop✕
Connections
3 pairs of types, where a type in driver.network.protocol uses a type in driver.network.
driver.network.protocol uses driver.network, so a change to driver.network can break driver.network.protocol, while a change to driver.network.protocol can't break driver.network.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
driver.network uses driver.network.protocol, so a change to driver.network.protocol can break driver.network, while a change to driver.network can't break driver.network.protocol.
Position
Below the diagonal: driver.network uses a module listed above it, which is the healthy direction.
ext.platforminject.api uses driver.inject, so a change to driver.inject can break ext.platforminject.api, while a change to ext.platforminject.api can't break driver.inject.
Position
Below the diagonal: ext.platforminject.api uses a module listed above it, which is the healthy direction.
driver.network.rpc.factory uses driver.network, so a change to driver.network can break driver.network.rpc.factory, while a change to driver.network.rpc.factory can't break driver.network.
Position
Below the diagonal: driver.network.rpc.factory uses a module listed above it, which is the healthy direction.
13→17 driver.network.rpc.factory uses driver.network.rpcpart of a loop✕
Connections
3 pairs of types, where a type in driver.network.rpc.factory uses a type in driver.network.rpc.
driver.network.rpc.factory uses driver.network.rpc, so a change to driver.network.rpc can break driver.network.rpc.factory, while a change to driver.network.rpc.factory can't break driver.network.rpc.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
driver.service uses driver.document, so a change to driver.document can break driver.service, while a change to driver.service can't break driver.document.
Position
Below the diagonal: driver.service uses a module listed above it, which is the healthy direction.
driver.service uses driver.network, so a change to driver.network can break driver.service, while a change to driver.service can't break driver.network.
Position
Below the diagonal: driver.service uses a module listed above it, which is the healthy direction.
14→18 driver.service uses driver.providerpart of a loop✕
Connections
1 pair of types, where a type in driver.service uses a type in driver.provider.
driver.service uses driver.provider, so a change to driver.provider can break driver.service, while a change to driver.service can't break driver.provider.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→23 driver.service uses driver.channelpart of a loop✕
Connections
1 pair of types, where a type in driver.service uses a type in driver.channel.
driver.service uses driver.channel, so a change to driver.channel can break driver.service, while a change to driver.service can't break driver.channel.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
ext.platforminject.api.spi uses driver.base, so a change to driver.base can break ext.platforminject.api.spi, while a change to ext.platforminject.api.spi can't break driver.base.
Position
Below the diagonal: ext.platforminject.api.spi uses a module listed above it, which is the healthy direction.
ext.platforminject.api.spi uses ext.platforminject.api, so a change to ext.platforminject.api can break ext.platforminject.api.spi, while a change to ext.platforminject.api.spi can't break ext.platforminject.api.
Position
Below the diagonal: ext.platforminject.api.spi uses a module listed above it, which is the healthy direction.
driver.impl.module uses driver.event, so a change to driver.event can break driver.impl.module, while a change to driver.impl.module can't break driver.event.
Position
Below the diagonal: driver.impl.module uses a module listed above it, which is the healthy direction.
driver.impl.module uses driver.inject, so a change to driver.inject can break driver.impl.module, while a change to driver.impl.module can't break driver.inject.
Position
Below the diagonal: driver.impl.module uses a module listed above it, which is the healthy direction.
driver.impl.module uses driver.registry, so a change to driver.registry can break driver.impl.module, while a change to driver.impl.module can't break driver.registry.
Position
Below the diagonal: driver.impl.module uses a module listed above it, which is the healthy direction.
driver.impl.module uses driver.network, so a change to driver.network can break driver.impl.module, while a change to driver.impl.module can't break driver.network.
Position
Below the diagonal: driver.impl.module uses a module listed above it, which is the healthy direction.
driver.impl.module uses driver.service, so a change to driver.service can break driver.impl.module, while a change to driver.impl.module can't break driver.service.
Position
Below the diagonal: driver.impl.module uses a module listed above it, which is the healthy direction.
driver.network.rpc uses driver.network.buffer, so a change to driver.network.buffer can break driver.network.rpc, while a change to driver.network.rpc can't break driver.network.buffer.
Position
Below the diagonal: driver.network.rpc uses a module listed above it, which is the healthy direction.
driver.network.rpc uses driver.network, so a change to driver.network can break driver.network.rpc, while a change to driver.network.rpc can't break driver.network.
Position
Below the diagonal: driver.network.rpc uses a module listed above it, which is the healthy direction.
driver.network.rpc uses driver.network.rpc.factory, so a change to driver.network.rpc.factory can break driver.network.rpc, while a change to driver.network.rpc can't break driver.network.rpc.factory.
Position
Below the diagonal: driver.network.rpc uses a module listed above it, which is the healthy direction.
driver.provider uses driver.document, so a change to driver.document can break driver.provider, while a change to driver.provider can't break driver.document.
Position
Below the diagonal: driver.provider uses a module listed above it, which is the healthy direction.
driver.provider uses driver.service, so a change to driver.service can break driver.provider, while a change to driver.provider can't break driver.service.
Position
Below the diagonal: driver.provider uses a module listed above it, which is the healthy direction.
18→23 driver.provider uses driver.channelpart of a loop✕
Connections
2 pairs of types, where a type in driver.provider uses a type in driver.channel.
driver.provider uses driver.channel, so a change to driver.channel can break driver.provider, while a change to driver.provider can't break driver.channel.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
modules.bridge.player uses driver.base, so a change to driver.base can break modules.bridge.player, while a change to modules.bridge.player can't break driver.base.
Position
Below the diagonal: modules.bridge.player uses a module listed above it, which is the healthy direction.
modules.bridge.player uses driver.document, so a change to driver.document can break modules.bridge.player, while a change to modules.bridge.player can't break driver.document.
Position
Below the diagonal: modules.bridge.player uses a module listed above it, which is the healthy direction.
modules.bridge.player uses driver.network, so a change to driver.network can break modules.bridge.player, while a change to modules.bridge.player can't break driver.network.
Position
Below the diagonal: modules.bridge.player uses a module listed above it, which is the healthy direction.
modules.bridge.player uses driver.service, so a change to driver.service can break modules.bridge.player, while a change to modules.bridge.player can't break driver.service.
Position
Below the diagonal: modules.bridge.player uses a module listed above it, which is the healthy direction.
node.impl.version uses driver.base, so a change to driver.base can break node.impl.version, while a change to node.impl.version can't break driver.base.
Position
Below the diagonal: node.impl.version uses a module listed above it, which is the healthy direction.
node.impl.version uses driver.event, so a change to driver.event can break node.impl.version, while a change to node.impl.version can't break driver.event.
Position
Below the diagonal: node.impl.version uses a module listed above it, which is the healthy direction.
node.impl.version uses driver.language, so a change to driver.language can break node.impl.version, while a change to node.impl.version can't break driver.language.
Position
Below the diagonal: node.impl.version uses a module listed above it, which is the healthy direction.
node.impl.version uses driver.document, so a change to driver.document can break node.impl.version, while a change to node.impl.version can't break driver.document.
Position
Below the diagonal: node.impl.version uses a module listed above it, which is the healthy direction.
node.impl.version uses driver.service, so a change to driver.service can break node.impl.version, while a change to node.impl.version can't break driver.service.
Position
Below the diagonal: node.impl.version uses a module listed above it, which is the healthy direction.
wrapper.configuration uses driver.network, so a change to driver.network can break wrapper.configuration, while a change to wrapper.configuration can't break driver.network.
Position
Below the diagonal: wrapper.configuration uses a module listed above it, which is the healthy direction.
wrapper.configuration uses driver.service, so a change to driver.service can break wrapper.configuration, while a change to wrapper.configuration can't break driver.service.
Position
Below the diagonal: wrapper.configuration uses a module listed above it, which is the healthy direction.
wrapper.holder uses driver.document, so a change to driver.document can break wrapper.holder, while a change to wrapper.holder can't break driver.document.
Position
Below the diagonal: wrapper.holder uses a module listed above it, which is the healthy direction.
wrapper.holder uses driver.service, so a change to driver.service can break wrapper.holder, while a change to wrapper.holder can't break driver.service.
Position
Below the diagonal: wrapper.holder uses a module listed above it, which is the healthy direction.
driver.channel uses driver.network.buffer, so a change to driver.network.buffer can break driver.channel, while a change to driver.channel can't break driver.network.buffer.
Position
Below the diagonal: driver.channel uses a module listed above it, which is the healthy direction.
driver.channel uses driver.service, so a change to driver.service can break driver.channel, while a change to driver.channel can't break driver.service.
Position
Below the diagonal: driver.channel uses a module listed above it, which is the healthy direction.
driver.channel uses driver.provider, so a change to driver.provider can break driver.channel, while a change to driver.channel can't break driver.provider.
Position
Below the diagonal: driver.channel uses a module listed above it, which is the healthy direction.
modules.bridge uses driver.service, so a change to driver.service can break modules.bridge, while a change to modules.bridge can't break driver.service.
Position
Below the diagonal: modules.bridge uses a module listed above it, which is the healthy direction.
modules.bridge uses driver.provider, so a change to driver.provider can break modules.bridge, while a change to modules.bridge can't break driver.provider.
Position
Below the diagonal: modules.bridge uses a module listed above it, which is the healthy direction.
modules.bridge uses modules.bridge.player, so a change to modules.bridge.player can break modules.bridge, while a change to modules.bridge can't break modules.bridge.player.
Position
Below the diagonal: modules.bridge uses a module listed above it, which is the healthy direction.
modules.bridge uses wrapper.configuration, so a change to wrapper.configuration can break modules.bridge, while a change to modules.bridge can't break wrapper.configuration.
Position
Below the diagonal: modules.bridge uses a module listed above it, which is the healthy direction.
node.cluster uses driver.network.protocol, so a change to driver.network.protocol can break node.cluster, while a change to node.cluster can't break driver.network.protocol.
Position
Below the diagonal: node.cluster uses a module listed above it, which is the healthy direction.
node.impl.setup uses driver.language, so a change to driver.language can break node.impl.setup, while a change to node.impl.setup can't break driver.language.
Position
Below the diagonal: node.impl.setup uses a module listed above it, which is the healthy direction.
node.impl.setup uses driver.service, so a change to driver.service can break node.impl.setup, while a change to node.impl.setup can't break driver.service.
Position
Below the diagonal: node.impl.setup uses a module listed above it, which is the healthy direction.
node.impl.setup uses driver.provider, so a change to driver.provider can break node.impl.setup, while a change to node.impl.setup can't break driver.provider.
Position
Below the diagonal: node.impl.setup uses a module listed above it, which is the healthy direction.
node.impl.setup uses node.impl.version, so a change to node.impl.version can break node.impl.setup, while a change to node.impl.setup can't break node.impl.version.
Position
Below the diagonal: node.impl.setup uses a module listed above it, which is the healthy direction.
driver.event.events.channel uses driver.network.buffer, so a change to driver.network.buffer can break driver.event.events.channel, while a change to driver.event.events.channel can't break driver.network.buffer.
Position
Below the diagonal: driver.event.events.channel uses a module listed above it, which is the healthy direction.
driver.event.events.channel uses driver.network, so a change to driver.network can break driver.event.events.channel, while a change to driver.event.events.channel can't break driver.network.
Position
Below the diagonal: driver.event.events.channel uses a module listed above it, which is the healthy direction.
driver.event.events.channel uses driver.channel, so a change to driver.channel can break driver.event.events.channel, while a change to driver.event.events.channel can't break driver.channel.
Position
Below the diagonal: driver.event.events.channel uses a module listed above it, which is the healthy direction.
modules.bridge.impl.platform uses driver.event, so a change to driver.event can break modules.bridge.impl.platform, while a change to modules.bridge.impl.platform can't break driver.event.
Position
Below the diagonal: modules.bridge.impl.platform uses a module listed above it, which is the healthy direction.
modules.bridge.impl.platform uses driver.network, so a change to driver.network can break modules.bridge.impl.platform, while a change to modules.bridge.impl.platform can't break driver.network.
Position
Below the diagonal: modules.bridge.impl.platform uses a module listed above it, which is the healthy direction.
modules.bridge.impl.platform uses driver.network.rpc.factory, so a change to driver.network.rpc.factory can break modules.bridge.impl.platform, while a change to modules.bridge.impl.platform can't break driver.network.rpc.factory.
Position
Below the diagonal: modules.bridge.impl.platform uses a module listed above it, which is the healthy direction.
modules.bridge.impl.platform uses driver.service, so a change to driver.service can break modules.bridge.impl.platform, while a change to modules.bridge.impl.platform can't break driver.service.
Position
Below the diagonal: modules.bridge.impl.platform uses a module listed above it, which is the healthy direction.
modules.bridge.impl.platform uses driver.network.rpc, so a change to driver.network.rpc can break modules.bridge.impl.platform, while a change to modules.bridge.impl.platform can't break driver.network.rpc.
Position
Below the diagonal: modules.bridge.impl.platform uses a module listed above it, which is the healthy direction.
modules.bridge.impl.platform uses driver.provider, so a change to driver.provider can break modules.bridge.impl.platform, while a change to modules.bridge.impl.platform can't break driver.provider.
Position
Below the diagonal: modules.bridge.impl.platform uses a module listed above it, which is the healthy direction.
modules.bridge.impl.platform uses modules.bridge.player, so a change to modules.bridge.player can break modules.bridge.impl.platform, while a change to modules.bridge.impl.platform can't break modules.bridge.player.
Position
Below the diagonal: modules.bridge.impl.platform uses a module listed above it, which is the healthy direction.
modules.bridge.impl.platform uses wrapper.configuration, so a change to wrapper.configuration can break modules.bridge.impl.platform, while a change to modules.bridge.impl.platform can't break wrapper.configuration.
Position
Below the diagonal: modules.bridge.impl.platform uses a module listed above it, which is the healthy direction.
modules.bridge.impl.platform uses wrapper.holder, so a change to wrapper.holder can break modules.bridge.impl.platform, while a change to modules.bridge.impl.platform can't break wrapper.holder.
Position
Below the diagonal: modules.bridge.impl.platform uses a module listed above it, which is the healthy direction.
modules.bridge.impl.platform uses modules.bridge, so a change to modules.bridge can break modules.bridge.impl.platform, while a change to modules.bridge.impl.platform can't break modules.bridge.
Position
Below the diagonal: modules.bridge.impl.platform uses a module listed above it, which is the healthy direction.
modules.npc.impl.node uses driver.event, so a change to driver.event can break modules.npc.impl.node, while a change to modules.npc.impl.node can't break driver.event.
Position
Below the diagonal: modules.npc.impl.node uses a module listed above it, which is the healthy direction.
modules.npc.impl.node uses driver.language, so a change to driver.language can break modules.npc.impl.node, while a change to modules.npc.impl.node can't break driver.language.
Position
Below the diagonal: modules.npc.impl.node uses a module listed above it, which is the healthy direction.
modules.npc.impl.node uses driver.inject, so a change to driver.inject can break modules.npc.impl.node, while a change to modules.npc.impl.node can't break driver.inject.
Position
Below the diagonal: modules.npc.impl.node uses a module listed above it, which is the healthy direction.
modules.npc.impl.node uses driver.impl.module, so a change to driver.impl.module can break modules.npc.impl.node, while a change to modules.npc.impl.node can't break driver.impl.module.
Position
Below the diagonal: modules.npc.impl.node uses a module listed above it, which is the healthy direction.
modules.npc.impl.node uses driver.provider, so a change to driver.provider can break modules.npc.impl.node, while a change to modules.npc.impl.node can't break driver.provider.
Position
Below the diagonal: modules.npc.impl.node uses a module listed above it, which is the healthy direction.
modules.npc.impl.node uses modules.bridge, so a change to modules.bridge can break modules.npc.impl.node, while a change to modules.npc.impl.node can't break modules.bridge.
Position
Below the diagonal: modules.npc.impl.node uses a module listed above it, which is the healthy direction.
modules.npc.impl.platform.bukkit uses driver.event, so a change to driver.event can break modules.npc.impl.platform.bukkit, while a change to modules.npc.impl.platform.bukkit can't break driver.event.
Position
Below the diagonal: modules.npc.impl.platform.bukkit uses a module listed above it, which is the healthy direction.
modules.npc.impl.platform.bukkit uses driver, so a change to driver can break modules.npc.impl.platform.bukkit, while a change to modules.npc.impl.platform.bukkit can't break driver.
Position
Below the diagonal: modules.npc.impl.platform.bukkit uses a module listed above it, which is the healthy direction.
modules.npc.impl.platform.bukkit uses ext.platforminject.api, so a change to ext.platforminject.api can break modules.npc.impl.platform.bukkit, while a change to modules.npc.impl.platform.bukkit can't break ext.platforminject.api.
Position
Below the diagonal: modules.npc.impl.platform.bukkit uses a module listed above it, which is the healthy direction.
modules.npc.impl.platform.bukkit uses driver.service, so a change to driver.service can break modules.npc.impl.platform.bukkit, while a change to modules.npc.impl.platform.bukkit can't break driver.service.
Position
Below the diagonal: modules.npc.impl.platform.bukkit uses a module listed above it, which is the healthy direction.
modules.npc.impl.platform.bukkit uses driver.impl.module, so a change to driver.impl.module can break modules.npc.impl.platform.bukkit, while a change to modules.npc.impl.platform.bukkit can't break driver.impl.module.
Position
Below the diagonal: modules.npc.impl.platform.bukkit uses a module listed above it, which is the healthy direction.
modules.npc.impl.platform.bukkit uses driver.provider, so a change to driver.provider can break modules.npc.impl.platform.bukkit, while a change to modules.npc.impl.platform.bukkit can't break driver.provider.
Position
Below the diagonal: modules.npc.impl.platform.bukkit uses a module listed above it, which is the healthy direction.
modules.npc.impl.platform.bukkit uses modules.bridge.player, so a change to modules.bridge.player can break modules.npc.impl.platform.bukkit, while a change to modules.npc.impl.platform.bukkit can't break modules.bridge.player.
Position
Below the diagonal: modules.npc.impl.platform.bukkit uses a module listed above it, which is the healthy direction.
modules.npc.impl.platform.bukkit uses wrapper.configuration, so a change to wrapper.configuration can break modules.npc.impl.platform.bukkit, while a change to modules.npc.impl.platform.bukkit can't break wrapper.configuration.
Position
Below the diagonal: modules.npc.impl.platform.bukkit uses a module listed above it, which is the healthy direction.
modules.npc.impl.platform.bukkit uses modules.bridge, so a change to modules.bridge can break modules.npc.impl.platform.bukkit, while a change to modules.npc.impl.platform.bukkit can't break modules.bridge.
Position
Below the diagonal: modules.npc.impl.platform.bukkit uses a module listed above it, which is the healthy direction.
modules.signs.impl.platform uses driver.event, so a change to driver.event can break modules.signs.impl.platform, while a change to modules.signs.impl.platform can't break driver.event.
Position
Below the diagonal: modules.signs.impl.platform uses a module listed above it, which is the healthy direction.
modules.signs.impl.platform uses driver.registry, so a change to driver.registry can break modules.signs.impl.platform, while a change to modules.signs.impl.platform can't break driver.registry.
Position
Below the diagonal: modules.signs.impl.platform uses a module listed above it, which is the healthy direction.
modules.signs.impl.platform uses driver.service, so a change to driver.service can break modules.signs.impl.platform, while a change to modules.signs.impl.platform can't break driver.service.
Position
Below the diagonal: modules.signs.impl.platform uses a module listed above it, which is the healthy direction.
modules.signs.impl.platform uses driver.provider, so a change to driver.provider can break modules.signs.impl.platform, while a change to modules.signs.impl.platform can't break driver.provider.
Position
Below the diagonal: modules.signs.impl.platform uses a module listed above it, which is the healthy direction.
modules.signs.impl.platform uses modules.bridge.player, so a change to modules.bridge.player can break modules.signs.impl.platform, while a change to modules.signs.impl.platform can't break modules.bridge.player.
Position
Below the diagonal: modules.signs.impl.platform uses a module listed above it, which is the healthy direction.
modules.signs.impl.platform uses wrapper.configuration, so a change to wrapper.configuration can break modules.signs.impl.platform, while a change to modules.signs.impl.platform can't break wrapper.configuration.
Position
Below the diagonal: modules.signs.impl.platform uses a module listed above it, which is the healthy direction.
modules.signs.impl.platform uses modules.bridge, so a change to modules.bridge can break modules.signs.impl.platform, while a change to modules.signs.impl.platform can't break modules.bridge.
Position
Below the diagonal: modules.signs.impl.platform uses a module listed above it, which is the healthy direction.
modules.bridge.impl.platform.minestom uses driver.event, so a change to driver.event can break modules.bridge.impl.platform.minestom, while a change to modules.bridge.impl.platform.minestom can't break driver.event.
Position
Below the diagonal: modules.bridge.impl.platform.minestom uses a module listed above it, which is the healthy direction.
modules.bridge.impl.platform.minestom uses driver.registry, so a change to driver.registry can break modules.bridge.impl.platform.minestom, while a change to modules.bridge.impl.platform.minestom can't break driver.registry.
Position
Below the diagonal: modules.bridge.impl.platform.minestom uses a module listed above it, which is the healthy direction.
modules.bridge.impl.platform.minestom uses driver.network, so a change to driver.network can break modules.bridge.impl.platform.minestom, while a change to modules.bridge.impl.platform.minestom can't break driver.network.
Position
Below the diagonal: modules.bridge.impl.platform.minestom uses a module listed above it, which is the healthy direction.
modules.bridge.impl.platform.minestom uses ext.platforminject.api, so a change to ext.platforminject.api can break modules.bridge.impl.platform.minestom, while a change to modules.bridge.impl.platform.minestom can't break ext.platforminject.api.
Position
Below the diagonal: modules.bridge.impl.platform.minestom uses a module listed above it, which is the healthy direction.
modules.bridge.impl.platform.minestom uses driver.network.rpc.factory, so a change to driver.network.rpc.factory can break modules.bridge.impl.platform.minestom, while a change to modules.bridge.impl.platform.minestom can't break driver.network.rpc.factory.
Position
Below the diagonal: modules.bridge.impl.platform.minestom uses a module listed above it, which is the healthy direction.
modules.bridge.impl.platform.minestom uses driver.service, so a change to driver.service can break modules.bridge.impl.platform.minestom, while a change to modules.bridge.impl.platform.minestom can't break driver.service.
Position
Below the diagonal: modules.bridge.impl.platform.minestom uses a module listed above it, which is the healthy direction.
modules.bridge.impl.platform.minestom uses driver.impl.module, so a change to driver.impl.module can break modules.bridge.impl.platform.minestom, while a change to modules.bridge.impl.platform.minestom can't break driver.impl.module.
Position
Below the diagonal: modules.bridge.impl.platform.minestom uses a module listed above it, which is the healthy direction.
modules.bridge.impl.platform.minestom uses driver.provider, so a change to driver.provider can break modules.bridge.impl.platform.minestom, while a change to modules.bridge.impl.platform.minestom can't break driver.provider.
Position
Below the diagonal: modules.bridge.impl.platform.minestom uses a module listed above it, which is the healthy direction.
modules.bridge.impl.platform.minestom uses modules.bridge.player, so a change to modules.bridge.player can break modules.bridge.impl.platform.minestom, while a change to modules.bridge.impl.platform.minestom can't break modules.bridge.player.
Position
Below the diagonal: modules.bridge.impl.platform.minestom uses a module listed above it, which is the healthy direction.
modules.bridge.impl.platform.minestom uses wrapper.configuration, so a change to wrapper.configuration can break modules.bridge.impl.platform.minestom, while a change to modules.bridge.impl.platform.minestom can't break wrapper.configuration.
Position
Below the diagonal: modules.bridge.impl.platform.minestom uses a module listed above it, which is the healthy direction.
modules.bridge.impl.platform.minestom uses wrapper.holder, so a change to wrapper.holder can break modules.bridge.impl.platform.minestom, while a change to modules.bridge.impl.platform.minestom can't break wrapper.holder.
Position
Below the diagonal: modules.bridge.impl.platform.minestom uses a module listed above it, which is the healthy direction.
modules.bridge.impl.platform.minestom uses modules.bridge, so a change to modules.bridge can break modules.bridge.impl.platform.minestom, while a change to modules.bridge.impl.platform.minestom can't break modules.bridge.
Position
Below the diagonal: modules.bridge.impl.platform.minestom uses a module listed above it, which is the healthy direction.
modules.bridge.impl.platform.minestom uses modules.bridge.impl.platform, so a change to modules.bridge.impl.platform can break modules.bridge.impl.platform.minestom, while a change to modules.bridge.impl.platform.minestom can't break modules.bridge.impl.platform.
Position
Below the diagonal: modules.bridge.impl.platform.minestom uses a module listed above it, which is the healthy direction.
modules.signs.impl.node uses driver.event, so a change to driver.event can break modules.signs.impl.node, while a change to modules.signs.impl.node can't break driver.event.
Position
Below the diagonal: modules.signs.impl.node uses a module listed above it, which is the healthy direction.
modules.signs.impl.node uses driver.language, so a change to driver.language can break modules.signs.impl.node, while a change to modules.signs.impl.node can't break driver.language.
Position
Below the diagonal: modules.signs.impl.node uses a module listed above it, which is the healthy direction.
modules.signs.impl.node uses driver.inject, so a change to driver.inject can break modules.signs.impl.node, while a change to modules.signs.impl.node can't break driver.inject.
Position
Below the diagonal: modules.signs.impl.node uses a module listed above it, which is the healthy direction.
modules.signs.impl.node uses driver.registry, so a change to driver.registry can break modules.signs.impl.node, while a change to modules.signs.impl.node can't break driver.registry.
Position
Below the diagonal: modules.signs.impl.node uses a module listed above it, which is the healthy direction.
modules.signs.impl.node uses driver.impl.module, so a change to driver.impl.module can break modules.signs.impl.node, while a change to modules.signs.impl.node can't break driver.impl.module.
Position
Below the diagonal: modules.signs.impl.node uses a module listed above it, which is the healthy direction.
modules.signs.impl.node uses driver.provider, so a change to driver.provider can break modules.signs.impl.node, while a change to modules.signs.impl.node can't break driver.provider.
Position
Below the diagonal: modules.signs.impl.node uses a module listed above it, which is the healthy direction.
modules.signs.impl.node uses modules.bridge, so a change to modules.bridge can break modules.signs.impl.node, while a change to modules.signs.impl.node can't break modules.bridge.
Position
Below the diagonal: modules.signs.impl.node uses a module listed above it, which is the healthy direction.
modules.signs.impl.node uses driver.event.events.channel, so a change to driver.event.events.channel can break modules.signs.impl.node, while a change to modules.signs.impl.node can't break driver.event.events.channel.
Position
Below the diagonal: modules.signs.impl.node uses a module listed above it, which is the healthy direction.
node.impl.provider uses driver.event, so a change to driver.event can break node.impl.provider, while a change to node.impl.provider can't break driver.event.
Position
Below the diagonal: node.impl.provider uses a module listed above it, which is the healthy direction.
node.impl.provider uses driver.language, so a change to driver.language can break node.impl.provider, while a change to node.impl.provider can't break driver.language.
Position
Below the diagonal: node.impl.provider uses a module listed above it, which is the healthy direction.
node.impl.provider uses driver.network, so a change to driver.network can break node.impl.provider, while a change to node.impl.provider can't break driver.network.
Position
Below the diagonal: node.impl.provider uses a module listed above it, which is the healthy direction.
node.impl.provider uses node.config, so a change to node.config can break node.impl.provider, while a change to node.impl.provider can't break node.config.
Position
Below the diagonal: node.impl.provider uses a module listed above it, which is the healthy direction.
node.impl.provider uses driver.network.rpc.factory, so a change to driver.network.rpc.factory can break node.impl.provider, while a change to node.impl.provider can't break driver.network.rpc.factory.
Position
Below the diagonal: node.impl.provider uses a module listed above it, which is the healthy direction.
node.impl.provider uses driver.service, so a change to driver.service can break node.impl.provider, while a change to node.impl.provider can't break driver.service.
Position
Below the diagonal: node.impl.provider uses a module listed above it, which is the healthy direction.
node.impl.provider uses driver.provider, so a change to driver.provider can break node.impl.provider, while a change to node.impl.provider can't break driver.provider.
Position
Below the diagonal: node.impl.provider uses a module listed above it, which is the healthy direction.
node.impl.provider uses driver.channel, so a change to driver.channel can break node.impl.provider, while a change to node.impl.provider can't break driver.channel.
Position
Below the diagonal: node.impl.provider uses a module listed above it, which is the healthy direction.
node.impl.provider uses node.cluster, so a change to node.cluster can break node.impl.provider, while a change to node.impl.provider can't break node.cluster.
Position
Below the diagonal: node.impl.provider uses a module listed above it, which is the healthy direction.
node.impl.provider uses node.impl.setup, so a change to node.impl.setup can break node.impl.provider, while a change to node.impl.provider can't break node.impl.setup.
Position
Below the diagonal: node.impl.provider uses a module listed above it, which is the healthy direction.
node.impl.provider uses node.service, so a change to node.service can break node.impl.provider, while a change to node.impl.provider can't break node.service.
Position
Below the diagonal: node.impl.provider uses a module listed above it, which is the healthy direction.
node.impl.tick uses driver.language, so a change to driver.language can break node.impl.tick, while a change to node.impl.tick can't break driver.language.
Position
Below the diagonal: node.impl.tick uses a module listed above it, which is the healthy direction.
node.impl.tick uses driver.network, so a change to driver.network can break node.impl.tick, while a change to node.impl.tick can't break driver.network.
Position
Below the diagonal: node.impl.tick uses a module listed above it, which is the healthy direction.
node.impl.tick uses driver.provider, so a change to driver.provider can break node.impl.tick, while a change to node.impl.tick can't break driver.provider.
Position
Below the diagonal: node.impl.tick uses a module listed above it, which is the healthy direction.
node.impl.tick uses node.impl.version, so a change to node.impl.version can break node.impl.tick, while a change to node.impl.tick can't break node.impl.version.
Position
Below the diagonal: node.impl.tick uses a module listed above it, which is the healthy direction.
node.impl uses driver.network.rpc.factory, so a change to driver.network.rpc.factory can break node.impl, while a change to node.impl can't break driver.network.rpc.factory.
Position
Below the diagonal: node.impl uses a module listed above it, which is the healthy direction.
node.impl.command.sub uses driver.base, so a change to driver.base can break node.impl.command.sub, while a change to node.impl.command.sub can't break driver.base.
Position
Below the diagonal: node.impl.command.sub uses a module listed above it, which is the healthy direction.
node.impl.command.sub uses driver.event, so a change to driver.event can break node.impl.command.sub, while a change to node.impl.command.sub can't break driver.event.
Position
Below the diagonal: node.impl.command.sub uses a module listed above it, which is the healthy direction.
node.impl.command.sub uses driver.language, so a change to driver.language can break node.impl.command.sub, while a change to node.impl.command.sub can't break driver.language.
Position
Below the diagonal: node.impl.command.sub uses a module listed above it, which is the healthy direction.
node.impl.command.sub uses driver.registry, so a change to driver.registry can break node.impl.command.sub, while a change to node.impl.command.sub can't break driver.registry.
Position
Below the diagonal: node.impl.command.sub uses a module listed above it, which is the healthy direction.
node.impl.command.sub uses driver.network, so a change to driver.network can break node.impl.command.sub, while a change to node.impl.command.sub can't break driver.network.
Position
Below the diagonal: node.impl.command.sub uses a module listed above it, which is the healthy direction.
node.impl.command.sub uses node.config, so a change to node.config can break node.impl.command.sub, while a change to node.impl.command.sub can't break node.config.
Position
Below the diagonal: node.impl.command.sub uses a module listed above it, which is the healthy direction.
node.impl.command.sub uses driver.service, so a change to driver.service can break node.impl.command.sub, while a change to node.impl.command.sub can't break driver.service.
Position
Below the diagonal: node.impl.command.sub uses a module listed above it, which is the healthy direction.
node.impl.command.sub uses driver.provider, so a change to driver.provider can break node.impl.command.sub, while a change to node.impl.command.sub can't break driver.provider.
Position
Below the diagonal: node.impl.command.sub uses a module listed above it, which is the healthy direction.
node.impl.command.sub uses node.impl.version, so a change to node.impl.version can break node.impl.command.sub, while a change to node.impl.command.sub can't break node.impl.version.
Position
Below the diagonal: node.impl.command.sub uses a module listed above it, which is the healthy direction.
node.impl.command.sub uses node.cluster, so a change to node.cluster can break node.impl.command.sub, while a change to node.impl.command.sub can't break node.cluster.
Position
Below the diagonal: node.impl.command.sub uses a module listed above it, which is the healthy direction.
node.impl.command.sub uses node.impl.setup, so a change to node.impl.setup can break node.impl.command.sub, while a change to node.impl.command.sub can't break node.impl.setup.
Position
Below the diagonal: node.impl.command.sub uses a module listed above it, which is the healthy direction.
node.impl.command.sub uses node.service, so a change to node.service can break node.impl.command.sub, while a change to node.impl.command.sub can't break node.service.
Position
Below the diagonal: node.impl.command.sub uses a module listed above it, which is the healthy direction.
node.impl.command.sub uses node.impl.tick, so a change to node.impl.tick can break node.impl.command.sub, while a change to node.impl.command.sub can't break node.impl.tick.
Position
Below the diagonal: node.impl.command.sub uses a module listed above it, which is the healthy direction.
node.impl.service.defaults uses driver.event, so a change to driver.event can break node.impl.service.defaults, while a change to node.impl.service.defaults can't break driver.event.
Position
Below the diagonal: node.impl.service.defaults uses a module listed above it, which is the healthy direction.
node.impl.service.defaults uses driver.language, so a change to driver.language can break node.impl.service.defaults, while a change to node.impl.service.defaults can't break driver.language.
Position
Below the diagonal: node.impl.service.defaults uses a module listed above it, which is the healthy direction.
node.impl.service.defaults uses driver.document, so a change to driver.document can break node.impl.service.defaults, while a change to node.impl.service.defaults can't break driver.document.
Position
Below the diagonal: node.impl.service.defaults uses a module listed above it, which is the healthy direction.
node.impl.service.defaults uses driver.network, so a change to driver.network can break node.impl.service.defaults, while a change to node.impl.service.defaults can't break driver.network.
Position
Below the diagonal: node.impl.service.defaults uses a module listed above it, which is the healthy direction.
node.impl.service.defaults uses node.config, so a change to node.config can break node.impl.service.defaults, while a change to node.impl.service.defaults can't break node.config.
Position
Below the diagonal: node.impl.service.defaults uses a module listed above it, which is the healthy direction.
node.impl.service.defaults uses driver.network.rpc.factory, so a change to driver.network.rpc.factory can break node.impl.service.defaults, while a change to node.impl.service.defaults can't break driver.network.rpc.factory.
Position
Below the diagonal: node.impl.service.defaults uses a module listed above it, which is the healthy direction.
node.impl.service.defaults uses driver.service, so a change to driver.service can break node.impl.service.defaults, while a change to node.impl.service.defaults can't break driver.service.
Position
Below the diagonal: node.impl.service.defaults uses a module listed above it, which is the healthy direction.
node.impl.service.defaults uses driver.network.rpc, so a change to driver.network.rpc can break node.impl.service.defaults, while a change to node.impl.service.defaults can't break driver.network.rpc.
Position
Below the diagonal: node.impl.service.defaults uses a module listed above it, which is the healthy direction.
node.impl.service.defaults uses driver.provider, so a change to driver.provider can break node.impl.service.defaults, while a change to node.impl.service.defaults can't break driver.provider.
Position
Below the diagonal: node.impl.service.defaults uses a module listed above it, which is the healthy direction.
node.impl.service.defaults uses node.impl.version, so a change to node.impl.version can break node.impl.service.defaults, while a change to node.impl.service.defaults can't break node.impl.version.
Position
Below the diagonal: node.impl.service.defaults uses a module listed above it, which is the healthy direction.
node.impl.service.defaults uses driver.channel, so a change to driver.channel can break node.impl.service.defaults, while a change to node.impl.service.defaults can't break driver.channel.
Position
Below the diagonal: node.impl.service.defaults uses a module listed above it, which is the healthy direction.
node.impl.service.defaults uses node.cluster, so a change to node.cluster can break node.impl.service.defaults, while a change to node.impl.service.defaults can't break node.cluster.
Position
Below the diagonal: node.impl.service.defaults uses a module listed above it, which is the healthy direction.
node.impl.service.defaults uses node.service, so a change to node.service can break node.impl.service.defaults, while a change to node.impl.service.defaults can't break node.service.
Position
Below the diagonal: node.impl.service.defaults uses a module listed above it, which is the healthy direction.
node.impl.service.defaults uses node.impl.tick, so a change to node.impl.tick can break node.impl.service.defaults, while a change to node.impl.service.defaults can't break node.impl.tick.
Position
Below the diagonal: node.impl.service.defaults uses a module listed above it, which is the healthy direction.
modules.docker.impl uses driver.event, so a change to driver.event can break modules.docker.impl, while a change to modules.docker.impl can't break driver.event.
Position
Below the diagonal: modules.docker.impl uses a module listed above it, which is the healthy direction.
modules.docker.impl uses driver.language, so a change to driver.language can break modules.docker.impl, while a change to modules.docker.impl can't break driver.language.
Position
Below the diagonal: modules.docker.impl uses a module listed above it, which is the healthy direction.
modules.docker.impl uses driver.inject, so a change to driver.inject can break modules.docker.impl, while a change to modules.docker.impl can't break driver.inject.
Position
Below the diagonal: modules.docker.impl uses a module listed above it, which is the healthy direction.
modules.docker.impl uses driver.network, so a change to driver.network can break modules.docker.impl, while a change to modules.docker.impl can't break driver.network.
Position
Below the diagonal: modules.docker.impl uses a module listed above it, which is the healthy direction.
modules.docker.impl uses node.config, so a change to node.config can break modules.docker.impl, while a change to modules.docker.impl can't break node.config.
Position
Below the diagonal: modules.docker.impl uses a module listed above it, which is the healthy direction.
modules.docker.impl uses driver.service, so a change to driver.service can break modules.docker.impl, while a change to modules.docker.impl can't break driver.service.
Position
Below the diagonal: modules.docker.impl uses a module listed above it, which is the healthy direction.
modules.docker.impl uses driver.provider, so a change to driver.provider can break modules.docker.impl, while a change to modules.docker.impl can't break driver.provider.
Position
Below the diagonal: modules.docker.impl uses a module listed above it, which is the healthy direction.
modules.docker.impl uses node.impl.version, so a change to node.impl.version can break modules.docker.impl, while a change to modules.docker.impl can't break node.impl.version.
Position
Below the diagonal: modules.docker.impl uses a module listed above it, which is the healthy direction.
modules.docker.impl uses node.service, so a change to node.service can break modules.docker.impl, while a change to modules.docker.impl can't break node.service.
Position
Below the diagonal: modules.docker.impl uses a module listed above it, which is the healthy direction.
modules.docker.impl uses node.impl.tick, so a change to node.impl.tick can break modules.docker.impl, while a change to modules.docker.impl can't break node.impl.tick.
Position
Below the diagonal: modules.docker.impl uses a module listed above it, which is the healthy direction.
modules.docker.impl uses node.impl.service.defaults, so a change to node.impl.service.defaults can break modules.docker.impl, while a change to modules.docker.impl can't break node.impl.service.defaults.
Position
Below the diagonal: modules.docker.impl uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 63.9 · Adequate · gated by X5 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
25
High / Critical
A03:2025 — Software Supply Chain Failures
5
Medium
A07:2025 — Authentication Failures
2
High / Critical
A02:2025 — Security Misconfiguration
2
Medium
Roadmap
Top priorities: Resolve the 4 Banned license finding(s) in License Compliance; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts; 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 this
Helps
Effort
Dimension
Resolve the 4 Banned license finding(s) in License Compliance.
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 SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
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.
Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens)
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 — 30
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 — 370
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 — 62
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 16
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 54 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 54 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 445 of 462 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.java) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
D11 Test Reliability — 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. Test source is present (.java) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
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. Not scored — 55 Maven/Gradle manifest(s) were read, stating a version for 75 dependency(ies) and leaving 4 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D21 Naming Consistency — 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — 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 commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (build.gradle.kts), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
D24 Comment Value — 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's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
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. `driver/api/src/main/java/eu/cloudnetservice/driver/event/EventManager.java`, `driver/api/src/main/java/eu/cloudnetservice/driver/network/chunk/ChunkedPacketSender.java`, `driver/impl/src/main/java/eu/cloudnetservice/driver/impl/event/DefaultEventManager.java`, `driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/chunk/builder/DefaultChunkedPacketSenderBuilder.java`, `driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/buffer/NettyMutableDataBuf.java`, … (+30 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.
AX1 Captive dependencies — 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 Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Guice, whose lifetimes are not modelled yet, 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.
C1 Data Protection — 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. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — 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. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — 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. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — 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. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — 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. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
ED5 Idempotency — 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 decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
S1 Web-Security Posture — 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. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X1 Async correctness — not measured this run — 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X12 Unreachable branch — 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
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.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
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").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
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.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
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.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
8 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was NPCCommand.onCommand at 114. 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 FieldAccessor.convertFieldValue at 21 — 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: wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/FieldAccessor.java (FieldAccessor.convertFieldValue at 21). 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.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with NPCCommand.onCommand (cyclomatic 114), NPCCommand.tabComplete (cyclomatic 47). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 7.2 to about 8.6/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 32 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with NPCCommand.onCommand (cognitive 186), BukkitPlatformNPCManagement.<init> (cognitive 61). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 5.4 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.3 / 10Stronggated by 27 serious findings✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 14 TooManyMethods finding(s) in God Classes — start with MemorySegmentBuffer.java, UnsafeReplacementDelegate.java, AbstractService.java. — One of this dimension's main actionable groups (14 warning-level).
Resolve the 5 FileTooLong finding(s) in God Classes — start with MemorySegmentBuffer.java, UnsafeReplacementDelegate.java, TasksCommand.java. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 4 MethodTooLong finding(s) in God Classes — start with NPCCommand.java, SystemInfoDataEmitter.java, NodePlayerChannelMessageListener.java. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
80 duplicated block group(s) detected. 4.9 % of the production lines (5,657 of 114,550) are in a reported copy. A further 152 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
Edited copy of a member (7 corresponding lines) · ×12modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/PlatformBridgeManagement.java:166
Edited copy of a member (9 corresponding lines) · ×12driver/impl/src/main/java/eu/cloudnetservice/driver/impl/registry/DefaultServiceRegistry.java:98
Edited copy of a member (8 corresponding lines) · ×11driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/memory/MemorySegmentBuffer.java:1132
Edited copy of a member (11 corresponding lines) · ×9modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/listener/NodeSetupListener.java:49
+ 92 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 12 Edited copy of a member (7 corresponding lines) finding(s) in Code Duplication — start with ProxyPlatformHelper.java (2), PlatformBridgeManagement.java, MemorySegmentBuffer.java. — One of this dimension's main actionable groups (12 warning-level).
Resolve the 12 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with UnsafeReplacementDelegate.java (5), DefaultServiceRegistry.java, PlatformNPCManagement.java. — One of this dimension's main actionable groups (12 warning-level).
Resolve the 11 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with MemorySegmentBuffer.java, NodePlayerManager.java, MySQLDatabase.java. — One of this dimension's main actionable groups (11 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.7 / 10Stronggated by 2 serious findings✓ 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.
53 production modules (Gradle), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 2 module(s) off the main sequence, with abstractness counted on 51 of the 53 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: :ext:modlauncher · ×2
What to do
Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Resolve the 7 Low cohesion finding(s) in Cohesion (LCOM4) — start with ServiceCommand.java, Parsers.java, TemplateCommand.java. — One of this dimension's main actionable groups (7 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
4 of 58 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 55 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 4 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. A further 17 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
8 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java. Counted over 648 of the 1130 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1 · ×2
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
12 deducted task-comment markers across 114550 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 10 TodoComment finding(s) in Explicit Debt — start with NettyUtil.java (2), Node.java, NodeGroupConfigurationProvider.java. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 2 HackComment finding(s) in Explicit Debt — start with BaseCloudMessenger.java (2). — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 1 documentation facets pass in full. 2 document(s) read across 1 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: 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.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. — 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.
5 of 51 build units (Gradle) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion · ×5node/impl/build.gradle.kts:1
What to do
Resolve the 5 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with build.gradle.kts (5). — One of this dimension's main actionable groups (5 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D27 · Navigability7.3 / 10Strong✓ Tool-verified
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
27 % of calls cross a namespace and 55 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
High interface indirection
What to do
Resolve the 1 High interface indirection finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d27_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
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).
25 finding(s): 0 critical, 25 high, 0 medium, 0 low. 17 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 36 file(s) — `driver/api/src/main/java/eu/cloudnetservice/driver/event/EventManager.java` (line 61, line 135), `driver/api/src/main/java/eu/cloudnetservice/driver/network/chunk/ChunkedPacketSender.java` (line 143), `driver/impl/src/main/java/eu/cloudnetservice/driver/impl/event/DefaultEventManager.java` (line 64), `driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/chunk/builder/DefaultChunkedPacketSenderBuilder.java` (line 94), `driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/buffer/NettyMutableDataBuf.java` (line 48), … (+31 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. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
What to do
Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (3), REDACTED. — One of this dimension's main actionable groups (8 issue-level).
No action in Static Analysis (SAST) — all 17 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (17 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
7 of 648 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/limboloohp/LimboLoohpBridgeManagement.java. Counted over 648 of the 1130 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
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.
Resolve the 3 Change coupling finding(s) in Change Coupling — start with NettyNetworkClient.java, NodeGroupConfigurationProvider.java, BungeeCordPlayerManagementListener.java. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 3 platform declaration(s) and 75 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
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.
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.
`DefaultModuleProvider` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (moduleDependencyLoader, moduleDirectory, moduleProviderHandler; e.g. `moduleDependencyLoader` in `moduleDependencyLoader` at line 152). — driver/impl/src/main/java/eu/cloudnetservice/driver/impl/module/DefaultModuleProvider.java:67
`DefaultNodeServerProvider` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (nodeServers; e.g. `nodeServers` in `registerNode` at line 145). — node/impl/src/main/java/eu/cloudnetservice/node/impl/cluster/defaults/DefaultNodeServerProvider.java:55
`JLine3Console` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (prompt, printingEnabled, matchingHistorySearch; e.g. `prompt` in `emptyPrompt` at line 302). — node/impl/src/main/java/eu/cloudnetservice/node/impl/console/JLine3Console.java:58
`DefaultNetworkServerChannelHandler` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (ipAllowlist; e.g. `ipAllowlist` in `shouldDenyConnection` at line 139). — node/impl/src/main/java/eu/cloudnetservice/node/impl/network/DefaultNetworkServerChannelHandler.java:43
`NodeBridgeManagement` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (configuration; e.g. `configuration` in `configurationSilently` at line 124). — modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/NodeBridgeManagement.java:45
`CloudNetCloudflareModule` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (cloudflareConfiguration; e.g. `cloudflareConfiguration` in `updateConfiguration` at line 250). — modules/cloudflare/impl/src/main/java/eu/cloudnetservice/modules/cloudflare/impl/CloudNetCloudflareModule.java:56
`CloudNetMongoDatabaseModule` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (config; e.g. `config` in `loadConfig` at line 35). — modules/database-mongodb/impl/src/main/java/eu/cloudnetservice/modules/mongodb/impl/CloudNetMongoDatabaseModule.java:30
`DockerizedServicesModule` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (configuration; e.g. `configuration` in `config` at line 111). — modules/dockerized-services/impl/src/main/java/eu/cloudnetservice/modules/docker/impl/DockerizedServicesModule.java:40
`InfluxModule` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (influxClient; e.g. `influxClient` in `start` at line 53). — modules/influx/impl/src/main/java/eu/cloudnetservice/modules/influx/impl/InfluxModule.java:40
`NodeLabyModManagement` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (configuration; e.g. `configuration` in `configurationSilently` at line 66). — modules/labymod/impl/src/main/java/eu/cloudnetservice/modules/labymod/impl/node/NodeLabyModManagement.java:30
`PlatformLabyModManagement` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (configuration; e.g. `configuration` in `setConfigurationSilently` at line 70). — modules/labymod/impl/src/main/java/eu/cloudnetservice/modules/labymod/impl/platform/PlatformLabyModManagement.java:39
`CloudNetReportModule` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (configuration; e.g. `configuration` in `finishStartup` at line 60). — modules/report/impl/src/main/java/eu/cloudnetservice/modules/report/impl/CloudNetReportModule.java:35
`CloudNetSignsModule` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (database, configuration; e.g. `database` in `initialize` at line 63). — modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/node/CloudNetSignsModule.java:48
`CloudNetTickListener` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (autoStartBlocks, autoStopTicks; e.g. `autoStartBlocks` in `handleAutoStart` at line 133). — modules/smart/impl/src/main/java/eu/cloudnetservice/modules/smart/impl/listener/CloudNetTickListener.java:51
`S3TemplateStorageModule` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (storage; e.g. `storage` in `handleInit` at line 39). — modules/storage-s3/impl/src/main/java/eu/cloudnetservice/modules/s3/impl/S3TemplateStorageModule.java:33
`SFTPTemplateStorageModule` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (storage; e.g. `storage` in `handleInit` at line 68). — modules/storage-sftp/impl/src/main/java/eu/cloudnetservice/modules/sftp/impl/SFTPTemplateStorageModule.java:38
`NodeSyncProxyManagement` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (configuration; e.g. `configuration` in `configurationSilently` at line 71). — modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/node/NodeSyncProxyManagement.java:33
What to do
Java/Kotlin: keep container singletons stateless — move per-request data into locals or a request-scoped bean — or back the state with java.util.concurrent types (ConcurrentHashMap, AtomicInteger/AtomicReference), guard it with synchronized / a Lock (Kotlin: withLock), or mark a flag that is only ever overwritten volatile (@Volatile).
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
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.
`Database` declares 23 abstract methods: `clear`, `clearAsync`, `contains`, `containsAsync`, `delete`, `deleteAsync`, `documentCount`, `documentCountAsync`, `documents`, `documentsAsync`, `entries`, `entriesAsync`, `find`, `find`, `findAsync`, `findAsync`, `get`, `getAsync`, `insert`, `insertAsync`, `keys`, `keysAsync`, `synced`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 23 declarations carry 21 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 21 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — driver/api/src/main/java/eu/cloudnetservice/driver/database/Database.java:54
`Document` declares 33 abstract methods: `contains`, `containsNonNull`, `elementCount`, `elements`, `empty`, `equals`, `factoryName`, `getBoolean`, `getByte`, `getDouble`, `getFloat`, `getInt`, `getLong`, `getShort`, `getString`, `immutableCopy`, `keys`, `mutableCopy`, `readDocument`, `readMutableDocument`, `readObject`, `readObject`, `readObject`, `send`, `serializeToString`, `toInstanceOf`, `toInstanceOf`, `toInstanceOf`, `toString`, `writeTo`, `writeTo`, `writeTo`, `writeTo`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 33 declarations carry 26 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 26 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — driver/api/src/main/java/eu/cloudnetservice/driver/document/Document.java:91
`ModuleProvider` declares 18 abstract methods under just 13 distinct name(s): `loadAll`, `loadModule`, `loadModule`, `module`, `moduleDependencyLoader`, `moduleDependencyLoader`, `moduleDirectoryPath`, `moduleDirectoryPath`, `moduleProviderHandler`, `moduleProviderHandler`, `modules`, `modules`, `notifyPostModuleLifecycleChange`, `notifyPreModuleLifecycleChange`, `reloadAll`, `startAll`, `stopAll`, `unloadAll`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 18 separate responsibilities: a caller binds to 13 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 18 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — driver/api/src/main/java/eu/cloudnetservice/driver/module/ModuleProvider.java:35
`ModuleWrapper` declares 16 abstract methods: `classLoader`, `dataDirectory`, `dependingModules`, `injectionLayer`, `loadModule`, `module`, `moduleConfiguration`, `moduleLifeCycle`, `moduleProvider`, `moduleTasks`, `reloadModule`, `startModule`, `stopModule`, `unloadModule`, `uri`, `url`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — driver/api/src/main/java/eu/cloudnetservice/driver/module/ModuleWrapper.java:39
`DataBuf` declares 31 abstract methods: `accessible`, `acquire`, `acquires`, `advanceReaderOffset`, `asMutable`, `close`, `forceRelease`, `readBoolean`, `readByte`, `readByteArray`, `readChar`, `readDataBuf`, `readDouble`, `readFloat`, `readInt`, `readLong`, `readNullable`, `readNullable`, `readObject`, `readObject`, `readShort`, `readString`, `readUniqueId`, `readableBytes`, `readableNioBuffer`, `readerOffset`, `readerOffset`, `redoTransaction`, `release`, `startTransaction`, `toByteArray`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 31 declarations carry 28 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 28 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — driver/api/src/main/java/eu/cloudnetservice/driver/network/buffer/DataBuf.java:59
`Mutable` declares 22 abstract methods: `advanceWriterOffset`, `asImmutable`, `ensureWriteable`, `writeBoolean`, `writeByte`, `writeByteArray`, `writeByteArray`, `writeChar`, `writeDataBuf`, `writeDouble`, `writeFloat`, `writeInt`, `writeLong`, `writeNullable`, `writeObject`, `writeShort`, `writeString`, `writeUniqueId`, `writeableBytes`, `writeableNioBuffer`, `writerOffset`, `writerOffset`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 22 declarations carry 20 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 20 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — driver/api/src/main/java/eu/cloudnetservice/driver/network/buffer/DataBuf.java:401
`CloudServiceProvider` declares 22 abstract methods: `runningServices`, `runningServicesAsync`, `service`, `serviceAsync`, `serviceByName`, `serviceByNameAsync`, `serviceCount`, `serviceCountAsync`, `serviceCountByGroup`, `serviceCountByGroupAsync`, `serviceCountByTask`, `serviceCountByTaskAsync`, `serviceProvider`, `serviceProviderByName`, `services`, `servicesAsync`, `servicesByEnvironment`, `servicesByEnvironmentAsync`, `servicesByGroup`, `servicesByGroupAsync`, `servicesByTask`, `servicesByTaskAsync`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — driver/api/src/main/java/eu/cloudnetservice/driver/provider/CloudServiceProvider.java:40
`ClusterNodeProvider` declares 20 abstract methods: `addNode`, `addNodeAsync`, `consoleCommand`, `consoleCommandAsync`, `consoleCommands`, `consoleCommandsAsync`, `consoleTabCompleteResults`, `consoleTabCompleteResultsAsync`, `node`, `nodeAsync`, `nodeInfoSnapshot`, `nodeInfoSnapshotAsync`, `nodeInfoSnapshots`, `nodeInfoSnapshotsAsync`, `nodes`, `nodesAsync`, `removeNode`, `removeNodeAsync`, `sendCommandLine`, `sendCommandLineAsync`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — driver/api/src/main/java/eu/cloudnetservice/driver/provider/ClusterNodeProvider.java:39
`SpecificCloudServiceProvider` declares 38 abstract methods: `addServiceDeployment`, `addServiceDeploymentAsync`, `addServiceRemoteInclusion`, `addServiceRemoteInclusionAsync`, `addServiceTemplate`, `addServiceTemplateAsync`, `cachedLogMessages`, `cachedLogMessagesAsync`, `deleteFiles`, `deleteFilesAsync`, `deployResources`, `deployResourcesAsync`, `forceUpdateServiceInfo`, `forceUpdateServiceInfoAsync`, `includeWaitingServiceInclusions`, `includeWaitingServiceInclusionsAsync`, `includeWaitingServiceTemplates`, `includeWaitingServiceTemplates`, `includeWaitingServiceTemplatesAsync`, `includeWaitingServiceTemplatesAsync`, `installedDeployments`, `installedInclusions`, `installedTemplates`, `removeAndExecuteDeploymentsAsync`, `restart`, `restartAsync`, `runCommand`, `runCommandAsync`, `serviceInfo`, `serviceInfoAsync`, `toggleScreenEvents`, `toggleScreenEventsAsync`, `updateLifecycle`, `updateLifecycleAsync`, `updateProperties`, `updatePropertiesAsync`, `valid`, `validAsync`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 38 declarations carry 36 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 36 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — driver/api/src/main/java/eu/cloudnetservice/driver/provider/SpecificCloudServiceProvider.java:43
`TemplateStorage` declares 37 abstract methods: `appendOutputStream`, `appendOutputStreamAsync`, `close`, `closeAsync`, `contains`, `containsAsync`, `create`, `createAsync`, `createDirectory`, `createDirectoryAsync`, `createFile`, `createFileAsync`, `delete`, `deleteAsync`, `deleteFile`, `deleteFileAsync`, `deploy`, `deployAsync`, `deployDirectory`, `deployDirectoryAsync`, `fileInfo`, `fileInfoAsync`, `hasFile`, `hasFileAsync`, `listFiles`, `listFilesAsync`, `newInputStream`, `newInputStreamAsync`, `newOutputStream`, `newOutputStreamAsync`, `openZipInputStreamAsync`, `pull`, `pullAsync`, `templates`, `templatesAsync`, `zipTemplate`, `zipTemplateAsync`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — driver/api/src/main/java/eu/cloudnetservice/driver/template/TemplateStorage.java:45
`NodeServer` declares 22 abstract methods: `available`, `channel`, `channel`, `close`, `connect`, `drain`, `draining`, `head`, `info`, `lastNodeInfoSnapshot`, `lastNodeInfoUpdate`, `lastStateChange`, `nodeInfoSnapshot`, `provider`, `sendCommandLine`, `serviceFactory`, `serviceProvider`, `shutdown`, `state`, `state`, `syncClusterData`, `updateNodeInfoSnapshot`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 22 declarations carry 20 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 20 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — node/api/src/main/java/eu/cloudnetservice/node/cluster/NodeServer.java:34
`Configuration` declares 38 abstract methods: `clientSSLConfig`, `clientSSLConfig`, `clusterConfig`, `clusterConfig`, `fileExists`, `forceInitialClusterDataSync`, `forceInitialClusterDataSync`, `hostAddress`, `hostAddress`, `identity`, `identity`, `ipAliases`, `ipAliases`, `ipWhitelist`, `ipWhitelist`, `javaCommand`, `javaCommand`, `language`, `language`, `load`, `maxCPUUsageToStartServices`, `maxCPUUsageToStartServices`, `maxMemory`, `maxMemory`, `maxServiceConsoleLogCacheSize`, `maxServiceConsoleLogCacheSize`, `printErrorStreamLinesFromServices`, `printErrorStreamLinesFromServices`, `processTerminationTimeoutSeconds`, `processTerminationTimeoutSeconds`, `properties`, `properties`, `reloadFrom`, `runBlockedServiceStartTryLaterAutomatic`, `runBlockedServiceStartTryLaterAutomatic`, `save`, `serverSSLConfig`, `serverSSLConfig`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 38 declarations carry 21 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 21 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — node/api/src/main/java/eu/cloudnetservice/node/config/Configuration.java:27
`CloudService` declares 17 abstract methods: `alive`, `cloudServiceManager`, `connectionKey`, `directory`, `lastServiceInfoSnapshot`, `lifeCycle`, `networkChannel`, `pluginDirectory`, `publishServiceInfoSnapshot`, `runtime`, `serviceConfiguration`, `serviceConsoleLogCache`, `serviceId`, `serviceInfo`, `waitingDeployments`, `waitingIncludes`, `waitingTemplates`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — node/api/src/main/java/eu/cloudnetservice/node/service/CloudService.java:33
`CloudServiceManager` declares 23 abstract methods: `addCloudServiceFactory`, `addCloudServiceFactory`, `addServicePreparer`, `addServicePreparer`, `cloudServiceFactories`, `cloudServiceFactory`, `currentReservedMemory`, `currentUsedHeapMemory`, `defaultJvmOptions`, `deleteAllCloudServices`, `localCloudService`, `localCloudService`, `localCloudService`, `localCloudServices`, `persistentServicesDirectory`, `removeCloudServiceFactory`, `removeServicePreparer`, `selectNodeForService`, `servicePreparer`, `servicePreparers`, `startAllCloudServices`, `stopAllCloudServices`, `tempDirectory`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 23 declarations carry 19 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 19 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — node/api/src/main/java/eu/cloudnetservice/node/service/CloudServiceManager.java:33
`Console` declares 32 abstract methods: `addCommandHandler`, `addTabCompleteHandler`, `animationRunning`, `clearScreen`, `commandHistory`, `commandHistory`, `commandInputValue`, `disableAllCommandHandlers`, `disableAllHandlers`, `disableAllTabCompleteHandlers`, `displayLength`, `emptyPrompt`, `enableAllCommandHandlers`, `enableAllHandlers`, `enableAllTabCompleteHandlers`, `forceWriteLine`, `printingEnabled`, `prompt`, `prompt`, `readLine`, `removeCommandHandler`, `removePrompt`, `removeTabCompleteHandler`, `resetPrompt`, `runningAnimations`, `startAnimation`, `togglePrinting`, `usingMatchingHistoryComplete`, `usingMatchingHistoryComplete`, `width`, `writeLine`, `writeRaw`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 32 declarations carry 29 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 29 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — node/impl/src/main/java/eu/cloudnetservice/node/impl/console/Console.java:31
`PlayerManager` declares 30 abstract methods: `deleteCloudOfflinePlayer`, `deleteCloudOfflinePlayerAsync`, `environmentOnlinePlayers`, `environmentOnlinePlayersAsync`, `firstOfflinePlayer`, `firstOfflinePlayerAsync`, `firstOnlinePlayer`, `firstOnlinePlayerAsync`, `globalPlayerExecutor`, `groupOnlinePlayers`, `offlinePlayer`, `offlinePlayerAsync`, `offlinePlayers`, `offlinePlayersAsync`, `onlineCount`, `onlineCountAsync`, `onlinePlayer`, `onlinePlayerAsync`, `onlinePlayers`, `onlinePlayers`, `onlinePlayersAsync`, `playerExecutor`, `registeredCount`, `registeredCountAsync`, `registeredPlayers`, `taskOnlinePlayers`, `updateOfflinePlayer`, `updateOfflinePlayerAsync`, `updateOnlinePlayer`, `updateOnlinePlayerAsync`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 30 declarations carry 29 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 29 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — modules/bridge/api/src/main/java/eu/cloudnetservice/modules/bridge/player/PlayerManager.java:58
`PlatformSelectorEntity<L, P, M, I, S>` declares 18 abstract methods: `canSpawn`, `entityId`, `executeAction`, `handleInventoryInteract`, `handleLeftClickAction`, `handleRightClickAction`, `infoLineEntityIds`, `location`, `npc`, `registerScoreboardTeam`, `remove`, `scoreboardRepresentation`, `selectorInventory`, `spawn`, `spawned`, `stopTrackingService`, `trackService`, `update`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — modules/npcs/api/src/main/java/eu/cloudnetservice/modules/npc/platform/PlatformSelectorEntity.java:25
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Where the width is an overload set rather than separate responsibilities, collapse the overloads instead — segregating those relieves no caller.
Other · Code Health — Unreviewed-generation residue in this repository's Java: methods whose whole body only throws a "not implemented" or bare unsupported-operation exception, or returns a default value (or nothing) under a TODO/FIXME marker, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of 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.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Java: methods that only throw a "not implemented" exception, methods that take inputs and return a constant or do nothing, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
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.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
Maturity · Maturity — Whether the 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.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Only 18/20 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `launcher/java8`, `launcher/patcher`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
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 spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 5 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:7
What to do
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
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.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Do you agree with this assessment?
X13 · Undrained process stream4.3 / 10Weak✓ Tool-verified
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. 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 `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
The JDK pipes both `stdout` and `stderr` of this child — no `redirectErrorStream`, `redirectError`, `redirectOutput` or `inheritIO` is set — and the parent reads the other stream to its end while nothing reads stdout; that read returns only at end of stream, which the child never reaches. The JDK's own `Process` documentation warns that failing to read a child's output promptly "may cause the process to block, or even deadlock": once the child writes more than the pipe holds (measured on OpenJDK 25 / Linux: 60,000 bytes finishes, 70,000 hangs forever), it blocks on the write, never exits, and the wait never returns. Nothing fails loudly. Read every piped stream before (or while) waiting — a thread or `CompletableFuture` per stream — merge them with `redirectErrorStream(true)` and read the one stream before `waitFor`, or discard what you do not want with `redirectOutput`/`redirectError(ProcessBuilder.Redirect.DISCARD)` (or a file). — node/impl/src/main/java/eu/cloudnetservice/node/impl/util/JavaVersionResolver.java:57
The JDK pipes both `stdout` and `stderr` of this child — no `redirectErrorStream`, `redirectError`, `redirectOutput` or `inheritIO` is set — and `process.waitFor()` is written before stdout and stderr is read, so nothing drains it while the parent waits. The JDK's own `Process` documentation warns that failing to read a child's output promptly "may cause the process to block, or even deadlock": once the child writes more than the pipe holds (measured on OpenJDK 25 / Linux: 60,000 bytes finishes, 70,000 hangs forever), it blocks on the write, never exits, and the wait never returns. Nothing fails loudly. Read every piped stream before (or while) waiting — a thread or `CompletableFuture` per stream — merge them with `redirectErrorStream(true)` and read the one stream before `waitFor`, or discard what you do not want with `redirectOutput`/`redirectError(ProcessBuilder.Redirect.DISCARD)` (or a file). — launcher/java22/src/main/java/eu/cloudnetservice/launcher/java22/util/Environment.java:42
What to do
Each finding names the span that makes the branch dead and the span it is dead because of. Confirm from the two, then delete the dead arm or fix the predicate that was meant to be reachable.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
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.
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.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
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.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen. Whether a `for (x in c)` or `c.forEach { … }` leaves the collection it is walking alone — a `mutableListOf`/`ArrayList`, `mutableMapOf`/`HashMap` or `mutableSetOf`/`HashSet` is a `java.util` collection on the JVM and is walked by its own fail-fast iterator, so a body that adds to or removes from the very collection the loop is walking makes the next step throw `ConcurrentModificationException` and the remaining elements 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.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
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.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×5) — wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/ShutdownHandler.java:49, wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:158, modules/storage-sftp/impl/src/main/java/eu/cloudnetservice/modules/sftp/impl/SFTPClientPool.java:185, …
`catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×3) — utils/base/src/main/java/eu/cloudnetservice/utils/base/io/FileUtil.java:109, modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bukkit/BukkitUtil.java:50, ext/platform-scheduler/src/main/java/eu/cloudnetservice/ext/scheduler/SchedulerUtil.java:62
`catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×7) — node/impl/src/main/java/eu/cloudnetservice/node/impl/util/NetworkUtil.java:63, node/impl/src/main/java/eu/cloudnetservice/node/impl/config/ConfigurationUtil.java:72, node/impl/src/main/java/eu/cloudnetservice/node/impl/command/defaults/AerogelInjectionService.java:43, …
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.
Other · Code Health — Whether Java packages are null-marked and not undermined by heavy nullness suppression — a package under `@NullMarked` (or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, or a NullAway/Checker Framework configuration naming it) makes an unannotated reference exclude null, and `@SuppressWarnings("NullAway")`, `("nullness")`, `("null")` and `castToNonNull(…)` are what silence it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
0/347 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
What to do
Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
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.
X10 Duplicated predicate — 21 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 57 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 — 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
AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
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
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — docker build failed (exit 1) — 9 | COPY . . 10 | >>> RUN ./gradlew build genUpdaterInformation -x test -x checkstyleMain -x checkstyleTest --no-daemon 11 | 12 | FROM azul/zulu-openjdk-alpine:25-jre-headless-latest -------------------- ERROR: failed to solve: process "/bin/sh -c ./gradlew build genUpdaterInformation -x test -x checkstyleMain -x checkstyleTest --no-daemon" did not complete successfully: exit code: 1; likely cause (the repository): a RUN step of the repository's REDACTED exited with code 1 (`/bin/sh -c ./gradlew build genUpdaterInformation -x test -x checkstyleMain -x checkstyleTest --no-daemon`): the build's own command failed, for example a compile or test error; runtime evidence skipped The cause is in the repository, not in our sandbox: a RUN step of the repository's REDACTED exited with code 1 (`/bin/sh -c ./gradlew build genUpdaterInformation -x test -x checkstyleMain -x checkstyleTest --no-daemon`): the build's own command failed, for example a compile or test error. Nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D11 Test Reliability — Test reliability not included — the .java suite was found but not re-run
D12 Dependency Hygiene — Not scored — 55 Maven/Gradle manifest(s) were read, stating a version for 75 dependency(ies) and leaving 4 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 1 candidate(s) found and not reported.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, .kt, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D30 Dependency Vulnerabilities — 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 Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).
D32 Data Compliance (PII/GDPR) — 35 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
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 Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).
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 included — suite not readable by the collector
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 108 value object(s); 41 domain event(s); its domain events are published by services or handlers — no domain entity raises one
ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 46 event handler(s); 1 CQRS handler(s)
ED5 Idempotency — Not assessed, and this one is on us: 47 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (an Axon event-sourcing framework (@Aggregate/@CommandHandler/@EventSourcingHandler annotations))
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
X1 Async correctness — X1 reached only 1% of this repository's production lines — java (112,949 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X12 Unreachable branch — X12 reached only 1% of this repository's production lines — java (112,949 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
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
X2 Cancellation propagation — no C# was loaded; this repository's Java and Kotlin were read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter; a Kotlin request outside a suspend function has no caller's cancellation to honour
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
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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 — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — 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.
Banned license: com.electronwill.night-config:toml — `com.electronwill.night-config:toml` 3.9.0 is published on Maven Central under `LGPL-3.0`, which this policy bans, and this repository declares it in a Maven or Gradle manifest. The licence was read from the artifact's POM `<licenses>` block — following `<parent>` where the POM inherits them — and normalised to SPDX before it was judged, because Maven publishes the name as free text (`GNU Affero General Public License v3` is AGPL-3.0). Where a POM lists several licences they are read as a CHOICE, per Maven's own documentation, so this is charged only because EVERY listed licence is banned. Replace the dependency, or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: com.electronwill.night-config:yaml — `com.electronwill.night-config:yaml` 3.9.0 is published on Maven Central under `LGPL-3.0`, which this policy bans, and this repository declares it in a Maven or Gradle manifest. The licence was read from the artifact's POM `<licenses>` block — following `<parent>` where the POM inherits them — and normalised to SPDX before it was judged, because Maven publishes the name as free text (`GNU Affero General Public License v3` is AGPL-3.0). Where a POM lists several licences they are read as a CHOICE, per Maven's own documentation, so this is charged only because EVERY listed licence is banned. Replace the dependency, or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: com.electronwill.night-config:json — `com.electronwill.night-config:json` 3.9.0 is published on Maven Central under `LGPL-3.0`, which this policy bans, and this repository declares it in a Maven or Gradle manifest. The licence was read from the artifact's POM `<licenses>` block — following `<parent>` where the POM inherits them — and normalised to SPDX before it was judged, because Maven publishes the name as free text (`GNU Affero General Public License v3` is AGPL-3.0). Where a POM lists several licences they are read as a CHOICE, per Maven's own documentation, so this is charged only because EVERY listed licence is banned. Replace the dependency, or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: com.mysql:mysql-connector-j — `com.mysql:mysql-connector-j` 26.10.0 is published on Maven Central under `GPL-2.0`, which this policy bans, and this repository declares it in a Maven or Gradle manifest. The licence was read from the artifact's POM `<licenses>` block — following `<parent>` where the POM inherits them — and normalised to SPDX before it was judged, because Maven publishes the name as free text (`GNU Affero General Public License v3` is AGPL-3.0). Where a POM lists several licences they are read as a CHOICE, per Maven's own documentation, so this is charged only because EVERY listed licence is banned. Replace the dependency, or record an accepted exception.
Stateful singleton: DefaultModuleProvider driver/impl/src/main/java/eu/cloudnetservice/driver/impl/module/DefaultModuleProvider.java:67— `DefaultModuleProvider` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (moduleDependencyLoader, moduleDirectory, moduleProviderHandler; e.g. `moduleDependencyLoader` in `moduleDependencyLoader` at line 152).
Stateful singleton: DefaultNodeServerProvider node/impl/src/main/java/eu/cloudnetservice/node/impl/cluster/defaults/DefaultNodeServerProvider.java:55— `DefaultNodeServerProvider` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (nodeServers; e.g. `nodeServers` in `registerNode` at line 145).
Stateful singleton: JLine3Console node/impl/src/main/java/eu/cloudnetservice/node/impl/console/JLine3Console.java:58— `JLine3Console` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (prompt, printingEnabled, matchingHistorySearch; e.g. `prompt` in `emptyPrompt` at line 302).
Stateful singleton: DefaultNetworkServerChannelHandler node/impl/src/main/java/eu/cloudnetservice/node/impl/network/DefaultNetworkServerChannelHandler.java:43— `DefaultNetworkServerChannelHandler` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (ipAllowlist; e.g. `ipAllowlist` in `shouldDenyConnection` at line 139).
Stateful singleton: NodeBridgeManagement modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/NodeBridgeManagement.java:45— `NodeBridgeManagement` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (configuration; e.g. `configuration` in `configurationSilently` at line 124).
Stateful singleton: CloudNetCloudflareModule modules/cloudflare/impl/src/main/java/eu/cloudnetservice/modules/cloudflare/impl/CloudNetCloudflareModule.java:56— `CloudNetCloudflareModule` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (cloudflareConfiguration; e.g. `cloudflareConfiguration` in `updateConfiguration` at line 250).
Stateful singleton: CloudNetMongoDatabaseModule modules/database-mongodb/impl/src/main/java/eu/cloudnetservice/modules/mongodb/impl/CloudNetMongoDatabaseModule.java:30— `CloudNetMongoDatabaseModule` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (config; e.g. `config` in `loadConfig` at line 35).
Stateful singleton: DockerizedServicesModule modules/dockerized-services/impl/src/main/java/eu/cloudnetservice/modules/docker/impl/DockerizedServicesModule.java:40— `DockerizedServicesModule` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (configuration; e.g. `configuration` in `config` at line 111).
Stateful singleton: InfluxModule modules/influx/impl/src/main/java/eu/cloudnetservice/modules/influx/impl/InfluxModule.java:40— `InfluxModule` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (influxClient; e.g. `influxClient` in `start` at line 53).
Stateful singleton: NodeLabyModManagement modules/labymod/impl/src/main/java/eu/cloudnetservice/modules/labymod/impl/node/NodeLabyModManagement.java:30— `NodeLabyModManagement` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (configuration; e.g. `configuration` in `configurationSilently` at line 66).
Stateful singleton: PlatformLabyModManagement modules/labymod/impl/src/main/java/eu/cloudnetservice/modules/labymod/impl/platform/PlatformLabyModManagement.java:39— `PlatformLabyModManagement` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (configuration; e.g. `configuration` in `setConfigurationSilently` at line 70).
Stateful singleton: CloudNetReportModule modules/report/impl/src/main/java/eu/cloudnetservice/modules/report/impl/CloudNetReportModule.java:35— `CloudNetReportModule` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (configuration; e.g. `configuration` in `finishStartup` at line 60).
Stateful singleton: CloudNetSignsModule modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/node/CloudNetSignsModule.java:48— `CloudNetSignsModule` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (database, configuration; e.g. `database` in `initialize` at line 63).
Stateful singleton: CloudNetTickListener modules/smart/impl/src/main/java/eu/cloudnetservice/modules/smart/impl/listener/CloudNetTickListener.java:51— `CloudNetTickListener` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (autoStartBlocks, autoStopTicks; e.g. `autoStartBlocks` in `handleAutoStart` at line 133).
Stateful singleton: S3TemplateStorageModule modules/storage-s3/impl/src/main/java/eu/cloudnetservice/modules/s3/impl/S3TemplateStorageModule.java:33— `S3TemplateStorageModule` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (storage; e.g. `storage` in `handleInit` at line 39).
Stateful singleton: SFTPTemplateStorageModule modules/storage-sftp/impl/src/main/java/eu/cloudnetservice/modules/sftp/impl/SFTPTemplateStorageModule.java:38— `SFTPTemplateStorageModule` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (storage; e.g. `storage` in `handleInit` at line 68).
Stateful singleton: NodeSyncProxyManagement modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/node/NodeSyncProxyManagement.java:33— `NodeSyncProxyManagement` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (configuration; e.g. `configuration` in `configurationSilently` at line 71).
TooManyMethods: MemorySegmentBuffer driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/memory/MemorySegmentBuffer.java:58— TooManyMethods — 126 methods. The bar is 30 methods; this is 96 over it, 4.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: UnsafeReplacementDelegate wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:47— TooManyMethods — 99 methods. The bar is 30 methods; this is 69 over it, 3.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AbstractService node/impl/src/main/java/eu/cloudnetservice/node/impl/service/defaults/AbstractService.java:90— TooManyMethods — 74 methods. The bar is 30 methods; this is 44 over it, 2.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: DefaultCloudServiceManager node/impl/src/main/java/eu/cloudnetservice/node/impl/service/defaults/DefaultCloudServiceManager.java:89— TooManyMethods — 57 methods. The bar is 30 methods; this is 27 over it, 1.90× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TasksCommand node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/TasksCommand.java:78— TooManyMethods — 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: NodePlayerManager modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/player/NodePlayerManager.java:70— TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: S3TemplateStorage modules/storage-s3/impl/src/main/java/eu/cloudnetservice/modules/s3/impl/S3TemplateStorage.java:71— TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. Most of these members implement template.TemplateStorage (37 of 44 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: SFTPTemplateStorage modules/storage-sftp/impl/src/main/java/eu/cloudnetservice/modules/sftp/impl/SFTPTemplateStorage.java:57— TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. Most of these members implement template.TemplateStorage (37 of 45 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: ImmutableGsonDocument driver/impl/src/main/java/eu/cloudnetservice/driver/impl/document/gson/ImmutableGsonDocument.java:61— TooManyMethods — 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: JLine3Console node/impl/src/main/java/eu/cloudnetservice/node/impl/console/JLine3Console.java:58— TooManyMethods — 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: JsonConfiguration node/impl/src/main/java/eu/cloudnetservice/node/impl/config/JsonConfiguration.java:49— TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: LocalTemplateStorage node/impl/src/main/java/eu/cloudnetservice/node/impl/template/LocalTemplateStorage.java:44— TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. Most of these members implement template.TemplateStorage (37 of 40 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: NettyImmutableDataBuf driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/buffer/NettyImmutableDataBuf.java:40— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: NPCConfigurationEntry modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/_deprecated/configuration/NPCConfigurationEntry.java:25— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×12
Edited copy of a member (7 corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/PlatformBridgeManagement.java:166— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/PlatformBridgeManagement.java:166-172 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/fabric/FabricFallbackEventListener.java:44-57 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/memory/MemorySegmentBuffer.java:1089— driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/memory/MemorySegmentBuffer.java:1089-1096 | driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/memory/MemorySegmentBuffer.java:1102-1108 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/limboloohp/LimboLoohpBridgePlugin.java:64— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/limboloohp/LimboLoohpBridgePlugin.java:64-71 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/nukkit/NukkitBridgePlugin.java:68-74 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/helper/ProxyPlatformHelper.java:72— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/helper/ProxyPlatformHelper.java:72-78 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/helper/ServerPlatformHelper.java:40-46 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/helper/ProxyPlatformHelper.java:64— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/helper/ProxyPlatformHelper.java:64-70 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/helper/ServerPlatformHelper.java:48-54 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/node/NodeNPCManagement.java:107— modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/node/NodeNPCManagement.java:107-115 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/node/NodeSignManagement.java:141-147 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordDirectPlayerExecutor.java:128— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordDirectPlayerExecutor.java:128-134 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/waterdog/WaterDogPEDirectPlayerExecutor.java:110-116 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) modules/npcs/api/src/main/java/eu/cloudnetservice/modules/npc/configuration/ItemLayout.java:35— modules/npcs/api/src/main/java/eu/cloudnetservice/modules/npc/configuration/ItemLayout.java:35-41 | modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/node/CloudNetNPCModule.java:213-220 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) node/impl/src/main/java/eu/cloudnetservice/node/impl/setup/DefaultTaskSetup.java:272— node/impl/src/main/java/eu/cloudnetservice/node/impl/setup/DefaultTaskSetup.java:272-282 | utils/base/src/main/java/eu/cloudnetservice/utils/base/io/FileUtil.java:124-130 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) node/impl/src/main/java/eu/cloudnetservice/node/impl/network/DefaultNetworkClientChannelHandler.java:60— node/impl/src/main/java/eu/cloudnetservice/node/impl/network/DefaultNetworkClientChannelHandler.java:60-66 | node/impl/src/main/java/eu/cloudnetservice/node/impl/network/DefaultNetworkServerChannelHandler.java:64-71 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) node/impl/src/main/java/eu/cloudnetservice/node/impl/network/listener/AuthorizationPacketListener.java:69— node/impl/src/main/java/eu/cloudnetservice/node/impl/network/listener/AuthorizationPacketListener.java:69-77 | node/impl/src/main/java/eu/cloudnetservice/node/impl/network/listener/AuthorizationResponsePacketListener.java:58-64 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/velocity/VelocityBridgePlugin.java:59— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/velocity/VelocityBridgePlugin.java:59-67 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/waterdog/WaterDogPEBridgePlugin.java:54-60 — 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 (9 corresponding lines) · ×12
Edited copy of a member (9 corresponding lines) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/registry/DefaultServiceRegistry.java:98— driver/impl/src/main/java/eu/cloudnetservice/driver/impl/registry/DefaultServiceRegistry.java:98-106 | driver/impl/src/main/java/eu/cloudnetservice/driver/impl/registry/DefaultServiceRegistry.java:117-125 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:460— wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:460-468 | wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:472-480 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/PlatformNPCManagement.java:248— modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/PlatformNPCManagement.java:248-256 | modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/PlatformNPCManagement.java:258-266 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) modules/report/impl/src/main/java/eu/cloudnetservice/modules/report/impl/command/ReportCommand.java:84— modules/report/impl/src/main/java/eu/cloudnetservice/modules/report/impl/command/ReportCommand.java:84-92 | modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/node/command/SyncProxyCommand.java:68-76 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:340— wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:340-348 | wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:352-360 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:364— wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:364-372 | wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:376-384 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:412— wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:412-420 | wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:424-432 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:436— wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:436-444 | wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:448-456 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/network/NodeBridgeChannelMessageListener.java:37— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/network/NodeBridgeChannelMessageListener.java:37-47 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/listener/PlatformChannelMessageListener.java:57-65 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/velocity/VelocityBridgeManagement.java:172— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/velocity/VelocityBridgeManagement.java:172-180 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/waterdog/WaterDogPEBridgeManagement.java:173-181 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/NodeBridgeManagement.java:94— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/NodeBridgeManagement.java:94-103 | modules/smart/impl/src/main/java/eu/cloudnetservice/modules/smart/impl/NodeSmartServiceManagement.java:87-95 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/bukkit/BukkitPlatformInfoProvider.java:24— ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/bukkit/BukkitPlatformInfoProvider.java:24-33 | ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/nukkit/NukkitPlatformInfoProvider.java:24-32 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×11
Edited copy of a member (8 corresponding lines) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/memory/MemorySegmentBuffer.java:1132— driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/memory/MemorySegmentBuffer.java:1132-1139 | driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/memory/MemorySegmentBuffer.java:1145-1152 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/player/NodePlayerManager.java:189— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/player/NodePlayerManager.java:189-196 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/player/NodePlayerManager.java:199-206 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabase.java:84— modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabase.java:84-94 | node/impl/src/main/java/eu/cloudnetservice/node/impl/database/h2/H2Database.java:98-105 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/object/DefaultObjectMapper.java:268— driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/object/DefaultObjectMapper.java:268-276 | node/impl/src/main/java/eu/cloudnetservice/node/impl/cluster/sync/DefaultDataSyncRegistry.java:74-81 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) modules/labymod/impl/src/main/java/eu/cloudnetservice/modules/labymod/impl/node/NodeLabyModListener.java:30— modules/labymod/impl/src/main/java/eu/cloudnetservice/modules/labymod/impl/node/NodeLabyModListener.java:30-37 | modules/labymod/impl/src/main/java/eu/cloudnetservice/modules/labymod/impl/platform/PlatformLabyModListener.java:33-40 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/PlatformNPCManagement.java:229— modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/PlatformNPCManagement.java:229-236 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/PlatformSignManagement.java:288-295 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/ClusterCommand.java:126— node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/ClusterCommand.java:126-133 | node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/MigrateCommand.java:63-70 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) modules/dockerized-services/impl/src/main/java/eu/cloudnetservice/modules/docker/impl/DockerizedLocalCloudServiceFactory.java:59— modules/dockerized-services/impl/src/main/java/eu/cloudnetservice/modules/docker/impl/DockerizedLocalCloudServiceFactory.java:59-68 | node/impl/src/main/java/eu/cloudnetservice/node/impl/service/defaults/factory/JVMLocalCloudServiceFactory.java:53-60 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) modules/storage-s3/impl/src/main/java/eu/cloudnetservice/modules/s3/impl/S3TemplateStorage.java:209— modules/storage-s3/impl/src/main/java/eu/cloudnetservice/modules/s3/impl/S3TemplateStorage.java:209-216 | modules/storage-sftp/impl/src/main/java/eu/cloudnetservice/modules/sftp/impl/SFTPTemplateStorage.java:160-169 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/nukkit/NukkitSignsPlugin.java:65— modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/nukkit/NukkitSignsPlugin.java:65-73 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/sponge/SpongeSignsPlugin.java:62-69 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/limboloohp/LimboLoohpBridgePlugin.java:54— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/limboloohp/LimboLoohpBridgePlugin.java:54-61 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/sponge/SpongeBridgePlugin.java:62-70 — 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.
Duplicated block (7 lines × 2) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/velocity/VelocityDirectPlayerExecutor.java:86— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/velocity/VelocityDirectPlayerExecutor.java:86-92 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/velocity/VelocityDirectPlayerExecutor.java:98-104 — both copies are in the same file, so extract the 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 `modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/velocity/VelocityDirectPlayerExecutor.java:86` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/sponge/functionality/SignsCommand.java:59— modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/sponge/functionality/SignsCommand.java:59-65 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/sponge/functionality/SignsCommand.java:112-118 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/client/NettyNetworkClient.java:243— driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/client/NettyNetworkClient.java:243-249 | driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/server/NettyNetworkServer.java:278-284 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/limboloohp/LimboLoohpPlayerManagementListener.java:51— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/limboloohp/LimboLoohpPlayerManagementListener.java:51-57 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/nukkit/NukkitPlayerManagementListener.java:51-57 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, 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 `modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/limboloohp/LimboLoohpPlayerManagementListener.java:51` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/sponge/SpongeDirectPlayerExecutor.java:87— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/sponge/SpongeDirectPlayerExecutor.java:87-93 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/velocity/VelocityDirectPlayerExecutor.java:117-123 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabase.java:68— modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabase.java:68-74 | node/impl/src/main/java/eu/cloudnetservice/node/impl/database/h2/H2Database.java:77-83 — before extracting anything, compare `modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabase.java` and `node/impl/src/main/java/eu/cloudnetservice/node/impl/database/h2/H2Database.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) modules/storage-s3/impl/src/main/java/eu/cloudnetservice/modules/s3/impl/S3TemplateStorageModule.java:70— modules/storage-s3/impl/src/main/java/eu/cloudnetservice/modules/s3/impl/S3TemplateStorageModule.java:70-76 | modules/storage-sftp/impl/src/main/java/eu/cloudnetservice/modules/sftp/impl/SFTPTemplateStorageModule.java:88-94 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/protocol/DefaultPacketListenerRegistry.java:111— driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/protocol/DefaultPacketListenerRegistry.java:111-117 | driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/rpc/handler/DefaultRPCHandlerRegistry.java:124-130 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/PlatformPlayerManager.java:83— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/PlatformPlayerManager.java:83-89 | wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/database/WrapperDatabaseProvider.java:45-51 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordDirectPlayerExecutor.java:142— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordDirectPlayerExecutor.java:142-148 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/waterdog/WaterDogPEDirectPlayerExecutor.java:124-130 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordDirectPlayerExecutor.java:138` calls `forEach`, `sendData` and `modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/waterdog/WaterDogPEDirectPlayerExecutor.java:119` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 2) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/limboloohp/LimboLoohpPlayerManagementListener.java:93— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/limboloohp/LimboLoohpPlayerManagementListener.java:93-99 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/nukkit/NukkitPlayerManagementListener.java:95-101 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note first that the copies are not typed on the same thing: `PlayerQuitEvent` names `cn.nukkit.event.player.PlayerQuitEvent` in one and `com.loohp.limbo.events.player.PlayerQuitEvent` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
TodoComment node/impl/src/main/java/eu/cloudnetservice/node/impl/Node.java:209— // TODO: remove in 4.1 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment node/impl/src/main/java/eu/cloudnetservice/node/impl/provider/NodeGroupConfigurationProvider.java:260— // TODO: remove in 4.1 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment node/impl/src/main/java/eu/cloudnetservice/node/impl/provider/NodeServiceTaskProvider.java:231— // TODO: remove in 4.1 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment node/impl/src/main/java/eu/cloudnetservice/node/impl/config/JsonConfiguration.java:109— // TODO: remove in 4.1 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment node/impl/src/main/java/eu/cloudnetservice/node/impl/console/ConsoleReadThread.java:40— // todo(derklaro): this can also throw an IOError, not sure how to handle that — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/sponge/SpongePlatformSign.java:103— // TODO: support text color — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/node/CloudNetSignsModule.java:69— // TODO: remove — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/CloudNetBridgeModule.java:203— // todo: remove in a release after 4.0.0-RC11 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/NettyUtil.java:125— // TODO: consider moving the default thread amount for an environment into the environment as a property — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/NettyUtil.java:160— // TODO: consider moving the default thread amount for an environment into the environment as a property — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Swallowed exception (caught, then discarded) utils/base/src/main/java/eu/cloudnetservice/utils/base/io/FileUtil.java:109— `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) node/impl/src/main/java/eu/cloudnetservice/node/impl/util/NetworkUtil.java:63— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) node/impl/src/main/java/eu/cloudnetservice/node/impl/config/ConfigurationUtil.java:72— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) node/impl/src/main/java/eu/cloudnetservice/node/impl/command/defaults/AerogelInjectionService.java:43— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) modules/storage-s3/impl/src/main/java/eu/cloudnetservice/modules/s3/impl/S3TemplateStorage.java:258— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) modules/storage-s3/impl/src/main/java/eu/cloudnetservice/modules/s3/impl/S3TemplateStorage.java:322— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) modules/storage-s3/impl/src/main/java/eu/cloudnetservice/modules/s3/impl/S3TemplateStorage.java:357— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bukkit/BukkitUtil.java:50— `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) ext/platform-scheduler/src/main/java/eu/cloudnetservice/ext/scheduler/SchedulerUtil.java:62— `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/rpc/handler/DefaultRPCHandler.java:226— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×9
Edited copy of a member (11 corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/listener/NodeSetupListener.java:49— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/listener/NodeSetupListener.java:49-60 | modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/node/listeners/NodeSetupListener.java:50-60 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/ArrayOps.java:87— wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/ArrayOps.java:87-97 | wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/MemoryOps.java:217-233 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) modules/labymod/impl/src/main/java/eu/cloudnetservice/modules/labymod/impl/platform/bungeecord/BungeeCordLabyModListener.java:40— modules/labymod/impl/src/main/java/eu/cloudnetservice/modules/labymod/impl/platform/bungeecord/BungeeCordLabyModListener.java:40-50 | modules/labymod/impl/src/main/java/eu/cloudnetservice/modules/labymod/impl/platform/velocity/VelocityLabyModListener.java:39-49 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabase.java:152— modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabase.java:152-162 | node/impl/src/main/java/eu/cloudnetservice/node/impl/database/h2/H2Database.java:163-174 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/MemoryOps.java:110— wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/MemoryOps.java:110-120 | wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/MemoryOps.java:172-185 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/node/listeners/NodeSetupListener.java:36— modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/node/listeners/NodeSetupListener.java:36-47 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/node/util/SignEntryTaskSetup.java:37-47 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/BukkitSignsPlugin.java:76— modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/BukkitSignsPlugin.java:76-88 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/nukkit/NukkitSignsPlugin.java:76-86 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/document/gson/ImmutableGsonDocument.java:482— driver/impl/src/main/java/eu/cloudnetservice/driver/impl/document/gson/ImmutableGsonDocument.java:482-492 | driver/impl/src/main/java/eu/cloudnetservice/driver/impl/document/gson/MutableGsonDocument.java:100-111 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/nukkit/NukkitPlatformSign.java:65— modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/nukkit/NukkitPlatformSign.java:65-75 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/sponge/SpongePlatformSign.java:67-77 — 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.
Duplicated block (5 lines × 2) ext/platform-inject-support/runtime/src/main/java/eu/cloudnetservice/ext/platforminject/runtime/platform/bungeecord/BungeeCordPlatformPluginManager.java:38— ext/platform-inject-support/runtime/src/main/java/eu/cloudnetservice/ext/platforminject/runtime/platform/bungeecord/BungeeCordPlatformPluginManager.java:38-42 | ext/platform-inject-support/runtime/src/main/java/eu/cloudnetservice/ext/platforminject/runtime/platform/waterdog/WaterDogPlatformPluginManager.java:45-49 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, 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 `ext/platform-inject-support/runtime/src/main/java/eu/cloudnetservice/ext/platforminject/runtime/platform/bungeecord/BungeeCordPlatformPluginManager.java:38` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `Plugin` names `dev.waterdog.waterdogpe.plugin.Plugin` in one and `net.md_5.bungee.api.plugin.Plugin` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (5 lines × 2) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordDirectPlayerExecutor.java:69— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordDirectPlayerExecutor.java:69-73 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/waterdog/WaterDogPEDirectPlayerExecutor.java:62-66 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/minestom/MinestomPlatformSign.java:98— modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/minestom/MinestomPlatformSign.java:98-102 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/nukkit/NukkitPlatformSign.java:104-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note first that the copies are not typed on the same thing: `DyeColor` names `cn.nukkit.utils.DyeColor` in one and `net.minestom.server.color.DyeColor` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (5 lines × 2) modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/platform/bungee/BungeeCordSyncProxyListener.java:90— modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/platform/bungee/BungeeCordSyncProxyListener.java:90-94 | modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/platform/velocity/VelocitySyncProxyListener.java:86-90 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/platform/bungee/BungeeCordSyncProxyListener.java:90` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `ProxyPingEvent` names `com.velocitypowered.api.event.proxy.ProxyPingEvent` in one and `net.md_5.bungee.api.event.ProxyPingEvent` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (5 lines × 2) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/rpc/rpc/DefaultRPC.java:209— driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/rpc/rpc/DefaultRPC.java:209-213 | driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/rpc/rpc/DefaultRPCChain.java:135-139 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/rpc/rpc/DefaultRPC.java:219— driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/rpc/rpc/DefaultRPC.java:219-223 | driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/rpc/rpc/DefaultRPCChain.java:145-149 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) ext/adventure-helper/src/main/java/eu/cloudnetservice/ext/component/AdventureComponentFormat.java:50— ext/adventure-helper/src/main/java/eu/cloudnetservice/ext/component/AdventureComponentFormat.java:50-54 | ext/adventure-helper/src/main/java/eu/cloudnetservice/ext/component/BungeeComponentFormat.java:44-48 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) node/impl/src/main/java/eu/cloudnetservice/node/impl/cluster/defaults/DefaultLocalNodeServer.java:216— node/impl/src/main/java/eu/cloudnetservice/node/impl/cluster/defaults/DefaultLocalNodeServer.java:216-220 | node/impl/src/main/java/eu/cloudnetservice/node/impl/provider/NodeClusterNodeProvider.java:195-199 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/BukkitPlatformSign.java:121— modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/BukkitPlatformSign.java:121-125 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/nukkit/NukkitPlatformSign.java:138-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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: `Player` names `cn.nukkit.Player` in one and `org.bukkit.entity.Player` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (8 lines × 2) modules/cloudflare/impl/src/main/java/eu/cloudnetservice/modules/cloudflare/impl/cloudflare/CloudFlareRecordManager.java:86— modules/cloudflare/impl/src/main/java/eu/cloudnetservice/modules/cloudflare/impl/cloudflare/CloudFlareRecordManager.java:86-93 | modules/cloudflare/impl/src/main/java/eu/cloudnetservice/modules/cloudflare/impl/cloudflare/CloudFlareRecordManager.java:120-129 — both copies are in the same file, so extract the 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 `modules/cloudflare/impl/src/main/java/eu/cloudnetservice/modules/cloudflare/impl/cloudflare/CloudFlareRecordManager.java:86` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 2) modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/bukkit/command/NPCCommand.java:466— modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/bukkit/command/NPCCommand.java:466-473 | modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/bukkit/command/NPCCommand.java:479-486 — both copies are in the same file, so extract the 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 `modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/bukkit/command/NPCCommand.java:466` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/node/NodeSignManagement.java:96— modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/node/NodeSignManagement.java:96-103 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/node/NodeSignManagement.java:108-115 — both copies are in the same file, so extract the 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 `modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/node/NodeSignManagement.java:96` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementMapping.java:92— wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementMapping.java:92-99 | wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementMapping.java:110-117 — both copies are in the same file, so extract the 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 `wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementMapping.java:92` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabase.java:197— modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabase.java:197-204 | node/impl/src/main/java/eu/cloudnetservice/node/impl/database/h2/H2Database.java:227-234 — before extracting anything, compare `modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabase.java` and `node/impl/src/main/java/eu/cloudnetservice/node/impl/database/h2/H2Database.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) node/impl/src/main/java/eu/cloudnetservice/node/impl/template/NodeTemplateStorageProvider.java:54— node/impl/src/main/java/eu/cloudnetservice/node/impl/template/NodeTemplateStorageProvider.java:54-61 | wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/provider/WrapperTemplateStorageProvider.java:56-63 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/command/PlayersCommand.java:98— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/command/PlayersCommand.java:98-105 | node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/TasksCommand.java:182-190 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/limboloohp/LimboLoohpDirectPlayerExecutor.java:84— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/limboloohp/LimboLoohpDirectPlayerExecutor.java:84-92 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/nukkit/NukkitDirectPlayerExecutor.java:76-83 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×7
Edited copy of a member (13 corresponding lines) modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/bukkit/listener/BukkitWorldListener.java:53— modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/bukkit/listener/BukkitWorldListener.java:53-66 | modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/bukkit/listener/BukkitWorldListener.java:69-81 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) utils/base/src/main/java/eu/cloudnetservice/utils/base/CodeGenerationUtil.java:84— utils/base/src/main/java/eu/cloudnetservice/utils/base/CodeGenerationUtil.java:84-96 | utils/base/src/main/java/eu/cloudnetservice/utils/base/CodeGenerationUtil.java:120-132 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) node/impl/src/main/java/eu/cloudnetservice/node/impl/console/ConsoleColor.java:63— node/impl/src/main/java/eu/cloudnetservice/node/impl/console/ConsoleColor.java:63-80 | node/impl/src/main/java/eu/cloudnetservice/node/impl/console/ConsoleColor.java:91-103 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabaseProvider.java:94— modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabaseProvider.java:94-107 | node/impl/src/main/java/eu/cloudnetservice/node/impl/database/h2/H2DatabaseProvider.java:71-83 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) modules/database-mongodb/impl/src/main/java/eu/cloudnetservice/modules/mongodb/impl/MongoDBDatabase.java:93— modules/database-mongodb/impl/src/main/java/eu/cloudnetservice/modules/mongodb/impl/MongoDBDatabase.java:93-105 | modules/database-mongodb/impl/src/main/java/eu/cloudnetservice/modules/mongodb/impl/MongoDBDatabase.java:141-153 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) modules/storage-sftp/impl/src/main/java/eu/cloudnetservice/modules/sftp/impl/SFTPTemplateStorage.java:233— modules/storage-sftp/impl/src/main/java/eu/cloudnetservice/modules/sftp/impl/SFTPTemplateStorage.java:233-247 | modules/storage-sftp/impl/src/main/java/eu/cloudnetservice/modules/sftp/impl/SFTPTemplateStorage.java:283-295 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/object/DefaultObjectMapper.java:250— driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/object/DefaultObjectMapper.java:250-262 | driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/object/DefaultObjectMapper.java:286-298 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (9 lines × 2) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/memory/MemorySegmentBuffer.java:406— driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/memory/MemorySegmentBuffer.java:406-414 | driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/memory/MemorySegmentBuffer.java:430-438 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) modules/database-mongodb/impl/src/main/java/eu/cloudnetservice/modules/mongodb/impl/MongoDBDatabase.java:159— modules/database-mongodb/impl/src/main/java/eu/cloudnetservice/modules/mongodb/impl/MongoDBDatabase.java:159-167 | modules/database-mongodb/impl/src/main/java/eu/cloudnetservice/modules/mongodb/impl/MongoDBDatabase.java:196-204 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `modules/database-mongodb/impl/src/main/java/eu/cloudnetservice/modules/mongodb/impl/MongoDBDatabase.java:159` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/node/listeners/NodeSetupListener.java:39— modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/node/listeners/NodeSetupListener.java:39-47 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/node/util/SignEntryTaskSetup.java:39-47 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, 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 `modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/node/listeners/NodeSetupListener.java:39` it begins part-way through the construct above it, so those exact lines 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) node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/TasksCommand.java:606— node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/TasksCommand.java:606-614 | node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/TasksCommand.java:697-705 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) node/impl/src/main/java/eu/cloudnetservice/node/impl/database/h2/H2Database.java:111— node/impl/src/main/java/eu/cloudnetservice/node/impl/database/h2/H2Database.java:111-119 | node/impl/src/main/java/eu/cloudnetservice/node/impl/database/h2/H2Database.java:149-157 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) node/impl/src/main/java/eu/cloudnetservice/node/impl/provider/NodeGroupConfigurationProvider.java:268— node/impl/src/main/java/eu/cloudnetservice/node/impl/provider/NodeGroupConfigurationProvider.java:268-276 | node/impl/src/main/java/eu/cloudnetservice/node/impl/provider/NodeServiceTaskProvider.java:246-254 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/fabric/FabricPluginInfoGenerator.java:89— ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/fabric/FabricPluginInfoGenerator.java:89-97 | ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/fabric/FabricPluginInfoGenerator.java:102-110 — both copies are in the same file, so extract the 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 `ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/fabric/FabricPluginInfoGenerator.java:89` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Low cohesion: ServiceCommand (LCOM4 15) node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/ServiceCommand.java:72— ServiceCommand's methods fall into 15 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 15 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.
Low cohesion: Parsers (LCOM4 13) node/impl/src/main/java/eu/cloudnetservice/node/impl/console/animation/setup/answer/Parsers.java:41— Parsers's methods fall into 13 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 13 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.
Low cohesion: TemplateCommand (LCOM4 9) node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/TemplateCommand.java:62— TemplateCommand's methods fall into 9 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 9 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.
Low cohesion: ClusterCommand (LCOM4 8) node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/ClusterCommand.java:77— ClusterCommand's methods fall into 8 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 8 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.
Low cohesion: TasksCommand (LCOM4 8) node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/TasksCommand.java:78— TasksCommand's methods fall into 8 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 8 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.
Low cohesion: GroupsCommand (LCOM4 4) node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/GroupsCommand.java:55— GroupsCommand's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: BukkitFunctionalityListener (LCOM4 4) modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/bukkit/listener/BukkitFunctionalityListener.java:54— BukkitFunctionalityListener's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×6
Edited copy of a member (6 corresponding lines) node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/ModulesCommand.java:193— node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/ModulesCommand.java:193-198 | node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/ModulesCommand.java:235-240 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bukkit/BukkitPlayerManagementListener.java:83— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bukkit/BukkitPlayerManagementListener.java:83-88 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/nukkit/NukkitPlayerManagementListener.java:86-92 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordDirectPlayerExecutor.java:60— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordDirectPlayerExecutor.java:60-65 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/waterdog/WaterDogPEDirectPlayerExecutor.java:53-58 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) node/impl/src/main/java/eu/cloudnetservice/node/impl/Node.java:457— node/impl/src/main/java/eu/cloudnetservice/node/impl/Node.java:457-463 | wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/Wrapper.java:160-165 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) modules/influx/impl/src/main/java/eu/cloudnetservice/modules/influx/impl/publishers/ConnectedNodeInfoPublisher.java:36— modules/influx/impl/src/main/java/eu/cloudnetservice/modules/influx/impl/publishers/ConnectedNodeInfoPublisher.java:36-42 | node/impl/src/main/java/eu/cloudnetservice/node/impl/provider/NodeClusterNodeProvider.java:126-131 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/minestom/MinestomSignsExtension.java:63— modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/minestom/MinestomSignsExtension.java:63-68 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/sponge/SpongeSignsPlugin.java:72-77 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
FileTooLong: memory/MemorySegmentBuffer.java driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/memory/MemorySegmentBuffer.java— FileTooLong — 839 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: MemorySegmentBuffer (58-1707). The bar is 500 significant lines; this is 339 over it, 1.68× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: unsafe/UnsafeReplacementDelegate.java wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java— FileTooLong — 716 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: UnsafeReplacementDelegate (47-1287). The bar is 500 significant lines; this is 216 over it, 1.43× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: sub/TasksCommand.java node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/TasksCommand.java— FileTooLong — 680 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 180 over it, 1.36× 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: command/NPCCommand.java modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/bukkit/command/NPCCommand.java— FileTooLong — 593 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: NPCCommand (62-877). The bar is 500 significant lines; this is 93 over it, 1.19× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: defaults/AbstractService.java node/impl/src/main/java/eu/cloudnetservice/node/impl/service/defaults/AbstractService.java— FileTooLong — 578 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: AbstractService (90-920). The bar is 500 significant lines; this is 78 over it, 1.16× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×5
Edited copy of a member (5 corresponding lines) modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/node/NodeNPCManagement.java:118— modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/node/NodeNPCManagement.java:118-122 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/node/NodeSignManagement.java:71-76 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bukkit/BukkitDirectPlayerExecutor.java:72— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bukkit/BukkitDirectPlayerExecutor.java:72-76 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/limboloohp/LimboLoohpDirectPlayerExecutor.java:77-81 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/node/NodeNPCManagement.java:159— modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/node/NodeNPCManagement.java:159-163 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/node/NodeSignManagement.java:118-122 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) driver/api/src/main/java/eu/cloudnetservice/driver/document/send/element/ArrayElement.java:41— driver/api/src/main/java/eu/cloudnetservice/driver/document/send/element/ArrayElement.java:41-45 | driver/api/src/main/java/eu/cloudnetservice/driver/document/send/element/ObjectElement.java:40-44 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/BukkitPlatformSign.java:48— modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/BukkitPlatformSign.java:48-52 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/nukkit/NukkitPlatformSign.java:57-62 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (6 lines × 2) modules/smart/impl/src/main/java/eu/cloudnetservice/modules/smart/impl/listener/CloudNetLocalServiceListener.java:62— modules/smart/impl/src/main/java/eu/cloudnetservice/modules/smart/impl/listener/CloudNetLocalServiceListener.java:62-68 | modules/smart/impl/src/main/java/eu/cloudnetservice/modules/smart/impl/listener/CloudNetLocalServiceListener.java:88-93 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note first that the copies are not typed on the same thing: the declarations holding them bind `event` to `CloudServicePostLifecycleEvent` in one and `CloudServicePrePrepareEvent` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (6 lines × 2) node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/GroupsCommand.java:193— node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/GroupsCommand.java:193-198 | node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/GroupsCommand.java:300-305 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) modules/database-mongodb/impl/src/main/java/eu/cloudnetservice/modules/mongodb/impl/CloudNetMongoDatabaseModule.java:48— modules/database-mongodb/impl/src/main/java/eu/cloudnetservice/modules/mongodb/impl/CloudNetMongoDatabaseModule.java:48-53 | modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/CloudNetMySQLDatabaseModule.java:71-76 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordDirectPlayerExecutor.java:80— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordDirectPlayerExecutor.java:80-85 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/waterdog/WaterDogPEDirectPlayerExecutor.java:73-78 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordDirectPlayerExecutor.java:80` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/bukkit/listener/BukkitWorldListener.java:59— modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/bukkit/listener/BukkitWorldListener.java:59-64 | modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/bukkit/listener/BukkitWorldListener.java:74-79 — both copies are in the same file, so extract the 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 `modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/bukkit/listener/BukkitWorldListener.java:59` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `event` to `ChunkLoadEvent` in one and `ChunkUnloadEvent` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Swallowed exception (empty catch) wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/ShutdownHandler.java:49— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:158— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) modules/storage-sftp/impl/src/main/java/eu/cloudnetservice/modules/sftp/impl/SFTPClientPool.java:185— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) launcher/java22/src/main/java/eu/cloudnetservice/launcher/java22/util/Environment.java:46— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) ext/platform-inject-support/api/src/main/java/eu/cloudnetservice/ext/platforminject/api/defaults/BasePlatformPluginManager.java:137— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
MethodTooLong: NPCCommand.onCommand modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/bukkit/command/NPCCommand.java:104— MethodTooLong — onCommand runs 414 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 314 over it, 4.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SystemInfoDataEmitter.emitData modules/report/impl/src/main/java/eu/cloudnetservice/modules/report/impl/emitter/defaults/SystemInfoDataEmitter.java:41— MethodTooLong — emitData runs 118 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 18 over it, 1.18× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: NodePlayerChannelMessageListener.handle modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/network/NodePlayerChannelMessageListener.java:50— MethodTooLong — handle runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.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: JsonConfiguration.load node/impl/src/main/java/eu/cloudnetservice/node/impl/config/JsonConfiguration.java:150— MethodTooLong — load runs 102 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
ClassTooLong: MemorySegmentBuffer driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/memory/MemorySegmentBuffer.java:58— ClassTooLong — 809 significant lines (blank, comment-only and punctuation-only lines excluded), 126 methods. The bar is 400 significant lines; this is 409 over it, 2.02× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: UnsafeReplacementDelegate wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:47— ClassTooLong — 696 significant lines (blank, comment-only and punctuation-only lines excluded), 99 methods. The bar is 400 significant lines; this is 296 over it, 1.74× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: NPCCommand modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/bukkit/command/NPCCommand.java:62— ClassTooLong — 550 significant lines (blank, comment-only and punctuation-only lines excluded), 6 methods. The bar is 400 significant lines; this is 150 over it, 1.38× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AbstractService node/impl/src/main/java/eu/cloudnetservice/node/impl/service/defaults/AbstractService.java:90— ClassTooLong — 507 significant lines (blank, comment-only and punctuation-only lines excluded), 74 methods. The bar is 400 significant lines; this is 107 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×4
Edited copy of a member (16 corresponding lines) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/memory/MemorySegmentBuffer.java:468— driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/memory/MemorySegmentBuffer.java:468-484 | driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/memory/MemorySegmentBuffer.java:490-505 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) node/impl/src/main/java/eu/cloudnetservice/node/impl/cluster/defaults/DefaultNodeServerProvider.java:184— node/impl/src/main/java/eu/cloudnetservice/node/impl/cluster/defaults/DefaultNodeServerProvider.java:184-200 | node/impl/src/main/java/eu/cloudnetservice/node/impl/cluster/defaults/DefaultNodeServerProvider.java:207-222 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/PlatformNPCManagement.java:83— modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/PlatformNPCManagement.java:83-98 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/PlatformSignManagement.java:103-118 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) node/impl/src/main/java/eu/cloudnetservice/node/impl/provider/NodeClusterNodeProvider.java:89— node/impl/src/main/java/eu/cloudnetservice/node/impl/provider/NodeClusterNodeProvider.java:89-104 | node/impl/src/main/java/eu/cloudnetservice/node/impl/provider/NodeClusterNodeProvider.java:107-123 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (12 lines × 2) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/network/NodePlayerChannelMessageListener.java:150— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/network/NodePlayerChannelMessageListener.java:150-161 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/network/NodePlayerChannelMessageListener.java:202-213 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/network/NodePlayerChannelMessageListener.java:150` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabase.java:213— modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabase.java:213-224 | node/impl/src/main/java/eu/cloudnetservice/node/impl/database/h2/H2Database.java:208-219 — before extracting anything, compare `modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabase.java` and `node/impl/src/main/java/eu/cloudnetservice/node/impl/database/h2/H2Database.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) modules/signs/api/src/main/java/eu/cloudnetservice/modules/signs/configuration/SignConfigurationEntry.java:48— modules/signs/api/src/main/java/eu/cloudnetservice/modules/signs/configuration/SignConfigurationEntry.java:48-59 | modules/signs/api/src/main/java/eu/cloudnetservice/modules/signs/configuration/SignConfigurationEntry.java:63-74 — both copies are in the same file, so extract the 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 `modules/signs/api/src/main/java/eu/cloudnetservice/modules/signs/configuration/SignConfigurationEntry.java:48` it begins part-way through the construct above it, so those exact lines 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) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignsCommand.java:54— modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignsCommand.java:54-65 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/nukkit/functionality/SignsCommand.java:44-55 — before extracting anything, compare `modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignsCommand.java` and `modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/nukkit/functionality/SignsCommand.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignsCommand.java:54` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `Command` names `cn.nukkit.command.Command` in one and `org.bukkit.command.Command` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (6 lines × 3) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordDirectPlayerExecutor.java:70— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordDirectPlayerExecutor.java:70-75 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordDirectPlayerExecutor.java:93-98 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordDirectPlayerExecutor.java:104-109 — 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 `modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordDirectPlayerExecutor.java:70` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 3) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/waterdog/WaterDogPEDirectPlayerExecutor.java:63— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/waterdog/WaterDogPEDirectPlayerExecutor.java:63-68 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/waterdog/WaterDogPEDirectPlayerExecutor.java:86-91 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/waterdog/WaterDogPEDirectPlayerExecutor.java:97-102 — 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 `modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/waterdog/WaterDogPEDirectPlayerExecutor.java:63` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 3) driver/api/src/main/java/eu/cloudnetservice/driver/document/property/DefaultingDocProperty.java:82— driver/api/src/main/java/eu/cloudnetservice/driver/document/property/DefaultingDocProperty.java:82-87 | driver/api/src/main/java/eu/cloudnetservice/driver/document/property/RewritingDocProperty.java:88-93 | driver/api/src/main/java/eu/cloudnetservice/driver/document/property/StandardDocProperty.java:75-80 — before extracting anything, compare `driver/api/src/main/java/eu/cloudnetservice/driver/document/property/DefaultingDocProperty.java` and `driver/api/src/main/java/eu/cloudnetservice/driver/document/property/StandardDocProperty.java` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `driver/api/src/main/java/eu/cloudnetservice/driver/document/property/DefaultingDocProperty.java:82` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note first that the copies are not typed on the same thing: the declarations holding them bind `readRewriteFunction` to `Function<E, V>` in one and `Function<O, V>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (6 lines × 3) wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/bukkit/FAWEConfigTransformer.java:48— wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/bukkit/FAWEConfigTransformer.java:48-53 | wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/bukkit/PaperConfigTransformer.java:50-55 | wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/bukkit/WorldEditJava8DetectorTransformer.java:47-52 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Change coupling: NettyNetworkClient.java ↔ NettyNetworkServer.java driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/client/NettyNetworkClient.java:1— `driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/client/NettyNetworkClient.java` and `driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/server/NettyNetworkServer.java` change together 82% of the time (9 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `18530b6b` drop: packet receive and packet send event (#1464) (at that commit the files were still `driver/src/main/java/eu/cloudnetservice/driver/network/netty/client/NettyNetworkClient.java` and `driver/src/main/java/eu/cloudnetservice/driver/network/netty/server/NettyNetworkServer.java`); `f0772bf5` chore: add a channel initializer that only sets supported options (#1… (at that commit the files were still `driver/src/main/java/eu/cloudnetservice/driver/network/netty/client/NettyNetworkClient.java` and `driver/src/main/java/eu/cloudnetservice/driver/network/netty/server/NettyNetworkServer.java`); `0dd885aa` fix: correct some netty channel options (#1080) (at that commit the files were still `driver/src/main/java/eu/cloudnetservice/driver/network/netty/client/NettyNetworkClient.java` and `driver/src/main/java/eu/cloudnetservice/driver/network/netty/server/NettyNetworkServer.java`) — run `git show` on any of them.
Change coupling: NodeGroupConfigurationProvider.java ↔ NodeServiceTaskProvider.java node/impl/src/main/java/eu/cloudnetservice/node/impl/provider/NodeGroupConfigurationProvider.java:1— `node/impl/src/main/java/eu/cloudnetservice/node/impl/provider/NodeGroupConfigurationProvider.java` and `node/impl/src/main/java/eu/cloudnetservice/node/impl/provider/NodeServiceTaskProvider.java` change together 62% of the time (10 of the 16 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 `dcce1a81` chore: allow re-using channel message builders again (#1695); `e91f1ea3` feat: add caching policies for remote inclusions (#1413) (at that commit the files were still `node/src/main/java/eu/cloudnetservice/node/provider/NodeGroupConfigurationProvider.java` and `node/src/main/java/eu/cloudnetservice/node/provider/NodeServiceTaskProvider.java`); `12f4c868` fix: group configurations are not upgraded correctly (#1274) (at that commit the files were still `node/src/main/java/eu/cloudnetservice/node/provider/NodeGroupConfigurationProvider.java` and `node/src/main/java/eu/cloudnetservice/node/provider/NodeServiceTaskProvider.java`) — run `git show` on any of them.
Change coupling: BungeeCordPlayerManagementListener.java ↔ VelocityPlayerManagementListener.java modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordPlayerManagementListener.java:1— `modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordPlayerManagementListener.java` and `modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/velocity/VelocityPlayerManagementListener.java` change together 60% of the time (9 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `860999f2` feat: allow to include disconnect reason in bridge messages (#1399); `5813e507` chore: allow to disable bridge messages (#957) (at that commit the files were still `modules/bridge/src/main/java/eu/cloudnetservice/modules/bridge/platform/bungeecord/BungeeCordPlayerManagementListener.java` and `modules/bridge/src/main/java/eu/cloudnetservice/modules/bridge/platform/velocity/VelocityPlayerManagementListener.java`); `9eb9da22` fix: correctly reset fallback profiles when keeping server connection… (at that commit the files were still `modules/bridge/src/main/java/eu/cloudnetservice/modules/bridge/platform/bungeecord/BungeeCordPlayerManagementListener.java` and `modules/bridge/src/main/java/eu/cloudnetservice/modules/bridge/platform/velocity/VelocityPlayerManagementListener.java`) — run `git show` on any of them.
D4 · Code Duplication· Edited copy of a member (25 corresponding lines) · ×3
Edited copy of a member (25 corresponding lines) wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/ArrayOps.java:205— wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/ArrayOps.java:205-229 | wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/ArrayOps.java:300-329 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (25 corresponding lines) node/impl/src/main/java/eu/cloudnetservice/node/impl/service/defaults/config/LimboLoohpServiceConfigurationPreparer.java:37— node/impl/src/main/java/eu/cloudnetservice/node/impl/service/defaults/config/LimboLoohpServiceConfigurationPreparer.java:37-61 | node/impl/src/main/java/eu/cloudnetservice/node/impl/service/defaults/config/VanillaServiceConfigurationPreparer.java:37-67 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (25 corresponding lines) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/rpc/rpc/DefaultRPC.java:237— driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/rpc/rpc/DefaultRPC.java:237-261 | driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/rpc/rpc/DefaultRPCChain.java:164-188 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×3
Edited copy of a member (19 corresponding lines) node/impl/src/main/java/eu/cloudnetservice/node/impl/Node.java:97— node/impl/src/main/java/eu/cloudnetservice/node/impl/Node.java:97-116 | wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/Wrapper.java:78-96 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) modules/smart/impl/src/main/java/eu/cloudnetservice/modules/smart/impl/listener/CloudNetLocalServiceListener.java:59— modules/smart/impl/src/main/java/eu/cloudnetservice/modules/smart/impl/listener/CloudNetLocalServiceListener.java:59-83 | modules/smart/impl/src/main/java/eu/cloudnetservice/modules/smart/impl/listener/CloudNetLocalServiceListener.java:86-104 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) node/impl/src/main/java/eu/cloudnetservice/node/impl/provider/NodeGroupConfigurationProvider.java:77— node/impl/src/main/java/eu/cloudnetservice/node/impl/provider/NodeGroupConfigurationProvider.java:77-97 | node/impl/src/main/java/eu/cloudnetservice/node/impl/provider/NodeServiceTaskProvider.java:84-102 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×3
Edited copy of a member (14 corresponding lines) ext/platform-inject-support/runtime/src/main/java/eu/cloudnetservice/ext/platforminject/runtime/platform/bungeecord/BungeeCordPlatformPluginManager.java:37— ext/platform-inject-support/runtime/src/main/java/eu/cloudnetservice/ext/platforminject/runtime/platform/bungeecord/BungeeCordPlatformPluginManager.java:37-50 | ext/platform-inject-support/runtime/src/main/java/eu/cloudnetservice/ext/platforminject/runtime/platform/limboloohp/LimboLoohpPlatformPluginManager.java:37-50 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/module/DefaultModuleWrapper.java:188— driver/impl/src/main/java/eu/cloudnetservice/driver/impl/module/DefaultModuleWrapper.java:188-201 | driver/impl/src/main/java/eu/cloudnetservice/driver/impl/module/DefaultModuleWrapper.java:207-227 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) modules/dockerized-services/impl/src/main/java/eu/cloudnetservice/modules/docker/impl/DockerizedLocalCloudServiceFactory.java:74— modules/dockerized-services/impl/src/main/java/eu/cloudnetservice/modules/docker/impl/DockerizedLocalCloudServiceFactory.java:74-92 | node/impl/src/main/java/eu/cloudnetservice/node/impl/service/defaults/factory/JVMLocalCloudServiceFactory.java:66-79 — 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 (21 corresponding lines) · ×3
Edited copy of a member (21 corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordBridgePlugin.java:74— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordBridgePlugin.java:74-94 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/waterdog/WaterDogPEBridgePlugin.java:63-87 — 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) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/object/DefaultObjectMapper.java:304— driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/object/DefaultObjectMapper.java:304-324 | driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/object/DefaultObjectMapper.java:331-351 — 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) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bukkit/BukkitBridgeManagement.java:74— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bukkit/BukkitBridgeManagement.java:74-94 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/limboloohp/LimboLoohpBridgeManagement.java:74-94 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×3
Edited copy of a member (18 corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordPlayerManagementListener.java:211— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordPlayerManagementListener.java:211-228 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/velocity/VelocityPlayerManagementListener.java:142-160 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) modules/storage-s3/impl/src/main/java/eu/cloudnetservice/modules/s3/impl/S3TemplateStorageModule.java:39— modules/storage-s3/impl/src/main/java/eu/cloudnetservice/modules/s3/impl/S3TemplateStorageModule.java:39-67 | modules/storage-sftp/impl/src/main/java/eu/cloudnetservice/modules/sftp/impl/SFTPTemplateStorageModule.java:68-85 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/BukkitSignManagement.java:67— modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/BukkitSignManagement.java:67-84 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/nukkit/NukkitSignManagement.java:69-91 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×3
Edited copy of a member (15 corresponding lines) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignInteractListener.java:39— modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignInteractListener.java:39-53 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/nukkit/functionality/SignInteractListener.java:39-54 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) modules/database-mongodb/impl/src/main/java/eu/cloudnetservice/modules/mongodb/impl/MongoDBDatabase.java:156— modules/database-mongodb/impl/src/main/java/eu/cloudnetservice/modules/mongodb/impl/MongoDBDatabase.java:156-170 | modules/database-mongodb/impl/src/main/java/eu/cloudnetservice/modules/mongodb/impl/MongoDBDatabase.java:193-207 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/VersionCommand.java:178— node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/VersionCommand.java:178-192 | node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/VersionCommand.java:204-218 — 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· Edited copy of a member (12 corresponding lines) · ×3
Edited copy of a member (12 corresponding lines) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/client/NettyNetworkClientInitializer.java:57— driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/client/NettyNetworkClientInitializer.java:57-71 | driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/server/NettyNetworkServerInitializer.java:57-68 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/MemoryOps.java:60— wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/MemoryOps.java:60-71 | wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/MemoryOps.java:87-99 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/bukkit/entity/BukkitPlatformSelectorEntity.java:347— modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/bukkit/entity/BukkitPlatformSelectorEntity.java:347-361 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/BukkitPlatformSign.java:70-81 — 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 copies of one member (3 members, 13+ corresponding lines) · ×3
Edited copies of one member (3 members, 13+ corresponding lines) node/impl/src/main/java/eu/cloudnetservice/node/impl/service/defaults/config/GlowstoneConfigurationPreparer.java:35— node/impl/src/main/java/eu/cloudnetservice/node/impl/service/defaults/config/GlowstoneConfigurationPreparer.java:35-48 | node/impl/src/main/java/eu/cloudnetservice/node/impl/service/defaults/config/VelocityConfigurationPreparer.java:35-47 | node/impl/src/main/java/eu/cloudnetservice/node/impl/service/defaults/config/WaterdogPEConfigurationPreparer.java:35-47 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 13+ corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/helper/ProxyPlatformHelper.java:45— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/helper/ProxyPlatformHelper.java:45-59 | modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/PlatformNPCManagement.java:139-151 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/PlatformSignManagement.java:154-166 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 13+ corresponding lines) modules/storage-s3/impl/src/main/java/eu/cloudnetservice/modules/s3/impl/S3TemplateStorage.java:311— modules/storage-s3/impl/src/main/java/eu/cloudnetservice/modules/s3/impl/S3TemplateStorage.java:311-325 | modules/storage-s3/impl/src/main/java/eu/cloudnetservice/modules/s3/impl/S3TemplateStorage.java:333-345 | modules/storage-s3/impl/src/main/java/eu/cloudnetservice/modules/s3/impl/S3TemplateStorage.java:348-360 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×3
Edited copy of a member (10 corresponding lines) modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/node/NodeNPCManagement.java:147— modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/node/NodeNPCManagement.java:147-156 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/node/NodeSignManagement.java:106-115 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) node/impl/src/main/java/eu/cloudnetservice/node/impl/provider/NodeClusterNodeProvider.java:211— node/impl/src/main/java/eu/cloudnetservice/node/impl/provider/NodeClusterNodeProvider.java:211-220 | node/impl/src/main/java/eu/cloudnetservice/node/impl/provider/NodeClusterNodeProvider.java:222-231 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/TasksCommand.java:645— node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/TasksCommand.java:645-654 | node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/TasksCommand.java:733-742 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 13+ corresponding lines) · ×3
Edited copies of one member (4 members, 13+ corresponding lines) node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/GroupsCommand.java:192— node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/GroupsCommand.java:192-204 | node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/GroupsCommand.java:299-312 | node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/TasksCommand.java:605-619 | node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/TasksCommand.java:696-710 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 13+ corresponding lines) modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/node/command/SyncProxyCommand.java:151— modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/node/command/SyncProxyCommand.java:151-163 | modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/node/command/SyncProxyCommand.java:171-183 | modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/node/command/SyncProxyCommand.java:191-203 | modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/node/command/SyncProxyCommand.java:211-223 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 13+ corresponding lines) node/impl/src/main/java/eu/cloudnetservice/node/impl/provider/NodeGroupConfigurationProvider.java:133— node/impl/src/main/java/eu/cloudnetservice/node/impl/provider/NodeGroupConfigurationProvider.java:133-146 | node/impl/src/main/java/eu/cloudnetservice/node/impl/provider/NodeGroupConfigurationProvider.java:157-169 | node/impl/src/main/java/eu/cloudnetservice/node/impl/provider/NodeServiceTaskProvider.java:138-151 | node/impl/src/main/java/eu/cloudnetservice/node/impl/provider/NodeServiceTaskProvider.java:162-174 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 9+ corresponding lines) · ×3
Edited copies of one member (4 members, 9+ corresponding lines) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/BukkitSignManagement.java:124— modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/BukkitSignManagement.java:124-138 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/minestom/MinestomSignManagement.java:128-136 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/nukkit/NukkitSignManagement.java:131-145 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/sponge/SpongeSignManagement.java:138-152 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 9+ corresponding lines) wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:316— wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:316-324 | wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:328-336 | wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:937-945 | wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:991-999 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 9+ corresponding lines) wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:388— wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:388-396 | wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:400-408 | wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:949-957 | wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:1003-1011 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
SignsCommand.onCommand (cyclomatic 21) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignsCommand.java:53— SignsCommand.onCommand has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SignsCommand.onCommand (cyclomatic 21) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/nukkit/functionality/SignsCommand.java:43— SignsCommand.onCommand has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
HackComment driver/impl/src/main/java/eu/cloudnetservice/driver/impl/channel/BaseCloudMessenger.java:57— // hack: get a new incomplete future here so that the previous thenApply step runs as well. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment driver/impl/src/main/java/eu/cloudnetservice/driver/impl/channel/BaseCloudMessenger.java:84— // hack: get a new incomplete future here so that the previous thenApply step runs as well. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
SignsCommand.onCommand (cognitive 32) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignsCommand.java:53— SignsCommand.onCommand has cognitive complexity 32 (threshold 15). Drivers by points: if/else 14 (20 pts), boolean chains 7, ternaries 2 (5 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SignsCommand.onCommand (cognitive 32) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/nukkit/functionality/SignsCommand.java:43— SignsCommand.onCommand has cognitive complexity 32 (threshold 15). Drivers by points: if/else 14 (20 pts), boolean chains 7, ternaries 2 (5 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (4 members, 50+ identical tokens) modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabase.java:97— modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabase.java:97-114 | modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabase.java:117-149 | node/impl/src/main/java/eu/cloudnetservice/node/impl/database/h2/H2Database.java:108-121 | node/impl/src/main/java/eu/cloudnetservice/node/impl/database/h2/H2Database.java:124-160 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/BukkitSignManagement.java:92— modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/BukkitSignManagement.java:92-121 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/minestom/MinestomSignManagement.java:90-121 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/nukkit/NukkitSignManagement.java:99-128 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/sponge/SpongeSignManagement.java:100-130 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×2
Edited copy of a member (22 corresponding lines) ext/platform-inject-support/runtime/src/main/java/eu/cloudnetservice/ext/platforminject/runtime/platform/minestom/MinestomPlatformPluginManager.java:50— ext/platform-inject-support/runtime/src/main/java/eu/cloudnetservice/ext/platforminject/runtime/platform/minestom/MinestomPlatformPluginManager.java:50-74 | ext/platform-inject-support/runtime/src/main/java/eu/cloudnetservice/ext/platforminject/runtime/platform/waterdog/WaterDogPlatformPluginManager.java:44-65 — 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) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/channel/BaseCloudMessenger.java:42— driver/impl/src/main/java/eu/cloudnetservice/driver/impl/channel/BaseCloudMessenger.java:42-63 | driver/impl/src/main/java/eu/cloudnetservice/driver/impl/channel/BaseCloudMessenger.java:69-90 — 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 (28 corresponding lines) · ×2
Edited copy of a member (28 corresponding lines) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/document/gson/send/GsonDocumentSend.java:66— driver/impl/src/main/java/eu/cloudnetservice/driver/impl/document/gson/send/GsonDocumentSend.java:66-94 | driver/impl/src/main/java/eu/cloudnetservice/driver/impl/document/gson/send/GsonDocumentSend.java:104-131 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (28 corresponding lines) modules/cloudflare/impl/src/main/java/eu/cloudnetservice/modules/cloudflare/impl/cloudflare/CloudFlareRecordManager.java:82— modules/cloudflare/impl/src/main/java/eu/cloudnetservice/modules/cloudflare/impl/cloudflare/CloudFlareRecordManager.java:82-109 | modules/cloudflare/impl/src/main/java/eu/cloudnetservice/modules/cloudflare/impl/cloudflare/CloudFlareRecordManager.java:115-153 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×2
Edited copy of a member (26 corresponding lines) wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/ArrayOps.java:114— wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/ArrayOps.java:114-139 | wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/ArrayOps.java:157-188 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (26 corresponding lines) modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/SharedChannelMessageListener.java:36— modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/SharedChannelMessageListener.java:36-61 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/SharedChannelMessageListener.java:33-61 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (32 corresponding lines) · ×2
Edited copy of a member (32 corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/velocity/VelocityBridgeManagement.java:76— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/velocity/VelocityBridgeManagement.java:76-107 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/waterdog/WaterDogPEBridgeManagement.java:74-107 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (32 corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/velocity/VelocityPlayerManagementListener.java:63— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/velocity/VelocityPlayerManagementListener.java:63-94 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/waterdog/WaterDogPEPlayerManagementListener.java:64-95 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×2
Edited copy of a member (30 corresponding lines) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/client/NettyNetworkClient.java:113— driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/client/NettyNetworkClient.java:113-142 | driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/server/NettyNetworkServer.java:122-160 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (30 corresponding lines) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/rpc/rpc/DefaultRPC.java:267— driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/rpc/rpc/DefaultRPC.java:267-296 | driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/rpc/rpc/DefaultRPCChain.java:194-227 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×2
Edited copy of a member (24 corresponding lines) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/object/serializers/CollectionObjectSerializer.java:68— driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/object/serializers/CollectionObjectSerializer.java:68-91 | driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/object/serializers/MapObjectSerializer.java:68-92 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (24 corresponding lines) node/impl/src/main/java/eu/cloudnetservice/node/impl/command/defaults/DefaultCommandPostProcessor.java:50— node/impl/src/main/java/eu/cloudnetservice/node/impl/command/defaults/DefaultCommandPostProcessor.java:50-73 | node/impl/src/main/java/eu/cloudnetservice/node/impl/command/defaults/DefaultCommandPreProcessor.java:51-77 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×2
Edited copies of one member (3 members, 9+ corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/velocity/VelocityDirectPlayerExecutor.java:60— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/velocity/VelocityDirectPlayerExecutor.java:60-68 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/velocity/VelocityDirectPlayerExecutor.java:83-92 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/velocity/VelocityDirectPlayerExecutor.java:95-104 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 9+ corresponding lines) node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/ClusterCommand.java:192— node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/ClusterCommand.java:192-200 | node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/ModulesCommand.java:159-167 | node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/ModulesCommand.java:201-209 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×2
Edited copy of a member (4 corresponding lines) ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/PlatformPluginProcessor.java:60— ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/PlatformPluginProcessor.java:60-66 | ext/platform-inject-support/runtime/src/main/java/eu/cloudnetservice/ext/platforminject/runtime/DefaultPlatformPluginManagerRegistry.java:34-37 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bukkit/BukkitDirectPlayerExecutor.java:100— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bukkit/BukkitDirectPlayerExecutor.java:100-105 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/limboloohp/LimboLoohpDirectPlayerExecutor.java:115-118 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 8+ corresponding lines) · ×2
Edited copies of one member (4 members, 8+ corresponding lines) modules/smart/impl/src/main/java/eu/cloudnetservice/modules/smart/impl/SmartCommand.java:59— modules/smart/impl/src/main/java/eu/cloudnetservice/modules/smart/impl/SmartCommand.java:59-67 | node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/ModulesCommand.java:141-149 | node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/TasksCommand.java:269-276 | node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/TemplateCommand.java:114-122 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 8+ corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bukkit/BukkitBridgePlugin.java:55— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bukkit/BukkitBridgePlugin.java:55-62 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordBridgePlugin.java:62-71 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/nukkit/NukkitBridgePlugin.java:57-65 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/BukkitSignsPlugin.java:65-73 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Duplicated block (23–28 lines × 2) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignsCommand.java:70— modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignsCommand.java:70-97 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/nukkit/functionality/SignsCommand.java:59-81 — before extracting anything, compare `modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignsCommand.java` and `modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/nukkit/functionality/SignsCommand.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignsCommand.java:70` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. Note first that the copies are not typed on the same thing: `Command` names `cn.nukkit.command.Command` in one and `org.bukkit.command.Command` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (23–28 lines × 2) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignsCommand.java:123— modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignsCommand.java:123-150 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/nukkit/functionality/SignsCommand.java:100-122 — before extracting anything, compare `modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignsCommand.java` and `modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/nukkit/functionality/SignsCommand.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignsCommand.java:123` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: `Command` names `cn.nukkit.command.Command` in one and `org.bukkit.command.Command` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (11 lines × 2) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/memory/MemorySegmentBuffer.java:360— driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/memory/MemorySegmentBuffer.java:360-370 | driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/memory/MemorySegmentBuffer.java:382-392 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) modules/storage-s3/impl/src/main/java/eu/cloudnetservice/modules/s3/impl/S3TemplateStorage.java:149— modules/storage-s3/impl/src/main/java/eu/cloudnetservice/modules/s3/impl/S3TemplateStorage.java:149-159 | modules/storage-sftp/impl/src/main/java/eu/cloudnetservice/modules/sftp/impl/SFTPTemplateStorage.java:134-144 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/rpc/generation/RPCImplementationGenerator.java:347— driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/rpc/generation/RPCImplementationGenerator.java:347-356 | driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/rpc/handler/invoker/MethodInvokerGenerator.java:75-84 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, 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 `driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/rpc/generation/RPCImplementationGenerator.java:347` it does not close everything it opens, so those 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, `driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/rpc/handler/invoker/MethodInvokerGenerator.java:86` calls `ofDescriptor`, `descriptorString` and `driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/rpc/generation/RPCImplementationGenerator.java:358` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordPlayerManagementListener.java:219— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordPlayerManagementListener.java:219-228 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/velocity/VelocityPlayerManagementListener.java:151-160 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordPlayerManagementListener.java:219` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) driver/api/src/main/java/eu/cloudnetservice/driver/module/ModuleLifeCycle.java:70— driver/api/src/main/java/eu/cloudnetservice/driver/module/ModuleLifeCycle.java:70-84 | driver/api/src/main/java/eu/cloudnetservice/driver/service/ServiceLifeCycle.java:58-72 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/_deprecated/configuration/NPCConfiguration.java:49— modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/_deprecated/configuration/NPCConfiguration.java:49-63 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/_deprecated/configuration/SignConfiguration.java:33-55 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Off the main sequence: :ext:modlauncher — :ext:modlauncher: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: :ext:adventure-helper — :ext:adventure-helper: abstractness 0.22, instability 0.00, distance 0.78 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
X13 · Undrained process stream· Redirected process stream is never drained (deadlock) · ×2
Redirected process stream is never drained (deadlock) node/impl/src/main/java/eu/cloudnetservice/node/impl/util/JavaVersionResolver.java:57— The JDK pipes both `stdout` and `stderr` of this child — no `redirectErrorStream`, `redirectError`, `redirectOutput` or `inheritIO` is set — and the parent reads the other stream to its end while nothing reads stdout; that read returns only at end of stream, which the child never reaches. The JDK's own `Process` documentation warns that failing to read a child's output promptly "may cause the process to block, or even deadlock": once the child writes more than the pipe holds (measured on OpenJDK 25 / Linux: 60,000 bytes finishes, 70,000 hangs forever), it blocks on the write, never exits, and the wait never returns. Nothing fails loudly. Read every piped stream before (or while) waiting — a thread or `CompletableFuture` per stream — merge them with `redirectErrorStream(true)` and read the one stream before `waitFor`, or discard what you do not want with `redirectOutput`/`redirectError(ProcessBuilder.Redirect.DISCARD)` (or a file).
Redirected process stream is never drained (deadlock) launcher/java22/src/main/java/eu/cloudnetservice/launcher/java22/util/Environment.java:42— The JDK pipes both `stdout` and `stderr` of this child — no `redirectErrorStream`, `redirectError`, `redirectOutput` or `inheritIO` is set — and `process.waitFor()` is written before stdout and stderr is read, so nothing drains it while the parent waits. The JDK's own `Process` documentation warns that failing to read a child's output promptly "may cause the process to block, or even deadlock": once the child writes more than the pipe holds (measured on OpenJDK 25 / Linux: 60,000 bytes finishes, 70,000 hangs forever), it blocks on the write, never exits, and the wait never returns. Nothing fails loudly. Read every piped stream before (or while) waiting — a thread or `CompletableFuture` per stream — merge them with `redirectErrorStream(true)` and read the one stream before `waitFor`, or discard what you do not want with `redirectOutput`/`redirectError(ProcessBuilder.Redirect.DISCARD)` (or a file).
NPCCommand.onCommand (cyclomatic 114) modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/bukkit/command/NPCCommand.java:104— NPCCommand.onCommand has cyclomatic complexity 114 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/bukkit/command/NPCCommand.java holds 2 of the 8 methods over the threshold — including the worst — and 131 of the 160 points over it (82%), 21.8× the next-largest file (modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignsCommand.java at 6). 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.
NPCCommand.tabComplete (cyclomatic 47) modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/bukkit/command/NPCCommand.java:733— NPCCommand.tabComplete has cyclomatic complexity 47 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This file is where this pass's cyclomatic complexity CONCENTRATES: modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/bukkit/command/NPCCommand.java holds 2 of the 8 methods over the threshold — including the worst — and 131 of the 160 points over it (82%), 21.8× the next-largest file (modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignsCommand.java at 6). 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.
NodeCloudMessenger.findTargetChannels (cyclomatic 21) node/impl/src/main/java/eu/cloudnetservice/node/impl/provider/NodeCloudMessenger.java:198— NodeCloudMessenger.findTargetChannels has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
JsonConfiguration.load (cyclomatic 20) node/impl/src/main/java/eu/cloudnetservice/node/impl/config/JsonConfiguration.java:150— JsonConfiguration.load has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
NodePlayerChannelMessageListener.handle (cyclomatic 20) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/network/NodePlayerChannelMessageListener.java:50— NodePlayerChannelMessageListener.handle has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
PlatformSignManagement.nextFreeSign (cyclomatic 16) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/PlatformSignManagement.java:381— PlatformSignManagement.nextFreeSign has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
NPCCommand.onCommand (cognitive 186) modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/bukkit/command/NPCCommand.java:104— NPCCommand.onCommand has cognitive complexity 186 (threshold 15). Drivers by points: if/else 68 (151 pts), ternaries 3 (12 pts), loops 3 (9 pts), boolean chains 7, match/switch 3 (7 pts) (nesting depth added 102). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/bukkit/command/NPCCommand.java holds 2 of the 38 methods over the threshold — including the worst — and 176 of the 520 points over it (34%), 3.7× the next-largest file (modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/bukkit/BukkitPlatformNPCManagement.java at 48). 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.
BukkitPlatformNPCManagement.<init> (cognitive 61) modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/bukkit/BukkitPlatformNPCManagement.java:84— BukkitPlatformNPCManagement.<init> has cognitive complexity 61 (threshold 15). Drivers by points: if/else 11 (49 pts), loops 2 (9 pts), boolean chains 3 (nesting depth added 45). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
MinestomSignManagement.startKnockbackTask (cognitive 38) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/minestom/MinestomSignManagement.java:90— MinestomSignManagement.startKnockbackTask has cognitive complexity 38 (threshold 15). Drivers by points: if/else 6 (27 pts), loops 2 (9 pts), boolean chains 2 (nesting depth added 28). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
PlatformSignManagement.tick (cognitive 36) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/PlatformSignManagement.java:331— PlatformSignManagement.tick has cognitive complexity 36 (threshold 15). Drivers by points: if/else 8 (27 pts), loops 3 (6 pts), boolean chains 3 (nesting depth added 22). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
DefaultTickLoop.start (cognitive 33) node/impl/src/main/java/eu/cloudnetservice/node/impl/tick/DefaultTickLoop.java:162— DefaultTickLoop.start has cognitive complexity 33 (threshold 15). Drivers by points: if/else 7 (22 pts), error handling 2 (5 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BungeeComponentUtil.replaceText (cognitive 31) ext/adventure-helper/src/main/java/eu/cloudnetservice/ext/bungee/BungeeComponentUtil.java:40— BungeeComponentUtil.replaceText has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (24 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
BukkitSignManagement.startKnockbackTask (cognitive 31) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/BukkitSignManagement.java:92— BukkitSignManagement.startKnockbackTask has cognitive complexity 31 (threshold 15). Drivers by points: if/else 5 (19 pts), loops 2 (9 pts), boolean chains 3 (nesting depth added 21). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
NukkitSignManagement.startKnockbackTask (cognitive 31) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/nukkit/NukkitSignManagement.java:99— NukkitSignManagement.startKnockbackTask has cognitive complexity 31 (threshold 15). Drivers by points: if/else 5 (19 pts), loops 2 (9 pts), boolean chains 3 (nesting depth added 21). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
SpongeSignManagement.startKnockbackTask (cognitive 31) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/sponge/SpongeSignManagement.java:100— SpongeSignManagement.startKnockbackTask has cognitive complexity 31 (threshold 15). Drivers by points: if/else 5 (19 pts), loops 2 (9 pts), boolean chains 3 (nesting depth added 21). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
PlatformSignManagement.nextFreeSign (cognitive 30) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/PlatformSignManagement.java:381— PlatformSignManagement.nextFreeSign has cognitive complexity 30 (threshold 15). Drivers by points: if/else 8 (19 pts), boolean chains 6, ternaries 1 (4 pts), loops 1 (nesting depth added 14). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
AutoServiceProcessor.process (cognitive 29) driver/ap/src/main/java/eu/cloudnetservice/driver/ap/registry/AutoServiceProcessor.java:66— AutoServiceProcessor.process has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 3 (6 pts), error handling 1 (3 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NodeCloudMessenger.findTargetChannels (cognitive 27) node/impl/src/main/java/eu/cloudnetservice/node/impl/provider/NodeCloudMessenger.java:198— NodeCloudMessenger.findTargetChannels has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (14 pts), ternaries 5 (12 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ColumnFormatter.formatLines (cognitive 26) utils/base/src/main/java/eu/cloudnetservice/utils/base/column/ColumnFormatter.java:93— ColumnFormatter.formatLines has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 3 (7 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DefaultDataSyncRegistry.handle (cognitive 25) node/impl/src/main/java/eu/cloudnetservice/node/impl/cluster/sync/DefaultDataSyncRegistry.java:126— DefaultDataSyncRegistry.handle has cognitive complexity 25 (threshold 15). Drivers by points: if/else 4 (12 pts), error handling 2 (5 pts), loops 2 (4 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BungeeCordPlayerManagementListener.handle (cognitive 25) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordPlayerManagementListener.java:81— BungeeCordPlayerManagementListener.handle has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 4 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ComponentConverter.convertText (cognitive 24) ext/adventure-helper/src/main/java/eu/cloudnetservice/ext/component/ComponentConverter.java:36— ComponentConverter.convertText has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (18 pts), loops 2 (5 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CommandExceptionHandler.handleCommandExceptions (cognitive 23) node/impl/src/main/java/eu/cloudnetservice/node/impl/command/exception/CommandExceptionHandler.java:78— CommandExceptionHandler.handleCommandExceptions has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (20 pts), ternaries 1 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PlatformPluginProcessor.process (cognitive 23) ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/PlatformPluginProcessor.java:82— PlatformPluginProcessor.process has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 3 (5 pts), error handling 1 (2 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DefaultRPCMethodMetadata.extractAndValidateChainMeta (cognitive 21) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/rpc/introspec/DefaultRPCMethodMetadata.java:158— DefaultRPCMethodMetadata.extractAndValidateChainMeta has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 3, loops 1 (2 pts), ternaries 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DefaultModuleWrapper.pushLifecycleChange (cognitive 20) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/module/DefaultModuleWrapper.java:328— DefaultModuleWrapper.pushLifecycleChange has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 1 (4 pts), boolean chains 2 (nesting depth added 12). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
JsonConfiguration.load (cognitive 20) node/impl/src/main/java/eu/cloudnetservice/node/impl/config/JsonConfiguration.java:150— JsonConfiguration.load has cognitive complexity 20 (threshold 15). Drivers by points: if/else 18 (19 pts), loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
NPCCommand.tabComplete (cognitive 20) modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/bukkit/command/NPCCommand.java:733— NPCCommand.tabComplete has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (17 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/bukkit/command/NPCCommand.java holds 2 of the 38 methods over the threshold — including the worst — and 176 of the 520 points over it (34%), 3.7× the next-largest file (modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/bukkit/BukkitPlatformNPCManagement.java at 48). 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.
DependencyHelper.loadFromLibrariesFile (cognitive 19) launcher/java22/src/main/java/eu/cloudnetservice/launcher/java22/dependency/DependencyHelper.java:42— DependencyHelper.loadFromLibrariesFile has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (12 pts), ternaries 1 (5 pts), boolean chains 1, loops 1 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
LayoutUtil.layoutHolder (cognitive 18) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/util/LayoutUtil.java:57— LayoutUtil.layoutHolder has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 4 (9 pts), if/else 5 (7 pts), loops 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RPCExceptionUtil.serializeHandlingException (cognitive 17) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/rpc/handler/util/RPCExceptionUtil.java:53— RPCExceptionUtil.serializeHandlingException has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (8 pts), loops 3 (8 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NodeDisconnectTrackerTask.run (cognitive 17) node/impl/src/main/java/eu/cloudnetservice/node/impl/cluster/task/NodeDisconnectTrackerTask.java:41— NodeDisconnectTrackerTask.run has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 2, loops 2, error handling 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CopyFilterStepExecutor.execute (cognitive 17) node/impl/src/main/java/eu/cloudnetservice/node/impl/version/execute/defaults/CopyFilterStepExecutor.java:40— CopyFilterStepExecutor.execute has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 2 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CloudNetNPCModule.convertConfiguration (cognitive 17) modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/node/CloudNetNPCModule.java:61— CloudNetNPCModule.convertConfiguration has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 1 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BukkitPlatformNPCManagement.startEmoteTask (cognitive 17) modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/bukkit/BukkitPlatformNPCManagement.java:249— BukkitPlatformNPCManagement.startEmoteTask has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CloudNetTickListener.handleAutoStart (cognitive 17) modules/smart/impl/src/main/java/eu/cloudnetservice/modules/smart/impl/listener/CloudNetTickListener.java:133— CloudNetTickListener.handleAutoStart has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 4 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
DefaultDataSyncRegistry.prepareClusterData (cognitive 16) node/impl/src/main/java/eu/cloudnetservice/node/impl/cluster/sync/DefaultDataSyncRegistry.java:99— DefaultDataSyncRegistry.prepareClusterData has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 2 (6 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AuthorizationPacketListener.handle (cognitive 16) node/impl/src/main/java/eu/cloudnetservice/node/impl/network/listener/AuthorizationPacketListener.java:80— AuthorizationPacketListener.handle has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
AbstractService.updateLifecycle (cognitive 16) node/impl/src/main/java/eu/cloudnetservice/node/impl/service/defaults/AbstractService.java:350— AbstractService.updateLifecycle has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 1, match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ServiceVersionProvider.installServiceVersion (cognitive 16) node/impl/src/main/java/eu/cloudnetservice/node/impl/version/ServiceVersionProvider.java:160— ServiceVersionProvider.installServiceVersion has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (6 pts), loops 3 (6 pts), boolean chains 2, error handling 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BukkitFunctionalityListener.playOnJoinEmoteIds (cognitive 16) modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/bukkit/listener/BukkitFunctionalityListener.java:174— BukkitFunctionalityListener.playOnJoinEmoteIds has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 1 (3 pts) (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
NodeSignsConfigurationHelper.convertGlowingInConfig (cognitive 16) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/node/configuration/NodeSignsConfigurationHelper.java:117— NodeSignsConfigurationHelper.convertGlowingInConfig has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 2 (4 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Near-duplicate member pair (58 shared lines) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignsCommand.java:53— modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignsCommand.java:53-150 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/nukkit/functionality/SignsCommand.java:43-122 — These two members are variants of one another: 58 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (6 members, 50+ identical tokens) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordDirectPlayerExecutor.java:68— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordDirectPlayerExecutor.java:68-75 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordDirectPlayerExecutor.java:90-98 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordDirectPlayerExecutor.java:101-109 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/waterdog/WaterDogPEDirectPlayerExecutor.java:61-68 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/waterdog/WaterDogPEDirectPlayerExecutor.java:83-91 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/waterdog/WaterDogPEDirectPlayerExecutor.java:94-102 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication· Edited copy of a member (45 corresponding lines) · ×1
Edited copy of a member (45 corresponding lines) ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/bukkit/BukkitPluginInfoGenerator.java:57— ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/bukkit/BukkitPluginInfoGenerator.java:57-108 | ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/nukkit/NukkitPluginInfoGenerator.java:56-100 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (59 corresponding lines) · ×1
Edited copy of a member (59 corresponding lines) modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/platform/bungee/BungeeCordSyncProxyListener.java:56— modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/platform/bungee/BungeeCordSyncProxyListener.java:56-114 | modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/platform/velocity/VelocitySyncProxyListener.java:52-116 — These two members are one piece of code written twice and then edited apart: 59 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (57 corresponding lines) · ×1
Edited copy of a member (57 corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/listener/PlatformChannelMessageListener.java:68— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/listener/PlatformChannelMessageListener.java:68-142 | wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/network/listener/message/ServiceChannelMessageListener.java:42-98 — These two members are one piece of code written twice and then edited apart: 57 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (41 corresponding lines) · ×1
Edited copy of a member (41 corresponding lines) ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/sponge/SpongeMainClassGenerator.java:59— ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/sponge/SpongeMainClassGenerator.java:59-101 | ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/velocity/VelocityMainClassGenerator.java:55-95 — 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 (37 corresponding lines) · ×1
Edited copy of a member (37 corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/command/BungeeCordHubCommand.java:45— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/command/BungeeCordHubCommand.java:45-81 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/velocity/commands/VelocityHubCommand.java:38-75 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 18+ corresponding lines) · ×1
Edited copies of one member (3 members, 18+ corresponding lines) ext/platform-inject-support/runtime/src/main/java/eu/cloudnetservice/ext/platforminject/runtime/platform/bukkit/BukkitPlatformPluginManager.java:40— ext/platform-inject-support/runtime/src/main/java/eu/cloudnetservice/ext/platforminject/runtime/platform/bukkit/BukkitPlatformPluginManager.java:40-59 | ext/platform-inject-support/runtime/src/main/java/eu/cloudnetservice/ext/platforminject/runtime/platform/nukkit/NukkitPlatformPluginManager.java:41-58 | ext/platform-inject-support/runtime/src/main/java/eu/cloudnetservice/ext/platforminject/runtime/platform/velocity/VelocityPlatformPluginManager.java:42-61 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (31 corresponding lines) · ×1
Edited copy of a member (31 corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/command/BungeeCordCloudCommand.java:47— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/command/BungeeCordCloudCommand.java:47-77 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/waterdog/command/WaterDogPECloudCommand.java:52-84 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (35 corresponding lines) · ×1
Edited copy of a member (35 corresponding lines) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/memory/MemorySegmentBuffer.java:563— driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/memory/MemorySegmentBuffer.java:563-597 | driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/memory/MemorySegmentBuffer.java:612-650 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 22+ corresponding lines) · ×1
Edited copies of one member (3 members, 22+ corresponding lines) modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/platform/bungee/BungeeCordSyncProxyListener.java:117— modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/platform/bungee/BungeeCordSyncProxyListener.java:117-145 | modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/platform/velocity/VelocitySyncProxyListener.java:119-140 | modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/platform/waterdog/WaterDogPESyncProxyListener.java:88-111 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 10+ corresponding lines) · ×1
Edited copies of one member (3 members, 10+ corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordDirectPlayerExecutor.java:78— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordDirectPlayerExecutor.java:78-87 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/velocity/VelocityDirectPlayerExecutor.java:71-80 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/waterdog/WaterDogPEDirectPlayerExecutor.java:71-80 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 24+ corresponding lines) · ×1
Edited copies of one member (3 members, 24+ corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bukkit/BukkitPlayerManagementListener.java:57— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bukkit/BukkitPlayerManagementListener.java:57-80 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/nukkit/NukkitPlayerManagementListener.java:60-83 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/sponge/SpongePlayerManagementListener.java:62-87 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 21+ corresponding lines) · ×1
Edited copies of one member (4 members, 21+ corresponding lines) node/impl/src/main/java/eu/cloudnetservice/node/impl/network/listener/message/GroupChannelMessageListener.java:47— node/impl/src/main/java/eu/cloudnetservice/node/impl/network/listener/message/GroupChannelMessageListener.java:47-71 | node/impl/src/main/java/eu/cloudnetservice/node/impl/network/listener/message/TaskChannelMessageListener.java:47-71 | wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/network/listener/message/GroupChannelMessageListener.java:31-51 | wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/network/listener/message/TaskChannelMessageListener.java:31-51 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 20+ corresponding lines) · ×1
Edited copies of one member (3 members, 20+ corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/CloudNetBridgeModule.java:181— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/CloudNetBridgeModule.java:181-201 | modules/labymod/impl/src/main/java/eu/cloudnetservice/modules/labymod/impl/node/CloudNetLabyModModule.java:74-93 | modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/node/CloudNetSyncProxyModule.java:70-89 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 14+ corresponding lines) · ×1
Edited copies of one member (3 members, 14+ corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/command/BridgeCommand.java:65— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/command/BridgeCommand.java:65-78 | modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/node/NPCCommand.java:66-79 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/node/SignCommand.java:67-81 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 15+ corresponding lines) · ×1
Edited copies of one member (5 members, 15+ corresponding lines) wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:298— wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:298-312 | wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:587-605 | wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:856-876 | wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:913-933 | wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java:967-987 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 15+ corresponding lines) · ×1
Edited copies of one member (3 members, 15+ corresponding lines) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/BukkitPlatformSign.java:127— modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/BukkitPlatformSign.java:127-142 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/nukkit/NukkitPlatformSign.java:145-159 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/sponge/SpongePlatformSign.java:133-148 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 12+ corresponding lines) · ×1
Edited copies of one member (3 members, 12+ corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/player/NodePlayerManager.java:242— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/player/NodePlayerManager.java:242-253 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/player/NodePlayerManager.java:268-279 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/player/NodePlayerManager.java:439-452 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (7 members, 11+ corresponding lines) · ×1
Edited copies of one member (7 members, 11+ corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bukkit/BukkitBridgeManagement.java:157— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bukkit/BukkitBridgeManagement.java:157-167 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordBridgeManagement.java:176-186 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/limboloohp/LimboLoohpBridgeManagement.java:160-170 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/nukkit/NukkitBridgeManagement.java:152-162 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/sponge/SpongeBridgeManagement.java:170-180 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/velocity/VelocityBridgeManagement.java:183-193 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/waterdog/WaterDogPEBridgeManagement.java:184-194 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 11+ corresponding lines) · ×1
Edited copies of one member (4 members, 11+ corresponding lines) modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabase.java:165— modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabase.java:165-175 | modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabase.java:178-189 | node/impl/src/main/java/eu/cloudnetservice/node/impl/database/h2/H2Database.java:177-188 | node/impl/src/main/java/eu/cloudnetservice/node/impl/database/h2/H2Database.java:191-204 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 16+ corresponding lines) · ×1
Edited copies of one member (3 members, 16+ corresponding lines) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/memory/MemorySegmentBuffer.java:381— driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/memory/MemorySegmentBuffer.java:381-396 | driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/memory/MemorySegmentBuffer.java:403-421 | driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/memory/MemorySegmentBuffer.java:428-445 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 12+ corresponding lines) · ×1
Edited copies of one member (4 members, 12+ corresponding lines) modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabaseProvider.java:130— modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabaseProvider.java:130-143 | modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabaseProvider.java:151-167 | node/impl/src/main/java/eu/cloudnetservice/node/impl/database/h2/H2DatabaseProvider.java:105-116 | node/impl/src/main/java/eu/cloudnetservice/node/impl/database/h2/H2DatabaseProvider.java:124-137 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 7+ corresponding lines) · ×1
Edited copies of one member (3 members, 7+ corresponding lines) launcher/java22/src/main/java/eu/cloudnetservice/launcher/java22/updater/updaters/LauncherCloudNetUpdater.java:28— launcher/java22/src/main/java/eu/cloudnetservice/launcher/java22/updater/updaters/LauncherCloudNetUpdater.java:28-34 | launcher/java22/src/main/java/eu/cloudnetservice/launcher/java22/updater/updaters/LauncherModuleJsonUpdater.java:28-35 | launcher/java22/src/main/java/eu/cloudnetservice/launcher/java22/updater/updaters/LauncherPatcherUpdater.java:28-35 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 8+ corresponding lines) · ×1
Edited copies of one member (3 members, 8+ corresponding lines) node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/GroupsCommand.java:113— node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/GroupsCommand.java:113-120 | node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/GroupsCommand.java:158-167 | node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/TasksCommand.java:376-385 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 14+ corresponding lines) · ×1
Edited copies of one member (4 members, 14+ corresponding lines) modules/smart/impl/src/main/java/eu/cloudnetservice/modules/smart/impl/SmartCommand.java:78— modules/smart/impl/src/main/java/eu/cloudnetservice/modules/smart/impl/SmartCommand.java:78-91 | node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/ModulesCommand.java:110-124 | node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/ModulesCommand.java:177-190 | node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/ModulesCommand.java:219-232 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 11+ corresponding lines) · ×1
Edited copies of one member (3 members, 11+ corresponding lines) modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/PlatformNPCManagement.java:111— modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/PlatformNPCManagement.java:111-121 | modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/PlatformNPCManagement.java:124-136 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/PlatformSignManagement.java:131-145 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 6+ corresponding lines) · ×1
Edited copies of one member (5 members, 6+ corresponding lines) modules/dockerized-services/impl/src/main/java/eu/cloudnetservice/modules/docker/impl/DockerCommand.java:130— modules/dockerized-services/impl/src/main/java/eu/cloudnetservice/modules/docker/impl/DockerCommand.java:130-135 | modules/dockerized-services/impl/src/main/java/eu/cloudnetservice/modules/docker/impl/DockerCommand.java:164-169 | modules/dockerized-services/impl/src/main/java/eu/cloudnetservice/modules/docker/impl/DockerCommand.java:315-320 | modules/dockerized-services/impl/src/main/java/eu/cloudnetservice/modules/docker/impl/DockerCommand.java:339-344 | modules/dockerized-services/impl/src/main/java/eu/cloudnetservice/modules/docker/impl/DockerCommand.java:370-375 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 6+ corresponding lines) · ×1
Edited copies of one member (3 members, 6+ corresponding lines) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/command/BridgeCommand.java:81— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/command/BridgeCommand.java:81-86 | modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/node/NPCCommand.java:82-89 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/node/SignCommand.java:84-91 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 8+ corresponding lines) · ×1
Edited copies of one member (6 members, 8+ corresponding lines) node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/GroupsCommand.java:231— node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/GroupsCommand.java:231-242 | node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/GroupsCommand.java:250-257 | node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/GroupsCommand.java:265-274 | node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/GroupsCommand.java:335-342 | node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/GroupsCommand.java:350-357 | node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/GroupsCommand.java:365-374 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 7+ corresponding lines) · ×1
Edited copies of one member (4 members, 7+ corresponding lines) modules/labymod/impl/src/main/java/eu/cloudnetservice/modules/labymod/impl/node/NodeLabyModManagement.java:41— modules/labymod/impl/src/main/java/eu/cloudnetservice/modules/labymod/impl/node/NodeLabyModManagement.java:41-47 | modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/node/NodeSyncProxyManagement.java:47-54 | node/impl/src/main/java/eu/cloudnetservice/node/impl/provider/NodeClusterNodeProvider.java:58-66 | node/impl/src/main/java/eu/cloudnetservice/node/impl/service/defaults/NodeCloudServiceFactory.java:75-83 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (3 corresponding lines) · ×1
Edited copy of a member (3 corresponding lines) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/module/DefaultModuleProvider.java:178— driver/impl/src/main/java/eu/cloudnetservice/driver/impl/module/DefaultModuleProvider.java:178-182 | node/impl/src/main/java/eu/cloudnetservice/node/impl/cluster/defaults/DefaultNodeServerProvider.java:115-117 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 7+ corresponding lines) · ×1
Edited copies of one member (5 members, 7+ corresponding lines) ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/bungeecord/BungeeCordPlatformInfoProvider.java:24— ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/bungeecord/BungeeCordPlatformInfoProvider.java:24-32 | ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/fabric/FabricPlatformInfoProvider.java:24-30 | ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/sponge/SpongePlatformInfoProvider.java:24-30 | ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/velocity/VelocityPlatformInfoProvider.java:24-30 | ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/waterdog/WaterDogPlatformInfoProvider.java:24-30 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
Duplicated block (29–30 lines × 2) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/_deprecated/configuration/entry/SignConfigurationEntry.java:68— modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/_deprecated/configuration/entry/SignConfigurationEntry.java:68-97 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/_deprecated/configuration/entry/SignConfigurationEntry.java:99-127 — both copies are in the same file, so extract the 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 `modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/_deprecated/configuration/entry/SignConfigurationEntry.java:99` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (25 lines × 2) node/impl/src/main/java/eu/cloudnetservice/node/impl/network/listener/message/ServiceChannelMessageListener.java:122— node/impl/src/main/java/eu/cloudnetservice/node/impl/network/listener/message/ServiceChannelMessageListener.java:122-146 | wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/network/listener/message/ServiceChannelMessageListener.java:74-98 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `node/impl/src/main/java/eu/cloudnetservice/node/impl/network/listener/message/ServiceChannelMessageListener.java:122` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21–22 lines × 2) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/minestom/functionality/SignsCommand.java:117— modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/minestom/functionality/SignsCommand.java:117-137 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/minestom/functionality/SignsCommand.java:162-183 — both copies are in the same file, so extract the 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 `modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/minestom/functionality/SignsCommand.java:117` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) node/impl/src/main/java/eu/cloudnetservice/node/impl/command/defaults/DefaultCommandPostProcessor.java:51— node/impl/src/main/java/eu/cloudnetservice/node/impl/command/defaults/DefaultCommandPostProcessor.java:51-70 | node/impl/src/main/java/eu/cloudnetservice/node/impl/command/defaults/DefaultCommandPreProcessor.java:52-71 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `node/impl/src/main/java/eu/cloudnetservice/node/impl/command/defaults/DefaultCommandPostProcessor.java:51` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `context` to `CommandPostprocessingContext<CommandSource>` in one and `CommandPreprocessingContext<CommandSource>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (19–20 lines × 2) node/impl/src/main/java/eu/cloudnetservice/node/impl/service/defaults/config/LimboLoohpServiceConfigurationPreparer.java:39— node/impl/src/main/java/eu/cloudnetservice/node/impl/service/defaults/config/LimboLoohpServiceConfigurationPreparer.java:39-57 | node/impl/src/main/java/eu/cloudnetservice/node/impl/service/defaults/config/VanillaServiceConfigurationPreparer.java:39-58 — before extracting anything, compare `node/impl/src/main/java/eu/cloudnetservice/node/impl/service/defaults/config/LimboLoohpServiceConfigurationPreparer.java` and `node/impl/src/main/java/eu/cloudnetservice/node/impl/service/defaults/config/VanillaServiceConfigurationPreparer.java` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `node/impl/src/main/java/eu/cloudnetservice/node/impl/service/defaults/config/LimboLoohpServiceConfigurationPreparer.java:39` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/platform/bungee/BungeeCordSyncProxyListener.java:57— modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/platform/bungee/BungeeCordSyncProxyListener.java:57-74 | modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/platform/velocity/VelocitySyncProxyListener.java:53-70 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/platform/bungee/BungeeCordSyncProxyListener.java:57` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `ProxyPingEvent` names `com.velocitypowered.api.event.proxy.ProxyPingEvent` in one and `net.md_5.bungee.api.event.ProxyPingEvent` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/platform/bungee/BungeeCordSyncProxyListener.java:76` calls `getResponse` and `modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/platform/velocity/VelocitySyncProxyListener.java:72` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13–16 lines × 2) modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabase.java:228— modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabase.java:228-240 | node/impl/src/main/java/eu/cloudnetservice/node/impl/database/h2/H2Database.java:243-258 — before extracting anything, compare `modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabase.java` and `node/impl/src/main/java/eu/cloudnetservice/node/impl/database/h2/H2Database.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10–15 lines × 3) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignsCommand.java:124— modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignsCommand.java:124-138 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/minestom/functionality/SignsCommand.java:183-197 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/nukkit/functionality/SignsCommand.java:101-110 — before extracting anything, compare `modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignsCommand.java` and `modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/nukkit/functionality/SignsCommand.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignsCommand.java:124` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `Command` names `cn.nukkit.command.Command` in one and `org.bukkit.command.Command` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (14 lines × 2) ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/bukkit/BukkitPluginInfoGenerator.java:71— ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/bukkit/BukkitPluginInfoGenerator.java:71-84 | ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/nukkit/NukkitPluginInfoGenerator.java:69-82 — before extracting anything, compare `ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/bukkit/BukkitPluginInfoGenerator.java` and `ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/nukkit/NukkitPluginInfoGenerator.java` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/bukkit/BukkitPluginInfoGenerator.java:68` calls `putOrDefault`, `apiVersion` and `ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/nukkit/NukkitPluginInfoGenerator.java:66` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 2) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/object/serializers/CollectionObjectSerializer.java:71— driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/object/serializers/CollectionObjectSerializer.java:71-83 | driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/object/serializers/MapObjectSerializer.java:71-83 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/object/serializers/CollectionObjectSerializer.java:71` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 3) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/object/serializers/CollectionObjectSerializer.java:69— driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/object/serializers/CollectionObjectSerializer.java:69-80 | driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/object/serializers/MapObjectSerializer.java:69-80 | driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/object/serializers/OptionalObjectSerializer.java:45-56 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (11–12 lines × 2) driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/client/NettyNetworkClient.java:126— driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/client/NettyNetworkClient.java:126-137 | driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/server/NettyNetworkServer.java:146-156 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, 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 `driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/client/NettyNetworkClient.java:126` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11 lines × 3) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/network/NodePlayerChannelMessageListener.java:149— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/network/NodePlayerChannelMessageListener.java:149-159 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/network/NodePlayerChannelMessageListener.java:184-194 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/network/NodePlayerChannelMessageListener.java:201-211 — 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 `modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/network/NodePlayerChannelMessageListener.java:149` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9–10 lines × 3) node/impl/src/main/java/eu/cloudnetservice/node/impl/service/defaults/config/LimboLoohpServiceConfigurationPreparer.java:46— node/impl/src/main/java/eu/cloudnetservice/node/impl/service/defaults/config/LimboLoohpServiceConfigurationPreparer.java:46-55 | node/impl/src/main/java/eu/cloudnetservice/node/impl/service/defaults/config/NukkitConfigurationPreparer.java:45-53 | node/impl/src/main/java/eu/cloudnetservice/node/impl/service/defaults/config/VanillaServiceConfigurationPreparer.java:46-55 — before extracting anything, compare `node/impl/src/main/java/eu/cloudnetservice/node/impl/service/defaults/config/LimboLoohpServiceConfigurationPreparer.java` and `node/impl/src/main/java/eu/cloudnetservice/node/impl/service/defaults/config/VanillaServiceConfigurationPreparer.java` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `node/impl/src/main/java/eu/cloudnetservice/node/impl/service/defaults/config/NukkitConfigurationPreparer.java:45` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `node/impl/src/main/java/eu/cloudnetservice/node/impl/service/defaults/config/VanillaServiceConfigurationPreparer.java:45` calls `shouldRewriteIp` and `node/impl/src/main/java/eu/cloudnetservice/node/impl/service/defaults/config/NukkitConfigurationPreparer.java:44` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7–10 lines × 2) ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/bukkit/BukkitPluginInfoGenerator.java:80— ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/bukkit/BukkitPluginInfoGenerator.java:80-89 | ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/bungeecord/BungeeCordPluginInfoGenerator.java:53-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/bukkit/BukkitPluginInfoGenerator.java:80` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8–10 lines × 2) node/impl/src/main/java/eu/cloudnetservice/node/impl/Node.java:99— node/impl/src/main/java/eu/cloudnetservice/node/impl/Node.java:99-108 | wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/Wrapper.java:80-87 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `node/impl/src/main/java/eu/cloudnetservice/node/impl/Node.java:99` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/bukkit/BukkitPluginInfoGenerator.java:90— ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/bukkit/BukkitPluginInfoGenerator.java:90-108 | ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/nukkit/NukkitPluginInfoGenerator.java:82-100 — before extracting anything, compare `ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/bukkit/BukkitPluginInfoGenerator.java` and `ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/nukkit/NukkitPluginInfoGenerator.java` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/bukkit/BukkitPluginInfoGenerator.java:90` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8–9 lines × 2) modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabase.java:106— modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabase.java:106-114 | modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabase.java:142-149 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabase.java:106` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 4) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/BukkitSignManagement.java:94— modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/BukkitSignManagement.java:94-100 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/minestom/MinestomSignManagement.java:92-98 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/nukkit/NukkitSignManagement.java:101-107 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/sponge/SpongeSignManagement.java:102-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/BukkitSignManagement.java:94` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 4) modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabase.java:106— modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabase.java:106-112 | modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabase.java:142-147 | node/impl/src/main/java/eu/cloudnetservice/node/impl/database/h2/H2Database.java:111-118 | node/impl/src/main/java/eu/cloudnetservice/node/impl/database/h2/H2Database.java:149-156 — before extracting anything, compare `modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabase.java` and `node/impl/src/main/java/eu/cloudnetservice/node/impl/database/h2/H2Database.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `modules/database-mysql/impl/src/main/java/eu/cloudnetservice/modules/mysql/impl/MySQLDatabase.java:106` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (30 lines × 2) modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/_deprecated/configuration/entry/SignConfigurationEntryType.java:1— modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/_deprecated/configuration/entry/SignConfigurationEntryType.java:1-30 | modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/node/configuration/SignConfigurationType.java:1-31 — before extracting anything, compare `modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/_deprecated/configuration/entry/SignConfigurationEntryType.java` and `modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/node/configuration/SignConfigurationType.java` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/_deprecated/configuration/entry/SignConfigurationEntryType.java:1` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 3) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bukkit/BukkitDirectPlayerExecutor.java:86— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bukkit/BukkitDirectPlayerExecutor.java:86-92 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/limboloohp/LimboLoohpDirectPlayerExecutor.java:95-101 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/nukkit/NukkitDirectPlayerExecutor.java:86-92 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bukkit/BukkitDirectPlayerExecutor.java:96` calls `forEach`, `sendPluginMessage` and `modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/nukkit/NukkitDirectPlayerExecutor.java:97` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 3) modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/platform/bungee/BungeeCordSyncProxyManagement.java:56— modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/platform/bungee/BungeeCordSyncProxyManagement.java:56-68 | modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/platform/velocity/VelocitySyncProxyManagement.java:57-69 | modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/platform/waterdog/WaterDogPESyncProxyManagement.java:56-68 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/platform/bungee/BungeeCordSyncProxyManagement.java:56` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 3) modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/command/BungeeCordCloudCommand.java:79— modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/command/BungeeCordCloudCommand.java:79-83 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/velocity/commands/VelocityCloudCommand.java:83-88 | modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/waterdog/command/WaterDogPECloudCommand.java:86-91 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Note first that the copies are not typed on the same thing: `CommandSender` names `dev.waterdog.waterdogpe.command.CommandSender` in one and `net.md_5.bungee.api.CommandSender` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated predicate launcher/java22/src/main/java/eu/cloudnetservice/launcher/java22/cnl/CnlInterpreter.java:41— `!line.isEmpty() && !line.startsWith("#")` appears character-identically in 2 files — launcher/java22/src/main/java/eu/cloudnetservice/launcher/java22/cnl/CnlInterpreter.java, launcher/java22/src/main/java/eu/cloudnetservice/launcher/java22/dependency/DependencyHelper.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignsCommand.java:101— `(args.length == 1 || args.length == 2) && args[0].equalsIgnoreCase("cleanup")` appears character-identically in 2 files — modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignsCommand.java, modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/nukkit/functionality/SignsCommand.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignsCommand.java:65— `(args.length == 2 || args.length == 3) && args[0].equalsIgnoreCase("create")` appears character-identically in 2 files — modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignsCommand.java, modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/nukkit/functionality/SignsCommand.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate ext/adventure-helper/src/main/java/eu/cloudnetservice/ext/component/AdventureComponentFormat.java:51— `(current == COLOR_CHAR || current == LEGACY_CHAR) && next == HEX_CHAR && (pos + HEX_SEG_LENGTH) < fullData.length` appears character-identically in 2 files — ext/adventure-helper/src/main/java/eu/cloudnetservice/ext/component/AdventureComponentFormat.java, ext/adventure-helper/src/main/java/eu/cloudnetservice/ext/component/BungeeComponentFormat.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate node/impl/src/main/java/eu/cloudnetservice/node/impl/Node.java:102— `Files.notExists(langDir) || !Files.isDirectory(langDir)` appears character-identically in 2 files — node/impl/src/main/java/eu/cloudnetservice/node/impl/Node.java, wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/Wrapper.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignsCommand.java:93— `args.length == 1 && args[0].equalsIgnoreCase("cleanupall")` appears character-identically in 2 files — modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignsCommand.java, modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/nukkit/functionality/SignsCommand.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignsCommand.java:118— `args.length == 1 && args[0].equalsIgnoreCase("remove")` appears character-identically in 2 files — modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignsCommand.java, modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/nukkit/functionality/SignsCommand.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignsCommand.java:110— `args.length == 1 && args[0].equalsIgnoreCase("removeall")` appears character-identically in 2 files — modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/functionality/SignsCommand.java, modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/nukkit/functionality/SignsCommand.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/ArrayOps.java:376— `byteCount > 0 && kind != ValueTypeKind.REF` appears character-identically in 2 files — wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/ArrayOps.java, wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/MemoryOps.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/BukkitSignManagement.java:107— `conf.bypassPermission() == null || !player.hasPermission(conf.bypassPermission())` appears character-identically in 3 files — modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/bukkit/BukkitSignManagement.java, modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/nukkit/NukkitSignManagement.java, modules/signs/impl/src/main/java/eu/cloudnetservice/modules/signs/impl/platform/sponge/SpongeSignManagement.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate modules/labymod/impl/src/main/java/eu/cloudnetservice/modules/labymod/impl/node/NodeLabyModListener.java:31— `event.channel().equals(LabyModManagement.LABYMOD_MODULE_CHANNEL) && LabyModManagement.LABYMOD_UPDATE_CONFIG.equals(event.message())` appears character-identically in 2 files — modules/labymod/impl/src/main/java/eu/cloudnetservice/modules/labymod/impl/node/NodeLabyModListener.java, modules/labymod/impl/src/main/java/eu/cloudnetservice/modules/labymod/impl/platform/PlatformLabyModListener.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/listener/BridgeLocalProxyPlayerDisconnectListener.java:76— `event.newLifeCycle() == ServiceLifeCycle.STOPPED || event.newLifeCycle() == ServiceLifeCycle.DELETED` appears character-identically in 2 files — modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/node/listener/BridgeLocalProxyPlayerDisconnectListener.java, modules/cloudflare/impl/src/main/java/eu/cloudnetservice/modules/cloudflare/impl/listener/CloudflareServiceStateListener.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/ClusterCommand.java:163— `hostAndPort == null || NetworkUtil.checkWildcard(hostAndPort)` appears character-identically in 3 files — node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/ClusterCommand.java, node/impl/src/main/java/eu/cloudnetservice/node/impl/command/sub/TasksCommand.java, node/impl/src/main/java/eu/cloudnetservice/node/impl/console/animation/setup/answer/Parsers.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/command/BungeeCordCloudCommand.java:62— `info == null || !sender.hasPermission(info.permission())` appears character-identically in 2 files — modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/command/BungeeCordCloudCommand.java, modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/waterdog/command/WaterDogPECloudCommand.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bukkit/BukkitPlayerManagementListener.java:72— `permission != null && !event.getPlayer().hasPermission(permission)` appears character-identically in 4 files — modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bukkit/BukkitPlayerManagementListener.java, modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/nukkit/NukkitPlayerManagementListener.java, modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/velocity/VelocityPlayerManagementListener.java, modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/waterdog/WaterDogPEPlayerManagementListener.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordPlayerManagementListener.java:104— `permission != null && !player.hasPermission(permission)` appears character-identically in 2 files — modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordPlayerManagementListener.java, modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/limboloohp/LimboLoohpPlayerManagementListener.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bukkit/BukkitDirectPlayerExecutor.java:88— `permission == null || player.hasPermission(permission)` appears character-identically in 7 files — modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bukkit/BukkitDirectPlayerExecutor.java, modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordDirectPlayerExecutor.java, modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/limboloohp/LimboLoohpDirectPlayerExecutor.java, modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/nukkit/NukkitDirectPlayerExecutor.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/client/NettyNetworkClient.java:114— `sslConfig == null || !sslConfig.enabled()` appears character-identically in 2 files — driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/client/NettyNetworkClient.java, driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/server/NettyNetworkServer.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bukkit/BukkitPlayerManagementListener.java:62— `task.maintenance() && !event.getPlayer().hasPermission("cloudnet.bridge.maintenance")` appears character-identically in 4 files — modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bukkit/BukkitPlayerManagementListener.java, modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/nukkit/NukkitPlayerManagementListener.java, modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/velocity/VelocityPlayerManagementListener.java, modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/waterdog/WaterDogPEPlayerManagementListener.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordPlayerManagementListener.java:92— `task.maintenance() && !player.hasPermission("cloudnet.bridge.maintenance")` appears character-identically in 2 files — modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/bungeecord/BungeeCordPlayerManagementListener.java, modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/limboloohp/LimboLoohpPlayerManagementListener.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/platform/bungee/BungeeCordSyncProxyListener.java:138— `this.syncProxyManagement.onlinePlayerCount() >= loginConfiguration.maxPlayers() && !player.hasPermission("cloudnet.syncproxy.fulljoin")` appears character-identically in 2 files — modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/platform/bungee/BungeeCordSyncProxyListener.java, modules/syncproxy/impl/src/main/java/eu/cloudnetservice/modules/syncproxy/impl/platform/velocity/VelocitySyncProxyListener.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Fat interface: Database (23 abstract methods) driver/api/src/main/java/eu/cloudnetservice/driver/database/Database.java:54— `Database` declares 23 abstract methods: `clear`, `clearAsync`, `contains`, `containsAsync`, `delete`, `deleteAsync`, `documentCount`, `documentCountAsync`, `documents`, `documentsAsync`, `entries`, `entriesAsync`, `find`, `find`, `findAsync`, `findAsync`, `get`, `getAsync`, `insert`, `insertAsync`, `keys`, `keysAsync`, `synced`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 23 declarations carry 21 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 21 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: Document (33 abstract methods) driver/api/src/main/java/eu/cloudnetservice/driver/document/Document.java:91— `Document` declares 33 abstract methods: `contains`, `containsNonNull`, `elementCount`, `elements`, `empty`, `equals`, `factoryName`, `getBoolean`, `getByte`, `getDouble`, `getFloat`, `getInt`, `getLong`, `getShort`, `getString`, `immutableCopy`, `keys`, `mutableCopy`, `readDocument`, `readMutableDocument`, `readObject`, `readObject`, `readObject`, `send`, `serializeToString`, `toInstanceOf`, `toInstanceOf`, `toInstanceOf`, `toString`, `writeTo`, `writeTo`, `writeTo`, `writeTo`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 33 declarations carry 26 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 26 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: ModuleProvider (18 abstract methods) driver/api/src/main/java/eu/cloudnetservice/driver/module/ModuleProvider.java:35— `ModuleProvider` declares 18 abstract methods under just 13 distinct name(s): `loadAll`, `loadModule`, `loadModule`, `module`, `moduleDependencyLoader`, `moduleDependencyLoader`, `moduleDirectoryPath`, `moduleDirectoryPath`, `moduleProviderHandler`, `moduleProviderHandler`, `modules`, `modules`, `notifyPostModuleLifecycleChange`, `notifyPreModuleLifecycleChange`, `reloadAll`, `startAll`, `stopAll`, `unloadAll`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 18 separate responsibilities: a caller binds to 13 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 18 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
Fat interface: ModuleWrapper (16 abstract methods) driver/api/src/main/java/eu/cloudnetservice/driver/module/ModuleWrapper.java:39— `ModuleWrapper` declares 16 abstract methods: `classLoader`, `dataDirectory`, `dependingModules`, `injectionLayer`, `loadModule`, `module`, `moduleConfiguration`, `moduleLifeCycle`, `moduleProvider`, `moduleTasks`, `reloadModule`, `startModule`, `stopModule`, `unloadModule`, `uri`, `url`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: DataBuf (31 abstract methods) driver/api/src/main/java/eu/cloudnetservice/driver/network/buffer/DataBuf.java:59— `DataBuf` declares 31 abstract methods: `accessible`, `acquire`, `acquires`, `advanceReaderOffset`, `asMutable`, `close`, `forceRelease`, `readBoolean`, `readByte`, `readByteArray`, `readChar`, `readDataBuf`, `readDouble`, `readFloat`, `readInt`, `readLong`, `readNullable`, `readNullable`, `readObject`, `readObject`, `readShort`, `readString`, `readUniqueId`, `readableBytes`, `readableNioBuffer`, `readerOffset`, `readerOffset`, `redoTransaction`, `release`, `startTransaction`, `toByteArray`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 31 declarations carry 28 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 28 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: Mutable (22 abstract methods) driver/api/src/main/java/eu/cloudnetservice/driver/network/buffer/DataBuf.java:401— `Mutable` declares 22 abstract methods: `advanceWriterOffset`, `asImmutable`, `ensureWriteable`, `writeBoolean`, `writeByte`, `writeByteArray`, `writeByteArray`, `writeChar`, `writeDataBuf`, `writeDouble`, `writeFloat`, `writeInt`, `writeLong`, `writeNullable`, `writeObject`, `writeShort`, `writeString`, `writeUniqueId`, `writeableBytes`, `writeableNioBuffer`, `writerOffset`, `writerOffset`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 22 declarations carry 20 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 20 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: CloudServiceProvider (22 abstract methods) driver/api/src/main/java/eu/cloudnetservice/driver/provider/CloudServiceProvider.java:40— `CloudServiceProvider` declares 22 abstract methods: `runningServices`, `runningServicesAsync`, `service`, `serviceAsync`, `serviceByName`, `serviceByNameAsync`, `serviceCount`, `serviceCountAsync`, `serviceCountByGroup`, `serviceCountByGroupAsync`, `serviceCountByTask`, `serviceCountByTaskAsync`, `serviceProvider`, `serviceProviderByName`, `services`, `servicesAsync`, `servicesByEnvironment`, `servicesByEnvironmentAsync`, `servicesByGroup`, `servicesByGroupAsync`, `servicesByTask`, `servicesByTaskAsync`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: ClusterNodeProvider (20 abstract methods) driver/api/src/main/java/eu/cloudnetservice/driver/provider/ClusterNodeProvider.java:39— `ClusterNodeProvider` declares 20 abstract methods: `addNode`, `addNodeAsync`, `consoleCommand`, `consoleCommandAsync`, `consoleCommands`, `consoleCommandsAsync`, `consoleTabCompleteResults`, `consoleTabCompleteResultsAsync`, `node`, `nodeAsync`, `nodeInfoSnapshot`, `nodeInfoSnapshotAsync`, `nodeInfoSnapshots`, `nodeInfoSnapshotsAsync`, `nodes`, `nodesAsync`, `removeNode`, `removeNodeAsync`, `sendCommandLine`, `sendCommandLineAsync`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: SpecificCloudServiceProvider (38 abstract methods) driver/api/src/main/java/eu/cloudnetservice/driver/provider/SpecificCloudServiceProvider.java:43— `SpecificCloudServiceProvider` declares 38 abstract methods: `addServiceDeployment`, `addServiceDeploymentAsync`, `addServiceRemoteInclusion`, `addServiceRemoteInclusionAsync`, `addServiceTemplate`, `addServiceTemplateAsync`, `cachedLogMessages`, `cachedLogMessagesAsync`, `deleteFiles`, `deleteFilesAsync`, `deployResources`, `deployResourcesAsync`, `forceUpdateServiceInfo`, `forceUpdateServiceInfoAsync`, `includeWaitingServiceInclusions`, `includeWaitingServiceInclusionsAsync`, `includeWaitingServiceTemplates`, `includeWaitingServiceTemplates`, `includeWaitingServiceTemplatesAsync`, `includeWaitingServiceTemplatesAsync`, `installedDeployments`, `installedInclusions`, `installedTemplates`, `removeAndExecuteDeploymentsAsync`, `restart`, `restartAsync`, `runCommand`, `runCommandAsync`, `serviceInfo`, `serviceInfoAsync`, `toggleScreenEvents`, `toggleScreenEventsAsync`, `updateLifecycle`, `updateLifecycleAsync`, `updateProperties`, `updatePropertiesAsync`, `valid`, `validAsync`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 38 declarations carry 36 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 36 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: TemplateStorage (37 abstract methods) driver/api/src/main/java/eu/cloudnetservice/driver/template/TemplateStorage.java:45— `TemplateStorage` declares 37 abstract methods: `appendOutputStream`, `appendOutputStreamAsync`, `close`, `closeAsync`, `contains`, `containsAsync`, `create`, `createAsync`, `createDirectory`, `createDirectoryAsync`, `createFile`, `createFileAsync`, `delete`, `deleteAsync`, `deleteFile`, `deleteFileAsync`, `deploy`, `deployAsync`, `deployDirectory`, `deployDirectoryAsync`, `fileInfo`, `fileInfoAsync`, `hasFile`, `hasFileAsync`, `listFiles`, `listFilesAsync`, `newInputStream`, `newInputStreamAsync`, `newOutputStream`, `newOutputStreamAsync`, `openZipInputStreamAsync`, `pull`, `pullAsync`, `templates`, `templatesAsync`, `zipTemplate`, `zipTemplateAsync`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: NodeServer (22 abstract methods) node/api/src/main/java/eu/cloudnetservice/node/cluster/NodeServer.java:34— `NodeServer` declares 22 abstract methods: `available`, `channel`, `channel`, `close`, `connect`, `drain`, `draining`, `head`, `info`, `lastNodeInfoSnapshot`, `lastNodeInfoUpdate`, `lastStateChange`, `nodeInfoSnapshot`, `provider`, `sendCommandLine`, `serviceFactory`, `serviceProvider`, `shutdown`, `state`, `state`, `syncClusterData`, `updateNodeInfoSnapshot`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 22 declarations carry 20 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 20 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: Configuration (38 abstract methods) node/api/src/main/java/eu/cloudnetservice/node/config/Configuration.java:27— `Configuration` declares 38 abstract methods: `clientSSLConfig`, `clientSSLConfig`, `clusterConfig`, `clusterConfig`, `fileExists`, `forceInitialClusterDataSync`, `forceInitialClusterDataSync`, `hostAddress`, `hostAddress`, `identity`, `identity`, `ipAliases`, `ipAliases`, `ipWhitelist`, `ipWhitelist`, `javaCommand`, `javaCommand`, `language`, `language`, `load`, `maxCPUUsageToStartServices`, `maxCPUUsageToStartServices`, `maxMemory`, `maxMemory`, `maxServiceConsoleLogCacheSize`, `maxServiceConsoleLogCacheSize`, `printErrorStreamLinesFromServices`, `printErrorStreamLinesFromServices`, `processTerminationTimeoutSeconds`, `processTerminationTimeoutSeconds`, `properties`, `properties`, `reloadFrom`, `runBlockedServiceStartTryLaterAutomatic`, `runBlockedServiceStartTryLaterAutomatic`, `save`, `serverSSLConfig`, `serverSSLConfig`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 38 declarations carry 21 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 21 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: CloudService (17 abstract methods) node/api/src/main/java/eu/cloudnetservice/node/service/CloudService.java:33— `CloudService` declares 17 abstract methods: `alive`, `cloudServiceManager`, `connectionKey`, `directory`, `lastServiceInfoSnapshot`, `lifeCycle`, `networkChannel`, `pluginDirectory`, `publishServiceInfoSnapshot`, `runtime`, `serviceConfiguration`, `serviceConsoleLogCache`, `serviceId`, `serviceInfo`, `waitingDeployments`, `waitingIncludes`, `waitingTemplates`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: CloudServiceManager (23 abstract methods) node/api/src/main/java/eu/cloudnetservice/node/service/CloudServiceManager.java:33— `CloudServiceManager` declares 23 abstract methods: `addCloudServiceFactory`, `addCloudServiceFactory`, `addServicePreparer`, `addServicePreparer`, `cloudServiceFactories`, `cloudServiceFactory`, `currentReservedMemory`, `currentUsedHeapMemory`, `defaultJvmOptions`, `deleteAllCloudServices`, `localCloudService`, `localCloudService`, `localCloudService`, `localCloudServices`, `persistentServicesDirectory`, `removeCloudServiceFactory`, `removeServicePreparer`, `selectNodeForService`, `servicePreparer`, `servicePreparers`, `startAllCloudServices`, `stopAllCloudServices`, `tempDirectory`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 23 declarations carry 19 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 19 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: Console (32 abstract methods) node/impl/src/main/java/eu/cloudnetservice/node/impl/console/Console.java:31— `Console` declares 32 abstract methods: `addCommandHandler`, `addTabCompleteHandler`, `animationRunning`, `clearScreen`, `commandHistory`, `commandHistory`, `commandInputValue`, `disableAllCommandHandlers`, `disableAllHandlers`, `disableAllTabCompleteHandlers`, `displayLength`, `emptyPrompt`, `enableAllCommandHandlers`, `enableAllHandlers`, `enableAllTabCompleteHandlers`, `forceWriteLine`, `printingEnabled`, `prompt`, `prompt`, `readLine`, `removeCommandHandler`, `removePrompt`, `removeTabCompleteHandler`, `resetPrompt`, `runningAnimations`, `startAnimation`, `togglePrinting`, `usingMatchingHistoryComplete`, `usingMatchingHistoryComplete`, `width`, `writeLine`, `writeRaw`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 32 declarations carry 29 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 29 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: PlayerManager (30 abstract methods) modules/bridge/api/src/main/java/eu/cloudnetservice/modules/bridge/player/PlayerManager.java:58— `PlayerManager` declares 30 abstract methods: `deleteCloudOfflinePlayer`, `deleteCloudOfflinePlayerAsync`, `environmentOnlinePlayers`, `environmentOnlinePlayersAsync`, `firstOfflinePlayer`, `firstOfflinePlayerAsync`, `firstOnlinePlayer`, `firstOnlinePlayerAsync`, `globalPlayerExecutor`, `groupOnlinePlayers`, `offlinePlayer`, `offlinePlayerAsync`, `offlinePlayers`, `offlinePlayersAsync`, `onlineCount`, `onlineCountAsync`, `onlinePlayer`, `onlinePlayerAsync`, `onlinePlayers`, `onlinePlayers`, `onlinePlayersAsync`, `playerExecutor`, `registeredCount`, `registeredCountAsync`, `registeredPlayers`, `taskOnlinePlayers`, `updateOfflinePlayer`, `updateOfflinePlayerAsync`, `updateOnlinePlayer`, `updateOnlinePlayerAsync`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 30 declarations carry 29 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 29 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: PlatformSelectorEntity<L, P, M, I, S> (18 abstract methods) modules/npcs/api/src/main/java/eu/cloudnetservice/modules/npc/platform/PlatformSelectorEntity.java:25— `PlatformSelectorEntity<L, P, M, I, S>` declares 18 abstract methods: `canSpawn`, `entityId`, `executeAction`, `handleInventoryInteract`, `handleLeftClickAction`, `handleRightClickAction`, `infoLineEntityIds`, `location`, `npc`, `registerScoreboardTeam`, `remove`, `scoreboardRepresentation`, `selectorInventory`, `spawn`, `spawned`, `stopTrackingService`, `trackService`, `update`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Orphaned file modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/limboloohp/LimboLoohpBridgeManagement.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/limboloohp/LimboLoohpPlayerManagementListener.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/limboloohp/LimboLoohpDirectPlayerExecutor.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/bukkit/FAWEReflectionUtilsTransformer.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/limboloohp/LimboLoohpBridgePlugin.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/bukkit/FAWEWorldEditDownloadURLTransformer.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/limboloohp/LimboLoohpPluginInfoGenerator.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×5
Projects may be oversized for their cohesion node/impl/build.gradle.kts:1— `node/impl` (21234 LoC, 160 module-visible types across 55 directories) overshoots its size bounds. 5 of 51 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 8.1/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Projects may be oversized for their cohesion driver/api/build.gradle.kts:1— `driver/api` (21818 LoC, 207 module-visible types across 39 directories) overshoots its size bounds. 5 of 51 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 8.1/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Projects may be oversized for their cohesion driver/impl/build.gradle.kts:1— `driver/impl` (18632 LoC, 93 module-visible types across 34 directories) overshoots its size bounds. 5 of 51 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 8.1/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Projects may be oversized for their cohesion modules/bridge/impl/build.gradle.kts:1— `modules/bridge/impl` (7812 LoC, 49 module-visible types across 24 directories) overshoots its size bounds. 5 of 51 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 8.1/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Projects may be oversized for their cohesion wrapper-jvm/impl/build.gradle.kts:1— `wrapper-jvm/impl` (6116 LoC, 37 module-visible types across 16 directories) overshoots its size bounds. 5 of 51 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 8.1/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 4 significant file(s) lose their only recent owner: wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/unsafe/UnsafeReplacementDelegate.java, wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/asm/AsmClassReaderTransformer.java, ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/infogen/NightConfigInfoGenerator.java, build-extensions/src/main/kotlin/eu/cloudnetservice/cloudnet/gradle/plugins/CloudNetModulesPlugin.kt. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 4 significant file(s) lose their only recent owner: modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/PlatformBridgeManagement.java, modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/bukkit/BukkitPlatformNPCManagement.java, modules/npcs/impl/src/main/java/eu/cloudnetservice/modules/npc/impl/platform/bukkit/util/BukkitPacketAdapterUtil.java, wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/bukkit/PaperclipClassLoaderTransformer.java. Pair on, review, or document these before any departure.
No ADRs found wrapper-jvm/impl/build.gradle.kts:97— 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 `wrapper-jvm/impl/build.gradle.kts` makes this repository a deployable product (line 97).
D27 · Navigability· High interface indirection · ×1
High interface indirection — 55 % of calls go through an interface — tracing a call means resolving the implementation each hop. Prefer concrete types where there's a single implementation.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
REDACTED
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 7 of 648 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 648 of the 1130 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/limboloohp/LimboLoohpBridgeManagement.java, modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/limboloohp/LimboLoohpPlayerManagementListener.java, modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/limboloohp/LimboLoohpDirectPlayerExecutor.java, wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/bukkit/FAWEReflectionUtilsTransformer.java, modules/bridge/impl/src/main/java/eu/cloudnetservice/modules/bridge/impl/platform/limboloohp/LimboLoohpBridgePlugin.java, wrapper-jvm/impl/src/main/java/eu/cloudnetservice/wrapper/impl/transform/bukkit/FAWEWorldEditDownloadURLTransformer.java, ext/platform-inject-support/processor/src/main/java/eu/cloudnetservice/ext/platforminject/processor/platform/limboloohp/LimboLoohpPluginInfoGenerator.java. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
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.
Logging is not universal — Only 18/20 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `launcher/java8`, `launcher/patcher`.
No SAST REDACTED:7— No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 5 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
X5 · Nullable reference types· Java packages are not null-marked everywhere · ×1
Java packages are not null-marked everywhere — 0/347 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
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.
none (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 Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).
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 35 file(s) — `driver/api/src/main/java/eu/cloudnetservice/driver/event/EventManager.java`, `driver/api/src/main/java/eu/cloudnetservice/driver/network/chunk/ChunkedPacketSender.java`, `driver/impl/src/main/java/eu/cloudnetservice/driver/impl/event/DefaultEventManager.java`, `driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/chunk/builder/DefaultChunkedPacketSenderBuilder.java`, `driver/impl/src/main/java/eu/cloudnetservice/driver/impl/network/netty/buffer/NettyMutableDataBuf.java`, … (+30 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
none (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 Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).
0
—
Run 01a1e558-e8e4-7b89-aa9d-5e31b5bd0663 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 30 · Warnings: 370 · Recommendations: 62 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 16-11-2026 @ 17:12 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.