That isn't intended, it will be super easy to get that bug fixed.
-
You've discovered RedGuides, an EverQuest multi-boxing and scripting community 🧙♀️⚙️. We want you to play several EQ characters at once, come join us and say hello! 👋
Resource icon
Release MQ2AutoLoot
- Thread starter plure
- Start date
That isn't intended, it will be super easy to get that bug fixed.
Is there a way to flag not to loot something if you already have a specific item? E.g. don't loot amorphous cohort helm if you have Cohorts Legionnaire Helm? Or would that rely on you setting up the advanced loot on that character manually to ignore those items?
There is no way directly with just mq2autoloot to accomplish this. You could use advloot filters to set amorphous cohort helm to never on the character that you don't want to loot it and mq2autoloot will never deal with that item on that person.
Sum1
Warriors are inferior (read: crybaby) tanks
- Joined
- Jul 30, 2006
- RedCents
- 6,302¢
There's syntax to send items to only certain classes of characters, though, right? I know that's not precisely what @vsab wanted, but it's a step in the right direction, I'd say.
Redbot updated MQ2AutoLoot with a new update entry:
initializing
Read the rest of this update entry...
initializing
Read the rest of this update entry...
Redbot updated MQ2AutoLoot with a new update entry:
new loot messages
Read the rest of this update entry...
new loot messages
Read the rest of this update entry...
Sum1
Warriors are inferior (read: crybaby) tanks
- Joined
- Jul 30, 2006
- RedCents
- 6,302¢
I was before the last patch, as well. The worst part is the spam locks up the toon, so in my case my chanter would do it all the time and wouldn’t be mezzing or anything until I cleared the loot window.
I’d have to confirm if it’s happening still after yesterday’s patch.
Sum1
Warriors are inferior (read: crybaby) tanks
- Joined
- Jul 30, 2006
- RedCents
- 6,302¢
What does that actually do? I’ve never messed with spamloot.
Silverspaceman
Seasoned veteran member
- Joined
- Jul 9, 2018
- RedCents
- 758¢
I apologize ahead of time if this is a dumb problem/question, but I have run into a wall with the plugin. Based on your original post and Maskoi's guide, I set up [...]\MQ2\release\macros\loot.ini with new drops from a camp, basically aiming for the exact same goal Maskoi was in his guide: distributing EOK T1 armor. With those being uncommon drops, I added a common item to the loot list as a test, for example:
Armor=Gear|Classes|CLR|MAG|NumberToLoot|1|
Common Item=Gear|Classes|MAG|NumberToLoot|1|
At camp, I turn autoloot on for each character and made sure each instance was pointed to [...]\MQ2\release\macros\loot.ini, tank set to ML, and double checked advloot is on. The zone is new, so no one has any settings in advloot for the actual loot drops.
Upon killing the named, my expectation was to see ML assign CommonItem to my MAG and see MAG loot it.
What I saw was my ML assign CommonItem to a different class. That class ignored the loot, leaving it on my corpse to rot. The subsequent drop for this item followed the same sequence of events.
For trouble shooting, I:
Double checked the loot.ini file path
I then made a copy of loot.ini and changed the =Gear| lines to =KEEP then pointed the plugin on my non-ML characters to that file, [...]\MQ2\release\macros\loot_copy.ini. My logic was that if the ML used the =Gear| tag and the looters had the =Keep tag, it would be assigned to the right person, then looted.
Again when the named dropped, my ML assigned CommonItem to the class that wasn't even in the =Gear|Classes| tag and that character completely ignored the item.
The only macro I load with MQ2 is KA11 and the only plugin I load is MQ2AutoLoot. I am really at a loss for these behaviors. Any direction or thoughts you can provide would be appreciated!
Armor=Gear|Classes|CLR|MAG|NumberToLoot|1|
Common Item=Gear|Classes|MAG|NumberToLoot|1|
At camp, I turn autoloot on for each character and made sure each instance was pointed to [...]\MQ2\release\macros\loot.ini, tank set to ML, and double checked advloot is on. The zone is new, so no one has any settings in advloot for the actual loot drops.
Upon killing the named, my expectation was to see ML assign CommonItem to my MAG and see MAG loot it.
What I saw was my ML assign CommonItem to a different class. That class ignored the loot, leaving it on my corpse to rot. The subsequent drop for this item followed the same sequence of events.
For trouble shooting, I:
Double checked the loot.ini file path
I then made a copy of loot.ini and changed the =Gear| lines to =KEEP then pointed the plugin on my non-ML characters to that file, [...]\MQ2\release\macros\loot_copy.ini. My logic was that if the ML used the =Gear| tag and the looters had the =Keep tag, it would be assigned to the right person, then looted.
Again when the named dropped, my ML assigned CommonItem to the class that wasn't even in the =Gear|Classes| tag and that character completely ignored the item.
The only macro I load with MQ2 is KA11 and the only plugin I load is MQ2AutoLoot. I am really at a loss for these behaviors. Any direction or thoughts you can provide would be appreciated!
Last edited:
Silverspaceman
Seasoned veteran member
- Joined
- Jul 9, 2018
- RedCents
- 758¢
Thanks for the quick response, Plure - the advloot loot screen comes up as it normally would with the green check and red x options to accept or reject looting, but no boxes are checked for need, greed, never, etc.
Once I get home later tonight, I could post additional details if I notice any.
Also, did you play on Cazic Thule in the guild, Second Age back in the early 2000s?
Once I get home later tonight, I could post additional details if I notice any.
Also, did you play on Cazic Thule in the guild, Second Age back in the early 2000s?
Last edited:
I did play on CT before I transfered to Povar and this was my orginal character's name back then. I couldn't tell you the name of the guild though.
Make sure mq2autoloot is loaded and turned on for that character using:
/autoloot turn on
It really sounds like the plugin isn't being used on that character.
Make sure mq2autoloot is loaded and turned on for that character using:
/autoloot turn on
It really sounds like the plugin isn't being used on that character.
Silverspaceman
Seasoned veteran member
- Joined
- Jul 9, 2018
- RedCents
- 758¢
I've got a hotkey for turning on KA and autoloot through EQBC on all my characters, including /bca //autoloot turn on; I think I will try a fresh KA installation with my existing ini files.
Silverspaceman
Seasoned veteran member
- Joined
- Jul 9, 2018
- RedCents
- 758¢
This weekend, I uninstalled and reinstalled MQ2 VV, starting over from scratch with the exception of my ML's loot.ini and my KA ini files. Aside from running KA, EQBC, and MQ2nav, I did not start any other plugins or macros. ML is assigned to my active character (tank) and Use Advanced Looting is checked on all characters' /advloot Loot Settings. No item boxes are checked for drops (e.g. AN AG NV, etc.). Loot is turned off in all of my KA inis. Here are a few relevant settings:
C:\MQ2\Release\Macros\Loot.ini
C:\MQ2\Release\MQ2AutoLoot.ini
Autoloot commands used:
It started off looking like everything worked out, with the ML assigning the first "Common Item" drop to MAG & MAG looting it!
My expectation was for the next "Common Item" drop to be left on corpse without matches in the gear assignment and class AND count effectively making it =ignore.
The next "Common Item" drop was assigned by ML to BST. Similarly, later in my session, ML assigned Armor to MAG despite his class not being listed in the =gear tag. ML has no issue assigning to himself and looting things like diamonds and trade skill items and happily hoards it all.
The problem I am left with is that ML is assigning gear to characters whose classes are not part of the =gear| tag or not reading the =gear| tag. At this point, I am assuming I have messed something up and need to just figure out what it is, not expecting that anyone would know what I need to fix unless the behavior jumps out as familiar. Will keep reading and playing around to try to fix stuff.
Double checked all /advloot settings; embarrassingly, I had previously left the Use Advanced Looting option unchecked on the BST, accounting, I believe, for him not acting on loot assigned to him. In fact, based on page 8, this simple error may have led to the other aberrant behavior I have seen.
Tested using different loot.ini for my looters where I copied loot.ini and replaced instances of =gear with =keep. Verified that all /advloot loot settings on each character agreed with Plure's screenshot on page 7. ML is still sending loot to someone whose class is not listed on the gear at all. It is like ML is ignoring the settings in his loot.ini file for loot rules.
I changed everyone back to using the same loot.ini file. My ML is now distributing loot as I would expect (one character has picked up all of the Amorphous gear now) with the drop of "Common Item" passed to all characters, then left on the corpse with each ML message showing something like the character said no or already has this item, going through the full group before being left.
So now everything appears to be working fine! It's been a week and everyone has picked up their armor with duplicates left on corpses.
C:\MQ2\Release\Macros\Loot.ini
Armor=Gear|Classes|CLR|NumberToLoot|1| --- this is the EoK T1 armor that I want distributed to 4 of my 6 characters
Common Item=Gear|Classes|MAG|NumberToLoot|1|
C:\MQ2\Release\MQ2AutoLoot.ini
["MLname"]
lootini=C:\MQ2\Release\Macros\Loot.ini
UseAutoLoot=1
["MAGname"]
lootini=C:\MQ2\Release\Macros\Loot.ini
UseAutoLoot=1
["BSTname"]
lootini=C:\MQ2\Release\Macros\Loot.ini
UseAutoLoot=1
["CLRname"]
lootini=C:\MQ2\Release\Macros\Loot.ini
UseAutoLoot=1
Autoloot commands used:
/bcaa //plugin mq2autoloot
/bcaa //autoloot turn on
It started off looking like everything worked out, with the ML assigning the first "Common Item" drop to MAG & MAG looting it!
My expectation was for the next "Common Item" drop to be left on corpse without matches in the gear assignment and class AND count effectively making it =ignore.
The next "Common Item" drop was assigned by ML to BST. Similarly, later in my session, ML assigned Armor to MAG despite his class not being listed in the =gear tag. ML has no issue assigning to himself and looting things like diamonds and trade skill items and happily hoards it all.
The problem I am left with is that ML is assigning gear to characters whose classes are not part of the =gear| tag or not reading the =gear| tag. At this point, I am assuming I have messed something up and need to just figure out what it is, not expecting that anyone would know what I need to fix unless the behavior jumps out as familiar. Will keep reading and playing around to try to fix stuff.
--edit for user errors and other data--
Double checked all /advloot settings; embarrassingly, I had previously left the Use Advanced Looting option unchecked on the BST, accounting, I believe, for him not acting on loot assigned to him. In fact, based on page 8, this simple error may have led to the other aberrant behavior I have seen.
Tested using different loot.ini for my looters where I copied loot.ini and replaced instances of =gear with =keep. Verified that all /advloot loot settings on each character agreed with Plure's screenshot on page 7. ML is still sending loot to someone whose class is not listed on the gear at all. It is like ML is ignoring the settings in his loot.ini file for loot rules.
I changed everyone back to using the same loot.ini file. My ML is now distributing loot as I would expect (one character has picked up all of the Amorphous gear now) with the drop of "Common Item" passed to all characters, then left on the corpse with each ML message showing something like the character said no or already has this item, going through the full group before being left.
So now everything appears to be working fine! It's been a week and everyone has picked up their armor with duplicates left on corpses.
Last edited:
It is working as intended if I read your post correctly.
The logic flow how how the plugin works goes like this.
1. The ML looks up an item out of loot.ini file, he then decides if he wants it or not.
2. If he doesn't want and it isn't marked as ignored/destroyed he is then going to pass out the loot.
3. He cycles through your group/raid attempting to pass out the item, till he succeeds or reaches the end of his list.
I didn't want to write a separate bit of logic for passing out items marked as gear, so I left that logic the same no matter what the item was marked, ie sell/quest/keep/gear/etc. It simplifies the code and also doesn't break anything if people are using two separate loot.ini files.
There is one flaw in the logic. The game treats items marked as greed/need/not marked for anything, the same when trying to pass out loot. Which is why when passing out loot, it really is necessary for everyone in the group to be using the plugin. or super active on clicking need/greed/etc.
The logic flow how how the plugin works goes like this.
1. The ML looks up an item out of loot.ini file, he then decides if he wants it or not.
2. If he doesn't want and it isn't marked as ignored/destroyed he is then going to pass out the loot.
3. He cycles through your group/raid attempting to pass out the item, till he succeeds or reaches the end of his list.
I didn't want to write a separate bit of logic for passing out items marked as gear, so I left that logic the same no matter what the item was marked, ie sell/quest/keep/gear/etc. It simplifies the code and also doesn't break anything if people are using two separate loot.ini files.
There is one flaw in the logic. The game treats items marked as greed/need/not marked for anything, the same when trying to pass out loot. Which is why when passing out loot, it really is necessary for everyone in the group to be using the plugin. or super active on clicking need/greed/etc.
I have just come back from a break. previously autoloot was working flawlessly and now it will not read or write to the ini, when it comes to looting it spams the message "The item is not in the database, setting it to Quest|10" even though quest is set to 1.
I have reinstalled MQ2. deleted ini files, rebooted computer. looting is set to 0 in kiss ini's, since i haven't changed anything since the last time i played at fabled time im wondering if there is something im missing.
I have reinstalled MQ2. deleted ini files, rebooted computer. looting is set to 0 in kiss ini's, since i haven't changed anything since the last time i played at fabled time im wondering if there is something im missing.
Sorry to be a pain. the ML is now handing out loot properly, but everyone is leaving it all on the corpse.
i have checked that looton=0 in kiss and that autoloot is turned on and pointed to the correct location for all toons, i also play on test if that makes a difference.
oh it is also spamming Slist: Setting to no.
i have checked that looton=0 in kiss and that autoloot is turned on and pointed to the correct location for all toons, i also play on test if that makes a difference.
oh it is also spamming Slist: Setting to no.
Sum1
Warriors are inferior (read: crybaby) tanks
- Joined
- Jul 30, 2006
- RedCents
- 6,302¢
Make sure the in-game eq advanced loot settings are all cleared out. If you have anything pre-set in there it messes up mq2autoloot.
Your ML is working like you would expect, but everyone else is just clicking no on every item?
few times now ive found Rares sitting on corpses in my camp. autoloot not looting things I don't have slected need/greed whatever just leaving on corpses? any fix for this
i do see in the log where it does try and hand out loot for other items.. but was sitting here looking at the log and a XXX rare rotted basically at some point.
Edit. now that I got it working correctly) god only knows what i havent noticed rotting)>!
i do see in the log where it does try and hand out loot for other items.. but was sitting here looking at the log and a XXX rare rotted basically at some point.
Edit. now that I got it working correctly) god only knows what i havent noticed rotting)>!
Last edited:
Sum1
Warriors are inferior (read: crybaby) tanks
- Joined
- Jul 30, 2006
- RedCents
- 6,302¢
do you have multiple looters designated via the Raid tool? If you don't modify the looters on the raid tool, the only person who can loot (by default) is the raid leader. This is independent of MQ2autoloot.
I used raid loot option 3 which assigned rl and group leader to be the looter. Each group leader can loot manually but it appears only the leader of the raid will auto loot. I believe plure already answered this question stating that it's a limitation of the plugin. I think that message got removed during site's upgrade.
Plure.
I am having a problem getting MQ2Autoloot to loot Cliff Stones on my Warrior. He is not the masterlooter. The end result is that the Cliff Stone stays on the corpse.
He has 1 Cliff Stone equipped and 12 in inventory.
All other loot is being distributed according to the setting in the Loot.ini file.
All the characters use KissAssist and their LootOn=0 (so that NinjaLoot.inc is not being used and potentially conflicting)
No filters are set, and all their AN_xxx, AG_xxx files are empty.
I have this entry in my loot.ini file. The file is sorted and there isn't a duplicate entry for it.
All may characters have MQ2Autoloot turned on and refer to the same Loot.ini file. This is how the loot.log file looks as it tries to distribute
I don't understand why my WIZ is nominated in last row above (My RNG is position1 and WIZ is position2 in group)
I was suspicious that it was an integer problem (too big), but I set another drop for the warrior to loot 25 of them and Autoloot successfully distributes them to him.
My Loot.ini setting are
Any thoughts ?
Thanks in advance,
Hylander
I am having a problem getting MQ2Autoloot to loot Cliff Stones on my Warrior. He is not the masterlooter. The end result is that the Cliff Stone stays on the corpse.
He has 1 Cliff Stone equipped and 12 in inventory.
All other loot is being distributed according to the setting in the Loot.ini file.
All the characters use KissAssist and their LootOn=0 (so that NinjaLoot.inc is not being used and potentially conflicting)
No filters are set, and all their AN_xxx, AG_xxx files are empty.
I have this entry in my loot.ini file. The file is sorted and there isn't a duplicate entry for it.
All may characters have MQ2Autoloot turned on and refer to the same Loot.ini file. This is how the loot.log file looks as it tries to distribute
I don't understand why my WIZ is nominated in last row above (My RNG is position1 and WIZ is position2 in group)
I was suspicious that it was an integer problem (too big), but I set another drop for the warrior to loot 25 of them and Autoloot successfully distributes them to him.
My Loot.ini setting are
Any thoughts ?
Thanks in advance,
Hylander
Last edited:
@Hylander
From your log file it appears that ranger gave everyone 5 seconds to select an action before attempting to pass out. Everyone selected no, till he reached your wizard (which for some unknown reason hasn't selected no). Once it went to your wizard's person loot list he then realized he didn't want it and then elected to leave it on the corpse.
There are a number of checks your warrior could have failed that would have caused him to select no instead of need/greed.
1. Do you have any cliff stones in your bank's inventory?
2. An item on your cursor will cause the plugin to select no for all of the items in the loot window
3. How many bag slots do you have left? If it is less then 3 they would select no
Assuming those all happen to be no. If you trade a couple away to someone in your group, does he start wanting to loot cliff stones again? I've looked over the code for counting the number of items and I don't see any obvious bugs, but this wouldn't be the first time something has sneaked past me.
The wizard I am just not sure wtf is going on with. If you pause the plugin on your ML and go to your wizard's screen are they checking need/greed or no for all of the items?
From your log file it appears that ranger gave everyone 5 seconds to select an action before attempting to pass out. Everyone selected no, till he reached your wizard (which for some unknown reason hasn't selected no). Once it went to your wizard's person loot list he then realized he didn't want it and then elected to leave it on the corpse.
There are a number of checks your warrior could have failed that would have caused him to select no instead of need/greed.
1. Do you have any cliff stones in your bank's inventory?
2. An item on your cursor will cause the plugin to select no for all of the items in the loot window
3. How many bag slots do you have left? If it is less then 3 they would select no
Assuming those all happen to be no. If you trade a couple away to someone in your group, does he start wanting to loot cliff stones again? I've looked over the code for counting the number of items and I don't see any obvious bugs, but this wouldn't be the first time something has sneaked past me.
The wizard I am just not sure wtf is going on with. If you pause the plugin on your ML and go to your wizard's screen are they checking need/greed or no for all of the items?
@plure
Thank you
1. No, all Cliff Stones are either in inventory on character or equipped. Definitely None in Bank, House, parcels etc
2. item on cursor could happen, from time to time he summons some food, but that'd be the rarity
3. plenty of bag space, so that is not an issue
Will try the the following
(a) watch the distribution and see what he selects
(b) check settings on other power sources and see if other chars and other PowerSources behave similarly
Thought - could it be checking against the no-drop default =Quest|5 ? and thinking "i've got more than 5" and then move onto next character?
It shouldn't be checking that unless for some reason it can't look up the item in your loot.ini file. I was also assuming all of your toons are using the same loot.ini file?
