Changelog

1. Back up and stop the server

These steps update sky_pets from 1.2.0 to 1.3.0. If you are on an older version, complete its earlier update steps first.

1. Download 1.3.0 and extract the ZIP on your computer.
2. Make a full backup of your server files and game database. Also keep a separate copy of the installed sky_pets folder.
3. Stop the server before replacing files. Put away equipped custom weapons first. Keep the backup until the update has been checked.

Standalone Pets needs Base, not Jobs Base. Update Jobs Base and the matching jobs only if you use their Pets integration.

2. Copy the new files

Use the files from the 1.3.0 download throughout these steps. All paths below are inside your installed sky_pets folder.

1. Delete the old source/ folder. Copy the complete new source/ folder into its place, including its interface files.
2. Replace fxmanifest.lua with the file from the same download.
3. Replace the complete config/locales/ folder with the new one. If you changed any wording, open the backed-up language file beside the new file and copy your edited text into the matching entries. Keep the new translation keys and folders.
4. Keep your existing config/config.lua; make only the settings changes described in step 3 below. Do not overwrite your configured jobs or locations with the download's defaults.

Copy the eight changed puppy XML files shown in Changed Files from the new data/ folder to their identical paths in the installed sky_pets/data/ folder. Keep other model files and separate breed resources.

3. Check your settings

No settings changes are required. Keep your existing configuration, breed add-ons, inventory selection and saved /petsconfig settings (/petconfig also works). Pets settings are separate from /jobconfig; no default import is needed.

Keep the database backup together with the server's resource KVP/checkpoint backup. The new version restores a clean-shutdown checkpoint before pets load. If startup reports a checkpoint/database restore error, keep the checkpoint, fix the reported database problem and restart. Do not delete KVP data to bypass the error.

4. Update database, items and models

The eight core puppy XML files were copied in step 2. They cover Chop, Husky, Poodle, Pug, Retriever, Rottweiler, Shepherd and Westy puppies. Keep their existing model names and separate breed add-ons.

No database import, new inventory item or breed-package replacement is required. Keep the existing Pets database and server KVP data. Do not repeat old Petshop map deletions. Reconnect all players after the full server restart so clients load the new model metadata.

5. Start the server and check

1. Finish the file copies, required Lua edits and database steps, then start the server. Start the framework, database connector, inventory and sky_base 1.48.0 first. Start your selected breed add-ons next, then sky_pets 1.3.0. Jobs Base is needed only for your chosen job integrations.
2. Check the server console for startup or database errors. If an error appears, resolve the first error before testing further. Check that this resource reports version 1.3.0.
3. Reconnect so the new interface and models load. If step 3 listed in-game settings, open the named configurator, make those changes and save. Then check your saved jobs and the features you use before reopening the server to everyone.

What to check for this resource: Load an existing pet and reopen its saved settings. On a test server, change growth/training/health, stop/start cleanly and confirm the values return. After reconnecting, check affected puppies can get up and follow without losing health. Cancel a treatment/training action and check that it affects the correct pet and refunds the correct item.

1. Prepare

These instructions update an existing 1.1.0 installation to 1.2.0. Older installations must first complete the 1.1.0 instructions. Back up the database, core resource, custom configuration/translations and saved Pets Configurator settings. Finish active pet activities and stop the server before replacing files. Keep Sky Base 1.47.0 or newer. Sky job integrations also need Jobs Base 1.50.0 or newer and the matching installed jobs; standalone Pets does not require Jobs Base.

2. Replace files and remove old maps

Delete the complete sky_pets/source/ folder and insert the supplied replacement, including the generated interface. Replace sky_pets/fxmanifest.lua from the same 1.2.0 package. Refresh the complete sky_pets/config/locales/ folder and merge custom translations; no new locale keys are required.

Delete these three files from the installed resource: sky_pets/stream/Petshop/ss1_rd1_long_0.ymap, sky_pets/stream/Petshop/hei_ss1_rd1_long_0.ymap and sky_pets/stream/Petshop/apa_ss1_rd1_long_0.ymap. Copying the new ZIP over the old folder does not remove them. Keep every other Petshop file, including sky_petshop.ymap, _manifest.ymf and both YTYPs. The matching new source and manifest replace only the rooftop billboard locally; no native model or texture needs rebuilding. Review any separately installed compatibility resource that still supplies those old street-map overrides.

3. Preserve settings

No plaintext key, default, provider selection, permission or saved configurator setting changes. Preserve sky_pets/config/config.lua, sky_pets/config/petshop.lua and the other custom configuration. Keep custom shop seller, pet, camera and target positions together. With Config.UseIngameConfigurator = true, saved settings plus shipped defaults remain authoritative. Use /petsconfig (alias /petconfig), independently from /jobconfig. Do not import or reset settings for this update: /petsconfig import intentionally replaces managed settings. Keep existing leash length and activity tolerances; these fixes need no tuning.

Optional diagnostics remain disabled by default. For support, put setr sky_profiler 1 in server.cfg before the Sky ensure lines and perform a full server restart. Run profiler record 1000, wait until profiler status reports completion and run profiler saveJSON sky-pets-1.2.0.json. Recording and upload are manual. Disable with setr sky_profiler 0 and another full restart; this is not a Pets Configurator or Job Configurator setting.

4. Keep data, items and selected breeds

No SQL migration, new inventory item, image or breed add-on is required. Do not replay the full sky_pets/import.sql. Preserve ownership, training, growth, outfits, health, saved settings and the existing Config.AutoExecuteQuery policy. Keep current item registrations, including pet_treat with consume = 0, and all remaining streamed assets. Optional sky_pets_<breed> resources are unchanged and separate from the core ZIP; install and start only your selected breeds.

5. Restart and check

Perform a full server restart and reconnect clients so the removed maps unload. Start the database connector, framework and configured inventory/providers first, then Base, any installed Sky job libraries/jobs, selected breed add-ons and finally sky_pets.

Confirm existing pets, outfits and saved settings load. Feed and water a small dog and a following dog through the normal inventory flow; check the approach, transitions, completion and cancellation cleanup. Attach/remove a leash, then test any other rope-using resource you have installed. Visit the Petshop and the affected nearby MLO after reconnecting; check the billboard, entrances and surrounding objects. This fixes the street-map override and shared-texture side effects; it does not establish a fix for every third-party fuel crash or an unrelated invisible-pet issue. For a remaining activity failure, an authorized admin can use /sky_pets_peddebug on, reproduce once, retain matching F8/server logs and turn it off with /sky_pets_peddebug off.

1. Prepare

These instructions update existing sky_pets 1.0.x installations to 1.1.0. Back up the database, the core resource, customized configuration/translations and saved Pets Configurator settings. Finish active pet activities and stop the server for replacement. Install Base 1.47.0 first. If you use Sky job integrations, also update Jobs Base to 1.50.0 and the matching installed jobs. Keep only your deliberately selected optional breed resources; this core update does not require new breeds or rebuilt models.

2. Replace files

Delete the complete sky_pets/source/ folder and insert the supplied replacement, including the generated interface. Replace sky_pets/fxmanifest.lua from the same 1.1.0 package. Refresh the whole sky_pets/config/locales/ folder and merge custom translations. Preserve the other configuration files and all existing streamed models/data: this update changes no native model, texture, clothing collection or map. Optional sky_pets_<breed> add-ons are separate resources and are not replaced by the core ZIP.

3. Merge settings

No plaintext key, configurator setting or default value is added, removed or renamed in this update. Keep the existing values in sky_pets/config/config.lua. Config.Leash.length remains 2 by default; it now specifies the maximum cord payout in metres, with excess cord taken up when the dog is closer. The existing /petsconfig (alias /petconfig) leash-length description explains this meaning. Keep customized length, speed, stopping distance, camera FOV and zoom limits; whole-number values now work without rewriting them as decimals.

With Config.UseIngameConfigurator = true, saved Pets Configurator settings plus shipped defaults are authoritative. Open /petsconfig to change managed values; do not use /jobconfig. An ordinary update needs no import or reset. If you intentionally choose to import Lua settings, back up the saved configuration, change the Lua files, restart sky_pets and then run /petsconfig import; this replaces the managed settings and is a deliberate administrative action.

The legacy shop migration now changes a location only when its seller, pet, camera and target coordinates all still match the old outdoor defaults. A customized layout stays together. Previously stored mixed or incorrectly positioned layouts are not overwritten automatically: inspect Config.Shops.pet_shop and Config.SuppliesShops.pet_supplies through the active configuration mode and correct their four related positions together only if necessary. No coordinate change is needed merely to fix camera zoom.

Optional diagnostics stay disabled by default. For a support recording, place setr sky_profiler 1 in server.cfg before the Sky ensure lines and perform a full server restart. Run profiler record 1000, wait for profiler status to show completion, then run profiler saveJSON sky-pets-1.1.0.json. Recording and uploading do not start automatically, and this is not a /petsconfig or /jobconfig option. Disable with setr sky_profiler 0 and another full restart.

4. Database, items and assets

This update adds no database table, column, data reset, inventory definition or image. Do not replay the full sky_pets/import.sql for an existing installation. Preserve pet ownership, training, growth, outfits, health, saved settings and your selected automatic/manual migration policy (Config.AutoExecuteQuery). Existing pet items, including pet_treat with consume = 0, remain registered through your current inventory setup. The activity correction does not consume a supply when its animation never starts or is cancelled.

No streamed asset is changed. Keep the installed native dogs, your selected optional add-ons and their existing model IDs. Preserve your current petshop mapping setup; a new MLO, clothing collection or breed installation is not part of 1.1.0.

5. Restart and check

Perform a full server restart and reconnect clients. Start the database connector, framework and configured inventory/providers first, then Base 1.47.0. Start any required Sky job libraries and jobs, then each explicitly selected pet breed add-on before sky_pets. Do not start every add-on category when you intend to select individual breeds.

Confirm existing pets, outfits and saved configuration load. Test pet/supplies shop previews at opening, mouse-wheel zoom and both limits. Confirm a customized outdoor shop keeps its seller, dog, camera and target together. Feed and water a pet, verify a delayed animation can start, and verify a genuine cancellation leaves no active activity or consumed supply. Attach the leash with a whole-number maximum length, walk closer/further and verify the cord retracts without exceeding that maximum. Check follow/recall and, if installed, a working-dog search. These are customer checks to perform; package and mocked regression results do not establish current FiveM rendering or multiplayer acceptance.

If support needs activity/camera details, an authorized admin can temporarily use /sky_pets_peddebug on, reproduce once and disable it afterward. The activity message alone does not establish an anticheat conflict; retain the matching provider/client logs instead of adding blanket anticheat exemptions.