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.

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

Allow more glitch levels (or maybe floats for levels?) #7

Closed
KopfKrieg opened this issue Feb 22, 2020 · 3 comments
Closed

Allow more glitch levels (or maybe floats for levels?) #7

KopfKrieg opened this issue Feb 22, 2020 · 3 comments

Comments

@KopfKrieg
Copy link
Contributor

@KopfKrieg KopfKrieg commented Feb 22, 2020

Just a suggestion for an enhancement: Currently there are only glitch levels between 1 and 10 allowed, but I miss a setting somewhere between 1 and 2. This could be solved by either allowing floats for glitch levels (not sure if the algorithm used can work with floats), or by doubling the number of levels by using a range from 1 to 20 instead of 1 to 10.

@TotallyNotChase
Copy link
Owner

@TotallyNotChase TotallyNotChase commented Mar 21, 2020

@KopfKrieg Just added this in 0.1.3! You can now use floats between 1.0 and 10.0 as glitch_amount! Single or double digit precision works best with this. Check out the docs for more info!

Increment/Decrement (aka glitch_change) will also receive support for floats shortly. Should be done by tomorrow, stay tuned :)

P.S - Sorry for taking so long, I had exams and had to postpone development

@TotallyNotChase
Copy link
Owner

@TotallyNotChase TotallyNotChase commented Mar 22, 2020

Alright, glitch_amount can now be in range 0.1 to 10.0 and increment/decrement (aka glitch_change) also supports floats! Check out 0.1.4!

@KopfKrieg
Copy link
Contributor Author

@KopfKrieg KopfKrieg commented Mar 23, 2020

Cool, thank you :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.