PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteA PVS-Studio article published September 29, 2026, describes six findings in Create at revision 87b3c6a, including a schematic-coordinate input defect, a warning-message null dereference, and a mechanical-crafter loop whose attempted fix did not hold in a longer setup. The author, PVS-Studio developer Kirill Epifanov, reports checking selected cases in Minecraft; these are his results, not an independent audit of current Create releases. Read the PVS-Studio article.
What the findings do—and do not—say about Create
They show that the analyzed revision contained several code-level problems, but they do not establish that every current Create release has these issues. The article examines one revision, 87b3c6a, and selects six findings the author considered interesting. As Epifanov puts it, “The article includes only the bugs that the author found interesting (yes, it’s a matter of personal taste).” It is therefore a report of selected findings, not a complete defect inventory.
As an Amazon Associate I earn from qualifying purchases.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →The article gives the mod’s CurseForge total as more than 206 million downloads at its September 2026 publication, excluding Modrinth. That is a dated figure, not a current download count.
Six reported findings, with their practical scope
| Finding | What the article reports | Practical status |
|---|---|---|
| Schematic coordinate paste | Spaces remain in pasted coordinates because the result of Java’s string replacement is discarded. | User-visible input issue; author reports checking it in-game. |
| Schedule condition width | A calculated maximum width is not assigned back, but the width had already been calculated sufficiently in the tested cases. | Ineffective calculation, not a demonstrated visible gameplay fault. |
| Mechanical crafter chain | A null check cannot handle an empty list; an attempted change stopped one loop but failed with a longer chain. | Behavior and complete fix unresolved in the article. |
| Train relocation warning | A null-train condition is followed by warning code that accesses the missing train’s ID. | Malformed or client-supplied request can trigger a logged exception; article says the packet is caught and left unhandled, not that the server crashes. |
| Mixer and contraption loading | A later Optional emptiness test is unreachable after a presence check; unknown contraption type data can result in a null dereference. | The mixer check is described as non-impacting in that path; malformed contraption data is reported to produce an exception. |
| Interrupted thread handling | A caught interruption is printed without restoring the thread’s interrupt status. | Applies to a debug command limited to operators in debug builds. |
1. Pasting coordinates into the schematic menu
In SchematicEditScreen, the code calls coords.replaceAll(" ", "") but does not store its returned string. Java strings are immutable, so this call does not remove spaces from the original coords value. The article says -156, 67, 204 fails, while -156,67,204 works. The suggested code-level correction is to assign the replacement result back to coords. This is the clearest ordinary-use, user-facing finding in the report.
#1 Best Overall
2. Schedule condition width
In ScheduleScreen, the result of Math.max(maxWidth, renderInput(...)) is discarded. That makes the calculation ineffective. However, Epifanov says that in the cases he tested, getConditionColumnWidth() had already computed enough width and returned the same value. He recommends removing the unnecessary wrapper; the article does not demonstrate a visible gameplay problem from it.
3. Mechanical crafters that pass items in a loop
The reported code path has getPrecedingCrafters return a list, including an empty list, rather than null. That means a null check in continueIfAllPrecedingFinished cannot catch the empty-list case. The author reports seeing items move indefinitely between crafters in a loop before trying a change.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Replacing the null test with isEmpty() stopped the loop in the first setup. But when the author added two more crafters, that change no longer worked. The article leaves open whether loop detection needs another fix or whether the behavior is intentional. It does not establish isEmpty() as a complete solution.
4. Train relocation warning with a nonexistent train
The handler checks whether train == null, but the warning message then reads train.id. According to the article, a client can send a relocation request with a nonexistent train ID and trigger an exception while the warning is being constructed. The packet registration catches and logs exceptions, so the report describes the packet as unhandled—not a server crash or a demonstrated compromise.
5. Mixer Optional check and malformed contraption data
In MechanicalMixerBlockEntity, the article identifies an emptiness check on an Optional after the code has already checked that the value is present. That later branch cannot be reached. Epifanov says other checks mean this does not affect gameplay in the described path, but calls the dead safeguard risky if the code is refactored later.
A separate loading issue is in Contraption.fromNBT: an unknown type can cause ContraptionType.fromType to return null, which the caller then dereferences. The author reports reproducing this with a malformed minecart command, seeing a NullPointerException stack trace, and having the minecart replaced by a vanilla minecart. This is a reported malformed-data case, not evidence that routine contraption loading fails.
Rank #4
6. Interrupted thread status in a debug helper
ServerLagger catches InterruptedException and only prints it. Because Thread.sleep clears the interrupt flag when it throws that exception, the interruption request is discarded unless the code restores it. The article’s suggested correction is Thread.currentThread().interrupt(). Its scope is limited: the helper belongs to a debug command and, according to the article, is available only to operators in debug builds.
Were the proposed fixes merged?
The PVS-Studio article says pull requests were submitted and links to #10696 and #10721. Their current merge status and whether any change shipped could not be established from the available source. Do not treat the suggested corrections or pull requests as proof that current Create releases contain fixes.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
