#CW RAIDJOB

1 messages · Page 1 of 1 (latest)

golden granite
#

CW-raidjob2

Has been the closest thing we can find thats actually pretty nice compared to others for missions, quests, heists introductions, etc

Problem were having is the multiple players accepting missions. the script only allows for one as a whole to allow this mission to be started, so therefore it not only puts a cooldown on the initial mission, Now ALL missions are on cooldown. theres alot of expanding that could be done on this script and im willing to help improve it. i know it may of not been designed to be used the way we intend to but i could see this conflicting with a majority of other players around the city that would like to start up different "raids"
i could get rid of the cooldown but now when multiple people accept the job it could potentionally duplicate the cars and peds spawned.
also group missions dont benifit at all, as far as what we've tested. you dont get 4x the reward. were also using the phone reccommended for this group raid. we all get the email. but the reward stays solo

tulip hull
#

So, first things first, are you talking about the raidjob2 or raidjob2-ox? because the non-ox version is never gonna get any update again, way to many issues with spawning.

Now ALL missions are on cooldown. theres alot of expanding that could be done on this script and im willing to help improve it.

Yeah, cooldowns SHOULD be on locations not per job, for sure. Needs a list in the server side that keeps track. Feel free to make a fork and publish any update you make to it thumbup

also group missions dont benifit at all,
This is intended. Design missions around assumed group sizes (this is what the low-mid-high is for). Payout should be relative to difficulty, not to group size. But it's all open source so you can always just add that if you want.

were also using the phone reccommended for this group raid. we all get the email. but the reward stays solo
This is also intended. The person dealing with the bosses is meant to pay out to the people who are in their crew. This is because:

  • It adds the ability for people to hire muscle without the muscle knowing the full payout or the location of the Boss.
  • The script is built up to let anyone return the case at any time. It makes no sense to pay out to everyone in their group since the case contents might get stolen.

But, it's open source, you can just add a loop that gives the payout to everyone in the group if you want to.

golden granite
#

so we are currently using cw-raidjob2, im assuming this is the one your no longer updating. if so is the raidjob2-ox only for OX-inventory? as far as cooldowns for each one im going to assume its going to need an SQL? i'm not the greatest developer but i understand how alot of this works and the exports and such. i just need a better understanding of what i need to do to improve some things with the script. i've only spent a day with it but if you can give some sort of direction on what we can do to change the way it works would be great. and with the groups thing , ok that can be solved the way you designed it. its more of cooldowns being the big issue here, we were basically using the script as an introduction to the city and pointing people here and there to what they could do with a little fun of fighting and grabbing items with reward.

tulip hull
#

so we are currently using cw-raidjob2, im assuming this is the one your no longer updating. if so is the raidjob2-ox only for OX-inventory?
It requires Ox_lib and ox_inventory.

as far as cooldowns for each one im going to assume its going to need an SQL?
No sql needed. Basically the cooldown right now is a boolean in the server file. It needs to be a table that holds location names and their status instead.

golden granite
#

ok thank you for your feedback, may update to ox inventory if we run into anymore issues with other scripts. untill then may just try to make adjustments to the current script. will keep you updated once the rest of our team wakes up so we can discuss these things.

you said the non ox version has a problem with spawning. ive encountered that issue with another script, never wouldve guessed it had anything to do with inventory, or im guessing its ox_lib that handles that?

tulip hull
#

Ox lib has some nice stuff around spawning and syncing peds

#

Not sure what else was reworked tho, since the OX rework was done by Khatrie, not me.

golden granite
#

interesting, does your new raidjob2-ox offer anything additional compared to the one i have?

tulip hull
#

NPCs that work PepeLaugh

#

The normal version works SOMETIMES, but the OX version has worked everytime it was tested as far as we could tell

golden granite
#

gotcha, i did relise that, i thought it was something i broke. i added in random lootbox instead of the % value and such as rewards but this answers that question. will talk to the guys about this, been searching for a good missions script for years now and this is the best we've came accrossed especially being free, even compared to the $80 one thats out which... heh🙊 will keep you updated thanks again!

spring patrol
golden granite
#

apparantly were actually running ox_lib, not that it fixed anything, i take it i still need the inventory for this enhancement? or do i just got a dead script sitting in my standalone folder lol

image.png
spring patrol
#

the ox version doesnt have any of the calls for QB/PS/LJ/Any other inventory in it. it was entirely converted to Ox inventory

#

the metadata handling and such in ox is just miles above any of the other primitive inventories out there.

tulip hull
#

I'd rather die than make cw-tuning in non-ox inventory PepeLaugh

spring patrol
#

lmao it wouldnt exist, QB meta handling is just.... Icky lmao

#

tbf the ox version has all the fixed renewewd group stuff as well, so it properly prompts on the phones per mission per person and such and blah blah too. its not just the base email given either

#

i always forget that was like a major enhancement to it all

tulip hull
#

The absolute craziest thing is that I don't think adding those features into QB would take much time.

spring patrol
#

the syncing is what mattered though lol

tulip hull
#

Yeah for Raidjob

#

but I mean the inventory metadata comparison stuff for example

#

adding that would take like an hour at most lol

spring patrol
#

Ohh, i mean prob not but that means QB would wanna expand from their 2020 mindset of scripting

tulip hull
#

Cant have that

spring patrol
#

dont get me wrong i love QB stuff, but their so dated

#

so many things i was told " Not possible" in the QB discords yet i got it working

golden granite
#

i havnt been to qb discord since my first month of developing, NEVER SOLVED ANYTHING for me lol. i can agree. only thing that ive seen change with qb is the cooler looking notifcation system. oh maybe the frame around the phone removing the camera was pretty cool 🤣

spring patrol
golden granite
#

so are you suggesting switch to a ox framework? talking with my guys they think its incomplete, i myself havnt ventured that route.

spring patrol
#

unfortunately no, because even stuff like QBOX isnt fully release ready yet. i know when i eventually went ox we just ended up doing the migration and conversion for the scripts as required from standard QB stuff. it did take a solid week worth of work to get everything switched over but this was also... 10 months ago now? so things may be easier

#

best bet would prob be to stick to QB as your Base, but integrate Ox as required if you choose to go that route. OR if your base is still generally fresh/new try out Qbox and see how it goes. i know they have done a lot of progress recently so it might not be too bad. Although id expect you will have some compatibility issues youll have to work through.

golden granite
#

ok thanks for the support and advice, doesnt look like i can do much with this. as far as what it offers as default, still useable, still fun unless the ped spawn causes any issues. id say as long as the guy with the key and briefcase is found no big deal. also looking into some of your guys other scripts to use, thanks again!