RedM Crayfish

Crayfish beds worth walking to.

Holes stock and empty on the world clock, the lure you drop in decides your odds, and every one of those decisions is taken on the server. A React overlay handles the lure book and the progress meter.

VORP RSG RedEM:RP Standalone

What it does

• 43 beds across Bayou Nwa, Lagras and Lakay. Twelve sit on holes the map already models; the rest are marked with a dirt pile so they can be found.
• Seeded per server. Each bed rolls once at start-up against its seed chance, so no two servers have crayfish in exactly the same holes.
• Day and night stocking. Every bed re-rolls on a timer — 28 minutes by day, 20 by night — against separate day and night odds.
• Lures that matter. Fresh meat pulls at 100, spoiled at 50, vegetables at 30. The roll happens on the server, so the numbers on the cards are the real ones.
• Crouch to work a hole — the same gesture the vanilla holes use. The prompt appears within reach of a bed, 2.5m by default.
• Cooldowns per bed, two hours by default, whether the pull landed or not.

Frameworks

Runs on VORP, RSG, RedEM:RP or standalone. It works out which at start-up by looking at what is actually running, and prints what it found:

[rm_crayfish] framework: VORP Core

Pin it in local/overrides.lua if you would rather it did not guess:

bridge = { framework = 'rsg' },   -- vorp | rsg | redemrp | standalone | auto

	Inventory	Staff permission
VORP	vorp_inventory	users.group or characters.group, or ace
RSG	rsg-inventory	HasPermission(src, 'admin'), or ace
RedEM:RP	redemrp_inventory	player group, or ace
Standalone	none — beds run bare-handed	ace only

Nothing outside server/adapters/ and client/adapters/ knows which one is in use.

Standalone has no inventory to spend a lure from or put a crayfish into, so beds fall back to bare-handed and a pull says what it would have given you. Every other rule — distance, cooldown, solitude, the server-side roll — is untouched, which makes it a fair way to demo the resource.

Requests don't use the framework's callback system

All three frameworks have one, all spelled differently, and standalone has none — so the resource carries its own over plain net events. It also times out, which a framework callback does not: a reply that never arrives becomes an ordinary refusal instead of a harvest thread parked forever.

How a pull works

The split between client and server is the whole design, so it is worth stating:

1. The client asks which lures the player is carrying. The server answers from their real inventory.
2. The player picks one. The client asks the server to open the bed with it.
3. The server checks the distance itself, checks the bed is stocked and off cooldown, checks nobody else is stood on it, checks the player really holds that lure — then spends the lure, rolls the outcome, starts the cooldown and returns a one-shot ticket.
4. The client plays the animation for as long as the server said.
5. The client hands the ticket back. Only then does it find out what it caught.

A modified client that skips straight to step 5 saves itself five seconds and learns nothing: the roll already happened, and it gets whatever the server rolled while it was pretending to dig. A replayed ticket finds nothing, because redeeming one consumes it.

Requirements

Nothing. No utility library, no progress-bar resource, no ox_lib, no external fonts, no CDN scripts.

The overlay ships pre-built in web/dist, so nothing needs installing to run it. Node is only needed if you want to change the UI.

There is deliberately no dependencies{} block

Naming one framework in the manifest would stop the resource starting on the other three.

The reward item p_crawdad01x and every lure must exist in your framework's item table — that is what Installation covers. Standalone skips it entirely.

Languages

en English · de Deutsch · es Español · fr Français · ja 日本語 · nl Nederlands · ru Русский

-- local/overrides.lua
RmCrayfish.Local = { language = 'de' },

Documentation

Page	What's in it
Installation	Pick your framework — each page is short
Item Icons	The twelve-icon pack and where it goes
Configuration	Every setting, and how to balance the odds
Commands	Staff commands, and adding your own beds
Troubleshooting	Symptom to cause to fix

Checking it works

/crayfish_ping

Answers with your framework, whether an inventory was found, and how many beds seeded. It touches no framework, no inventory and no bed, so a reply proves the resource is running and talking to itself properly.

Support

• 💬 Discord: https://discord.gg/w4Ew4k3Exn
• 🛒 Store: https://redmorrow.com/products/redm-crayfish