SW Stats 2.0 Timeline Sneak Peak

[Artack]

Here is some info on the 2.0 Timeline and datasegments and their implications.

http://www.sw-stats.com/timline.jpg

Items marked in green are currently being used to calculate data.
Items marked in red are currently selected.
Items marked in orange are selected and are currently being used to calculate data.
To delete segments press the “X” button. You cannot delete the active data segment (the last one). Once you have deleted a segment there is no way back! So make sure that’s what you want to do.
To rename segments press the “R” button. To accept the rename press enter or click the “R” button again. If you rename the active segment (the last one) and it contains no data it might be renamed automatically.

Merging: Once you have merged a range of segments there is no way back! So make sure that’s what you want to do. You CAN merge the active segment with previous segments, but data currently being collected will be added to the merged segment. (Essentially it will be the new active segment).
After merging data the only segment to calculate data will be the active segment. Re-select whatever data you want to display.

Selecting segments to calculate data:
If you only select the active segment (the last one) SW Stats 2.0 will behave very much like SW Stats 1.x versions, although if you reset data it isn’t lost like in 1.x. In 2.0 a new data segment is created and then is automatically the active segment.
If you select a range that doesn’t include the active segment the data displayed is “static” (Nothing is being added to old data segments). If you select a range including the active segment you have something like an “auto end marker”. Even if you reset to create a new segment the data will keep counting up but will be separated in different data segments.

This stuff eats memory, here is why:
These are ONLY the BASIC infos of a unit:
"Damage",
"Heal",
"Deaths",
"DecurseCount",
"TotalDmgTicks",
"OverHeal",
"HealInFight",
"OverHealInFight",
"DOTTicks",
"DOTDmg",
"TotalFightTime",

A unit will have some of these entries double, one for done and one for received.
To keep it simple the basic unit data is lets say 20 integers. That in itself isn’t so bad but now every time you create a new segment you create another 20 integers (and the table containing them). You see where this is going. Above the basic data there is also school data with resist info, skill with resist, crushing glancing etc info. (also, on a done and received basis) and more.

So.
Either /sws nuke after your done looking at the numbers (this deletes everything collected) or merge the entire raid data into one data segment. This is still a ton of data but a lot less then lets say keeping 15 segments alive. (Which in our previous example, would have held 300 integers for just one person instead of 20)
Of course it’s not quite as simple as this, there is more going on but that’s the gist of it.

This might sound really bad, but if you nuke your data every 1 or 2 raids SW Stats 2.0 will still use less memory then “DB addons” like loot link or enchantrix etc.
If you don’t – well it will eat your script memory for breakfast.
I’m still debating if I should add some warning “Dude delete the stuff, it’s getting out of hand”.

One thing I am really not sure how to handle in 2.0 are the reporting functions. Everybody can reset his/her data at their own leisure and Sync still works. Everybody can select whatever segments he wishes. Posting one certain data view gets rather pointless.
(Hey I made 5 billion damage – but I didn’t /sws nuke in ages and this is the data from 3 weeks)

[edit]

As a further explanation of the data segments:
It’s like you would "Save" data in other add-ons, just that a save happens automatically when you reset, zone, join a group/raid and leave a group/raid. I do not have a "last fight" thing though, imho it's to much overhead for the info given. The only real interesting last fight info is on bosses.. and you guys reset on those anyways.
These automatic saves will be extended in the future (2.2 +) to handle boss fights without the need to reset manually.

[Darclite]

Sounds pretty good can't wait for it. Keep the good work!

[mok]

i love you ^^

[LouTheKiller]

I suggest you just remove reporting in SWS2, this will 'force' people to install the addon if they want stats and speed development.

[Ilyd]

It would be great if you could actually have more segments active at one time. f.e. you could have a segment for a whole raidnight (AQ40 clear and stuff) then a segment for each bossfight.
Like:
Segment 1: WholeNight (gets not resetted, is active the whole night)
Segment 2: BossFight1 (is active while Skeram)
Then, after Skeram, you create a Segment 3, so the Trashmob before Sartura doesn't fake the Skeram-Segment. So you get to Sartura and create a:
Segment 3: BossFight2 (is active while Sartura)
and delete the TrashmobsAfterSkeram-Segment. And so on.
So in the end of the whole raidnight you'd have a segment for all fights (bosses & trashmobs, together) and several fragements for each bossfight. And then, the night after, you just /sws nuke it and begin again (naxx spiderwing-clear f.e)

[Artack]

I implemented the ability to merge non consecutive data segements, to do the stuff you described Ilyd. (It wasn't in when i did the Sneak Peak).
Atm it's a little bit click intensive, but you can do it.
Things like "special boss segments" that automates some of this will have to wait somewhat.

[LouTheKiller]

[Artack]

[LouTheKiller]

[Artack]

[GuaRRand]

ETA on it?
I know it'll be done when its done and all that, but since both SWstats and Damagemeter are not up to date..... i neeeed my stats!!

[mok]

it would be nice to quickly hack some code to use SendAddOnMessage(), until version 2.0 is up and running

[Vill]

[dafire]

No.. don't extend the spam by another 4 rows ...
I second removing reporting to party, raid and guild channel.

It's simply not necessary with a good working sync where everybody can install the mod.

I'd rather like to see some kind of xml export including the segments, I'd write a webapp for saving and displaying

[Isyn]