Release (YALM) Yet Another Loot Manager 0.12.7

KingArthur · Jan 23, 2024

Well, I just back into the game and still want to use this my favorite loot Lua. I downloaded the newest version yet after /Lua run yalm, it says:

I clicked Install, a cmd window with no hints just pop then when I closed it, it says:

Any idea to fix this plz? I really love this one..

P. S. I also tried as Brainiac said in another post "%appdata%/local/luarocks delete it and stop running as admin" and still no go. (that action used to fix the similar error on Boxhud though)

Knightly · Jan 23, 2024

Knightly updated (YALM) Yet Another Loot Manager with a new update entry:

PackageMan Cleanup

PackageMan was being used in includes that didn't require PackageMan functionality.

Read the rest of this update entry...

Knightly · Jan 23, 2024

KingArthur said:
P. S. I also tried as Brainiac said in another post "%appdata%/local/luarocks delete it and stop running as admin" and still no go. (that action used to fix the similar error on Boxhud though)

I did some cleanup just now, but I'm not in a place where I can test it. I also don't think my cleanup was related to your issue. The only folder that matters is your Modules folder and you can delete the whole thing without impact. Besides that, just make sure you're up to date.

KingArthur · Jan 23, 2024

Knightly said:
I did some cleanup just now, but I'm not in a place where I can test it. I also don't think my cleanup was related to your issue. The only folder that matters is your Modules folder and you can delete the whole thing without impact. Besides that, just make sure you're up to date.

Sir, I downloaded the newest version and deleted the module folder under my MQNext folder, yet it still shows

And then it shows a little bit different yet still error:

Thank you for the help!

P. S. Everytime I deleted my modules folder, it will regenerate a new one, dunno if that matters.

Knightly · Jan 23, 2024

KingArthur said:
P. S. Everytime I deleted my modules folder, it will regenerate a new one, dunno if that matters.

I meant make sure your MacroQuest is up to date (but the script too). You can try opening mq\PackageMan.Lua and flipping PackageMan.debug to true and it should output more information.

You only needed to delete the modules folder one time, it puts it back when it runs.

KingArthur · Jan 23, 2024

Knightly said:
I meant make sure your MacroQuest is up to date (but the script too). You can try opening mq\PackageMan.lua and flipping PackageMan.debug to true and it should output more information.

You only needed to delete the modules folder one time, it puts it back when it runs.

Changed PackageMan.debug = true, now it shows:

Knightly · Jan 23, 2024

KingArthur said:
Changed PackageMan.debug = true, now it shows:

No clue, copy paste that command into a command prompt and see what happens. Copy/Paste from MQ console which is ctrl+` (ctrl+backtick)

KingArthur · Jan 25, 2024

Knightly said:
No clue, copy paste that command into a command prompt and see what happens. Copy/Paste from MQ console which is ctrl+` (ctrl+backtick)

Thank you sir, I did what you said and it works again! :hfive:

Knightly · Jan 25, 2024

Well, that wasn't meant to be the actual answer. Sounds like I need to add more debug output to packageman.

Mikey02 · Jan 31, 2024

Thank you, can finally donate for tribute in mass. Will there be any plan to adding error checking for when tribute is full? Right now it seems to just hang if you can no longer donate due to tribute cap.

a_moss_snake · Feb 1, 2024

Regarding tribute, I made the following changes on my system:

Tribute.lua

Lua:

...
local function action(global_settings, char_settings, args)
    if args[2] then
        if not (args[2] == "guild" or args[2] == "me") then
            Write.Error("That is not a valid option")
        end
    end
...

and
helpers.lua

Lua:

...
helpers.ready_tribute_window = function(travel, tribute_master)
    if
        tribute_master == "me"
        or (tribute_master == nil and mq.TLO.Target.Class() ~= "Guild Tribute Master" and mq.TLO.NearestSpawn('class "Tribute Master"').Class() == "Tribute Master")
        or (tribute_master == nil and mq.TLO.Target.Class() == "Tribute Master")
    then
        return helpers.ready_npc_window("TributeMasterWnd", "Tribute Master", travel)
    elseif
        tribute_master == "guild"
        or (tribute_master == nil and mq.TLO.Target.Class() ~= "Tribute Master" and mq.TLO.NearestSpawn('class "Guild Tribute Master"').Class() == "Guild Tribute Master")
        or (tribute_master == nil and mq.TLO.Target.Class() == "Guild Tribute Master")
    then
        return helpers.ready_npc_window("TributeMasterWnd", "Guild Tribute Master", travel)
    end
...

Now guild/personal tribute is working fine for me.

Nightmare327 · Mar 1, 2024

Mikey02 said:
Thank you, can finally donate for tribute in mass. Will there be any plan to adding error checking for when tribute is full? Right now it seems to just hang if you can no longer donate due to tribute cap.

I wonder if we could add an event to trigger a variable, then have the main code for tribute have a loop where it checks that variable? I have just started trying to use this script again, and I am still learning the ins and outs of the configuration.

Nightmare327 · Mar 4, 2024

Trying out the guild tribute feature, and running into an issue. I do the /yalm tribute guild, and the toon navigates to the Personal Tribute master, not the Guild tribute Master I have targeted.

Some minor bug fixes: yalm>config>commands>Tribute.Lua, line 63
if args[2] ~= "guild" and args[2] == "me" then (old)
if args[2] ~= "guild" and args[2] ~= "me" then (new, should be not equal to "me")

yalm>core>helpers.Lua lines 118-128 ( I had to change or to and, then enclose the second and third conditions in a parenthesis)

Lua:

   if
        tribute_master == "me"
        and (mq.TLO.NearestSpawn('class "Tribute Master"').Class() == "Tribute Master"
        or mq.TLO.Target.Class() == "Tribute Master")
    then
        return helpers.ready_npc_window("TributeMasterWnd", "Tribute Master", travel)
    elseif
        tribute_master == "guild"
        and (mq.TLO.NearestSpawn('class "Guild Tribute Master"').Class() == "Guild Tribute Master"
        or mq.TLO.Target.Class() == "Guild Tribute Master")
    then

was

Lua:

   if
        tribute_master == "me"
        or mq.TLO.NearestSpawn('class "Tribute Master"').Class() == "Tribute Master"
        or mq.TLO.Target.Class() == "Tribute Master"
    then
        return helpers.ready_npc_window("TributeMasterWnd", "Tribute Master", travel)
    elseif
        tribute_master == "guild"
        or mq.TLO.NearestSpawn('class "Guild Tribute Master"').Class() == "Guild Tribute Master"
        or mq.TLO.Target.Class() == "Guild Tribute Master"
    then

There was some timing issues with the guild tribute running too fast, so it would skip items, but I am troubleshooting that. I reached the favor cap, so I will keep testing later on. There also seemed to be an issue with items being added to either the all or me list, still trying to verify this issue.

If I did /yalm setitem Tribute me - the YALM.Lua was not updated (I am not sure where the character items are stored, if anywhere?)
If I ran the command /yalm setitem Tribute all, the item would appear in the config/YALM.Lua file as I expected.

Cannonballdex · Mar 6, 2024

Nightmare327 said:
Trying out the guild tribute feature, and running into an issue. I do the /yalm tribute guild, and the toon navigates to the Personal Tribute master, not the Guild tribute Master I have targeted.
View attachment 58377

Some minor bug fixes: yalm>config>commands>Tribute.lua, line 63
if args[2] ~= "guild" and args[2] == "me" then (old)
if args[2] ~= "guild" and args[2] ~= "me" then (new, should be not equal to "me")

yalm>core>helpers.lua lines 118-128 ( I had to change or to and, then enclose the second and third conditions in a parenthesis)

Lua:

if tribute_master == "me" and (mq.TLO.NearestSpawn('class "Tribute Master"').Class() == "Tribute Master" or mq.TLO.Target.Class() == "Tribute Master") then return helpers.ready_npc_window("TributeMasterWnd", "Tribute Master", travel) elseif tribute_master == "guild" and (mq.TLO.NearestSpawn('class "Guild Tribute Master"').Class() == "Guild Tribute Master" or mq.TLO.Target.Class() == "Guild Tribute Master") then

was

Lua:

if tribute_master == "me" or mq.TLO.NearestSpawn('class "Tribute Master"').Class() == "Tribute Master" or mq.TLO.Target.Class() == "Tribute Master" then return helpers.ready_npc_window("TributeMasterWnd", "Tribute Master", travel) elseif tribute_master == "guild" or mq.TLO.NearestSpawn('class "Guild Tribute Master"').Class() == "Guild Tribute Master" or mq.TLO.Target.Class() == "Guild Tribute Master" then

There was some timing issues with the guild tribute running too fast, so it would skip items, but I am troubleshooting that. I reached the favor cap, so I will keep testing later on. There also seemed to be an issue with items being added to either the all or me list, still trying to verify this issue.

If I did /yalm setitem Tribute me - the YALM.lua was not updated (I am not sure where the character items are stored, if anywhere?)
If I ran the command /yalm setitem Tribute all, the item would appear in the config/YALM.lua file as I expected.

Been a while but I remember these issues. If you actually opened up the guild tribute master and ran it then it would work otherwise would run to personal. There is a timing issue as well, I can't remember where , but I remember changing the delay and it worked great.

Nightmare327 · Mar 7, 2024

Cannonballdex said:
Been a while but I remember these issues. If you actually opened up the guild tribute master and ran it then it would work otherwise would run to personal. There is a timing issue as well, I can't remember where , but I remember changing the delay and it worked great.

Even if I had the right vendor opened up, it would still run to the wrong vendor. I wonder if it is possible to get these fixes into the codebase? I am not sure who maintains this codebase currently.

KingArthur · Mar 24, 2024

Dunno if this is still been actively maintained, but I just could not get this work again. What I want to do is ignore basically collectibles, keep TS/Quest stuff. And here is my rules under my config/yalm.Lua,

Code:

['rules'] = {
        ['Farm'] = {
            ['category'] = '',
            ['items'] = {},
            ['name'] = 'Farm',
            ['conditions'] = {
                [1] = {
                    ['quantity'] = 1,
                    ['name'] = 'Collectible',
                    ['setting'] = 'Ignore',
                },
                [2] = {
                    ['name'] = 'Poisons',
                    ['setting'] = 'Ignore',
                },
                [3] = {
                    ['name'] = 'Venom',
                    ['setting'] = 'Ignore',
                },
                [4] = {
                    ['name'] = 'Augmentation',
                    ['setting'] = 'Keep',
                },
                [5] = {
                    ['name'] = 'Temporary',
                    ['setting'] = 'Ignore',
                },
                [6] = {
                    ['name'] = 'Defiant',
                    ['setting'] = 'Ignore',
                },
                [7] = {
                    ['name'] = 'Ornament',
                    ['setting'] = 'Ignore',
                },
                [8] = {
                    ['name'] = 'FoodDrink',
                    ['setting'] = 'Ignore',
                },
                [9] = {
                    ['name'] = 'Quest',
                    ['setting'] = 'Keep',
                },
                [10] = {
                    ['name'] = 'Tradeskill',
                    ['setting'] = 'Keep,
                },
                [11] = {
                    ['name'] = 'LowStack',
                    ['setting'] = 'Ignore',
                },
                [12] = {
                    ['name'] = 'NoValue',
                    ['setting'] = 'Ignore',
                },
            },
        },
    },

Here is what under my config/yalm/yalm-server-character.Lua,

Code:

return {
    ['settings'] = {
          unmatched_item_rule = {
            setting = 'Keep',
        },
    },
    ['items'] = {},
    ['save'] = {},
    ['rules'] = {
        {
            name = 'Farm',
            enabled = true,
        },
    },
}

I'm in a group, the group leader also as the master looter /Lua run yalm, yet still he looted everything, included the collectibles and other junkies which supposed to be ignored.

Any ideas?

P. S. I used /yalm check for the collectibles on my cursor, and it said correctly should be ignoreed blahblah... However the actual loot behavior is looting the collectibles, which is really confusing..

KingArthur · Mar 24, 2024

Well, looks like all LS item can't return the correct value of conditions...

a_moss_snake · Mar 28, 2024

Nightmare327 said:

yalm>core>helpers.lua lines 118-128 ( I had to change or to and, then enclose the second and third conditions in a parenthesis)

Lua:

   if
        tribute_master == "me"
        and (mq.TLO.NearestSpawn('class "Tribute Master"').Class() == "Tribute Master"
        or mq.TLO.Target.Class() == "Tribute Master")
    then
        return helpers.ready_npc_window("TributeMasterWnd", "Tribute Master", travel)
    elseif
        tribute_master == "guild"
        and (mq.TLO.NearestSpawn('class "Guild Tribute Master"').Class() == "Guild Tribute Master"
        or mq.TLO.Target.Class() == "Guild Tribute Master")
    then

was

Lua:

   if
        tribute_master == "me"
        or mq.TLO.NearestSpawn('class "Tribute Master"').Class() == "Tribute Master"
        or mq.TLO.Target.Class() == "Tribute Master"
    then
        return helpers.ready_npc_window("TributeMasterWnd", "Tribute Master", travel)
    elseif
        tribute_master == "guild"
        or mq.TLO.NearestSpawn('class "Guild Tribute Master"').Class() == "Guild Tribute Master"
        or mq.TLO.Target.Class() == "Guild Tribute Master"
    then

check out the modifications I made to the same code a few posts above, for the conditions you might want to reconsider (either just rely on the me/guild setting, or define the conditions if the setting is missing).

Cannonballdex · Mar 28, 2024

KingArthur said:

Dunno if this is still been actively maintained, but I just could not get this work again. What I want to do is ignore basically collectibles, keep TS/Quest stuff. And here is my rules under my config/yalm.lua,

Code:

['rules'] = {
        ['Farm'] = {
            ['category'] = '',
            ['items'] = {},
            ['name'] = 'Farm',
            ['conditions'] = {
                [1] = {
                    ['quantity'] = 1,
                    ['name'] = 'Collectible',
                    ['setting'] = 'Ignore',
                },
                [2] = {
                    ['name'] = 'Poisons',
                    ['setting'] = 'Ignore',
                },
                [3] = {
                    ['name'] = 'Venom',
                    ['setting'] = 'Ignore',
                },
                [4] = {
                    ['name'] = 'Augmentation',
                    ['setting'] = 'Keep',
                },
                [5] = {
                    ['name'] = 'Temporary',
                    ['setting'] = 'Ignore',
                },
                [6] = {
                    ['name'] = 'Defiant',
                    ['setting'] = 'Ignore',
                },
                [7] = {
                    ['name'] = 'Ornament',
                    ['setting'] = 'Ignore',
                },
                [8] = {
                    ['name'] = 'FoodDrink',
                    ['setting'] = 'Ignore',
                },
                [9] = {
                    ['name'] = 'Quest',
                    ['setting'] = 'Keep',
                },
                [10] = {
                    ['name'] = 'Tradeskill',
                    ['setting'] = 'Keep,
                },
                [11] = {
                    ['name'] = 'LowStack',
                    ['setting'] = 'Ignore',
                },
                [12] = {
                    ['name'] = 'NoValue',
                    ['setting'] = 'Ignore',
                },
            },
        },
    },

Here is what under my config/yalm/yalm-server-character.lua,

Code:

return {
    ['settings'] = {
          unmatched_item_rule = {
            setting = 'Keep',
        },
    },
    ['items'] = {},
    ['save'] = {},
    ['rules'] = {
        {
            name = 'Farm',
            enabled = true,
        },
    },
}

I'm in a group, the group leader also as the master looter /lua run yalm, yet still he looted everything, included the collectibles and other junkies which supposed to be ignored.

Any ideas?

P. S. I used /yalm check for the collectibles on my cursor, and it said correctly should be ignoreed blahblah... However the actual loot behavior is looting the collectibles, which is really confusing..

Not sure what is different here, figured I would share my files as a reference. I am ignoring all Defiant and Ornaments.

Code:

return {
    ['categories'] = {},
    ['functions'] = {},
    ['settings'] = {
        ['save_slots'] = 3,
        ['always_loot'] = true,
        ['unmatched_item_rule'] = {
            ['setting'] = 'Keep',
        },
    },
    ['rules'] = {
        ['Defiant'] = {
            ['items'] = {},
            ['category'] = '',
            ['conditions'] = {
                [1] = {
                    ['setting'] = 'Ignore',
                    ['name'] = 'Defiant',
                },
            },
            ['name'] = 'Defiant',
        },
        ['Ornament'] = {
            ['items'] = {},
            ['category'] = '',
            ['conditions'] = {
                [1] = {
                    ['setting'] = 'Ignore',
                    ['name'] = 'Ornament',
                },
            },
            ['name'] = 'Ornament',
        },
    },
    ['preferences'] = {},
    ['items'] = {
        ['Descending Moon Idol of Adroitness'] = {
            ['setting'] = 'Keep',
        },
        ['Twisted Gorilla Hand'] = {
            ['setting'] = 'Keep',
        },
        ['Chainmail Collar Template Pattern'] = {
            ['setting'] = 'Sell',
        },
        ['Engineer\'s Toolbox'] = {
            ['setting'] = 'Destroy',
        },
        SHORTENED HERE AS THERE ARE 1000s more items.

Toon File

Code:

do local _ = {
   settings = {},
   items = {},
   save = {},
   ['rules'] = {
      {
          name = "Defiant",
          enabled = true,
      },
      {
         name = "Ornament",
         enabled = true,
     },
  },
}
return _
end

KingArthur · Mar 28, 2024

Cannonballdex said:

Not sure what is different here, figured I would share my files as a reference. I am ignoring all Defiant and Ornaments.

Code:

return {
    ['categories'] = {},
    ['functions'] = {},
    ['settings'] = {
        ['save_slots'] = 3,
        ['always_loot'] = true,
        ['unmatched_item_rule'] = {
            ['setting'] = 'Keep',
        },
    },
    ['rules'] = {
        ['Defiant'] = {
            ['items'] = {},
            ['category'] = '',
            ['conditions'] = {
                [1] = {
                    ['setting'] = 'Ignore',
                    ['name'] = 'Defiant',
                },
            },
            ['name'] = 'Defiant',
        },
        ['Ornament'] = {
            ['items'] = {},
            ['category'] = '',
            ['conditions'] = {
                [1] = {
                    ['setting'] = 'Ignore',
                    ['name'] = 'Ornament',
                },
            },
            ['name'] = 'Ornament',
        },
    },
    ['preferences'] = {},
    ['items'] = {
        ['Descending Moon Idol of Adroitness'] = {
            ['setting'] = 'Keep',
        },
        ['Twisted Gorilla Hand'] = {
            ['setting'] = 'Keep',
        },
        ['Chainmail Collar Template Pattern'] = {
            ['setting'] = 'Sell',
        },
        ['Engineer\'s Toolbox'] = {
            ['setting'] = 'Destroy',
        },
        SHORTENED HERE AS THERE ARE 1000s more items.

Toon File

Code:

do local _ = {
   settings = {},
   items = {},
   save = {},
   ['rules'] = {
      {
          name = "Defiant",
          enabled = true,
      },
      {
         name = "Ornament",
         enabled = true,
     },
  },
}
return _
end

Though the structure seems the same, but still a big thanks and I will try this later(one rule with one condition of item and maybe the condition name should be the same as the rule name?)

KingArthur · Mar 28, 2024

@Cannonballdex btw, do you tried this on the LS content plz?

KingArthur · Mar 30, 2024

Cannonballdex said:

Not sure what is different here, figured I would share my files as a reference. I am ignoring all Defiant and Ornaments.

Code:

return {
    ['categories'] = {},
    ['functions'] = {},
    ['settings'] = {
        ['save_slots'] = 3,
        ['always_loot'] = true,
        ['unmatched_item_rule'] = {
            ['setting'] = 'Keep',
        },
    },
    ['rules'] = {
        ['Defiant'] = {
            ['items'] = {},
            ['category'] = '',
            ['conditions'] = {
                [1] = {
                    ['setting'] = 'Ignore',
                    ['name'] = 'Defiant',
                },
            },
            ['name'] = 'Defiant',
        },
        ['Ornament'] = {
            ['items'] = {},
            ['category'] = '',
            ['conditions'] = {
                [1] = {
                    ['setting'] = 'Ignore',
                    ['name'] = 'Ornament',
                },
            },
            ['name'] = 'Ornament',
        },
    },
    ['preferences'] = {},
    ['items'] = {
        ['Descending Moon Idol of Adroitness'] = {
            ['setting'] = 'Keep',
        },
        ['Twisted Gorilla Hand'] = {
            ['setting'] = 'Keep',
        },
        ['Chainmail Collar Template Pattern'] = {
            ['setting'] = 'Sell',
        },
        ['Engineer\'s Toolbox'] = {
            ['setting'] = 'Destroy',
        },
        SHORTENED HERE AS THERE ARE 1000s more items.

Toon File

Code:

do local _ = {
   settings = {},
   items = {},
   save = {},
   ['rules'] = {
      {
          name = "Defiant",
          enabled = true,
      },
      {
         name = "Ornament",
         enabled = true,
     },
  },
}
return _
end

I've noticed that your toon file is a bit different from mine regarding on structure, even they should be same effect though.

Mine was like:

Code:

return {
    ['settings'] = {
          unmatched_item_rule = {
            setting = 'Keep',
        },
    },
    ['items'] = {},
    ['save'] = {},
    ['rules'] = {
        {
            name = 'Farm',
            enabled = true,
        },
    },
}

the return is very similar, but I've tested both structure, and none of them works on customized rules...sad=(

fuddles · Apr 5, 2024

fuddles updated (YALM) Yet Another Loot Manager with a new update entry:

0.10.1

Commits

Updated items.zip file

Click to expand...

(b3fe366) ~Nathan

Updates

Click to expand...

(c43951f) ~Nathan

Updates

Click to expand...

(581256d) ~Nathan

Read the rest of this update entry...

fuddles · Apr 5, 2024

I've updated the items.db file for the new expansion. You'll have to manually unzip it as I haven't figured out how to automatically do it.

GitHub - MrKumaPants/yalm

Contribute to MrKumaPants/yalm development by creating an account on GitHub.

github.com

Also set up for auto release from git, so people can submit pull requests.

KingArthur · Apr 5, 2024

Thank you sir for the hardworking!! Somehow the collectibles of LS seems not included into the new db file yet

fuddles · Apr 7, 2024

fuddles updated (YALM) Yet Another Loot Manager with a new update entry:

0.11.0

Commits

Updated items.zip file

Click to expand...

(75d6e77) ~Nathan

Read the rest of this update entry...

Klunk · Apr 8, 2024

So with this can i set so each person loots the correct amour drop for them?

fuddles · Apr 8, 2024

Klunk said:
So with this can i set so each person loots the correct amour drop for them?

Yes

Klunk · Apr 8, 2024

cool thanks

fuddles · Apr 10, 2024

fuddles updated (YALM) Yet Another Loot Manager with a new update entry:

0.11.1

Commits

PR # [1](https://github.com/MrKumaPants/yalm/pull/1): tribute fixes

Click to expand...

(eb4f183) ~Nathan

+ tribute fixes

Click to expand...

(ee80849) ~a_moss_snake

Read the rest of this update entry...

KingArthur · Apr 12, 2024

Absolutely my favorite looting script, the customized conditions is a game-changer in terms of looting imo.

fuddles · Apr 13, 2024

fuddles updated (YALM) Yet Another Loot Manager with a new update entry:

0.11.2

Commits

Added condition name to item pass string

Click to expand...

(fe6a847) ~Nathan

Read the rest of this update entry...

fuddles · Apr 14, 2024

fuddles updated (YALM) Yet Another Loot Manager with a new update entry:

0.11.4

Commits

Fixed error message and added Write.Inspect

Click to expand...

(27f2d2b) ~Nathan

Added NoDrop item function and error

Click to expand...

(22f8744) ~Nathan

Read the rest of this update entry...

fuddles · Apr 14, 2024

fuddles updated (YALM) Yet Another Loot Manager with a new update entry:

0.12.0

Commits

Now uses mq2linkdb to generate database

Click to expand...

(d113f0d) ~Nathan

Fixed error message

Click to expand...

(a6ba415) ~Nathan

Read the rest of this update entry...

fuddles · Apr 15, 2024

fuddles updated (YALM) Yet Another Loot Manager with a new update entry:

0.12.1

Bug Fixes

Fixed nodrop

Click to expand...

(7bbc09d) ~Nathan

Read the rest of this update entry...

fuddles · Apr 15, 2024

fuddles updated (YALM) Yet Another Loot Manager with a new update entry:

0.12.2

Commits

Added log_level setting

Click to expand...

(d523bdc) ~Nathan

Read the rest of this update entry...

fuddles · Apr 16, 2024

fuddles updated (YALM) Yet Another Loot Manager with a new update entry:

0.12.3

Commits

Workaround for lore equip items returning wrong ID from advloot

Click to expand...

(75b13e5) ~Nathan

Read the rest of this update entry...

fuddles · Apr 16, 2024

fuddles updated (YALM) Yet Another Loot Manager with a new update entry:

0.12.6

Performance

Performance improvement

Click to expand...

(46cef0a) ~Nathan

Performance improvement

Click to expand...

(2f09706) ~Nathan

Commits

Syntax error

Click to expand...

...

Read the rest of this update entry...

fuddles · Apr 18, 2024

fuddles updated (YALM) Yet Another Loot Manager with a new update entry:

0.12.7

Commits

PR # [4](https://github.com/MrKumaPants/yalm/pull/4): AugSlot1 and added lore/loreequip tag in Item.lua

Click to expand...

(c34a9a5) ~Nathan

Fixed AugSlot1 and added lore/loreequip tag in Item.lua

The new funcs are in alphabet order now.

Click to expand...

(6b0fa3f) ~EQKA-Pmac

Read the rest of this update entry...

DraexSZ · Apr 27, 2024

What am I doing wrong here? Instead of destroying them, it just times out and leaves them on corpse.

Release (YALM) Yet Another Loot Manager 0.12.7

Seasoned veteran member

kicks you for 69420 points of dmg!

Master Tinkerer

kicks you for 69420 points of dmg!

Master Tinkerer

Well-known member

Commits​

Well-known member

Well-known member

Commits​

Well-known member

Well-known member

Well-known member

Well-known member

Commits​

Well-known member

Commits​

Well-known member

Commits​

Well-known member

Commits​

Well-known member

Bug Fixes ​

Well-known member

Commits​

Well-known member

Commits​

Well-known member

Performance ​

Commits​

Well-known member

Commits​

Member

Users who are viewing this thread

Cart

Commits

Commits

Commits

Commits

Commits

Commits

Bug Fixes

Commits

Commits

Performance

Commits

Commits