WowAce

Alls quiet for a day, im guessing that one was happy. Enjoy. :)

Anyone having trouble with DKP at all?

From the 2.1.32 release notes:

- lots of UI rework, mostly things you wouldnt see,
but making faster or more stable or easier to deal with for me. there arte still a few places i havnt rewritten and was getting that done. in this case was primarity the list line templates. needed more love. the more i digest and make clean the msot stable these releases will be.
- cleaning DBs in DB update for:
nils in Leave Join from user player removes, cause was fixed as well
session zone as empty string should have been nil, never empty string
probably left over from CT imports, not accounted for. in this one no zone is no zone
- fixed export issue exporting new instance XML
- redid part of attendee lookups hops of fixing stat-up issue one person had
- fixed long time cosmetic UI issue where note icons were high stratus causing them to get drawn over other windows

fixed, wil be in .32

does this happen every tiem you load?
can send me your db again if not too much trouble?

also nice if to knwo if ther was an error before that.
btw for anyone who has had lots of issues with plugins in the past, "swatter" is a very good error catcher. comes with autioneer if you have that also. it stores and puts them all in one window, much less annoying and can page back to see if one thing caused another.

ok i jsut tried it with your old data,, in party and raid, and even tried to exit game in raid and come back and stil works

Should not have increased in size in any signifiacant way. The format is basically the same. What might help some woudl be to remove the events from the eml and see if that works better. If might be that for some teh events started workign again with wotlk. < BossKills >

And of course if AutoZone not turned on (the ability to automatically set the zone) then 3 wont work either, of course :).

And if that wasnt enough updates today....

From the 2.1.31 release notes:
- added new log type - 3, for each group type
configurable for each group type separately
0 off, 1 log, 2 auto create, 3 auto instance
raid is 3 by default
this is the auto create session on change zone feature

This is the last real feature from any CT version I know of that was not in this one, sans a few the various export forks. So is feature completenow and all forks merged. There are a ton of forks that implement one minor export differnce, and that wil take time to consolidate all those if any worth still for anyone.

This feature will fire if set per group type of which there are 5 atm. You can see what group type it thinks you are in, in the status bar text at the top. This one (3) will fire, in addtion to all of the rules for 2 (Auto Create), when you are in a session and the zone changes from one trigger zone to another, and when fires will create a new log session automaticaly. If you are in a session that has not hit a triggerable zone yet it will not create a new session, and if you are not in a session then it wil not fire either. If you woudl rather I make this so it creates a new session even if not in one for hiting a triggerable zone let me know. If thats the case i might roll them all up and jsut make that a part of auto create. Currently auto create (2) will create an instance if: triggerable event occurs, triggerable looting occurs, or creating a triggerable party. This is geting way too technical, some will enjoy.

Things to remember:
- 0 (off) will never log or create session while in that group type
- 1 (log) log events, loot, members if pass other filters if group already started
- 2 (auto create) will log and create if boss kill, start group of that type, recieve loot passes filters
- 3 (auto instance) will log create, and also change new session if triggerabel zone changes.

soem how this all works out, and jstu looking at the options screen, for many wil understnd the forst three to soem degree intuitively.

XML got clipped:
< instance >
< id >123456< /id >
< name >Naxxramus< /name >
< reset >123456< /reset >
< difficulty >2< /difficulty >
< /instance >

Most important thing here is that difficulty > 1 is a 25 man raid instance. Yes I added something to the format, ill proly get flamed hard, but... It shouldnt hurt anyting. And some web dev soemwher in each of these places wil probably be happy to have this option. This was placed in all three formats, starting with 2.1.30 both session and events wil have this marked on them in the db, and wil output this in the export strings. If you had an id recorded or reset time, it wil be moved to this structure in the db, and any furture events or sessions will have all 4 values always.

Ok i did something to fix an issue i relaize all of the sites will have. Please use this, dont make users edit names in xml.

From the 2.1.30 release notes:

- added new record for export XML for all formats
added on both events and root of session
it is assumed that this root one is true for all entries
unless otherwise marked, although it is intended that
each event be marked separately
regardless of format, old conventions or otherwise, this tag
primary driver was to allow dkp sites ability to distinguish
10/25 man runs without having to contort things or lose automation
guarantees:
* all items are matched, they belong together
* neutral enUS instance name
* instance id is of the zone marked at same level if any

<instance>
<id>123456</id>
<name>Molten Core</name>
<reset>123456</reset>
<difficulty>2/difficulty>
</instance>

2.1.29 is out, im chasing down random things in hopes of makign my side as clean as possible, nothing ive fixed or found really explains this on my side. Do you have a working xml that you KNOW works form some where? And oen example of one that doesnt?

Send me your DB, celess22 at gmail dot com

I'll look at it. I actualy went to the siteand made a guild and tested it. I'm having issues too. The format is exactly the same as the plugin they recommend which is a bit outdated now. So the format is already in there. I'm not sure what they changed ot forgot, if its mine il be happy to fix it.