RedM Lantern Troubleshooting

First step, always

Config.Debug = true

Restart the resource and reproduce the problem. The console prints every state change and every failure reason:

[rm_Lantern] framework: vorp
[rm_Lantern] mode IDLE -> STOWED_PED
[rm_Lantern] saddle prop 939522 on bone 283 (ES_L_WeightBag0) pos vec3(...) rot vec3(...)
[rm_Lantern] attach point 11 refused the lantern, using cosmetic prop

That output answers most questions on its own. Turn it back off afterwards — it is noisy.

Nothing happens when I press the key

Check
Is the lantern in your hand?	The prompt only appears when there is something to do
Is it actually a lantern?	Only lantern weapons are recognised
Did you change CustomKey?	An unknown key name falls back to R, with a console warning
Another resource using R?	Try Config.Controls.UseCustomKey with a free key
Controls.UsePrompts = false?	Then there is no prompt — the key still works

I see two lanterns

This should not happen with default settings. If it does:

Config.RemoveWeaponOnHorse = true   -- must be true
Config.RemoveWeaponOnPlace = true   -- must be true

With either set to false the resource falls back to hiding the engine's copy of the lantern, which the engine does not reliably allow. The result is one lantern on the saddle or ground and a second on the player's belt.

The lantern floats next to the horse

The attach bone exists on the skeleton but there is nothing there to hang from. Most often: the horse has no saddlebag, and Config.HorseAttachPoint is weightbag.

Config.HorseAttachPoint = 'saddle'

PH_saddle_attach_L is part of the saddle itself, which every ridable horse has. See Carrying & attach points.

The lantern is in the wrong place on the saddle

Custom saddles sit differently. Turn on the tuning commands and fit it:

Config.TuningCommands = true

/lanterntune
/lanternmove 0 -0.2 0

Paste the printed line into config.lua. Full walkthrough in Carrying & attach points.

Colour or brightness does nothing

Cause
Lantern is stowed	The hold-aim controls need it in hand. Use /lanterncolour instead
Pressing Up at level 0	0 is the maximum. There is no brighter — only five steps down
Testing in daylight	The change is nearly invisible. Test at night
Feature disabled	Check Config.ColourChanging and Config.Brightness

Lanterns disappear after a restart

Expected unless you turned persistence on:

Config.Persistence.Placed = true

If it is already on and they still vanish, your host is likely blocking writes to the resource folder — common with escrow protected builds. Switch to Mode = 'mysql'. See Persistence.

Console says framework: standalone but I run VORP

The resource started before your core. Fix the order in server.cfg:

ensure vorp_core
ensure vorp_inventory
ensure rm_Lantern

Or skip detection entirely:

Config.Framework = 'vorp'

Notifications look wrong, or appear as plain text

The framework's notification export could not be reached, so the built-in on-screen text took over. Usually a core update that renamed an export.

bridge/client.lua stays readable in escrowed builds — fix the call in Bridge.Notify for your core. See Frameworks.

"There is nowhere to set it down"

The placement checks refused the spot. One of:

• no ground within reach in front of the player
• the drop is more than 1.75m up or down — a ledge, or a roof below
• something solid between the player and the spot

Face open ground and try again. Tight interiors and stairs are the usual culprits.

Players can place unlimited lanterns

Config.UnlimitedPlacement = false   -- one at a time
Config.MaxPlacedPerPlayer = 8       -- cap when unlimited
Config.MaxPlacedGlobal = 200        -- server wide

I cannot pick up a lantern

Cause
Too far away	Config.PickupDistance, default 2.0m
Not yours	Config.AllowForeignPickup = false restricts pickup to the placer
Inventory full	Only with RequireItem and ConsumeOnPlace on. The lantern stays lit rather than vanishing

Performance

Threads sleep when nothing is happening and placed lanterns render by distance. If you need to cut further:

Config.RenderDistance = 80.0
Config.MaxPlacedGlobal = 100
Config.ColourChanging = false
Config.Brightness = false

Turning both lighting options off stops the lighting thread doing any work.

Still stuck

Open a ticket in Discord and include:

• your Config.Debug = true console output, client and server
• your framework and version
• what you expected, and what happened instead
• whether it happens for every player or just one