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

Add 4* Special Rate to Sim #2

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Conversation

DTM9025
Copy link
Contributor

@DTM9025 DTM9025 commented Feb 25, 2024

This is the first iteration of taking into account the effect
4* Special Rates have on summoning. Right now this assumes the
rate always starts at 3% (which has always been the case so far)
and the pools for 3* and 4* units are the same (which is currently
the case).

This doesn't include 4* Special Hero Special Rates, which would
add another 3* rate to the table. Given that this particular rate
is very rare as opposed to the normal 4* Special Rate (only appears
on old seasonal reruns) and would need some mechanism to turn
it on, I forwent that for now.

This is the first iteration of taking into account the effect
4* Special Rates have on summoning. Right now this assumes the
rate always starts at 3% (which has always been the case so far)
and the pools for 3* and 4* units are the same (which is currently
the case).

This doesn't include 4* Special Hero Special Rates, which would
add another 3* rate to the table. Given that this particular rate
is very rare as opposed to the normal 4* Special Rate, that will
be for later.
In adding the new 4* Special Rate pool, I made an error in getting
the pity rate adjustments, mistakenly dividing the proportion by
a further 100 which messed it up and made the 4* Special Rate seem
to have an outsize impact on the sims despite that shouldn't being
the case. This fixes this error.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant