[PE] TeamPhoenix

[bauwoo]

New Bug:

Message: ...erface\AddOns\probably\system\protected\firehack.lua:63: bad argument #1 to 'band' (number expected, got string)
Time: 03/26/15 22:36:33
Count: 407
Stack: [C]: ?
[C]: in function `band'
...erface\AddOns\probably\system\protected\firehack.lua:63: in function `UnitsAroundUnit'
Interface\AddOns\probably\system\conditions\core.lua:1108: in function <Interface\AddOns\probably\system\conditions\core.lua:1106>
Interface\AddOns\probably\system\core\dsl.lua:52: in function <Interface\AddOns\probably\system\core\dsl.lua:20>
(tail call): ?
Interface\AddOns\probably\system\core\parser.lua:195: in function `nested'
Interface\AddOns\probably\system\core\parser.lua:261: in function `table'
Interface\AddOns\probably\system\core\parser.lua:325: in function `table'
Interface\AddOns\probably\system\timers\rotation.lua:71: in function `cycle'
Interface\AddOns\probably\system\timers\rotation.lua:130: in function `event'
Interface\AddOns\probably\system\core\timer.lua:16: in function <Interface\AddOns\probably\system\core\timer.lua:11>

Locals:

[akeon1]

Meh doubtful that's a pe. Issue.

More likely a result of failed wrote to probably.lua

[akeon1]

New Bug:

Message: ...erface\AddOns\probably\system\protected\firehack.lua:63: bad argument #1 to 'band' (number expected, got string)
Time: 03/26/15 22:36:33
Count: 407
Stack: [C]: ?
[C]: in function `band'
...erface\AddOns\probably\system\protected\firehack.lua:63: in function `UnitsAroundUnit'
Interface\AddOns\probably\system\conditions\core.lua:1108: in function <Interface\AddOns\probably\system\conditions\core.lua:1106>
Interface\AddOns\probably\system\core\dsl.lua:52: in function <Interface\AddOns\probably\system\core\dsl.lua:20>
(tail call): ?
Interface\AddOns\probably\system\core\parser.lua:195: in function `nested'
Interface\AddOns\probably\system\core\parser.lua:261: in function `table'
Interface\AddOns\probably\system\core\parser.lua:325: in function `table'
Interface\AddOns\probably\system\timers\rotation.lua:71: in function `cycle'
Interface\AddOns\probably\system\timers\rotation.lua:130: in function `event'
Interface\AddOns\probably\system\core\timer.lua:16: in function <Interface\AddOns\probably\system\core\timer.lua:11>

Locals:

Try re injecting firehack. Not an issue with the rotation. Please try keep this thread clean

[barandeniz]

In the addons file just make capital P of the probably file. It happens when you use github application to synch. Just make probably to Probably. You are welcome. Its for the reseting issue btw.

Sent from my iPad using Tapatalk

[bauwoo]

Thanks, that did it.

[bri134]

Got this today after updating:

Message: ...dOns\Probably_AkeRotations\cr\paladin\protection.lua:30: attempt to concatenate a nil value
Time: 03/27/15 18:09:26
Count: 1612
Stack: [C]: ?
...dOns\Probably_AkeRotations\cr\paladin\protection.lua:30: in function `evaluation'
Interface\AddOns\Probably\system\core\parser.lua:188: in function `nested'
Interface\AddOns\Probably\system\core\parser.lua:261: in function `table'
Interface\AddOns\Probably\system\timers\rotation.lua:71: in function `cycle'
Interface\AddOns\Probably\system\timers\rotation.lua:130: in function `event'
Interface\AddOns\Probably\system\core\timer.lua:16: in function <Interface\AddOns\Probably\system\core\timer.lua:11>

Locals:

[akeon1]

my heart bleeds for ya.

[bri134]

LoL look dude I like your routines. How do you want us to report issues?

[StinkyTwitch]

Try unchecking and then checking the Lay on hands setting in the config then reload. The way the config is initialized doesn't seem to be setting those things on load. Let me know if that works. I took a look at it and tried it and seemed to work for my paladin.

[bri134]

Try unchecking and then checking the Lay on hands setting in the config then reload. The way the config is initialized doesn't seem to be setting those things on load. Let me know if that works. I took a look at it and tried it and seemed to work for my paladin.

Seemed to work - thank your sir!

[akeon1]

Seemed to work - thank your sir!

Just remember: basic troubleshooting:

- Clear out config files from WTF folder (if poo really hits the fan) and if you do this remember you need to check the gui settings as Stinky pointed out.
- ensure FH is attached properly (LUA Protected error mean its not)
- reload and open close settings a few time (Can resolve many GUI to PE issues.
- always keep the prior version of PE backed up when you are updating (so you can roll back - aka the Unit.buff error everyone was complaining about).

If after all this you think its a rotation issue - try and:

1) Describe the error and what you are seeing happen
2) Copy it in the (post like you did)
3) "/pe al" can help me see if casts are getting stuck or the wrong spell is prioritized

Not target at you specifically, just a general tips for people.

[akeon1]

Updated Retribution pally by adding two AE modes (chosen in GUI)
Spam mode - spams divine storm, using Final verdict only when the buff can be consumed by Divine Storm immediatly after.
Conserve - Traditional DS / FV alternating usage.


Personal feeling is use spam mode on groups of large adds.
Conserve mode when all 3 targets are bosses. (AKA maidens).

But i thought id give you guys the choice so added to GUI


Update from Git

[Drinksbeer]

updated retribution pally by adding two ae modes (chosen in gui)
spam mode - spams divine storm, using final verdict only when the buff can be consumed by divine storm immediatly after.
Conserve - traditional ds / fv alternating usage.


Personal feeling is use spam mode on groups of large adds.
Conserve mode when all 3 targets are bosses. (aka maidens).

But i thought id give you guys the choice so added to gui


update from git

u r awesum

[bauwoo]

Fresh install of PE and this update and I get this bug:

Message: Interface\AddOns\Probably_AkeRotations\cr\paladin\retribution.lua:105: '}' expected (to close '{' at line 92) near '{'
Time: 04/03/15 01:31:53
Count: 1
Stack:
Locals:

[akeon1]

ok sorry i missed a comma.

try now (redownload