• 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! 👋

  • A TLP without truebox has thawed (Very Vanilla ready)
    Frostreaver
Ninjadvloot.inc

Release Ninjadvloot.inc 2022-06-23

No permission to download
It automatically adds any new item it encounters. I've copied the post with all the instructions for you to read below.
There are several options you can select to determine how (keep, ignore...) the item is added, see below for details.
I will test on FV tomorrow. Hoping to have new instruction post on Saturday, to make thing easier to read.


New file uploaded 7/8/16

Ninjadvloot.inc 6.1
Ninjadvloot 6.1 is completely compatible with kissassist 8.5 from the current compile.
NOTE: These 'improvements' only apply to the advloot system. If you are not using advloot - why the Hell not, It's great.

Advloot filters and Ninjadvloot 6.1 play together like most siblings. That is to say they get along perfectly fine most of the time. But when they fight, look out, you will suffer. Some observations to avoid fights:

The Advloot filter 'Never' overrides everything. You simple CAN NOT loot an item if advloot filter is Never. Ninjadvloot is suppose to identify the 'never' filter and deal with it, however, the MQ2 Gremlin is still reporting occasional problems. I recommend not using the advloot filter Never.

The Master Looter / ninjadvloot.inc macro overrides the advloot filters AlwaysGreed and AlwaysNeed. They don't seem to cause any problems, but if the loot.ini is set to ignore or destroy - that is what will happen regardless of other group members advloot filters. Make sure your advloot filters and loot.ini settings match or at least make sense. Don't set one to destroy and the other to AlwaysNeed.

New ini settings:

From 6.0 - QuestKeep=10.....the default number of items to keep if an item is set to Quest using the command /lootquest.
From 6.0 - StackPlatValue=50.....The stack value of new items being automatically added to the ini file that determines =Keep or =Ignore
From 6.0 - GMLSelect=1.....Group Master Looter Select has two functions, 1. it will select a Master Looter if the group does NOT already have one.
............... 2. It will select a new Master Looter if the sharedlist count increase more then 5x without a decrease.
From 6.0 - ExcludeBag1=NULL/ExcludeBag2=NULL.....allows you to exclude two special or limited item containers from your free inventory count.

NEW - LootLagDelay=0.....A hard coded delay in 1/10ths of second to compensate for lag. 5=half second, 10= one second
NEW - SpamLootInfo=1.....0/off, 1/on turns on/off informational loot spam in the MQ2 chat window.


Process changes from 6.0:

Increased the priority for quest items autoroll to avoid possible conflict with advloot filter "AlwaysNeed"

Notes worth repeating:

Ninjadvloot is compatable with kissassist 8.5 - you doNOT have to change anything, with the possible exception of your default loot.ini file
If you have a custom macro using ninjadvloot and want the new features you need to have everyone in the group check for:


Code:
(${AdvLoot.SCount}||${AdvLoot.PCount})
I also included a delay timer so they don't spam the loot check

Code:
!${LootTimer}
Here is the command I am using in my custom macro:

Code:
/if (${Me.UseAdvancedLooting} && (${AdvLoot.SCount}||${AdvLoot.PCount}) && !${LootTimer} && ${Me.CombatState.NotEqual[combat]}) /call UseAdvLoot
The GMLSelect setting will check your KissAssist_CharactorName.ini for the LootOn=0 setting. Group Members with LootOn=0 will be excluded from being selected Master Looter, they will still receive LORE and Quest items.

Finally, for those who want valueless items set to =Destroy instead of =Ignore. Send me a Private Message, prove you intelligent enough to understand what you are asking and beg. I will tell you which command to change to make that happen. I DO NOT recommend letting the macro set anything to =Destroy automatically, I tried it and was very upset when it destroyed stuff I wanted Keep.


From the 6.0 post:





| Updates by Hoosierbilly, advloot system only, May 2016
| 1. Group Leader will automatically assign a Master Looter if there is no Master Looter.
| Group Leader will replace Master Looter if shared list count increases more then three times in a row without a decrease.
| Added new setting GMLSelect=1 to ini file, 0=off, 1=on, default is on
| 2. Lore items marked Keep/Sell will automatically be distributed to everyone in the group, then left on the corpse.
| 3. Added Quest|xx to the ini file, allows all group members to autoroll for items until they have xx number of said item.
| Added new command /lootquest will set item to =Quest|default value
| Added new setting to ini file: QuestKeep=default value is 10
| Requires the following command in your macro's main loop or MQ2melee downflag



Code:
/if (${Me.UseAdvancedLooting} && (${AdvLoot.SCount}||${AdvLoot.PCount}) && !${LootTimer} && ${Me.CombatState.NotEqual[combat]}) /call UseAdvLoot
| Note: Items set to "Never" in the Master Looters advloot filters will be treated simular to Quest items without a quantity limit.
| Advloot filters AlwaysNeed/AlwaysGreed/Never will autoselect else the loot.ini settings will determine if individual group member will roll or not.
| 4. Added check for item stack platinum value when adding new items to ini file.
| Item will Keep if above selected ini value, else item will be Ignored.
| Added new setting to ini file: StackPlatValue=default value is 50
| StackSize is limited to 20.
| 5. Added free container slot check. Will automatically stop looting if container space is < 3.
| Added new setting to ini file to exclude up to two special/limited containers from free container slot check.
| example: ExcludeBag1=Extraplanar Trade Satchel
|


Here is a list of the new loot.ini file heading with the new settings colored red:



Code:
[Settings]
|================================================= =====================|
Version=6.0
AddNewSales=1
LootForage=1
LootMobs=TRUE
CorpseRadius=100
MobsTooClose=40
ReportLoot=FALSE
LootChannel=g
LootForageSpam=1
GlobalLootOn=1
CombatLooting=0
QuestKeep=10
StackPlatValue=50
GMLSelect=1
ExcludeBag1=Extraplanar Trade Satchel
ExcludeBag2=NULL


QuestKeep=10 this is the default amount the command /lootquest will update in the loot.ini file.
if you want to keep more or less you have to manually adjust the amount in the loot.ini file

StackPlatValue=50 the amount of platinum a stack must equal in value to be set to Keep instead of Ignore
StackSize is limited to a maximum of 20 items for this check
StackPlatValue=0 will turn this feature off, adding all new items as Keep, except NoDrop they are always Ignore
This only applies when new items are added to the loot.ini file

GMLSelect=1 0/off, 1/on, default is on, group leader will automatically select a Master Looter if you don't already have one and change Master Looter if shared loot list count increases more then 3x in a row without a decrease.
EDIT: Added individual group members can be exclude from being selected for Master Looter Role by using LootOn=0 in the KissAssist_charactorname.ini settings. They will however, still receive LORE items.

ExcludeBag1=Extraplanar Trade Satchel Always you to pick two containers to exclude from your Free.Inventory count.


Processing loot:
Master Looter looks at each item in the shared loot list and checks it against the loot.ini file
items set to Ignore he leaves on the corpse
items set to Keep/Sell/Destroy he moves it to his personal loot list except
LORE items set to Keep/Sell will be giveto each member of the group in turn, first to the Master Looter, then backwards down the Group.Member list
if everyone has the item it will be left on the corpse
LORE items set to Destroy will be looted and destroy or left on the corpse if Master Looter is unable to loot
items set to Quest will be flagged for autoroll and stay in the shared loot list until rolled for

Everyone checks the shared list for items set to Quest
if they need the item (have fewer than listed in the loot.ini file) they will select Greed
if they have enough of the item they will select No
An autoroll will determine who actually gets the item
if no one wants the item (everyone selects No) the Master Looter will leave the item on the corpse

Note: Items set to "Never" in the Master Looters advloot filters will be treated simular to Quest items without a quantity limit, ei set to AutoRoll
advloot filters AlwaysNeed/AlwaysGreed/Never will autoselect else the loot.ini file settings will determine if individual group member will roll or not.

Everyone processes their own personal loot list
if an item not already in the loot.ini is found:
NoDrop items are left on the corpse and added =Ignore to the loot.ini file
New items will be looted to determine the Stack Value and added to the Loot.ini file either =Keep or =Ignore
NOTE: make sure any low value tradeskill item are included in your loot.ini file as =Keep or they may well become =Ignore
then
LORE items will be left on the corpse if you can't loot it, ie. already have one
items set to Ignore will be left on corpse
items set to Quest will be checked to see how many you already have and either looted or left on the corpse
items set to Keep/Sell/Destroy will be looted, and items set to Destroy will be destroyed Damn, that's a long post.

File updated to included Maskio's fixes for global looting sub.





Quote Originally Posted by Maskoi

NinjAdvLoot
I may have added a wildcard global section to the loot.ini. DON"T USE IT!]

[Global]
|================================================= =====================|
Global1=hero's forge|Destroy
Global2=diamond|Sell
Global3=Defiant|Destroy
Global4=Item Name|Ignore/Destroy/Keep/Sell
Global5=Item Name|Ignore/Destroy/Keep/Sell[/CODE]
Just spent a while trying to understand the Global Looting sub... Maskoi is right don't use this, especially for =Destroy, it is simple too unpredictable. If you insist on wanting to this, you will have to figure out how on your own. I will NOT help or support anyone lacking the basic skill to puzzle out how to make global work.

6/11/16 - Corrected an issue with lore item distribution to group members.
Corrected an issue with lore items in your bank causing hang-ups.
6/14/16 - Corrected an error in last update.
Updated file: 6/23/16
corrected/improved several minor issues.
added selectable action for new nodrop items
added new loot.ini setting NoDropDefault=Quest|Keep|Ignore
pick how you want ninjadvloot to add nodrop items =quest, =keep, =ignore
quest is the default, if no setting is found item will be ignored and left on corpse
updated file: 6/29/16
Locked loot items should now be properly processed, no longer causing the macro to hang-up.
Locked items will be left on corpse, this will likely cause you to miss a desired item occasional.
update: 7/5/16
corrected an issue with switching master looter. I totally flubbed this one by releasing the wrong file on 6/29

update: 7/8/16
corrected an issue with adding nodrop items to the ini file.
corrected another issue with switching master looter

New file uploaded 7/8/16
 
Last edited:
Well, it depends on how you wanting to use it an with what macro. That is an include file, so it needs to be included in a macro of some sort.

I would recommend checking out this thread

if after perusing that thread you still have question, I would recommend posting your questions in that thread. It helps keeps all the questions about X thing together... to help other folks later on who may run into similar issues find out how it got resolved =)
 
File Updated: 8/31/16

DISCLAIMER: This updated inc file was coded by a community member for his personal use. It is released for use by the community as a gesture of goodwill. With enough support from the community it may be possible to add this to the redguides compile.

CREDIT: Incognito for user testing and suggesting too many improvements to recount.

IMPROVMENTS/CHANGES from ninjadvloot 5.x
Recommend reading Ninjadvloot 5.2 for basic use.


WARNING:
Attempting to use both the in-game advanced loot filters and Ninjadvloot 6.x will cause strange behavior. It is strongly recommended you ensure the following in-game advloot settings:
1. LOOT ALL is turned off in the advloot window.
2. Don't say I didn't warn you. Attempts to get both system to work together have not been entirely successful.



IMPROVMENT #1 - Automatically Select/Replace Group Master Looter
New user selectable setting: GMLSelect=1 0=off/1=on
Allows Ninjadvloot to automatically select a Group Master Looter and replace the Group Master Looter if his/her bags become full.
To exclude a group member from being selected Master Looter turn off looting (LootOn=0) in your KissAssist_CharactorName.ini file. By default all group members are selectable as Master Looter.

New loot.ini setting: ExcludeBag1=Extraplanar Trade Satchel
Exclude special/limited item bags from being counted toward available inventory slots.
Required for the proper replacement of Group Master Looter when bags become full.



IMPROVMENT #2 - Quest Looting
New item ini file setting: =Quest|xx
NOTE: This has nothing to do with the in-game item descriptions.
This setting uses the advloot autoroll feature to distribute a given number of an item marked =Quest|xx in the loot.ini file to each group member. After each group member has xx items any additional items will be ignored.
Items must by manually marked in the loot.ini file using either a text editor or the new command /lootquest.
The default number of items to be kept is user selectable with the loot.ini setting QuestKeep=10
The actual number of items to be kept can be manually adjusted (with a text editor) in the loot.ini file.
For this function to work properly every group member must check for loot items in their advloot window.
Recommend using the following command in your macro's main loop:
Rich (BB code):
/if ((${AdvLoot.SCount}||${AdvLoot.PCount}) && !${LootTimer} && ${Me.CombatState.NotEqual[combat]}) /call UseAdvLoot



IMPROVEMENT #3 - Plat Farming
New user selectable setting: StackPlatValue=0
Loots and checks the value of a stack of any NEW items being added to the loot.ini file. Stack size is limited to 20.
If item stack value is less then StackPlatValue setting, item will be marked =Ignore in the loot.ini file
WARNING: low value tradeskill and LORE items will be marked =Ignore if below the StackPlatValue setting
Because the item must be looted to check it's value, one of the item will remain in your bag
Items that can be worn (equipped) bypass this check and will be marked =Keep in the loot.ini file



ADDITIONAL NOTES:
New user selectable setting: NoDropDefault=Quest|Keep|Ignore
Determines how NoDrop/NoTrade items will be marked in the loot.ini file when encountered for the first time. The default is Quest|1

LORE items marked =Keep in the loot.ini file will be distributed to everyone in the group, when everyone has one item will be ignored.

New user selectable setting: LootLagDelay=0
Increase the setting if you have problems with lag. 5=half second, 10=one second, 20=two seconds...

New user selectable setting: SpamLootInfo=1 0=off/1=on
Spams loot information to your MQ window

Allowing your Group Master Looter to die is NOT recommended. Locked items will be ignored, possibly leaving desirable or valuable items on corpse.



If you download and use Ninjadvloot 6.x PLEASE report your experience good or bad.

Edit: 7/17/16 - uploaded new file - added kissassist_server_charactorname.ini to the check to exclude group members being selected Master Looter

File Updated: 7/30/16 - Correct an issue in the /destroy routine.

File Updated: 8/31/16
Added feature to limit how many foraged items are kept using the =quest|xx flag. cred: Incognito
destroying items should no longer leave the bag open. cred: Incognito
looted stacks of items should be properly destroyed without destroying more than the amount looted
corrected an issue for checking items on the shared loot list, it should now check every item each loot cycle instead of occasional skipping an item
The Master Looter will flag items marked never or no to autoroll (this should help with each group member having their own ini file) cred: dreamflux

update: still having issues with nodrop lore items... troubleshooting continous
final update, I hope: corrected issue with nodrop lore items (dreamflux, this ones for you)


download the most recent version here
 
Last edited:
On behalf of geeks nerds RGers & gamahs everywhere, I salute you brother! Ninja needed an update, and your mods are greatly appreciated!

- - - Updated - - -

Note: For users that are running a mac that embeds the INC file (aka KA), it is best to issue commands to alter the ini rather than to manually edit it as making a mistake can have... aberrant results:
Rich (BB code):
/lootdestroy - will mark the item on your cursor =destroy
/lootkeep - will mark the item on your cursor =keep
/lootsell - will mark item on your cursor =sell
/lootquest - will mark item on your cursor =quest|default value (QuestKeep=10 in loot.ini)
/lootignore - will mark item on your cursor =ignore (leaves on corpse)

Furthermore:
Rich (BB code):
/sellstuff - A command that if you have a merchant targeted will sell everything in your inventory marked =sell
/depositstuff - Target your guildbanker and this command will deposit any item in your inventory marked =keep into the guild bank.
 
It was pointed out that Eqmule used a slightly different kissassist.ini file name in his amazing kissini.mac

Updated the Master Looter select/replace section to include both kissassist_charactorname.ini and kissassisst_server_charactorname.ini formats when looking for the LootOn=0 variable to exclude group members from being select as Master Looter.

cred: Icognito
 
1. LOOT ALL is turned off in the advloot window.

Note: This is really only important for the Master Looter. This is because Auto Loot will process and capture items in the Personal Loot Window (put there by Ninja to be processed by Ninja) before Ninja can get to them (for delete etc). IF you know that ML will not fill up, thus ML will not be re-assigned, then you can have that on for the other memebers of the grp. Why? Because with it off grp members may not get items that ML is trying to pass out. I have some more digging to do, but that is what I suspect at this time. If you are there to watch it, you can click the Loot All button, or the green checkmark icon to loot individual items. However, if you are not there, the item ML is trying to pass out might sit in the personal loot window until the corpse times out and poof. Again, this is just what I suspect at this time.

Why can't we just leave well enough alone I tell you.

Lol bud, LOL...
 
Note: This is really only important for the Master Looter. This is because Auto Loot will process and capture items in the Personal Loot Window (put there by Ninja to be processed by Ninja) before Ninja can get to them (for delete etc). IF you know that ML will not fill up, thus ML will not be re-assigned, then you can have that on for the other memebers of the grp. Why? Because with it off grp members may not get items that ML is trying to pass out. I have some more digging to do, but that is what I suspect at this time. If you are there to watch it, you can click the Loot All button, or the green checkmark icon to loot individual items. However, if you are not there, the item ML is trying to pass out might sit in the personal loot window until the corpse times out and poof. Again, this is just what I suspect at this time.

Lol bud, LOL...

Stuff should only sit in your personal loot window under a couple different conditions.

1) Your inventory is complete full. I mean completely, stuff is stuck on your cursor full. /autoinventory no longer works full.

2) If you are not calling the include file from your main macro for that particular character. Ninjadvloot spams a fair amount of what is going on. If you are not seeing any spam on a particular character, that character is not calling loot. Check your main macro and make sure there is a call to loot for everyone in the group, even if they are not allowed to be master looter, LootOn=0. Lore, nodrop, and quest marked items can still be looted by every group member regardless of any ini settings, as long as they have at least some empty inventory slots.


The LOOT ALL function of the in game system is much faster then ninjadvloot. If ANY character has LOOT ALL on they WILL loot all items that get to their personal list, regardless of any settings in your loot.ini file
 
Understood, and agree.

And you just hit the nail on the head, my bad. Given Raz's proclivity for wizzy's having one job and that's to NUKE, it stands to reason there is zero call to Ninja in AFnuke... Now see, if you hadn't responded I could simply delete my post *sigh*.

- - - Updated - - -

Noteworthy to mention; the Gremlin can and will make shit up...
 
I was afraid you had discovered yet another weakness... This heat wave BS is keeping me real busy at work and I don't really have time to play or troubleshoot code until things cool off again.
 
This..

Furthermore:
Rich (BB code):
/sellstuff - A command that if you have a merchant targeted will sell everything in your inventory marked =sell
/depositstuff - Target your guildbanker and this command will deposit any item in your inventory marked =keep into the guild bank.
[/QUOTE]


.... is awesome.

Any chance we can have a command to drop items marked put in house/storage crate?
 
For the record, the commands are actually old, Maskoi had added those as far back as 2010.

In fact, going into the code to extract that date I noticed another command:
Rich (BB code):
/buy ItemToBuy QuantityToBuy

I had heard mention of 'buy' before but never really paid any mind. It isn't an alias so didn't get included in my command list above. If you have a vendor targeted (not tested) you can issue a /buy water flask 20 and it will buy 20 waters. I have never used it, and it doesn't seem to work on the VeteranReward vendors, looks like they report as a familiar which is filtered out in the target check. I will have to try it when I get back to town (main grp been in the filed for weeks).

- - - Updated - - -

In looking at the DepositToGuildBank sub routine, it is feasible to add a storage crate item(s) deposit, but there would have to be a significant user demand to consider it. Seems a one off to me...
 
Have you guys ever run into issues with this and kissassist when using a character with insta-clickies as a master looter? My mage is the only one who gets this weird exchange error while using KISS, and it only happens when he's also the master looter. I can't figure out if this include file might be part of the issue, or if it's code inherent to kiss. The errors that the macro spits out at me are all lines in the kiss code, but now that I have it narrowed down (I think) to a looting issue... yea.
 
I have occasionally had exchange issues with KISS, although I always thought it was actually MQ2Exchange. What is the error you are getting?

- - - Updated - - -

Hoosier, I did actually see the msg 'There was no container in slot 31' just now. It had been awhile since I had seen it (different slot #). The only thing I can think of is that this particular character has two 'Heroic Satchel of the Adventurer'. It would be interesting to see if the rare few that had seen this msg also have heroic bags. I think Maskoi mentioned seeing this msg once, but again it's been awhile.

It fires during the destroy routine, and sends the msg 5 times. The worse case scenario is that stuff doesn't get destroyed in that particular bag is all.

Right now, they are the last 2 bags to be filled so the issue doesn't come up unless I wait to clear out bag space. Iirc, when I was getting oddities with slot 1 (mentioned before) it was related to putting one of those heroic bags in the first slot. The more I think about it the more I am leaning towards heroic bags being involved somehow...
 
Have you guys ever run into issues with this and kissassist when using a character with insta-clickies as a master looter? My mage is the only one who gets this weird exchange error while using KISS, and it only happens when he's also the master looter. I can't figure out if this include file might be part of the issue, or if it's code inherent to kiss. The errors that the macro spits out at me are all lines in the kiss code, but now that I have it narrowed down (I think) to a looting issue... yea.

I have occasionally had exchange issues with KISS, although I always thought it was actually MQ2Exchange. What is the error you are getting?

- - - Updated - - -

Hoosier, I did actually see the msg 'There was no container in slot 31' just now. It had been awhile since I had seen it (different slot #). The only thing I can think of is that this particular character has two 'Heroic Satchel of the Adventurer'. It would be interesting to see if the rare few that had seen this msg also have heroic bags. I think Maskoi mentioned seeing this msg once, but again it's been awhile.

It fires during the destroy routine, and sends the msg 5 times. The worse case scenario is that stuff doesn't get destroyed in that particular bag is all.

Right now, they are the last 2 bags to be filled so the issue doesn't come up unless I wait to clear out bag space. Iirc, when I was getting oddities with slot 1 (mentioned before) it was related to putting one of those heroic bags in the first slot. The more I think about it the more I am leaning towards heroic bags being involved somehow...

Been thinking about this for bit.... I have heroic toons so will try heroic bag in first slot see if I can replicate that as an issue. The only time I had any problem with exchanging items was letting kissassist switch out range item for throwing blades. KA did fine if it was bow and arrow but throwing blades flipped it out completely. I forget how I stopped it from doing that.... I think I equipped the throwing blades when starting the KA macro so there was no need for anything to be exchanged.
 
FYI the heroic bag is NOT currently in first slot, I only mentioned first slot because I think it's related and previously when mentioning it, it WAS in first slot. Make sense?
 
I have occasionally had exchange issues with KISS, although I always thought it was actually MQ2Exchange. What is the error you are getting?

I wrote it down at home, so I'll try to remember to come back and post it later on. What I've confirmed is it has something to do with clickies (either using them or actually summoning them). When the error happens I need to log to character select and back in or as soon as I re-start KISS I get spammed with an exchange error (something about not being able to find item 75603 (guessing the number... I can get it later on)). I also found yesterday that it happened on my mage even after I swapped master looting to another toon, so perhaps its not directly tied to this include file. Once I removed all insta-clickies (mage wand and summoned nuke clickies) from my KISS.ini the thing ran all night flawlessly.
 
Are you using kiss8 or kiss 9. What spells or clickies. I have an old lower level mage I can setup and try to replicate the problem, if I can get close to the same kind of spells clickies
 
Mage is lvl 100 and using the last kiss 8 version (believe 8.5.5.). The issues happen when using the summoned mod rods AND the summoned clicky nuke items (have had it happen when using both).

I *think* it has something to do with what happens when the item is used up. I've seen the mod rod work fine for one clicky, and then when I come back it's gone and the macro is freaking the f out.

(this is likely not a ninjadvloot.inc issue ... at least I'm thinking the chances of it being associated with this file are very low now)
 
I have occasionally had exchange issues with KISS, although I always thought it was actually MQ2Exchange. What is the error you are getting?

- - - Updated - - -

Hoosier, I did actually see the msg 'There was no container in slot 31' just now. It had been awhile since I had seen it (different slot #). The only thing I can think of is that this particular character has two 'Heroic Satchel of the Adventurer'. It would be interesting to see if the rare few that had seen this msg also have heroic bags. I think Maskoi mentioned seeing this msg once, but again it's been awhile.

It fires during the destroy routine, and sends the msg 5 times. The worse case scenario is that stuff doesn't get destroyed in that particular bag is all.

Right now, they are the last 2 bags to be filled so the issue doesn't come up unless I wait to clear out bag space. Iirc, when I was getting oddities with slot 1 (mentioned before) it was related to putting one of those heroic bags in the first slot. The more I think about it the more I am leaning towards heroic bags being involved somehow...

just a note, here is a list of slot #'s (not bag slot 9 & 10 are indexed as # 31 & 32). So it could very well be an issue with those particular items.
Rich (BB code):
"usage: /useitem <slot> <subindex>
slot definitions:
Charm = 0
Left Ear = 1
Head = 2
Face = 3
Right Ear = 4
Neck = 5
Shoulders = 6
Arms = 7
Back = 8
Left Wrist = 9
Right Wrist = 10
Range = 11
Hands = 12
Primary = 13
Secondary = 14
Left Ring = 15
Right Ring = 16
Chest = 17
Legs = 18
Feet = 19
Waist = 20
Power Source = 21
Ammo = 22
Bag Slot 1 = 23
Bag Slot 2 = 24
Bag Slot 3 = 25
Bag Slot 4 = 26
Bag Slot 5 = 27
Bag Slot 6 = 28
Bag Slot 7 = 29
Bag Slot 8 = 30
Bag Slot 9 = 31     <XXX
Bag Slot 10 = 32   <XXX
subindex: Only used if slot is a bag. Bag slot number starting at 0, left to right, top to bottom."
 
Thx Meistro!

Ok, woke up to find bags full of things marked destroy. I logged that toon out and back in and now things are working fine. Maybe there is a limit to how long we can expect things to work before going wonky (not gonna tell how long this toon has been on... not gonna do it).

One of the debugging methods I use, when something starts behaving differently, is to ascertain what has changed environmentally. I have suspected before that if you change around your bags, like if you had an empty one in another bag, took it out and placed it in a open slot, that it would confuse Ninja, MQ2, KA, or something. I am always looking for something that gets cached. I had moved some bags around, and maybe even moved 1 inside another, and back again, and maybe that list/array isn't getting updated.

Working now so will monitor it and try to narrow down the conditions that cause it to fail.
 
Mage is lvl 100 and using the last kiss 8 version (believe 8.5.5.). The issues happen when using the summoned mod rods AND the summoned clicky nuke items (have had it happen when using both).

I *think* it has something to do with what happens when the item is used up. I've seen the mod rod work fine for one clicky, and then when I come back it's gone and the macro is freaking the f out.

(this is likely not a ninjadvloot.inc issue ... at least I'm thinking the chances of it being associated with this file are very low now)

Still thinking about this, my mage account is tied up an another project so can't do any actual testing just yet.
I am curious, are the clicky items showing up in your loot.ini file? I don't think they should, but I have occasional had weird things happen...
I think something gets confused when an item is already on the cursor while you are trying to loot.

Makes me wonder.... Are you using foraging?

Foraging is an older section of code, I haven't messed with or even looked closely at the older original code.

- - - Updated - - -

Thx Meistro!

Ok, woke up to find bags full of things marked destroy. I logged that toon out and back in and now things are working fine. Maybe there is a limit to how long we can expect things to work before going wonky (not gonna tell how long this toon has been on... not gonna do it).

One of the debugging methods I use, when something starts behaving differently, is to ascertain what has changed environmentally. I have suspected before that if you change around your bags, like if you had an empty one in another bag, took it out and placed it in a open slot, that it would confuse Ninja, MQ2, KA, or something. I am always looking for something that gets cached. I had moved some bags around, and maybe even moved 1 inside another, and back again, and maybe that list/array isn't getting updated.

Working now so will monitor it and try to narrow down the conditions that cause it to fail.

Still trying to reproduce issue. I found a place on my server that appears to be so far off the beaten path no one has bothered me in two days. When the healers stop letting the tanks die, I should be able to get a long run time.
I think you might be correct, long run times may cause macro's to lose track of variables. I almost never let my computers stay on more then 24 hours, usually restart them in the morning and turn them off at night.

Bah, sitting here typing this and noticed my stupid druid is on a hunger strike... won't cast his food/drink clicky. Actually, he's not casting any buffs... somehow buffs didn't get turned on in the ini. This is why I can't have nice things...

Anyway... I am trying to get this to happen to me. Heroic bags in various slots, with/without empty bags inside them, full bags/empty bags...
 
I'm not using foraging on the mage. I'll have to check my loot.ini file later on and see if something weird happened.

I'm honestly lost because Maskoi said KISS doesn't use MQ2Exchange, but this issue is associated with it somehow, and ONLY presents itself when I use KISS with the mage. When my zerker was running around using a different macro there wasn't issues, and I've never had issues looting with KISS on my shaman or chanter (using this .inc file).
 
Maskoi said KISS doesn't use MQ2Exchange
Kiss is using something to swap out bow for pulling and an AC item in Ranged for combat. I had always thought it was MQ2Exchange. I will have to check the KA code to see what else it might use.

- - - Updated - - -

Rich (BB code):
/exchange "${OrigRanged}" ranged

KA is riddled with /exchange cmds. Unless Mask has overridden the /exchange cmd, it is using MQ2Exchange.

Rich (BB code):
/call CheckPlugin MQ2Exchange
It checks for the plugin...
 
Ahhh, I misspoke ... Now that I think about it he said it doesn't use mq2exchange to cast stuff like summoned clicky nukes or mod rods.
 
I would guess it uses MQ2Cast or the include spell_cast_routines...
Maskio or CTaylor would be the ones to ask about that. My limited understand of code is nothing in ninjadvloot would cause either of these issues... but my understanding is limited and I am always surprised when I look at what others are doing with their macros.


Honestly, this project was beyond me ability until I started it and expanded my abilities to make it work. If I can reproduce the issue, I have up until now been lucky enough to figure out a way to overcome/mitigate the problems. Any details that help me cause the same to happen to me are greatly appreciated.
 
I would guess it uses MQ2Cast or the include spell_cast_routines...
Maskio or CTaylor would be the ones to ask about that. My limited understand of code is nothing in ninjadvloot would cause either of these issues... but my understanding is limited and I am always surprised when I look at what others are doing with their macros.


Honestly, this project was beyond me ability until I started it and expanded my abilities to make it work. If I can reproduce the issue, I have up until now been lucky enough to figure out a way to overcome/mitigate the problems. Any details that help me cause the same to happen to me are greatly appreciated.

Really impressive work if it was partially a learning as you go kind of thing. The only thing I wish it had at this point was some way to filter NO DROP items to only classes that can use them.

One thing I'll say, for farming HoT armor and the like, is that it's pretty great you can flag the drops as Quest|1 (or 2 for bracers) and your characters will round robin the items.
 
Really impressive work if it was partially a learning as you go kind of thing. The only thing I wish it had at this point was some way to filter NO DROP items to only classes that can use them.

One thing I'll say, for farming HoT armor and the like, is that it's pretty great you can flag the drops as Quest|1 (or 2 for bracers) and your characters will round robin the items.

Sorting NO DROP by class proved difficult. I could not find a way to read the class information while the item was still on the shared list in the advloot window. I know it can probable be done, but I suspect it will require additional TLO members... That's a mothership sort of thing. If enough people pester the MQ2 developers into making the TLO's I will revisit this possibility.

The quest items feature was what started this... I hated trying to sort through items I needed for quests and armor drops...
 
I guess there wouldn't be a part of the code where you could create a loot.ini based on character name so as to manually be able to tell it ignore/keep on particular items you are hunting for? I used to do this by making more than one kissassist macro where each character had their own that generated a loot-character.ini that I would then manually manage.

- - - Updated - - -

Err... wait. Does the name of the kissassist.mac file matter to this? I think I mistook the INI requirement for a kissassist.mac requirement.
 
Off the top of my head, if you had different Kissassist.macs for diff toons, like KA_Brd.mac & KA_Clr.mac, you could modify the call to Ninja so it points to custom Ninja.inc(s) (NinjaBrd.inc & NinjaClr.inc) that could be pointing to custom loot.ini (lootbrd.ini & lootclr.ini). Make Sense? I'll have to think if there is a more elegant solution...

The actual KA name does not matter in this. There was a brief time where there was debug code in Ninja based on KA name, but that has since been removed.
 
I guess there wouldn't be a part of the code where you could create a loot.ini based on character name so as to manually be able to tell it ignore/keep on particular items you are hunting for? I used to do this by making more than one kissassist macro where each character had their own that generated a loot-character.ini that I would then manually manage.

- - - Updated - - -

Err... wait. Does the name of the kissassist.mac file matter to this? I think I mistook the INI requirement for a kissassist.mac requirement.

Yes, I do it all the time using server or group leader.

In your macro (kissassist.mac or MacroName.mac) find the command to initialize ninjadvloot
Rich (BB code):
/call SetupAdvLootVars
You may add a parameter after that line to change the name of your loot.ini file
Rich (BB code):
/call SetupAdvLootVars Loot_Farming.ini
or
Rich (BB code):
/call SetupAdvLootVars Loot_${Me.Name}.ini
or
Rich (BB code):
/call SetupAdvLootVars Loot_${EverQuest.Server}_${Me.Name}.ini
or
Rich (BB code):
	/if (${Select[${Group.Leader.Name},blah,blah1]}) {
		/call SetupAdvLootVars Loot_Farming.ini
	} else /if (${Select[${Group.Leader.Name},blah2,blah3]}) {
		/call SetupAdvLootVars Loot_Quest.ini
	} else {
		/call SetupAdvLootVars
	}

The possibilities are endless. Once you select the file name you are stuck with it until you restart your macro, changing it on the fly is wonky.

The name of the macro (kissassist/afknuke/whatever) does not matter. It's all about the /call parameter.

Not sure I would want to keep up with loot.ini for each group member though... Using 3 separate loot files across different three computers is pain enough for me...

- - - Updated - - -

BINGO


duplicated the error no container in slot

- - - Updated - - -

Hoosier, I did actually see the msg 'There was no container in slot 31' just now. It had been awhile since I had seen it (different slot #)...

If the item to be destroyed is in a top level slot instead of a container it generates the error, unless it is the upper left slot - Bag Slot 1 = 23

This is part of the original code, not something I changed....yet

Now to figure out how to fix it.

Temp fix - put something/anything in all top level slots.

- - - Updated - - -

Ok, woke up to find bags full of things marked destroy. I logged that toon out and back in and now things are working fine. Maybe there is a limit to how long we can expect things to work before going wonky (not gonna tell how long this toon has been on... not gonna do it).

One of the debugging methods I use, when something starts behaving differently, is to ascertain what has changed environmentally. I have suspected before that if you change around your bags, like if you had an empty one in another bag, took it out and placed it in a open slot, that it would confuse Ninja, MQ2, KA, or something. I am always looking for something that gets cached. I had moved some bags around, and maybe even moved 1 inside another, and back again, and maybe that list/array isn't getting updated.

Working now so will monitor it and try to narrow down the conditions that cause it to fail.

Finally found a place where I could go for a long uninterrupted session. This morning my toons went stupid. kissassist and spell cast routine.inc and ninjadvloot.inc showing various variable errors, unable to parse, blah,blah. Restarting just the macro's did not fix the problem. Looks like your gonna have to reboot and restart periodically, at least everyday or two.
 
Bump.

Threads don't get bumped when merely updated so I am bumping this manually. We have fixed 2 very elusive long standing issues in Ninja.

1) A semi-rare condition where you would see the msg There is no container in slot XX. This was during the destroy process and would fail to destroy the newly looted item.

2) In certain conditions, with an item marked for destroy, Ninja could destroy a whole stack rather than the individual item it just looted.

This is a very solid Ninja release and we have accomplished everything we set out to. I believe we are done.

I cannot thank you enough Hoosier for working on this. This is what makes RG work. Ppl like you stepping up and taking on a project to completion. I am proud to have worked on this with you and I salute you! Damnit, now to go rez my wizzy *sigh*.
 
Interesting.... Turning off the AdvLoot filters interferes with autoroll for quest marked items. I have removed that recommendation.
 
Has anyone run into issues where kissassist will suddenly stop looting certain items? Mine went from looting the hell out of everything (which i wanted) to leaving certain things behind... no freaking idea what could have changed because all my macros and the include files were the same.
 
Check the loot.ini file entry for the items. Particularly if they are nodrop/notrade or lore.

Lore items you can only keep one for each group member.
items marked =quest|xx will stop looting when everyone has xx number of items.
The only other thing I can think of is if the group master looter changed and the in-game advloot filters are coming into play.
The last think to look at is the > StackPlatValue=x < setting in the loot.ini file. The item must have value >= to the setting. =0 will keep everything.
 
I may have slipped up and clicked a button on the in-game advloot filters, but that's all I can think of. The ninjaadvloot 6.2 is letting all Essence .... bleh... the things that drop like freakin candy in CoTF zones... on the corpses. It will loot everything else and properly divvy out lore items. The same toon has looted probably 1000 of the things (and has like 600 on him right now) in the last week, so I don't think its the loot.ini or the issue with groups of 10. I also thought of the plat value entry and I believe they're worth plenty more than 50 a stack (which was the default, iirc).

I don't think it's your .inc file giving me issues, I just don't like the fact that my nice, clean afk exp camp is suddenly riddled with corpses lol. Since this has become the defacto "loot awesomely" thread for me, I thought I'd ask if you guys ran into this.

I'd like to add that this has changed the way I afk farm gear... I have a team in game right now camping one out-of-the-way TBM named for a couple of items and for the visible gear. It's great!
 
It is a game changer... at least for me it is.
Please confirm loot.ini entry for items in question and the in-game advanced loot filters. I have had the in-game system suddenly decide it don't like a particular item. I thought I isolated that issue and fixed it long time ago.

FYI - when farming gear I would set StackPlatValue=0 just to be safe and/or make sure the gear has an entry (=keep) in the loot.ini file. Better to keep some valueless trash and have to delete it, then have something you want left on the corpse to rot.

I discovered a 24 slot bag on one of my afk toons that had been set to =ignore, makes me bit sad wondering how many rotted before I discovered it.
 
Don't forget your ini can get corrupted. I had one that I poured over for weeks and never found a anything in it awry. However the second I deleted it (actually, renamed it) everything started working fine. To this day I can't find what is wrong in the ini.
 
Release Ninjadvloot.inc

Users who are viewing this thread

Back
Top
Cart