Skip to content

add production warning with FiveM official recommended version#20

Open
TGIANN wants to merge 1 commit intojgscripts:mainfrom
TGIANN:main
Open

add production warning with FiveM official recommended version#20
TGIANN wants to merge 1 commit intojgscripts:mainfrom
TGIANN:main

Conversation

@TGIANN
Copy link
Copy Markdown

@TGIANN TGIANN commented May 3, 2026

Surface a red 'Important' note that warns against running latest artifacts in production and links to FiveM's officially recommended build (Windows and Linux) fetched from the changelog API.

image

Surface a red 'Important' note that warns against running latest artifacts
in production and links to FiveM's officially recommended build (Windows
and Linux) fetched from the changelog API.
@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented May 3, 2026

@TGIANN is attempting to deploy a commit to the JG Software Team on Vercel.

A member of the Team first needs to authorize it.

@jrgrimshaw
Copy link
Copy Markdown
Member

@TGIANN Appreciate the PR, but the issue with this is (at least historically), that the recommended version isn't updated very often, hence the reason for this database to exist. It's to ensure that server owners can use a recent artifact release, while avoiding known issues reported by the community.

@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented May 5, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
fivem-artifacts-db Ready Ready Preview, Comment May 5, 2026 3:17pm

Request Review

@TGIANN
Copy link
Copy Markdown
Author

TGIANN commented May 5, 2026

@TGIANN Appreciate the PR, but the issue with this is (at least historically), that the recommended version isn't updated very often, hence the reason for this database to exist. It's to ensure that server owners can use a recent artifact release, while avoiding known issues reported by the community.

Yes, but people are using these insufficiently tested versions on their main servers, and when they cause various problems, they open tickets as if the script is faulty. Currently, 28k versions have various issues such as packet loss and script errors, and when I tell people that this version is broken, they say that no problems have been reported in JG Artifacts. Regardless of the latest versions, using them on main servers should never be recommended.

As a result, this is updated based on community reports, and generally the latest versions are broken

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants