+1. Download the latest version of the script using the "Download ZIP" button on the right side of this page.
+2. Extract the ZIP file.
+3. Rename the folder to `sticks-keypad` and copy it to your `resources` directory.
+4. Add `ensure sticks-keypad` to your `server.cfg`.
+5. All done, start your server and enjoy!
-This repository is a basic boilerplate for getting started
-with React in NUI. It contains several helpful utilities and
-is bootstrapped using `create-react-app`. It is for both browser
-and in-game based development workflows.
+## Configuration
-For in-game workflows, Utilizing `craco` to override CRA, we can have hot
-builds that just require a resource restart instead of a full
-production build
+You can configure the script in the `server/server.lua` file. To add a new entry, you need the door ID, the cords of the door, the teleport cords, and the password. An example is already in the file to help you understand how to add a new entry, and can also be seen below.
-This version of the boilerplate is meant for the CfxLua runtime.
-
-## Requirements
-* [Node > v10.6](https://nodejs.org/en/)
-* [Yarn](https://yarnpkg.com/getting-started/install) (Preferred but not required)
-
-*A basic understanding of the modern web development workflow. If you don't
-know this yet, React might not be for you just yet.*
-
-## Getting Started
-
-First clone the repository or use the template option and place
-it within your `resources` folder
-
-### Installation
-
-*The boilerplate was made using `yarn` but is still compatible with
-`npm`.*
-
-Install dependencies by navigating to the `web` folder within
-a terminal of your choice and type `npm i` or `yarn`.
-
-## Features
-
-This boilerplate comes with some utilities and examples to work off of.
-
-### Lua Utils
-
-**SendReactMessage**
-
-This is a small wrapper for dispatching NUI messages. This is designed
-to be used with the `useNuiEvent` React hook.
-
-Signature
```lua
----@param action string The action you wish to target
----@param data any The data you wish to send along with this action
-SendReactMessage(action, data)
+-- Example
+{1, {x = -3029.3825683594, y = 72.813552856445, z = 11.4}, {x = -3031.3232421875, y = 93.021644592285, z = 12.346099853516}, "1234"},
```
-Usage
-```lua
-SendReactMessage('setVisible', true)
-```
+## Credits
-**debugPrint**
-
-A debug printing utility that is dependent on a convar,
-if the convar is set this will print out to the console.
-
-The convar is dependent on the name given to the resource.
-It follows this format `YOUR_RESOURCE_NAME-debugMode`
-
-To turn on debugMode add `setr YOUR_RESOURCE_NAME-debugMode 1` to
-your server.cfg or use the `setr` console command instead.
-
-Signature (Replicates `print`)
-```lua
----@param ... any[] The arguments you wish to send
-debugPrint(...)
-```
-
-Usage
-```lua
-debugPrint('wow cool string to print', true, someOtherVar)
-```
-
-### React Utils
-
-Signatures are not included for these utilities as the type definitions
-are sufficient enough.
-
-**useNuiEvent**
-
-This is a custom React hook that is designed to intercept and handle
-messages dispatched by the game scripts. This is the primary
-way of creating passive listeners.
-
-
-*Note: For now handlers can only be registered a single time. I haven't
-come across a personal usecase for a cascading event system*
-
-**Usage**
-```jsx
-const MyComp: React.FC = () => {
- const [state, setState] = useState('')
-
- useNuiEvent('myAction', (data) => {
- // the first argument to the handler function
- // is the data argument sent using SendReactMessage
-
- // do whatever logic u want here
- setState(data)
- })
-
- return(
-