• World of Warcraft Addons
  • World of Warcraft
  • Average Rating:

  • Your Rating

  • Share
  • Report Abuse

KonferSK (Suicide Kings)

 

Project Updated:
Files Updated: Fri, Nov 13 2009
Supports Game Version: 3.2.0
Category: Boss Encounters, and Guild
Tags:

, , , , , , and [Edit Tags]

Project Manager: Cruciformer
Additional Authors: No additional authors
Current Version: r99
License: Apache License version 2.0
Development Site: CurseForge.com
Avg Daily DL (last 30 days): 56
Downloads Total: 3,848
Favorites: 11
Comments: 41
  • Curse Giveaways
  • Alganon

    Alganon

    Alganon Open Beta Key Giveaway Alganon is an upcoming fantasy-based MMORPG that allows thousands of people to play together in a virtual world that features a rich history dominated by commanding deities...

    Get Key

  • Contests
  • About KonferSK (Suicide Kings)
  •  

Konfer (Suicide Kings Edition) implements the Suicide Kings loot distribution system. This mod is under active development so comments, good or bad, are welcome. I especially want to hear from you if you find any problems so that I can fix them ASAP. The official home for KSK is http:kahluamod.com/ksk. Also if you are able to translate KonferSK into other languages I would love to hear from you.

Features

  • Supports multiple configurations, including guild configs and PUG configs. Each configuration is completely discrete.
  • Quick and easy user and list management
  • Simple, compact user interface
  • Robust synchronization between administrators
  • Item editor that allows you to auto-assign items to users or set default loot priorities
  • User-only mode for non-administrators so they can see their list positions and watch looting take place
  • Auto-assignment of loot when a bid is won
  • Auto-assign loot to defined enchanters if no users bid on an item
  • Supports open rolls that do not suicide users on lists
  • Open roll system supports alt-spec rolls (/roll 101-200)
  • Import of existing SKG users and lists
  • Import users by guild rank or from a CSV list
  • Export to CSV or XML formats
  • Announces winners in guild or raid chat
  • Supports silent bidding (highest bidder not announced)
  • Filters out all mod-related messages for master looter so chat isn't cluttered
  • Will support automatic list position decay (in a few weeks)
  • Allows master looter to force bids and retractions
  • Automatically assigns BOE items that are not bid on to the master looter
  • Automatically supports class restrictions if an item is class specific
  • Guild rank based filtering (allow only raiders and above to roll, then members and above etc)
  • Allows you to define user "roles" such as tank, healer, spellcaster etc, and filter based on that role
  • Detailed admin guide at http:kahluamod.com/ksk/admins.html (summarized below)

First Time Usage

To start using KonferSK you must first create a "configuration". KonferSK supports any number of configurations, each of which can be thought of as a completely different installation of KonferSK. They share no data whatsoever. To create a configuration type:

/ksk createconfig "Configuration Name"

Since this is your first configuration, it will also be the default. You can now use "/ksk" to access the main window. You can also type "/ksk config admin" to get to the configuration admin panel.

The first thing you need to decide is whether or not this is a guild or a PUG configuration. Guild configurations broadcast all of their information to the guild, and PUG configurations only to an active raid. Usually only the guild leader or an officer will create a guild configuration. You should then decide whether or not alts are "tethered". If alts are tethered, it means that only 1 entry will appear in any roll lists for a user. All of that user's defined alts will appear underneath that main user, and they all move on the lists as a group. Thus, no matter which toon they are playing, if they move on a list all of their toons move together. If you want each toon to be its own entity and move independently of each other, turn alt tethering off.

Once the configuration has been created, press the "Users" tab at the bottom or type "/ksk users". This will display the user editor. You can then either create each user by hand, import guild users by rank, or import an existing SKG players list if you were using SKG. When adding users you can assign each user a specific "role". The possible values for the role are "Healer", "Spellcaster", "Melee DPS", "Ranged DPS" and "Tank". It is possible to filter out bids based on which role a user has. If you don't care to do role filtering, leave this as "Not Set" (or you can define the roles for keeping track of who does what and simply not use role filters).

Once you have users defined, you should press the "Lists" button at the bottom or type "/ksk lists". This will show you the currently defined lists and the members on each list, in their correct order. Currently this will be empty. Press the "Config" tab at the top to display the list configuration window. At the bottom right are buttons you can use to create, delete, rename lists etc, or import users into the lists by rank or from an existing SKG roll list if you have SKG installed. Once a list has been created, you can change its sort order if you do not want lists to simply be sorted alphabetically (for example, you want the raiders list displayed before the members list). Lists with the lowest numbered sort order will be displayed first, and lists with the same sort order will be sorted alphabetically. If you do not import users from the guild roster or SKG, press the "Members" tab at the top, select the list you want to add users to, and press the "Insert" button to insert users into the list.

Commands

  • /ksk or /ksk lists - opens the main window, which is the loot members list
  • /ksk loot - opens the loot assignment window
  • /ksk items - opens the item editor
  • /ksk additem itemlink - adds the specified item to the item editor. You need to shift-click an item link from elsewhere to get the correct item link.
  • /ksk users - opens the user editor
  • /ksk sync - opens the sync manager
  • /ksk config - opens the loot assignment options window
  • /ksk help - shows all other commands you can use

Loot Assignment

There are things you can do to make your life easier when it comes time to distribute loot. First, if you have multiple lists that people roll on and you usually start with one particular list, set the default roll list in the loot configuration window (/ksk config). Second, if this is a guild configuration and your ranks are sanely assigned and you use rank filtering, set the default rank you want to start bidding with in each list's configuration. Third, correctly mark those users that are enchanters in the user editor.

When a user has been marked as an enchanter in the user editor, you can select them in the loot assignment options to receive loot that is not bid on. You can set up to 6 enchanters here. Whichever of these enchanters is in raid will be awarded any item that is not bid or rolled on (they will not be suicided).

By default "Auto assign loot when bids close" is enabled. What this means is that when users have bid on an item and a winner has been determined (or users have rolled, or no users have bid and a trusted enchanter is online), KSK will give you the option to automatically assign the item to the relevant user. You always have the option of canceling this auto-assignment, but if you accept, the item is immediately awarded to the user, there is no need to select the item in the standard Blizzard loot frame. In fact if you auto-assign the loot, it will be removed from the Blizzard frame.

Sometimes you may want a specific user to receive a specific item, either because they are collecting a set or because you made a loot mistake or correction and want to ensure that a user receives an item the next time it drops. To do this, add the item with /ksk additem, and in the item editor (/ksk items) select "Assign Next Drop to user", and then press the "Select" button to select the user that will receive the item. You can optionally cause this auto-assignment to suicide the user on a given list, and if this is to be a once-off auto-assignment, select "Auto remove when assigned". If you want the user to receive all drops of the item leave that option unchecked. A good use of this option is for items like the shards for the legendary mace out of Ulduar, you can use this to always assign them to the same healer until they have all 30 shards.

When you add an item to the item list you can also select a specific list to roll on for the item (for example, force Tier items to be rolled for on a Tier list). You can also set custom class restrictions, although the defaults are based on the item type, armor type, or any intrinsic class restrictions.

Each time you click on a lootable item (the top right hand window in the loot panel) it will set whichever list is appropriate as the default (either the global default list or a list specifically set for that item in the item editor). It will also set the initial class filters and guild rank, if you have set any of those values for the roll lists or for the item. You can change the list and filters as you see fit, and then press either "Open Bids" or "Open Roll". Opening bids will allow users to whisper you the word "bid" to bid on an item or "retract" to retract their bid. If they are also using KonferSK, they will see the same window you do and will be able to press the Bid or Retract buttons.

You can change the bid list while bidding is active to move from one list to another, and you can change various filters such as the guild rank filter to allow more and more users to bid. For my own guild, we always start bidding for "raiders", and then if none bid change the guild rank filter to "members", then "initiates" etc. There is a little red "-" next to the guild rank filter that will automatically move down one guild rank to make life easier for rank based filtering.

As the master looter you can select a member from the members list (bottom left panel) and press "Force Bid" to force that user to bid, or select a person who has already rolled and press "Force Retract" to force a retraction. When bid time is over, press "Close Bids" and if there was a winner, it will suicide the user on the list they bid on, and optionally automatically assign the item to them. If no users bid and there are enchanters online (and the option is enabled) it will assign the item to an enchanter to be disenchanted. If the item is a BoE item and the option is set (it is by default) it will assign the item to the master looter instead of an enchanter.

If you want users to be able to roll for an item and not be suicided, you can press "Open Roll" instead of "Open Bids". This starts a 10-second roll-off. Only the 5 highest rollers are shown. If a user types /roll within the last 5 seconds of the countdown, the timer will be automatically extended back to to 5 seconds. KSK supports the notion of "rolling for alts". Normal users who want the item for their main spec can use /roll as per normal. If a user is rolling for an alt, they can use /roll 101-200 to indicate they are rolling for an alt. KSK automatically recognizes that a main spec roll of 89 is higher than an alt-spec roll of 190. If a user rolled incorrectly (they typed just /roll instead of /roll 101-200 for an off-spec item), they can re-roll. However, they do not actually get another shot at rolling a higher number. Their original number is preserved. For example, if a user typed /roll and rolled 65, but realized they should have rolled for off-spec and type /roll 101-200, KSK will adjust their original roll and pretend they had rolled 165 initially, even if their new roll was 199. You can manually pause and resume the roll countdown timer by pressing "Pause" and "Resume".

  • Downloads (7)
  •  
File Name Release Type Game Version Downloads Date
Addon Curse.com Beta 2.3.3 0 9/29/2008
  File Name Release Type Game Version Downloads Date  
  KonferSK (Suicide Kings) r99 Release 3.2.0 669 11/13/2009
  KonferSK (Suicide Kings) r96 Release 3.2.0 869 10/29/2009
  KonferSK (Suicide Kings) r92 Release 3.2.0 1,021 9/29/2009
  KonferSK (Suicide Kings) r89 Release 3.2.0 96 9/28/2009
  KonferSK (Suicide Kings) r86 Release 3.2.0 205 9/23/2009
  • Comments

Add Comment  

Add

You need to login or register to post.

Benefits of Registration

  • Interact with hundreds of thousands of other gamers on an open social network.
  • Post your stories, news, images, videos, and other content to share.
  • Create a network with your fellow gamers or join an existing one.
  • Gain reputation for everything you do.
  • zekeurness said

    I gotta say I love this mod. It makes loot distribution very easy and clear.

    I have one small problem. When I have "Alts Tethered", and a user is playing their alt in a raid, when they check their ranking via the suicide command, they are assigned as spot 0. I usually have to reset the alt as a prime, insert them next to the main, run the raid, reintegrate them by hand to preserve placement. Is this by design?

    Once again, thanks for the addon.

    Reply Report Permalink
  • No this is a bug and I will fix it for the next release.

    Reply Report Permalink
  • PureChaos said

    Ok so i just tried the mod in action. And i had a few issues im wondering how to fix.

    The first is when it went to suicide people it droped them odd amounts, even when i press the button it didnt make people go all the way down on the list.

    Also it droped people if and when it did to the bottom, below people not in the raid.

    I dont know if this is just what the mod does or im missing something(also why do all the f's next to names mean)

    Thanks

    Reply Report Permalink
  • It doesn't drop by "odd amounts" :) Here's how it works.

    If you are in a raid and you manually suicide a user, or they get suicided due to receiving loot, they drop to the bottom of the list. But "bottom" has slightly different meanings. If you are in a raid, the "bottom" means to the slot occupied by the lowest raider on the list. So if there are users below the last user that are not in the raid, the suicide will put them at the last slot of all of the online raiders. However, if they were already in the last slot and they suicide again (receive more loot) then they move to the extreme bottom of the list. That just the way the algorithm works. If a user is marked as "reserved" then the algorithm pretends they are online and in the raid, even if they are not. If a user is frozen, then their position doesnt change at all, unless the algorithm has no choice due to too many people above them being suicided.

    Incidentally, thats what the "F" next to their name means - it means you marked them as frozen, and they will not move, which is wrong. Freezing a user is intended for long-term absenses where you want the user to keep their position. So if you have frozen users you probably want to undo that.

    Reply Report Permalink
  • Uhll said

    Its a great add on.
    I keep getting this see below, i supose its linked with the syncronisation. how do i fix it? and avoid it in the futur?

    Date: 2009-11-16 18:01:28
    ID: 1
    Error occured in: Global
    Count: 1
    Message: ..\AddOns\KKonferSK\KSK-Sync.lua line 732:
    bad argument #3 to 'strfmt' (number expected, got nil)
    Debug:
    (tail call): ?
    (tail call): ?
    (tail call): ?
    [C]: ?
    KKonferSK\KSK-Sync.lua:732: SyncCleanup()
    KKonferSK\KKonferSK.lua:2033:
    KKonferSK\KKonferSK.lua:1954
    [string "safecall DispatcherQ[1]"]:4:
    [string "safecall DispatcherQ[1]"]:4
    [C]: ?
    [string "safecall DispatcherQ[1]"]:13: ?()
    KKonferSK\KKore\KKore.lua:873: SendMessage()
    KKonferSK\KKonferSK.lua:1152:
    KKonferSK\KKonferSK.lua:1095
    (tail call): ?
    [C]: ?
    [string "safecall Dispatcher[1]"]:9:
    [string "safecall Dispatcher[1]"]:5
    (tail call): ?
    KKonferSK\KKore\KKore.lua:2117:
    KKonferSK\KKore\KKore.lua:2099
    [C]: ?
    [C]: pcall()
    Cartographer\Cartographer.lua:928: LoadLoadOnDemandModules()
    Cartographer\Cartographer.lua:522:
    Cartographer\Cartographer.lua:370
    [C]: ?
    ...AddOns\Cartographer\libs\LibRock-1.0\LibRock-1.0.lua:2461:
    ...AddOns\Cartographer\libs\LibRock-1.0\LibRock-1.0.lua:2436
    ...AddOns\Cartographer\libs\LibRock-1.0\LibRock-1.0.lua:2510:
    ...AddOns\Cartographer\libs\LibRock-1.0\LibRock-1.0.lua:2503
    ...AddOns\Cartographer\libs\LibRock-1.0\LibRock-1.0.lua:2583:
    ...AddOns\Cartographer\libs\LibRock-1.0\LibRock-1.0.lua:2546
    ...AddOns\Cartographer\libs\LibRock-1.0\LibRock-1.0.lua:2694:
    ...AddOns\Cartographer\libs\LibRock-1.0\LibRock-1.0.lua:2689
    [C]: LoadAddOn()
    ..\FrameXML\UIParent.lua:232: UIParentLoadAddOn()
    ..\FrameXML\UIParent.lua:255: CombatLog_LoadUI()
    ..\FrameXML\UIParent.lua:502:
    ..\FrameXML\UIParent.lua:474
    AddOns:
    Swatter, v5.6.4424 (KangaII)
    ACP, v3.2.0.23
    AucAdvanced, v5.6.4424 (KangaII)
    AucDb, v5.1.DEV.3583
    AucFilterBasic, v5.6.4424 (KangaII)
    AucFilterOutlier, v5.6.4424.2531
    AucMatchUndercut, v5.6.4424.2531
    AucStatClassic, v5.6.4424 (KangaII)
    AucStatHistogram, v5.6.4424 (KangaII)
    AucStatiLevel, v5.6.4424 (KangaII)
    AucStatPurchased, v5.6.4424 (KangaII)
    AucStatSales, v5.6.4424.2842
    AucStatSimple, v5.6.4424 (KangaII)
    AucStatStdDev, v5.6.4424 (KangaII)
    AucStatWOWEcon, v5.6.4424.2530
    AucUtilAHWindowControl, v5.6.4424.3311
    AucUtilAppraiser, v5.6.4424.2530
    AucUtilAskPrice, v5.6.4424.3175
    AucUtilAutoMagic, v5.6.4424.3142
    AucUtilCompactUI, v5.6.4424.2530
    AucUtilEasyBuyout, v5.6.4424.3583
    AucUtilFixAH, v5.6.4424 (KangaII)
    AucUtilItemSuggest, v5.6.4424.3108
    AucUtilPriceLevel, v5.6.4424.2545
    AucUtilScanButton, v5.6.4424.2530
    AucUtilScanFinish, v5.6.4424.2530
    AucUtilScanProgress, v5.6.4424.2530
    AucUtilSearchUI, v5.6.4424.3655
    AucUtilSimpleAuction, v5.6.4424.0
    AucUtilVendMarkup, v5.6.4424.2530
    AuctionLite, v1.5.1
    Babylonian, v5.1.DEV.130
    Bagnon, v2.12.0
    BagnonForever, v1.1.2
    BagnonTooltips, v
    Cartographer, v2.0
    CartographerBattlegrounds, v2.0
    CartographerInstanceMaps, v2.0
    CartographerWaypoints, v2.0
    ChatBar, v2.5
    Clique, vwowi:revision
    Configator, v5.1.DEV.130
    CurseProfiler, v
    DBMCore, v
    DebugLib, v5.1.DEV.130
    Decursive, v2.4.3.2
    Dominos, v1.12.1
    DominosBufftimes, v
    DominosCast, v
    DominosRoll, v
    DominosTotems, v
    DominosXP, v
    FuBarAddonSpamFu, v1.0.1
    GarQuickLook, v3.0.0.10142008
    Gatherer, v3.1.14
    Grid, v1.30200.2009081101
    GridAutoFrameSize, v2.3.8
    GridIndicatorCornerPlus, v30200-1
    GridIndicatorIconBar, vv1.2.1
    GridIndicatorSideText, v1.0
    GridManaBars, v1.0
    GridStatusHots, v3.2
    gridstatusmending, vv3.01.01.03 release
    GridStatusRaidDebuff, vv3.01
    GridStatusRDBC, v1.0
    GridStatusRDWotLK, v1.0
    GridStatusSelf, v1.0
    GridStatusThreat, v30200-2
    GroupCalendar5, v5.0.1
    KKonferSK, v1.0.0r99
    LibHealComm30, v
    Omen, v3.0.8
    OmniCC, v2.5.7
    Parrot, vv1.10.5
    PowerAuras, v2.6.0
    Quartz, v1.0
    QuestHelper, v1.2.7
    RangeColors, v
    RatingBuster, v
    Recount, v
    SlideBar, v5.6.4424 (KangaII)
    Stubby, v5.6.4424 (KangaII)
    BlizRuntimeLib_enUS v3.2.2.30200 <eu>
    (ck=907)

    Reply Report Permalink
  • Another way you can fix it is to eit KSK-Sync.lua and on line 732 make it be:
    local aps = strfmt ("%s%014.0f", ak, av.lastevent or 0)

    In other words, and the "or 0" part before the closing parenthesis.

    Reply Report Permalink
  • Somehow you have ended up with an active admin without a last event ID. That's what that error is telling me. I would appreciate it if you could send me your savedvariables file so I can try and see how this could happen. I can fix your file for you and mail it back, or, if your list is up to date and you are the config owner, you can delete all your current co-admins, and re-add them. Thats a bit of a pain as they will all have to resync with you but if they are all online it shouldn't take long. Just do this:
    Remove all the admins
    Broadcast the config so they all realise they are no longer admins
    Add all the admins back
    Broadcast so they realize they are all admins again
    Have them sync with you 1 at a time

    Please mail your savedvariables file to cruciformer at gmail dot com. thanks.

    Reply Report Permalink
  • Uhll said

    Thx a lot, I m the owner so will delete all admins and reinstall them.

    Reply Report Permalink
  • cuyukostas said

    Hello and thank you for this awesome Addon. it is a great help for all of us that raid :)

    One question rather simple actually if I may.

    How can a member see his/her position in any list without having to DL the addon?
    Is there a command that can whisper me (ML) and have her the returned position as an answer?

    Thank you in advance

    Reply Report Permalink
  • Aelentel said

    just wisp 'suicide' to the ML or any toon that have been defined as a co-admin of the configuration.
    (that work really fine in our guild)

    Reply Report Permalink
  • PureChaos said

    This mod so far is looking very good and as others have said we have used the old SK for raids. I have however do have a question.

    1- Is the decay been added yet and what is it based on? Is it attendance im guessing or is it you just cant sit at the top all day.

    2- If this mod could track attendance on top of whats its doing it would be by far the best. Setting up rules like you must attend 50% of raids or X thing happen is what im looking for in a SK mod that would be great. I can look at the list showing peoples attendence showing a percentage(on top of this a way so when we run 10 mans instead of 25 it counts both 10's as one raid so it doesnt show Person A as not in a raid or w/e possibly make it by day instead of raid)

    Reply Report Permalink
  • No, the decay system is not in place yet. A big part of the reason is your second question. KSK is a loot distribution addon, not a raid/attendance tracker. I firmly believe mods should be small and single purpose, otherwise your game just suffers. My compromise for lack of the actual decay was guild rank priorities, which fills the gap for most people. However, I do still want KSK to be able to do decay, so in order to support that I have to write a raid-tracker, which KSK can then hook into. I am working on that now.

    Reply Report Permalink
  • PureChaos said

    While i thank ya for your reply and respect that you think that it shouldnt track people. I honestly think thats a big part of loot, Alot of guilds still use a attendance system and integrating it into a loot mod makes it loads easier.

    Reply Report Permalink
  • Sieger said

    Add on seems strong so far, we've been using the original SK add on for some time and have found it severely lacking.

    However, I cannot seem to rename a configuration. I have tried various iterations of the /ksk renameconfig oldname newname command to no avail.

    I've /ksk renameconfig "The Original List" "New List Name", I've tried it with single quotes, with one of the arguments quoted and the other not etc, any help would be appreciated.

    Reply Report Permalink
  • This is a bug. I will fix it in the next revision. There are two ways you can fix this for now:
    1. Use the GUI in /ksk config admin and select the config you want to rename, and press the Rename button. That works.
    2. Edit KKonferSK.lua and on or near line 586 change the word "RenameConfigSpace" to "RenameConfig".

    Both solutions will work, but only for you. You need to do a broadcast for other users to pick up the name change. The config name is not synced in the normal way, it is only sent via a broadcast, so your co-admins and users will get the new name when they receive a broadcast from you after you have changed it.

    Reply Report Permalink
  • Kokuei said

    Is it possible to get a description on how the sync algorithms work (pseudo) and the interaction between admin and co-admins lists?

    Reply Report Permalink
  • I updated the admin guide at http://kahluamod.com/ksk to include a description of the sync internals. Hope this helps you.

    Reply Report Permalink
  • Kokuei said

    = BUG REPORT ==
    Date: 2009-11-05 19:38:57
    ID: 1
    Error occured in: Global
    Count: 1
    Message: ..\AddOns\KKonferSK\KKonferSK.lua line 148:
    attempt to concatenate local 'str' (a nil value)
    Debug:
    (tail call): ?
    (tail call): ?
    KKonferSK\KKonferSK.lua:148:
    KKonferSK\KKonferSK.lua:128
    KKonferSK\KSK-Lists.lua:248: setitem()
    KKonferSK\KKore\KKoreUI.lua:2598:
    KKonferSK\KKore\KKoreUI.lua:2575
    KKonferSK\KKore\KKoreUI.lua:2714: UpdateList()
    KKonferSK\KSK-Lists.lua:1594: RefreshMemberList()
    KKonferSK\KSK-Lists.lua:128:
    KKonferSK\KSK-Lists.lua:119
    (tail call): ?
    (tail call): ?
    KKonferSK\KKore\KKoreUI.lua:2599:
    KKonferSK\KKore\KKoreUI.lua:2575
    KKonferSK\KKore\KKoreUI.lua:2720: SetSelected()
    KKonferSK\KSK-Lists.lua:1748: RefreshLists()
    KKonferSK\KSK-Lists.lua:2035: SetMemberList()
    KKonferSK\KSK-Comms.lua:1343: ?()
    KKonferSK\KSK-Comms.lua:312:
    KKonferSK\KSK-Comms.lua:200
    KKonferSK\KSK-Comms.lua:384: ?()
    KKonferSK\KKore\KKore.lua:924:
    KKonferSK\KKore\KKore.lua:924
    [string "safecall DispatcherQ[4]"]:4:
    [string "safecall DispatcherQ[4]"]:4
    [C]: ?
    [string "safecall DispatcherQ[4]"]:13: ?()
    KKonferSK\KKore\KKore.lua:873: Fire()
    KKonferSK\KKore\KKore.lua:1593: raf()
    KKonferSK\KKore\KKore.lua:1633:
    KKonferSK\KKore\KKore.lua:1626
    AddOns:
    Swatter, v3.1.14 (<%codename%>)
    Ace2, v
    Auctionator, v2.4.9
    AuctionLite, v1.4.1
    AutoLog, v1.06c
    Babylonian, v5.1.DEV.130
    Bagnon, v2.10.0
    BagnonForever, v1.1.2
    BagnonTooltips, v
    Bartender4, v4.4.1
    Cartographer, v2.0
    CartographerBattlegrounds, v2.0
    CartographerCoordinates, v2.0
    CartographerFoglight, v2.0
    CartographerGroupColors, v2.0
    CartographerGuildPositions, v2.0
    CartographerInstanceLoot, v2.0
    CartographerInstanceMaps, v2.0
    CartographerInstanceNotes, v2.0
    CartographerLookNFeel, v2.0
    CartographerNotes, v2.0
    CartographerPOI, v2.0
    CartographerWaypoints, v2.0
    CartographerZoneInfo, v2.0
    Configator, v5.1.DEV.190
    DBMCore, v
    EavesDrop, v2.1
    eCastingBar, v
    Examiner, v09.08.13
    FuBar, v
    FuBarDurabilityFu, v2.11
    FuBarExperienceFu, v1.1 $Revision: 65606 $
    FuBarGuildFu, v2.4.4-117
    FuBarMoneyFu, vv1.2.2
    FuBarRecountFu, v3.10
    FuBarRoutesFu, v1.1
    Gatherer, v3.1.14
    Grid, v1.30200.2009081101
    GridManaBars, v1.0
    GridStatusHots, v3.2
    HideBlizzard, v1.0.54
    IceHUD, v1.5.14 (Revision: 442)
    KKonferSK, v1.0.0r96
    LibRock10, v
    mbuffbar, v
    Omen, v3.0.8
    OmniCC, v2.5.7
    oRA2, v2.0.$Revision: 666 $
    Postal, v3.2.2
    Prat30, v3.2.10
    Prat30Libraries, v
    QuestHelper, v1.2.3
    RatingBuster, v
    Recount, v
    Routes, vv1.2.7
    SlideBar, v3.1.14 (<%codename%>)
    SpamMeNot, v3.2
    SuicideKings, v3.10
    TellMeWhen, v1.2.0
    Tipsy, v$project-version$
    XArt, v1.12.1
    XLoot, v0.9
    XLootMaster, v0.8
    BlizRuntimeLib_enUS v3.2.2.30200 <eu>
    (ck=5f1)


    Reply Report Permalink
  • That error was caused by a user being on a roll list but not in the users database. About the only way I can see that happening is if a co-admin or the owner has made changes to the user list and you are not fully synced.

    Reply Report Permalink
  • avis57 said

    Our guild has just started using this, and are fairly satisfied so far. But there is one small thing bugging me. Whenever loot is assigned and the ml's list changes, the rest of the raid's list doesn't change unless a broadcast is sent out with the updated list. Is this intended or are we doing something wrong?

    Reply Report Permalink
  • Similar Addons
  •  

Average downloads per day

  1. 26,373 Deadly Boss Mods Boss Encounters, and Combat
  2. 3,303 Decursive Buffs & Debuffs, Boss Encounters...
  3. 3,071 BigWigs Bossmods Boss Encounters, and Combat
  4. 3,071 Omen Threat Meter Boss Encounters, and Combat
  5. 2,561 epgp (dkp reloaded) Guild