Yes the script exits.
you can try replace lootnscoot/init.Lua with this which just puts a try/catch around the entire main loop and see if it happens to catch anything
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.

Yes the script exits.
I'm playing on Might tonight same thing is happening. Here are the last few lines before lootnscoot exited.did you try with debug on so that it would log to the mq console?
I didn't see this message before the last post I did. Will give it a try.you can try replace lootnscoot/init.lua with this which just puts a try/catch around the entire main loop and see if it happens to catch anything
Here is the latest log with the try/catch code. Three toons exited at the same time.
Bigbooper log
[2026/01/15 20:59:33] [LootnScoot] [20:59:33] (actor.lua::337) [DEBUG] :: Action: addrule Who: Maddog Lookup: loot.RegisterActors() ItemID: 37016 Rule: Ask Classes: All Event: Received message Link: 009098000000000000000000000000000000000000000000CCBDAFEASmall Gear #3 Directions: NULL LNS_Mode: directed
[2026/01/15 20:59:33] [LootnScoot] [20:59:33] (db.lua::374) [DEBUG] :: SQL Query: SELECT * FROM Items WHERE item_id = 37016 ORDER BY name ASC
[2026/01/15 20:59:33] [LootnScoot] [20:59:33] (actor.lua::337) [DEBUG] :: Action: addrule Who: Maddog Lookup: loot.RegisterActors() ItemID: 37016 Rule: Ask Classes: All Event: Received message Link: 009098000000000000000000000000000000000000000000CCBDAFEASmall Gear #3 Directions: NULL LNS_Mode: directed
[2026/01/15 20:59:33] [LootnScoot] [20:59:33] (actor.lua::434) [DEBUG] :: Action: new Who: Maddog Lookup: loot.RegisterActors() ItemID: 37016 Rule: Ask Classes: All Event: Received message Link: 009098000000000000000000000000000000000000000000CCBDAFEASmall Gear #3 Directions: NULL LNS_Mode: directed
[2026/01/15 20:59:33] [LootnScoot] [20:59:33] (init.lua::1600) [DEBUG] :: Link for 37016 ALREADY MATCHES 009098000000000000000000000000000000000000000000CCBDAFEASmall Gear #3
[2026/01/15 20:59:33] Ending lua script 'lootnscoot' with PID 48 and status 0
[2026/01/15 20:59:42] [RGMercs:ERROR <51044.806> (lootnscoot.lua::unknown_func():262 )] >>> [LOOT]: Looting is enabled, but LNS does not appear to be running!
[2026/01/15 20:59:42] [ -->(all) ] group_EQMight_Traken Bigbopper has looting enabled, but LNS does not appear to be running!
[2026/01/15 21:00:01] [ fazilmere (all) ] group_EQMight_Traken Fazilmere has looting enabled, but LNS does not appear to be running!
[2026/01/15 21:00:28] [ milbena (all) ] group_EQMight_Traken Milbena has looting enabled, but LNS does not appear to be running!
Fazilmere log
[2026/01/15 20:59:05] Target cleared.
[2026/01/15 20:59:33] [LootnScoot] [20:59:33] (actor.lua::337) [DEBUG] :: Rule: Ask Classes: All Who: Maddog Lookup: loot.RegisterActors() LNS_Mode: directed Action: addrule Link: 009098000000000000000000000000000000000000000000CCBDAFEASmall Gear #3 Directions: NULL Event: Received message ItemID: 37016
[2026/01/15 20:59:33] [LootnScoot] [20:59:33] (db.lua::374) [DEBUG] :: SQL Query: SELECT * FROM Items WHERE item_id = 37016 ORDER BY name ASC
[2026/01/15 20:59:33] [LootnScoot] [20:59:33] (actor.lua::337) [DEBUG] :: Rule: Ask Classes: All Who: Maddog Lookup: loot.RegisterActors() LNS_Mode: directed Action: addrule Link: 009098000000000000000000000000000000000000000000CCBDAFEASmall Gear #3 Directions: NULL Event: Received message ItemID: 37016
[2026/01/15 20:59:33] [LootnScoot] [20:59:33] (actor.lua::434) [DEBUG] :: Rule: Ask Classes: All Who: Maddog Lookup: loot.RegisterActors() LNS_Mode: directed Action: new Link: 009098000000000000000000000000000000000000000000CCBDAFEASmall Gear #3 Directions: NULL Event: Received message ItemID: 37016
[2026/01/15 20:59:33] [LootnScoot] [20:59:33] (init.lua::1600) [DEBUG] :: Link for 37016 ALREADY MATCHES 009098000000000000000000000000000000000000000000CCBDAFEASmall Gear #3
[2026/01/15 20:59:33] Ending lua script 'lootnscoot' with PID 37 and status 0
[2026/01/15 20:59:42] [ bigbopper (all) ] group_EQMight_Traken Bigbopper has looting enabled, but LNS does not appear to be running!
[2026/01/15 21:00:01] [RGMercs:ERROR <51063.506> (lootnscoot.lua::unknown_func():262 )] >>> [LOOT]: Looting is enabled, but LNS does not appear to be running!
[2026/01/15 21:00:01] [ -->(all) ] group_EQMight_Traken Fazilmere has looting enabled, but LNS does not appear to be running!
[2026/01/15 21:00:28] [ milbena (all) ] group_EQMight_Traken Milbena has looting enabled, but LNS does not appear to be running!
Milbena
[2026/01/15 20:59:33] [LootnScoot] [20:59:33] (actor.lua::337) [DEBUG] :: Lookup: loot.RegisterActors() Event: Received message Action: addrule Directions: NULL Who: Maddog LNS_Mode: directed ItemID: 37016 Rule: Ask Classes: All Link: 009098000000000000000000000000000000000000000000CCBDAFEASmall Gear #3
[2026/01/15 20:59:33] [LootnScoot] [20:59:33] (db.lua::374) [DEBUG] :: SQL Query: SELECT * FROM Items WHERE item_id = 37016 ORDER BY name ASC
[2026/01/15 20:59:33] [LootnScoot] [20:59:33] (init.lua::1600) [DEBUG] :: Link for 37016 ALREADY MATCHES 009098000000000000000000000000000000000000000000CCBDAFEASmall Gear #3
[2026/01/15 20:59:33] [LootnScoot] [20:59:33] (actor.lua::337) [DEBUG] :: Lookup: loot.RegisterActors() Event: Received message Action: addrule Directions: NULL Who: Maddog LNS_Mode: directed ItemID: 37016 Rule: Ask Classes: All Link: 009098000000000000000000000000000000000000000000CCBDAFEASmall Gear #3
[2026/01/15 20:59:33] [LootnScoot] [20:59:33] (actor.lua::434) [DEBUG] :: Lookup: loot.RegisterActors() Event: Received message Action: new Directions: NULL Who: Maddog LNS_Mode: directed ItemID: 37016 Rule: Ask Classes: All Link: 009098000000000000000000000000000000000000000000CCBDAFEASmall Gear #3
[2026/01/15 20:59:33] Ending lua script 'lootnscoot' with PID 21 and status 0
[2026/01/15 20:59:43] [ bigbopper (all) ] group_EQMight_Traken Bigbopper has looting enabled, but LNS does not appear to be running!
[2026/01/15 21:00:01] [ fazilmere (all) ] group_EQMight_Traken Fazilmere has looting enabled, but LNS does not appear to be running!
[2026/01/15 21:00:27] [RGMercs:ERROR <51089.954> (lootnscoot.lua::unknown_func():262 )] >>> [LOOT]: Looting is enabled, but LNS does not appear to be running!
[2026/01/15 21:00:27] [ -->(all) ] group_EQMight_Traken Milbena has looting enabled, but LNS does not appear to be running!
Commits
...Attempt some fixes for LNS exiting
- Create prepared statement up front for item lookup by ID
- Skip checking wildcard rule when looking up item after receiving addrule actor message
- Consolidate addrule messages for normal and global rules when AlwaysGlobal is enabled
- Skip item lookup after addrule actor message on toon who sent the message
- Pass itemLink into lookupLootRule after addrule actor message for less unnecessary link lookups
Commits
...Few actor and db related changes
- Skip addrule/deleterule message in LNS.modifyItemRule when called from LNS.AddNewItem
- Include rule sections of addrule/deleterule message into new item message
- Enter actor callback addrule/deleterule logic on new item message
- Create prepared statements up front for get item link update item link
- Add check for AddNewtributes setting around adding rule on tribute item events

Again what the heck does it do other than cause you to ignore items that are set to ask?always global and global rules in general were a result of adding the option to re-evaluate based on current settings (old versions of LNS)
Honestly both really have no value anymore with personal rules tables and the fact we don't set sell based on thresholds we only use the thresholds to decide if we loot it in general. Same with AlwaysEval as that is no longer needed.
AlwaysAsk was there and I think I removed with while debugging, I've readded that and changed the check for it alwaysask or rule == ask
Yes, that is exactly what disabling that stuff does.So what was happening was with UseAutoRules disabled it was making everything ask that was a new item and setting the rule as ask forcing you to select.
Which is fine and dandy if you want it that way and why i don't mind it as a toggle, but it was defaulted to disabled which was confusing many as the items weren't getting assigned rules for them, and thus being left behind on corpses.
The issue with looting unintended items that were new should have been resolved a few patches ago as well.

I think autorules and alwaysask are about the same, just autorules applies to new items and alwaysask is all items.if you have alwaysask off and autorules on, if autorules decides not to loot an item, will you ever notice the items which get left behind dropped? i've never tried autorules before, what does it do with no drop items if you don't have loot no drop on? will auto rules set them to ask?
-- Handle AlwaysAsk setting
if settings.Settings.AlwaysAsk or lootRule == "Ask" then
newRule = true
lootDecision = "Ask"
To what algar said, for drawthow issue of the item set to sell but still asking, that was just because last night or this morning or something I put a GlobalItems instead of Global_Rules somewhere that it was passing the table name to use when upserting rule into the DB.Yes, that is exactly what disabling that stuff does.
Forces you to provide input.
The fact that it would leave items behind being a bad thing is a matter of perspective.
AQ1 or you or whoever is going to decide whatever it is you are going to decide and at the end of the day that is what it is
I just don't know why it was touted as a fix for an issue that doesn't really sound related.
I think like grim mentioned it dates back to some naming convention from ninjadvloot, but I've really no idea. My own usage of LNS is about as simple as possible. I just use the normal rules table. I don't use it for no drop items. I don't use it for no drop quest items.Cool deal
So is there an actual reason global vs standard exists when we already have personal rules?
I still do not get it.
I am not alone in this :3
Deleting everything from the personal table seems to fix this problem.After the updates from yesterday items in the database are being treated as new items. I don't have any way of verifying this but it seems like items entered into the db before yesterday and items put in yesterday or today have the problem.
Also increasing the lua turbo number from 500 to 1500 seems to solve the LNS ending randomly.
yeah the bug where you mentioned that it kept asking after you set the rule, was that it was accidentally throwing things into the personal table with rule set to Ask. that took precedence over the rules you were setting. It should be fixed now but you'd have to cleanup those personal Ask rules that got created.Deleting everything from the personal table seems to fix this problem.
