Well, in the SQL database, you use to set any starting load out as you wish...
but it don't work.....
Then, we install the TSW anti-hack who just inject cust_loadout, and cust_loadout_profile folder in the SQL
So we now can set a custom loadout, in "Cust_loadout / profile"
and then put it to an...
I set a TSW anti-hack on my server that inject those cust_loadout and cust_loadout_profile to my DB
Through this way, we success to set a custom loadout per unique ID, and we have no gender selection on the start, if we set it off, we have to choose a gender.....
So.... anyone know if is...
thx, well, we copy paste it to our files, edit, package reupload etc
clean the database, but still don't work...
Heard we have to disable the gender selection.... but obviously, dunno how to..... any way to do this ?
Then this topic could be a kinda clear tutorial lol
.........................................
"server_playerlogin.sqf"
not much like is there a thousant files and folders in those pbos...
Well then we have to replace :
//Record initial inventory
_config = (configFile >> "CfgSurvival" >> "Inventory" >> "Default");
_mags = getArray...
I do modify what it seems logic to modifiy, but we just can't be sure about what we need to change or not :s
is there so many pbos files, and as I ask 10 days ago : "what are those "all files" ?......."
It's maybe simple for a coder, not for a user u know :)
I do change the SQL database, to set a deifferent loadout for everyone, cleared the whole ids, and then, some people are spawning with that custom loadout, and some other (the main part) not....
awww dat Scrumbee, the guy we can't even poke or text on his own teamspeak :D
thx for your answer here :)
edit : hmm I'm actually in this config.cpp (arma2/@dayzoverwatch/addons)
And then :
_____________________
class CfgSurvival {
class Inventory {
class Default {
//weapons[] =...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.