Guys, I will likely be puting out a new update for the February patch.

The current STOCK classic looter as well as my MODIFIED versions will work in February REGARDLESS of what the dev team does. Virindi was clever enough to make it very open and configurable.

My update will just include the GUI fixes for the weapon class lists.

But, If you guys want me to add any other features or requirements, now is the time to request them. I only want to update my classic looter every once in a great while. The reason being any NEW requirements I may develop would not be backwards compatable, thus, I want to avoid a bunch of users on different versions of my modified looter.

HEHE, oookay, you asked for it! Muuhhaahhaa!! Here it comes: LoL


Feature Request: How about enhancing (or replicating) the 4 color matching requirements with some "Not=" options? =)

“One Similar Color”

“Armor Type Similar Color”

“Slot Similar Color”

“Slot Exact Palette”

My guess is you’d have to make a copy of each requirement that looks for a match using the same exact logic, but then aborts the processing of that rule so the item doesn’t get looted. But you’re the programmer not me! =)


Feature Request: Another color based enhancement I saw someone else wanting is a "All Color Slots = Color" requirement. I can only guess it's for colors/shades not obtainable from dye, and they want the trim the same.


Feature Request: Have the VTCL Window remember where I put it and how I resized it every time I close/open it. I love that I can resize it now. Thank You!, but I use your Mag-Tools feature to auto move my AC Client Window on logon, so I always move the VTCL window to the same exact place next to the AC Client every time I launch it. It would be nice if VTCL automatically went to the same place and size of my choosing every launch. =)


Feature Request: Can you give us a "OR" Requirement Group - Adding this to a rule actually puts 2 lines in, "Begin Or Group" and "End Or Group". All requirements added (using the Ctrl+Add method) between these two lines *OR* with each other. Only 1 of the requirements has to be True for the processing of that rule to continue. If none of the “OR” requirements are True, the entire rule is aborted. =)


Feature Request: A new rule type just like "Keep #". But this one goes a step further: "Keep # & Disable Looting" rule type. Once the # has been met, looting turns itself off. My idea is for questing. Example is Paradox Touched Olthoi Queen. Everybody needs 1 gland to do this quest. The gland is obtainable on the way down. Don't want to fall behind by looting everything during a quest, especially when dragging alts along that also need just 1 gland.


Feature Request: A method to specify what monsters to loot. This is a further refinement of #2 above. Only certain mobs drop glands, so only looting those corpses would further reduce the delays caused by looting during a quest, especially when dragging alts along.


Feature Request: Maximize Main Chat Window automatically every logon...

Opening Main Inventory and Maximizing Chat are the first 2 things I do every time I log in. Even on my mules. I just started letting your Mag-Tools open inventory for me and am LOVING IT!!! Thank you!


Hehe, hope you haven’t passed out from thinking about all the coding involved here! =)

-Picaro

Feature Request: A new rule type that executed a chat command when it's requirements proved true.

Loot a perfect sword --> "/think You lucky SOB, you just looted a perfect Sword!"


Hehe!!

Oops, I just realized I've been saying something wrong:


When I ask for a new rule "Type" what I mean is "Action".


And now that i'm looking at the list of available Actions, I have another request...


Feature Request: A new rule Action "Salvage #", works same as Salvage, but it stops after obtaining # of full bags of that material type.

Hmm.. I can really do a lot of things with classic looter.

I'm not sure about using classic looter to send the client messages though, I'll have to look into it.

It'd be really good if everyone put their wish lists for classic looter in here so I could just do one release. Like I mentioned before, it's not good if there are others running different versions of classic looter. I don't change the version # as i dont want to break virindis update process, and as such it's hard to determine which one the users are actually using if I release multiple builds.

PS. V has expressed interest in merging my code into her pub release, which would make sharing these enhanced profiles SO much easier for the alinco converts.

Thanks Mag-nus!
I'd love to see an option for including "or" in a salvage rule. Such as material type 1 or 12 or 64 etc. I just hate having so many salvage rules for so many materials...

FYI: The "OR Group" method I mentioned above would work with anything (even salvage). No need to make any special salvage specific "OR" features.


just trying to help trim down the workload.


-Picaro

How about sound alerts can set for when get hits. Maybe half dozen or so, to be able to set a few specific ones for particular rules and a general one for multiple hits. Be nice if could turn on/off ig also.

SL

Any type of alerts would have to be done with a combo of plugins.

IE: In Classic Looter, you define the rule as "Alert X", and then in Mag-Tools for instance, you would enable alerts.

Classic looter has a very simple responsibility, to validate loot, nothing more. It can however validate loot with information that the requester of validation can use.