HVBattle
HVBattle provides reusable HentaiVerse battle-domain APIs. It builds on
hvbrowser for the authenticated Hentaiverse browser session and keeps the
private command-line runner in a separate application workspace.
The package exposes a policy-neutral BattleSession, atomic battle actions,
and a BattleRunner that runs exactly one already-active battle using a
client-supplied BattleStrategy. It never repairs equipment, recovers stamina,
or starts Arena/GrindFest on its own. Campaign policy and post-battle work belong
to the calling application.
BattleSession is a facade, not an HVDriver subclass. It composes an explicit
browser_client, a battle-scoped state store, a battle launcher, and shared
action/item/skill/buff collaborators. Callers that also need non-battle
hvbrowser operations use session.browser_client explicitly; this prevents
maintenance APIs from leaking into the battle-domain surface. The legacy
battle_dashboard name remains a compatibility alias for the state store.
Version 0.2.7 restores the game's final completion acknowledgement as a
runner-owned safety step. BattleRunner captures the immutable completion and
round summary before clicking the exact finishbattle.png control at most
once, revalidating that the selected control still belongs to the observed
completion document first. It returns BattleCompleted only after a new,
ready document on the same realm has no battle, finish, next-floor, or
PonyChart controls. A click or navigation error is reconciled through read-only
state probes and is never resent; missing positive exit evidence raises
BattleInterruptedError.
Turn preparation uses BattleTurnState and BattleTurnPhase to distinguish an
active turn, next-floor transition, PonyChart challenge, positive completion,
and an absent battle page. BattleRunner consumes this typed state directly;
the former sentinel-returning prepare_turn() remains only as a compatibility
adapter.
Next-floor transition DOM is never accepted over a retained duplicate XHR receipt: a matching monitor must be either unsent with count zero or sent once with count one, even when the next round is already visible. If transition evidence remains unknown, recovery evidence freezes its XHR fields from that same retained monitor, so a duplicate cannot be hidden behind an unrelated count-one record.
An ambiguous turn or next-floor action is eligible for same-browser recovery
only when immutable evidence binds the server-communication-failed dialog to
that exact action token and the XHR is either the precise terminal status-zero
error shape or has an incomplete zero/one-send receipt with null status and
outcome. Recovery never replays the cached action. It accepts only a new, ready
document on the expected persistent/Isekai realm after at least two stable
state signatures. Complete and next-floor controls take priority over
PonyChart; an active phase additionally needs its log/action-control markers
and must parse with a live monster. The runner then returns to turn preparation
and asks strategy for a fresh decision. A second ambiguity before a confirmed
ACTED or next-floor receipt exhausts that browser's recovery budget. Only
this typed exhaustion may open one fresh authenticated browser, whose own
same-browser budget starts unused; it can never open a third browser.
Final-completion acknowledgement ambiguity never enters that fresh-browser
path.
A ZendriverOperationTimeout is not treated like an ordinary retryable
TimeoutError, because its CDP command deliberately remains live. A live
timeout while arming or cleaning an action monitor, or while parsing session
state, interrupts and closes the current browser without retry. After a click,
it leaves the post-click document unobservable, so that unknown action is not
eligible for first-use recovery. If it occurs inside recovery after incident
evidence was already established, the failed old-browser reconciliation is
typed exhaustion and may use only the one fresh-browser stage described above.
BattleSession preloads the PonyChart classifier and ONNX model before opening
the browser, so a timed challenge never pays the first-load cost. The runner
checks for and resolves PonyChart before parsing an ordinary battle turn or
calling client strategy code. Classifier screenshots are temporary and removed
after every attempt. Failure artifacts are retained only when
ponychart_diagnostic_directory is explicitly configured, and that directory
is bounded by ponychart_diagnostic_file_limit.
import asyncio
from hvbattle import BattleCompleted, BattleRunner, BattleSession, TurnDecision
class MyStrategy:
async def take_turn(self, session: BattleSession, /) -> TurnDecision:
if await session.go_next_floor():
return TurnDecision.ACTED
if not session.alive_monster_ids:
return TurnDecision.IDLE
if await session.attack_monster(session.alive_monster_ids[0]):
return TurnDecision.ACTED
return TurnDecision.IDLE
async def after_battle(session: BattleSession, completed: BattleCompleted) -> None:
print(completed)
async def main() -> None:
async with BattleSession(headless=True) as session:
result = await BattleRunner(session, MyStrategy()).run_current()
if isinstance(result, BattleCompleted):
await after_battle(session, result)
asyncio.run(main())
The example requires credentials through the normal EH_USERNAME and
EH_PASSWORD indirection and an already-active server battle; otherwise
run_current() returns None. TurnDecision.STOP deliberately returns a
BattleStopped result. Leaving the battle page without positive final-round
completion evidence raises BattleInterruptedError, so callers cannot mistake
an expired login or unexpected navigation for a completed battle.
BattleDriver is only a transitional name alias for BattleSession, not an
API-compatible implementation of the old driver. Migrate constructor strategy
settings into a BattleStrategy, replace driver.battle() with
BattleRunner(driver, strategy).run_current(), and perform maintenance,
post-battle tasks, and next-battle selection after the returned
BattleCompleted. Arena choice follows the same boundary:
list_arena_options() returns data and start_arena(option) starts only the
option explicitly selected by the caller.
GrindFest uses the equivalent list_grindfest_options() and
start_grindfest(option) pair; the package does not silently choose the first
or last server option.
BaseControlPanel, ControlPanel, and NullControlPanel provide reusable
pause, named-action, named-toggle, and validated integer mechanisms. The
set_actions() API is the generic spelling; the older set_skills() spelling
remains available as a compatibility alias. Integer edits become live only
after Apply or Enter, so partially typed mutation amounts are never published.
Closing the interactive window sets the pause flag before the GUI exits.
The package does not register campaign choices or choose their defaults: a
calling application owns the control names, labels, initial values, and the
policy that reads their committed state. Importing hvbattle does not import
Tk or start a GUI process.
Development
The dependency-free Lean model in formal/ covers the safety-critical action
and transition evidence predicates, the guarded same-browser recovery budget
and no-replay boundary, the final-completion acknowledgement click bound,
error-record ordering, and supervisor no-retry exit policy. Run it separately
from the Python checks:
(cd formal && lake build)
This is a proved model of the observable decision boundary, not an automatic translation of the Python, browser, network, or log-sink implementations. The offline Python and shell tests cover those implementation boundaries.
Build a clean environment backed by PyPI releases:
bash scripts/rebuild-env.sh
For coordinated local development before all dependent releases are on PyPI, overlay editable checkouts in dependency order:
uv pip install --python .venv/bin/python --reinstall --no-deps --editable \
/Users/kuanlun_wang/Desktop/git-repo/hbrowser.clone
uv pip install --python .venv/bin/python --reinstall --no-deps --editable \
/Users/kuanlun_wang/Desktop/git-repo/hvbrowser.clone
Commands that must preserve these editable overlays use uv run --no-sync.
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file hvbattle-0.3.4.tar.gz.
File metadata
- Download URL: hvbattle-0.3.4.tar.gz
- Upload date:
- Size: 80.5 kB
- Tags: Source
- Uploaded using Trusted Publishing? Yes
- Uploaded via:
twine/7.0.0 CPython/3.13.14
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
7800c21a2a0002d475466263e30a178409b0b28e6fb82a942e83441627cdf930
|
|
| MD5 |
0b87a5f30c41f88f2f4be60d10cb8d5d
|
|
| BLAKE2b-256 |
301a8b4e0f87f2cabc575cac502470aafea81416bbf8dd97cd0a9a474e16971d
|
Provenance
The following attestation bundles were made for hvbattle-0.3.4.tar.gz:
Publisher:
publish.yml on Kuan-Lun/hvbattle
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
hvbattle-0.3.4.tar.gz -
Subject digest:
7800c21a2a0002d475466263e30a178409b0b28e6fb82a942e83441627cdf930 - Sigstore transparency entry: 2359455165
- Sigstore integration time:
-
Permalink:
Kuan-Lun/hvbattle@ba46735c46cc1798843110d1515a462e9451523e -
Branch / Tag:
refs/heads/main - Owner: https://github.com/Kuan-Lun
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
publish.yml@ba46735c46cc1798843110d1515a462e9451523e -
Trigger Event:
push
-
Statement type:
File details
Details for the file hvbattle-0.3.4-py3-none-any.whl.
File metadata
- Download URL: hvbattle-0.3.4-py3-none-any.whl
- Upload date:
- Size: 59.7 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? Yes
- Uploaded via:
twine/7.0.0 CPython/3.13.14
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
60693f435984b4afe2f22924e405e439219cdfebf0c8528eedade4f71aedfd5e
|
|
| MD5 |
8ca86273e2cf92d18cc44bd5d3f273cb
|
|
| BLAKE2b-256 |
99a18c0a5a95a4c16feae98853e38b3ab4f3dce7324503c215df249ff865da0d
|
Provenance
The following attestation bundles were made for hvbattle-0.3.4-py3-none-any.whl:
Publisher:
publish.yml on Kuan-Lun/hvbattle
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
hvbattle-0.3.4-py3-none-any.whl -
Subject digest:
60693f435984b4afe2f22924e405e439219cdfebf0c8528eedade4f71aedfd5e - Sigstore transparency entry: 2359455397
- Sigstore integration time:
-
Permalink:
Kuan-Lun/hvbattle@ba46735c46cc1798843110d1515a462e9451523e -
Branch / Tag:
refs/heads/main - Owner: https://github.com/Kuan-Lun
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
publish.yml@ba46735c46cc1798843110d1515a462e9451523e -
Trigger Event:
push
-
Statement type: