Disclaimer

No affiliation with Cfx.re, Rockstar Games or Take-Two

Unfckd and unfckd-lite are built by an independent developer. Cfx.re, FiveM, RedM, Rockstar Games, and Take-Two Interactive have no involvement in this project. They have not reviewed it, approved it, sponsored it, or endorsed it.

The names FiveM and RedM appear on this site to describe what the software works with. That is ordinary descriptive use. All trade marks belong to their respective owners.

The same goes for the frameworks named in the example scan output, including QBCore and ox_lib. They appear because they are common on real servers, not because their authors are involved here.

No warranty on the software

unfckd-lite is free software under GPL-3.0, and sections 15 and 16 of that licence disclaim all warranty. In plain words, you run it at your own risk. It is provided as it is, with no promise that it is fit for any particular purpose, and nobody who wrote or distributed it owes you damages if it misbehaves. The full text ships with the source at https://github.com/unfckd/unfckd-lite.

That is the normal arrangement for free software. It reflects the fact that you paid nothing and received the source, so you can inspect exactly what you are about to run.

A clean scan does not mean a healthy server

unfckd-lite reads manifest files and reports what it can detect from them. There are many ways a server can break that a manifest scan will never see.

• Logic errors inside a script that only appear at runtime
• Database problems, missing tables, and bad queries
• Performance problems and resource exhaustion under player load
• Conflicts between resources that both declare their dependencies correctly
• Anything that depends on state rather than on configuration

Treat the report as a useful signal, not a certificate. You stay responsible for your own server.

Test changes before you apply them live

Each finding suggests a fix, such as installing a missing resource or adding a dependency to a manifest. Those suggestions are generated from what the scanner read. They are not reviewed by a person and they do not account for anything specific about your setup.

Back up before you change anything. Test on a development server where you can. Applying a suggested change directly to a live server is your decision and your risk.

Unfckd is not released

The pages on this site describe the Unfckd dashboard, the scan history, the error catcher, and the update alerts as planned work. None of it is available today, none of it is priced, and none of it has a release date. Those descriptions state current intent rather than a promise. Plans change, and features described here may change or never ship. The comparison on the home page marks clearly which parts exist and which do not.

Only unfckd-lite is released. Everything else is in development.

Accuracy of this site

We try to keep the content here correct and current. We do not guarantee it is either. The performance figure quoted on the home page, 184 resources in 0.4 seconds, describes one specific example scan and is not a benchmark you should expect to reproduce on different hardware or a different server.

External links

We link to GitHub, Discord, and other sites we do not control. We are not responsible for their content or their behaviour, and a link is not an endorsement.

How this fits with the terms

This page explains things in plain words. The terms of service set out the binding version, including the limits on liability and the consumer rights that Dutch and EU law does not allow us to exclude.