Description
A lockscreen with PIN/pattern entry, a failed-attempt lockout, remote wipe, and a fence that pays far less for a locked or stolen handset. It exists to give phone-theft loops their counterplay, a stolen phone the thief cannot open is worth little, which makes both the theft and the security meaningful.
Prompt Template
You are writing a FiveM resource for phone lockscreen security + anti-theft that runs with…
The full prompt template and its reference Lua are part of a one-time pack. Pick your depth, both are lifetime access, no subscription, ever.
- 60 prompts + syntax-validated reference Lua
- Lifetime access, pay once
- All 510 prompts, the full library
- Per-prompt profit/trend intelligence (CSV + playbook)
- Lifetime free updates, new niches as the market moves
$49 for 60 · $199 for all 510 + intelligence, one-time, no subscription.
Expected Output
The reference Lua lives at content/expected-outputs/phone/05-lockscreen-security-antitheft.lua. It implements a server-side PIN compare with a persistent attempt counter and a MAXATTEMPTS lockout…
The full prompt template and its reference Lua are part of a one-time pack. Pick your depth, both are lifetime access, no subscription, ever.
- 60 prompts + syntax-validated reference Lua
- Lifetime access, pay once
- All 510 prompts, the full library
- Per-prompt profit/trend intelligence (CSV + playbook)
- Lifetime free updates, new niches as the market moves
$49 for 60 · $199 for all 510 + intelligence, one-time, no subscription.
Known Failure Modes & Corrective Prompt
- Client-side PIN compare, comparing the PIN client-side lets a thief read or bypass it; verify on the server.
- Resettable counter, a counter that resets on each NUI open never trips the lockout; keep it on the server, reset only on a correct PIN.
- Full-value fence, paying full value ignores the lock state and kills the incentive; reduce the payout server-side for locked/stolen phones.
Corrective re-prompt: "Move the PIN compare and attempt counter into server.lua with a MAX_ATTEMPTS lockout that flags the phone stolen, and make phoneSec:fence pay a reduced amount when the target phone is locked or stolen."
Framework Integration
- ESX: not targeted here, but
xPlayermetadata could hold the hashed PIN if you port it. - QBCore:
QBCore = exports['qb-core']:GetCoreObject(); store the PIN hash in the phone item'sinfometadata so it travels with the item. - QBox:
exports.qbx_core:GetPlayer(src)withox_inventorymetadata, read/write the PIN and stolen flag on the item so a fenced phone keeps its state.
Profit Potential
$250-$3500/mo on Tebex (expected ~$900), priced within the $50-389 script band against a corpus of comparable Tebex sellers (median ~$11.85K/mo), scaled for a rising niche.
Trend Signal
↗ rising, inferred: Pairs with phone-theft loops; rising counterplay demand; inventory-metadata (ox) driven, qb/qbox-leaning.
Sales Angle
The counterplay half of any phone-theft loop, PIN lockout, remote wipe, and a gutted fence value that make a stolen phone nearly worthless until cracked. Recommended Tebex price $89.
Difficulty & Ship Time
intermediate · ships in 5-8h.