E7 Hub

E7 Hub is a free, unofficial Windows desktop companion for Epic Seven. It combines owned-gear optimization, gear analysis, ADB enhancement automation, and local capability checks in one compact application.

Everything runs locally. Normal users launch the installed E7 Hub shortcut— there is no PowerShell window, system Python installation, Node.js setup, or cloud account.

Download the latest release

E7 Hub is currently an unsigned fan-made application. Windows may show an unknown-publisher warning. Install it only when you obtained it from this repository and your own Windows or organization policy permits unsigned applications.

What it includes

Workspace	Purpose
Importer	Imports a Fribbels gear.txt into E7 Hub's local owned-inventory database.
Optimizer	Searches six-piece builds on CPU or optional NVIDIA CUDA, then filters, sorts, exports, and displays exact gear cards.
Analyzer	Scores one gear piece from compact manual input or an ADB screenshot.
Enhancer	Runs bounded ADB-only enhancement automation with a safe stop and explicit destructive confirmation.
Health Center	Checks the packaged backend and isolated ADB, OCR, Ollama, and GPU capabilities.
Settings	Configures appearance, ADB, screenshot regions, click points, and timing without editing files.

E7 Hub is useful even when an optional tool is unavailable. CPU optimization and manual Analyzer entry do not depend on ADB, Ollama, Tesseract, or CUDA.

Requirements

• Windows 10 or Windows 11 on x64 hardware.
• A Fribbels gear.txt for owned-inventory optimization.
• Android Platform Tools/ADB only for screenshots, previews, and automation.
• A compatible NVIDIA GPU and driver only for optional CUDA acceleration.

The installer contains the Electron interface, packaged Python backend, offline game-data snapshot, character artwork, and required application runtime. Optional CUDA components are a separate, user-approved download that can exceed 1 GB and occupy several GB.

Install and first launch

1. Open the latest GitHub Release.
2. Download the versioned file whose name ends in Setup.exe. Do not use the automatically generated Source code archives; they are not installers.
3. Double-click the installer.
4. If Windows shows Windows protected your PC, choose More info, verify that the application is E7 Hub, and choose Run anyway only if your policy allows it. E7 Hub does not bypass Smart App Control or organization policy.
5. Open E7 Hub from its desktop or Start menu shortcut.
6. Open Health Center. The packaged backend should report ready; optional capabilities are shown independently with their setup or repair actions.

Administrator access is not normally required. Reinstalling or updating the application preserves app-owned data under %APPDATA%\E7 Hub.

For the full unsigned-installer, optional-component, uninstall, and reinstall details, see Installing E7 Hub.

Import and optimize owned gear

1. Import Fribbels gear

Open Importer, choose Select gear.txt, and select the file exported by Fribbels. A common location is:

Documents\FribbelsOptimizerSaves\gear.txt

E7 Hub reads a file only after you select it. The normalized inventory stays local; reports do not expose or retain the source path or raw file. Re-import merges stable gear identities and preserves E7 Hub-owned metadata.

Erase all optimizer data is intentionally separate and requires an explicit confirmation. It removes imported gear, saved hero profiles, and optimizer results.

2. Configure the hero and build

Open Optimizer and:

1. Select a character. The app then displays its bundled pose and exact base profile choices.
2. Use Add bonus stats for artifacts, imprints, exclusive equipment, custom modifiers, and independent S1/S2/S3 damage contexts.
3. Enter any inclusive minimum and maximum primary-stat bounds. Blank means unrestricted; 0 remains a real boundary.
4. Set each primary-stat priority from -1 through 3. The displayed Prio follows Fribbels-style independently rounded item scoring.
5. Choose up to three set requirements. None (any set) leaves that capacity unrestricted, so sets may be completely optional, 4+2, or 2+2+2.
6. Choose whether gear equipped by other heroes is eligible with Include equipped.
7. Optionally enable Use reforged stats. The optimizer otherwise uses imported current values and always considers only +15 gear.
8. Open Secondary stat filters only when you need right-side main-stat or derived-metric restrictions.

3. Search and inspect results

Choose Start search. Automatic execution uses the app-owned CUDA component only after its readiness probe succeeds; otherwise it uses the deterministic CPU path. A failed CUDA run can be restarted from permutation zero on CPU.

The exact-result ceiling is 5,000,000 builds. If build 5,000,001 matches, E7 Hub stops without presenting a partial run and asks for stricter requirements. Narrow with primary or derived metrics, requested sets, right-side main stats, or equipped-gear eligibility.

The result table keeps every primary and derived metric compact and sortable. CR deliberately remains uncapped above 100 so wasted Critical Hit Chance is visible, while damage formulas use the effective gameplay cap. Select any row to open six owned-gear cards. Completed set icons, current equipped-owner portraits, main/substats, Gear Score, and lock/equipped state remain visible.

Equip updates ownership only inside E7 Hub and leaves the build cards open as an in-game checklist. It never taps or changes Epic Seven. Selecting another hero or starting a new search clears the previous results. CSV/JSON export writes the complete active filtered and sorted view through the Windows Save dialog.

The complete field-by-field workflow is in the user guide, and every derived formula is in the metric reference.

Analyze gear

Analyzer keeps one piece's identity and four substats beside Gear Score and archetype results. Enter the piece manually, or use Auto-detect gear after ADB is ready. Calculation details and bounded OCR/debug evidence are available without turning the page into a wall of text.

Manual evaluation remains available when ADB, OCR, or Ollama is not ready.

Enhance through ADB

Every E7 Hub game screenshot and tap uses the configured ADB device. The app does not capture or click a visible Windows emulator window.

Enhancer places run limits and destructive permission beside live progress, the latest decision, and a bounded evidence log. The stop boundary is checked before every action. Allow destroy clicks is off by default and must be confirmed for each run.

Configure the ADB executable and optional device serial in Settings, then confirm ADB automation in Health Center. Never continue an automation run when the configured preview or coordinates are wrong.

Optional local tools

Capability	What it enables	If unavailable
ADB	Analyzer capture, Settings previews, Enhancer screenshots and taps	Manual Analyzer and optimization remain available.
Tesseract	Local OCR during automatic analysis	Manual gear entry remains available.
Ollama	Optional local interpretation support	Unrelated workflows remain available.
CUDA component	High-throughput NVIDIA optimizer search	Deterministic CPU optimization remains available.

Health Center installs or opens only the narrowly relevant setup path. E7 Hub does not silently install a display driver, system CUDA Toolkit, or nvcc.

Consent-first updates

Installed releases perform a small public GitHub metadata check after startup and at a bounded interval. A check does not invoke Squirrel or download the large package.

When a newer stable release exists:

1. E7 Hub shows its version, concise notes, and expected package size.
2. Nothing downloads until you choose Download update.
3. After download, choose Restart and install or Install on close.
4. An immediate restart requires another confirmation if an optimizer search, export, Analyzer scan, enhancement job, health operation, or unsaved edit would be interrupted.

Later dismisses only that release. Manual checking and release notes remain available in Settings. Offline or GitHub errors never disable the app.

Local data and privacy

Settings, imported inventory, hero profiles, results, optional GPU components, and kernel cache stay under %APPDATA%\E7 Hub. E7 Hub does not require a cloud account. GitHub is contacted only for public update metadata and an accepted release download; optional tool installers use their documented sources only after a user action.

Uninstall removes the application and shortcuts but preserves app-owned data for reinstall. Do not delete the entire data directory as routine troubleshooting. Follow the data recovery guide before restoring settings, the inventory database, profiles, results, or CUDA data.

Troubleshooting

Problem	First action
Windows blocks the installer	Confirm it came from the official release. Respect Smart App Control or organization policy; E7 Hub does not bypass it.
Backend unavailable	Restart E7 Hub, then inspect Health Center. Do not launch retired Python/Tk or PowerShell entry points.
ADB unavailable	Configure adb and the correct serial in Settings, authorize the device, then refresh Health Center.
Import rejected	Select Fribbels gear.txt, review row-level issues, and avoid unrelated export formats.
More than 5,000,000 matches	Tighten stats, metrics, sets, eligible mains, or equipped-gear scope and run again.
CUDA limited or failed	Keep using CPU, update/check the NVIDIA driver outside E7 Hub, then use Repair GPU components.
Update check failed	Continue using the app and retry from Settings later; the installed version is unchanged.
Reinstall appears empty or damaged	Stop E7 Hub and follow the validated recovery procedure.

Development

The public source uses Electron Forge + React + TypeScript for the desktop shell and a packaged Python backend for OCR, ADB, persistence, and optimization. The renderer is sandboxed, has no Node integration, and communicates through a strict typed preload bridge.

Start with:

• Desktop development and packaging
• CUDA runtime contract
• Result lifecycle
• Current continuation context

Core semantic roots are assets, desktop, src, tests, scripts, and docs. Generated builds, caches, local databases, debug images, private planning notes, benchmark evidence, and release artifacts are ignored rather than committed.

Before contributing, run the pinned Python suite, desktop tests/type-check, and documentation validator described in the development guide. Stable releases are built only from a matching vMAJOR.MINOR.PATCH tag after the complete Windows audit and smoke pipeline passes.

Unofficial project and attribution

E7 Hub is not affiliated with, endorsed by, or sponsored by Smilegate, Super Creative, or the Epic Seven rights holders. Epic Seven names, characters, statistics, and artwork remain the property of their respective rights holders.

The offline data snapshot and Fribbels-compatible behavior are pinned and documented. Character artwork, equipment icons, set icons, application art, runtime notices, hashes, and exact source revisions are recorded in Attribution, data provenance, and project status.

The E7 Hub package currently declares UNLICENSED; a public repository does not by itself grant reuse or redistribution rights. Third-party components retain their own licenses and notices.