Skip to content
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

Jump to bottom

incorrect MAX cr 0 filtering #189

Open
BiscuitCookies opened this issue Mar 25, 2020 · 2 comments
Open

incorrect MAX cr 0 filtering #189

BiscuitCookies opened this issue Mar 25, 2020 · 2 comments
Labels
bug

Comments

@BiscuitCookies
Copy link

The copper dragon wyrmling says the stat block is on page 111 while it is on 112 (at least in my book)

When trying to set the max CR to CR 0 it will display all CR levels no matter whether min CR is set to Min CR or CR 0
@Asmor
Copy link
Owner

Asmor commented Mar 25, 2020

Thanks, fixed the copper dragon. Leaving this open to track the CR 0 bug. In the future, please submit separate issues for each problem or suggestion.

@Asmor Asmor added the bug label Mar 25, 2020
@Asmor Asmor changed the title Wrong copper dragon wyrmling page number and incorrect MAX cr 0 filtering incorrect MAX cr 0 filtering Mar 25, 2020
@BiscuitCookies
Copy link
Author

Yeah, sorry should have know better.

@Villawhatever Villawhatever mentioned this issue Apr 16, 2021
Closed
@Villawhatever Villawhatever mentioned this issue Aug 23, 2021
Merged
V13Axel pushed a commit to fantasycalendar/scaled-encounters that referenced this issue Aug 23, 2021
@Villawhatever
Fix maxCR == 0 not actually filtering. Closes Asmor#189. (#1)
2f97729
mfzha pushed a commit to mfzha/scaled-encounters that referenced this issue Aug 23, 2021
@Villawhatever @mfzha
Fix maxCR == 0 not actually filtering. Closes Asmor#189. (fantasycale…
1dcd428 
…ndar#1)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix maxCR == 0 not actually filtering.
2 participants
@Asmor @BiscuitCookies