My guild leader is saying that NRT is no longer giving people in the raid attendance credit if they're offline. This may be desired behavior for some guilds, but for us it just creates extra work of having to add those people. Could some way to toggle the behavior be added?
Okay I understand this problem better now. What's happening is people who whisper in from alts who are not in our guild are automatically rejected with some kind of vague "cannot be added" error. I believe this may be a side-effect of the guild rank filtering feature.
Okay I understand this problem better now. What's happening is people who whisper in from alts who are not in our guild are automatically rejected with some kind of vague "cannot be added" error. I believe this may be a side-effect of the guild rank filtering feature.
That can't be right either.
They should whisper him the name of their main, and he should be added to the attendance set provided their main is in the guild, is not on the blacklist and has a guild rank that is allowed on attendance sets.
Do you think you might be willing/able to add more informative feedback to NRT when it rejects a whisper, so that we can narrow down what the cause of rejection is? This is a real issue for us, and I'd like to work to get it resolved.
If nothing else, I guess I could hack NRT myself every time a new version is released to remove those checks, and have our guild leader use that.
Edit: Is the rank filtering inclusive or exclusive? I see all the ranks are checked by default.
Edit 2: Guild leader says all ranks are checked and noone is in her blacklist, but they were still being rejected when whispering from alts not in our guild. She added some of the problem people to the whitelist after the raid ended, so hasn't had a chance to see if that works as a workaround.
i basically use almost the same output as the default raidtracker xml, i put it as mentionned in a separate custom output .lua to make sure it doesnt get modified when nrt update.
so with the code
NRT:RegisterOutputFormatter("Elusive", function(attendance, loot, killedBosses)
local lootByTracked = {}
for i, v in ipairs(loot) do
if not lootByTracked[v.from] then lootByTracked[v.from] = {} end
table_insert(lootByTracked[v.from], v)
end
...........etc...........
end)
i get this error when trying to use "elusive" : interface\addons\nrtelusive\formatter.lua:5:attempt to cal global 'table_insert' (a nil value)
Trying to make a few changes for myself can't get one of them working.
First one is to add player to WL when manually adding to attendance set. (This is working fine) http://ace.pastey.net/87375
Second one is to print out the current WL to guild chat (when shift double-clicking on the NRT icon) http://ace.pastey.net/87376
I keep getting this error:
[2008/05/07 02:02:35-234-x1]: SendChatMessage(): Invalid escape code in chat message:
<in C code>: ?
<in C code>: ?
<in C code>: in function `SendChatMessage'
NRT-372464\NRT.lua:1526: in function `OnDoubleClick'
FuBarPlugin-2.0-63898 (BugSack):955: in function <...Ons\BugSack\Libs\FuBarPlugin-2.0\FuBarPlugin-2.0.lua:953>
---
It prints the wl correctly in the local addon message but not in guild chat. Any idea what is causing the error?
I notice sometimes that if there are like 4 pieces of loot on a boss, 3 of them will get assigned to the boss, then one randomly to the zone and I'm not sure how to deal with that. Also sometimes trash loot gets attributed to a mob name instead of the zone name so there's no string for that.
Also, some of the other officers are having issues with it showing the wrong raid information, but I think that's because they try to store weeks of raids in it or something silly
Exactly, when you kill a boss, NRT starts an internal timer of 5 minutes. Anything looted inside that window will be attributed to the boss.
Anything else looted will be attributed to the persons target if it exists and is a "elite" or "worldboss" mob, if not it will be attached to the zone.
I hope that makes sense.
Now, I'm not sure if this is ideal or not. How would you else have it attribute items - any suggestions?
1. Perhaps all drops should just be attributed to the zone and then have a .target property that will be populated if the target could be found? That wouldn't solve boss drops though.
2. Perhaps the internal timer could be shorter, say 2-3 minutes, and have it reset back to zero each time something is looted after a boss kill? That would "solve" bosses with lots of loot, I guess?
Exactly, when you kill a boss, NRT starts an internal timer of 5 minutes. Anything looted inside that window will be attributed to the boss.
Anything else looted will be attributed to the persons target if it exists and is a "elite" or "worldboss" mob, if not it will be attached to the zone.
I hope that makes sense.
Now, I'm not sure if this is ideal or not. How would you else have it attribute items - any suggestions?
1. Perhaps all drops should just be attributed to the zone and then have a .target property that will be populated if the target could be found? That wouldn't solve boss drops though.
2. Perhaps the internal timer could be shorter, say 2-3 minutes, and have it reset back to zero each time something is looted after a boss kill? That would "solve" bosses with lots of loot, I guess?
Tracking the loot source mob is an enormous pain with the current state of the API. The only assured way I can think of to determine the exact loot source mob is if there's a ML with a loot that matches the ML threshold. Your method solves the majority of relevant cases. An alternative, slightly more costly method which would require no timer would be to check each raid target on any threshold loot for a relevant boss mob and attribute it to a trash mob if no worldboss target exists.
I'd really like to see them add this info to an event or API call.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Charming.
NRT: was the gem that was missing. I was using addon:
Thank you.
Okay I understand this problem better now. What's happening is people who whisper in from alts who are not in our guild are automatically rejected with some kind of vague "cannot be added" error. I believe this may be a side-effect of the guild rank filtering feature.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThat can't be right either.
They should whisper him the name of their main, and he should be added to the attendance set provided their main is in the guild, is not on the blacklist and has a guild rank that is allowed on attendance sets.
If nothing else, I guess I could hack NRT myself every time a new version is released to remove those checks, and have our guild leader use that.
Edit: Is the rank filtering inclusive or exclusive? I see all the ranks are checked by default.
Edit 2: Guild leader says all ranks are checked and noone is in her blacklist, but they were still being rejected when whispering from alts not in our guild. She added some of the problem people to the whitelist after the raid ended, so hasn't had a chance to see if that works as a workaround.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumWhat does the added 'do' statement on line 1107 do, just out of curiosity?
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIt creates a new scope.
so with the code
NRT:RegisterOutputFormatter("Elusive", function(attendance, loot, killedBosses) local lootByTracked = {} for i, v in ipairs(loot) do if not lootByTracked[v.from] then lootByTracked[v.from] = {} end table_insert(lootByTracked[v.from], v) end ...........etc........... end)i get this error when trying to use "elusive" :
interface\addons\nrtelusive\formatter.lua:5:attempt to cal global 'table_insert' (a nil value)
First one is to add player to WL when manually adding to attendance set. (This is working fine)
http://ace.pastey.net/87375
Second one is to print out the current WL to guild chat (when shift double-clicking on the NRT icon)
http://ace.pastey.net/87376
I keep getting this error:
It prints the wl correctly in the local addon message but not in guild chat. Any idea what is causing the error?
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumwaitlisttext = waitlisttext:gsub("(|r)", "")To remove the "|r" after the color.
EDIT: Oh, and you shouldn't use the locale when printing it.
Just print the variable directly. If you want to localize something, it should only be "WL".
Thanks! That got it working. Feel free to use the changes if you want.
Also, some of the other officers are having issues with it showing the wrong raid information, but I think that's because they try to store weeks of raids in it or something silly
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumAnything else looted will be attributed to the persons target if it exists and is a "elite" or "worldboss" mob, if not it will be attached to the zone.
I hope that makes sense.
Now, I'm not sure if this is ideal or not. How would you else have it attribute items - any suggestions?
1. Perhaps all drops should just be attributed to the zone and then have a .target property that will be populated if the target could be found? That wouldn't solve boss drops though.
2. Perhaps the internal timer could be shorter, say 2-3 minutes, and have it reset back to zero each time something is looted after a boss kill? That would "solve" bosses with lots of loot, I guess?
Tracking the loot source mob is an enormous pain with the current state of the API. The only assured way I can think of to determine the exact loot source mob is if there's a ML with a loot that matches the ML threshold. Your method solves the majority of relevant cases. An alternative, slightly more costly method which would require no timer would be to check each raid target on any threshold loot for a relevant boss mob and attribute it to a trash mob if no worldboss target exists.
I'd really like to see them add this info to an event or API call.