Sidekick Lite

What it is

A small companion that follows, sits, stays, and emotes — scoped deliberately narrow so it earns its place with clips rather than client cost. What it does not do is as designed as what it does. For owners who want a wholesome beat without another heavy resource. Designed for Qbox, QBCore, and ESX Legacy through ForgeCore. Escrow split publishes at release. In development; performance [measured-pending]; no runtime proof published — pending Shadow bench.

The problem it exists for

Solo hours on an RP server are quietly lonely — the drive across the map with nobody online, the shop shift with no customers. Pet scripts try to fix this and usually overreach: a needs system nobody asked for, a stable of exotic animals, an AI ped that pathfinds into a wall and dies in traffic. The server pays for a simulator when what the player wanted was company.

Why we're building it

We think the right size for a companion is small: follows, sits, stays, emotes, makes the sunset walk a scene. Every feature past that point costs frames and adds failure modes, which is why 'Lite' is in the name as a promise rather than an apology. It is also why this is the rare product page where the honest pitch is mostly about what it won't do.

What it's designed to do

Design intent, not shipped behaviour — none of this has been built yet.

• Designed as a thin layer: follow, sit, stay, emote — presence, not a needs bar.
• Designed to stay out of the frame budget, because a companion that costs performance is a companion that gets uninstalled.
• Designed for RP flavor rather than advantage — nothing about it fights, carries, or scouts, so owning one changes your scenes and not your odds.
• Intended to stay small on purpose: it is explicitly not a full pet simulator, and feature requests that would turn it into one will lose.

What is not proven

The section every product page should have and almost none do.

• Not built and not purchasable — unlike the rest of the catalogue this one has no resource in the studio repo yet, only a specification.
• No resmon figure — [MEASURED-PENDING]. 'Lightweight' is this product's entire argument, and right now it is an unmeasured claim.
• No price exists — [price-pending]. We haven't set one and won't invent one for the card.
• No release date.

What we're building toward

The companion trotting alongside its owner at sunset, sitting on command — a warm beat.

Current status, stated exactly

• resmon [measured-pending]
• escrow manifest — at release
• framework support — decided at build, published at release
• open-vs-escrowed manifest — published at release, file by file

What to verify before buying any event resource

This applies to every product in this category, ours included, whenever it arrives. Hold Sidekick Lite to exactly these when it launches — and if it fails one of them, don't buy it.

• Ask for the resmon cost with the companion active and following, not despawned — an AI ped's price is paid while it moves (see /guides/fivem-resmon-script-performance).
• Ask what happens near stairs, elevators, water, and traffic. Pathfinding edge cases are where companion scripts go from charming to clip-worthy in the wrong way.
• Ask whether it grants any gameplay advantage. The moment a companion carries, scouts, or fights, you're balancing a combat feature, not buying flavor.
• Our July 2026 survey collected no companion prices — no reference exists in our data, so judge sellers on evidence rather than anchoring on a number (see /guides/how-to-vet-fivem-script-sellers).

Universally: ask for the measured resmon figure with its method and date, the exact list of which files ship open versus escrowed, a dated changelog, and the refund window. Four answers. Any of them missing is an answer too.