Arm Wrestling
Step-by-step installation guide, common issues & solutions, code snippets, error codes, config previews, locales previews, SQL previews, and changelogs; all in 1 easily accessible place.
2. Unzip the
cd_armwrestling.zip folder and place this folder in your server's resource folder.3. Add the resource to your server start config (server.cfg):
ensure cd_armwrestling. If you are using a framework, it must be placed anywhere below your framework resource e.g., es_extended, not above.ensure es_extended
ensure cd_armwrestling
You MUST read all configurable options inside the
[cd_armwrestling/configs/config.lua] file and configure them to suit your server's needs. Please read the ”commented out help text” at the end of each line so you can understand what each config option does.
Introducing our new 'auto_detect' feature! It automatically identifies your framework and applies the appropriate default settings.
This resource is very easy to install and configure. Once the steps above are complete the rest is simple:
- 1.
- 2.Walk up to it and press E to join the game.
- 3.You will have to wait for another player, but once the other player joins, the countdown will start.
- 4.Spam the keys displayed on your screen.
This resource does not use key mapping; these keys are hard coded.
Key | Description |
|---|---|
E | Join a game at the closest table. |
X | While waiting for another player this key will cancel the game. |
These chat commands can be renamed and/or disabled in the Keys and Commands section of the
[configs/config.lua].The exact usage for each command will be displayed in the chat suggestions when using the commands in-game.
Command | Description |
|---|---|
/armwrestling_table | Spawn an arm wrestling table. |
/armwrestling_delete | Delete the closest arm wrestling table (within a small radius). |
These events are completely optional; you can use them if needed.
client-side to client-side
server-side to client-side
Spawn an arm wrestling table
Spawns the prop on your location.
TriggerEvent('cd_armwrestling:SpawnTable')
Delete the closest arm wrestling table
Deletes the closest within a small radius.
TriggerEvent('cd_armwrestling:DeleteTable')
Spawn an arm wrestling table
Spawns the prop on your location.
TriggerClientEvent('cd_armwrestling:SpawnTable', source)
Delete the closest arm wrestling table
Deletes the closest within a small radius.
TriggerClientEvent('cd_armwrestling:DeleteTable', source)
Usable items can be renamed or disabled in the
[configs/config.lua].Item Name | Description |
|---|---|
armwrestling_table | Spawn an arm wrestling table. |
Add items on ESX
Add items on QBCore
Run these SQL queries in your database.
1
INSERT INTO `items` (`name`, `label`, `weight`, `rare`, `can_remove`) VALUES ('armwrestling_table', 'Arm Wrestling Table', 1, 0, 1);
Add these lines to [qb-core/shared/items.lua].
1
['armwrestling_table'] = {['name'] = 'armwrestling_table', ['label'] = 'Arm Wrestling Table', ['weight'] = 500, ['type'] = 'item', ['image'] = 'armwrestling_table.png', ['unique'] = false, ['useable'] = true, ['shouldClose'] = true, ['combinable'] = nil, ['description'] = 'Spawn an arm wrestling table'},
🔔 Folder Name Make sure the name of the folder either
cd_armwrestling.🔔 Encrypted Files Do not edit the encrypted files in any way.
If you see an error code not listed below please open a script support ticket in the Codesign Discord.
Server
Client
N/A
N/A
Files ChangedNot every update requires you to replace the whole folder. We do this because we understand it's a pain to redo the configs for every update.
- All Files - This means you should delete your old
cd_armwrestlingfolder, download and add in the latest version, reconfigure the configs folder and restart your server. - All Files Except config.lua - This means you should do all of the above (in the All Files section) but additionally make a backup of the
config.luafile and replace the new config.lua file with the one you made a backup of. - Specific Files - This means you can copy and paste the SPECIFIC new files over the old ones and restart the server.
Update TypeOn rare occasions, you are forced to update to the latest version. Mostly due to authentication updates where the old versions will no longer work.
- Mandatory - This means you MUST update to this new version, or the old versions will no longer work.
- Optional - This means it's completely your choice whether you wish to update to the latest version. But we do not offer support for old versions for obvious reasons; they are old.
Skipping Updates
If you are attempting to update to the latest version but have skipped previous updates, you should update all files just to be safe. For example., let's say you are currently on v4.0.1, you did not update when v4.0.2 was released, and now v4.0.3 is released, and you want to update; you should always use the “All Files” update method.
v1.0.0
v1.0.1
Files Changed:
- All Files
- All Files Except config.lua
- Specific Files
Update Type:
- Mandatory
- Optional
Changelog:
Add
- Auto Framework Detection - We have added a new feature we are calling 'auto_detect', which will automatically identify your framework and apply the appropriate default settings.
- Added the option to display debug prints.
Last modified 3mo ago