Class ScannedMod

  • All Implemented Interfaces:

    
    public final class ScannedMod
    
                        

    What one scanner made of one mod jar: which side it belongs on, and what it declared it needs.

    A scanner returns one of these per jar it was handed, whatever the outcome — a jar it could not open, or one carrying no descriptor it understands, comes back with the defaults rather than being dropped. The include-list is built solely from what the scanners return, so an omission here is a mod missing from the finished server pack.

    There is deliberately no equals/hashCode. Scanning a directory with two scanners yields two instances for one jar which may disagree on sideness, and value-equality would let a Set or distinct() keep whichever landed first and silently drop the other verdict. Merging those verdicts is a decision the caller makes explicitly; compare on file when identifying the same jar across two scans.