Commands

All of these are staff-only, checked on the server. An ordinary player typing one gets a refusal and nothing else.

Getting permission

Either works — both are checked, and the server console always passes.

An ace, which works on every framework:

add_ace group.admin rm_crayfish.staff allow

Or your framework's own groups:

VORP	/addGroup <server id> admin, then relog — VORP loads your group when your character does
RSG	/addpermission <server id> admin
RedEM:RP	Set the player's group to admin
Standalone	Ace only

Change the accepted group names with admin.groups in your overrides.

The commands

Command
/crayfish	Nearest bed — what your client believes next to what the server holds
/crayfish_here	Prints the line to paste into config/beds.lua for where you stand
/crayfish_warp <id>	Teleport to a bed by number
/crayfish_fill	Stock every bed and clear every cooldown
/crayfish_dump	Print the whole registry to the server console
/crayfish_ping	Check the server is answering, and what it has bound

crayfish_fill and crayfish_dump also work from the server console without the slash.

Adding your own beds

This is the one most people want.

1. Stand exactly where you want the hole.

2. Run:

/crayfish_here

It prints a ready-to-paste line, and warns you if an existing bed is within five metres:

[rm_crayfish] paste into config/beds.lua:
	{ 2193.2842, -1263.8918, 40.4100 },
  add `mound = false` if it sits on a hole the map already models

3. Paste it into local/overrides.lua under addBeds, so it survives updates:

RmCrayfish.Local = {
    addBeds = {
        { 2193.2842, -1263.8918, 40.4100 },
        { 1234.5678,  -987.6543, 40.5000, rest = 60 },
    },
}

4. Restart the resource.

Anything you leave out falls back to BedDefaults, so three coordinates is a complete entry. Add mound = false if the spot already has a crayfish hole modelled into the map — otherwise a dirt pile is dropped so players can find it.

Every field is listed in Configuration.

Patching a shipped bed

Beds are addressed by their position in config/beds.lua:

RmCrayfish.Local = {
    beds = {
        [13] = { seed = 100, rest = 45 },
    },
}

Use addBeds for new beds

Inserting into the shipped list shifts every override below the insertion point by one.

Checking an install

/crayfish_ping

[rm_crayfish] answered in 12ms
  version    1.0.0
  framework  VORP Core
  inventory  yes
  beds       33 seeded
  you are    staff

This touches no framework, no inventory and no bed, so an answer proves the resource is running and talking to itself properly. If it does not answer, see Troubleshooting.

/crayfish

Reports the nearest bed twice — once as your client sees it, once as the server holds it. They should agree. If it says they disagree, note what you did just before it and report that.

Testing without waiting

The shipped odds mean a bed has a 45% chance of holding anything by day, and a two hour cooldown once worked. Testing a change against that takes all evening.

/crayfish_fill

Stocks every bed and clears every cooldown. Run it again whenever a test leaves the map picked clean.

Pair it with /crayfish_warp 13 to jump straight to a dirt-pile bed, or /crayfish_warp 1 for one of the natural holes.