CurseForge.com

ShockAndAwe

146 - Magma Totem being suggested even when present

What steps will reproduce the problem?
1. Enable ShockAndAwe with default settings (Magma Totem is Sixth Priority)
2. Enter combat, placing totems including Magma Totem
3. Observe that the SAA priority frame continues to suggest magma totem even when it's already present

What is the expected output? What do you see instead?
The magma totem check should fall through when the totem is already present, instead SAA seems to think there are no ticks of magma left and suggests to use it at a seemingly high priority

What version of the product are you using?
5.6.2

Do you have an error log of what happened?

Please provide any additional information below.
Did a little testing and it seems ShockAndAwe.db.char.priority.magmatime appears to always be 0, so timeleft is always a negative value.

User When Change
Pericles Dec 22, 2009 at 00:07 UTC Changed status from New to Fixed
tindelli Dec 21, 2009 at 16:31 UTC Create

You must login to post a comment. Don't have an account? Register to get one!

  • 1 comment
  • 1 comment

Facts

Last updated
Dec 22, 2009
Reported
Dec 21, 2009
Status
Fixed - Developer made requested changes. QA should verify.
Type
Defect - A shortcoming, fault, or imperfection
Priority
Medium - Normal priority.
Votes
0

Reported by

Possible assignees