How neversinkdev/neversink-filter-for-poe2 works
Main Components to Highlight
• Filter Engine/Script Files: At the core are the .filter files (e.g., “NeverSink’s filter 2 – 0-SOFT.filter” up to “UBER-PLUS-STRICT”) which define the various strictness levels.
• Asset/Resource Directories: There are two main style directories – “CUSTOMSOUNDS” and “DARKMODE”. Each holds assets (custom sounds or style-specific filter files) that provide alternative aesthetics and behavior.
• Additional Files & Deprecated Archives: The “ADDITIONAL-FILES” directory (with Deprecated files) and other support documents (CHANGELOG, LICENSE) show versioning/maintenance but are less central to the runtime behavior.
• CI/CD & Release Automation: The .github directory, along with configuration files like “autorelease.yml” and “release-drafter.yml”, indicate automated release management to ensure updated filters are published each league.
• Companion Website Integration: Though not part of the core repository code, the README calls attention to the FilterBlade website (filterblade.xyz) which allows users to modify, preview, and customize the filters. This external service is an accessory but important for how end users interact with the overall solution.
Relationships & Data/Dependency Flow
• The “Filter Scripts” are the primary deliverable that will be deployed into the Path of Exile 2 game client.
Architectural Patterns and Design Principles
• Separation of Concerns: Different directories and files are clearly separated by their functions (assets versus filter scripts versus release configurations).
• Modularity: With 7 distinct strictness levels and distinct style options (Custom vs. Dark Mode), the design encapsulates each variant in its own subdirectory or file module.
• Automation: The presence of GitHub workflows indicates a modern, automated release and update cycle, which should be highlighted.