RedM Crayfish Troubleshooting

Start here

Two lines should appear in your server console when the resource starts:

[rm_crayfish] framework: VORP Core
[rm_crayfish] v1.0.0 ready — 33 of 43 bed(s) seeded

Then, in game:

/crayfish_ping

Between those three things, almost every problem names itself. Most of this page is about reading what they say.

The server console, not F8

Nearly every diagnostic prints server-side. Lines like Creating script environments and ResourceCache are the client console, and the server's output will not be in there.

The first line is wrong

It says Standalone on a framework server

The probe did not find your framework — usually because rm_crayfish started before it. Move ensure rm_crayfish below your framework in server.cfg, or stop it guessing:

-- local/overrides.lua
RmCrayfish.Local = { bridge = { framework = 'vorp' } },

Fix this first

Standalone runs bare-handed and grants no items, so everything after this looks broken in ways that have nothing to do with the real cause.

It says running bare-handed on RedEM:RP

[rm_crayfish] RedEM:RP inventory is missing count, add — running bare-handed

Your inventory build spells its methods differently to the ones probed for. Beds still work; they just stop asking for a lure and stop granting the crayfish. The names it did find are printed on the line above. See Installing on RedEM:RP.

Neither line appears at all

The server side never ran. Check for an error further up the console — a resource that failed earlier can take others with it. Also check you do not have two copies of rm_crayfish in your resources folder.

Nothing happens at a bed

Symptom	Cause
No prompt at all	Are you crouched? Nothing appears until you are. Then check the bed is stocked with /crayfish
Prompt is greyed out	The bed is resting or empty. That is correct behaviour — it greys rather than vanishing so you know to come back. /crayfish_fill to test
Prompt only right on top of the hole	Raise the interaction radius: bedDefaults = { reach = 3.5 }
No dirt piles anywhere	They stream in at 50m. Beds 1–12 are natural holes with no prop by design — try /crayfish_warp 13

The lure book

It opens empty

You are carrying none of the eleven lures, or your item names differ from the ones in config/lures.lua. Check what your items table actually calls them and map the difference rather than editing config:

RmCrayfish.Local = {
    bridge = { itemAliases = { consumable_bread = 'bread' } },
}

It never opens — the animation starts immediately

The framework line says Standalone. Bare-handed beds skip the book. See above.

The cursor is stuck after closing it

This should be impossible — Escape, clicking outside, and picking a lure all release focus. If you hit it, note exactly what you did and report it. Restart the resource to recover.

A harvest completes but no item arrives

The inventory resource was not restarted after the item was added. This is the most common install mistake by a wide margin. They all cache the item table at start-up and will not see a new row until they restart.

restart vorp_inventory

If that is not it, the item name is wrong. The server console prints the payout either way, because as far as the resource is concerned it handed the item over — so a payout line with nothing in your bags means the inventory rejected it, not that the harvest failed.

Check the row exists, and that it matches what config/beds.lua calls yield:

SELECT * FROM `items` WHERE `item` = 'p_crawdad01x';

Requests fail

did not answer in time / no reply in 10000ms

The request never reached the server, or the server never answered. Run /crayfish_ping. If that also fails, the server side is not running — see neither line appears.

failed on the server followed by a reason

The server refused and told you why. The reason is the answer — a handler that threw, or one that was never registered because server/boot.lua did not finish loading. Look further up the server console for the error that stopped it.

rpcTimeoutMs is 10, which is shorter than any round trip

You have read a millisecond setting as seconds. A round trip is 20–40ms on localhost and 150ms across the internet, so a 10ms timeout gives up before any answer can physically arrive. It should be 10000.

The same mistake catches noticeMs — at 30 your notices vanish faster than a frame draws. Both settings carry Ms in the name for this reason.

You do not have permission to do that

The server console prints exactly what it checked:

[rm_crayfish] refused Kiran (id 1) tried crayfish_fill: you do not have permission
[rm_crayfish]          framework  VORP Core
[rm_crayfish]          they hold  user
[rm_crayfish]          allowed    admin  or ace rm_crayfish.staff

Usual causes:

• VORP: you ran /addGroup but did not relog. The group loads with your character.
• You are not on a character yet.
• admin.enabled = false in your overrides — the refusal reads staff commands are switched off on this server instead.

The quickest fix that works everywhere is the ace:

add_ace group.admin rm_crayfish.staff allow

The overlay

Symptom	Cause
Panel blank, cursor stuck	web/dist is missing from the package
Progress bar looks empty	Report it — the fill draws over the stone, and an empty trough means it is being covered
Text overflows the panel	Report it with your resolution. The UI is sized in vw and tested at 1080p and 1440p

Other

Props left in the world after stopping the resource. Should be impossible — every prop is swept on stop. Report it.

Two players on one bed both get it. Should be impossible — solitude is checked on the server. Report it with both players' distance from the bed.

Beds never restock. The clock is reported by clients. On an empty server nothing reports, so the day/night state holds at whatever it last knew. It resolves as soon as a player is on.

Reporting something

Include:

1. The two start-up lines from the server console
2. The output of /crayfish_ping
3. Your framework and inventory resource
4. What you changed in local/overrides.lua

With debug = { enabled = true } in your overrides and a restart, the console also prints every override that actually applied — which rules out "the setting never took" before anyone starts looking at code.

Then open a ticket in Discord.