-
Notifications
You must be signed in to change notification settings - Fork 49
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
Need to store (un)enchanted states? #5
Comments
But, when we need to re-calculate the enchanted states WHAT'S IMPORTANT IS... That is, we have no idea what enchantments yield the current states.
Even, we can deal with silence, as long as we load the base states from the database. So, we might need to store un-enchanted states in entity. BTW, this comes with a price.
|
Yes, we should store unenchanted states. So we can do enchantment re-calculation for aura-update phase. |
For the base stats, we could
For the enchantment recalculation issue when parsing from log, we could...
Now, we should have a consistency states. |
Fixed in commit: 6a48407 |
Some fields (e.g., owner, a.k.a. controller, player) does not resides in card database So we still need to store the original states in entity |
Fixed in commit: fc9d27f |
Need to store (un)enchanted states in entity?
Or, when we need to update/re-calculate enchanted states, we...
--> which remove divine-shield / charge / spell damage / etc.
The text was updated successfully, but these errors were encountered: