Skip to content

fix: allow up to 1000 for timed percent to see if that work in ORP mode #96

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
cryptk merged 1 commit into from
Nov 20, 2025
Merged

fix: allow up to 1000 for timed percent to see if that work in ORP mode #96

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pyomnilogic_local/cli/debug/commands.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -243,7 +243,7 @@ def set_chlor_params(ctx: click.Context, bow_id: int, equip_id: int, timed_perce
omni: OmniLogicAPI = ctx.obj["OMNI"]

# Validate timed_percent
if not 0 <= timed_percent <= 100:
if not 0 <= timed_percent <= 1000: # Temporarily allow up to 1000 to test ORP behavior
click.echo(f"Error: timed_percent must be between 0-100, got {timed_percent}", err=True)
raise click.Abort

Expand Down