{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigu2vonte4yaldtvokr37flzyzntqexhuahtdcabkxcyup7lbryoy",
    "uri": "at://did:plc:pvz7ox4x2ehjiezsahttqyyz/app.bsky.feed.post/3mk7ibe7jjbl2"
  },
  "path": "/viewtopic.php?p=450717#p450717",
  "publishedAt": "2026-04-24T01:37:52.000Z",
  "site": "https://forum.luanti.org",
  "tags": [
    "Nathan.S"
  ],
  "textContent": "I don't impose a max distance, but it looks like Luanti must have started doing that. I get this error now if I'm about 13 nodes away.\n\nCode:\n\n\n    2026-04-23 20:18:15: ACTION[Server]: Player singleplayer tried to access inventory from too far: d=126.966, max_d=100; ignoring.\n\nIt worked before, so I'm not sure what changed, or why..... I don't see an anti-cheat setting for it. I took a brief look through the open and closed issues on Github and don't see anything that immediately looks like something that would have effected this. I don't see anything in the .conf file or in the mod api that looks like this value can be changed. Nothing mentioned in breaking changes either. I'll have to ask around about this. I'm pretty positive it worked before, 'cause I remember having issues with getting the inventory to even display and had to do some workarounds for that.\n\nEdit:\nMaybe I'm just retarded and never actually tested that you could interact with the inventory... Not sure what the point of being able to see an inventory is if you are too far away to interact with it. Changing the range of the remote, that would be the pointing range, does change how far away I can be from the system and interact with the inventory. The trouble with setting that to something stupid high is anytime you wield it it calculates which node you are pointing at, which I think is computationally expensive, and not very recommended. I don't see any option available to change this on a per inventory basis. I would have to change to either player connected inventories and detached inventories, both of which would require reworking a large portion of the code. I'll try and look into some things, but I'm super busy with some commissioned work right now. (Actually some very similar to this, and I was using the same backend system, which now I need to change there because this clearly doesn't work)\n\nStatistics: Posted by Nathan.S — Fri Apr 24, 2026 01:37\n\n* * *",
  "title": "WIP Mods • Re: [mod] Automated Storage & Retrieval System [asrs]",
  "updatedAt": "2026-04-24T01:37:52.000Z"
}