ESX • QBCore • Qbox compatible
Instant download
Updates included
Discord support
Secure checkout
Weapon Scope Glint
Add immersive sniper scope glint to your FiveM server, inspired by Call of Duty and Battlefield. A standalone script tha...
Key Features
Easy Configuration
Simple config files for quick setup
Extensible Code
Clean, well-structured codebase
Secure & Optimized
Server-side validation & performance
Multi-Language
Fully translatable labels
$6.99
$13.99
Works with ESX • QBCore • Qbox
What's included:
- Full script files
- Configuration files
- Installation documentation
- Lifetime updates
- Discord support
Instant download
Updates included
Discord support
Overview
This FiveM resource adds a dynamic and customizable sniper scope glint to scoped weapons - just like in popular shooters. When players aim down sights with a high-powered optic, a realistic lens flare / sniper glint appears, making long-range engagements more tactical and fair.
Features
- Realistic scope glint effect: A visible glint is shown when players or NPCs aim down sights with scoped weapons.
- Fully standalone: No framework required - works out of the box with any server setup (ESX, QBCore, or custom).
- Sprite & corona modes: Choose between sprite-based glint or a light-based corona effect.
- Day/Night awareness: Automatically disables glint during nighttime hours for realism (configurable).
- Distance-based visibility: Glint appears only within configurable minimum and maximum range values.
- Field of view control: Adjust the angular visibility cone for glint detection (default: 20°).
- Dynamic intensity: Smooth fading at the edge of visibility for realistic transitions based on view angle.
- Configurable scope components: Easily define which weapon components trigger the glint.
- Optimized performance: Clean, efficient design with low resource usage and intelligent draw checks.
- Built-in debug tools: Visualize glint field, LOS, and detection logic using included test NPCs and debug lines.
Resmon: Idle: 0.00ms – Under load: ~0.02ms
Installation
- Download the resource from portal.cfx.re (Assets > Granted Assets)
- Extract the files and move the resource folder to your server's resources directory
- Add to server.cfg by adding:
ensure gs_scopeglint - Restart your server to load the resource
- Configure (optional) by editing the config.lua file in the resource folder
Configuration
All scripts include easy-to-edit configuration files. Common settings include:
- Language/localization options
- Feature toggles
- Price and economy settings
- Notification preferences
Escrow vs Source: Which Should You Choose?
Escrow (Encrypted)
Best for server owners who want plug-and-play functionality.
- Protected code files
- Easy configuration via config files
- Same features as source version
Source (Unencrypted)
Best for developers who need full customization.
- 100% editable code
- Full customization freedom
- Same features as escrow version
Same features; editability differs.
What others say
"Good work guys, always new ideas. love it! <3"
- Jackster2233
You Might Also Like
Frequently Asked Questions
Yes! All our scripts are compatible with ESX, QBCore, and Qbox frameworks. Additionally, all
framework-related code is accessible, so you can easily integrate our scripts with any
custom framework.
Escrow (encrypted) is best for plug-and-play functionality with protected files. Source
(unencrypted) gives you full customization freedom with 100% editable code. Both include
the same features, updates, and support.
Yes! We provide detailed documentation and Discord support to help you with installation and
configuration.
We regularly update our scripts to ensure compatibility with the latest FiveM versions. All
purchases include lifetime updates, so you'll receive notifications when new versions are
available.
Yes! All scripts include configuration files for easy customization. If you purchase the
Source (unencrypted) version, you have full access to modify the code. Escrow versions allow
configuration changes but protect the core code files.
Most scripts function independently and don't require additional resources. If any
dependencies are needed, this information will be clearly provided in the installation
documentation and product description.