Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.

Not sure if this update addressed the errors I just uploaded. After downloading the update it ran for much longer before erroring out.aquietone updated lootnscoot (for emu) with a new update entry:
12/03/2025
Read the rest of this update entry...

rgmercs starts lootnscoot for you from its own location outside of rgmercs with commandDid I read somewhere that RGMercs calls a version of LootnScoot from it's own directory?
/lua run lootnscoot directed rgmercsLetting rgmercs manage itrgmercs starts lootnscoot for you from its own location outside of rgmercs with command/lua run lootnscoot directed rgmercs
When you toggle DoLoot to on, it first stops lootnscoot if its already running, then starts it with the above command.
from the screenshots you're pasting they aren't really telling anything useful except that in most cases lootnscoot is exiting normally (status 0).
are you trying to run lootnscoot yourself at all or just leaving it to rgmercs to manage it?
It's defiantly running much better before the last patch the program would crash within looting 10 mobs now I can pull and entire zone and only crash once or twice when looting.rgmercs starts lootnscoot for you from its own location outside of rgmercs with command/lua run lootnscoot directed rgmercs
When you toggle DoLoot to on, it first stops lootnscoot if its already running, then starts it with the above command.
from the screenshots you're pasting they aren't really telling anything useful except that in most cases lootnscoot is exiting normally (status 0).
are you trying to run lootnscoot yourself at all or just leaving it to rgmercs to manage it?


Having some problems with LootNScoot
1. LootNScoot crashes after pulling 3 or 4 mobs even on characters that do not have looting enabled.
2. I have an item configured for quest|1 , but when my first toon looed he got all 4. Did I misunderstand the |1 after quest?
View attachment 73001
I think this is the output you are looking for the item marked a quest|1 but got looted 4 timeshave any output from it crashing? for quest there should be output in the LNS console about the decisions its making.

Looks like that's happening because multiple of the same item on 1 corpse. It evaluates the rule and makes decision to keep because 0 < 1 initially. Then it keeps looting multiple of the item from the corpse based on that initial decision. It does check the updated count you have on each item looted, but appears to only be for logging purposes at that point.I think this is the output you are looking for the item marked a quest|1 but got looted 4 times
View attachment 73140

See above posts from drawthow which are all about that, he made some workaround here https://www.redguides.com/community/posts/656614/ but if you have some kind of info on how to reproduce this i'd try to look into it, like what is happening when it happens to exit?I just came back to Project Lazarus after a year and getting reacclimated to RGMercs + new LootNScoot. I'm experiencing an odd condition where LootNScoot will... just stop/exit at seemingly random times on all of my characters. I only notice it's not running because one of the loot macros on a character will produce a command error. Otherwise I don't get any other MQ messages or obvious indicators about the lua crashing or stopping. Once I restart it on the characters (using the directed rgmercs command) it will resume normally for another period of time before stopping. Any ideas on what might be happening?
Thanks I missed this other thread. I can't really say how or why it happens, but as drawthow points out it seems to exit cleanly. For now I've also added the restart command to the lootnscoot.Lua file in rgmercs\modules. If there was a way to monitor the MQ chat window with MQ2Events, I could probably run the Lua restart based on the "LNS not running!" log message but I don't think that's possible.See above posts from drawthow which are all about that, he made some workaround here https://www.redguides.com/community/posts/656614/ but if you have some kind of info on how to reproduce this i'd try to look into it, like what is happening when it happens to exit?
After this update I have been able to run for just a little over an hr. without crashing. Before this update characters would only run for between 3 and 20 loots before crashing.aquietone updated lootnscoot (for emu) with a new update entry:
12/10/2025
Read the rest of this update entry...
the only change here was to add a line when the script exits to say why it's exiting. do you see that print?Are there any
After this update I have been able to run for just a little over an hr. without crashing. Before this update characters would only run for between 3 and 20 loots before crashing.
The only time I see that message is when I'm shutting down RGMercs.the only change here was to add a line when the script exits to say why it's exiting. do you see that print?
Commits
PR # [63](https://github.com/aquietone/lootnscoot/pull/63): split up init.lua into ui, db, actor, settings
- Maybe fixed CTD errors. Ran under debug build and fixed a bunch of random imgui errors popping up.
- Maybe fixed script randomly exiting. Seemed to occur mostly when both a modify and add rule actor message are sent when setting a rule from new item table.
- Fixed removing entries in restock list.
- Refactored a bunch so probably broke everything...
This one should be fixed.I just did get a crash rom deleting the Iron ration and the water flask from the buy table. Happened on multiple people.
View attachment 73509
May or may not be improved not really sure.Are there any
After this update I have been able to run for just a little over an hr. without crashing. Before this update characters would only run for between 3 and 20 loots before crashing.
Worked around the crash for now, issue here https://github.com/macroquest/macroquest/issues/953Just happened again, this time with a different boss, different item. Same symptoms, 100% reproduce rate.
I reverted #61 (the last update) locally and was able to loot the corpse without issue.
Edit: It occurs to me the first item today when I was crashing was also a weapon augment with a skill mod.
View attachment 73229
The update mentioned above hasn't released yet. That message you keep showing is also printed by rgmercs, not LNS, and offers no useful info about what might be up with LNS.Just crashed while looting got this error.
Sorry I posted it because that was the first time I had seen an error number. Thought it may be helpful.The update mentioned above hasn't released yet. That message you keep showing is also printed by rgmercs, not LNS, and offers no useful info about what might be up with LNS.
Commits
(6c7fa73) ~aquietoneAvoid item.DMGBonusType crash for now and loot non-lore items before lore items
lootnscoot/modules/db.Lua line 717 change actors.send to actors.Send
dgg is the same as dgga. are you sure it wasn't some other part of the command failing to parse? a screenshot of the command / error would helpAfter the last update, I've noticed when I goto group Sell stuff it fails. In the MQ window I see it states cannot parse. And I see the error is a missing A. It has /dgg /multi-line /tar.... etc etc. So I made a quick key /dgga /tar etc etc.... and that works fine. Just thought I'd let someone know.
