We actively maintain Viper Multijob, and this page tracks its updates. Keeping a public changelog is part of how we operate — you can see the script is alive, supported, and improving over time. (Update this post as you ship changes; each entry keeps the page fresh, which both buyers and search engines value.)
Why we keep a changelog
An actively maintained script is worth far more than an abandoned one. FiveM, frameworks, and dependencies evolve, and scripts need to keep pace. A visible changelog tells you:
- The script is actively supported
- Bugs get fixed, not ignored
- New features arrive over time
- The creator stands behind their work
When you're choosing a script to buy, an update history is one of the strongest quality signals there is.
How updates reach you
Viper Multijob is delivered through the Cfx.re Portal. When we ship an update, it arrives through the same portal your original purchase did — updates are free. We announce changes in our Discord so you know when something new is available.
Changelog
Latest
- Ongoing maintenance and compatibility updates for current QBCore and ESX versions
- Performance tuning to keep idle resmon at near-zero
- UI refinements and theming improvements
*(Detailed version entries are posted here and in our Discord as they ship.)*
Reporting issues & requesting features
Part of maintaining a script well is listening to the servers running it. If you hit a bug or have a feature idea:
- Open a ticket in our [Discord](https://discord.gg/sJBrnZdD7W)
- Describe your framework, versions, and what's happening
- We'll help directly
A lot of our improvements come from exactly this kind of feedback.
New to Viper Multijob?
If you haven't picked it up yet, Viper Multijob is our dual-framework multijob system — one-click switching, duty toggling, server-side security, a re-themeable UI, and four languages. Read the full feature overview or grab it directly.