SUPPORT

 Need a support or a private order ?

Open a ticket on my discord 

Description de l'image

Full Pack -50%

Description de l'image

For ox_inv 15%

Description de l'image

Rytrak Tebex Store

If you are looking for some scripts, you can visit my friend's store.

Description de l'image

Recent Payments

  • MacBlume

    Emergency #1 Animati...

    Tue 08:32
  • IMPERIORPV1

    Easter (DUO + PROPS)

    Tue 02:00
  • QPCommunity

    Emergency #1 Animati...

    Mon 19:02
  • judari123

    Emergency #1 Animati...

    Fri 19:05
  • akillmarck

    Armor plate

    5th Oct 26
  • rasheddo

    Emergency #1 Animati...

    5th Oct 26

cm-target | RedM targeting system

Targeting system for RedM. It replaces ox_target and answers its exports, so every script you already run keeps working without a single line changed.

Two things set it apart from a plain third eye: the player can aim with a free mouse cursor instead of a fixed crosshair, and while the targeting mode is open a marker is drawn above everything around them that can actually be interacted with right now.

Requires ox_lib and OneSync. No database.

WHAT YOU CAN SET

Aiming mode. Mouse mode frees the cursor and holds the camera still: the player points at what they want and clicks. Crosshair mode keeps the target at the center of the screen, the way ox_target works. Pick one for the server, or let players switch for their own session with a command.

The key. Left ALT by default, and players rebind it in the game settings under Keybinds, with no file to edit. In mouse mode the key can either toggle the cursor or be held down.

Reveal markers. The detection radius, how many markers can be on screen at once, how often the surroundings are scanned, whether other players are included, and whether a marker only shows once the interaction is really within reach. The whole feature can be switched off.

Marker colors. Three levels, from the general to the precise: by kind of entity, by the script that registered the interaction, and by the name of the interaction itself. Coloring everything one of your scripts adds takes one line and no guesswork. The marker also breathes, and you set how fast and between which opacities.

Interactions you would rather not announce. Sitting on a chair and lighting a lamp exist by the thousand. Listed by script or by interaction name, they stay fully usable from the menu, they are simply not shown from a distance. A marker is only worth something while it stays rare.

Marker anchoring. A tree has its bounding box center up in the foliage, ten meters above where the axe lands. A rule moves the marker down onto the trunk for the interactions you name, and leaves the rest of the scenery alone.

Aim precision. How far a target can be aimed at, a widened aim so small props like lanterns and buckets are not missed by a few centimeters, and a bounded search behind whatever blocks the view, so the clerk standing behind a counter window can be reached. Each of the three can be turned off.

The mount. The aim starts at the camera, behind the rider, so it never catches the horse being ridden and its own options are out of reach. With the fallback on, as soon as the aim holds nothing interactive while mounted, the mount is the target. Anything really interactive keeps priority.

The menu. Accent, paper, text and disabled colors. Past a number of entries you choose, the menu folds into chapters instead of one endless list, and you name those chapters per script. Staff tools can be pushed to the end.

Framework. Job, grade and item filters are read from your framework. VORP and its inventory are detected on their own, and can be forced. With no framework running nothing is gated, so a server without jobs does not lose half its interactions in silence.

FOUR THINGS WORTH KNOWING BEFORE YOU INSTALL

Only one targeting resource can run at a time. Stop ox_target before starting this one: both would claim the same exports and the same controls. Nothing else changes, scripts calling exports.ox_target land here.

RDR3 has no outline native. The game can only put a real light on an aimed entity, and a light shows at night and disappears in broad daylight. That is why the aimed target also changes the color of its marker, which is a sprite and stays readable at any hour.

The game draws at most 32 markers per frame and silently skips the rest, so the marker budget and the zone sprite budget together have to stay under thirty. The resource says so in the console if you set them too high.

The Cfx asset escrow only encrypts Lua. The interface is a web page and is therefore shipped readable, which means you can go further than the config file and rework the theme yourself.

INSTALLATION

  • Copy the folder into your resources.
  • Remove ensure ox_target from your server.cfg if you had it.
  • Add ensure cm-target.
  • Start the server and edit config/config.lua.

DOCUMENTATION AND SUPPORT

Full documentation: docs.camsurmotion.fr
Questions, bug reports and feature requests: Discord