Minion Beta! - Help us test our new AddOn updater. Get it now!
Download
(312 Kb)
Download
Updated: 11-15-14 01:16 AM
Pictures
File Info
Compatibility:
Warlords of Draenor Pre-Patch (6.0.3)
Warlords of Draenor Pre-Patch (6.0.2)
Updated:11-15-14 01:16 AM
Created:08-27-09 09:05 AM
Downloads:6,863
Favorites:38
MD5:
6.0.3

Konfer Suicide Kings Edition  Popular! (More than 5000 hits)

Version: r605
by: Cruciformer [More]

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 and Suicide Kings 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 history - opens the loot assignment history window
  • /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 addloot itemlink - adds the specified item to the loot list (for manually adding loot items)
  • /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".

Changes in r605:
  • Fixed a small Lua error introduced with the last version

Changes in r604:
  • Fixed a problem where the local realm was being replaced for xrealm characters
  • Try to fix a problem where disconnected realm player rolls aren't recognised

Changes in r603:
  • Fixed a problem with detecting guild officers.

Changes in r602:
  • Fixed a problem that was preventing broadcasts due to incorrectly determining guild rank permissions.

Changes in r601:
  • Fixed a problem that was preventing raids being correctly detected, which meant that the mod wasn't active in SoO, for example.

Changes in r600:
  • Updated to work with 6.0.x. This is largely untested so please report any problems immediately.

Changes in r544:
  • Fixed guild configs so they can be broadcast again
  • Fixed a Lua error that sometimes appeared when adding users

Changes in r543:
  • Fixed whisper bids not working
  • Fixed not assigning loot correctly
  • Fixed not assigning to enchanter when no successful bids

Changes in r542:
  • Fixed a bug where brand new users or if you removed your configs would create a Lua error

Changes in r541:
  • Updated for 5.4.x
  • Hopefully works with cross-realm guild and raid members now

Changes in r530:
  • Updated for 5.3.x
  • No longer get "user in raid but not in list" warnings when in LFR
  • Hopefully fix bug where sometimes loot window doesn't open for some bosses
  • Other minor improvements

Changes in r510:
  • Updated for patch 5.1.0

Changes in r502:
  • Fixed a Lua error when clicking on some loot items the ML can't loot
  • Fixed a Lua error relating to the removal of the decay option that would show up when clicking users sometimes

Changes in r501:
  • Fixed several bug relating to API changes that Blizzard made. A bunch of Lua errors were fixed.
  • Removed the "Exempt from Decay" option in the user editor because KSK will never have decay.
  • A very big thank you to Malkie and LestatAlmighty for helping me test this new release. Lets just pretend r500 never existed.
  • Fixed a string that was causing an unlocalized warning to appear.

Changes in r500:
  • Updated to work with 5.0.x
  • Fixed problems with checksums and other issues for 64-bit client

Changes in r430:
  • Updated to work with 4.3 client

Changes in r412:
  • Hopefully fixed addon communication so syncing will work again

Changes in r411:
  • Updated for 4.2 (finally)

Changes in r410:
  • Updated for patch 4.1.0. Should fix things not being communicated between players.

Changes in r312:
  • Fixed a bug that was causing a Lua error on startup due to changes in 406. Now all relics are available to all classes, and bosses won't drop sigils, librams etc.

Changes in r311:
  • Fixed max level to be 85 instead of 80.

Changes in r310:
  • Updated for 4.0.1
  • Minor French locale fix

Changes in r309:
Changed the way guild ranks are interrogated. This will hopefully eliminate the issue of users not getting broadcasts for guild configs for once and for all.

Changes in r308:
There is still a problem with initialization where the guild ranks are not being set correctly when the mod first starts up. I am working on that issue. For the time being if you use a guild config I suggest you do:
Code:
/kore ginit
/kore status
before trying to do major syncs or broadcasts. Not only you, but the recipient needs to do it too. I will find a way to fix this but it is taking a while to get it exactly right.
  • Added French locale support thanks to Florian Dupret (Grimal)
  • Added BBcode export thanks to Florian Dupret (Grimal)
  • Attempt to improve guild member detection which was preventing broadcasts from working sometimes, which made it difficult for users to sync.
  • Corrected Warlock weapons list as they can use staves. This would affect the class filter and make it incorrectly disallow warlocks from receiving staves unless you explicitly enabled it.
  • Added /kore ginit command to force guild rank initialisation in case the mod gets it wrong.
  • Added /kore status command that produces some useful debugging info in case you are still having trouble with some users not able to receive broadcasts.
  • Fixed a bug where the wrong enchanter was being set when you pressed different "Select" buttons for the 6 possible enchanters.

Please note if you use KonferPUG you must also update it to get the new version of KKore.

Changes in r307:
  • Small change to the sync display window that was preventing some users from doing an initial sync with the config owner due to the sync button being greyed out for first time usage.

Changes in r306:
  • Improved /ksk repair to repair missing data from lists that was causing Lua errors. Lists could have had incorrect data broadcast if they had a ":" in the name.

Changes in r305:
  • Slight change to loot announce to announce one item per line, always.
  • XSLT sorting issue fixed (thanks to David Fillmore)
  • Co-admin highlight issue fixed
  • Added list name and membership checks to /ksk repair

Changes in r304:
  • Fixed a bug where the initial broadcast of a config was causing a Lua error, which would prevent the mod from working further, and users would be unable to select a config correctly.
  • When you change configs, clear out the syncers list in case you had existing sync requests displayed from the old config.

Changes in r302:
  • Fixed the Lua error with SetMinMax that some users were seeing

Changes in r301:
  • Fixed the Lua error during a suicide roll
  • Clean up the owner's user structure if they remove all admins
  • Fixed a problem with detecting alts for co-admins

Changes in r300:
  • This is mostly cosmetic but changed the way version numbers are generated. No longer use the Subversion revision number but rather a manually incremented number. For no particular reason other than the fact that its a round number, this version number is 300.
  • When you switch lists or looting begins, optionally display a list of current raiders who are not on the selected list.
  • Fixed a problem where if an admin's alt tried to create a user, it was using the wrong admin ID.
  • Fixed announcement message for off-spec rolls.
  • Fixed a logic bug with the sync history auto-trimming code that was keeping processed events around even after the events are known to have been safely processed. This didn't affect functionality but did cause a small amount of memory to be wasted.
  • Ensure stored events are auto-trimmed even if it was an admin's alt that sent us the auto-trim event.
  • Fixed a problem where the user count was being corrupted when you switched from tethered to untethered alts and back. This could also be triggered when you marked or unmarked as user as being an alt. If you had a previously corrupted user count this version will fix the user count.
  • Fixed a problem where the list count was being corrupted when a list was deleted. If you had a previously corrupted list database this version will automatically fix the list count.
  • Item tooltips are now enabled in the history browser.
  • You can now Shift-Click items in both the loot distribution window and the history browser to insert a chat link for the clicked item. If you do this in the loot window it does NOT select the item or change the currently selected item, it just inserts the link.
  • Significant changes and speedup in the list display code for long lists (like the full user list, roll lists etc).
  • Significant change to the few places where popup menus are used (inserting a user into a roll list, selecting an alt's main, selecting an enchanter and assigning the next drop to a specific user). Uses the new KKore popup list code and no longer wastes memory the way the old code did.
  • A few other visual cleanups, such as disabling the user interface elements in the user panel when no user is selected (and disabling the Delete and Rename buttons).
  • When using the "Announce All" button in the list panel, prefix additional lines with "KonferSK" so that the chat message filter works for any additional lines that get sent, not just the first.
  • When the chat message filter is enabled, also filter out mod messages that go to guild chat, not just raid chat.
  • In the config administration panel, the config owner is now a dropdown list of currently configured coadmins. Only existing coadmins can ever be converted to the list owner and it makes more sense to have this be a dropdown rather than having to type the user's name in.
  • Fixed a bug in the dropdown code that was causing a titled dropdown to lose its title. This could be seen in the Copy Config dialog where the dialog box with the list of roll lists to copy was not correctly titled.
  • If you inserted a user into the list and you had tethered alts set, selecting an alt from the popup list would incorrectly insert the alt into the list, not the user's main. Fixed.
  • Correctly disable the force bid button if you cancel a bid.
  • Several under the hood improvements to the KKore UI module, many of which improve the visual appearance. The changes are subtle but noticable if you are as picky as me.

Changes in r217:
  • Fixed the user delete dialog to correctly display the "Delete all alts of user" option.
  • Pop up a visible warning rather than just printing a line of text if you receive protocol messages from a user whose mod is out of date.
  • Increased the protocol version number to force all users to upgrade. Users with older versions of the mod will still only see the printed warning, not the popup dialog.
  • Fixed a nasty bug in the user delete code where it was skipping over every second alt when you deleted a user and all their alts. Also fix corrupted user lists on startup if you had been affected by this bug.

Changes in r209:
  • Fixed importing of SKG and SuicideKings lists.
  • Fixed a Lua aerror that was popping up when you tried to add a new user.
Archived Files (6)
File Name
Version
Size
Author
Date
r604
312kB
Cruciformer
11-14-14 11:31 AM
r604
312kB
Cruciformer
11-14-14 11:29 AM
r603
312kB
Cruciformer
10-21-14 12:26 AM
r602
312kB
Cruciformer
10-20-14 02:22 AM
r543
312kB
Cruciformer
02-25-14 01:37 PM
r530
312kB
Cruciformer
06-04-13 01:16 PM


Post A Reply Comment Options
Unread 11-11-09, 08:10 AM  
Cruciformer
A Kobold Labourer
AddOn Author - Click to view AddOns

Forum posts: 1
File comments: 65
Uploads: 2
Re: Re: Re: Re: Re: Re: Re: Updated admin guide

Originally posted by Zanthor
Bug Report: Sometimes when running a bid the list positions report from a different list. For example bidding on an epic item with the epic list shown on the UI shows playerX in 5th place, but when he bids it announces he's in 30th place (which he is, on the Tier list)...

I can fix this by changing lists and then back or canceling the bid and reopening.

This is an issue I've had happen several times now but have never been able to replicate an exact cause or even make happen on demand... I'd wager some form of race condition.
"the bid list report from a different list" - reported by what?
How is the list originally selected? By you manually selecting it or automatically becuase of a config default or item setting?
Cruciformer is offline Report comment to moderator  
Reply With Quote
Unread 11-10-09, 08:35 AM  
Zanthor
A Theradrim Guardian
AddOn Author - Click to view AddOns

Forum posts: 64
File comments: 23
Uploads: 2
Re: Re: Re: Re: Re: Re: Updated admin guide

Bug Report: Sometimes when running a bid the list positions report from a different list. For example bidding on an epic item with the epic list shown on the UI shows playerX in 5th place, but when he bids it announces he's in 30th place (which he is, on the Tier list)...

I can fix this by changing lists and then back or canceling the bid and reopening.

This is an issue I've had happen several times now but have never been able to replicate an exact cause or even make happen on demand... I'd wager some form of race condition.
Zanthor is offline Report comment to moderator  
Reply With Quote
Unread 11-10-09, 08:32 AM  
Zanthor
A Theradrim Guardian
AddOn Author - Click to view AddOns

Forum posts: 64
File comments: 23
Uploads: 2
Re: Re: Re: Re: Re: Updated admin guide

Originally posted by Cruciformer
I cant do what you want. The auto-assigning of loot is optional, closing a bid isn't. That is the only safe place to put the suicide. If your raiders can't make their minds up, leave the bid open a little longer. Confirm with them on vent etc. Sounds like a little communication would solve the problem. They could just as easily change their mind after you press OK too you know

However this has often been requested and I will certainly see what I can come up with to add a proper undo.
I'd appreciate a proper undo at the least... we do communicate, a lot. It never fails though that every week or two this issue comes up, stops raid for 5 minutes while I fix it, etc...

The main issue for me is the guilds culture doesn't allow being a hardass about this. I'd quite happily live by the rule of if a winner changes their mind the loot moves to the next person in line, they get suicided, etc... and the first winner stays suicided. I'd get voted off the island in no time though.
Zanthor is offline Report comment to moderator  
Reply With Quote
Unread 11-10-09, 08:20 AM  
Cruciformer
A Kobold Labourer
AddOn Author - Click to view AddOns

Forum posts: 1
File comments: 65
Uploads: 2
Re: Re: Re: Re: Updated admin guide

Originally posted by Zanthor
Simply moving them back to the previous position doesn't put everyone else back where they belong and is unfair to those who aren't on that raid. The method that I've used is very similar but actually puts everyone back exactly where they belonged before the mishap...

I scroll back up and find what position they were in as well. I then suicide the player in that position until the list is back in it's previous state.

While you can't suicide on receipt of the loot you could suicide on the click of the "OK" button instead of the "Close Bid" button... The dialog where it asks if you really want to give player X item Y... if it suicides at that point you've already had your moments reprieve... Would solve the issue I've run into most often which is players reevaluating right after I click close.
I cant do what you want. The auto-assigning of loot is optional, closing a bid isn't. That is the only safe place to put the suicide. If your raiders can't make their minds up, leave the bid open a little longer. Confirm with them on vent etc. Sounds like a little communication would solve the problem. They could just as easily change their mind after you press OK too you know

However this has often been requested and I will certainly see what I can come up with to add a proper undo.
Cruciformer is offline Report comment to moderator  
Reply With Quote
Unread 11-10-09, 06:46 AM  
Zanthor
A Theradrim Guardian
AddOn Author - Click to view AddOns

Forum posts: 64
File comments: 23
Uploads: 2
Re: Re: Re: Updated admin guide

Simply moving them back to the previous position doesn't put everyone else back where they belong and is unfair to those who aren't on that raid. The method that I've used is very similar but actually puts everyone back exactly where they belonged before the mishap...

I scroll back up and find what position they were in as well. I then suicide the player in that position until the list is back in it's previous state.

While you can't suicide on receipt of the loot you could suicide on the click of the "OK" button instead of the "Close Bid" button... The dialog where it asks if you really want to give player X item Y... if it suicides at that point you've already had your moments reprieve... Would solve the issue I've run into most often which is players reevaluating right after I click close.
Zanthor is offline Report comment to moderator  
Reply With Quote
Unread 11-10-09, 03:09 AM  
Cruciformer
A Kobold Labourer
AddOn Author - Click to view AddOns

Forum posts: 1
File comments: 65
Uploads: 2
Re: Re: Updated admin guide

Originally posted by Zanthor
I'd like to suggest making the Suicide action actually happen when loot is awarded not when the auction ends... (Or putting a single-transaction rollback in place)

I've run into the situation where a player has the item and can't be awarded it, or didn't get permission to receive the loot, and have had to do major monkey business to get the list back straight!
Can not do it on loot receipt because you do not always get the message that someone has received loot. For example if they have changed to a different wing in Naxx or taken a portal to a different part of Ulduar and are out of range, they can still get the loot but you wont receive any message letting you know they have. Its been a thorn in my side that there is not an official event I can trap that tells me when loot is awarded in a raid.

I go to considerable trouble to make sure that only the correct user can receive loot. It filters out inappropriate classes, ensures that the user was actual present for the boss kill etc. As for implementing a rollback, it is quite complicated due to the way in which sync events are managed. In the rare cases where we had to "undo" a suicide it was a simple matter of scrolling up in the chat log to see what position the user was in before the roll happened, and to manually move the user back up to that position. Its a few button clicks and doesn't complicate the data model. I dont understand why it takes any "monkey business" to just move them up. If they were near the top you can "King" them (move them to the extreme top of the list) and then move them down to their previous place, or if they were near the bottom just click move up a few times. Is that not acceptable?

I've thought about having an undo for quite a while and it really is much nastier than you think but if manually moving them is somehow too taxing I can re-visit the idea and see if I can't find a workable solution for it.
Cruciformer is offline Report comment to moderator  
Reply With Quote
Unread 11-09-09, 07:11 PM  
Zanthor
A Theradrim Guardian
AddOn Author - Click to view AddOns

Forum posts: 64
File comments: 23
Uploads: 2
Re: Updated admin guide

I'd like to suggest making the Suicide action actually happen when loot is awarded not when the auction ends... (Or putting a single-transaction rollback in place)

I've run into the situation where a player has the item and can't be awarded it, or didn't get permission to receive the loot, and have had to do major monkey business to get the list back straight!
Zanthor is offline Report comment to moderator  
Reply With Quote
Unread 10-31-09, 05:06 AM  
Cruciformer
A Kobold Labourer
AddOn Author - Click to view AddOns

Forum posts: 1
File comments: 65
Uploads: 2
Updated admin guide

I have updated the admin guide (http://kahluamod.com/ksk/admins.html) to discuss the various new options that have been added since the guide as first written, as well as added a brief section on XML exports.
Cruciformer is offline Report comment to moderator  
Reply With Quote
Unread 10-29-09, 02:18 PM  
Cruciformer
A Kobold Labourer
AddOn Author - Click to view AddOns

Forum posts: 1
File comments: 65
Uploads: 2
Re: Re: XSLT stylesheet for XML export string

Originally posted by Eneswar
That download link doesnt work, could you check it out please?
The XSLT is now part of the distribution. Look in the XSLT directory.
Last edited by Cruciformer : 10-29-09 at 04:47 PM.
Cruciformer is offline Report comment to moderator  
Reply With Quote
Unread 10-29-09, 12:31 PM  
Pagezero2
A Kobold Labourer

Forum posts: 0
File comments: 20
Uploads: 0
Re: Re: Decay

Originally posted by Cruciformer
To be honest I am a bit in two minds about decay....
Thanks for the update about decay, I know it isn't easy it just sounded so nice. People seem to get upset when they get demoted from the "raider" level but maybe it is because we don't do it very often, but I do agree rank based is probably a better overall solution.

Decaying seems to be a good solution for a problem we see often, a raider takes a break for a month or two and then comes back full time. I guess we could leave them them at the demoted level for a while once they return, we just need to get by the social issues of "why am I not at the raider rank".
Pagezero2 is offline Report comment to moderator  
Reply With Quote
Unread 10-29-09, 09:43 AM  
Eneswar
A Fallenroot Satyr
 
Eneswar's Avatar

Forum posts: 21
File comments: 41
Uploads: 0
Re: XSLT stylesheet for XML export string

Originally posted by Cruciformer
If you want to use the XML export feature, I have created an XSLT stylesheet you may want to use and modify for your website. For an example of how it renders the lists, see http://kahluamod.com/ksk/xml/ksk.xml. The actual stylesheet can be found at http://kahluamod.com/files/ksk/XSLT.zip.

Since the XML export from the mod does not add a full XML header, you need to add one, with the correct encoding, and a pointer to whatever you call your stylesheet. Using the example link above, use your browser's "view source" ability to see the two lines I added at the top, or you can cut and paste these (as long as you use the stylesheet name ksk.xslt):

Code:
<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml-stylesheet type="text/xsl" href="ksk.xslt"?>
That download link doesnt work, could you check it out please?
Eneswar is offline Report comment to moderator  
Reply With Quote
Unread 10-29-09, 04:24 AM  
Cruciformer
A Kobold Labourer
AddOn Author - Click to view AddOns

Forum posts: 1
File comments: 65
Uploads: 2
Re: Decay

Originally posted by Pagezero2
While your changing some the internals around, what are you plans for the decay feature? Are you thinking of a manual thing (Decay now button) or something more automatic (every X days if the player hasn't raid in Y days). Is the only option for decay to move down a spot?
To be honest I am a bit in two minds about decay. Unlike systems like EP/GP where decay is part of the algorithm, suicide kings does not lend itself well to decay. About the only realistic thing you can do is move users down X slots on a list.

I added (a few releases ago, release 89 I think) the ability to use guild rank priorities. I know this isn't decay but it does ensure that active members (who it is assumed have a different rank to non-active members) get loot in priority over non-active members. Speaking to the GM's of several guilds running the mod, as well as my own guild's experience, we all found that using rank based control was much easier to grasp than the idea of decay. GM's and officers tend to keep a close watch for attendance and performance, and usually adjust guild ranks accordingly.

I haven't given up on the idea of decay permanently, but part of doing decay is accurate raid tracking. I don't like any of the raid trackers I have seen out there, so I have decided to write my own. Once it is done, either KSK will have a dependency on that mod if you want to use decay, or will use the relevant code bits from that mod within KSK.

Either way, if you were waiting breathlessly for decay I am afraid the wait will be a bit longer than I first thought. I still have a bunch of cleanup left (r96 was from the main branch not the cleanup branch) but all thats left for the cleanup now is some repetitive changes, the actual hard part is done and the UI library I wrote for KSK has been significantly updated and improved, and uses considerably less resources. That same library (KKore) is being used for the raid tracking mod, as yet un-named.
Cruciformer is offline Report comment to moderator  
Reply With Quote
Unread 10-29-09, 04:09 AM  
Cruciformer
A Kobold Labourer
AddOn Author - Click to view AddOns

Forum posts: 1
File comments: 65
Uploads: 2
Changes in r96

  • Added loot history export (XML only)
  • Added XSLT stylesheets and examples in XSLT/ directory
  • Added ability (in list config screen) to add either missing raid members or all missing users to a list, both in order or randomly.
  • Cleaned up the list XML export string to remove duplicate information
  • Changed how a co-admin is interpreted. Now, if a co-admin or config owner are on an alt, they are still recognised as an admin / owner. The only time you need to define an alt as a co-admin is if that alt is on a different account.
  • Added the export date and time to both the list and history XML export.
  • If a user is deleted, preserve their name and class in the loot history list so that if the user ID is reused, it does not incorrectly show the new user as having received loot.
Cruciformer is offline Report comment to moderator  
Reply With Quote
Unread 10-26-09, 02:16 PM  
Pagezero2
A Kobold Labourer

Forum posts: 0
File comments: 20
Uploads: 0
Decay

While your changing some the internals around, what are you plans for the decay feature? Are you thinking of a manual thing (Decay now button) or something more automatic (every X days if the player hasn't raid in Y days). Is the only option for decay to move down a spot?
Pagezero2 is offline Report comment to moderator  
Reply With Quote
Unread 10-08-09, 03:46 PM  
Cruciformer
A Kobold Labourer
AddOn Author - Click to view AddOns

Forum posts: 1
File comments: 65
Uploads: 2
Re: Re: Re: Re: XSLT stylesheet for XML export string

Originally posted by Zanthor
Minor request, add the date of the export to the KSK node...
Sure I can do that for the next release. That may be a while, I am reworking quite a bit of the internal UI code (things wont look much different visually but the code will be a lot better, especially for drop-down menus where I am abandoning Blizzard's code) as well as some other code that was written a long time ago before I knew what I know now.
Last edited by Cruciformer : 10-08-09 at 03:47 PM.
Cruciformer is offline Report comment to moderator  
Reply With Quote
Post A Reply



Category Jump: