RaidWatch 2

19 - ToGC 10 or 25 Northrend Beasts

What steps will reproduce the problem?
1. Wait till Icehowl comes out during northrend beasts encounter.

What is the expected output? What do you see instead?
Expect nothing, get a window reporting an error as soon as Icehowl comes out.

What version of the product are you using?
1.25

Do you have an error log of what happened?
No I do not.  But the error window that popped up I did notice the error count going up rather fast, and something about movement.

Please provide any additional information below.
I will try to run ToGC again after the reset and take a screenshot when this occurs.

User When Change
mangeg May 11, 2010 at 17:02 UTC Changed status from Replied to Fixed
mangeg Apr 28, 2010 at 07:47 UTC Changed component from Crusaders Coliseum to Plugins
Schmokin Apr 27, 2010 at 21:38 UTC Changed status from Waiting to Replied
mangeg Apr 27, 2010 at 12:10 UTC Changed status from New to Waiting
Schmokin Apr 27, 2010 at 09:37 UTC Create

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

  • 6 comments
  • Avatar of mangeg mangeg May 11, 2010 at 17:02 UTC - 0 likes

    Fixed in the comming builds.

  • Avatar of Schmokin Schmokin Apr 29, 2010 at 06:56 UTC - 0 likes

    I typed 0,0 in the boxes underneath the sliders. It gave an error, but the bar disappeared.

  • Avatar of mangeg mangeg Apr 28, 2010 at 07:47 UTC - 0 likes

    Were you even able to set the size to 0,0? If so that is weird since I have put the restriction to allow 10 as the smallest size both for width and height. Will have to look into that.

    Anyway, I have planned to remake how the anchors for timers work so its possible to make custom anchors and assign different type of timers to any anchor. But this will probably not be before Cataclysm. So for now its not possible to avoid 3 different anchors.

  • Avatar of Schmokin Schmokin Apr 28, 2010 at 04:06 UTC - 0 likes

    I figured out what the problem was, I didn't like the idea of 3 timer bars, so I thought by moving up the timer to the Normal bars up to 200 seconds and decreasing the size of Long timers to 0,0 it would put anything > 15 seconds in Normal bars. With these settings it was making this error occur for any boss who had a timer of anything longer than 200 seconds. My apologies.

    Last edited Apr 28, 2010 by Schmokin
  • Avatar of Schmokin Schmokin Apr 27, 2010 at 21:38 UTC - 0 likes

    I'll try to get in there asap and take a few screenshots of the error.

    EDIT: K took a few screenshots of the error that popped up.

    Last edited Apr 28, 2010 by Schmokin
    • WoWScrnShot_042710_160107.jpg
    • WoWScrnShot_042710_160109.jpg
    • WoWScrnShot_042710_160123.jpg
  • Avatar of mangeg mangeg Apr 27, 2010 at 12:10 UTC - 0 likes

    Will need the Lua error to be able to fix it, so waiting until you done ToGC next reset.

  • 6 comments

Facts

Last updated
May 11, 2010
Reported
Apr 27, 2010
Status
Fixed - Developer made requested changes. QA should verify.
Type
Defect - A shortcoming, fault, or imperfection
Priority
Medium - Normal priority.
Votes
0
Component
Plugins

Reported by

Possible assignees