/
Var-PinCode
StandaloneVar-PinCode is a developer-friendly NUI PIN keypad for FiveM that gates any action behind a code: doors, safes, vehicles, or your own scripts. Two exports (callback and async) return a clean true or false, it runs on ESX, QBCore, or Standalone with a single toggle, and it needs no database.
Promocja aktywna|Oszczędź €2.00 na tym skrypcie
Dostęp do kodu
Zawarte w pakiecie Var Utility Pack|€23.32 +4|oszczędź 22%
A polished React NUI keypad with digit entry and delete/backspace, styled with the Bai Jamjuree font for a crisp, readable look.
SendToPinCode takes a callback, SendToPinCodeSync awaits a promise. Pick the pattern that matches your codebase and get a clear true or false either way.
The expected PIN is passed on each call, so one UI secures every lock on your server: doors, safes, vehicles, or custom script actions, each with its own code.
Players get a green correct or red incorrect notification instantly, and your script receives the matching boolean result.
ESX, QBCore, or Standalone via a single config toggle, with matching notification handlers per framework.
An example /pin command ships in the resource, so you can see the full flow working before wiring it into your own systems.
All messages and prompt text live in editable locale strings, so you can translate or re-word without touching the bundle.
No SQL, no tables, no persistence layer. A built-in version checker tells you when an update is available.
Add the resource, ensure it in server.cfg, and set your framework in the single shared config file. There is no database to import, and you can test the keypad immediately with the included /pin example command.
Call one of the two exports: SendToPinCode with a callback, or SendToPinCodeSync if you prefer await. You pass the expected PIN on each call and receive true or false, so protecting a door, safe, or vehicle takes a few lines of code.
Yes, plus Standalone. You select the framework with a single toggle, and notifications automatically use the matching handler for your setup.
Yes, that is the core design. The expected PIN is set per call, so every door, safe, vehicle, or script action can have its own code while sharing the same keypad UI.
No. Var-PinCode stores nothing: your script passes the expected code on each call, and the keypad simply returns whether the entry matched. Where codes come from, config, database, or gameplay, stays entirely up to your own resources.
No. It is a deliberately lightweight resource: no database, a keypad UI that only appears when a PIN is requested, and a version checker that runs once on resource start.
