Excellent log, the problem was really that oRA3 wasn't watching the highest rank of rebirth
Cool, thanks :)
If now oRA3 would allow me to set "+" as invite keyword, I can finally switch ;)
(Hacked the check myself from "< 2" to "< 1" in the code now, but that's a bit annoying for updating.)
Got this when my party leader was changed in combat:
[2009/09/18 12:02:37-2534-x1]: <event>ADDON_ACTION_BLOCKED:AddOn 'oRA3' tried to call the protected function 'oRA3FrameSub:SetPoint()'.
<in C code>: in function `SetPoint'
oRA3-270\oRA3.lua:812: in function `AdjustPanelInset'
oRA3-270\oRA3.lua:310: in function `?'
CallbackHandler-1.0-5 (Ace3):146: in function <...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:146>
<string>:"safecall Dispatcher":4: in function <[string "safecall Dispatcher"]:4>
<in C code>: ?
<string>:"safecall Dispatcher":13: in function `?'
CallbackHandler-1.0-5 (Ace3):91: in function `Fire'
AceEvent-3.0-3 (Ace3):119: in function <Interface\AddOns\Ace3\AceEvent-3.0\AceEvent-3.0.lua:118>
I'm getting some strange problems with autopromote and guild invite keywords for the last weeks. I can't really describe the circumstances when the problem happens. Players with the same guildrank don't get invited when whispering the keyword from one second to another (people where out of group on both whispers). The same problem happens with autopromote. I can't really find a pattern when this happens. Sometimes people get invited after their second whisper, or they don't.
Has anybody had a problem like this or has an idea what's the problem?