You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let me begin by saying I am not a programmer, I just couldn't find the answer so I figured it out.
As it stands, the fxmanifest.lua file has as follows:
-- Set this to one of the following:
-- FiveM: "gta5"
-- RedM: "rdr3"
local gameName = ""
fx_version "cerulean"
game(gameName)
rdr3_warning "I acknowledge that this is a prerelease build of RedM, and I am aware my resources will become incompatible once RedM ships."
With this, I kept getting an error: "Warning: Resource spooner is not using CitizenFXv2 manifest. This is not allowed for the current game (rdr3)."
With a bit of research, the problem was obviously not the
fx_version "cerulean"
line, so it had to have been something else. Looking at older manifests, they all had a line that said
games { 'rdr3' }
or, if the case happened to be,
games { 'rdr3', 'gtav' }
or something of the like.
The manifest that comes here states two lines:
local gameName = ""
game(gameName)
Of course, in the parentheses in line 1, rdr3 must go there--which I had done.
I switched it out for
games { "rdr3"}
and it worked. I do not know if it mattered but I used quotation marks instead of apostrophes because the rest of the file did and I assumed it was a protocol thing. In my very limited knowledge of programming, the original option wouldn't make sense, as the line would seem to be reversed, but what do I know; I am a liberal arts student lol.
Anywhilst, perhaps I did something wildly wrong, but it didn't work and now it does, so perhaps consider changing the lines
local gameName = ""
game(gameName)
to
games { "" }
Or not do whatever you want.
I also got rid of the first three informational lines but I assumed those were recognized as comments, but perhaps that was what fixed it--I doubt it, though.
I am not quite sure why it was recognized as an error regarding it not being a citizenfxv2 manifest problem when that was the only line I listed that worked lol.
The text was updated successfully, but these errors were encountered:
Let me begin by saying I am not a programmer, I just couldn't find the answer so I figured it out.
As it stands, the fxmanifest.lua file has as follows:
-- Set this to one of the following:
-- FiveM: "gta5"
-- RedM: "rdr3"
local gameName = ""
fx_version "cerulean"
game(gameName)
rdr3_warning "I acknowledge that this is a prerelease build of RedM, and I am aware my resources will become incompatible once RedM ships."
With this, I kept getting an error: "Warning: Resource spooner is not using CitizenFXv2 manifest. This is not allowed for the current game (rdr3)."
With a bit of research, the problem was obviously not the
fx_version "cerulean"
line, so it had to have been something else. Looking at older manifests, they all had a line that said
games { 'rdr3' }
or, if the case happened to be,
games { 'rdr3', 'gtav' }
or something of the like.
The manifest that comes here states two lines:
local gameName = ""
game(gameName)
Of course, in the parentheses in line 1, rdr3 must go there--which I had done.
I switched it out for
games { "rdr3"}
and it worked. I do not know if it mattered but I used quotation marks instead of apostrophes because the rest of the file did and I assumed it was a protocol thing. In my very limited knowledge of programming, the original option wouldn't make sense, as the line would seem to be reversed, but what do I know; I am a liberal arts student lol.
Anywhilst, perhaps I did something wildly wrong, but it didn't work and now it does, so perhaps consider changing the lines
local gameName = ""
game(gameName)
to
games { "" }
Or not do whatever you want.
I also got rid of the first three informational lines but I assumed those were recognized as comments, but perhaps that was what fixed it--I doubt it, though.
I am not quite sure why it was recognized as an error regarding it not being a citizenfxv2 manifest problem when that was the only line I listed that worked lol.
The text was updated successfully, but these errors were encountered: