You want to see the lines like You say, Zojak...

Just uncheck filter spellcasting in Mag-tools and that will not hide the you say zojack type lines.

If I understand it correctly though, you want to filter out spell casting messages from others but keep your own.

Paste some lines that you want hidden and want to see, etc.. I'm not very familiar with /filter -spellcasting.

Right now Mag-Tools would filter both of these out:

Joeblow says, "Zojak Quaguz" ---> Someone else casting a spell

You say, "Zojak Quaguz" ---> Me casting a spell

If I use /filter -spellcasting it filters out the first one but leaves the second one alone. That's the desired behavior for me. I like using Mag-Tools' filtering because it lets me still see Aetheria surges on other people, which /filter -spellcasting filters out.

The ideal situation would be to have two spellcasting filter options, "Filter My Spellcasting" and "Filter Others' Spellcasting." The first one would filter out ONLY my words where the second would filter out ONLY other people's. People that want it to work exactly as the plugin does today would check both boxes.

Does that make sense?

Yea, I can do that no prob.

BTW, can you explain to me why you want to see those cryptic words? Do you have them memorized? I don't get it...

Well, I do have most of them memorized, but the main reason is that it tells me what spell I'm currently casting. It sounds silly, but sometimes I hit the wrong button (like pressing 3 for stamina to mana instead of 4 for revitalize self), and I need to then adjust my intended casting order to reflect that. I may not be explaining very well, but with the words filtered out I am much less responsive when playing my mages. Knowing exactly what spell you are casting at any given moment is very important information for a mage, in my opinion, especially when spells take more than 3s to cast.

thanks for this plugin, i've been using it about a week now and really like the parts i am using. I am a stats junky so i love the combat tracker....

A few things to perhaps help it get a bit more accurate, or just easier to figure out what is the best weapon to use....

I'll give an example.

I have a blunt 2h that has an average/max damage of 322/462 during a short test run against olthoi rippers.
I have the olthoi slayer which has an avg/max damage of 273/446.

So that would lead me to think the blunt is better, BUT...

The blunt i crit with 10% of the time and the slayer i crit 20.7% of the time.

crits with blunt: 696/696

With slayer 784/1070

This also doesn't take into account the spell surge of the slayer weapon which just in observation seems to be just under 100 points of damage per shot. I can't tell if it is hitting multiple critters per proc tho and that damage doesn't seem to be tracked.

So my request would be as follows.

1) add the olthoi slayer surge/proc to the tracking.
2) include damage tracking from both cloak and aetheria surges.
3) have a total per weapon tracking, so add all the different damage types up and output a total average to get a true sense of what setup is actually best instead of just what seems best.

Thanks for a really cool plugin. Maybe one day this weekend I can take the time to figure out how to do the auto vendor selling.

i just took the total damage and divided by the total attacks and came up with the slayer being about 20 points per attack better. So I guess it isn't too hard to kinda figure out without these changes, but hey, it would be nice anyway

It is definitely broken due to the changes; however I managed to make a little work around using the following Rule.

ObjectClass = Salvage
UsesRemaining != 100 // Optional this just sells partial bags
SalvageWorkmanship <=9.9 // Optional. Salvages everything but Wms 10
Material == 60 (Gold)
Material == 63 (Silver) // Need a Material line for each type you want to sell.

Alternatively, you could do "Material !=" and sell everything but the materials you list.

Hope this helps,

Laieda

1. I just tested. The tracker does track the surge spells of the PoQ weapons.

2. This ones a little more tricky. I thought about doing this but its tough to know exactly when you're suring, what surges you have running, etc.. It's not impossible, but pragmatically it requires a bit more work. Simply detecting a surge of a cloak/aetheria is much simpler. My advice is if you want to test specific damage #'s and ranges, dequip your aetheria/cloak. That's what I do during my testing.

3. It's basically the same as #2. This is the reason I added the current session stats and the persistent stats (I just noticed I spelled persistent wrong on the tab).. There is a clear button on Combat Tracker->Options that you can use to clear the persistent stats. You can test weapon A, write down your #'s, then clear the stats and test weapon B.

If you want to know if a weapon that has an offensive spell on it (like a PoQ) out damages a standard weapon you'll need to setup your own timed test. Set yourself up and let the macro run for 100 Killing Blows. Write down your avg normal/crit %/avg crit. Clear the current session and do the same with a new weapon.


Testing loot gen weapons against each other is a lot easier than loot vs quest or quest vs quest. Quest weapons do not all crit at 10% or 50% (CS).

For example, here are the results of some of my testing:
Upgraded Ultimate Singualarity Wand, ~18K attacks, 30% crit
Upgraded Ultimate Singularity Sword, ~44K attacks, 25.1% crit

Soulbound Staff, ~25K attacks, 14.6% crit

Red Rune Sword, ~82K attacks, 15.1% crit

PoQ Wand, ~34K attacks, 24.9% crit
PoQ Sword, ~12K attacks, 22.6% crit

Bloodscorch Sword, ~85K attacks, 23.8% crit

As you can see, my sample sizes were rather large. I would let the macro run next to a pyreal target druge for a day or so. Even so, I doubt turbine made the bloodschorch crit % 23.8, or 22.6 for the PoQ sword. But, those #'s are probably very close to the real #'s.

The point is, once you have a weapons crit % you can do some very quick testing to determine a weapons effectiveness vs another.


Remove your surge of destruction aetheria.
Buff both weapons equally.
Attack the monster with the weapon.
* Give it at least 20 attacks if you're a melee. This should be enough to get a close enough average non-crit # and the crit # (constant for melee attacks).
* If you're a mage you may want to give it a little more to get a more accurate crit #.
Do the math with your average non crit, crit %, and average crit #'s to determine your average damage output.







I did post a fixed profile.

1.0.8.5:
Fixed spelling mistake.
Changed the way instantiated objects reference VTClassic.dll. You should no longer have to copy VTClassic.dll to the same folder as MagTools.dll
If you have previously copied VTClassic.dll to the same folder you placed MagTools.dll in, I recommend you delete the copied VTClassic.dll. It is possible that MagTools might load your copied VTClassic.dll preventing Virindi Tank from loading any updated VTClassic.dll's you might receive.
Broke down Filters.SpellCasting into SpellCasting - Mine and SpellCasting - Others


This is pretty important:
If you have previously copied VTClassic.dll to the same folder you placed MagTools.dll in, I recommend you delete the copied VTClassic.dll. It is possible that MagTools might load your copied VTClassic.dll preventing Virindi Tank from loading any updated VTClassic.dll's you might receive.

I'm about to post a modified classic looter that adds some really great stuff. If you don't update your MagTools.dll and delete the copied vtclassic.dll, you may be stuck with an old vtclassic.dll and not even know it.

What happens is MagTools might load VTClassic.dll (the one you copied over) before Virindi Tank has a chance to load an updated/newer version. If this happens, Virindi Tank might just use the one MagTools has loaded, which would be the out dated copied one.

Mag-nus,

To which profile are you referring? I have the latest one off the documentation page, and I didn't see one on here. I'm probably overlooking it, or misunderstanding something.

The profile on the documentation page sells every piece of salvage in your inventory, which maybe what you intended. In which case I retract my previous statement about it being broke as it does work given that criteria. The profile I posted lets you control what is sold a little better. In either case, great program! I was fixing to code an auto sell feature to do much the same thing, but you saved me a lot of coding.


Thanks,

Laieda