> For the complete documentation index, see [llms.txt](https://docs.cdev.shop/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cdev.shop/fivem/pet-system/faq.md).
# FAQ
## How can I add another job to use the K9 pet?
***
You can add another job by configuring the `IsPlayerAllowedToBuyK9` function, which you can find in the file `cdev_pets > public > server > api.lua`.
Suppose the other job you want to add is named **Xerif**, then the code will look like this:
```
PetResourceAPI.IsPlayerAllowedToBuyK9 = function(source)
local jobName, grade = clib.api.Character.GetCharacterJobFromSource(source)
if jobName ~= "police" and jobName ~= "Xerif" then
return false
end
return true
end
```
## How stop Dog Attack?
***
After the pet starts attacking the player or NPC, keep holding the G key until it obeys your command to stop attacking.
## Issue with DrawText for players in Asia how Fix it?
***
**To fix the DrawText issue, go to `cdev_lib > public > config > config.lua` (lines 31 and 32) and change them to match the code below exactly.**
> ```lua
> DrawTextConfig = {
> OverrideDrawtextFont = true,
> OverrideDrawtextFontId = 4
> },
> ```
***
## **How Pet Stamina System Work ?**
***
{% hint style="info" %}
Stamina represents your pet’s physical energy. It is consumed when the pet performs activities and regenerated only under specific conditions.
{% endhint %}
### 📍 Where are stamina settings located?
All stamina-related configuration values can be found here:
```
cdev_pets/public/config/config.lua
```
***
### ⚙️ Stamina Configuration Values
```lua
StaminaDecreaseFollowingPerTick = 4,
StaminaDecreaseFromFetch = 4,
StaminaIncreaseWhileSleepingPerTick = 2,
StaminaChangeWhileSleepingNotify = 1,
StaminaDecreaseWhenAttacking = 5,
```
***
### ⏱️ How often does stamina update? (AI Tick)
Stamina does **not** update every second.\
It updates based on the server’s AI Tick system:
```lua
AI = {
TickFrequency = 60, -- in seconds
}
```
#### 🔎 Meaning:
**Stamina is updated only once every 60 seconds (1 minute).**
Whether the pet is following, sleeping, or performing an action, stamina will only change at each tick.
***
## 😴 How Stamina Regenerates
Stamina increases **only** when the pet is properly sleeping in its bed.
#### Regeneration Rate:
```lua
StaminaIncreaseWhileSleepingPerTick = 2
```
| State | Stamina Change | Amount |
| ------------------- | -------------- | ----------------- |
| **Sleeping in bed** | Increase | **+2 per minute** |
#### ⚠️ Important Requirement
{% hint style="danger" %}
**You (the owner) must remain near the pet while it sleeps.**\
If you move too far away, the pet may leave the sleeping state and stamina will stop regenerating.
{% endhint %}
{% hint style="warning" %}
**If your pet is very** hungry **or very** thirsty**, it will lose stamina — even while sleeping.**
{% endhint %}
***
## 📉 Stamina Consumption (Default Config)
Below is a complete list of all actions that reduce stamina.
***
### 🐕 Following
| Action | Stamina Change | Value |
| ------------------- | ----------------- | ----------------- |
| Following the owner | Decrease per tick | **–4 per minute** |
***
### 🎾 Fetching (Toy/Ball)
```lua
StaminaDecreaseFromFetch = 4
```
| Action | Stamina Change |
| ----------- | ----------------- |
| Fetch a toy | **–4 per action** |
***
### 🐺 Attacking
```lua
StaminaDecreaseWhenAttacking = 5
```
| Action | Stamina Change |
| ------ | ----------------- |
| Attack | **–5 per action** |
***
## 🎓 Training Activities
Training stamina costs are configured here:
```lua
training = {
Cones = { StaminaDecrease = 5 },
Ramp = { StaminaDecrease = 7 },
Dummy = { StaminaDecrease = 7 },
Hoop = { StaminaDecrease = 7 }
}
```
#### Training Stamina Costs
| Training | Stamina Cost |
| -------------------------- | ------------ |
| **Cones** | –5 |
| **Ramp** | –7 |
| **Dummy (Practice Dummy)** | –7 |
| **Hoop (Ring)** | –7 |
***
## 💤 Tired State (Stamina = 0)
When stamina reaches **0**, the pet becomes **Tired**.
Effects:
* Cannot attack
* Cannot train
* Cannot fetch
* Cannot perform demanding actions
* May whine or show tired mood
* Must sleep to recover stamina
***
## 📘 Complete Stamina Overview (Summary Table)
| Situation | Change | Amount | Notes |
| ------------------- | ------ | --------------------- | ---------------------- |
| Pet sleeping in bed | + | **+2 / minute** | Owner must stay close |
| Pet following owner | – | **–4 / minute** | Tick = 60s |
| Fetch toy | – | **–4 / action** | Instant |
| Attack | – | **–5 / action** | Instant |
| Cones training | – | **–5** | Requires stamina |
| Ramp training | – | **–7** | Requires stamina |
| Dummy training | – | **–7** | Requires stamina |
| Hoop training | – | **–7** | Requires stamina |
| Stamina minimum | 0 | Pet becomes **Tired** | Cannot perform actions |
***
## 🛠 Balancing Tips (Optional)
| Goal | Change |
| ------------------------------------ | ---------------------------------------------- |
| Faster stamina recovery | Increase `StaminaIncreaseWhileSleepingPerTick` |
| Slower stamina drain while following | Lower `StaminaDecreaseFollowingPerTick` |
| Faster stat updates | Reduce `AI.TickFrequency` (use with caution) |
***
## 💡 Additional Notes
* Stamina is clamped between **0 and 100**.
* Notifications are sent every time **increase**.
* Stamina changes happen at **tick intervals**, not instantly.
* The pet must be truly *inside* the bed’s interaction area to start sleeping.
***
## My K9 dog is not dealing damage to the player it was ordered to attack how fix it?
***
⚠ **Attention:** **Your** **K9** **will not deal damage to the player because the setting** **EnableAttackUpdate****is enabled in the configuration file:**\
`cdev_pets > public > config > config.lua` (lines 39–40).
**With this setting ****enabled****, only ****K9**** pets are ****allowed to attack****, and they will ****only target players****. However, they will not cause any ****damage**** — they will simply ****knock the player down and immobilize**** them, making the behavior more realistic, just like a real-life K9 unit.**
**Now, if you want the pet to deal damage to the player, you will need to make some changes in the file**\
`cdev_pets > public > config > config.lua` **as shown below.**
```lua
-- if true, pets can only attack players
-- if false, pets can attack any entity
EnablePetToOnlyAttackPlayers = false, or EnablePetToOnlyAttackPlayers = true,
-- If true, will enable the new attack update with the police being the only that can use this feature and train the dog
-- If true, only the K9 will be able to attack, and it won’t deal damage to players — it will only knock them down and immobilize them to make it more realistic.
-- If false, will reverse to old one
-- If This is true need EnablePetToOnlyAttackPlayers to be true
EnableAttackUpdate = false,
```
⚠ **Attention:** **Keep in mind that if you disable the EnableAttackUpdate setting, all pets will be able to attack, removing the exclusivity of the** **K9** **pet.**
## Is it possible to add a pet Add-ON to the Pets system? And How Add ?
***
Yes, it’s possible to add a pet Add-on or even a some native GTA V animal. However, below you can find a list of functions that will be compatible and others that will not be compatible with Add-on pets or native GTA V animals.
⚠ **Attention:** **You will only be able to add pets (Add-on or native) that belong to the Dog or Cat category. Other pets, such as** **a\_c\_chickenhawk, a\_c\_chimp, a\_c\_fish, a\_c\_hen, a\_c\_pig, a\_c\_rat****, cannot be added — your pet will not have any movements and will also die instantly**.
\
⚠ **Attention:** **Issues with animations related to positioning, Add-on crashes and other problems with added pets (not including ours) are not covered by our support.**
| Appears | Actions | Accessories | Care |
| --------------------------------------------------- | --------------------------------------- | -------------------------- | ---------------------- |
| -------------------- | Follow, Cuddle, Pet Stats, Animations ✅ | Leash, Beds, Bwols, Toys ✅ | Food, Liquid, Health ✅ |
| Collar, Clothes, Shoes, Head, Patch, Glasse, Maks ⛔ | K9 Functions (Sniff, Training) ⛔ | ------------------- | -------------------- |
### How install new pet Add-on or retail pet from GTAV
{% stepper %}
{% step %}
### Add the animal’s photo to the shop.
⚠ **Recommended size:**** 237 x 168**
⚠ **To make sure the image works correctly in the shop, please use the** WEBP format for the photo.
⚠ **The file name (the animal’s photo) must match exactly the** **KEY** **variable name defined in** **cdev\_pets > public > config > shop.lua****.**
**Add the photo in the ****cdev\_lib**** resource under the path: ****cdev\_pets > html > pets > > inventory****.**
{% endstep %}
{% step %}
### Creating the animal
**You will add a line by copying from another animal inside the ****pets.lua**** file located in the folder ****cdev\_pets > public > config > pets.lua****.**
**Example (Using a native pet from GTAV):**
```lua
["a_c_westy"] = { -- Change
Item = "a_c_westy", -- Change
LeashSettings = { -- No touch
Bone = 39317, -- No touch
BoneName = "SKEL_Neck1", -- No touch
BoneOffset = vector3(0.0, 0.15, -0.1), -- No touch
},
FloatingUISettings = { -- No touch
Bone = 31086, -- No touch
Offset = vector3(0.0, 0.0, 0.6), -- No touch
MenuOffset = vector3(0.0, 0.05, 0.4), -- No touch
BalloonOffset = vector3(0.0, 0.0, 1.0), -- No touch
StatsOffset = vector3(-0.2, 0.0, -0.1) -- No touch
},
CameraCloseSettings = { -- No touch
Bone = 31086, -- No touch
Offset = vector3(0.3, 1.2, 0.5), -- No touch
Rotation = vector3(0.0, 0.0, 160.0), -- No touch
},
BallSettings = { -- No touch
Enable = true, -- No touch
AttachBone = 46240, -- No touch
AttachBoneOffset = vector3(0.14, 0.0, 0.05), -- No touch
},
Animations = DogAnims["SmallDog"], -- Change
},
```
**Explanation of the part that needs to be changed:**
**\["****a\_c\_westy****"]**: Inside the key, instead of **a\_c\_westy**, you will put the name of the resource (the pet add-on folder you are adding) Or, if the pet is from GTAV, you should only use the ped name as shown on the website.
\ **Item = "****a\_c\_westy****"**: Here you will enter the spawn name of the ped. For an add-on file, you can find it inside the **peds.meta** file in the section marked as \a\_c\_westy\.
**Animations = DogAnims\["****SmallDog****"],** : In this part, where it says **SmallDog**, you should choose based on the size and category. There are three options: **BigDog** (for large dogs), **SmallDog** (for small dogs), and **Cat** (for cats).
{% endstep %}
{% step %}
### Adding the new created pet for sale in the shop
**You will copy the line below and paste it inside the ****shop.lua**** file located in the folder ****cdev\_pets > public > config > shop.lua.**
```lua
{
PetShopId = "a_c_westy", -- Change
key = "a_c_westy", -- Change
hasFemale = false, -- No touch
label = "Yorkshire GTAV", -- Change
isPremiumPackage = false, -- No touch
price = 5000, -- Change (If you want a different price)
category = "pet_category_pets", -- Not touch
description = "A YorkShire GTAV", -- Change
},
```
**Explanation of the part that needs to be changed:**
PetShopId = "a\_c\_westy": Identification name that will be recorded after the purchase in the shop.
key = "a\_c\_westy": Same name given to the **Item** variable in the**pet.lua** file, and it will also be used to retrieve the photo file inside **cdev\_lib**.
label = "Yorkshire GTAV": Animal name displayed in the shop.
description = "A Yorkhire GTAV": Description of the animal that will be sold in the shop.
{% endstep %}
{% step %}
### Adding the new animal to items exclusive to certain types and sizes of animals
Some items in the **items.lua** file located in **cdev\_pets > public > config > items.lua** have exclusivity settings to prevent issues related to the animal’s size and category. For your new animal to be able to purchase these items, you need to add it to the **limited** variable.
Example item (dogbaga) :\
\
⚠ **You will add the name you used in the variable** **`Item = "a_c_westy"`** **located in the file:** **cdev\_pets > public > config > pets.lua****.**\
\
**Before add:**
```lua
limited = { "pet_frbul", "pet_minpit", "pet_pug", "pet_shusky", "pet_york", "pet_poodle", "pet_chiua", "pet_dash" },
```
\
**After add:**
```lua
limited = { "pet_frbul", "pet_minpit", "pet_pug", "pet_shusky", "pet_york", "pet_poodle", "pet_chiua", "pet_dash", "a_c_westy" },
```
{% endstep %}
{% endstepper %}
## I changed the keybinds in the config, but they didn’t change in-game. How do I fix this?
***
For anyone who joined before the change, you’ll need to clear the keybinds saved in your FiveM cfg file.
Here’s how:
1. Press `WIN + R`, type `%appdata%`, and open the folder.
2. Navigate to:\
`AppData/Roaming > CitizenFX > fivem.cfg`
3. Open the `fivem.cfg` file with a text editor.
4. Look for any lines with `cdev_pets` binds and delete them, or remove only the specific bind you want to reset.
Example line to remove:
```
rbind cdev_pets KEYBOARD TAB "+petbag"
```
After clearing these lines, restart FiveM. The new keybinds from your server’s config will then load correctly.
## Is it necessary to add the items that are inside the items.lua file to my inventory?
***
No, and it won’t work if you try to add them. The pet system has its own inventory already integrated with the **cdev\_pets** resource. So regarding the items, you don’t need to do any configuration or add them to your own inventory system, since it is completely separate and has its own inventory system.
The only item you *can* add to your framework’s inventory if you want is the **baseball** item. For more information on how to add it, you can read the documentation at the link below.
{% content-ref url="/pages/cpB11jNzeLtEtMeEhcbQ" %}
[OX Inventory](/fivem/pet-system/misc-integrations/ox-inventory.md)
{% endcontent-ref %}
***
## Discord Webhook Logs (Pets & Shops)
***
CDev Pets sends several events to Discord using:
```lua
clib_Logs.discord(, <fields>)
```
Below you can find a complete list of all available webhook log types, when they are triggered, and which fields are included.
{% tabs %}
{% tab title="🐾 Pet Logs" %}
#### **Pet Delete - Permission Denied**
**When it fires**\
Triggered when a player tries to delete a pet but does **not** have permission.
| Field | Description |
| ---------- | -------------------- |
| Player | Name of the player |
| Identifier | Character identifier |
***
#### **Pet Deleted**
**When it fires**\
Triggered when an admin successfully deletes a pet.
| Field | Description |
| ------------ | -------------------------- |
| Admin | Admin name and server ID |
| Identifier | Owner character identifier |
| Pet ID | ID of the deleted pet |
| {% endtab %} | |
{% tab title="🏪 Shop Management Logs" %}
#### **Created Shop**
**When it fires**\
Triggered when a player creates a new shop.
| Field | Description |
| ------------- | ------------------------------ |
| Identifier | Creator’s character identifier |
| Player | Creator’s character name |
| Shop Name | Name of the created shop |
| Shop Location | JSON location / blip data |
***
#### **Deleted Shop**
**When it fires**\
Triggered when a shop is deleted.
| Field | Description |
| ------------ | ---------------------------------------------- |
| Identifier | Character identifier of the player deleting it |
| Player | Player who deleted the shop |
| Shop Name | Deleted shop name |
| {% endtab %} | |
{% tab title="👥 Employee Management Logs" %}
{% hint style="warning" %}
`{shop}` is automatically replaced with the shop name in the log title.
{% endhint %}
#### **{shop} Added Employee**
**When it fires**\
Triggered when a new employee is added to a shop.
| Field | Description |
| ---------------- | --------------------------------- |
| Identifier | Player performing the action |
| Player | Player name performing the action |
| Added Identifier | Identifier of new employee |
| Added Player | Name of new employee |
| Role | Employee role (Employee/Boss) |
***
#### **{shop} Fired Employee**
**When it fires**\
Triggered when an employee is removed.
| Field | Description |
| ---------------- | -------------------------------------- |
| Identifier | Player performing the action |
| Player | Player name performing the action |
| Fired Identifier | Character identifier of removed player |
| Fired Player | Name of removed employee |
| {% endtab %} | |
{% tab title="💰 Shop Vault Logs" %}
{% hint style="warning" %}
`{shop}` is automatically replaced with the shop name in the log title.
{% endhint %}
#### **\[{shop}] Deposited vault money**
**When it fires**\
Triggered when money is deposited into the shop vault.
| Field | Description |
| ---------------- | ----------------------- |
| Identifier | Player depositing money |
| Player | Player name |
| Amount | Deposited amount |
| New Total Amount | New vault balance |
***
#### **\[{shop}] Withdrawn vault money**
**When it fires**\
Triggered when money is taken out of the vault.
| Field | Description |
| ---------------- | ------------------------ |
| Identifier | Player withdrawing money |
| Player | Player name |
| Amount | Withdrawn amount |
| New Total Amount | New vault balance |
***
#### **\[{shop}] Removed vault money**
**When it fires**\
Triggered when money is removed by a system/admin action.
| Field | Description |
| ---------------- | --------------------- |
| Identifier | Player removing money |
| Player | Player name |
| Amount | Amount removed |
| New Total Amount | New vault balance |
| {% endtab %} | |
{% tab title="📦 Shop Stock Logs" %}
{% hint style="warning" %}
`{shop}` is automatically replaced with the shop name in the log title.
{% endhint %}
#### **\[{shop}] Added stock**
**When it fires**\
Triggered when items are added to shop inventory.
| Field | Description |
| ---------- | ------------------- |
| Identifier | Player adding stock |
| Player | Player name |
| Item | Item ID |
| Amount | Quantity added |
***
#### **\[{shop}] Removed stock**
**When it fires**\
Triggered when items are removed from stock.
| Field | Description |
| ---------- | --------------------- |
| Identifier | Player removing stock |
| Player | Player name |
| Item | Item ID |
| Amount | Quantity removed |
***
#### **\[{shop}] Bought stock**
**When it fires**\
Triggered when a player purchases stock for the shop.
| Field | Description |
| ---------- | --------------------------- |
| Identifier | Player buying stock |
| Player | Player name |
| Items | JSON with items and amounts |
| Price | Total purchase price |
***
#### **\[{shop}] Updated stock price**
**When it fires**\
Triggered when a shop item price is modified.
| Field | Description |
| ------------ | --------------------- |
| Identifier | Player updating price |
| Player | Player name |
| Item | Item ID |
| Price | New item price |
| {% endtab %} | |
{% tab title="🐕 Vet Table Logs" %}
{% hint style="warning" %}
`{shop}` is automatically replaced with the shop name in the log title.
{% endhint %}
#### **\[{shop}] Updated vet tables**
**When it fires**\
Triggered when the list of vet tables is updated.
| Field | Description |
| ------------ | ------------------------ |
| Identifier | Player updating |
| Player | Player name |
| Tables Count | New amount of vet tables |
***
#### **\[{shop}] Removed vet table**
**When it fires**\
Triggered when a vet table is removed.
| Field | Description |
| ------------- | --------------------- |
| Identifier | Player removing table |
| Player | Player name |
| {% endtab %} | |
| {% endtabs %} | |
***
## Where is the Pet MLO location?
***
```
Location coords : vec3(85.74, -204.44, 54.49)
```
<figure><img src="https://1004862655-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPhIA9eCA4bwgx77hxx4i%2Fuploads%2FmxqeJ8nt7xVpn7IuluV7%2FLocation.png?alt=media&token=f9583370-d8cb-4e7e-acaf-3606e3ab3459" alt=""><figcaption></figcaption></figure>
## Is there a way to disable the pet store in the TAB menu?
***
Yes! You can disable the shop button in the pet bag menu (TAB) by editing the `config.lua` file:
Path:
```
cdev_pets > public > config > config.lua
```
Find the line:
```
WantPetShopButton = true
```
and set it to:
```
WantPetShopButton = false
```
## How do I change the colors of the menu ?
***
⚠ <mark style="color:red;">**Before making any changes, make a full backup of the cdev\_lib and cdev\_pets folders. If you don't have experience with development or modifying code, it is not**</mark> <mark style="color:yellow;">**recommended**</mark> <mark style="color:red;">**that you follow these steps.**</mark>
### Changing Bag Pets Menu `cdev_lib > dist > css > app.xxxx.css`
<div align="left"><figure><img src="https://1004862655-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPhIA9eCA4bwgx77hxx4i%2Fuploads%2FzUIkxasUO0gMnnppUa0n%2Fimage.png?alt=media&token=4a59099b-c692-41a3-8be5-2467a020e41d" alt="" width="180"><figcaption></figcaption></figure></div>
***
{% hint style="info" %} <mark style="color:red;">**(Header)**</mark> **`#1f1f22`**
{% endhint %}
Formatted CSS Search For
```css
.ct-container-menu .ct-menu-app .menu-app .ct-header-menu-app .header-menu-app
```
Minified CSS Search For
<pre class="language-css"><code class="lang-css"><strong>padding:3rem;width:100%;background:#1f1f22;border-top-left-radius:2rem;border-top-right-radius:2rem;flex-direction:row;gap:1rem;align-items:center;justify-content:center
</strong></code></pre>
***
{% hint style="info" %} <mark style="color:yellow;">**(Body)**</mark> **`#161619`**
{% endhint %}
Formatted CSS Search For
```css
.ct-container-menu .ct-menu-app .menu-app .ct-body-menu-app .body-menu-app
```
Minified CSS Search For
{% code fullWidth="false" %}
```css
width:100%;padding:2rem;flex-direction:column;gap:1.2rem;max-height:40rem;overflow:auto;background:#161619
```
{% endcode %}
***
{% hint style="info" %} <mark style="color:green;">**(Footer)**</mark> **`#1f1f22`**
{% endhint %}
Formatted CSS Search For
```css
.ct-container-menu .ct-menu-app .menu-app .ct-footer-menu-app .footer-menu-app
```
Minified CSS Search For
```css
padding:2rem;width:100%;background:#1f1f22;border-bottom-left-radius:2rem;border-bottom-right-radius:2rem
```
***
### Changing Main Shop Pets Menu `cdev_lib > dist > css > app.xxxx.css`
<figure><img src="https://1004862655-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPhIA9eCA4bwgx77hxx4i%2Fuploads%2Fhj3nxWvNgUM9iOZnYOl3%2Fimage.png?alt=media&token=b9f6708c-2c60-458f-a75a-1f2ef2094443" alt=""><figcaption></figcaption></figure>
***
{% hint style="info" %} <mark style="color:red;">(</mark><mark style="color:red;">**Side Bar Item Menu)**</mark>** Selected `#7289da` Not Selected `#1f1f22`**
{% endhint %}
<mark style="color:yellow;">Selected</mark> Formatted CSS Search For
<pre class="language-css"><code class="lang-css"><strong>.ct-container-shop .ct-shop-app .shop-app .ct-body-shop-app .body-shop-app .ct-left-body-shop-app .left-body-shop-app .ct-menu-left-body-shop-app .menu-left-body-shop-app .ct-body-menu-left-body-shop-app .body-menu-left-body-shop-app .ct-item-menu-left-body-shop-app .item-menu-left-body-shop-app.selected
</strong></code></pre>
<mark style="color:yellow;">Selected</mark> Minified CSS Search For
```css
background:#7289da!important
```
<mark style="color:$success;">Not Selected</mark> Formatted CSS Search For
```
.ct-container-shop .ct-shop-app .shop-app .ct-body-shop-app .body-shop-app .ct-left-body-shop-app .left-body-shop-app .ct-menu-left-body-shop-app .menu-left-body-shop-app .ct-body-menu-left-body-shop-app .body-menu-left-body-shop-app .ct-item-menu-left-body-shop-app .item-menu-left-body-shop-app
```
<mark style="color:$success;">Not Selected</mark> Minified CSS Search For
```css
display:flex;width:100%;height:-moz-fit-content;height:fit-content;align-items:center;padding:2rem;cursor:pointer;background:#1f1f22
```
***
{% hint style="info" %} <mark style="color:yellow;">**(Side Bar Background)**</mark> **`#d9d9d9`**
{% endhint %}
Formatted CSS Search For
```css
.ct-container-shop .ct-shop-app .shop-app .ct-body-shop-app .body-shop-app .ct-left-body-shop-app .left-body-shop-app .ct-menu-left-body-shop-app .menu-left-body-shop-app
```
Minified CSS Search For
```css
display:flex;width:100%;height:100%;background:#d9d9d9;flex-direction:column
```
***
{% hint style="info" %} <mark style="color:orange;">**(Background)**</mark> **`#161619`**
{% endhint %}
Formatted CSS Search For
```css
.ct-container-shop .ct-shop-app .shop-app
```
Minified CSS Search For
```css
display:flex;width:100%;height:100%;align-items:center;background:#161619;padding:2rem 4rem;gap:2rem;flex-direction:column
```
***
{% hint style="info" %} <mark style="color:blue;">**(Text Hrizontal menu)**</mark>** Selected `#7289da` Not Selected `#000`**
{% endhint %}
<mark style="color:yellow;">Selected</mark> Formatted CSS Search For
```css
p.text-title-item-sub-menu-top-right-body-shop-app.selected
```
<mark style="color:yellow;">Selected</mark> Minified CSS Search For
```css
p.text-title-item-sub-menu-top-right-body-shop-app.selected{color:#7289da}
```
<mark style="color:$success;">Not Selected</mark> Formatted CSS Search For
```
p.text-title-item-sub-menu-top-right-body-shop-app
```
<mark style="color:$success;">Not Selected</mark> Minified CSS Search For
```css
p.text-title-item-sub-menu-top-right-body-shop-app{font-size:1.5rem;text-transform:uppercase;color:#000}
```
***
{% hint style="info" %} <mark style="color:green;">**(Background Horizontal Bar)**</mark>`#d9d9d9`
{% endhint %}
Formatted CSS Search For
```css
top-right-body-shop-app
```
Minified CSS Search For
```css
right-body-shop-app{display:flex;width:100%;height:100%;align-items:center;padding:2rem 3rem;background:#d9d9d9}
```
***
{% hint style="info" %}
**(Pagination Menu)** **Selected `#`**`7289da` Not Selected `No Background`
{% endhint %}
Formatted CSS Search For
```css
item-pagination actualPage
```
Minified CSS Search For
```css
.item-pagination.actualPage{border-color:transparent;background:#7289da}
```
***
## How can i buy a K9 pet and K9 items ?
***
To buy the <mark style="color:yellow;">K9</mark> pet and the exclusive <mark style="color:yellow;">K9</mark> **accessories** and **items** in the shop, you need to have the <mark style="color:yellow;">police</mark> job set in your **framework**.
After that, when you click to buy the pet, if it is a <mark style="color:yellow;">K9 type</mark>, you will see an extra <mark style="color:red;">checkbox</mark> appear in the purchase menu, just like in the example below.
<figure><img src="https://1004862655-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPhIA9eCA4bwgx77hxx4i%2Fuploads%2F5lla5LbYrejiIw88LoP6%2FFiveM_GTAProcess_C7AZyPNlqE.gif?alt=media&token=d66eb4c5-5ec8-4141-9d5b-029c0b8b7e53" alt=""><figcaption></figcaption></figure>
If you want to change the required job or add more jobs allowed to buy the K9 and its accessories, follow this tutorial: [Here](#how-can-i-add-another-job-to-use-the-k9-pet)
## How to use the K9 pet's Sniff action ?
***
{% hint style="success" %}
**The Sniff action can be used on both **<mark style="color:yellow;">**players**</mark>** and **<mark style="color:yellow;">**vehicles**</mark>**. For players, it will search only the player's **<mark style="color:yellow;">**inventory**</mark>**, while for vehicles, it will search both the **<mark style="color:yellow;">**glovebox**</mark>** and the **<mark style="color:yellow;">**trunk**</mark>**.**
{% endhint %}
⚠ <mark style="color:red;">**To use the**</mark> <mark style="color:yellow;">**Sniff**</mark> <mark style="color:red;">**feature, you first need to have a**</mark> <mark style="color:yellow;">**K9 category pet**</mark><mark style="color:red;">**. You can see how to get a**</mark> <mark style="color:yellow;">**K9**</mark> <mark style="color:red;">**pet**</mark> [**HERE**](https://docs.cdev.shop/fivem/pet-system/faq#how-can-i-buy-a-k9-pet-and-k9-items)<mark style="color:red;">**.**</mark>
<figure><img src="https://1004862655-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPhIA9eCA4bwgx77hxx4i%2Fuploads%2FkNAD14fMqVwFXJZcvr9O%2FFiveM_GTAProcess_wrVKoMGHQm-_online-video-cutter.com_.gif?alt=media&token=cc3c4873-fdb2-4da9-8951-76fe8b1ef2aa" alt=""><figcaption></figcaption></figure>
### How to configure the items that the dog will sniff?
Access the file `config.lua` located in the folder `cdev_pets > public > config > config.lua`.
First, enable the `SearchEnabled` function so that everything works correctly on <mark style="color:yellow;">line 382</mark>:
```lua
SearchEnabled = true
```
Now, go to <mark style="color:yellow;">lines</mark> <mark style="color:yellow;">390</mark> to <mark style="color:yellow;">398</mark> and configure the items for each category as shown in the example below. These will be the items that the dog will search for and identify as <mark style="color:yellow;">illegal</mark>.
<pre class="language-lua"><code class="lang-lua">DrugItems = {
"phone",
<strong>},
</strong>MoneyItems = {
"water_bottle",
},
WeaponItems = {
"sandwich",
},
</code></pre>
### How Sniff system work and Sniff Skill Level?
**The level determines the chance you have to perform the Sniff action successfully so lets use image bellow to example:**
<div align="left"><figure><img src="https://1004862655-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPhIA9eCA4bwgx77hxx4i%2Fuploads%2Fjt5sHGx8qUpzMWTANhui%2FSniff%20Level.png?alt=media&token=a8310e24-8b48-4b5f-9f97-07e61418c4eb" alt=""><figcaption></figcaption></figure></div>
In this case, I have a 20% chance for the K9 dog to successfully find the items. You can change the <mark style="color:yellow;">`DefaultLevel`</mark>and <mark style="color:yellow;">`MinLevel`</mark> in the `config.lua` file located in the folder `cdev_pets > public > config > config.lua` (<mark style="color:yellow;">lines 314</mark> and <mark style="color:yellow;">317</mark>), as shown below.
```lua
sniff = {
-- Level the k9 starts at
DefaultLevel = 20,
-- Minimum level the k9 can be at
-- if 0 then it will be impossible to sniff
MinimiumLevel = 1,
-- How much the sniff level increases per successful sniff
LevelIncrease = 5,
-- How much of the skill it will take out
TakeOut = 5,
},
```
**Now lets explain how the Sniff System Works to better understand the Sniff system, here’s a step-by-step explanation:**
1. **First** – When you trigger the Sniff action near a vehicle, the system will start scanning the **DrugItems** configuration we set up earlier, regardless of where you clicked to activate Sniff.
* It will first check the **GloveBox**, reading the vehicle’s plate and verifying in the database if any of the configured items are stored there.
* If it finds an item, it will trigger the **Try Sniff** action, which determines success based on your pet’s level (as explained earlier).
* If nothing is found in the GloveBox, it will proceed to search the **Trunk** for the configured **DrugItems**.
* If it finds something in the Trunk, the dog will bark and perform a spinning animation.
2. **Second** – If no items from the **DrugItems** list are found, the system will then check the **MoneyItems** list, following the same process:
* First, it searches the **GloveBox**, then the **Trunk**.
* If an item is found, the dog will sit and bark.
3. **Third** – If no items from either the **DrugItems** or **MoneyItems** lists are found, the system will move on to check the **WeaponItems** list.
4. **Four** **and final -** The system works the same way if you use the Sniff action on a player, but it will only check the player's inventory.
***
Do you want me to also **add formatting for code examples** in the documentation so it’s easier for developers to configure the item lists? That would make it even more user-friendly.
## Does the VIP system work only for clothes and accessories ?
***
No, the VIP system works for any item listed in the file: <kbd>cdev\_pets > public > config > shop.lua</kbd>
Inside this file, you just need to add `vip = true` to any item you want to make VIP-only. If the item doesn't already have it, here’s an example of how to add VIP to the dogs:
```lua
{
PetShopId = "pet_hottweiler",
key = "pet_chop",
label = "Hottweiler",
hasFemale = true,
vip = true, -- Add this Line
price = 5000,
category = "pet_category_pets",
description = "A Hottweiler",
canBeK9 = true,
},
```
⚠ <mark style="color:red;">**If you change the**</mark> <kbd>**isPremiumPackage**</kbd> <mark style="color:red;">**variable for any pet, I suggest you revert it to avoid potential issues in the future**</mark>
## After I start the assets folder this crash happens how fix ?
***
<div><figure><img src="https://1004862655-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPhIA9eCA4bwgx77hxx4i%2Fuploads%2FT2hsNh3gDf1EhBe32AKz%2Fimage.png?alt=media&token=841a71fb-cfc0-4e0a-bc5b-f72877195b25" alt=""><figcaption></figcaption></figure> <figure><img src="https://1004862655-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPhIA9eCA4bwgx77hxx4i%2Fuploads%2FMbfFKvMC2D60YgxcoIMR%2FPool%20Size.png?alt=media&token=5a7c198b-3333-4eaf-a7ca-e520e69fe246" alt=""><figcaption></figcaption></figure></div>
This happen because you got limit addons texture or other limit you can have in one server for fix this you have some options
1. Remove some others texture like cars , new maps , clothes ..
2. Increase TxdStore inside sever.cfg ( This is not recommend) `increase_pool_size "TxdStore" 26000`
3.Use different games force build to receive more space for addons we recomended use 3258 `sv_enforceGameBuild 3258`
You can check more about Game Build [here](https://docs.fivem.net/docs/server-manual/server-commands/#sv_enforcegamebuild-build)
You can read more inside this documentation and check all limits [here](https://docs.fivem.net/docs/server-manual/server-commands/#increase_pool_size-poolname-increase)
⚠ <mark style="color:red;">**Changing the gamebuild won’t necessarily free up more space, but it will remove updates, which can help allocate more addons. Keep in mind that by using an older gamebuild version, any GTA V updates included in that build will be lost, and clothing slots as well as other limits in GTA V will change, which can negatively affect other resources on your server.**</mark>
{% hint style="info" %}
**You can also access the **<mark style="color:red;">**tool**</mark>** that **<mark style="color:yellow;">**FiveM**</mark>** provides to check how much **<mark style="color:yellow;">**%**</mark>** is being used in the **<kbd>**TxDStore Pool**</kbd>**, which is related to textures, by following the image below. Also remember that a large portion, at least **<mark style="color:red;">**15 to 20%**</mark>**, comes from the default **<mark style="color:yellow;">**GTA V**</mark>**.**\
\
**The full list of pet assets below uses a total of **<mark style="color:yellow;">**8.81%**</mark>** of the **<kbd>**TxDStore**</kbd>**:**
* cdev\_petshop
* cdev\_pets\_assets
* cdev\_pets\_assets2
* cdev\_dog\_pets
* cdev\_cat\_pets
{% endhint %}
Press the <mark style="color:yellow;">F8</mark> key to open the Client console in order to access the tool below.
<div align="left"><figure><img src="https://1004862655-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPhIA9eCA4bwgx77hxx4i%2Fuploads%2FPSjOUaPcF6KLcD8LmLRt%2Fimage.png?alt=media&token=68345c07-7c4d-42d2-896f-80a545fd5ca6" alt=""><figcaption></figcaption></figure></div>
⚠ <mark style="color:red;">**If you don’t have this option in the**</mark> <mark style="color:yellow;">**F8 menu**</mark><mark style="color:red;">**, you need to change your FiveM**</mark>** version**<mark style="color:red;">**. Go to the**</mark> <mark style="color:yellow;">**gear**</mark> <mark style="color:red;">**icon right after opening**</mark> <kbd>**FiveM Settings > Game > Update Channel**</kbd> <mark style="color:red;">**and switch it to**</mark> <mark style="color:yellow;">**Latest (Unstable)**</mark><mark style="color:red;">**.**</mark>
<figure><img src="https://1004862655-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPhIA9eCA4bwgx77hxx4i%2Fuploads%2FEu1kuLXDzOliG6MmqehD%2Fimage.png?alt=media&token=c2b10351-3723-4448-9efd-7236399fd1f6" alt=""><figcaption></figcaption></figure>
## How can I remove some clothes from the stream folder and the store?
***
{% hint style="danger" %}
**Attention:** Removing clothes/accessories from the *stream* folder may cause issues with pets that already have the removed clothing or accessory.
{% endhint %}
{% hint style="info" %}
**Note:** It is only recommended to remove them if you are really running out of space in **txdStore** and want to use the pets.
{% endhint %}
{% hint style="warning" %}
**Below is the list of stream/textures for each category.**\
**Attention:** Do not delete files that contain <mark style="color:yellow;">**^head / ^head\_diff**</mark>, <mark style="color:yellow;">**^lowr / ^lowr\_diff**</mark>, or <mark style="color:yellow;">**^hair / ^hair\_diff**</mark>.
{% endhint %}
| Category | Component Number | Stream names / Texture |
| ---------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------ |
| Collar | 8 | <p>cdev\_xxx\_xxx^accs\_xxx\_u.ydd (Model)<br>cdev\_xxx\_xxx^accs\_diff\_xxx\_x\_uni.ytd (Texture)</p> |
| Mask / Tie (Collar Category) | 1 - Maks, 8 - Tie | <p>cdev\_xxx\_xxx^berd\_xxx\_u.ydd (Model)<br>cdev\_xxx\_xxx^berd\_diff\_xxx\_x\_uni.ytd (Texture)</p> |
| Shoes | 6 | <p>cdev\_xxx\_xxx^feet\_xxx\_u.ydd (Model)<br>cdev\_xxx\_xxx^feet\_diff\_xxx\_x\_uni.ytd (Texture)</p> |
| Head | 9 | <p>cdev\_xxx\_xxx^task\_xxx\_u.ydd (Model)<br>cdev\_xxx\_xxx^task\_diff\_xxx\_x\_uni.ytd (Texture)</p> |
| Glasses | 7 | <p>cdev\_xxx\_xxx^teef\_xxx\_u.ydd (Model)<br>cdev\_xxx\_xxx^teef\_diff\_xxx\_x\_uni.ytd (Texture)</p> |
| Clothes | 3 | <p>cdev\_xxx\_xxx^uppr\_xxx\_u.ydd (Model)<br>cdev\_xxx\_xxx^uppr\_diff\_xxx\_x\_uni.ytd (Texture)</p> |
| Patch | 1 | <p>cdev\_xxx\_xxx^berd\_002\_u.ydd (Model)<br>cdev\_xxx\_xxx^berd\_diff\_002\_x\_uni.ytd (Texture)</p> |
#### 1 - Identifying the clothing you want to remove.
1.2 - First, we will open the store and choose an accessory. In this case, I will choose the <mark style="color:yellow;">Red Air One Shoes</mark>.
<div align="left"><figure><img src="https://1004862655-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPhIA9eCA4bwgx77hxx4i%2Fuploads%2FABn6FDPToXqUaMOSIluM%2Fimage.png?alt=media&token=a410e7a7-76c5-4555-8aab-f63fc5cb0cbd" alt=""><figcaption></figcaption></figure></div>
1.3 - Now we will identify which stream represents the <mark style="color:yellow;">Red Air One Shoes</mark>.\
We already know, according to the table above, that it is among the stream files `cdev_xxx_xxx^feet_xxx` because it belongs to the <mark style="color:yellow;">Shoes</mark> category.
So, open the **`items.lua`** file located at **`cdev_pets > public > config > items.lua`** and search for **“Red Air One Shoes.”**
```lua
data = {
component = 6, -- This is just type of acessrioes from ped
drawable = 7, -- This is number of the model so cdev_dog_rott^feet_007_u.ydd
texture = 0, -- This is the texture color so 0 -> A cdev_dog_rott^feet_diff_007_a_uni.ytd
},
```
1.4 - **So we found that the drawable number is 7**, which is the model, and the **texture is 0**, which represents letters.\
For example: **0 → A, 1 → B, ...**
Therefore, the **model and texture for the Red Air One Shoes** would be:
**`cdev_dog_rott^feet_007_u.ydd`**\
\&#xNAN;**`cdev_dog_rott^feet_diff_007_a_uni.ytd`**
## Where are the images from shop of the pets, clothes, and accessories located ?
***
All the images that appear in the store menu are located inside the **cdev\_lib** resource:
<kbd>**cdev\_lib > nui > dist > pets > inventory**</kbd>
The cdev\_lib use the <mark style="color:yellow;">**KEY**</mark> variable inside the file: <kbd>cdev\_pets > public > config > shop.lua</kbd> to look up the images in the folder mentioned above.
Example:
```lua
{
PetShopId = "pet_hottweiler",
key = "pet_chop", -- This Key is reference for images inside the folder lib
label = "Hottweiler",
hasFemale = true,
price = 5000,
category = "pet_category_pets",
description = "A Hottweiler",
canBeK9 = true,
},
```
⚠ <mark style="color:red;">**The images must have the**</mark><kbd>**.webp**</kbd> <mark style="color:red;">**extension. Any changes inside this folder are not recommended unless you have experience.**</mark>
## Pets not spawning in?
***
{% hint style="danger" %}
Check to make sure you have an active CFX Element Club subscription: [HERE](https://portal.cfx.re/subscriptions)
{% endhint %}
## \[cdev\_pets] (ERROR) Network control timeout for spawning pet, Please Try Again!
<div align="center"><figure><img src="https://1004862655-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPhIA9eCA4bwgx77hxx4i%2Fuploads%2FkrhZYAPd7MQU17l0zR9U%2Fimage.png?alt=media&token=8d185e84-a69b-44ad-b22f-701f54fe10d7" alt=""><figcaption></figcaption></figure></div>
{% hint style="danger" %}
If you have an anti-cheat, it may be blocking the pet events, please check with your AC provider on how you can resolve this
{% endhint %}
## After I updated cdev\_pets to version 2.9.3 or (Higher), I can no longer open the store manager how can i fix?
***
<figure><img src="https://1004862655-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPhIA9eCA4bwgx77hxx4i%2Fuploads%2FcnJyy2ZHwBNvYlNCVAai%2FError%20When%20Try%20open%20Manager.png?alt=media&token=193bd8f8-f1f6-48db-9014-48d5356202ae" alt=""><figcaption></figcaption></figure>
✅ <mark style="color:yellow;">**Please note: if you’re not yet using the resource on your production server, and it’s not an issue for you to delete all the cdev\_pets tables, the best practice is to remove them entirely and recreate the shop. This will fix all existing problems and help avoid any future issues.**</mark><br>
### List of all tables to delete <mark style="color:red;">(Only delete everything if you have no problem losing all previously recorded data.)</mark>
* cdev\_pets
* cdev\_pets\_petshops
* cdev\_pets\_petshops\_employees
* cdev\_pets\_petshops\_sales
* cdev\_pets\_petshops\_sell\_prices
* cdev\_pets\_petshops\_stock
\
\
⚠ <mark style="color:red;">**This error happens because in the new updates, some**</mark> <mark style="color:yellow;">**items**</mark> <mark style="color:red;">**were**</mark> <mark style="color:yellow;">**renamed**</mark> <mark style="color:red;">**and problematic items were also**</mark> <mark style="color:yellow;">**removed**</mark> <mark style="color:red;">**from the**</mark> **`items.lua`** <mark style="color:red;">**and**</mark> **`shop.lua`** <mark style="color:red;">**files. Additionally, we replaced all the**</mark> <mark style="color:yellow;">**images**</mark> <mark style="color:red;">**as well. To fix this issue with the store, simply clear the tables in the database listed below and fully restart the server.**</mark>
### List of tables to empty
* cdev\_pets\_petshops\_sales
* cdev\_pets\_petshops\_sell\_prices
* cdev\_pets\_petshops\_stock
### Example Video using <mark style="color:yellow;">HeidiSQL ( version: 12.10.0.7000)</mark>
<div align="left"><figure><img src="https://1004862655-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPhIA9eCA4bwgx77hxx4i%2Fuploads%2FUvQUZI55Lv8XuoulG1tq%2Fheidisql_HIy3VGXBQi.gif?alt=media&token=4c8c43fd-71d7-4da9-95fd-463a151fa2de" alt=""><figcaption></figcaption></figure></div>
⚠ <mark style="color:red;">**In addition to the issue above, it can also happen that when a player opens the**</mark> <kbd>**/petbag**</kbd> <mark style="color:red;">**or the**</mark> <kbd>**TAB**</kbd><mark style="color:red;">**menu and tries to spawn certain pets, a similar error will occur. I’ll use the**</mark> <mark style="color:yellow;">**Golden Retriever**</mark> <mark style="color:red;">**pet as an example, which had some changes made to it.**</mark>
### This is what happens when you try to spawn a pet whose models were changed or that was removed.
<div align="left"><figure><img src="https://1004862655-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPhIA9eCA4bwgx77hxx4i%2Fuploads%2Fj3Q7B9fqtZ3TQDIxrq4z%2FFiveM_GTAProcess_fIeZZGPrKZ.gif?alt=media&token=7be57661-78da-499e-ae59-a39ddf977dee" alt=""><figcaption></figcaption></figure></div>
#### Client Side Error (F8 Console)
<div align="left"><figure><img src="https://1004862655-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPhIA9eCA4bwgx77hxx4i%2Fuploads%2FBWfIzHAZY4TxDbuZa6ZP%2FClient%20Error%20Pet.png?alt=media&token=a698e120-c4c1-4fcb-addc-606558ed46d9" alt=""><figcaption></figcaption></figure></div>
#### Server Side Error (Prompt or TxAdmin Console)
<figure><img src="https://1004862655-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPhIA9eCA4bwgx77hxx4i%2Fuploads%2FqXJV2OsIQiTELXshEbSW%2FServer%20Errror%20Pet.png?alt=media&token=22c1607d-6671-45c5-b073-5595e4383b20" alt=""><figcaption></figcaption></figure>
### Now I’ll explain how to fix this problem if you updated the version and this is happening to your players who had the old pets.
In the database image below, in the `cdev_pets` table, you’ll need to modify two columns: the first is the `KEY` column and the second is the `PETSHOPID` column, as shown in the image below.
<figure><img src="https://1004862655-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPhIA9eCA4bwgx77hxx4i%2Fuploads%2FP2ZCTjmimDaeDS7u7LhK%2FYou%20go%20change%20this.png?alt=media&token=65c31676-0a56-4f59-b923-333f9e4491fd" alt=""><figcaption></figcaption></figure>
First, let’s find the new names for the <mark style="color:yellow;">Golden Retriever</mark>, which we’re using as an example. You’ll start by opening the `shop.lua` file located in the folder `cdev_pets > public > config > shop.lua`, and you’ll find the Golden Retriever code just like in the example below.
```lua
{
PetShopId = "pet_gold", -- Here is the (petshopid) column
key = "pet_gold", -- And Here is the (key) column
label = "Golden Retriever",
isPremiumPackage = true,
price = 5000,
category = "pet_category_pets",
description = "A Golden Retriever",
canBeK9 = true,
},
```
Now that we have the new strings, we’re going to update them in the database, and the result will look like the image below.
<figure><img src="https://1004862655-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPhIA9eCA4bwgx77hxx4i%2Fuploads%2FdhgSE6WZIe1owVWIXNOL%2FNewStrings.png?alt=media&token=a21fd3e9-1c30-4d6a-9ee7-d581b02eedcc" alt=""><figcaption></figcaption></figure>
<mark style="color:yellow;">After all the changes, you will</mark> shut down <mark style="color:yellow;">and</mark> restart <mark style="color:yellow;">the server, and the pet on your client or your player’s client will be working normally.</mark>
⚠ <mark style="color:red;">**Just a reminder: if you don’t have experience, I recommend not modifying the tables to avoid any serious issues with your server, such as data loss.**</mark>
